Closed Bug 1428935 Opened 7 years ago Closed 7 years ago

if using templates by multiple clients accessing the same server, mail does not show up in the expected Sent folder (but some other Sent folder)

Categories

(Thunderbird :: Untriaged, defect)

52 Branch
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 394216

People

(Reporter: x471, Unassigned)

Details

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0 Build ID: 20171208114127 Steps to reproduce: I have 2 PC Win 7 prof with thunderbird 52.5.2 both using one same account (A) and some other accounts (B C D E) all accounts are on my dovecot server. PC 1 uses accounts A B C PC 2 uses accounts A D E I create a template on PC 1 and can use it as expected. Mail is sent and saved in the sent folder (account A). Actual results: If i use this template on PC 2 the mail is sent but does not show up in sent folder (account A) instead it is saved in the sent folder of another account (D) I can not find anything wrong in the template. Nothing is indicating it was originally written on PC 1. PC 1 and 2 are using the same configuration, explicitly: [x] Save a Copy (x) Folder Sent in: account A may be related: https://www.thunderbird-mail.de/forum/thread/78857-vorlagen-nicht-im-gesendet-ordner/?postID=427909&highlight=vorlagen%2Bgesendet#post427909 Expected results: The template sent from PC 2 should be stored in sent folder of account A.
That's the old identity confusion when accessing the same IMAP server with various clients, bug 394216. We've fixed that, you can see it working in TB 58 beta. As a workaround for TB 52: When you use a template, set the From explicitly before sending, then it should go to that account's sent folder.
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
Summary: if using templates mail does not show up in sent folder → if using templates by multiple clients accessing the same server, mail does not show up in the expected Sent folder (but some other Sent folder)
You need to log in before you can comment on or make changes to this bug.