Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

Funkcjonalność tej witryny będzie ograniczona w czasie konserwacji. Jeśli artykuł nie rozwiązuje twojego problemu i chcesz zadać pytanie, to nasza społeczność wsparcia jest dostępna na @FirefoxSupport na Twitterze i /r/firefox na Reddicie.

Przeszukaj pomoc

Unikaj oszustw związanych z pomocą.Nigdy nie będziemy prosić Cię o dzwonienie na numer telefonu, wysyłanie SMS-ów ani o udostępnianie danych osobowych. Zgłoś podejrzaną aktywność, korzystając z opcji „Zgłoś nadużycie”.

Więcej informacji

Problems saving email to the sent folder

  • 1 odpowiedź
  • 1 osoba ma ten problem
  • 5 wyświetleń
  • Ostatnia odpowiedź od Matt

more options

Whenever I send an email ... with any size attachment, but most notably with any attachments larger than 50K or so...which is most all attachments! I get the error box: "unable to save the message to the sent folder..."

I read in an old archived answer that the following info would be needed to see if the imap was communicated properly with Thunderbird to let it save messages in the sent folder. PS: I never had this problem until about a year ago when it started.

Here's that info from my thunderbird program:

 Application Basics
   Name: Thunderbird
   Version: 60.5.3
   Build ID: 20190304124934
   Update Channel: release
   User Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.5.3
   OS: Windows_NT 10.0
   Multiprocess Windows: 0/0 (Disabled)
   Web Content Processes:
   Stylo: content = true (enabled by default), chrome = true (enabled by default)
   Enterprise Policies:
   Google Key: Missing
   Mozilla Location Service Key: Missing
   Safe Mode: false
 Mail and News Accounts
   account1:
     INCOMING: account1, , (imap) imap.secureserver.net:993, SSL, passwordCleartext
     OUTGOING: , smtpout.secureserver.net:465, SSL, passwordCleartext, true
   account2:
     INCOMING: account2, , (none) Local Folders, plain, passwordCleartext
   account3:
     INCOMING: account3, , (imap) imap.aol.com:993, SSL, OAuth2
     OUTGOING: , smtp.aol.com:465, SSL, passwordCleartext, true
 Crash Reports for the Last 3 Days
 All Crash Reports
 Extensions
     Name
     Version
     Enabled
     ID
     Manually sort folders
     1.2.1
     false
     tbsortfolders@xulforum.org
Whenever I send an email ... with any size attachment, but most notably with any attachments larger than 50K or so...which is most all attachments! I get the error box: "unable to save the message to the sent folder..." I read in an old archived answer that the following info would be needed to see if the imap was communicated properly with Thunderbird to let it save messages in the sent folder. PS: I never had this problem until about a year ago when it started. Here's that info from my thunderbird program: Application Basics Name: Thunderbird Version: 60.5.3 Build ID: 20190304124934 Update Channel: release User Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.5.3 OS: Windows_NT 10.0 Multiprocess Windows: 0/0 (Disabled) Web Content Processes: Stylo: content = true (enabled by default), chrome = true (enabled by default) Enterprise Policies: Google Key: Missing Mozilla Location Service Key: Missing Safe Mode: false Mail and News Accounts account1: INCOMING: account1, , (imap) imap.secureserver.net:993, SSL, passwordCleartext OUTGOING: , smtpout.secureserver.net:465, SSL, passwordCleartext, true account2: INCOMING: account2, , (none) Local Folders, plain, passwordCleartext account3: INCOMING: account3, , (imap) imap.aol.com:993, SSL, OAuth2 OUTGOING: , smtp.aol.com:465, SSL, passwordCleartext, true Crash Reports for the Last 3 Days All Crash Reports Extensions Name Version Enabled ID Manually sort folders 1.2.1 false tbsortfolders@xulforum.org

Wszystkie odpowiedzi (1)

more options

With which account or both? If both, what anti virus are you using? It is quite probably the cause (you cropped the troubleshooting information before you got to it.)