You can also use an asterisk (*) as a wildcard for zero or more characters and a question mark (?) as a wildcard for zero or one character, much as you would to specify filename patterns in a shell. If a sender's address matches a whitelist_from address, the spam score of the message is reduced by 100 points, which makes it nearly impossible for the message to be tagged as spam.įor example, if you receive important messages from, you can ensure that they won't be tagged as spam by using this line in the systemwide configuration file: whitelist_from can use multiple whitelist_from directives or multiple addresses in a single directive to whitelist several addresses. The sender's address is the address that appears in the Resent -From header, if that header exists, or in any of the headers: From, Envelope-Sender, Resent-Sender, or X-Envelope-From. Use the whitelist_from directive to whitelist a sender's address. Whitelists are most commonly used to ensure that messages from important senders are not marked as spam, but they can also be used to change the spam threshold for recipients or enable recipients to effectively opt out of spam-tagging. SpamAssassin whitelists reduce the spam scores of messages when the sender or recipient appears on the whitelist. A related feature, autowhitelists, is covered in Chapter 4. It begins by examining the SpamAssassin directives for systemwide whitelisting and blacklisting, and then explores two different ways to manage user-specific lists. #SPAMASSASSIN BLACK LIST HOW TO#This chapter discusses how to set up whitelists and blacklists. SpamAssassin also allows you to set up system-wide or user-specific lists of senders whose mail should be tagged as spam. You may know ahead of time that you don't want to receive mail from certain organizations or senders. On the other hand, you may regularly receive unwanted mail from a particular sender that doesn't get tagged reliably by SpamAssassin. SpamAssassin allows you to set up systemwide or user-specific lists of senders whose mail should not be considered spam, and (systemwide) lists of users who don't want their email filtered. You may even have users who don't like spam-filtering. You may want to be sure that SpamAssassin will never mistake email from an important user, client, vendor, or other sender for spam. If you plan to white or blacklist your domain, please check our Whitelisting/Blacklisting your domain article.Although SpamAssassin generally does a good job of avoiding false positives, you may find that some mail that you want to receive contains enough spamlike characteristics that SpamAssassin regularly tags them as spam. More details on this feature are available in our White and Black listing section article. You can manage your white and black lists in both webmail clients by clicking on the Manage button next to SpamAssassin White and Black listing from the E-mail Filters section. When SpamAssassin is enabled for your mailbox, you can take advantage of its white and black listing feature. The only difference in the SpamAssassin management interface between the webmail clients and hosting Control Panel is that SpamAssassin can be disabled only through the hosting Control Panel. Since the SpamAssassin management interface in the webmail clients is identical to the one available in the Mail Manager section of the hosting Control Panel, you can refer to our Enable SpamAssassin article for instructions on how to enable and manage your SpamAssassin settings. You can manage the SpamAssassin settings for your mailbox by opening the Settings task in Roundcube or the Options tab in Webmail Classic from the main menu, going to E-mail Filters, and using the SpamAssassin subsection. SpamAssassin is a very powerful filter, you can learn more about it in our SpamAssassin article.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |