Solved

Disable Base64 Encoding for Specific Mailbox/Contact on Exchange 2010

Posted on 2012-03-26
4
4,392 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
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 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

MS Dynamics Made Instantly Simpler

Make Your Microsoft Dynamics Investment Count  & Drastically Decrease Training Time by Providing Intuitive Step-By-Step WalkThru Tutorials.

Question has a verified solution.

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

Read this checklist to learn more about the 15 things you should never include in an email signature.
After hours on line I found a solution which pointed to the inherited Active Directory permissions . You have to give/allow permissions to the "Exchange trusted subsystem" for the user in the Active Directory...
To show how to generate a certificate request in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.:  First we need to log into the Exchange Admin Center. Navigate to the Servers >> Certificates…
In this Micro Video tutorial you will learn the basics about Database Availability Groups and How to configure one using a live Exchange Server Environment. The video tutorial explains the basics of the Exchange server Database Availability grou…

752 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