Re: AUTH48 is stuck

Hi Charles,

> The problem is that it is agreed it needs to refer to RFC 5532 rather than
> RFC 2822, but RFC has changed the syntax of Message-ID (considerably
> simplified it) and this has consequential effects on the corresponding
> syntax in RFC 5536.

If I understand well the new syntax in USEFOR, the following message-IDs
are invalid:

<"test"@test>
<te"st@test>
<test@[te\st]>
<test@[te\\st]>

whereas the following message-ID is valid:

<test@[te"st]>


Do you confirm?



Syntax in USEFOR is:

   message-id      =  "Message-ID:" SP *WSP msg-id *WSP CRLF

   msg-id          =  "<" msg-id-core ">"
                      ; maximum length is 250 octets

   msg-id-core     =  id-left "@" id-right

   id-left         =  dot-atom-text

   id-right        =  dot-atom-text / no-fold-literal

   no-fold-literal =  "[" *mdtext "]"

   mdtext          =  %d33-61 /        ; The rest of the US-ASCII
                      %d63-90 /        ; characters not including
                      %d94-126         ; ">", "[", "]", or "\"

with (from RFC 5322):

   dot-atom-text   =   1*atext *("." 1*atext)

   atext           =   ALPHA / DIGIT /    ; Printable US-ASCII
                       "!" / "#" /        ;  characters not including
                       "$" / "%" /        ;  specials.  Used for atoms.
                       "&" / "'" /
                       "*" / "+" /
                       "-" / "/" /
                       "=" / "?" /
                       "^" / "_" /
                       "`" / "{" /
                       "|" / "}" /
                       "~"


Thanks,

-- 
Julien ÉLIE

« Tempora si fuerint nubila, solus eris. » (Ovide)