Closed Bug 1558193 Opened 6 years ago Closed 6 years ago

Delivery status notification has stopped working

Categories

(Thunderbird :: Message Compose Window, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: arno.versfeld, Unassigned)

References

Details

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:67.0) Gecko/20100101 Firefox/67.0

Steps to reproduce:

When I compose an email I mostly request "Delivery status notification", particularly for important emails where I need proof that the emails have been delivered to the mail boxes.
I always received the requested delivery status notifications until they stopped during February 2019.
I have not been getting delivery status notifications from any of the companies to whom I have sent emails and from whom I requested delivery status notifications.

Actual results:

I contacted one company to find out if they stopped acknowledging receipt of emails. They said their system, Exchange Server of Microsoft, is set to acknowledge receipt of email and actually tested their system to confirm their statement.
I sent a test email, requesting a delivery status notification but received none.
I later received an email from the receiver in response to my email proving that it was delivered.

Expected results:

I should have received emails acknowledging receipt of the emails I sent since some time in February 2019 to date.
I GET THE IMPRESSION THAT THUNDERBIRD DOES NOT REQUEST THE DELIVERY STATUS NOTIFICATION ALTHOUGH I SET IT IN THE WRITE WINDOW, OPTIONS, DELIVERY NOTIFICATION.
Thunderbird version: 60.7.0
OS version: Ubuntu 18.04

The OS is a 64 bit version

We get bugs like this from time to time since there seems to be some confusion.

I've just sent an e-mail via an outgoing server that is known to produce those DSNs. And I get them:

The original message was received at Wed, 12 Jun 2019 10:32:30 +0000
from 102.39.16.95.dynamic.jazztel.es [95.16.39.102]

   ----- The following addresses had successful delivery notifications -----
<jorgk@jorgk.com>  (relayed to non-DSN-aware mailer)

   ----- Transcript of session follows -----
<jorgk@jorgk.com>... relayed; expect no further notifications

So if you don't get DSN, it's not a TB problem, it's a problem of the various MTAs that handle the mail.

Sorry, DSN is not reliable. It's better to ask for a "read receipt".

Status: UNCONFIRMED → RESOLVED
Closed: 6 years ago
Resolution: --- → INVALID
See Also: → 749413
You need to log in before you can comment on or make changes to this bug.