Closed
Bug 137130
Opened 23 years ago
Closed 23 years ago
Copies of sent messages appear unread
Categories
(MailNews Core :: Networking: IMAP, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: dbooth, Assigned: mscott)
Details
Using the "other" option for "when sending messages automatically place a copy
in.." to select a specific folder on an IMAP server (corporate "standard" is MS
exchange server *gag* *puke* so the sent folder has to be called "Sent Items" if
I'm to be able to use both outlook and moz to work with my email) the copies are
now appearing as unread. Not a big deal but a step backwards from how it used to
be. May perhaps be a server quirk but accessing the same mail server with other
IMAP clients doesnt do this and nor did moz release 0.9.8. Perhaps explicitly
mark saved copies of sent emails as read after saving them?
To reproduce:
set up a mail account pointing to an IMAP server and configure copies of sent
emails to go to some IMAP folder other than "sent"
Send an email from that account.
Expected behaviour: a copy should be filed in the specified folder but not
marked as new.(this is how 0.9.8 release behaved)
Actual behaviour: copy is correctly filed but its marked as new.
Reproducible 100% with a Microsoft IMAP server, not managed to test with any
others yet.
| Reporter | ||
Comment 1•23 years ago
|
||
D'oh - forgot I'd filed this one and found it when I was looking for dupes
before filing it again. Still there in build 2002051522. Since it USED to work
as expected should this one have the regression keyword set?
Comment 2•23 years ago
|
||
does it still happen with a recent build such as 1.1beta?
| Reporter | ||
Comment 3•23 years ago
|
||
Appears to have gone away in 2002080422 or earlier.. cant say exactly when, I've
been out of the office and not updating my build as often as I'd like.....
Marking fixed.
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Updated•21 years ago
|
Product: MailNews → Core
Updated•17 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•