Steffen Nurpmeso wrote in <20240131203248.XtHi_6Do@steffen%sdaoden.eu>: |Wietse Venema via Postfix-users wrote in | <4tqc213rcwzj...@spike.porcupine.org>: ||So you're suggesting that as long as an MTA-to Milter connection ||is not in an error state, sending || || SMFIC_QUIT_NC || ||and later sending || || SMTIC_CONNECT || ||are sufficient to make a Milter fully forget a past SMTP session and ||to make it ready to handle events from a new SMTP session? || ||I'd like to see some documentation for that. | |Well. That is how QUIT_NC is documented i would say, i munged it to | | a_SMFIC_QUIT_NC = 'K', /* QUIT but new connection follows (since \ | Sendmail 8.14) */ | |So this implies that SMFIC_CONNECT is to be expected next. I have | | $Id: milter-protocol.txt,v 1.6 2004/08/04 16:27:50 tvierling Exp $ ...
I did not understand because i have seen no code that backs SMFIC_QUIT_NC. If only somewhere there would have been a "QUIT, but socket remains open and SMFIC_CONNECT follows". To be honest *i* first stumbled because of select(2) waking up and read returning 0, in a loop. I only then realized that the socket was actually closed. That is, i have * 'Q' SMFIC_QUIT Quit milter communication * Expected response: Close milter connection and, you know: i did not. But the socket was dead! What a shame. --steffen | |Der Kragenbaer, The moon bear, |der holt sich munter he cheerfully and one by one |einen nach dem anderen runter wa.ks himself off |(By Robert Gernhardt) _______________________________________________ Postfix-users mailing list -- postfix-users@postfix.org To unsubscribe send an email to postfix-users-le...@postfix.org
