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. --
![]() David Milholen Project Engineer P:501-318-1300 |
- [qmailtoaster] spf for domain question David Milholen
- [qmailtoaster] Re: spf for domain question Eric Shubert
- Re: [qmailtoaster] Re: spf for domain question David Milholen
- [qmailtoaster] Re: spf for domain question Eric Shubert
- Re: [qmailtoaster] Re: spf for domain ques... David Milholen
- Re: [qmailtoaster] spf for domain question Pak Ogah