bug-mailutils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug-mailutils] Re: Bugs in movemail with IMAP folders


From: Thomas Guyot-Sionnest
Subject: [bug-mailutils] Re: Bugs in movemail with IMAP folders
Date: Tue, 10 Feb 2009 06:57:28 -0500
User-agent: Thunderbird 2.0.0.19 (X11/20090105)

On 10/02/09 05:21 AM, Sergey Poznyakoff wrote:
> Hi Thomas,
> 
> I revised the patch. It looks mostly OK to me, except several parts
> where INBOX can be one of arguments, e.g.:
> 
> -     status = imap_writeline (f_imap, "g%s APPEND %s %s {%s}\r\n",
> +     status = imap_writeline (f_imap, "g%s APPEND \"%s\" %s {%s}\r\n",
> 
> According to RFC 3501:
> 
> mailbox         = "INBOX" / astring
>                     ; INBOX is case-insensitive.  All case variants of
>                     ; INBOX (e.g., "iNbOx") MUST be interpreted as INBOX
>                     ; not as an astring.  An astring which consists of
>                     ; the case-insensitive sequence "I" "N" "B" "O" "X"
>                     ; is considered to be INBOX and not an astring.
>                     ;  Refer to section 5.1 for further
>                     ; semantic details of mailbox names.
> 
> Unless I'm misinterpreting it, this rule indicates that the special name
> INBOX must not be quoted.

; [...].  An astring which consists of
; the case-insensitive sequence "I" "N" "B" "O" "X"
; is considered to be INBOX and not an astring.

No, and that's how it worked with mailutils-1.2. I read the other parts
of the RFC and put all details in me 2nd email (Jan 13). The quoted form
is defined as an "astring" and the RFC specifically says that a
case-insensitive "INBOX" astring is to be considered INBOX, not an astring.

If you feel better handling these differently I could do it, however
this patch does fix a real problem and does not break the RFC.

Regards,

--
Thomas





reply via email to

[Prev in Thread] Current Thread [Next in Thread]