Man, they'll try anything to hack your system...

[Dan Jenkins]

Fred wrote:

>  I've run into that problem in the past. Forget emailing to anyone on
>  AOL from your own "private" MX.

FWIW, I've compiled a list I use. I run a few mail servers for clients 
on cable connections.
Email sent to the domains below needs to be routed through the cable 
ISP's SMTP server.
Whatever blacklist rcn.com or rr.com (I forget which) uses also includes 
DSL lines and T1s.
So, a client with a T1 for ten years is blocked with a mildly snotty 
message. No reply to any
contact attempts to resolve the matter, of course. Whenever I discover a 
new one, I add it
to all the clients' lists. (Yes, I could simply relay all their mail, 
but I know of one ISP which
apparently discards all undeliverable emails without any notice to the 
sender of the failure.
I prefer to be more in control.)

Here's my list from Postfix's transport table:
adelphia.com
adelphia.net
aerosat.com
amerprinting.com
aol.com
bellsouth.net
can.xerox.com
cthulhu.neutraldomain.org
earthlink.net
ed.state.nh.us
hp.com
juno.com
lightshipmail.net
mailer-useast.xerox.com
mailstore1.secureserver.net
mail.support.hp.com
mail.tfsd.sk.ca
monster.com
moria.seul.org
netscape.net
netzero.com
netzero.net
prodigy.net
rcn.com
registeredsite.com
rr.com
sbcglobal.net
schoolforge.net
server.totalnetnh.net
smtp.secureserver.net
state.nh.us
support.hp.com
supportwebsite.com
totalnetnh.net
veeco.com
verizon.net
williampikedesign.com
wmconnect.com
xerox.com
yahoo-inc.com

-- 
Dan Jenkins (dan at rastech.com)
Rastech Inc., Bedford, NH, USA --- 1-603-206-9951
*** Technical Support Excellence for over a quarter century