> 1) here is my setting for MercuryS SMTP server : under connection control > Relay control
They seem to be OK (and if one of the lower options is checked, option 1 is grayed - see help)
> 2) I also looked under "Compliance", But I am do not know what to check or not?
You may i.e. "Limit maximum number of failed RCPT commands" and "Limit maximum number of failed RCPT commands" in conjunction with "Enable short-term blacklisting for compliance failures". But do it with care - read the help or the Mercury manual. I activate them on need - in case those atempts increase.
> What is kind of setting do you have?
Activated "Enable transaction-level expression filtering" and put in some special rules there. But these rules depend on using a NDS/eDirectory of Novell for authentification. In NDS are objects represaenting organisation and it may be possible to send mails to the organisation ... resulting in errormessages (these objects don't have a mailaddress :-). I stopped this boring errors by creating rules so MercuryS will reject those mails already on communication with sender.
Have a killfile for some addresses that come on and on ... and activated "Check originator address fields against the killfile". Perhaps you may need a whitelist in addition.
You may reject mails on missing headers like subject and date ... but this is more to "educate" the senders to put in a significant subject or to use mailclients setting the date-header. I didn't enable it but it may be, that not a few spammers miss setting date or subject and it may be a possibility to reduce contacts by spammers.
At least all these setting are for enabling MercuryS to reject mails already on communication with originator or a delivering external mailhost.
If you have problems with spammails, read on spamhalter and install it in Mercury. You have to do a lot of training for selflearning spamhalter in the beginning and always have to look for false positiv.
bye Olaf
<p>&gt; 1) here is my setting for MercuryS SMTP server : under connection control &gt; Relay control </p><p>They seem to be OK (and if one of the lower options is checked, option 1 is grayed -&nbsp; see help)</p><p>&gt; 2) I also looked under "Compliance", But I am do not know what to check or not?
</p><p>You may i.e. "Limit maximum number of failed RCPT commands" and "Limit maximum number of failed RCPT commands"&nbsp; in conjunction with "Enable short-term blacklisting for compliance failures". But do it with care - read the help or the Mercury manual. I activate them on need - in case those atempts increase.</p><p>&gt; What is kind of setting do you have? </p><p>Activated "Enable transaction-level expression filtering" and put in some special rules there. But these rules depend on using a NDS/eDirectory of Novell for authentification. In NDS are objects represaenting organisation and it may be possible to send mails to the organisation ... resulting in errormessages (these objects don't have a mailaddress :-). I stopped this boring errors by creating rules so MercuryS will reject those mails already on communication with sender.
</p><p>Have a killfile for some addresses that come on and on ... and activated "Check originator address fields against the killfile". Perhaps you may need a whitelist in addition.</p><p>You may reject mails on missing headers like subject and date ... but this is more to "educate" the senders to put in a significant subject or to use mailclients setting the date-header. I didn't enable it but it may be, that not a few spammers miss setting date or subject and it may be a possibility to reduce contacts by spammers.</p><p>At least all these setting are for enabling MercuryS to reject mails already on communication with originator or a delivering external mailhost. </p><p>If you have problems with spammails, read on spamhalter and install it in Mercury. You have to do a lot of training for selflearning spamhalter in the beginning and always have to look for false positiv.</p><p>bye &nbsp;&nbsp; Olaf</p><p>&nbsp;</p>
