44
be marked as not-spam.
CaseSensitivity
- values 0 or 1. 0 meaning the phrase is case insensitive. 1 meaning the
phrase is case sensitive.
Examples:
replica, SPAM, 100, 0
Dear eBay member, PHISH, 90, 1
return to sender, BOUNCE, 80, 0
Further options for blacklisting/whitelisting are offered by files
approvedsenders
and
blockedsenders
, that can be found
under
C:\Documents and Settings\All Users\Application Data\ESET\ESET Mail Security\MailServer
. You can add sender
addresses or domains to these lists, while the
approvedsenders
file represents the list of allowed addresses/domains,
the
blockedsenders
file represents the list of blocked addresses/domains.
Warning:
As senders' addresses are very often spoofed (altered to appear as original), we do not recommend to use
the
approvedsenders
and
blockedsenders
files as means of whitelisting/blacklisting. The use of allowed and blocked IP
addresses for this purpose is much more reliable and secure. If you need to whitelist by the address/domain of the
sender (the
approvedsenders
file), you should always employ an additional method of message validation (e.g. SPF).
Other settings:
enable_spf
This option enables/disables validation by Sender Policy Framework. This validation method
checks the public rules of a domain - domain policy to determine whether a sender is authorized
to send messages from that domain.
enable_all_spf
This option is to determine whether domains not on the spf_list or Mailshell file can bypass the
SPF validation. For this option to work correctly the enable_realtime_spf parameter must be set
to yes.
enable_realtime_spf Is the option enabled, DNS requests will be sent in real-time during SPF validation. This can
negatively influence the performance (delays during message evaluation).
spf_list
This option allows you to assign importance to a specific SPF entry, thus influencing the overall
spam score of a message.
spf_*_weight
The asterisk represents 14 possible SPF validation results (see
spamcatcher.conf
for more details).
The value entered for this parameter is an offset, that is then applied to the spam score
according to individual result types. If the SPF validation results is "fail" the offset from the
spf_fail_weight parameter will be applied. Depending on the offset value the resulting spam
score is then increased/decreased.
spf_recursion_depth Maximum nesting depth (using the "include" mechanism). The RFC 4408 norm specifies this limit
to 10 (to prevent Denial-of-Service), however, some SPF records nowadays do not respect this
limit, as more nesting levels need to be applied to fully satisfy the SPF request.
enable_livefeed_sen
der_repute
If this option is disabled, the SPF information from
LiveFeed
will be ignored.
