Feat/peer metadata + Envelope.AddHeader #18
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.
New features:
map[string]interface{}) and functions to manipulate itBreaking changes:
in checker functions
Peeris now link to struct, not struct like it was beforeWhy do i need peer metadata?
i can process message differently, for example, if
RCPT TOpoints to existing record in LDAP database, i deliver message to dovecot via lmtp, if address forRCPT TPis in some list, i can either send message to quarantine, report to rspamd as spam or even parse message and create new task in redmine via api call.we had similar complicated email server on Haraka before, but since it is nodejs and i encountered few bugs with it (like constant memleaks and some issues with prototype pollutions), i decided to find some minimalistic and easy to hack email server in golang, and your's one was probably the best.