Ok, I really should finish the write up on my setup one day :) I was having the same difficulty as you mentioned. Every one of my users is an alias to a procmail file.
alias file has entry like so: loser1: "| /usr/bin/procmail /etc/procmailrcs/loser1.rc " loser1.rc looks like so (over simplified version): :0fw | spamc -f -u onelegituser :0: * ^X-Spam-Level: \*\*\*\*\*\*\* ! [EMAIL PROTECTED] :0 ! [EMAIL PROTECTED] Then I have a static route to internal.mydomain.com, which is my internal exchange server. My exchange email server emails right out to internet, not thru gateway. Only incoming comes thru SA. I had to make aliases for EVERYONE on the internal exchange server. This was because the exchange server used to be directly on the internet!! (I inherited that!) So inside I had to make alias [EMAIL PROTECTED] Was a pain at first, but now it's just 2 seconds for each new user. ONLY ONE GOOFY PROBLEM. Return requests (read or received) go to the mail daemon of the email gateway. Because the daemon forwarded the email to the internal server, exchange sends the receipt to it. I aliased that to /dev/null. So no receipts go out. No big deal. :) I only have 2 users on the email gateway. root, and onelegituser for doing SA. (That's not the real name!) I have a script that takes a template rc file and creates the new file and alias. So new users are as easy as "crmail newperson" then make their internal exchange account with internal alias. So yes, procmail is trying to deliver it locally. However to a local procmail script that eventually forwards it to internal server. So you would have to setup procmail as local agent. This is however using sendmail. I have no clue about any other mailer. :) This is such a cool setup. I can customize each users procmail script to do anything. For instance, skip SA if the email came from the SA list ;) If I wanted to, I could make additional users to run SA as, with different rulesets. But global has been working great. If anyone else is using procmail and forwarding to internal server, I would love to hear if their setup is different. I never found docs on this kind of setup. I fumbled my way thru this. I bothered the heck out of Theo :) and just experimented. This is why I want to write a complete guide to my setup for the wiki. All I need is time! HTH Chris Santerre System Admin and SA Custom Rules Emporium keeper http://www.merchantsoverseas.com/wwwroot/gorilla/sa_rules.htm "A little nonsense now and then, is relished by the wisest men." - Willy Wonka > -----Original Message----- > From: Jason Williams [mailto:[EMAIL PROTECTED] > Sent: Monday, September 22, 2003 2:57 PM > To: Chris Santerre > Subject: RE: [SAtalk] Using Procmail with SpamAssassin for redirecting > spa m email... > > > Hi Chris, > > Thanks for your reply in response to my question. > Im currently working on trying to implement this, but i've > run into a problem. > > My gateway is running OpenBSD 3.3, postfix-2.0.16 and procmail-3.22. > The problem I seem to be having is actually having postfix > envoke procmail > on incoming email. I cant seem to get it to work correctly. > One thing that I think could be the problem is that procmail > is normally > used for local deliveries, correct? If that is true, then my > mail gateway > is not delivering locally, but instead relaying to my > internal mail server. > > I would like to implement exactly what you suggested: have > email tagged as > spam delivered to a specific account for review, but i'm > having a bugger of > a time trying to figure it out. > > Obivously, procmail will come into play, but since I cant > seem to get it to > run on my mail gateway, im stumped. Do you have any suggestions or > recommendations? > > Thanks Chris. I do appreciate your time and help. > > Cheers, > > Jason > > > At 02:12 PM 9/22/2003 -0400, you wrote: > > > > > -----Original Message----- > > > From: [EMAIL PROTECTED] > > > [mailto:[EMAIL PROTECTED] > > > Sent: Saturday, September 20, 2003 2:34 PM > > > To: [EMAIL PROTECTED] > > > Subject: [SAtalk] Using Procmail with SpamAssassin for > > > redirecting spam > > > email... > > > > > > > > > Hello everyone. > > > > > > Well, after getting some great help from people on this > > > board, I was able > > > to setup postfix ans spamassassin (running as spamd) to > work together. > > > > > > My current setup for SA and postfix is on a mail gateway. > All email is > > > piped through SA and then back to postfix, THEN relayed to my > > > internal mail > > > server. > > > > > > My next task that I want to do is this: > > > > > > All email that is tagged/flagged as spam, will be sent to a > > > specific email > > > account on the mail server, not the mail gateway. Then, I can > > > log in with > > > the specified account on the mail server, and review the > > > email that has > > > been tagged as spam. (BTW, is this the geneeral recommended > > > method? Or is > > > there a better option?) > > > > > > Im thinking that the best way to do this would be with procmail? > > > I'm not sure though, I could be wrong. > > > > > > I was curious if anyone had suggestions on how to go about > > > configuring this. > > > > > > Does anyone have any recommendations or suggestions? > > > Thanks everyone. > > > > > > Cheers, > > > > > > Jason > > > > > > >This is a great way to do it. Actually send high scoring > spam to both an > >internal email account AND an account on the gateway. This > way you can > >review what came in, and on the gateway you start getting a > corpus in mbox > >format to test against. I also send some copies of ham from > a few users to > >an account on the gateway. This way I also have a ham corpus. > > > >I only do this with spam 7+. Between 5 and 7 go to the user. > > > >Chris Santerre > >System Admin and SA Custom Rules Emporium keeper > >http://www.merchantsoverseas.com/wwwroot/gorilla/sa_rules.htm > >"A little nonsense now and then, is relished by the wisest > men." - Willy > >Wonka > ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ Spamassassin-talk mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/spamassassin-talk
