fileinto sieve vs mailDeliveryOption: forward
Here's the architecture in question:
- Initial SMTP connections from all senders is handled by a non CommsSuite MTA (MTA1). This MTA also performs antispam checking.
- MTA1 then delivers to CommSuite MTA for either delivery via LMTP to a CommSuite Message Store or outbound to remote mail systems
- Today MTA1 will drop/silent discard all spam positive messages so CommSuite never sees this volume
I am going to be altering this configuration such that MTA1 will tag "spam positive" messages with a unique header:value and the CommSuite MTA will have a tcp_lmtpcs channel level sieve filter to file messages with this header into spam folders.
- Initial SMTP connections from all senders is handled by a non CommsSuite MTA (MTA1). This MTA also performs antispam checking.
- MTA1 then delivers to CommSuite MTA for either delivery via LMTP to a CommSuite Message Store or outbound to remote mail systems
- Today MTA1 will drop/silent discard all spam positive messages so CommSuite never sees this volume
I am going to be altering this configuration such that MTA1 will tag "spam positive" messages with a unique header:value and the CommSuite MTA will have a tcp_lmtpcs channel level sieve filter to file messages with this header into spam folders.
0