Bounce notifications received from Smartermail but not when sending from Gmail
Problem reported by rishikesh Somshetti - 1/22/2026 at 6:01 AM
Not A Problem

Hello SmarterTools Team,

We are observing an inconsistency with bounce notifications for invalid recipient email addresses and would like your guidance.

Expected behavior:
When an email is sent to an invalid email ID within a domain, a bounce (NDR) notification should be delivered back to the sender.

Observed behavior:

  • When testing from smarter mail, sending emails to invalid email IDs correctly generates bounce notifications to the sender.

  • However, when performing the same test from Gmail, no bounce notification is delivered back to the sender.

Test details:

  • Recipient: Invalid/non-existent email ID on our domain

  • Sending clients tested:

    • smarter mail→ Bounce received ✅

    • Gmail → No bounce received ❌

As per internal guidance, we verified that bounce handling works correctly at the server level via smarter mail, but Gmail-originated emails do not appear to receive or relay the bounce notification.

Could you please clarify:

  1. Whether this behavior is expected when emails are sent from external providers like Gmail?

  2. If Gmail suppresses or handles NDRs differently for invalid recipients?

  3. Whether any SmarterMail configuration is required to ensure bounce notifications are generated or relayed back to external senders like Gmail?

Looking forward to your insights.

Andrew Barker Replied
Employee Post
As far as SmarterMail's behavior, this is expected. Bounce messages are supposed to be generated by the last server to accept the message.

When a sending server issues a RCPT TO command during an SMTP session, the receiving server is permitted to check if it can accept mail for the specified recipient. If it cannot, then the receiving server should return an error message. In the case of a recipient who does not exist, that error would probably be something like "550 No such user". That error response indicates that the server does not accept the message for that recipient, and it then becomes the responsibility of the sending server to generate the bounce message.

I can think of three likely reasons for why you are not getting bounce messages in your test. The first is that Gmail is not requesting bounce messages. Bounce messages are failure type Delivery Status Notifications (DSNs) and must be requested during the SMTP session. This leads to the second possibility, that a server in the relay chain does not support DSNs, since support is an optional extension of the SMTP protocol. If some server between the originating server and the destination server does not support DSNs, then a DSN request will get lost. Finally, some servers that officially support DSNs may be configured to not generate failure messages specifically.

As for your final question, since it is not SmarterMail's responsibility to generate the bounce message in your scenario, there is not really any configuration change you can make to ensure bounce messages are generated.
Andrew Barker Lead Software Developer SmarterTools Inc. www.smartertools.com
Sébastien Riccio Replied
Hi,

When I'm sending a mail from gmail to an invalid user of a domain hosted on our SmarterMail instance, I'm receiving a bounce back in gmail, generated by gmail, saying the remote server responded with 550 error code saying that no such user exists.

Is that the test you're doing ?

If yes, do you have any incoming gateway in front of SmarterMail ?

You might also want to check your smartermail delivery logs and SMTP logs to capture the session related to your attempt that did not generate the bounce, to see what SmarterMail replied in the SMTP session.

Kind regards.


Sébastien Riccio System & Network Admin https://swisscenter.com
rishikesh Somshetti Replied
Hi,

We are performing the same test. However, in our case we do not receive any bounce message in Gmail when sending to an invalid user on the SmarterMail-hosted domain.

Additionally, we do not see any related SMTP or delivery log entries on our SmarterMail server for these attempts, which suggests the message may not be reaching SmarterMail at all.

Reply to Thread

Enter the verification text