I am having a strange problem: our users that are using slocal (from nmh) in their .forward files do not have their email messages go through SpamAssassin. Note that their mail does cget correctly processed by our milters (we have two). Deleting their .forward fixes the .problem. The .forward simply calls slocal, which has a single default entry to delivery the mail to /var/spool/mail. We used to use the suppressdup option to eliminate multiple delivery of the same message, but we haven't gotten around to converting every account from maildelivery/.forward to procmail.
Procmail users (those with or without a custom .procmailrc file) are just fine. Our setup is SpamAssassin 2.11 with spamd, sendmail 8.12.2 with milter support, perl 5.6.1 and procmail 3.22 as the default local mailer. I was under the impression that the Spamassassin and any milters actually happen BEFORE stuff in the .forward or the .procmailrc. We've confirme that the milters process each message, but not spamd. So what gives? Why would spamd not process the message if .forward has a call to slocal? the only strange thing I can find in the logs are the following entries: Mar 21 11:02:20 lester.arraycomm.com spamd[6652]: Still running as root: user not specified, not found, or set to root. Fall back to nobody. Mar 21 11:02:22 lester.arraycomm.com spamd[6652]: clean message (0/5) for root:60001 in 2 seconds. But these happen even when slocal is not part of the .forward. Cheers. -- Timothy Demarest ArrayComm, Inc. [EMAIL PROTECTED] 2480 North 1st Street, Suite 200 http://www.arraycomm.com San Jose, CA 95131 _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
