You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Which feature or improvement would you like to request?
I hope that the Request in MTA-HOOK can include the original email EML data, so that third parties can call it when they have their own EML parsing API. Currently, when using the rust mail_parser library, eml_message.body_html(0).unwrap() or eml_message.body_text(0).unwrap() cannot be used, because in the MTA-HOOK context, the EML has already been parsed into a string through Content-Transfer-Encoding.
Is your feature request related to a problem?
I'm having a problem with...
Code of Conduct
I agree to follow this project's Code of Conduct
The text was updated successfully, but these errors were encountered:
I suggest that you use Milter instead, the request includes the raw message.
Thank you very much for your suggestion, milter does indeed solve this problem!
At the same time, I also hope that MTA-HOOK, as a new email filtering standard, can support user freedom in configuration to choose whether to parse EML emails into fields for sending or to send the original EML content, which is more flexible.
Which feature or improvement would you like to request?
I hope that the Request in MTA-HOOK can include the original email EML data, so that third parties can call it when they have their own EML parsing API. Currently, when using the rust mail_parser library,
eml_message.body_html(0).unwrap()
oreml_message.body_text(0).unwrap()
cannot be used, because in the MTA-HOOK context, the EML has already been parsed into a string throughContent-Transfer-Encoding
.Is your feature request related to a problem?
I'm having a problem with...
Code of Conduct
The text was updated successfully, but these errors were encountered: