Reposition Email Signatures on Reply and Forward
MDaemon Signatures do not appear to be signatures as we come to appreciate in Outlook Emails, but rather a message Disclaimer. It would be nice to have the ability to position the signature after a senders message content added as a message reply or message forward. MDaemon currently adds the signatures to the very bottom of the message content of replied and forwarded messages. This doesn't look very professional when all the signatures appear to be grouped at the bottom of the message. It looks confusing. As a side note, users on mobiles devices with ActiveSync should have their mobile signature removed and an MDaemon user configured signature added for consistency. This could be done by allowing a broader use of MACROS and configuration options within CF Rules.
A new signature management tools has been implemented in MDaemon that addresses this issue. Added the ability to configure a signature that is pushed to supported mail clients (Webmail and MDaemon Connector). A default client signature can be set at Setup | Server Settings | Client Signatures or it can be set per domain on the Domain Manager’s “Client Signatures” screen. Use macros such as $CONTACTFULLNAME$, $CONTACTEMAILADDRESS$, to personalize the signature with data pulled from the user’s contact in the domain’s Public Contacts folder. Use the $ATTACH_INLINE:filename$ macro for inline images in the HTML signature. After entering signature text, it will appear in Webmail as the “System” signature, and will become the user’s default signature. It can be enabled/disabled by default at Setup | Web & IM Services | Webmail | Settings or per domain on the Domain Manager’s “Webmail” screen. For MDaemon Connector, the signature’s name and related settings can be configured at Setup | MDaemon Connector | MC Client Settings | Signature. Requires MDaemon Connector 6.5.0 or newer, and “Push client settings to MC users” to be enabled. The $CLIENTSIGNATURE$ macro can be used in other mail clients to have the server add the client signature to messages.
We are using v19.5.5 and no comment on this feature in v20, the signature is still appending to the very bottom of the email threads rather than at the bottom of the new message sent. What Arron is saying is if the person uses WorldClient, not other email clients.
We are using v19.5.5, and the signature is still appending to the bottom of the email rather than at the bottom of the new message sent.
Which version? v20 up till now is not public.
The signature should be appended just below a new message that is added, not at the end of the message thread. People don't scroll down to the bottom of thread to see sender signature.
Presently, signature is appended to the end of the message. And if the message is a response and is threaded, the signature is at the bottom of the thread.
Suggestion is the signature should be added at the end of the new message text, not at the end of the thread.
Dan Wallace commented
I was going to add this same idea myself... I wish I could add more votes!!
I've been looking at ways to resolve this issue using CF, and thought I'd found a way by specifying a "<<SIG>>" code in the Outlook signature, then using the CF Search and Replace option, but unfortunately this only allows one word to be suplimented. If this could be tweaked to allow an HTML file to be inserted where the "macro" is, then this would be a quick and easy solution while a full solution is investigated.
Implementing this together with the much needed personal macros and potention AD macros mentioned in several other suggestions, eg $Firstname$, $lastname$, $jobTitle$, $PhoneNumber$ , would be a vast improvement.
The signature capabilities within MDaemon are very poor by comparison to the features offered by Exchange and as an administrator looking for more control, thanks to business demands for consistency, and marketing dept demands for adding marketing messages to outgoing emails, this is something that is weakening my support for what has been a fantastic product in the 10 years I've been using it.