Haines wrote: > DROPPRIVS=yes > PATH=/bin:/usr/bin:/usr/local/bin > SHELL=/bin/sh > # Spamassassin > :0fw > * <300000 > |/usr/bin/spamassassin > # Spamassassin > :0fw > * <300000 > |/usr/bin/spamassassin
> I didn't realize that procmail/amavisd-new was an either/or situation, > and I didn't mention procmail because it knew it was not doing any spam > filtering. Maybe not filtering, in the sense that it was not discarding messages, but procmail was having spamassassin scan your messages. So you don't misunderstand, you can still use procmail, but here you WERE using procmail to call spamassassin (twice!) to scan your mail. This is where the (non amavisd-new) headers were coming from. You can use this file (for other purposes) if you like, but at the very least get rid of (or comment out) the two spamassassin entries: > # Spamassassin > :0fw > * <300000 > |/usr/bin/spamassassin > # Spamassassin > :0fw > * <300000 > |/usr/bin/spamassassin > But the issue is really who is calling for the filtering, > and that should be amavisd-new, not procmail. Although you don't say > explicitly, To keep procmail out of the spam business, I'll just > comment/remove the /etc/procmailrc file. If you don't have any other plans for it, I believe this would be an OK thing to do. You know, you can create a .procmailrc file in your home directory (it may already exist) to perform various tasks, one such task would be to read the headers of your mail, looking for text such as "X-Spam-Status: Yes" and act on that. This example moves spam to a different folder: :0: * ^X-Spam-Status: Yes /home/username/mail/spam See: http://spamassassin.apache.org/full/3.0.x/dist/procmailrc.example for other examples. So, as you can see, it is possible to use procmail to send your messages to spamassassin (but because you are using amavisd-new, this is not recommended), and then also use procmail to act on the results of the spamassassin headers. As I said before, the disadvantage would be you are not doing a virus scan, and you are missing out on other features that amavisd-new provides. The point was that amavisd-new will use spamassassin to scan mail, and if properly configured, will create the X-Spam type headers, so it is a waste to have procmail do this also. If you like, you *can* use a combination of amavisd-new and your ~/.procmailrc file to have complete control of your spam. Gary V ------------------------------------------------------- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42" plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php _______________________________________________ AMaViS-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/amavis-user AMaViS-FAQ:http://www.amavis.org/amavis-faq.php3 AMaViS-HowTos:http://www.amavis.org/howto/
