[pmg-devel] [PATCH pmg-api/pmg-docs v2] make filter timeout configurable

Dominik Csapak d.csapak at proxmox.com
Wed Feb 21 15:35:07 CET 2024

Looked and tested this, and it does what it says on the tin.

My original concern still exists but that would require a much more
intrusive fix (that we can still do in the future):

when the sending/remaining processing of the mail (aka the actions)
take longer than what time we still have remaining, we have
the same behavior as the original problem.

a short example:

filter-timeout: x seconds
processing up to the check: y seconds (but smaller than x)

if now the actions take more than 'x - y' seconds, the first
postfix instance runs into it's timeout, but the pmg-smtp-filter
is already processing the action (e.g. sending/quarantining)

To completely fix that, we'd have to (before the timeout check):
find out what actions would be taken,
return the postfix that status as if it was done
(e.g. accept/reject) (if that's even possible?)

and then do the actual action.
if that fails, we'd have to take an appropriate action,
e.g. send an ndr.

Aside from that, consider this series

Reviewed-by: Dominik Csapak <d.csapak at proxmox.com>
Tested-by: Dominik Csapak <d.csapak at proxmox.com>

More information about the pmg-devel mailing list