3 ms·
My business sends a lot of emails. Yesterday morning we were scheduled to send an email to ~8,000 of our subscribers. I sent an test email to a test list, and i
by JacobJans 13y ago
My business sends a lot of emails. Yesterday morning we were scheduled to send an email to ~8,000 of our subscribers. I sent an test email to a test list, and it did not go through. This test email went to 4 different Gmail address. None of them received it. Around 40 minutes later, one of the Gmail accounts finally received the message. At this point I sent another email to the test list. Still nothing. I tried emailing from a Yahoo account, to Gmail, and it went through. However, for over 3 hours I couldn't send an email from my server to Gmail. Emails from other servers were able to go through.
The problem does not appear to be with individual user accounts, but from Google's ability to receive emails from certain parts of the internet universe.
The result was lost time and lost money on my end. I imagine this had very little impact on the experience of individual users -- but for businesses that depend on getting emails to their customers, this had a much bigger impact.
My experience was this:
1. This problem was not a 2.6 second delay. It was a multi-hour delay.
2. The problem was not with 1.5% of Gmail users, but with Google's ability to receive messages from other parts of the internet. (A major pipe was down, according to the OP.)
3. No Gmail user had all their incoming mail delayed for a couple hours -- Certain senders to Gmail had all of their mail delayed for several hours.
- mhurron 13y ago> This problem was not a 2.6 second delay. It was a multi-hour delay. Technically this is not a problem. SMTP does not guarantee instantaneous delivery, just that if a SMTP server accepts the message it will be delivered. In reality, this 'delay' could be perfectly normal and is just fine according to spec.