SMTP protocol is matched case-sensitively

[fatalbanana]

Protocol is matched case-sensitively where-as the receiving MTA probably doesn't care. This can cause metadata not to be collected or false protocol synchronization errors to be generated.

Also: elements like MAIL FROM might/not contain one/more spaces before <.

[linyows]

Oh, Thanks!

[linyows]

Thank you for the valuable information. Do you have plans to use Warp for any specific purpose? If you have any use cases, sharing them would be motivating for development, so I would be happy to hear about them.

[fatalbanana]

Thank you for the valuable information. Do you have plans to use Warp for any specific purpose?

Yes, I have a use-case in mind but it's not yet clear to me that I'll be pursuing it. The idea is to implement support for scanning messages with Rspamd - and inserting fake rejections into the stream if messages would be considered bad (and dropping the connections most likely).

[linyows]

That's a good idea. I wonder if it would be good to have an extension like milter in Warp for that?

[fatalbanana]

That's a good idea. I wonder if it would be good to have an extension like milter in Warp for that?

Milter support could be generally useful but Rspamd's HTTP protocol would be a better target for an Rspamd integration (in that it's relatively flexible vs milter or other integration).