Avatar for Username

Sök i support

Akta dig för supportbedrägerier: Vi kommer aldrig att be dig att ringa eller skicka ett sms till ett telefonnummer eller dela personlig information. Rapportera misstänkt aktivitet med alternativet "Rapportera missbruk".

Läs mer

Denna tråd har arkiverats. Ställ en ny fråga om du behöver hjälp.

TB sent email OK but cannot save in remote sent directory on ISP server

  • 1 svar
  • 1 har detta problem
  • 12 visningar
  • Senaste svar av Kinetix

Kinetix
Kinetix
more options

This happens intermittently on Thunderbird 68 in both 32 bit & 64 bit PCs. Happens for both email with and without attachment. The error message is: "Your message was sent but a copy was not placed in your sent folder (Sent Mail) due to network or file access errors. You can retry or save the message locally to Local Folders/Sent Mail-xxxxxxx@aussiebroadband.com.au"

This happened when I upgraded to TB 68 so I have gone back to TB 60 and the problem has not reoccurred so far. I had a similar problem before that was caused by the antivirus software email scanning. Since that time, I have the antivirus email scanning switched off for both sending and receiving. So this problem is not caused by the antivirus software.

This happens intermittently on Thunderbird 68 in both 32 bit & 64 bit PCs. Happens for both email with and without attachment. The error message is: "Your message was sent but a copy was not placed in your sent folder (Sent Mail) due to network or file access errors. You can retry or save the message locally to Local Folders/Sent Mail-xxxxxxx@aussiebroadband.com.au" This happened when I upgraded to TB 68 so I have gone back to TB 60 and the problem has not reoccurred so far. I had a similar problem before that was caused by the antivirus software email scanning. Since that time, I have the antivirus email scanning switched off for both sending and receiving. So this problem is not caused by the antivirus software.

Alla svar (1)

Kinetix
Kinetix Frågans ägare
more options

Update to the problem, just encountered the same problem on Thunderbird 60 as well. So not unique to version 68.