Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Archive, draft, sent being directed to server instead of local

  • 1 reply
  • 1 has this problem
  • 13 views
  • Last reply by gmhyman

more options

I'm using an exchange 2010 server as an imap server. I recently had to delete my account from thunderbird and recreate it. My problem is that even though I specify copies be sent to the "sent" folder on local, archives to "archives" on local, etc. Thunderbird keeps sending them to the right folder, but on my imap (i.e. exchange) server. The previous version of the account did not have this problem, only happened after I deleted and re-created it, which is looking more and more like a bad idea ;)

Any help most appreciated.

I'm using an exchange 2010 server as an imap server. I recently had to delete my account from thunderbird and recreate it. My problem is that even though I specify copies be sent to the "sent" folder on local, archives to "archives" on local, etc. Thunderbird keeps sending them to the right folder, but on my imap (i.e. exchange) server. The previous version of the account did not have this problem, only happened after I deleted and re-created it, which is looking more and more like a bad idea ;) Any help most appreciated.

All Replies (1)

more options

OK, I figured it out. I had created several identities to minimize extra copies on replies - e.g. first.last, last,first, etc. Turns out each identity has a "copies and folders" section of it's own. I changed all of them to what I want and all is OK>

gmhyman said

I'm using an exchange 2010 server as an imap server. I recently had to delete my account from thunderbird and recreate it. My problem is that even though I specify copies be sent to the "sent" folder on local, archives to "archives" on local, etc. Thunderbird keeps sending them to the right folder, but on my imap (i.e. exchange) server. The previous version of the account did not have this problem, only happened after I deleted and re-created it, which is looking more and more like a bad idea ;) Any help most appreciated.