Fallback to Original-recipient if invalid address in Final-recipient field in bounced mail message #1592
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…field in bounced mail message. Also ignore invalid angle-brackets in email address (not part of addr-spec according to RFC 822).
|
We should not fallback to the Original-Recipient as it may be an alias. We don't want to block an entire alias (e.g. mailing list), the Original-Recipient, because mail could not be delivered to one member (the Final-Recipient). |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fallback to Original-recipient if invalid address in Final-recipient field in bounced mail message.
Also ignore invalid angle-brackets in email address (not part of addr-spec according to RFC 822).