Comcast's blacklist ~ Epsilon server

[j-z]

Epsilon has been on-and-off the Comcast blacklist 4 times in the past 10 days. The problem is that once it comes off the blacklist it goes right back on. The reason, as best as I can tell, is that when spam gets forwarded through Epsilon (or whichever server handles it) Comcast sees that as spam even though it doesn't originate from the Epsilon server.

One of many articles on the subject:
http://www.mercurynews.com/mld/mercurynews/15393026.htm

My suggestion -- in that I don't see a fix -- is to stop forwarding email to Comcast email addresses.

The downside of NOT doing this is that Comcast will blacklist the server and NO email will go to ANY Comcast users.

[RobbieLePommie]

Have you raised a ticket? Nothing we can help with in the forum but the server admins may be able to spot a rogue script or something that's causing this problem.

Although, looking at that article you posted, it may be that comcast is blocking geniune e-mails (a-la AOL)

[j-z]

Yes, I've been working with Support on this problem. They've enabled spam filtering on all the comcast forwards which will hopefully reduce the amount of spam that makes it to Comcast and keep us off the blacklist. Aside from that it seems there's no fix.

[j-z]

The Epsilon server is once again on the Comcast blacklist. I've submitted a support ticket. The issue I see, that is going to arrise again and again, is that every time an email redirect is created on Epsilon that redirects spam to Comcast we run the risk that Comcast will decide to blacklist Epsilon. But what to do about it? I'd rather we can be PROACTIVE and not REACTIVE on this issue. I handle 90% of my client's email set-up so I know when I'm redirecting to Epsilon and can set-up filtering. But how about the rest of us on Epsilon? Is Epsilon strickly used for resellers, or is HN also selling individual accounts there? Any ideas?

[j-z]

Support had this to say:

There were some bad php forms and contacs on the server and the spammers take advantage of them and sent smap using the server. We have disabled these scripts and announced the respective clients. But this can happen again since many clients dont secure their scripts especially the contact forms and with the help of these a spammer can easily spam using the server.

[RobbieLePommie]

This, unfortunately, will probably be there until the end of time through any shared hsoting service. The only options are:
- stop allowing sendmail access to PHP / CGI scripts (that would cause problems for many websites)
- ensure all mail forms are vetted (very tricky to do)

The best chance you have is to go dedicated and start vetting forms. But I know I couldn't do that for my (very limited number of) clients. I don't know how many you've got, but if it's only few and mail is critical, then that may be your best option.

It's cruel to blame the programmers (everyone starts somewhere) so one day, just one day, perhaps something can be done to sort out spam at the source. But perhaps I'm dreaming.