On Sat, Mar 14, 2009 at 06:21:16PM -0000, Jim Hermann wrote: > --- In milter-greylist@yahoogroups.com, Petar Bogdanovic <petar@...> wrote: > > > > On Fri, Mar 13, 2009 at 09:58:57AM -0500, Jim Hermann - UUN Hostmaster wrote: > > > > > > Also, the spamd > 5 only blocks messages with a score above 5.5. I can't > > > put 5.0 in the dacl line. > > > > Would you mind pasting some logs? (incl. spamassassin/spamd output) > > Actually, it appears that the problem is with spamd scores between 5.00 and 5.05. > > Mar 10 07:20:18 host sm-acceptingconnections[16729]: n2ACK3Zk016729: from=<info@...>, size=2541, class=0, nrcpts=1, msgid=<20090306140313.M58348@...>, proto=ESMTP, daemon=MTA, relay=server.arinsa.com.pe [161.132.180.62] > Mar 10 07:20:18 host spamd[16591]: spamd: connection from localhost.localdomain [127.0.0.1] at port 45863 > Mar 10 07:20:18 host spamd[16591]: spamd: checking message <20090306140313.M58348@...> for (unknown):98 > Mar 10 07:20:19 host spamd[16591]: spamd: identified spam (5.0/5.0) for (unknown):98 in 0.8 seconds, 3006 bytes. > Mar 10 07:20:19 host spamd[16591]: spamd: result: Y 5 - ADVANCE_FEE_2,BAYES_50,SUBJ_ALL_CAPS scantime=0.8,size=3006,user=(unknown),uid=98,required_score=5.0,rhost=localhost.localdomain,raddr=127.0.0.1,rport=45863,mid=<20090306140313.M58348@...>,bayes > =0.430686,autolearn=no > Mar 10 07:20:19 host sm-acceptingconnections[16729]: n2ACK3Zk016729: Milter add: header: X-Greylist: .... > Mar 10 07:20:19 host sm-acceptingconnections[16729]: n2ACK3Zk016729: to=<xxxxx@...>, delay=00:00:02, mailer=virthostmail, pri=32541, stat=queued I don't understand. The score of this message is exactly 5. And since 5 is not >5, the message gets queued. > spamd also will report non-spam messages with the same score report: > > Mar 11 15:50:01 host spamd[23462]: spamd: clean message (5.0/5.0) for (unknown):98 in 2.1 seconds, 4701 bytes. There is a difference between spamd and milter-greylist when it comes to the decision, whether a message is spam or not. The former decides based on the required_score threshold in local.cf and the latter based on dacls in greylist.conf. Therefore, even if spamd considers the message as being spam does not necessary mean that milter-greylist thinks the same and since it's milter-greylist who decides, the reported result by spamd is irrelevant. Petar Bogdanovic
Message
Re: [milter-greylist] Re: Odd Behavior with dacl in version 4.2b1
2009-03-15 by Petar Bogdanovic
Attachments
- No local attachments were found for this message.