On Wed, Dec 10, 2025 at 02:41:49PM +0100, Ralf Hildebrandt via Postfix-users wrote:
> I have several mails in my queue which exposed the same error: > "status=deferred (bounce failed)" When delivery fails, the queue manager tries to contact the bounce service to send a bounce reporting errors for one or more recipients. This fails for some reason. Perhaps a problem with "master.cf", or some problem with permissions (selinux or apparmor), ... When that fails, the message stays in the queue to be tried again later. > Logs for 4dQkMb1TPYz2xXY: These are not necessarily all the relevant logs. You should look for logs from the bounce(8) service at the same time. Of course if the connection was not successful, that would of course not be logged by bounce(8). > Dec 9 17:11:19 mx01 postfix/smtp[2530437]: 4dQkMb1TPYz2xXY: > to=<[email protected]>, > relay=mailgate4.oneofmydomains.de[195.50.145.12]:25, delay=77, > delays=0.27/76/0.19/0.05, dsn=5.1.1, status=bounced (host > mailgate4.oneofmydomains.de[195.50.145.12] said: 550 5.1.1 > <[email protected]>: Recipient address rejected: undeliverable > address: host 192.168.180.5[192.168.180.5] said: 550 Address unknown (in > reply to RCPT TO command) (in reply to RCPT TO command)) The delivery failed, and the recipient was marked "done" by the smtp(8) delivery agent, and presumably added to the bounce log. > Dec 9 17:11:20 mx01 postfix/qmgr[2494891]: 4dQkMb1TPYz2xXY: status=deferred > (bounce failed) The queue manager fails to trigger the bounce delivery. > Dec 9 17:19:17 mx01 postfix/qmgr[2494891]: 4dQkMb1TPYz2xXY: > from=<[email protected]>, > size=20709, nrcpt=1 (queue active) > Dec 9 17:19:17 mx01 postfix/qmgr[2494891]: 4dQkMb1TPYz2xXY: status=deferred > (bounce failed) Tries to trigger the bounce again. > Dec 9 17:29:17 mx01 postfix/qmgr[2494891]: 4dQkMb1TPYz2xXY: > from=<[email protected]>, > size=20709, nrcpt=1 (queue active) > Dec 9 17:29:17 mx01 postfix/qmgr[2494891]: 4dQkMb1TPYz2xXY: status=deferred > (bounce failed) Tries to trigger the bounce again. > Dec 9 17:49:17 mx01 postfix/qmgr[2494891]: 4dQkMb1TPYz2xXY: > from=<[email protected]>, > size=20709, nrcpt=1 (queue active) > Dec 9 17:49:17 mx01 postfix/qmgr[2494891]: 4dQkMb1TPYz2xXY: status=deferred > (bounce failed) Tries to trigger the bounce again. > Dec 9 18:29:17 mx01 postfix/qmgr[2494891]: 4dQkMb1TPYz2xXY: > from=<[email protected]>, > size=20709, nrcpt=1 (queue active) > etc. Tries to trigger the bounce again. > Yes, the machine shouldn't have accepted [email protected] > in the first place, but... shouldn't bouncing the mail work anyway? Yes, it should. Something is wrong with the system or Postfix config. > There's no "(error|warning|fatal)" log entries in that period. > This is Postfix 3.5.25 How about "panic"? In any case, this is a local matter, unrelated to any remote systems. On Wed, Dec 10, 2025 at 02:50:26PM +0100, Carsten Strotmann (sys4) via Postfix-users wrote: > > There's no "(error|warning|fatal)" log entries in that period. > > This is Postfix 3.5.25 > > I see the same here. > > These mails would bounce back to Google, and Google mail is not accepting the > bounces with That's not correct. The issue has nothing to do with any remote system, Postfix bounce delivery is asynchronous. The bounce services tries to queue a bounce for delivery, actual delivery to Google happens later as part of processing queued mail in the usual way. -- Viktor. 🇺🇦 Слава Україні! _______________________________________________ Postfix-users mailing list -- [email protected] To unsubscribe send an email to [email protected]
