Solved

Disable Base64 Encoding for Specific Mailbox/Contact on Exchange 2010

Posted on 2012-03-26
4
4,273 Views
Last Modified: 2012-04-02
Hi Guys,

Is there a way to Disable Base64 Encoding for a Specific Mailbox/Contact on Exchange 2010?

We're having issues with our Managed Services Software whereby we've narrowed it down so that emails sent from the application are being encoded in Base64 and our SMS Provider that receives these emails doesn't support it - Simply SMS's us as Base64 messages.

Thanks in Advance!

Cheers,
Ray.
0
Comment
Question by:UncleRaymondo
  • 2
4 Comments
 
LVL 15

Expert Comment

by:tenaj-207
ID: 37772732
It appears that you can only change the encoding for the Exchange server as a whole, not on individuale mailboxes.  

Here's more information;
http://technet.microsoft.com/en-us/library/gg144562.aspx
or
http://technet.microsoft.com/en-us/library/bb310794.aspx
0
 
LVL 27

Expert Comment

by:tliotta
ID: 37774354
Be aware that if base64 encoding (or similar encoding) is needed because the e-mail contains anything but 7-bit ASCII text, then you're trying send stuff that is not allowed without encoding. That's just a fundamental requirement.

Tom
0
 

Accepted Solution

by:
UncleRaymondo earned 0 total points
ID: 37776483
Hi Guys,

Thanks for the replies, but I've managed to resolve the issue about 5 minutes ago. Tom, that's true, but for some reason, this SMS provider (of which the Email Alerts get forwarded to), doesn't support Base64 Encoded Emails/Messages and the Base64 Encoded message is what was appearing in the SMS Messages.

Tenaj-207, you can actually be a lot more specific than the whole Exchange Server. How I fixed it was by creating a New-TransportRule, changing the Content-Type header from text/html to text/plain and then removing the Content-Transfer-Encoding header which is where it said base64. The actual command is as follows:

New-TransportRule -Name '<call it whatever here>' -Comments '' -Priority '0' -Enabled $true -SentTo '<put the external email you're sending to here>' -SetHeaderName 'Content-Type' -SetHeaderValue 'text/plain' -RemoveHeader 'Content-Transfer-Encoding'

Once we did that, the email alerts via our SMS provider to our phones came through as readable text :)

Thanks again for your help!

Cheers,
Ray.
0
 

Author Closing Comment

by:UncleRaymondo
ID: 37795068
Issue Self Resolved
0

Featured Post

Free Tool: Path Explorer

An intuitive utility to help find the CSS path to UI elements on a webpage. These paths are used frequently in a variety of front-end development and QA automation tasks.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Find out what you should include to make the best professional email signature for your organization.
This article explains how to install and use the NTBackup utility that comes with Windows Server.
The basic steps you have just learned will be implemented in this video. The basic steps are shown to configure an Exchange DAG in a live working Exchange Server Environment and manage the same (Exchange Server 2010 Software is used in a Windows Ser…
To add imagery to an HTML email signature, you have two options available to you. You can either add a logo/image by embedding it directly into the signature or hosting it externally and linking to it. The vast majority of email clients display l…

821 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question