Hi, >> Would it technically possible to have a smtpd_to_lmtp_proxy option (or >> however it could be called), that would receive on smtpd and open a >> connection to its LMTP server, doing cleanup and Co. in memory and wait for >> the result of the LMTP server? If the LMTP process gets 250 OK, postfix >> would give that back to the client. Else closing the session with error >> status code received from the LMTP server. > > quota and such things can be done with a policyd, below a example for dbmail > ___________________________ > > generally wait for a 250 OK from LMTP would be dumb
But you have to wait for that with smtpd_proxy_filter as well ;-) > > * think about performance Improvmnet. No queuing on MTA side > * think about temporary LMTP problems 450 Service currently not available. Same behavior than with Milter problems. > * consider how make a difference hard/soft Can you give mor details on that? > * you do NOT want a hard-bounce obly because LMTP hangs Why? If I can not hand over mail to the LMTP server, the remote MTA would still queue the mail and retry later. > some months ago i did as example a major-upgrade on dbmail > i stopped imap/pop3 and closed submission port > but we received new messages due the whole migration > after that "postqueue -f" delivered all of them to the inboxes See above. Kind regards -Christian Rößner -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Franziskanerstraße 15, 81669 München Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 Vorstand: Patrick Ben Koetter, Axel von der Ohe, Marc Schiffbauer Aufsichtsratsvorsitzender: Joerg Heidrich
