Back to Community Threads
1
Reject spam - Don't mark as spam
Idea shared by Thomas Odermatt - 7/1/2015 at 12:20 AM
Completed
I use another tool called NoSpamProxy. It's a spam smtp server and works as follows:
 
All incoming mails comes via port 25 to the nospamproxy. They are checked by rbl and other criteria. If an email is identified as spam it won't be accepted. All other emails were forwarded to SmarterMail.
 
I think it is the best solution to reject spam as this: Senders of wrong identified spam (good emails) were informed that email could not sent because of a spam filter.
 
SmarterMail has the whole functionality. In my opinion is it really simple: Just add a spam filter action to reject instead of 'delete message', 'add prefix to subject'...
 
 

6 Replies

Reply to Thread
0
SMTP Blocking does exactly what you want.  The messages are rejected and the sender notified.
Thanks, -Joe
0
Joe,
Where is that at ?  See screenshots.  On our SmarterMail there is no option for that under SMTP Blocking.  How do we implement rejection ?
 
 
www.HawaiianHope.org - Providing technology services to non profit organizations, low income families, homeless shelters, clean and sober houses and prisoner reentry programs. Since 2015, We have refurbished over 11,000 Computers !
0
 
It always contains the most up-to-date settings for SmarterMail, and effectively blocks more than 97% of all spam messages before they are accepted.
 
The document is updated frequently, and the link to the most recent version will always be found in the KB article, "SmarterMail Antispam Settings Document"
 
Bruce Barnes ChicagoNetTech Inc brucecnt@comcast.net Phonr: (773) 491-9019 Phone: (224) 444-0169 E-Mail and DNS Security Specialist Network Security Specialist Customer Service Portal: https://portal.chicagonettech.com Website: https://www.ChicagoNetTech.com Security Blog: http://networkbastion.blogspot.com/ Web and E-Mail Hosting, E-Mail Security and Consulting
0
In your first screen capture you have SMTP Blocking, Incoming Weight Threshold set to 30 and enabled. So any message that hits 30 points on tests you've enabled for SMTP Blocking will be rejected and the sender will receive a "554 Sending address not accepted due to spam filter" bounce message. So all you have to do is set your weights according to your wishes.

What you NEVER want to do is use the "Delete Message" option if you want your server to be HIPAA-HITECH ciomplaint which only allow deleting of messages that are potentially dangerous or harmful.... which does not include that they may simply be spam. In other words EVERY message must be accounted for (either reported to the recipient or sender) unless that message is potentially dangerous or harmful. So you're on the right track by SMTP Blocking since that keeps you complaint because the sender is notified of the disposition of the message. If you simply deleted it neither the sender or recipient would be, or could be, notified of the disposition of the message... a clear violation unless it is potentially dangerous or harmful (which would include phishing, but not plain spam).

If a User or Domain Administrator chooses to filter messages that includes deleting messages your server is still complaint. If you as a System Admin who provides email services for others choose the policy to delete you are clearly non-compliant.

-Joe
Thanks, -Joe
0
So with the first screen, and SMTP blocking enabled, does that mean the message over 30 is fully rejected ? should they still show up in the inbox or junk folder because of screenshot 2 ?

Right now even though those are our settings, we are still getting "high" spams coming in to the junk folder. Is that normal ?
www.HawaiianHope.org - Providing technology services to non profit organizations, low income families, homeless shelters, clean and sober houses and prisoner reentry programs. Since 2015, We have refurbished over 11,000 Computers !
0
Take a look at your Antispam Administration page and look at the various Spam Checks. You can then select which spam checks you want to use for SMTP Blocking by checking the boxes in the "Enable for SMTP blocking". In your case if an inbound message exceeds 30 points in the tests you have marked as enabled for SMTP blocking the message will be REJECTED and the sender will simply receive a bounce message saying "554 Sending address not accepted due to spam filter". Those messages will not be accepted by SmarterMail.

Both questions have to do with which tests you've enabled for SMTP Blocking.
Thanks, -Joe
Back to Community Threads

Reply to Thread

Related Knowledge Base Articles

Recommended SPAM SettingsSmarterMail > Antispam and Antivirus
Deploying Rspamd For Use With SmarterMailSmarterMail > Server Configuration and Management
Cannot Send Email MessagesSmarterMail > Troubleshooting
Legal Holds and LitigationSmarterMail > Installation and Configuration
Untangle Spam Filtering and SmarterMail TLS IssuesGeneral Topics