Scan-To-Email PDFs Sent As MIME Type

[Llama God]

Hi,

Has anybody had issues with scanning to Exchange 2013 when the PDF attachment is displayed as, and I quote, a "MIME-type" in the main body of the email rather than as an attachment? The displayed data is gibberish, just a huge string of letters and numbers, that goes on and on.

This has suddenly started happening at a customer's site where they have a range of machines from MPc305s to Pro 907s, all of which have the same problem.

Any ideas would be most welcome!

Thanks in advance,

Chris

[rthonpm]

Check and make sure there isn't a maximum file size set on the copier for scan to email files. More than likely, the copier is breaking the scan into smaller pieces to get past the limitation. Also confirm what, if any, size limit there is on the Exchange server and set the limit a few MB below that and then set the copier to not send if the limit is reached as opposed to 'Divide and Send'.

[slimslob]

Check and make sure there isn't a maximum file size set on the copier for scan to email files. More than likely, the copier is breaking the scan into smaller pieces to get past the limitation. Also confirm what, if any, size limit there is on the Exchange server and set the limit a few MB below that and then set the copier to not send if the limit is reached as opposed to 'Divide and Send'.

I agree. The only I have ever seen mime type attachment on a scan to email is when "Divide and Send" has been.

Check with the customers IT people. If it suddenly started happening and they haven't started sending larger PDFs than before, there might have been a change to the Exchange server. Divide and send can be used with a proper configured Exchange server and outlook client, the client will reassemble the mime files back into the document or so I have read somwhere.

[Llama God]

Divide and send is set to "off" and there's no maximum email size set on the copier. Additionally, this happens when scanning a single mono sheet to a file of less than 100kb. If we scan a large document in our office and forward it to them, it goes through fine.

There have been no changes to the Exchange Server; I know this as we look after their IT. I've been told, although I haven't checked this myself, that the maximum size in Exchange is set to 15mb.

We're putting a service pack onto an image of Exchange that we've installed in the office to see whether this fixes it. Somebody found a post on the Microsoft site saying that it will, but it seems a bit hazardous.

[Llama God]

Sorry for the later reply, I'm not getting email notifications through!

[Tonerbomb]

Are all your frimwar's current??

[KenB]

I'm pretty sure that split attachments come through with a ".dat" extension.

[Llama God]

Are all your frimwar's current??

Quite possibly not.

[ApeosMan]

As soon as I saw 'MIME' it took me back to when I learned about 'S/MIME' for e-mail. This could possibly be a security issue or setting. The customer may have changed their security settings on their mail server. For more info see this:

http://en.wikipedia.org/wiki/S/MIME

[Llama God]

For reference, this is the email that comes through:

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

This E-mail was sent from "RNP0026735BA562" (Aficio MP C3002).

Scan Date: 07.01.2014 12:36:36 (+0100)
Queries to: administrator@xxxxxxxxxxx.co.uk


--DC_BOUND_PRE_<1389094596.0026734f808b>
Content-Type: application/pdf; name="201401071236.pdf"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
filename="201401071236.pdf"

JVBERi0xLjQKJeLjz9MKNCAwIG9iago8PC9UeXBlL1hPYmplY3 QKL1N1YnR5cGUvSW1hZ2UK
L1dpZHRoIDM1MDgKL0hlaWdodCAyNDgwCi9CaXRzUGVyQ29tcG 9uZW50IDgKL0NvbG9yU3Bh
Y2UvRGV2aWNlUkdCCi9GaWx0ZXIgL0RDVERlY29kZQovTGVuZ3 RoIDM4Mjg2MAo+PgpzdHJl
YW0K/9j/4AAQSkZJRgABAQEBLAEsAAD/2wBDABQODxIPDRQSEBIXFRQYHjIhHhwcHj0sLiQy
SUBMS0dARkVQWnNiUFVtVkVGZIhlbXd7gYKBTmCNl4x9lnN+gX z/2wBDARUXFx4aHjshITt8
U0ZTfHx8fHx8fHx8fHx8fHx8fHx8fHx8fHx8fHx8fHx8fHx8fH x8fHx8fHx8fHx8fHx8fHz/
wAARCAmwDbQDASIAAhEBAxEB/8QAHwAAAQUBAQEBAQEAAAAAAAAAAAECAwQFBgcICQoL/8QA
tRAAAgEDAwIEAwUFBAQAAAF9AQIDAAQRBRIhMUEGE1FhByJxFD KBkaEII0KxwRVS0fAkM2Jy
ggkKFhcYGRolJicoKSo0NTY3ODk6Q0RFRkdISUpTVFVWV1hZWm NkZWZnaGlqc3R1dnd4eXqD

etc