[maccanada]

The latter.
You’ll be told by the blinky lights, error log, and notifications when any of those options need using.

[maccanada]

Hmmmm, just double-checked and realised that my log entries were from my launchd job to run it.

Let me check on a clean server…

[maccanada]

1. You need to type the following in the Terminal:
sudo ln -s /var/clamav/.spamassassin /var/amavis/.spamassassin
This will create a link from the folder that SpamAssassin looks to for Bayesian data (amavis) to the folder that has the Bayesian data written to it during the learn_junk_mail process (clamav).

2. Up until 10.4.2 the daily learning jobs did not run. 10.4.3 fixes that; my server has been running the jobs at 1:30 am every day since the update.

[maccanada]

Andrina did a great piece on exactly this procedure

Importing users into 10.4 without their old passwords will not affect mail…but this method works – obvioulsy test it all out first and have a backup.

We also have articles on backing up the mail server for both 10.3 and 10.4

[maccanada]

Yeah, a few things…like the owner of the directories has changed. It’s all covered in the Migration doc

[maccanada]

The test systems here are OK so far on Server, I’ve seen some Mail.app plugins on the client side causing some problems – disabling them clears things up nicely. Some good changes to LoginWindow, among many others (the following is pasted from Scott Barber’s MacEnterprise post):

Host Information Field

The Host Information field in the Login Window UI displays a number of different bits information such as the System Build, System Version, Host Name (the default), Serial Number, or Time.

In Mac OS X 10.4.3, IP Address and Network Account Status were added. The IP Address is that of the primary interface. If that interface doesn’t have an address the IP Address is not shown.

The Network Account Status provides information about the availability of Network Accounts. The following states are available:

GREEN DOT – Network Accounts Available (I have connectivity to ALL of my remote DS)
YELLOW DOT – Some Network Accounts Available (I have connectivity to some, but not all of my remote DS)
RED DOT – Network Accounts Unavailable (I have no connectivity to ANY remote DS)
Network Access Requires Login (Access to the network requires authentication — i.e. 802.1x)

An Administrator can specify which field to show when loginwindow UI displays by doing the following:

defaults write /Library/Preferences/com.apple.loginwindow AdminHostInfo <desired field>

Where is one of the following: HostName, SystemVersion, SystemBuild, SerialNumber, IPAddress, DSStatus, or Time.

Once you have written the default to a sample workstation, you could use the Workgroup Manager preference editor to apply this preference to ANY computer list (including Guest Computers) in your remote Directory Service.

Startup Delay

The startup delay will delay the display of the Login Window UI by the number of seconds specified by the system administrator.

This is done to allow the system time to finish obtaining an IP Address via DHCP and for DS to bind to the servers.

If the Login Window UI detects that the network servers are available when it starts, it will skip the delay.

If the network servers become available before the delay expires, the Login Window UI cancels the delay and displays. An Administrator can specify the startup delay d by doing the following:

defaults write /Library/Preferences/com.apple.loginwindow StartupDelay -int <number of seconds to delay>

Once you have written the default to a sample workstation, you could use the Workgroup Manager preference editor to apply this preference to ANY computer list (including Guest Computers) in your remote Directory Service.

[maccanada]

Right, mine is set at 3 and I get maybe one or two sneak through each day…eventually they get picked up on the bayesian rules…

The ALL_TRUSTED rule is getting hit more frequently – it means the message hasn’t passed through any suspect hosts. I think it’s down to zombie pc’s getting used as mailers and the message comes through major ISP’s. (A google search for ALL_TRUSTED shows a lot of discussion). This will negatively score the message.

You can either lower your level setting, raise the score for the rules that are getting triggered (in 50_scores.cf in /usr/share/spamassassin), write your own rules tailored to the kind of messages you’re receiving or lower the score for the ALL_TRUSTED rule (it’s also in 50_scores.cf in /usr/share/spamassassin)

You’re also not getting any Bayesian rules triggered, are you running the learn_junk_mail script?

There’s an article on writing rules (among other things)…

[maccanada]

No experience…I would think any FC attached tape device would be fine…compatibility with the backup software would be the main factor here. How much do you have to backup and how long do you have to back it up?

[maccanada]

Do you have the performance cache turned on? It uses port 16080

[maccanada]

What exactly are you trying to achieve? There may be better ways than forcing kills on imapd, which could lead to other issues.

[maccanada]

defaults read com.apple.softwareupdate

CatalogURL is the string you’re looking for

Running tcpdump on a clean box as you run software update will provide all the details of what’s going on

~Ian

[maccanada]

Your log files should tell you what’s going on:
(They’re in /var/log/)

[maccanada]

local.cf is written to by server admin, and read every time the mail service starts. Change the header rewrite message in Server Admin and it updates both amavisd.conf and local.cf

local.cf should be used for creating custom rules for SpamAssassin. All of the tag levels for hits are defined in amavisd.conf

[maccanada]

I haven’t checked thoroughly, but I think they’re all handled by launchd: launchctl list shows entries for cyrus, postfix, amavis and clamav

[maccanada]

The settings are in /etc/imapd.conf
configdirectory: /var/imap
partition-default: /var/spool/imap

However, you may be better off storing stuff on a RAID and simply running a script to re-zone the storage to your second server…or go direct and simply unplug the cable from the dead server and plug it into your standby machine. Apple does not support 10.3 or 10.4 mail servers with storage on Xsan volumes:
http://docs.info.apple.com/article.html?artnum=301640

Cyrus murder is also designed to separate front-end/back-end servers for this kind of fault-tolerance/load-balancing role.

[Author]

Posts