249399 - Append a mail message to another IMAP server with $MDNSeen flag set failes

Status: RESOLVED EXPIRED

(Thunderbird :: General, defect)

Description

[Dan Strömberg]

User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; .NET CLR 1.1.4322)
Build Identifier: Thunderbird 0.7

I am using M$ Exchange as my email server, I have installed another IMAP 
server, where i MOVE all mails that I have read.

Error case:
1. somebody send an email message to me with a Return Receipt.
2. I press OK, and send a return receipt for the message I read with 
Thunderbird 0.7
3. Thunderbird sets the $MDNSeen flag on the Exchange server.
4. I try to move the message to a IMAP server that does not support the 
optional $MDNSeen flag
5. Dialog stating APPEND failed.
----
Workaround for me, but should be fixed in Thunderbird aswell:
i telnet to the exhcange server on port 143 and issue a IMAP command for that 
particular message:

idn store 3 -FLAGS ($MDNSeen)
In other words i unset the problematic flag, and restart thunderbird. after 
that I can move the message to the other IMAP server.
  



Reproducible: Always
Steps to Reproduce:
1. In details field
2.
3.

Actual Results:  
In Details field

Expected Results:  
The software should not copy optional flags (in APPEND) if the target IMAP 
server does not support them.

Comment 1

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 2

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.

Comment 3

[spiralvoice]

I am having the same problem with Thunderbird 3.0a1

Comment 4

[spiralvoice]

Because I can not re-open this bug report I filled a new one: bug #373910