-
Notifications
You must be signed in to change notification settings - Fork 274
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
Add modifiers to rewrite headers #158
Comments
A useful feature implemented in postfix “header_checks REPLACE” allows you to change some fields in the header. |
One obscure feature of RFC 5322 is that it permits multiple addresses in the From field. In that case, simple regexp-based replacement may change only one address from the list unless applied repeately. I am not sure whether it is worth supporting (I don't think it is widely supported in clients). So perhaps as an alternative it might be possible to introduce a set of modifiers for headers manipulation.
|
I am sure that modifiers are the best option. replace_header FROM [email protected] [email protected] |
Blocked by emersion/go-message#75. |
Is this still blocked? If not, I'd be willing to try (partially) implementing this, if it's still desired and would be merged |
go-message still has a fairly restrictive interface for header manipulation. See discussion of the referenced PR. |
What's the status of implementing this @ptrcnull ? |
See #158 (comment).
--
Original post:
This should not be used for relays (RFC 5321 prohibits modification of existing header fields) but is usually fine for submission servers. In case of submission, this is what people probably want when saying "replace sender" *.
Need to think whether it may be useful for replace_rcpt too.
* replacing only MAIL FROM command argument (as currently done by replace_sender) can invalidate DMARC alignment, btw.
The text was updated successfully, but these errors were encountered: