Re: [qmailtoaster] Re: spf for domain question

[David Milholen]

Eric,  I live for spamdyke it is like my ultimate shield against most threats. It is these annoying emails that seem to get thru. I believe I have spamassasin on but I am not sure. I do not think I have configured it yet. Ever since I tightened up the server on authentication and using tls everything is soooo much better. If I can just get a handle on these annoying mails coming from att.net and other huge mailers like these.  I only have the one server for all mail coming or leaving the entire network all subscribers on my network are blocked on sending mail port 25 unless it has a valid pop server or have a valid auth account with our server.  Little tricks at the pop sites on firewalls handle all of that and keep the network quiet.   --Dave   On 10/21/2010 9:28 AM, Eric Shubert wrote: SPF is not going to cut it for you. SPF is something that the sending server needs to set up, and per the Received-SPF header, att.net does not have this set up, so there's nothing you can do SPF-wise. Even if they did public SPF records, the email is actually coming from their servers, so it wouldn't do anything to reduce the spam coming from there. I don't think spamdyke would be any help here either, as these are major mailers that also send out valid messages. You'll need to rely on spamassassin scanning for this sort of thing. I see that you have simscan running, but I don't see any spamassassin headers. Do you have spamassassin activated? I would. I'd be sure to have spamdyke installed before activating spamassassin, as the load on your server will be substantially higher if you have spamassassin on with no spamdyke. -- David Milholen Project Engineer P:501-318-1300