Solved

Scanner Sending Text Exchange 2013

Posted on 2014-01-16
8
951 Views
Last Modified: 2014-01-26
Hey community.  Quick question regarding Exchange 2013 Standard and sending scanned documents as attachments.  I recently migrated this environment from Exchange 2010 to Exchange 2013 and since then the scanned documents have been sent to the recipient as a very large string of text rather than a PDF.

I'm thinking it may have something to do with the receive connector.  I attached some images. Thanks for the help.

This is the first part of one of the emails received.  The text goes on nearly forever.

This is a multi-part message in MIME format.
--DC_BOUND_PRE_<1389879852.000074c8add9>
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

This E-mail was sent from "RNPC8ADD9" (Aficio MP 2500).

Scan Date: 01.16.2014 08:44:12 (-0500)
Queries to: scanner@******.com
--DC_BOUND_PRE_<1389879852.000074c8add9>
Content-Type: application/pdf; name="20140116084412935.pdf"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
	filename="20140116084412935.pdf"

JVBERi0xLjQKJRamipIKNCAwIG9iago8PC9UeXBlL1hPYmplY3QKL1N1YnR5cGUvSW1hZ2UK
L1dpZHRoIDIyMDAKL0hlaWdodCAxNzAxCi9CaXRzUGVyQ29tcG9uZW50IDEKL0NvbG9yU3Bh
Y2UvRGV2aWNlR3JheQovRmlsdGVyIC9DQ0lUVEZheERlY29kZQovRGVjb2RlUGFybXMgPDwv
Q29sdW1ucyAyMjAwIC9Sb3dzIDE3MDE+PgovTGVuZ3RoIDEyNTE1MQo+PgpzdHJlYW0KABAV
UAAgKqAAQFVAAICqgAEBVQACAqoABAVUAA1CD48Pjw8Pjw8PjhB4fHh8eHh8djp4fHh05Dw+
PD45D7w+Pvjw+PD48Pvjw8Pjw+PDkPjw8Puh8efHh8eHh8fH33Q8+Pvj7w+Pjzoch4eHx4fH
h9zHh8ch4eHQ6HMeHh8cnx94cx4eHQ5Dw8PjodD4+PD748Pjk8Pjw5vjw8Pvjw+OMfHIeHx4
eHx98fHhyHh8fHQ6HQ6HIdj48PD48PvjodDmPDw8Pjw8PD48Pjw8Oh4eH3x98eHx8cY8Pjw8
OY++OxzeHx8eH3IffHGPj77mPPjw+PDkPjkObm+PD48PjsfH3h8eHQ6HIchxj4++PDw+PD74
8PjzmPDw+Pj7w+PDw+OQ8Oh4eHhzHh4eHx4eHx4fHh8eHh94dDz48PDodD48Pjw+PD48OQ+P
vD4+PDw6HQ+Pjw8Pjw8Pjw+PDkPjw5jofHh8fHh2Pj7mPDw+PD48PD48PDw+Pjw++PDmPDw+
8Pjw+Pvj48PDkPD7w+Pjw+PDkPjw+PD48PDiDw8OQ+5jw8Obw+OQ8PDw+PuQ+PDw+PDw+6Hh

Open in new window

copier-receive-connector.jpg
Copier-receive-connector-2.jpg
Copier-receive-connector-3.jpg
0
Comment
Question by:TripapHoniC
  • 5
  • 3
8 Comments
 
LVL 4

Expert Comment

by:milikad
ID: 39785438
1. Get the output of get-transportagent | fl

if you have any antispam agents then disable them

Restart transport service. If doesn't help then,


2. In authentication
Uncheck TLS and select Basic and Integerated Authentication  and in permissions select Exchange users

Restart transport service and check.

3. If none of the above works. Change the port to 24. Restart Transport services and check new mail with attachment.

Plz update the result
0
 
LVL 4

Expert Comment

by:milikad
ID: 39785444
* update to above is if you're going for step 3 then even change the port on scanner to 24 as well.
0
 

Author Comment

by:TripapHoniC
ID: 39785450
Thanks for the prompt response milikad.  I'm going to try your suggestions now.
0
 

Author Comment

by:TripapHoniC
ID: 39787322
This is what I get after I run the get-transportagent | fl command

