26 Sep MDaemon 18.5 – Now with Dynamic Email Signatures

More is better. The mantra of the signature stuffer.

From job titles and contact details to special offers and even instructions to save the trees. Nothing is off limits when it comes to providing ‘useful’ information to our lucky recipients by the medium of email footer.

It’s a perfect picture unless of course, you’re the poor soul tasked with making sure the emails your company sends are consistent, professional and accurate.

If you’re that person, you’re going to love this latest MDaemon release.

MDaemon 18.5 now makes it possible for you as the mail administrator to have central control over the information that’s displayed in footers, along with the option of pulling the common content such as name, job role, contact info etc. from the information held in MDaemon’s public contacts.

That’s right, personalised signatures for all, that don’t become out of date and that are ideal for adding things like custom lines for time-limited promotions. Woohoo!

Let’s take a look at the steps…

Step 1 – Making sure the user-specific information is available within your Public Contacts

So in order to use custom fields, we need to store the information somewhere.

To do this MDaemon makes use of the Public Contacts folder.

This automatically will contain a contact for every MDaemon user, with many fields of information that can be populated.

For example, if you want to include your business phone number in the signature, simply make sure all your contacts have a phone number configured.

Once you’re happy the data you want to display is recorded within the public contacts for our users, we can move onto editing the global signature template.

Step 2 – Global Signature settings

The global signature settings can be found under Settings > Server Settings > Default SIgnatures.

In this example, I’ve created a text-only signature and a basic HTML formatted signature that will be used depending on the sending email format the client chooses.

There are two Signature Macros used in this example:

$CONTACTFULLNAME$

and

$CONTACTBUSINESSPHONE$

Both will be replaced by the sender’s data stored under there own public contact.

Step 3 – Preview signature

All that’s left is to check when composing a new email that your info is displayed correctly.

Senders no longer need to add any signature, in fact it’s worth actively advising against this from now on. MDaemon has it covered!

For a full list of macros that can be used please see the table below:

(please note this data needs to be populated within the public contact or blank data will be passed)