Franck Martin was running this down most recently, based on some chatter on the
mailman-dev list.
I'll offer up Franck's thinking (of which I agree!):
- Register 5.7.17 with IANA
-
http://www.iana.org/assignments/smtp-enhanced-status-codes/smtp-enhanced-status-codes.xml
- ..to indicate a DMARC policy rejection.
Unclear if such an entry would cover SPF, ADSP, etc, too.
Reasonable?
=- Tim
On Aug 9, 2013, at 2:35 PM, Ryan Boyd <[email protected]> wrote:
> Saw this as well last night.
> On Fri, Aug 9, 2013 at 11:28 AM, Jeff Macdonald
> <[email protected]> wrote:
> Hi all,
>
> I don't think I've seen any chatter about this on the list. If I missed it, I
> apologize.
> In the wild today, from AOL, there is this:
>
> 521 5.2.1 : (DMARC) This message failed DMARC Evaluation and is being
> refused due to provided DMARC Policy
>
> This has a SMTP status code that is meant for an initial connection. See
> http://tools.ietf.org/html/rfc1846.
> The extended SMTP code is meant for disabled mailboxes, which I suppose one
> could stretch to fit dmarc, but that seems wrong too.
>
> This doesn’t seem right to me for using with DMARC. AOL uses 521 for other
> anti-spam purposes as well. Has there been discussion about appropriate SMTP
> responses?
_______________________________________________
dmarc-discuss mailing list
[email protected]
http://www.dmarc.org/mailman/listinfo/dmarc-discuss
NOTE: Participating in this list means you agree to the DMARC Note Well terms
(http://www.dmarc.org/note_well.html)
