According to Matt Kettler: > 9 times out of 10, this is caused by someone who's calling SA at the MTA > layer, but they're trying to use the user_prefs in the recipients home > directory. > > SA has no reliable way to determine who the recipient is, given the > content of the message it receives. Even if it could, it would not know > if that user has a local account or not. > > Therefore, unless told otherwise with spamc -u, SA uses the userprefs > that belongs to the userid that executed the call to spamassassin. > > Most MTA layer integrations wind up always calling SA as the same system > account user that the MTA runs as, resulting in only one user_prefs ever > being used.
Yikes! Somehow I didn't catch this. I'm using spamass-milter and it has a "-u" option for just this situation. Many thanks!! Rich
