Author Archives: Dave Warren (everything-mdaemon.com)

Exporting Worldclient contacts the hard way

Posted on by — No Comments ↓

In a previous post I covered the supported ways to access WorldClient contact data. Now we’ll dig under the hood a little and I’ll show you one method to convert a contact entry directly to a CSV file. The only tools needed are Windows Explorer and Excel 2007.

Open Windows Explorer on the server, browse to the user’s contacts folder:

e.g. C:\MDaemon\USERS\example.com\UserName\Contacts.IMAP

Copy the file AddrBook.mrk to a temporary area, where you can work on this file, then rename this file to AddrBook.xml. You can copy the file to another machine, from this point forward MDaemon isn’t needed.

Start Microsoft Excel 2007.

Select File – Open – browse to the temporary area and choose the AddrBook.xml file.

Leave the option “As an XML table” option selected and click OK, then click OK again.

Excel will now have a new file opened with the following columns: version, encoding, guid, modified, fullName, email

Delete the columns: version, encoding, guid & modified

Keep the columns: fullName & email

You can now copy and paste this data into a CSV format required by your email client address book for importing.

Please note: the above instructions work if using MS-Office Excel 2007, older versions of Excel may not have the required XML importer.

Exporting Worldclient contacts the easy way

Posted on by — 6 Comments ↓

How can I export contacts from my WorldClient address book?

There are two supported methods, and one unsupported method I’ll cover later.

  • ComAgent

ComAgent can synchronize a WorldClient address book with Outlook or Outlook Express.

To use ComAgent, have the user login to WorldClient, go to Preferences, then download and install ComAgent. Once installed, right click on ComAgent, go to Properties, then to Address Book Synchronization, choose the appropriate mail client and local folders and away you go.

Note that this is a two-way synchronization, items in your local address book will be sent up to the server. This is unavoidable.

  • SyncML

This method takes a bit more work, but is actually more flexible since you can access any Contacts folder. The process requires an SyncML external application, so you’ll need to find one based on the destination.

Relying on upstream ISP spamassassin

Posted on by — 2 Comments ↓

In a default configuration, MDaemon automatically removes the existing X-Spam-Flag header on inbound mail so that pre-inserted headers don’t interfere with your local SpamAssassin configuration.

In certain cases, such as where your ISP inserts a trusted X-Spam-Flag header of their own, you may want to change this behaviour.

Changing this is pretty simple; Go to Setup –> Misc Options –> [Headers] tab, uncheck the “Strip ‘X-Spam-Flag’ option” and MDaemon will stop stripping the header.

Now, be aware you can’t use this header as input to SpamAssassin if it’s the same header that your SpamAssassin outputs, but you could use the content filter if you wanted to set this to yes if the ISP *or* local MDaemon say “Yes”

So, if you’re running a local copy of SpamAssassin too, you’ll need to make some changes.

First, edit the 10_misc.cf file and comment or change the “add_header spam Flag _YESNOCAPS_” line.

If you changed it to “add_header spam FlagX _YESNOCAPS_” then you’ll get a header called X-Spam-FlagX instead and you can use this internally.

NOTE: Normally I would not recommend editing the built-in files, normally we suggest you use local.cf or your own CF file. This is an exception as there is no way to “undo” this command, you need to remove it entirely. Also be aware that whenever you upgrade MDaemon, these changes will need to be re-done.

Once the appropriate “add_header” entry is changed, you can either use the content filter or your local SpamAssassin itself to filter on the X-Spam-Flag header.