At 09:38 PM 5/25/2004 -0400, Ben Treichel wrote:
>Wandering John wrote:
>> I posted over an hour ago. 9:23 PDT for this one.
>The navy coffee one took 24 hrs to hit the list.
There are a few possibilities here, for those interested in
these sort of things.
Lets pretend that the SM listserver was rebooted which might
take a few minutes. This is not an uncommon thing to do for
maintenance, upgrades, etc.
But during that time, you post a message. Your ISP's mail server
cannot contact the mailserver hosting sweetmarias.com and so your
ISP's mail server queues up the message and keeps trying again
according to its configured settings until it is delivered. It is
very conventional to try again once per day for 5 days and then
call it quits as a "undeliverable message". So on the next attempt
the very next day, the mail server is back up so your message goes
through just fine. All along it was sitting on your ISP's mail
server's storage (incoming and outgoing message area called a queue)
This is an explanation of why an email can take 24 hours to show
up. Email systems are designed so nothing ever gets lost, but there
is no guaranty how long it might take! ;-)
Now here is an explanation why an email might be delayed an hour or
two. Lets pretend the SM listserver goes down for whatever reason.
But they have their act together, and have a secondary MX record
(email record for their domain) pointing to a backup mail server.
This backup server will receive mail and queue it until the primary
server comes back online and then it slowly catches back up. This
is very common too and can take hours.
I know this is not an ISP list but I thought some of you might
like a logical explanation of why these sort of events might
happen the way they do. Its a little less frustrating sometimes
when something is better understood, be it a roaster or mail server. :)