Hilfe durchsuchen

Vorsicht vor Support-Betrug: Wir fordern Sie niemals auf, eine Telefonnummer anzurufen, eine SMS an eine Telefonnummer zu senden oder persönliche Daten preiszugeben. Bitte melden Sie verdächtige Aktivitäten über die Funktion „Missbrauch melden“.

Weitere Informationen

Message not delivered but saved in the sent folder.

  • 6 Antworten
  • 1 hat dieses Problem
  • 9 Aufrufe
  • Letzte Antwort von Stans

more options

Hello,

a user sent a message using thunderbird, that message was saved in the sent folder, however, it was not delivered to the recipient.

When analyzing the server logs, no authentication attempts were found on the SMTP server at the time the message was saved in that user's outbox, which ensures that the message was not actually sent.

I would like to know why the message was saved in the sent folder but in fact it was not sent, can this really happen? Is it a bug or other common reason?

Grateful.

Hello, a user sent a message using thunderbird, that message was saved in the sent folder, however, it was not delivered to the recipient. When analyzing the server logs, no authentication attempts were found on the SMTP server at the time the message was saved in that user's outbox, which ensures that the message was not actually sent. I would like to know why the message was saved in the sent folder but in fact it was not sent, can this really happen? Is it a bug or other common reason? Grateful.

Alle Antworten (6)

more options

Who is the provider? There is another fairly recent thread with exactly the same thing happening intermittently. As far as saving a copy of the sent message, Thunderbird is by default configured to do this, unless the user deliberately changes that setting in case the SMTP server automatically saves sent messages in the Sent folder. I know for certain that this isn't a common problem, so it's highly unlikely to be a bug.

more options

My provider is MAV Tecnologia, they provided the server logs and there is no SMTP authentication at the time the message was saved in the sent folder on Thunderbird, that is, it was not sent by the server but thunderbi

more options

My provider is MAV Tecnologia, they provided the server logs and there is no SMTP authentication at the time the message was saved in the sent folder in Thunderbird, that is, it was not sent by the server but thunderbird stored it in the sent ones.

more options

Is your case also intermittent?

more options

Yes, it's intermittent.

The current provider has a control panel where the log of all e-mails that have been sent, whether outgoing or incoming, is shown, this facilitates the analysis. In addition they made the authentication logs available in SMTP, we verify that this user has not authenticated ...

Even without authenticating with SMTP, can Thunderbird save the message in sent items? That is, even without being sure that the message was sent, can he move it to this folder?

more options

rayanmaia said

Yes, it's intermittent. Even without authenticating with SMTP, can Thunderbird save the message in sent items? That is, even without being sure that the message was sent, can he move it to this folder?

Sure it can, but it shouldn't IF the message sending process fails for some reason, because that would be a bug. Since this is the second report of such an occurence that I've come across and it involves different providers, I suggest you file a bug here bugzilla.mozilla.org IF none has been filed yet. Enable logging for SMTP by following the guide here https://wiki.mozilla.org/MailNews:Logging then try to reproduce the issue by sending test messages to another address of yours. When the issue occurs, take note of the time and trim the log file to remove older lines because the log can grow quite fast, then attach the file to the bug report. Hopefully the log will show exactly what's happening between the SMTP server and Thunderbird at that time. Thunderbird's error console could also reveal something, so have a look there as well while reproducing the issue and save a log of the same. While you're at it, you could install Tbird 68, create a separate profile for it and try to reproduce the same. This will confirm whether it's only affecting the current release version of Tbird or not.