Closed Bug 1041204 Opened 11 years ago Closed 11 years ago

After smtp password was requested, mail is sent but not copied to sent folder (IMAP)

Categories

(Thunderbird :: Untriaged, defect)

31 Branch
x86_64
Windows 7
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: kbolkomertz, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:30.0) Gecko/20100101 Firefox/30.0 (Beta/Release) Build ID: 20140605174243 Steps to reproduce: An IMAP Account has no password stored in PW Manager, and is configured to copy automatically sent mails to the "sent" folder. I composed a first mail during TB session from this account and pressed the "send" bottom. As expected, a pop-up window appears saying "connected to < smtp server >". This window is overlaid by another one titled " SMTP server password required " asking "enter your password for <userid> at <smtp server>". I entered the correct password and left unchecked the option " Use password manager to store this password", then clicked on "OK". (Please note that I'm using the German version of TB 24.6.0, and the titles and messages of the English version may be diffferent from my translation.) Actual results: The pop-up window disappeared, no report about the progress of sending, no report of "copying to sent folder" (as is shown when the smtp server password is known, either by password manager or after it had been entered during the first mail processing), and indeed it was not copied, but the mail had been sent correctly. Expected results: The progress of sending an copying to "sent" folder should be shown, and the mail should have been copied to the "sent" folder.
With Version 31 I found the same behaviour
Version: 24 → 31
Sorry, with Version 31 the sent file was stored, but i was confused by the fact that in case of an account with an alias TB uses different folders for the alias than for the original account. I'll search for that and perhaps will open another bug reprot.
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.