email not marked as replied

UNCONFIRMED
Unassigned

Status

Thunderbird
Folder and Message Lists
UNCONFIRMED
5 years ago
5 years ago

People

(Reporter: sumanbhttchrj, Unassigned)

Tracking

24 Branch
x86
Windows 7

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

5 years ago
User Agent: Mozilla/5.0 (Windows NT 6.1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/31.0.1650.63 Safari/537.36

Steps to reproduce:

1. Open an email
2. click on reply
3. write my reply
4. click on send
5. look for the replied symbol/mark on the email
6. replied symbol/mark is missing


Actual results:

after replying to am email, that email is not marked with a replied symbol


Expected results:

a replied symbol should appear on an email after i reply to it.

Comment 1

5 years ago
Which email account type is this about? IMAP? POP?
Flags: needinfo?(sumanbhttchrj)
(Reporter)

Comment 2

5 years ago
(In reply to Andre Klapper from comment #1)
> Which email account type is this about? IMAP? POP?

This is IMAP email account
Flags: needinfo?(sumanbhttchrj)
(In reply to sumanbhttchrj from comment #2)
> This is IMAP email account

Same problem as bug 530528, which you could easily found if you searched closed bugs also, which will be fixed in Tb 26?
(Reporter)

Comment 4

5 years ago
(In reply to WADA from comment #3)
> (In reply to sumanbhttchrj from comment #2)
> > This is IMAP email account
> 
> Same problem as bug 530528, which you could easily found if you searched
> closed bugs also, which will be fixed in Tb 26?

That bug is occurs when you save the reply as draft and then send.
I did not save my email as draft. It is immediate reply, type and send.
Still the reply symbol is missing.
Today I noticed the symbol comes for a while, until you click on get email.
Hope this information helps.
Even if you don't do "Save as draft" explicitly, if you request Tb to do auto-save, and if you request Tb not to show "confirmation dialog after save as draft", Tb silently does do "auto-save" periodically according to your request.
And, IIRC, default of auto-save is "auto-save=Enabled, each 5 minutes", and default of "confirmation dialog after save as draft" is Off(disabld, unchecked).

> It is immediate reply, type and send.
What is time between the "immediate reply" and "send"?

Even when IMAP account is used and Mbox where replied mail is held is IMAP Mbox, "draft folder" can be located anywhere by your Copies&Folders setting. And, "Send" can be "not immeadiate Send", according to your option setting. "Send Later, send to server as background job" like action may be done by Tb. If so, same thing as "Send Later" can occur. See duped bugs to that bug, please.

IIRC, "Replied status" is saved as flag/keyword if replied mail is held in IMAP Mbox(usually Inbox of the IMAP accunt). And the flag/keyword for the "Replied status" is fetched from server.
Get IMAP log and check IMAP level flow around your "reply, send" using Text Editor.
See bug 402793 comment #28 for getting log.
See http://tools.ietf.org/html/rfc3501 for IMAP command and response.
Following is perhaps usefull, because "Inbox access/flag store and fetch/draft save at IMAP Mbox" is involved.
> SET NSPR_LOG_MODULES=timestamp,imap:5,ImapAutoSync:5,IMAPOFFLINE:5,MsgCopyService:5
> MsgCopyService:5 is for log of "copy to Draft or save to Outbox etc. during composition".
Flags is stored/removed and fetched by;
  uid store nn +Flags(FlagName ...)
  uid store nn -Flags(FlagName ...)
  uid fetch nn  Flags(), uid fetch aa:bb,...,yy:zz Flags()
  uid fetch nn  Flags(FlagName ...), uid fetch aa:bb,...,yy:zz Flags(FlagName ...)

Tb has problem of Bug 840418(local mail folder).
"X-Mozilla-Status: header is not wriiten in local mail folder case" may correspond to "flag for Replied status is not stored in IMAP folder".
(Reporter)

Comment 6

5 years ago
(In reply to WADA from comment #5)
> Even if you don't do "Save as draft" explicitly, if you request Tb to do
> auto-save, and if you request Tb not to show "confirmation dialog after save
> as draft", Tb silently does do "auto-save" periodically according to your
> request.
> And, IIRC, default of auto-save is "auto-save=Enabled, each 5 minutes", and
> default of "confirmation dialog after save as draft" is Off(disabld,
> unchecked).
> 
> > It is immediate reply, type and send.
> What is time between the "immediate reply" and "send"?
> 
> Even when IMAP account is used and Mbox where replied mail is held is IMAP
> Mbox, "draft folder" can be located anywhere by your Copies&Folders setting.
> And, "Send" can be "not immeadiate Send", according to your option setting.
> "Send Later, send to server as background job" like action may be done by
> Tb. If so, same thing as "Send Later" can occur. See duped bugs to that bug,
> please.
> 
> IIRC, "Replied status" is saved as flag/keyword if replied mail is held in
> IMAP Mbox(usually Inbox of the IMAP accunt). And the flag/keyword for the
> "Replied status" is fetched from server.
> Get IMAP log and check IMAP level flow around your "reply, send" using Text
> Editor.
> See bug 402793 comment #28 for getting log.
> See http://tools.ietf.org/html/rfc3501 for IMAP command and response.
> Following is perhaps usefull, because "Inbox access/flag store and
> fetch/draft save at IMAP Mbox" is involved.
> > SET NSPR_LOG_MODULES=timestamp,imap:5,ImapAutoSync:5,IMAPOFFLINE:5,MsgCopyService:5
> > MsgCopyService:5 is for log of "copy to Draft or save to Outbox etc. during composition".
> Flags is stored/removed and fetched by;
>   uid store nn +Flags(FlagName ...)
>   uid store nn -Flags(FlagName ...)
>   uid fetch nn  Flags(), uid fetch aa:bb,...,yy:zz Flags()
>   uid fetch nn  Flags(FlagName ...), uid fetch aa:bb,...,yy:zz
> Flags(FlagName ...)
> 
> Tb has problem of Bug 840418(local mail folder).
> "X-Mozilla-Status: header is not wriiten in local mail folder case" may
> correspond to "flag for Replied status is not stored in IMAP folder".

Thanks WADA for this information. I will look forward to see this working in future release.
(In reply to sumanbhttchrj from comment #6)
> I will look forward to see this working in future release.
Please check with current Tb release, which you currently use, on which you consistently see your problem, instead of only in "future release(s)".
You need to log in before you can comment on or make changes to this bug.