Does this mean that you didn't get my email from a few days ago? (And I shouldn't take it personally that you didn't respond?)

(Reply) (Thread)

Quite possibly.

I also haven't checked my email since...Tuesday, as I haven't been home.

Resend?

(Reply) (Parent) (Thread)

No need. I was seeing if you were around this past weekend. I'll catch you soon...

(Reply) (Parent) (Thread)

The "time to live" you show now in the domain is 41 days:
3600000/60 (seconds)
60000
60000/60 (minutes)
1000
1000/24 (hours)
41

I recommend never publishing an MX at level 0, so you can always insert lower ones later.

(Reply) (Thread)

I concur with both mistergrumpy's attitude and analysis. 41 days is a long ass ttl. But if the old server is shutdown you would probably be fine with introducing a higher MX number and a good mail server should go there next.

(Reply) (Parent) (Thread)

Yeah, I was hoping the shutdown of the old server would sort things out, but it hasn't (apparently).

I think that part of the issue is that the old server is still responding to DNS queries for other domains, just not mine. I'm hoping the admin of that server can redirect queries in some way to my new server.

(Reply) (Parent) (Thread)

On second glance you are probably more correct then I. I was assuming standalone server, but your MX points to your hosting companies mail host which they didn't shutdown. The sending server will only move on if no one answers the door. I guess you could ask your old hosting company to allow relaying for your domain and make sure they have updated DNS (or host file manual entries) that correctly relay your mail to the new place. That said unless they are a very nice bunch of folks they'll probably just say no.

(Reply) (Parent) (Thread)

Well, as the previous hosting company was actually just a friend of mine who hosted a lot of domains for friends, he might.

We'll see...

How did you determine where the old MX was pointing, OOC?

(Reply) (Parent) (Thread)

Oh, I just looked at this:
Status: 5.1.0 (550 5.7.1 <tommy@roadtrip.net>... Relaying denied)
Remote-MTA: dns;mail3.oldhostingmachine.org.

I figured that means it connected to mail3 (probably a mail server) at oldhostingmachine.org which told it relaying denied. Which is short for, this is not me and I'm not willing to be you lacky and resend it to some other random host I don't know about.

I didn't do any real test because everything I looked at pointed to hostmonster which I think is probably your new server but if your old server had a really long ttl and thus people that email you have local dns servers that had cached the old info they'd probably still get it. I don't since no one here has look at your site and thus nothing is cached.

(Reply) (Parent) (Thread)

Your calculations make sense: are they based on the current DNS record, obtained from the current dns host (hostmonster.com), or did you somehow glean that from the above header?

I assume the former, which means I should be contacting my new hosting company and requesting they reduce the TTL, despite the fact that I have a long contract with them.

Thanks!

(Reply) (Parent) (Thread)

They're for the current record, however, I have no reason to assume the old one was not similarly long.

(Reply) (Parent) (Thread)

Hi, my friends! I want to download program X-Rumer 5.07 Palladium free. Have you any link???
I'm so need this magic program! It's can break captchas automatically! Activate accounts via email automatically too! Absolutely great software! Help me!
And did you hear news - price for XRumer 5.0 Palladium will grow up to $540 after 15 may 2009... And XRumer 2.9 and 3.0 - too old versions, it's cant break modern catpchas and cant break modern anti-bot protections. But XRumer 5.0 Palladium CAN!!!!
So help me for download this great program for free! Thanks!

(Reply) (Thread)