Quoting Peter Maas <[EMAIL PROTECTED]>: > I just setup Qmail-scanner + spamassassin yesterday. > > If you have an entry like > 63.172.73.:allow,RELAYCLIENT="" > > Spamassassin will NOT scan that message, or messages from those ip > addresses. > > Header from yahoo.com (non relay client ip) > Received: from [EMAIL PROTECTED] by 11.goquest.net by uid 502 with > qmail-scanner-1.12 (spamassassin: 2.30. . Clear:SA:1(1.6/1.0):. Processed > in > 0.345283 secs); 20 Jun 2002 16:22:20 -0000 > X-Spam-Status: Yes, hits=1.6 required=1.0 > > Header from goquest.com (relay client ip) > Received: from [EMAIL PROTECTED] by 11.goquest.net by uid 502 with > qmail-scanner-1.12 (spamassa > ssin: 2.30. . Clear:. Processed in 0.055295 secs); 20 Jun 2002 > 16:28:53 -0000 > > Both of the messages had the exact same content. > > Just to restate, if a message comes from a RELAYCLIENT it is never sent to > the spamd daemon. > > This about drove me crazy before I figured it out > > Peter Maas > pixl@!goquest.com >
I have the same problem. I have 2 Qmail processes running. The first excepts connections on port 25 on all interfaces and forwards them to port 26 on 127.0.0.1. I have 127.0.0.1:allow,RELAYCLIENT="" in my smtp.rules file. How do you get around spam assasin not testing the emails? Maybe in my case I have two qmail-scanners running. The first on port 25 just does the spam stuff. The second does the virus checking on port 26? Any ideas? Dan ------------------------------------------------------- Sponsored by: ThinkGeek at http://www.ThinkGeek.com/ _______________________________________________ Qmail-scanner-general mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/qmail-scanner-general
