Benoit,
Thanks for the help. It at least stimulated some thought. The
netpluscom.com admin
solved the problem by intentionally opening TCP port 53 on his DNS firewall
(previously
only open to UDP port 53). It looks like, in the process, he also put his
domain servers
first in the MX records, above AT&T's. Note that we both use AT&T as one of
our bandwidth
sources. Mail is currently flowing freely to the netpluscom.com domain.
The question now becomes, does IMS "REQUIRE" Tcp port 53 be open on a dns
server
somewhere?
If so, is it possible to change this IMS behavior to allow IMS to also
use TCP
port 53 ???
Thanks to all.
Rich
-----Original Message-----
From: BSarton <[EMAIL PROTECTED]>
To: [email protected] <[email protected]>
Date: Monday, December 15, 2003 2:46 AM
Subject: Re: DNS & IMS Help
>Rich,
>
>When I ping netpluscom 's MX serveur (cuda) , I get a normal ping answer ,
>but when I ping the name serveur (sandy) , which is in the same class than
>cuda ( ie 207.140.80/24 ), I get a different pattern,
>like : answer from 12.118.224.38 - impossible to reach destination network
>
>Is that what you would expect ?
>
>Benoit
>
>
>
>----- Original Message -----
>From: "Rich Warren" <[EMAIL PROTECTED]>
>To: <[email protected]>
>Sent: Saturday, December 13, 2003 5:45 PM
>Subject: DNS & IMS Help
>
>
>| Hello,
>| I have a few domains to which we can not send e-mail,
>loganclaypipe.com and
>| netpluscom.com. I have tried all suggested testing described under the
>"Unusual DNS
>| Resolution ? Issue" thread with no success as to why I can not send to
>these domains. I
>| can receive from them, but any messages sent just get stuck in the hold
>queue for a few
>| days and then are returned with the message "cannot resolve domain". The
>domains resolve
>| just fine on the mail server and any other machine that I have. My MCSE
>has no additional
>| suggestions. This seems to have started at about the time that I went all
>AT&T as a
>| bandwidth provider.
>| So back to basics. My question for the the group is:
>| In detail, can anyone tell me how IMS sends out mail? In particular,
>how does IMS
>| send out mail that may be different than any other e-mail server?
>| I seem to be looking for what must be a very small, but important
>difference, and
>| perhaps, it also has something to do with the way I am routed through
>AT&T. On the ATT
>| side, the only difference there (of which I am aware) is that I am using
>their NxT1
>| service. This bonds T1's using CEF (Cisco Express Forwarding). This
>setup sends backets
>| out equally through multiple T1's and does not retain local route history,
>i.e., no route
>| cache. In theory, this should have nothing to do with anything, but I am
>grasping at
>| straws.
>| Thanks in advance.
>| Rich
>| [EMAIL PROTECTED]
>|
>|
>| This is the discussion list for the IMS Free email server software.
>| To unsubscribe send mailto:[EMAIL PROTECTED]
>|
>| Delivered by Rockliffe MailSite
>| http://www.rockliffe.com/mailsite
>| Rock Solid Software (tm)
>|
>
>This is the discussion list for the IMS Free email server software.
> To unsubscribe send mailto:[EMAIL PROTECTED]
>
> Delivered by Rockliffe MailSite
> http://www.rockliffe.com/mailsite
> Rock Solid Software (tm)
>
This is the discussion list for the IMS Free email server software.
To unsubscribe send mailto:[EMAIL PROTECTED]
Delivered by Rockliffe MailSite
http://www.rockliffe.com/mailsite
Rock Solid Software (tm)
