We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi,
I would like to suggest to support Plus addressing in EFA's MailWatch interface.
It is possible to allow mails to be sent, for example, to:
[email protected] or [email protected] or [email protected]
In postfix this is acheived by adding In main.cf
recipient_delimiter = + This works well, the mails are routed correctly to the final MTA and there is moved in the right folder.
However, if I log in to the MailWatch interface with the user [email protected], it wont be listed.
This is because the to_address stored in the maillog db is [email protected].
Maybe a workaround would be that MailWatch query into the db looks for to_address matching [email protected] AND user+*@domain.tld ?
Just an idea :)
Cheers, Sébastien
Issue already open in v3: E-F-A/v3#413
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Hi,
I would like to suggest to support Plus addressing in EFA's MailWatch interface.
It is possible to allow mails to be sent, for example, to:
[email protected] or [email protected] or [email protected]
In postfix this is acheived by adding In main.cf
recipient_delimiter = +
This works well, the mails are routed correctly to the final MTA and there is moved in the right folder.
However, if I log in to the MailWatch interface with the user [email protected], it wont be listed.
This is because the to_address stored in the maillog db is [email protected].
Maybe a workaround would be that MailWatch query into the db looks for to_address matching [email protected] AND user+*@domain.tld ?
Just an idea :)
Cheers,
Sébastien
Issue already open in v3: E-F-A/v3#413
The text was updated successfully, but these errors were encountered: