Re: Is it possible to trace where an e-mail travels?
- From: Unruh <unruh-spam@xxxxxxxxxxxxxx>
- Date: 1 Nov 2006 18:26:24 GMT
Pascal Hambourg <boite-a-spam@xxxxxxxxxxxxxxx> writes:
Hello,
Polaris431 a écrit :
We switched ISP's. The new one is in a different country although the
domain name has remained the same. Normally, they say it can take up to
3 days for the new DNS Primary domain to update throughout the Internt.
Normally, it is good practice to reduce the DNS record TTL (time to
live) value soon enough before doing the change so that the old data in
DNS caches expire within a few minutes or hours.
It does not matter. Those "time to live" are advisory and many places
ignore them.
1. We used 1 ISP for 2 domains: domain1.com and domain2.com. Both are
located in Israel. Both domains used the same mail server.
2. We move domain1.com to the USA and have it hosted by an ISP there.
You don't move a domain to a country because a domain is just a name, it
is not physically located in any country. You just move hosts. What
host(s) did you move ? Authoritative DNS servers, mail servers ?
"move the domain" means "move the host and the DNS record associated with
that domain".
4. People can send and receive e-mail on both domains to and from
anyone with one exception: if an e-mail is sent from the mail server on
domain2.com to domain1.com, it never arrives and no message is sent
from any mail server indicating any problem. Some people in Israel can
send an e-mail to domain1.com or domain2.com and it arrives. If someone
in Israel is using a different ISP, then their DNS is probably correct.
If they are using the same ISP, it is possible that there are multiple
DNS servers and the one they are using happens to be updated.
It would then logically appear that the mail server on domain2.com is
forwarding the e-mail not to the new ISP but has an old cached DNS on
its system somewhere.
Cached data should have expired, unless you had set a very long TTL. If
TTLs are advisory, not compulsory. Some people do not take advice.
you moved the DNS server for domain1.com, maybe the old data are still
present as authoritative data in the old DNS server. Or maybe the mail
server which previously handled mail for domain1.com is still configured
with domain1.com as local, so it delivers the mail to domain1.com
locally regardless of DNS instead of forwarding it properly.
Is it possible from my computer to run a program
of some sort to determine where the e-mail is ending up at when sent
through the mail server on domain2.com? In other words, is it possible
to find out somehow (from my own computer) if the old DNS Primary name
is still being used by the domain2.com mail server?
AFAIK, there is no "traceroute" for SMTP routing, if this is what you
have in mind. You must watch into the mail server logs to see what host
a mail was received from and what host it was forwarded to. But you can
use simple tools to query the DNS servers and mail servers used by
people who fail to send mail to the domain.
That of course implies that the mail actually gets through. In his case he
is wondering about mail that does not get through.
By the way, what is the Linux-related part in this topic ?
Linux is by far the best way of trying to track down problems like this.
.
- References:
- Is it possible to trace where an e-mail travels?
- From: Polaris431
- Re: Is it possible to trace where an e-mail travels?
- From: Pascal Hambourg
- Is it possible to trace where an e-mail travels?
- Prev by Date: Re: Debian, Fedora, Redhata Linux?
- Next by Date: Re: sendmail problem
- Previous by thread: Re: Is it possible to trace where an e-mail travels?
- Next by thread: Re: Is it possible to trace where an e-mail travels?
- Index(es):
Relevant Pages
|
Loading
