Exchange Disclaimer plain text formatting - email

I am using a Transport Rule in Exchange Server 2010 to append some HTML to the end of our company emails. This is working just fine when an email is sent out as HTML. When the message is plain text, the HTML and images are converted into [links] and it looks a mess.
Is it possible to apply conditional formatting to append an HTML message at the end of HTML emails, and a different layout for plain text emails? Failing that, can I get it to simply ignore the rule if the message isn't in HTML?
Thank you

I have discovered that the only way to achieve what I was after is by using a 3rd party add-on. So the answer to the question really is "no" for both parts!
3rd party tools like Symprex or Exclaimer may help people out in a similar situation.

Related

Outlook email format changes when forwarded, How to format in such a way its not modified

The automated outlook emails using pywin32 and plain HTML were great till people started using it for forwarding and reply, Once you forward all the HTML formats are getting stripped and the borders of the table suddenly disappears. The way around is to go to your outlook settings and disable the option "Reduce message size by removing format information not necessary for the message".
The question is how to format the email so that it wont be lost when forwarded and make the format information necessary for the message ?
I have found out a work around though, It is observed that outlook is stripping of those styles which are defined in style block, If the styles are defined embedded in tags its escaping the stripping. As of now I have taken this approach

How to select a URL from an email in mutt and open it in a web browser?

When I read mails I sometimes would like to select one of the links in the mail's text to open it in a web browser.
Before you answer, I know there is urlview, but there are also BASE64-encoded (or other transfer encodings) mails from which urlview does not find any URLs. Then there are also HTML-only mails that can also be encoded with transfer encodings.
I wonder if there is a trivial and/or nice solution that I couldn't find. I cannot be the only one with this problem. It does not need to be based on urlview, of course.
urlview will work if you employ the "pipe_decode" setting. Example use in a macro, binding to "\u":
macro index,pager \\u "<enter-command>set pipe_decode = yes<enter><pipe-message>urlview<enter><enter-command>set pipe_decode = no<enter>" "view URLs"
with urlscan there exists a worthy successor to urlview.
Support for emails in quoted-printable and base64 encodings. [..] For HTML mails, a crude parser is used to render the HTML into text.

Replying to other email

I'm building webmail with PhpMailer.
I need advice about replaying to other email.
How to attach previous email? Should I simply attach it as a file - I think it's not good.
I prefer attach email text, but how? Using only blockquote? But what about previous mail's styles? I see in thunderbird blockquote with cite="mid:hash" attribute. What is it?
Maybe PhpMailer has some options regarding this?
It's generally pretty straightforward. Read this about how to deal with the headers (use addCustomHeader to set them) so that mail clients can identify it as a reply.
There's no particular standard for what to do with the body, though it's common to copy all the lines of the original body into the new message, preceded by >, though you could wrap it in a blockquote in HTML, or some other formatting. It's up to you what you do with attachments.

Handling Outlook-style quoting in Gnus

Since a lot of my workflow is Emacs-based, I'm trying to migrate to using Gnus at the office. Most people here use Outlook and with it rely on the Microsoft-style top-quoting in replies.
I've set things up quite nicely with markdown automatically converted to HTML when I post etc. The problem is that I end with the text version of the quoted messages in the reply thread instead of the original HTML email. This is not really appreciated by the other participants in the thread.
My question is: Is there a way in which I can preserve the original HTML in the reply-chain when replying using top-posting style?
I've been looking at various ways of doing it myself, but there is actually a lot of work doing it right, as it involves parsing the original HTML and inserting my message in the right place, etc. So I was hoping that someone else might have done this already.
After a long time, this question has remained unanswered so I concluded that no one has had the need to do this.
So, I resorted to solve it myself. My solution involves taking the message that is written, passing it through muse in order to format it as HTML, then passing this generated HTML together with the original HTML source of the original mail and send it to an external application that I wrote that parses the HTML and merges them into a new HTML document. This HTML is them returned and is then inserted into the email buffer before being submitted.
There was quite a lot of hackery needed in order to make sure that attachments are handled correctly, but in the end it all worked out well.
The code is available at: https://github.com/lokedhs/gnus-outlook-style

Multipart email best practices

I am developing a web app that sends out emails. Currently, all emails have a HTML part.
Questions:
Is it important to include a text part also?
Do you include both?
Is just removing all the tags from the HTML message and adding a few line breaks good enough to create a text part from the HTML part?
Thanks, Kevin
Is it Important to include a text part also? It's a best practice to provide a plain text version of the email. However, in my opinion and in this day and age, I would guess that it is not such a big deal to leave it out. However, if you know more about your recipients' email clients (eg: if you're sending the emails in a corporate environment and everyone uses a particular email client), then you can determine how necessary it really is.
Do you include both? The .net framework (which I use) provides an AlternateView class (MSDN) that allows you to easily specify copies of an email in different formats. It makes things very easy to include a plain text version of the email. Perhaps you can find something similar in apache/php.
Is just removing all the tags from the HTML message and adding a few line breaks good enough to create a text part from the HTML part? Technically, yes but be VERY CAREFUL here. A complex HTML layout that has been converted to plain text will look absolutely terrible if all you do is remove HTML tags and pile the content together. It really depends on your content and how much you can do to manipulate said content. Also, take a look at Campaign Monitor'ssuggestions for formatting plain text emails.
One final word of advice for you HTML emails to test, test, and then test some more. When you're finished testing, test again. HTML emails will render differently in different email clients and, if some of your recipients are using Microsoft Word 2007/2010 then you can forget about web standards. I urge you to take a look at Campaign Monitor's Guide to CSS support in email.