Yahoo Groups archive

Milter-greylist

Index last updated: 2026-04-28 23:32 UTC

Message

Re: [milter-greylist] SPF breakage

2007-03-22 by Mart Pirita

Tere.

Sorry, second try, don't know why previous message wasn't sent:

Mar 22 01:31:12 tibu sendmail[14096]: l2LNV0vs014092: 
to=<milter-greylist@yahoogroups.com>, ctladdr=<sysadmin@...> 
(516/500), delay=00:00:12, xdelay=00:00:12, mailer=esmtp, pri=121994, 
relay=mta7.grp.scd.yahoo.com. [66.218.67.33], dsn=2.0.0, stat=Sent (ok 
1174519872 qp 99928)



> When "nospf" option is unset everything passes through due to change
> of spf.c on 2007/01/28.
>
>   

I'm confused, does or doesn't this patch concern me?

You see, I have always compiled milter-greylist with same options:

./configure --with-user=smmsp --without-db --without-drac-db
\
    --with-conffile=/etc/mail/greylist.conf
--with-dumpfile=/etc/mail/greylist.db \
    --bindir=/usr/local/sbin --enable-dnsrbl --with-libbind=/usr/lib

And I presume, that the spf stuff is optional, not default choice?
Anyway I don't want to use spf feature. However since I compiled and
installed the milter-greylist-3.1.7 I noticed a lot spam coming true, so
I did even increase the delay time, but later checked logs:

Mar 22 00:24:59 tibu milter-greylist: Sender IP 218.113.87.15 and
address <wordsbyjoy.com@...> are SPF-compliant, bypassing
greylist
Mar 22 00:35:53 tibu milter-greylist: Sender IP 83.20.171.150 and
address <repetitionopu@...> are SPF-compliant,
bypassing greylist
Mar 22 00:46:38 tibu milter-greylist: Sender IP 85.82.202.106 and
address <hassan@...> are SPF-compliant, bypassing greylist

What the hell is going on? As I haven't compiled milter-greylist with
the spf support, also the nospf option is commented out in conf file.
Should I enble it, or use --without-libspf2 (btw I don't even have any
spf sources, etc at all in my computer) option when compiling?


-- 
Mart

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.