This rule will trip on a blank subject header (where the header DOES exist, but has no content)

[Rule001]
RuleName=If subject is NOT empty, Skip next rule
Enable=Yes
ThisRuleCondition=All
ProcessQueue=LOCAL
Condition01=SUBJECT|reg exp|AND|^..+$|
Action01=skip rule|"1"
[Rule002]
RuleName=Subject IS empty!
Enable=Yes
ThisRuleCondition=All
ProcessQueue=LOCAL
Condition01=SUBJECT|exists|AND|
Action01=move to bad Msg|


UPDATE 2009/06/17: For some reason this rule was completely broken, both by WordPress inserting smartquotes, and a logic error. My apologies, it has been corrected and tested on MDaemon 10.0.5, it should now work as advertised.

It has been reported that this SpamAssassin rule helps:

header __CTYPE_MULTIPART_MXD Content-Type =~ /multipart\/mixed/i
mimeheader __ANY_TEXT_ATTACH Content-Type =~ /text\/\w+/i
meta MIME_IMAGE_ONLY (__CTYPE_MULTIPART_MXD && __ANY_IMAGE_ATTACH && !__ANY_TEXT_ATTACH)
score MIME_IMAGE_ONLY 2.00
describe MIME_IMAGE_ONLY Image body part but no text body parts

To use it, copy these five lines into the bottom of your \MDaemon\SpamAssassin\rules\local.cf file, then either restart MDaemon or create a mdspamd.sem file in the \MDaemon\App\ directory.

You may want to tweak the “Score”, but start with 2.0 as this rule hasn’t been aggressively tested so there is a higher risk of false positives then with the default SpamAssassin rules.

Lastly, it’s also worth mentioning that Outbreak Protection (part of SecurityPlus 4 and higher) is flagging these messages as spam.

UPDATE 2009/05/19: The above rule only works in MDaemon 10 and higher, for earlier versions, you’ll need one more line:

mimeheader __ANY_IMAGE_ATTACH Content-Type =~ /image\/(?:gif|jpeg|png)/
(Thanks goes to “Greg Vancardo” for tracking this one down)

The lookup is still in the SA 3.24 rules MDaemon uses. If you have DNS service available set to Yes or Test, that might be slowing down SA processing. Try adding the following line to your \MDaemon\SpamAssassin\rules\local.cf file.

score RCVD_IN_DSBL 0

Once this is done, open a command prompt and type the following command to reload your SpamAssassin rules, and/or restart MDaemon;

echo. > C:\MDaemon\App\mdspamd.sem

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).

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

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.

Happy monitoring!

If a MSG file has no corresponding record, MDaemon will update the IMAP.MRK file the next time an IMAP client or WorldClient user touches the folder, and the message will be treated as UNSEEN and UNREAD

The header is defined as follows:

struct IMAPMrkHeader
{
unsigned HeaderVersion;
unsigned UIDValidity;
unsigned UIDNext;
unsigned LastWriteCounter;
unsigned Filler0;
unsigned Filler1;
unsigned Filler2;
unsigned Filler3;
unsigned CRLF;
};

Each MSG file will have one record, which is defined as follows:

struct IMAPMrkMessage {
char Filename[MAX_IMAP_FILENAME];
unsigned char Flags;
unsigned UID;
unsigned Size;
time_t Date;
};

#define FLAG_SEEN 32
#define FLAG_ANSWERED 16
#define FLAG_FLAGGED 8
#define FLAG_DELETED 4
#define FLAG_DRAFT 2
#define FLAG_RECENT 1
#define MAX_IMAP_FILENAME 23
#define IMAP_RECORD_SIZE 36

So what do all those fields mean?

• HeaderVersion is a tag to identify what file format the IMAP.MRK is using. The current value is 1. UIDValidity is the IMAP UID Validity for the folder. UIDNext is the UID that will be used for the next message added to the folder.
• LastWriteCounter is a value that changes whenever something has changed in the file. This was added when IDLE support was added to the IMAP server, so that there’s a quick way to check for changes (by comparing this one value rather than doing a compare of the entire file’s contents).When changing records in the file, lock the IMAP folder, increment the LastWriteCounter, change the records, then unlock the folder.
• UIDNext is the next UID to be assigned. To add records, lock the IMAP folder, increment the LastWriteCounter, and for each record you’re adding, use the current UIDNext value as its UID and then increment UIDNext.

So how do you lock a folder?

• Lock an IMAP folder by creating a file “IMAP-foldername-email.lck”, where foldername is a “filename-safe” version of the folder name (” and ‘/’ characters replaced with ‘_’) and email is the owner’s email address (use “public” for public folders). If the lock file already exists, something is currently operating on the IMAP.MRK so you should wait until it is unlocked before you lock it and continue.

Hope this helps someone.

In the Default Domain GUI you have your “Domain IP” to which you can then “Restrict connections to this IP”, which will bind MDaemon to a single IP address.

You can’t add multiple DomainIP lines to the INI file, but there is a trick you can use, we rely on the fact that each secondary domain can be bound to it’s own IP address, but those IPs will service requests for all domains as long as the user logs in using their full email address.

To bind 10.0.0.1 and 10.0.0.2 to MDaemon but not 10.0.03, bind 10.0.0.1 to your primary domain, then bind 10.0.0.2 to a secondary domain called mail-2.example.com (where example.com is your real domain, and mail-2.example.com is the DNS record assigned to 10.0.0.2), rinse and repeat for each additional domain.

Hope this helps.

For some time I’ve been using a RapidSSL reseller called “RapidSSL Online”

Unlike much of the competition, their prices start at $14.95USD/year, offering 128 / 256 bit single root SSL certificate.

I have no affiliation with them beyond being a satisfied customer, and I receive no compensation for this referral, I simply detest some of the larger players charging substantially more for what is ultimate the same thing.