SMTP 550-5.7.1 Rejected Because of Virginia Redistricting

khanna.law

69 points·hkhanna··6 comments

Article doesn't make it clear, but I assume that SMTP 550-5.7.1 was an extant error code and the VA redistricting was simply the message body that the server returned alongside the error code? Otherwise the article might lead one to believe that error 550-5.7.1 was explicitly created for the purpose of VA redistricting (a la HTTP status code 418: "I'm a teapot").

Correct. 5.7.1 is supposed to be for malformed/inappropriate sending to the address, so I think they shouldn’t have used it here as the VA resident did nothing wrong. 5.2.1 might be a better error since it means a problem with the recipient/that the recipient is refusing email.

"550 Requested action not taken: mailbox unavailable (e.g., mailbox not found, no access, or command rejected for policy reasons)"

https://en.wikipedia.org/wiki/List_of_SMTP_server_return_cod...

I imagine the "-5.7.1" is an in-house reference by the Virginia IT folks.

5.7.1 is the response code Exchange uses any time a policy blocks a message. If they are using Exchange then they set it up with a mail flow rule action of 'block the message / reject the message and include an explanation'.

Am I the only one who thinks this is really thoughtful. Even the error message is good. Brilliant

Those are managed by IANA: https://www.iana.org/assignments/smtp-enhanced-status-codes/... and X.7.1 reads out:

"Delivery not authorized, message refused" and "The sender is not authorized to send to the destination. This can be the result of per-host or per-recipient filtering. This memo does not discuss the merits of any such filtering, but provides a mechanism to report such. This is useful only as a permanent error."

Reply on news.ycombinator.com