Understanding Incoming SMTP Blocking

I am trying to understand how Incoming SMTP Blocking differs from the normal Filtering that is broken into the 3 weights.

I may be over thinking this, but since we have the highest weight in the Filtering set to Delete. Is the incoming SMTP blocking necessary?

Thank you,

Kevin

kevind Replied

3/27/2018 at 3:52 PM

It's more efficient to block at SMTP and never accept the message.

The alternative is to accept the message, put it in the spool, run a bunch of tests like SpamAssassin and Bayes, then delete it. This wastes disk and CPU.

Employee Replied

3/27/2018 at 3:56 PM

Employee Post Marked As Answer

Hi Kevin. Filtering occurs once the EML file has been created and the message added to the spool for delivery.

An SMTP block occurs during the inbound connection. If a block occurs, the sender will receive a "550 Sender is not allowed" response from SmarterMail, and the SMTP connection is terminated.

Kevin McNally Replied

3/27/2018 at 4:29 PM

Thanks Rod

3 Replies

Reply to Thread

Related Knowledge Base Articles

3 Replies

Reply to Thread

Tags

Related Knowledge Base Articles