On Fri, 2007-12-07 at 14:03 -0500, Rich Dygert wrote: > McDonald, Dan wrote: > > On Fri, 2007-12-07 at 11:15 -0500, Rich Dygert wrote: > > > >> A couple months ago my email traffic doubled (from 1 million a day to 2 > >> million a day). After some investigation I found that a spammer was > >> sending from [EMAIL PROTECTED] and I was getting the back splatter. I > >> cancelled the [EMAIL PROTECTED] account and thought the spammer would soon > >> stop. Turns out I was wrong, the spammer is still at it. > >> [...] > >> Is there a better way to handle something like this? > >> > > > > SPF or domainkeys. Then Walmart would know that the message being sent > > was forged.
> That is a reasonable suggestion but my customers don't always send email > from my SMTP servers. As I understand SPF I would have to list my > servers and says "It is not an error if it comes from some other server." > > Would that not be a problem for Domain Keys also? Yes. If you don't control who can send mail with your return address, then you have no way to eliminate joe-jobs. That is a business decision. On the other hand, Walmart shouldn't be back-scattering you.... -- Daniel J McDonald, CCIE #2495, CISSP #78281, CNX Austin Energy http://www.austinenergy.com
signature.asc
Description: This is a digitally signed message part
