Mozilla created a 'sent' folder instead of using existing 'Sent Items'



MailNews Core
Networking: IMAP
16 years ago
9 years ago


(Reporter: Colin, Assigned: Scott MacGregor)


Windows 95

Firefox Tracking Flags

(Not tracked)




16 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Win95; en-US; rv:1.2a) Gecko/20020910
Build Identifier: Mozilla/5.0 (Windows; U; Win95; en-US; rv:1.2a) Gecko/20020910

Using Samsung Contact Imap server. Account used with SC client, Outlook
97/OM_MAPI & Outlook Express(SMTP/IMAP). The others *all* used the 'Sent Items'
folder. Mozilla seems to be insisting that, if I keep a copy of things I send,
then they must go in a folder called 'Sent'. Indeed, when I sent a message, it
created a new folder called 'sent' to put a copy in!

Reproducible: Always

Steps to Reproduce:
1. Send a mail from an IMAP account
2. does the same if I install a new account on the system and send a mail from that

Expected Results:  
I rather expected Mozilla to use the folder called 'Sent Items' by default. That
it does not wouldn't be a problem if it allowed me to change the folder to which
sent items are copied to.

Comment 1

16 years ago
Mozilla 1.2b & NT 4.0 Similar but slightly different problem. Mozilla created a
“Sent Items” folder, apparently when it was installed.

I already had a “Sent” folder on my corporate mail server under Netscape
Messenger 4.73. 

Under Mozilla, sent mail gets put in the “Sent” folder. When I tried to remove
the “Sent Items” folder manually, by deleting the “Sent Items.snm” & “Sent
Items.msf” files, the folder gets recreated the next time Mozilla’s mail client
is started.

So I have a "Sent" folder that is used & a "Sent Items" folder which is not used.

Comment 2

16 years ago
So I'm really dumb. When I went back and checked, it does allow you to choose
where to put deleted and sent items.
Last Resolved: 16 years ago
Resolution: --- → INVALID

Comment 3

16 years ago


15 years ago
QA Contact: huang → gchan
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.