Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

support MAIL command with a null #7

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

stadaki
Copy link

@stadaki stadaki commented Mar 25, 2021

MAIL command with a null is required in rfc5321 as shown below.

https://tools.ietf.org/html/rfc5321#section-3.6.3

One way to prevent loops in error reporting is to specify a null reverse-path
in the MAIL command of a notification message.
When such a message is transmitted, the reverse-path MUST be set to null
(see   Section 4.5.5 for additional discussion).
A MAIL command with a null reverse-path appears as follows:

  MAIL FROM:<>

In fact, Postfix bounce emails have MAIL command set to "FROM:<>".
But, MailHog validation judges "FROM:<>" as an error.
Therefore, Postfix bounce email cannot be received by MailHog.

This Pull Request allows you to receive Postfix bounce email by support MAIL command with a null.

MAIL command with a null is required in rfc5321 as shown below.

https://tools.ietf.org/html/rfc5321#section-3.6.3
```
One way to prevent loops in error reporting is to specify a null reverse-path
in the MAIL command of a notification message.
When such a message is transmitted, the reverse-path MUST be set to null
(see   Section 4.5.5 for additional discussion).
A MAIL command with a null reverse-path appears as follows:

  MAIL FROM:<>
```

In fact, Postfix bounce emails have MAIL command set to "FROM:<>".
But, MailHog validation judges "FROM:<>" as an error.
Therefore, Postfix bounce email cannot be received by MailHog.

This Pull Request allows you to receive Postfix bounce email by support MAIL command with a null.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant