HTML Email Signatures | MDaemon Technologies, Ltd.
  1. Forum
  2. MDaemon
  3. HTML Email Signatures

HTML Email Signatures

  • T

    Thank you Arron. I will consider the beta program down the line when we are up and running live. 

     

    0 likes
  • A

    We are working on improving our documentation for HTML signatures.  I think it may help you as well. 

    I've said in the past that CSS is not supported, this is not correct.  CSS is supported, however, our sanitization process removes the style tag, which is where the CSS is commonly found.  My apologies for the incorrect information.

    We use a sanitization process to try to prevent problems.  The following tags are the only tags allowed in a client signature:
     
      "address", "article", "aside", "footer", "header", "h1", "h2", "h3", "h4", 
      "h5", "h6", "hgroup", "main", "nav", "section", "blockquote", "dd", "div", 
      "dl", "dt", "figcaption", "figure", "hr", "li", "main", "ol", "p", "pre", 
      "ul", "a", "abbr", "b", "bdi", "bdo", "br", "cite", "code", "data", "dfn", 
      "em", "i", "kbd", "mark", "q", "rb", "rp", "rt", "rtc", "ruby", "s", "samp", 
      "small", "span", "strong", "sub", "sup", "time", "u", "var", "wbr", "caption", 
      "col", "colgroup", "table", "tbody", "td", "tfoot", "th", "thead", "tr", "img",
      "span", "u", "map", "area"
     
    Any tag that is not in the list above will be stripped when saved using Remote Administration.  This includes html, head, body, and style tags.
     
    Styling should be done inline using a style attribute.
     
    Below is an example of the signature we use for mdaemon.com that uses inline styling.
     
    -- <br>
<strong>$CONTACTFULLNAME$</strong>
<br>$CONTACTBUSINESSTITLE$
<br><strong>o</strong>: 817-601-3222
<strong>e</strong>: $CONTACTEMAILADDRESS$<br><br>
<span style=" font-size: 16pt;"><strong>M</strong>Daemon Technologies</span><br>
<span style="font-weight: bold; font-size: 10pt;">Simple Secure Email</span>
<br><br>
Visit us on <a style="color: #006699;" href="https://www.mdaemon.com">www.mdaemon.com</a> | 
<a style="color: #006699;" href="https://www.facebook.com/MDaemon.Technologies/">Facebook</a> | 
<a style="color: #006699;" href="https://www.linkedin.com/company/mdaemon-technologies">LinkedIn</a> | 
<a style="color: #006699;" href="https://www.youtube.com/c/MDaemonTechnologies">YouTube</a> | 
<a style="color: #006699;" href="https://www.reddit.com/r/MDaemonTechnologies/">Reddit</a>
<br>Sent using the <a style="color: #006699;" href="https://www.mdaemon.com/">MDaemon Email Server</a></div>
     
    If you want to bypass the sanitization process you can save the file directly on the MDaemon server.  Domain client signatures are saved under \MDaemon\Domains\$DOMAINNAME$\, default client signatures are stored at \MDaemon\Domains\, and group client signatures are stored at \MDaemon\Data\Groups\$GROUPNAME$\, in the ClientSignatures.html and ClientSignatures.txt files. Administrators should proceed with caution when bypassing the sanitization process as its possible to introduce issues.  For example, you can manipulate the style of an entire email, a style tag in the body violates the HTML standard and could lead to unpredictable behavior in email clients, and tags could be used to introduce malicious content.  

    --
    Arron Caruth

    0 likes
  • 1
  • 2 / 2
Please login to reply this topic!