Franck Martin wrote:
> Even in this case Lastname is not a valid mailbox as it does not have a valid
> email address,
That is my interpretation also. The ability of many MTAs to work with implicit
domains internally is outside 5322's scope.
- Roland
On Wed, Apr 6, 2016 at 9:41 AM, A.
Even in this case Lastname is not a valid mailbox as it does not have a
valid email address, even when you take into account the EAI update it
should have been written as Lastname;
Strictly speaking the ABNI allows display name with no double quotes as
long you don't use any special characters
Of cause
From: Lastname, Firstname
is a result of omitted backslash or double quotes. The fact is,
according to RFC 5322 it's valid RFC5322.From field with 2 mailboxes in
it and is not covered by RFC 7489. OpenDMARC implementation follows to
known best practices noticed in RFC
Vladimir,
We are not discussing here the fact you can put 2 mailboxes in a From: but
that the display part must be between double quotes.
A mailbox is an optional display part within double quotes followed by an
email address within <>. Mailboxes are separated by comas ,.
On Wed, Apr 6, 2016 at
It happens a lot..
The obsoleted format allowed it, not the recent one. I think we should
ignore the obsolete format now...
The problem is:
From: j...@example.com
Which certain quite old versions of .net do.
On Wed, Apr 6, 2016 at 3:26 AM, A. Schulze via dmarc-discuss <
This From contains 2 mailboxes (Lastname and u...@yahoo.com). This is
valid RFC 5322 syntax
from= "From:" mailbox-list CRLF
...
mailbox-list= (mailbox *("," mailbox)) / obs-mbox-list
but it's invalid for DMARC RFC 7489 and it's not covered by DMARC
specification:
Hello,
I noticed a message with this RFC5322.From:
From: Lastname, Firstname
the message was authenticated by SPF and DKIM but opendmarc rejected finally.
Is this From really valid? I would quote the displayname.
If it's valid, I hit a bug in OpenDMARC.
If it's invalid,