2
NDRs for non-existing users causing blacklisting
Question asked by Tina Cline - 1/23/2018 at 9:15 AM
Unanswered
I have to admit I am a spool watcher.  I routinely take a look throughout the day as it gives me a quick glance at possible issues such as email domains not accepting email or not functioning, possible spam compromises, blacklisting, etc.  
Usually there are about 100+ emails in the spool trying their 10 times to send - they are usually all System Admins sending NDRs to spammers since the User Does Not Exist in a certain domain.  Some of these incoming spams do have a weight well above the deliverable threshold, but because the user does not exist , SM cannot verify if it should be rejected or not and just send the user non-existent NDR.  
Is there a way to tell the to not send Smartermail NDRs for emails of a certain weight?  
This is snagging us as some of these NDRs are going to known spam-traps and blacklisting us.
SmarterMail 15
 
Example; here is what our current spool has 213 of:
Return-Path: <>
Message-ID: <636015146784037195@mySmartermail.Server.com>
From: "System Administrator"
To: Spammer@Spammer.com
Date: Tue, 14 Jun 2016 15:24:38 -0400
Subject: Delivery Failure
X-SmarterMail-MessageType: Bounce

1 Reply

Reply to Thread
0
Tina Cline Replied
BUMP - this is still occurring where NDRs for "No Such User" are getting caught in spamtraps and resulting BACKSCATTERER blacklisting.  Can we turn off No Such User NDRs only?

Reply to Thread