It does look like I'm running some sort of built-in malware agent.  How would I stop it?

[PS] C:\Windows\system32>get-transportagent | fl


RunspaceId            : c54f3b72-a801-4d28-a0d4-57a24df2db95
Enabled               : True
Priority              : 1
TransportAgentFactory : Microsoft.Exchange.MessagingPolicies.TransportRuleAgent.TransportRuleAgentFactory
AssemblyPath          : C:\Program Files\Microsoft\Exchange Server\V15\TransportRoles\agents\Rule\Microsoft.Exchange.Me
                        ssagingPolicies.TransportRuleAgent.dll
Identity              : Transport Rule Agent
IsValid               : True
ObjectState           : New

RunspaceId            : c54f3b72-a801-4d28-a0d4-57a24df2db95
Enabled               : True
Priority              : 2
TransportAgentFactory : Microsoft.Exchange.Transport.Agent.Malware.MalwareAgentFactory
AssemblyPath          : C:\Program Files\Microsoft\Exchange
                        Server\V15\TransportRoles\agents\Antimalware\Microsoft.Exchange.Transport.Agent.Malware.dll
Identity              : Malware Agent
IsValid               : True
ObjectState           : New

RunspaceId            : c54f3b72-a801-4d28-a0d4-57a24df2db95
Enabled               : True
Priority              : 3
TransportAgentFactory : Microsoft.Exchange.TextMessaging.MobileDriver.TextMessagingRoutingAgentFactory
AssemblyPath          : C:\Program Files\Microsoft\Exchange Server\V15\bin\Microsoft.Exchange.MobileDriver.dll
Identity              : Text Messaging Routing Agent
IsValid               : True
ObjectState           : New

RunspaceId            : c54f3b72-a801-4d28-a0d4-57a24df2db95
Enabled               : True
Priority              : 4
TransportAgentFactory : Microsoft.Exchange.TextMessaging.MobileDriver.TextMessagingDeliveryAgentFactory
AssemblyPath          : C:\Program Files\Microsoft\Exchange Server\V15\bin\Microsoft.Exchange.MobileDriver.dll
Identity              : Text Messaging Delivery Agent
IsValid               : True
ObjectState           : New


                                                                                                                      

Open in new window

0
Don't lose your head updating email signatures!

Do your end users still have the wrong email signature? Do email signature updates bore you or fill you with a sense of dread? You can make this a whole lot easier on yourself by trusting an Exclaimer email signature management solution. Over 50 million users do...so should you!

 
LVL 4

Expert Comment

by:milikad
ID: 39788160
They are default agents and do not stop them. Please continue with the rest plan suggested.
0
 

Author Comment

by:TripapHoniC
ID: 39788450
Tried your second suggestion with changing the security settings in the connector and the copier said authentication failed.
0
 

Accepted Solution

by:
TripapHoniC earned 0 total points
ID: 39798584
Exchange Server 2013 Cumulative Update 1 resolved the issue where Receive Connectors for devices such as scanner copiers and other multi-function machines were scanning to email and attaching plain text rather than a PDF.  Since, at the time of this problem, we're already at Cumulative Update 3, installing it corrected this issue.

The following settings I used for the Receive Connector.

Scoping
Remote Network Settings is whatever IP of the device you'll be sending from
Network adapter bindings would be set to (All Available IPv4)

Security
No Authentication
Anonymous users under Permissions group

I also set the Receive Connector in Exchange 2013 ECP to no authentication and Anonymous Users.
0
 

Author Closing Comment

by:TripapHoniC
ID: 39809843
No one else was able to resolve my issue.  I researched the problem and found the resolution on my own.
0

Featured Post

IT, Stop Being Called Into Every Meeting

Highfive is so simple that setting up every meeting room takes just minutes and every employee will be able to start or join a call from any room with ease. Never be called into a meeting just to get it started again. This is how video conferencing should work!

Join & Write a Comment

Resolve DNS query failed errors for Exchange
Exchange server is not supported in any cloud-hosted platform (other than Azure with Azure Premium Storage).
In this video we show how to create a User Mailbox 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 Recipients >> Mailb…
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…

743 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

Need Help in Real-Time?

Connect with top rated Experts

15 Experts available now in Live!

Get 1:1 Help Now