Re: [courier-users] Best practice for SMTP level spam filter

2016-04-12 Thread Sam Varshavchik
Gordon Messmer writes: On 04/11/2016 03:56 PM, Sam Varshavchik wrote: > maildrop's embedded mode runs for RCPT TO, and DATA commands. > Additionally, when using the embedded in the default configuration, > Courier will defer, using 4xx, recipients that do not have the > embedded mode filter

Re: [courier-users] Best practice for SMTP level spam filter

2016-04-12 Thread Sam Varshavchik
Gordon Messmer writes: On 04/09/2016 09:19 PM, Bernd Wurst wrote: > We use delivery by .courier files for both, local user accounts / > aliases and virtualdomains. Spam filtering happens with some custom > scripts inside the .courier files and therefore only deletion, sorting > or bouncing is

Re: [courier-users] Best practice for SMTP level spam filter

2016-04-12 Thread Gordon Messmer
On 04/11/2016 03:56 PM, Sam Varshavchik wrote: > maildrop's embedded mode runs for RCPT TO, and DATA commands. > Additionally, when using the embedded in the default configuration, > Courier will defer, using 4xx, recipients that do not have the > embedded mode filter activated. Thanks for

Re: [courier-users] Best practice for SMTP level spam filter

2016-04-12 Thread Alessandro Vesely
On Mon 11/Apr/2016 18:44:41 +0200 Gordon Messmer wrote: > > It's possible to scan the message during SMTP. It's possible to deliver > or drop on a per-recipient basis, as well. You simply mark the message > delivered for those recipients who wouldn't want to receive it. > However, there's