"How do you actually do this in Tuffmail? There doesn't seem to be any way to access the whitelist maintained by one of the webmail clients from a custom Sieve script..."The key to doing this at Tuffmail -- or at any IMAP service provider that lets you create Sieve scripts through both a webmail client and a stand-alone Sieve editor -- is to use the Sieve include extension to include your webmail-created Sieve script in your non-webmail-created Sieve script.
Here's how I set this up at Tuffmail.
- Go to manage.tuffmail.net and log in to the Tuffmail Account Manager.
- Go to Mailboxes > Sieve Filters and choose the the relevant UserID (aka the relevant "mailbox").
- Create your primary Sieve script and have it contain something like this:
include :personal "bluelist";
include :personal "greenlist";
#IMPORTANT: The ingo script must be edited through the Horde interface.
include :personal "ingo";
- Name this script and save it. I use the name
1sieveso it will be listed first in my Script Name list (that's why the first character is
- In the Scripts for UserID box in the upper right of this Tuffmail Account Manager window, click Activate to activate this primary script.
- Use this Tuffmail Account Manager window to create your greenlist and bluelist scripts[*], but do not activate them. Your primary Sieve script (created in Step 3) will be the only active script.
- Log on to Horde, go to Options > Filters, and make sure the following is not checked.
[ ] Automatically activate the script on the server after each change?This will ensure that your primary script (e.g.,
1sieve) is not de-activated when you use Horde to update the
ingoscript must be created and edited through the Horde interface. For example, by clicking the Whitelist button in Horde/IMP.
- After you have set up your scripts, send test messages to this user's account (the user specified in Step 2) and make sure that all of this user's Sieve filters are working as you expect.
phpscriptin the above instructions. [I'm not sure what the analog of Step 7 is in SquirrelMail -- please post a comment if you know.]
You can maintain all your Sieve scripts, other than
phpscript, using a desktop ManageSieve client. ManageSieve is a good reason to download and try Mulberry. Mulberry recently became free/gratis and supports IMAP, LDAP, ManageSieve, and a lot more!
[*] I discuss Sieve greenlist scripts in Greenlisting with Sieve. I use a bluelist to filter my solicited bulk email, e.g., mailing lists, and I will write more about Sieve bluelist scripts in a future post.
Hashtag: #greenlisting [?]
Post & Read Comments (located elsewhere)
Post & Read Comments (located here)
If you train Bogofilter on all ham marked as unsure, it rapidly recognises your mail. Bogofilter false negatives are very rare, so I setup the bayes filter to add -20 to mail classified as ham, which is close to whitelisting. Bogofilter does a better job of whitelisting than sieve rules can, because it carries on working even if an address changes.
I have a sieve rule that uses the sieve copy extension to place a copy of all mail not caught as spam, and marked as Unsure by bogofilter, in the top-level autotrain folder. As they are copies I don't actually have to read mail in this folder. Once in a while I look it over and drop the contents into the approriate training-folder; however, after a few weeks, virtually nothing comes into this folder. Those that do are normally from someone I haven't corresponded with before.
Links to this page
Each item © Nancy McGough
Each comment © the author of the comment
Deflexion.com web site hosted by DreamHost.com
← More deflexions & reflexions, & feeds available via the sidebar top &
For bookmarks & links, please use