On Mon, 2021-05-31 at 19:07 -0400, Wietse Venema wrote: > Jim Popovitch: > > > Postfix will try each IP address in the order as returned from > > > getaddrinfo(3) until it can establish a TCP connection. Postfix > > > will not reconnect when an established Milter connection goes bad. > > > For example, the Milter does not respond, or produces bad responses. > > > > Right, I got that from your earlier post, thank you again. Would you be > > interested in a patch or some idea on how to make that more robust? > > How would you handle the case that the Milter hangs after RCPT TO > or END-OF-DATA, or after the Milter has requested changes to queue > file content? That requires replaying events already sent to a > milter, and redoing changes already made to a queue file. >
Hanging after RCPT TO and END-OF-DATA should be (imho) handled the same as milter_command_timeout, unless there is some reason that I can't think of. I'm not sure about the after the Milter has requested changes to queue file contents, can you explain more about when/how that would happen? Thanks! -Jim P.
