Checking Elastic IPs for spammer/blacklist status

[Aaron Unger]

Hi all-

I remember there being some headaches involving an elastic IP in AWS
that once was associated with spammers and was added to some common
blacklists. What's the best way to check if a new elastic IP is "clean"?

I found this site which seems like a start:
http://cnet.robtex.com/107.22.195.html

Any others?

-- Aaron

[Parker Morse]

I've used the MXToolbox Super Tool for this: http://www.mxtoolbox.com/SuperTool.aspx .

We had a multi-point checklist for avoiding mail sent from Rails servers getting classified as spam. Some of the points had a lot of sub-detail, but it boiled down to this (in order of descending importance)

* Make sure the IP isn't blacklisted

* Send good-looking email (N.B. this doesn't mean content - it means packaging, headers, etc. This is a place where there's a fair amount of detail.)

* Use SPF records.

* Use DKIM-signing.

The rough checklist of "sending good-looking email" was,

* Use host SMTP (sendmail/postfix/qmail) instead of Ruby SMTP.

* Use the same sender and reply-to addresses.

* Give sendmail a signature address using the -f flag.

-- Aaron

--
----
post message :cc-developers@googlegroups.com
unsubscribe: cc-developers-unsubscribe@googlegroups.com
more options: http://groups.google.com/group/cc-developers?hl=en

--

Parker Morse | pmo...@concord.org

The Concord Consortium | http://concord.org

https://twitter.com/concorddotorg https://www.facebook.com/concordconsortium

Dedicated to transforming education through technology.