Igor,

That option has been available in version 2.0.1.309 and higher, please see the release notes below. Error codes are mandatory in the customized items, if an entry does not have an error code, no error will be reported to the remote SMTP server, which will cause SpamFilter to accept the email even though it may be spam.

// New to VersionNumber = '2.0.1.309';
{TODO -cNew : When the SpamFilter.ini is updated the event is logged}
{TODO -cNew : Added the :TAG option to the AuthorizedTO whitelist to tag emails classified as spam}
{TODO -cNew : Updated documentation and GUI to show blacklists that support the :NULL tag}
{TODO -cNew : Added the TagAndQuarantine option to SpamFilter.ini file}
{TODO -cNew : Added the SPAMTagPrefix option to SpamFilter.ini file to customize spam tag prefix in subject}
{TODO -cNew : We are now writing in the activity log when a quarantined email is forced-delivered}
{TODO -cFix : The Do not quarantine and :NULL option for the attachment blacklist is now working correctly}
{TODO -cNew : Added ini option for DoNotSendNDROnQuarantine - this will cause all emails to be accepted without returning an error code to the remote server, thus preventing NDR's to be sent to the sender}

;Setting DoNotSendNDROnQuarantine to 1 will prevent generation of NDR when email are quarantined by causing SpamFilter *not* to send an error code when quarantining emails
DoNotSendNDROnQuarantine=0

Roberto F.
LogSat Software

Benny,

Thanks for pointing out the misleading note. We've updated the release note to read as follows:

{TODO -cNew : Added ini option for DoNotSendNDROnQuarantine - this will cause all emails to be accepted from the sender (but not forwarded to the recipient) without returning an error code to the remote server, thus preventing NDR's to be sent to the sender}

Roberto F.
LogSat Software

Benny,

You can'tremove the 3-digit code at the beginning of the customized responses. Without that code the sender will not know what happened to the email, may resend it, may or may not cause a bounce, remote servers testing your server may see it non-RFC compliant and blacklist you, and so on... In short, do so if you wish, but you will see unexpected behavior and we will not be able to provide support.

Roberto F.
LogSat Software

Benny,

Since the RFC require the presence of the 3 digit code in the SMTP responses, not including it can and will have unpredictable results from the various mail servers. As this is a condition that should never occur, how each software reacts to a condition that's not supposed to happen is unknown. SpamFilter will, depending on the filter, accept an email, reject an email, generate an NDR, make an email "disappear" if the codes are not there. In all cases, it's behavior that will not be controlled as it's a scenario that must never occur.

If you wish to find out more, RFC 2821 is a very good source of information.

Roberto F.
LogSat Software