Gnus development mailing list
 help / color / mirror / Atom feed
From: "Naim\, Halim." <halimsrama@gmail.com>
To: ding@gnus.org
Subject: Re: Outlook rejecting messages because not RFC 5322 Compliant
Date: Mon, 16 May 2016 08:25:17 -0400	[thread overview]
Message-ID: <8737piw5oy.fsf@gmail.com> (raw)
In-Reply-To: <8760ueyzpg.fsf@tullinup.koldfront.dk> ("Adam \=\?utf-8\?Q\?Sj\?\= \=\?utf-8\?Q\?\=C3\=B8gren\=22's\?\= message of "Mon, 16 May 2016 14:06:19 +0200")

I think this is the relevan section (3.4) of the RFC:

----
|3.4.  Address Specification
|
|   Addresses occur in several message header fields to indicate senders
|   and recipients of messages.  An address may either be an individual
|   mailbox, or a group of mailboxes.
|
|   address         =   mailbox / group
|
|   mailbox         =   name-addr / addr-spec
|
|   name-addr       =   [display-name] angle-addr
|
|   angle-addr      =   [CFWS] "<" addr-spec ">" [CFWS] /
|                       obs-angle-addr
|
|   group           =   display-name ":" [group-list] ";" [CFWS]
|
|   display-name    =   phrase
|
|   mailbox-list    =   (mailbox *("," mailbox)) / obs-mbox-list
|
|   address-list    =   (address *("," address)) / obs-addr-list
|
|   group-list      =   mailbox-list / CFWS / obs-group-list
---

In the same section, there is a note:

----
|     Note: Some legacy implementations used the simple form where the
|      addr-spec appears without the angle brackets, but included the
|      name of the recipient in parentheses as a comment following the
|      addr-spec.  Since the meaning of the information in a comment is
|      unspecified, implementations SHOULD use the full name-addr form of
|      the mailbox, instead of the legacy form, to specify the display
|      name associated with a mailbox.  Also, because some legacy
|      implementations interpret the comment, comments generally SHOULD
|      NOT be used in address fields to avoid confusing such
|      implementations.
----

I believe the header being rejected does not conform to this syntax. I
may be wrong as I have no experience with reading RFCs.
The Note seems to describe this case.




  parent reply	other threads:[~2016-05-16 12:25 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-14 21:41 Naim, Halim.
2016-05-16  8:01 ` Steinar Bang
2016-05-16 10:09 ` Adam Sjøgren
2016-05-16 11:42   ` Naim, Halim.
2016-05-16 12:06     ` Adam Sjøgren
2016-05-16 12:24       ` Sven Joachim
2016-05-16 17:06         ` Adam Sjøgren
2016-05-16 12:25       ` Naim, Halim. [this message]
2016-05-16 13:52         ` Andreas Schwab

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8737piw5oy.fsf@gmail.com \
    --to=halimsrama@gmail.com \
    --cc=ding@gnus.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).