On Tue, Jan 30, 2007 at 04:11:25PM -0800, Paul Johnson wrote: > Greg Folkert wrote: > > > I am running SA using SA-Exim at SMTP time. This then rejects the mail > > before it is accepted, if it doesn't do RFC822 properly. > > > > Yeah, I know this is against the RFC, but it has reduced the processing > > on my machine by magnitudes. If they really want to send it to me, > > they'll do it the right way. > > Do you have spamassassin configured so each user has their own > ~/.spamassassin read in for email destined for them? I've been trying > to figure out how to do that so I can implement it at my site and > suggest it to people considering far worse alternatives > (challenge-response, address munging, etc). the easiest way I can find to do this is to have the users call SA from their procmail recipes. In that case, the child spamd will be called as that user and it will then look in that user's ~/.spamassassin. something like: :0fw * < 256000 #big messages can overload SA, supposedly | /usr/bin/spamassassin <options you like here> :0: * ^X-Spam-Status: yes /dev/null should more or less do it. otherwise you have to configure your MTA so that *it* calls SA as the recipient and I don't have a clue how to do that though it can surely be done. Probably one of the methods that uses SA as a transport is the way to go in exim. just a guess. A
Attachment:
signature.asc
Description: Digital signature