James G. Sack (jim) wrote:
Mike Marion wrote:
Quoting markw <[EMAIL PROTECTED]>:
So they are blocking because the "originator" ip is in the header? Or
is being blocked because the from domain doesn't match cox? That'll
break stuff, since most virtual domains don't use their own server.
Do you have this dnsrbl message?
Right. Most of the residential RR IP space is blocked anymore too, but
I've been using an MX host to relay my mail for a couple years now and
have yet to have things blocked simply because the originator IP was
inside the RBL. Yes it shows up in the headers.
I also set it up to use a different port between my home box and MX
too... just to avoid if they ever do block 25 anyway. They could be for
all I know.
I'm a little confused. Can somebody summarize this? Is it that a mail
server inside cox or rr is likely to get marked as spam because it has
an ip that is classified as within those providers' "residential"
ip-space?, or does it relate to reverse lookup verification of the
sending mail server? or both? Or what??? :-\
Without seeing the headers, it's hard to tell. it could be something
as anal as dropping it because it originated in cox's space, but doesn't
have a cox domain. This will break anyone using a virtual domain.
Without seeing the rbl message as to why it was blocked, it's hard to say.
Mark
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
