Looks like SM will accept a message for a disabled account over SMTP, then generate an outgoing bounce back to sender?

Looks like SM will accept a message for a disabled account over SMTP...

[2024.09.29] 21:10:58.008 [59.59.90.196][65038424] rsp: 250 OK <contact@WHATMAN.COM> Sender ok
[2024.09.29] 21:10:58.008 [59.59.90.196][65038424] Sender accepted. Weight: 0. 
[2024.09.29] 21:10:58.258 [59.59.90.196][65038424] cmd: RCPT TO: <contact@test.com>
[2024.09.29] 21:10:58.258 [59.59.90.196][65038424] rsp: 250 OK <contact@test.com> Recipient ok

...then generate an outgoing bounce back to sender during delivery...

[2024.09.29] 21:11:11.144 [65265906] Starting local delivery to contact@test.com
[2024.09.29] 21:11:11.144 [65265906] Delivery for contact@WHATMAN.COM to contact@test.com has bounced. Reason: The recipient does not exist
[2024.09.29] 21:11:11.347 [65265906] DSN email written to 65265907 with status failed to contact@test.com

(`contact@test.com` is a disabled account)

These then get usually stuck in the queue since they are from spammers.

Seems like it would make more sense to check if the account is disabled before sending back the "250 OK" to the "RCPT TO:" during the SMTP transaction?

Is this possible to configure?

Thanks!

-josh

Tony Scholz Replied

10/1/2024 at 10:54 AM

Employee Post

Hello Josh,

What version of SmarterMail are you running? When I test this locally the bounce is during the SMTP session?

10:50:30.342 [127.0.0.1][37118524] cmd: MAIL FROM:<fake_user@fake_doamin.tld> BODY=8BITMIME SMTPUTF8
10:50:30.342 [127.0.0.1][37118524] senderEmail(1): fake_user@fake_doamin.tld
10:50:30.342 [127.0.0.1][37118524] rsp: 250 OK <fake_user@fake_doamin.tld> Sender ok
10:50:30.342 [127.0.0.1][37118524] Sender accepted. Weight: 0. 
10:50:30.342 [127.0.0.1][37118524] cmd: RCPT TO:<acquaintances.sbin.testing@ascholz.io>
10:50:30.346 [127.0.0.1][37118524] acquaintances.sbin.testing@ascholz.io is disabled.
10:50:30.346 [127.0.0.1][37118524] rsp: 551 <acquaintances.sbin.testing@ascholz.io> No such user here
10:50:30.349 [127.0.0.1][37118524] disconnected at 10/1/2024 10:50:30 AM

In this case the user is set up as "Disabled (do not allow mail)". Running version 100.0.9035.22254 (Sep 26, 2024)

Tony Scholz System/Network Administrator SmarterTools Inc. www.smartertools.com

josh levine Replied

10/11/2024 at 1:17 PM

SmarterMail Professional

Build 8664 (Sep 21, 2023)

Also, there is a catch-all on the domain so maybe that matters?

Thanks!

-josh

2 Replies

Reply to Thread

Related Knowledge Base Articles

2 Replies

Reply to Thread

Tags

Related Knowledge Base Articles