Actually, I was sending email to wfolta@netmail.to@mail2.futurequest.net, which essentially forces the email to go through your host even though the domain info has not fully propagated yet. I guess your MTA handles double
's differently than my past experience.
It looks like the DNS propagation is going well, and I'll drop my old web hoster in a day or two. (Remind me to tell you the story about how they -- on three separate occasions -- bounced all my email for 12+ hours. And how the last straw was when I had intermittent email bounces and it took them 48 hours to call back to let me know what was going on.)
Back on the Futurequest homefront: I tried to get my email tonight and am getting an error from the POP server:
Server not responding. 706; Lost connection to server. {37:1136}
Which is why a small operation can be good, but it can also make me nervous when things are confusing or messed up at night.
(The flip side of the coin is that I've only ever experienced one company that had knowledgeable tech support people there at night. Basically, they were day people that got paged.)
Linear Mode
