>List: openbsd-misc >Subject: Re: spamd greylisting: false positives >From: peter () bsdly ! net (Peter N ! M ! Hansteen) >Date: 2012-05-27 23:19:47 >Message-ID: 87sjel43fw.fsf () deeperthought ! bsdly ! net >[Download message RAW] > >> Or did you mean, this breaks spamlogd, rather? >> >> pass in on egress proto tcp from any to egress \ >> port smtp rdr-to 127.0.0.1 port spamd synproxy state >> >> This is what it was. The logging is on now. > >The important ones to log are the rules that pass smtp traffic from the >members of the spamd-white table (and nospamd if you're using that) plus >the one that passes smtp traffic from your real mail server to >elsewhere. See the spamd and spamlogd man pages, it's explained there.
Ok, I was doing this. I just started logging the rdr-to spamd rule too. >But why are you synproxying for spamd? Why shouldn't I? These guys do in their example. https://calomel.org/spamd_config.html >delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds. It's cool to see an on-topic sig. .d.d.
