Hi folks,
I'm observing this thread for a while now and for days I want to publish my observations on this BUT:
Since I didn't have a bbs account before I couldn't post anything -- I had to register before. BUT:
For registering I'm to use a
SG mail address -- which an activation mail is being sent to. BUT:
The activation mail was delayed a few times until the activation link sent was invalid.
BUT:
Now I made it.
Here my two cents:
For me it looks as if
- few mails are being delivered very delayed,
- some got lost at all,
- some are delivered immediately
all of this
not depending on the SG account the eMail was addressed to.
- From about January 18th to about January 23rd (period 1) no eMails to my SG accounts were delivered to my hidden account at GMX at all.
- Since January 23rd some mails sent to that SG accounts during the period 1 are delivered from time to time, maybe 2 or 3 a day.
- Some mails -- for example an answer to a mail I sent as a test to one of my SG accounts -- obviously got lost completely.
- Up to now a lot of mails are delayed for up to 4 days, a few get lost.
So for me theres no completely loss of mails to some SG accounts at a certain SG domain.
But if there would be a problem with TLS, DNS, ..., whatever: shouldn't all mails to a certain SG account get lost?
Why are mails delayed instead? Are there any fallback mechanisms hit due to timeouts which sum up to 4 days?
I made these two tests days before and want to share my observations with you:
- Code: Select all
_#sender_account#_ is the originating (senders) eMail address
_#sg_account#_@dfgh.net is the disposable SG-address the eMail was addressed to
_#hidden_account#_ is the eMail account at GMX that SG should deliver to
The following mail was sent by me from another GMX account to my SG account ... and delivered about 47 hours later:
- Code: Select all
Received: from gourmet8.spamgourmet.com ([216.75.62.102]) by mx-ha.gmx.net (mxgmx116 [212.227.17.5])
with ESMTPS (Nemesis) id ###
for <_#hidden_account#_>; Sun, 29 Jan 2023 13:35:26 +0100
Received: from spamgourmet by gourmet7.spamgourmet.com
with local (Exim 4.94.2)
(envelope-from <_#sender_account#_>) id ###
for _#hidden_account#_; Fri, 27 Jan 2023 13:31:06 +0000
Received: from mout.gmx.net ([212.227.17.20]) by gourmet7.spamgourmet.com
with esmtps (TLS1.3)
tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2)
(envelope-from <_#sender_account#_>) id ###
for _#sg_account#_@dfgh.net; Fri, 27 Jan 2023 13:31:06 +0000
Received: from [##ip##] ([##ip##]) by web-mail.gmx.net (3c-app-gmx-bap10.server.lan [172.19.172.80])
(via HTTP); Fri, 27 Jan 2023 14:31:04 +0100
From: "_#sender_account#_" <...@ob.0sg.net>
To: _#sg_account#_@dfgh.net
Date: Fri, 27 Jan 2023 14:31:04 +0100
The mail retour which I sent about 8pm that day via "answer" never arrived.
As another test I caused booking.com to send me an mail to the same account. This was delivered nearly immediately:
- Code: Select all
Received: from gourmet8.spamgourmet.com ([216.75.62.102]) by mx-ha.gmx.net (mxgmx117 [212.227.17.5])
with ESMTPS (Nemesis)
id ### for <_#hidden_account#_>; Sun, 29 Jan 2023 22:14:19 +0100
Received: from spamgourmet by gourmet7.spamgourmet.com
with local (Exim 4.94.2)
(envelope-from <noreply@mailer.booking.com>)
id ###
for _#hidden_account#_; Sun, 29 Jan 2023 20:44:18 +0000
Received: from mailout-106-r3.booking.com ([37.10.31.9]) by gourmet7.spamgourmet.com
with esmtps (TLS1.3)
tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2)
(envelope-from <noreply@mailer.booking.com>)
id ###
for _#sg_account#_@dfgh.net; Sun, 29 Jan 2023 20:44:18 +0000
From: "customer.service@booking.com" <...@ob.0sg.net>
Sender: "customer.service@booking.com" <...@ob.0sg.net>
To: _#sg_account#_@dfgh.net
Date: Sun, 29 Jan 2023 21:44:14 +0100
I cannot imagine that the "Sender" field makes the difference.
At the beginning of my observations the delay was around 2 days (Jan 27th - Jan 29th).
At the moment its's 4 days (Jan 29th - Feb 2nd).
Could there be a (increasing) load problem somewhere at SG?
Best regards
Hilde