![]() This includes, for example, setting their spam filters to automatically delete messages marked by SpamAssassin, or setting up their personal black and white lists. Though you cannot configure SpamAssassin to delete all spam messages, you can let each mailbox owner configure their own spam protection settings. ![]() If you want, the spam filter will additionally include a specific text string to the beginning of the messages' subject line (by default, this string is *****SPAM*****). So, for the server-wide policy, you can choose only marking messages as spam: X-Spam-Flag: YES and X-Spam-Status: Yes headers are added to the message source by default. If SpamAssassin marks valid messages as spam, decrease the sensitivity by setting a higher value.Īt the server level, you cannot set the server-wide spam filter to automatically delete spam: you can do it only on a per-mailbox basis. If your users still receive spam messages with the default sensitivity, increase it by setting a lesser value, for example, 6. By default, the filter sensitivity is set so that all messages that score 7 or more points are classified as spam. For example, a message containing the text string “BUY VIAGRA AT LOW PRICE!!!” in Subject line and message body scores 8.3 points. ![]() The higher the number, the more likely a message is spam. As a result, each message scores a number of points. To identify spam messages, SpamAssassin performs a number of different tests on contents and subject line of each message. To achieve the desired level of spam protection, Plesk lets you configure a number of SpamAssassin settings, namely: The SpamAssassin spam filter identifies spam messages among emails sent to mailboxes hosted on your Plesk server. Go to documentation for the latest version, Plesk Obsidian.
0 Comments
Leave a Reply. |