193040 - Sent mail not saved

Status: RESOLVED WORKSFORME

(MailNews Core :: Backend, defect)

Description

[Steffen Kaiser]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3b) Gecko/20030210
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3b) Gecko/20030210

Sent mails are not saved in the "Sent Mail" folder. Bug occours since updating
1.3a to 1.3b.

Reproducible: Always

Steps to Reproduce:
1. Compose a message.
2. Sent the message.
3. Check "Sent Mail" - no copy there.

Comment 1

[Matthias Versen [:Matti]]

Imap, pop3/SMTP,Movemail ?

Comment 2

[Alexey Chernyak]

I encountered similar problem on POP3/SMTP mail with multiple POP3 accounts.
However I later found the message in Sent folder under Local Folders.

The problem could be (just guessing):
I replied to an email in one account.
While composing the message I looked at messages in other accounts.
So when I hit Send, a different account was highlighted in the Messenger window.
This might be what made it save in Local Folders, instead of under the account
to which the message was being replied to.

Over to Mail Back End.

Reporter, please check your Local Folders->Sent and comment in here if you find
anything.

Comment 3

[Alexey Chernyak]

Also check the Settings for your accounts under Copies&Folders.

Comment 4

[Andrew Beverley]

I'm also having exactly the same problem. Since upgrading from 1.3a to 1.3b I
cannot find any messages I have sent.

I have searched the whole of my mail subdirectory using TextPad, but the sent
messages cannot be found anywhere.

I have checked the 'copies and Folders' settings, which were correctly setup for
leaving a copy of the sent message in the Sent Items folder. I have tried
changing the setting, enabling and disabling it, trying different folders but
nothing seems to work. The interesting thing is that the setting is not saved -
whatever I change it to it is always back to 'leave copy in Sent folder'.

Comment 5

[Andrew Beverley]

I solved the problem by manually editing prefs.js. Took me a while to work it
out, but in the end I created a new (duff) account, which worked fine saving
sent messages, and then copied the appropriate settings from that one into my
real account, changing the appropriate driectories etc.

Comment 6

[Jason M. Abels]

I can confirm that this does happen under the conditions specified in comment #2

Comment 7

[Andreas Moser]

I still have the same problem in Build ID 2003082204. The problem seems to be
related to the other Mail folders.

Example: You have "Sent" and you have another folder "Sent Items". With this
configuration you are able to send Mails, but they are not copied to the "Sent"
folder and oftenly, not always, the mail client hangs.

Solution: I renamed the "Sent Items" folder, which was inherited from another
mail server, to "Old Sent Mail" and now everything just works fine!

Comment 8

[Patrick]

Is bug 263279 to be duped to this one?

Comment 9

[Mike Cowperthwaite]

Steffen Kaiser never responded to the question in comment 1.  There have been many problems with messages not getting copied to IMAP Sent folders; there may still be a few (bug 298974), but Seamonkey 1.0/TB 1.5 have all the patches I'm aware of for this problem.

Alexey Chernak's comment 2 might be on a trail of something: the Sent folder preference is specific to the identity (From:) used to compose the message.  
I doubt that *looking* at mails in other accounts would cause a problem, but replying to a message sent to a different identity generally uses that same identity for the reply, and the setting might be different between them.  
With current builds, there is now UI to allow the setting of this preference 
for each identity.

Andrew Beverley's comment 4 & 5 might be a different problem; see bug 221386.

The original report of the dupe suggested in comment 8 could also be the issue of a per-identity Sent folder, but this bug's original report is insufficient.
Steffen Kaiser, if you're still getting this bugmail, please update on whether this is still a problem for you, and if so, respond to the question in 
comment 1.

Comment 10

[Mike Cowperthwaite]

No response from reporter  => WFM