Issue Mailer-Daemon does not send notifications to failed mail sender.

[Luciferian]

Server operating system version

Debian 10.13

Plesk version and microupdate number

Plesk Obsidian 18.0.52

Hello everyone,

I hope someone can help me with an issue I'm experiencing on my Plesk server with Postfix.

The problem is that when I send an email to a non-existent address, the sender does not receive the bounce delivery notification from the mailer-daemon. I have checked the Postfix logs and found the following entries:

2023-06-01 15:31:40 INFO postfix/smtp [11616] 6F65F438C6: to=<[email protected]>, relay=mx1.gmail.it[62.141.49.168]:25, delay=6.4, delays=0.08/0.02/0.33/6, dsn=5.1.1, status=bounced (host mx1.gmail.it[62.141.49.168] said: 550 5.1.1 <[email protected]>: Recipient address rejected: User unknown in virtual mailbox table (in reply to RCPT TO command))

2023-06-01 15:31:34 INFO postfix/smtp [10906] 0C98743146: to=<[email protected]>, relay=127.0.0.1[127.0.0.1]:10024, delay=0.53, delays=0.11/0/0/0.41, dsn=2.0.0, status=sent (250 2.0.0 from MTA(smtp:[127.0.0.1]:10025): 250 2.0.0 Ok: queued as 6F65F438C6)"

As you can see, the email is correctly rejected by the destination server with a bounce message, but the sender does not receive the bounce delivery notification.

I would expect the sender to receive a failed delivery notification in case the destination address does not exist or is incorrect. I have checked the Postfix configuration, but I couldn't identify the issue.

Has anyone had similar experiences in the past or any suggestions on how to resolve this issue?

Thank you very much!

PS: I came from a migration with the official Plesk tool from Centos. On the old server, the notification worked correctly.

 

[mediengestalter]

I have a similar issue, also after Migration from older Ubuntu with Plesk Obsidian. But the bounce messages are sent to the Server-Admin-Adress, not to the original sender.

OS version: Ubuntu 22.04.3 LTS
Plesk version: Plesk Obsidian 18.0.54 Update #3

 

[Peter Debik]

@mediengestalter, it depends on what the true technical sender address of an email was. For example if the mail was generated by a website, it may mention the <subscription-user>@<hostname> as the sender. You'll first need to check the header content of the ougtoing mail thoroughly to find out what the recipient server sees.