Gordon Messmer writes:
On 04/11/2016 12:22 PM, Jeff Potter wrote:
> Gordon, could one potentially change the replies after the first RCPT TO
to 4xx responses, to ensure the incoming message is being delivered to
exactly one user?
Not exactly. Courier's mail filtering API only issues one
Idézem/Quoting Gordon Messmer :
> On 04/09/2016 09:25 AM, SZÉPE Viktor wrote:
>> Looking at Gordon's greylist.py that would be the "remember" part, and
>> combining it with DNSBL lookup from whitelist_dnswl.py ...
>> but:( I am not a python developer.
>
> Sounds like
On 04/09/2016 09:25 AM, SZÉPE Viktor wrote:
> Looking at Gordon's greylist.py that would be the "remember" part, and
> combining it with DNSBL lookup from whitelist_dnswl.py ...
> but:( I am not a python developer.
Sounds like another use case for making individual filters conditional.
It's on
On 04/11/2016 12:22 PM, Jeff Potter wrote:
> Gordon, could one potentially change the replies after the first RCPT TO to
> 4xx responses, to ensure the incoming message is being delivered to exactly
> one user?
Not exactly. Courier's mail filtering API only issues one call, after
the body is
> Most mail gateways that I've worked with deal with this by rejecting
> mail when no recipients would accept the message. For messages with
> mixed results, the message is accepted and delivered to some and
> quarantined for others.
Gordon, could one potentially change the replies after the
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 available.
Bouncing mail,