[pfx] Re: status=deferred (bounce or trace service failure)
Viktor Dukhovni via Postfix-users: > On Mon, Apr 22, 2024 at 12:21:01AM -0400, 785 243 via Postfix-users wrote: > > > Recently i'm seeing a few messages deferred with status=deferred > > (bounce or trace service failure) > > > > instead of status=deferred (host .. said: 450 ...) > > > > from the logs: > > > > postfix/smtp[272605]: warning: unexpected protocol > > delivery_request_protocol from private/bounce socket (expected: > > delivery_status_protocol) > > Your master.cf file has bad settings. Post the verbatim (no rewrapping > of whitespace of line breaks) output of "postconf -Mf". > > The "bounce" service entries should be: > > # Possibly chrooted, if Debian prefers that. > # > bounce unix - - n - 0 bounce > defer unix - - n - 0 bounce > trace unix - - n - 0 bounce > > Or perhaps the "bounce" service executable has been replaced with a link > to a delivery agent? The "real" bounce service supports the expected > protocol. Replacing the 'bounce' service with the 'discard' delivery agent has never been a supported configuration. It just happened to "work" because of sloppy protocol checks. Wietse ___ Postfix-users mailing list -- postfix-users@postfix.org To unsubscribe send an email to postfix-users-le...@postfix.org
[pfx] Re: status=deferred (bounce or trace service failure)
I discovered I had bounce set to discard I don't recall why, it's been that way for years. Maybe to suppress backscatter. After i set it back to bounce' i got the expected 550 reject On Mon, Apr 22, 2024 at 2:09 AM Viktor Dukhovni via Postfix-users wrote: > > On Mon, Apr 22, 2024 at 12:21:01AM -0400, 785 243 via Postfix-users wrote: > > > Recently i'm seeing a few messages deferred with status=deferred > > (bounce or trace service failure) > > > > instead of status=deferred (host .. said: 450 ...) > > > > from the logs: > > > > postfix/smtp[272605]: warning: unexpected protocol > > delivery_request_protocol from private/bounce socket (expected: > > delivery_status_protocol) > > Your master.cf file has bad settings. Post the verbatim (no rewrapping > of whitespace of line breaks) output of "postconf -Mf". > > The "bounce" service entries should be: > > # Possibly chrooted, if Debian prefers that. > # > bounce unix - - n - 0 bounce > defer unix - - n - 0 bounce > trace unix - - n - 0 bounce > > Or perhaps the "bounce" service executable has been replaced with a link > to a delivery agent? The "real" bounce service supports the expected > protocol. > > -- > Viktor > ___ > Postfix-users mailing list -- postfix-users@postfix.org > To unsubscribe send an email to postfix-users-le...@postfix.org ___ Postfix-users mailing list -- postfix-users@postfix.org To unsubscribe send an email to postfix-users-le...@postfix.org
[pfx] Re: status=deferred (bounce or trace service failure)
On Mon, Apr 22, 2024 at 12:21:01AM -0400, 785 243 via Postfix-users wrote: > Recently i'm seeing a few messages deferred with status=deferred > (bounce or trace service failure) > > instead of status=deferred (host .. said: 450 ...) > > from the logs: > > postfix/smtp[272605]: warning: unexpected protocol > delivery_request_protocol from private/bounce socket (expected: > delivery_status_protocol) Your master.cf file has bad settings. Post the verbatim (no rewrapping of whitespace of line breaks) output of "postconf -Mf". The "bounce" service entries should be: # Possibly chrooted, if Debian prefers that. # bounce unix - - n - 0 bounce defer unix - - n - 0 bounce trace unix - - n - 0 bounce Or perhaps the "bounce" service executable has been replaced with a link to a delivery agent? The "real" bounce service supports the expected protocol. -- Viktor ___ Postfix-users mailing list -- postfix-users@postfix.org To unsubscribe send an email to postfix-users-le...@postfix.org
