Re: Milter calls based on conditions and deliberate delays

Noel Jones: > > > On Apr 10, 2021, at 11:10 AM, Wietse Venema wrote: > > > > ?Ralph Seichter: > >> * Wietse Venema: > >> > Would that not cause a prohibitively large number of open connections > between Postfix's smtp and the sleeping proxy? > >>> > >>> Limited by the (master.cf) per

Re: Milter calls based on conditions and deliberate delays

> On Apr 10, 2021, at 11:10 AM, Wietse Venema wrote: > > Ralph Seichter: >> * Wietse Venema: >> Would that not cause a prohibitively large number of open connections between Postfix's smtp and the sleeping proxy? >>> >>> Limited by the (master.cf) per-delivery-transport process lim

Re: Milter calls based on conditions and deliberate delays

Ralph Seichter: > * Wietse Venema: > > >> Would that not cause a prohibitively large number of open connections > >> between Postfix's smtp and the sleeping proxy? > > > > Limited by the (master.cf) per-delivery-transport process limit, > > and the (main.cf) per-delivery-transport concurrency limi

Re: Milter calls based on conditions and deliberate delays

* Wietse Venema: >> Would that not cause a prohibitively large number of open connections >> between Postfix's smtp and the sleeping proxy? > > Limited by the (master.cf) per-delivery-transport process limit, > and the (main.cf) per-delivery-transport concurrency limits. I have written and tested

Re: Milter calls based on conditions and deliberate delays

> On 07 Apr 2021, at 14:35, Ralph Seichter wrote: > > * Wietse Venema: > >> What problem are you trying to solve? > > Milters A, B and C in my example scenario can trigger asynchronous > actions in backend systems, the results of which become available only > after a delay caused by processi

Re: Milter calls based on conditions and deliberate delays

Ralph Seichter: > * Wietse Venema: > > > What does the milter do when data is unavailable? > > My understanding is that milter D is unable to decide whether or not to > add its own flag header if the data is unavailable. There might be a > default behaviour, but it would render the milter useless

Re: Milter calls based on conditions and deliberate delays

* Wietse Venema: > What does the milter do when data is unavailable? My understanding is that milter D is unable to decide whether or not to add its own flag header if the data is unavailable. There might be a default behaviour, but it would render the milter useless. It would require milter chan

Re: Milter calls based on conditions and deliberate delays

Ralph Seichter: > * Wietse Venema: > > > Perhaps better, Milter D defers the message immrediately, and Postfix > > retries a few minutes later, until the necessary data is available. > > Indeed. Having milter D block until the required data becomes available > would tie up too many resources. Bet

Re: Milter calls based on conditions and deliberate delays

* John Stoffel: > So what happens if you get 1,000 emails coming into your system? In one form or other, incoming messages flagged by milters A-C need to be queued until milter D is ready for them. Like I wrote in my original post, I am expecting a queue size of 1-5 million messages during peak h

Re: Milter calls based on conditions and deliberate delays

* Wietse Venema: > Perhaps better, Milter D defers the message immrediately, and Postfix > retries a few minutes later, until the necessary data is available. Indeed. Having milter D block until the required data becomes available would tie up too many resources. Better to make D reply with 4xx a

Re: Milter calls based on conditions and deliberate delays

* Wietse Venema: What problem are you trying to solve? On 07.04.21 22:35, Ralph Seichter wrote: Milters A, B and C in my example scenario can trigger asynchronous actions in backend systems, the results of which become available only after a delay caused by processing, which takes about 3 min

Re: Milter calls based on conditions and deliberate delays

Wietse Venema: > Ralph Seichter: > > * Wietse Venema: > > > > > What problem are you trying to solve? > > > > Milters A, B and C in my example scenario can trigger asynchronous > > actions in backend systems, the results of which become available only > > after a delay caused by processing, which

Re: Milter calls based on conditions and deliberate delays

Ralph Seichter: > * Wietse Venema: > > > What problem are you trying to solve? > > Milters A, B and C in my example scenario can trigger asynchronous > actions in backend systems, the results of which become available only > after a delay caused by processing, which takes about 3 minutes. These >

Re: Milter calls based on conditions and deliberate delays

> "Ralph" == Ralph Seichter writes: Ralph> * Wietse Venema: >> What problem are you trying to solve? Ralph> Milters A, B and C in my example scenario can trigger Ralph> asynchronous actions in backend systems, the results of which Ralph> become available only after a delay caused by processi

Re: Milter calls based on conditions and deliberate delays

* Wietse Venema: > What problem are you trying to solve? Milters A, B and C in my example scenario can trigger asynchronous actions in backend systems, the results of which become available only after a delay caused by processing, which takes about 3 minutes. These results are required by milter

Re: Milter calls based on conditions and deliberate delays

Ralph Seichter: > Hello list, > > I am trying to configure Postfix to process inbound mail in the following > manner: > > 1. A sender connect to Postfix smtpd to deliver a message. > > 2. Postfix calls Milters A, B, C. Each of these Milters can either (a) > reject the message, (b) accept the mes

Re: Milter calls based on conditions and deliberate delays

On 2021-04-07 20:10, Ralph Seichter wrote: If you have ideas that could help me solve this, I'd appreciate you letting me know. maybe https://github.com/milter-manager/milter-manager ?