Mail Routing Problem
- From: howard@xxxxxxxxxxx
- Date: Wed, 03 Jan 2007 20:22:47 -0500
Hello.
I have a difficult and unusual mail rouing problem that I have not
been able to solve. While I realize this is not exactly the correct
group to be asking in, from reading the postings you guys are very
good at solving mail routing problems.
If you'd like to take a crack at it, here is the scenario:
I am a comcast.net user. I have my own domain which is neteast.com.
The neteast.com domain is parked at EasyDNS (www.easydns.com) which
also handles my DNS records. For neteast domain email, I have
mailmaps at EasyDNS that map back to my Comcast email addresses.
I set up Lyris ListManager 9.1 (www.lyris.com) to test out listerv
functionality.
The listserv works great except it cannot send email from the list to
either neteast.com or comcast.net addresses. This is true for any
address in these domains. It can send to every other domain I tested.
Here is a log failure entry for a sample neteast.com recipient:
Wed, 03 Jan 2007 18:33:35 Sending email to: howard@xxxxxxxxxxx
<-- DNS info available for: neteast.com
--> Attempting to connect to: neteast.com (205.210.42.52 25)
<-- Connected to: neteast.com (205.210.42.52 25)
<-- 220 storm.easydns.com ESMTP spoken here.
--> HELO mail.neteast.com
<-- 250 storm.easydns.com
--> MAIL FROM: bounce-60-8@xxxxxxxxxxxxxxxx
<-- 250 Ok
--> RCPT TO:<howard@xxxxxxxxxxx>
<-- 571 <c-69-140-35-107.hsd1.md.comcast.net[69.140.35.107]>: Client
host rejected: dialup/DSL/cable host, please use your ISP's SMTP
server
Here is a log failure entry for a sample message comcast.net
recipient:
Wed, 03 Jan 2007 18:33:34 Sending email to: howard100@xxxxxxxxxxx
<-- DNS info available for: comcast.net
--> Attempting to connect to: comcast.net (206.18.177.26 25)
<-- Connected to: comcast.net (206.18.177.26 25)
<-- 220 alnrmxc19.comcast.net - Maillennium ESMTP/MULTIBOX alnrmxc19
#122
--> HELO mail.neteast.com
<-- 250 alnrmxc19.comcast.net
--> MAIL FROM: bounce-60-10@xxxxxxxxxxxxxxxx
<-- 550 69.140.35.107 blocked by ldap:ou=rblmx,dc=comcast,dc=net ->
Comcast.net subscribers are not permitted to directly connect to this
mail server. If you are a Comcast Commercial Services customer and
need support, please contact support_biz@xxxxxxxxxxxxxxxxx
In theory, all outgoing SMTP traffic from the listserv should be going
to EasyDNS.
My guess is that Comcast is recognizing my IP address as one of their
own and is intercepting the outgoing mail and routing it internally.
Comcast says it's not their problem. They fault EasyDNS. EasyDNS
claims its a Comcast problem.
Does anyone have a solution or a workaround?
Direct replies would be appreciated to howard@xxxxxxxxxxx
Thanks.
.
- Follow-Ups:
- Re: Mail Routing Problem
- From: Steve Schofield
- Re: Mail Routing Problem
- Prev by Date: Re: SMTP and POP3
- Next by Date: Re: Mail Routing Problem
- Previous by thread: Re: OWA and IIS6 on second server
- Next by thread: Re: Mail Routing Problem
- Index(es):
Relevant Pages
|