Spam filtering
in [Postfix]
|
From: Steve Linford on 23 Jun 2010 10:34 On 23 Jun 2010, at 06:34, Stan Hoeppner wrote: > DKIM checks are pretty much useless for killing spam Currently true, but hopefully soon to change Spamhaus is releasing two new DNSWLs in about 4 weeks time, one of which specifically validates DKIM domains against a list of verified known good domains. Once it's available, if the server validates the DKIM domain in the message it can then validate that the domain is not a spammer. At that point DKIM becomes useful for killing spam. I'll post a link to more information about this in a couple of weeks (we're still working on the information pages for it). Regards, Steve Linford The Spamhaus Project http://www.spamhaus.org
From: Stan Hoeppner on 23 Jun 2010 21:10
Steffan A. Cline put forth on 6/23/2010 8:39 AM: > I am assuming from your conf file you have: >> POSTGREY_OPTS="--inet=127.0.0.1:60000" > From the options I see, I could put that into the startup file above by > changing: > OPTIONS="--unix=$SOCKET" > To > OPTIONS="--inet=127.0.0.1:60000" Yeah, that's it, that's the right Postgrey file. You can use a UNIX socket or inet. The key thing is that they must match between postgrey and postfix. Postfix has to know how to communicate with Postgrey. Sometimes using a socket can be problematic or more difficult, specifically in chroot environments, IIRC. This may be why the default recommended setup for on Debian is inet, as Debian runs Postfix in a chroot by default. For these reasons I use the inet interface. It's just easier for me, and no real potential gotchas. > My question now lies in do I need to add any any additional config to > master.cf file to take advantage of this service? No, nothing is needed in master.cf for this, only the line in main.cf. As I stated in a recent post, I've been using Postfix for 5 years now. I have never edited master.cf. -- Stan |