Threading messages in Thunderbird
Posted on April 24, 2009
Filed Under General | Leave a Comment
One of my favourite features in a mail client is Threading. This shows you all the messages in a folder that are related to one conversation in one place, similar to GoogleMail’s conversation view, but it actually more context with you have multiple related discussions going on at once.
Outlook Express has had it for years, as has Thunderbird, WorldClient recently added Threading support too. For OE and WorldClient, this setting is per-user, it applies to all folders in your profile, so it’s easy enough to toggle. However, Thunderbird stores the “thread” flag on a per folder basis though, which is always a pain when setting up a new computer since I’ve got hundreds of folders and want every one of them threaded. After literally years of searching, I stumbled across a way to accomplish this goal.
Find your Thunderbird profile, create a file called “user.js” and edit it in notepad. Take care to not end up with “user.js.txt” as that won’t work. Inside the file, add these lines:
# Mozilla User Preferences
user_pref(“mail.check_all_imap_folders_for_new”, true);
user_pref(“mailnews.default_sort_order”, 22);
user_pref(“mailnews.default_sort_type”, 1);
user_pref(“mailnews.default_view_flags”, 1);
user_pref(“mailnews.headers.showSender”, true);
user_pref(“mailnews.headers.showUserAgent”, true);
Restart Thunderbird, and now any newly created folders will automatically have threading enabled, oldest threads first. If you want newest threads first, change “default_sort_type” to 2.
I got this clue from Thunderbird’s bugzilla bug #86845 and thought I’d share it here since I’m sure I’m not the only one who has wanted this.
So what if you want to make all your current folders thread automatically without going folder by folder? If you use IMAP, you’re in luck, shut down Thunderbird, look for the \ImapMail\ subdirectory and rename or delete it. This will cause Thunderbird to forget everything it knows about all folders, reloading them as new, and redownload all content (which doesn’t take long since it just downloads headers, messages aren’t downloaded until they’re accessed).
Don’t autorespond to forwarded messages
Posted on March 4, 2009
Filed Under MDaemon | Leave a Comment
It is sometimes desireable to avoid autoresponding to messages that have been forwarded from one local user to another.
This is especially useful if you regularly forward mailboxes to multiple destinations and want to avoid each of those destinations from generating their own autoresponses.
This whitelist allows you to enter both email addresses (which aren’t useful here) as well as headers that will cause an autoresponder to be skipped, in this case we’re adding the X-MDRedirect header, a header MDaemon adds when a message is forwarded.
- Go to the Accounts menu
- Select “Account Settings”
- Find “Auto Responders”
- Open the “White List” submenu
- Add “X-MDRedirect: 1″ to the autoresponder whitelist/exception list
Detecting the use of BCC from the content filter
Posted on February 26, 2009
Filed Under MDaemon | 3 Comments
This is a simple content filter rule that will help you in filtering messages where the current destination was BCC’d rather then being listed in the TO or CC field.
Note that this will trip on most mailing lists — This is correct behaviour, unless the mailing list fills in the recipient’s name in the TO field (and most do not), lists are essentially using BCC.
It only works reliably in the LocalQ, it won’t work in the RemoteQ unless you turn off smartspooling, and it only works for mail received via SMTP, not MultiPOP or DomainPOP.
[Rule001]
RuleName=Detect BCC’d messages
Enable=No
ThisRuleCondition=All
ProcessQueue=LOCAL
Condition01=TO|does not contain|AND|$HEADER:X-Rcpt-To$|
Condition02=CC|does not contain|AND|$HEADER:X-Rcpt-To$|
Action01=add header|”X-BCC”,”True”
To use this rule, copy the above text and paste it into the very top or very bottom of your MDaemonAppcfrules.dat file using Notepad, then open the content filter dialog in MDaemon and enable the rule.
No semaphore files needed, no need to restart MDaemon.
« go back — keep looking »