Open Bug 720919 Opened 12 years ago Updated 2 years ago

"Timestamp in Date: header of appended mail" is better not requested as "internal date of the mail", because "internal date" usually means "mail arrival date", and because some IMAP servers return NO to APPEND with old "internal date"

Categories

(MailNews Core :: Networking: IMAP, defect)

defect

Tracking

(Not tracked)

People

(Reporter: World, Unassigned)

Details

This is spin-off of bug 693353 comment #19.

Example of "NO to APPEND" due to old date/time string in bug 693353.
> 10 append "INBOX" (\Seen) "13-Jan-2012 12:31:50 -0500"
> 10 NO APPEND attempt to set internal date back more than 86400 seconds

(A) Because it's SHOULD and is not not MUST,
> RFC3501 : If a date-time is specified, the internal date SHOULD be set 
NO response due to old date/time is never RFC violation by server.

(B) "13-Jan-2012 12:31:50 -0500" perhaps comes from Date: header of appended(uploaded) mail.
> Date: Fri, 13 Jan 2012 12:31:50 -0500

Is append request with "internal date of mail's Date:" mandatory?
What's wrong with no data/time parameter? (current date is set as internal date)
If possible, per server option for "internal date request based on Date: header" is better implemented, because existent IMAP server actually returns NO to APPEND request with old "internal date" from Date: header. 

http://tools.ietf.org/html/rfc3501#section-6.3.11
> 6.3.11. APPEND Command
>    Arguments:  mailbox name
>                OPTIONAL flag parenthesized list
>                OPTIONAL date/time string
>                message literal
>(snip) 
>       If a date-time is specified, the internal date SHOULD be set in
>       the resulting message; otherwise, the internal date of the
>       resulting message is set to the current date and time by default.
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.