Exchange 2013 STMP via Open Relay converts attachments to text?

Posted on 2013-08-28
Medium Priority
Last Modified: 2013-09-24
We have several photocopiers in the office that send scanned images via Email.
They have a very simple setup:  STMP server name  :     SMTP Port :
We have set up this before and it worked fine with our Exchange Server 2003.

The new Exchange Server 2013 is setup to accept Mail Relay (under Flow Control) from the photocopier IP address.
Actually the Mail Relay works, because we receive the mail from the photocopier fine.  It's just the attachment (should be a PDF) is converted to scrambled ASCII in the body of the mail message.

I don't know where to check in the Exchange Server 2013 for attachment settings?

Question by:Mchallinor
  • 3
  • 2

Expert Comment

ID: 39444826
It could be an incompatibility issue between the photocopier and the Exchange 2013, can you force the mail relay to use HELO instead of EHLO, this will turn off the extended Exchange SMTP language set and it should use a simpler mime format which may resolve the issue.

Author Comment

ID: 39444852
Where would you make the changes?
Attached are two images for the Mail Relay setup...
LVL 25

Expert Comment

by:Mohammed Khawaja
ID: 39444860
Another option would be to use SMTP on a IIS server (worked for us).
Easily manage email signatures in Office 365

Managing email signatures in Office 365 can be a challenging task if you don't have the right tool. CodeTwo Email Signatures for Office 365 will help you implement a unified email signature look, no matter what email client is used by users. Test it for free!


Expert Comment

ID: 39444912

Set-ReceiveConnector -Identity "<name of your connecter here" -BinaryMimeEnabled=$false

Restart the transport service and then retry sending from the copier, if that doesn't work, set it back using:

Set-ReceiveConnector -Identity "<name of your connecter here" -BinaryMimeEnabled=$true

And then setup an IIS relay instead ;)

Accepted Solution

Mchallinor earned 0 total points
ID: 39506180
Thanks for your suggestions however this was a problem with MS Exchange Server resolved by a cumulative update


Problem Solved

Author Closing Comment

ID: 39517245
No suggestion worked because it was a bug in Exchange Server 2013 resolved by a cumulative update.

Featured Post

Get your problem seen by more experts

Be seen. Boost your question’s priority for more expert views and faster solutions

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Upgrading from older Exchange server to the latest Exchange server can be tiresome, error-prone and risky, without being a seasoned exchange server administrators. It can become even problematic if you're an organization that runs on tight timeline…
There’s hardly a doubt that Business Communication is indispensable for both enterprises and small businesses, and if there is an email system outage owing to Exchange server failure, it definitely results in loss of productivity.
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…
Exchange organizations may use the Journaling Agent of the Transport Service to archive messages going through Exchange. However, if the Transport Service is integrated with some email content management application (such as an anti-spam), the admin…

586 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