Skip to main content

Invalid or Badly Formatted MDN

Typically, the content of a returned MDN is formatted as a Multipart MIMEExternal LinkThis link leads to an external website and will open in a new tab, wrapped in an encrypted and signed file.

Files.com AS2 will automatically attempt to decrypt the file and verify its signature. If the decryption succeeds, you will be able to view the contents of the MDN in the AS2 Logs.

A correctly formatted MDN will look like this:

------7F351D7B2DF82DAA639F0F4BAF1126B2
Content-Type: multipart/report; report-type=disposition-notification; boundary="----=_Part_1_20231005223333321"


------=_Part_1_20231005223333321
Content-Type: text/plain
Content-Transfer-Encoding: 7bit

The AS2 message has been received successfully

------=_Part_1_20231005223333321
Content-Type: message/disposition-notification
Content-Transfer-Encoding: 7bit

Reporting-UA: YOUR_AS2_PARTNER
Original-Recipient: rfc822; YOUR_AS2_PARTNER
Final-Recipient: rfc822; YOUR_AS2_PARTNER
Original-Message-ID: <YOUR_AS2_PARTNER-20231005223330@mysite.files.com>
Disposition: automatic-action/MDN-sent-automatically; processed
Received-Content-MIC: WoWTby7qm+yTTydEWhG9Um7llknPrWCTNiSUvnOOROM=, sha-256

------=_Part_1_20231005223333321--

------7F351D7B2DF82DAA639F0F4BAF1126B2
Content-Type: application/x-pkcs7-signature; name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="smime.p7s"

MIIHBwYJKoZIhvcNAQcCoIIG+DCCBvQCAQExDzANBglghkgBZQMEAgEFADALBgkq
hkiG9w0BBwGgggPyMIID7jCCAtYCCQCfMq8S3SzAkTANBgkqhkiG9w0BAQsFADCB
uDELMAkGA1UEBhMCVVMxEzARBgNVBAgMCkNhbGlmb3JuaWExETAPBgNVBAcMCFZh
bGVuY2lhMRIwEAYDVQQKDAlGaWxlcy5jb20xEDAOBgNVBAsMB1Byb2R1Y3QxLjAs
BgNVBAMMJWNsYXVkaW9mb3VyLmFzMi5jbGF1ZGlvdGVzdC5maWxlcy5jb20xKzAp
BgkqhkiG9w0BCQEWHGNsYXVkaW8udGlubmlyZWxsb0BmaWxlcy5jb20wHhcNMjMw
NjAxMTg0NTU4WhcNMjQwNTMxMTg0NTU4WjCBuDELMAkGA1UEBhMCVVMxEzARBgNV
BAgMCkNhbGlmb3JuaWExETAPBgNVBAcMCFZhbGVuY2lhMRIwEAYDVQQKDAlGaWxl
cy5jb20xEDAOBgNVBAsMB1Byb2R1Y3QxLjAsBgNVBAMMJWNsYXVkaW9mb3VyLmFz
Mi5jbGF1ZGlvdGVzdC5maWxlcy5jb20xKzApBgkqhkiG9w0BCQEWHGNsYXVkaW8u
dGlubmlyZWxsb0BmaWxlcy5jb20wggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEK
AoIBAQC7aBmHVHe5OcaFRPZytBlT4MeC0MW4+twsne+iiW4LZR6PkfNfwRYzVMCi
xDPyvfe6O7alGCXBd5jYgAI8LXTntHJlPDF3TKmQ/x7etQzFOFhaNYKD6r+0FP8l
25fHj59y6GUT9iR3W2JYFApmIle0pd540BTXvnD5mgv5FxWVJ5viB+5bAslXnH9c
Unyfcp0A+6vmmJpRK1KdiS4XTszs4J2DvgEEug3ALysEKay+zq0ysWZQB17EtNM5
/1ePR1qph6wPvyQQY5/o91r17T5gEP3QZj7Qg2O9aTwS1dbhb2JFbUJhEp/hcdbq
H9Qa1kMbQoiL5vVPFO5nWmVVwK8DAgMBAAEwDQYJKoZIhvcNAQELBQADggEBAFRH
fKW1TY5UY90+7ouf6DibX9RtBAfzOIRNrv54+ojBANaqscSMtBl08Wq+5HLrrPzg
EfqD8avf1C2eeHE3pmXACW5tVpT6S/arzx1CRP71sTIzBNhtBcWk6NxqvtwB7XLm
BL7rUMVA2oYxteHndDt6TLN7GVg85oSvz6hDIIb+bPkXf9zc9uXz8mozt4bIxuX6
F9TmcFtvy2LmZ3B8hJylYJK9zGJaT9xAed1vE6lHF0KfEpJSmBp5+nP3impcoD5M
7QCwiWLFjUNYMk1q29BdbUN5ZKbqrR3Rm6zHQgd7yqMu3iKsMWq21MiBXTT8Jq/F
rtiX+dULo0KcENpNQysxggLZMIIC1QIBATCBxjCBuDELMAkGA1UEBhMCVVMxEzAR
BgNVBAgMCkNhbGlmb3JuaWExETAPBgNVBAcMCFZhbGVuY2lhMRIwEAYDVQQKDAlG
aWxlcy5jb20xEDAOBgNVBAsMB1Byb2R1Y3QxLjAsBgNVBAMMJWNsYXVkaW9mb3Vy
LmFzMi5jbGF1ZGlvdGVzdC5maWxlcy5jb20xKzApBgkqhkiG9w0BCQEWHGNsYXVk
aW8udGlubmlyZWxsb0BmaWxlcy5jb20CCQCfMq8S3SzAkTANBglghkgBZQMEAgEF
AKCB5DAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3DQEJBTEPFw0y
MzEwMDUyMjMzMzNaMC8GCSqGSIb3DQEJBDEiBCArw1luHUS6Aagd2G2hU00/FuRp
PePJFvmMNcoQzbExDjB5BgkqhkiG9w0BCQ8xbDBqMAsGCWCGSAFlAwQBKjALBglg
hkgBZQMEARYwCwYJYIZIAWUDBAECMAoGCCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIA
gDANBggqhkiG9w0DAgIBQDAHBgUrDgMCBzANBggqhkiG9w0DAgIBKDANBgkqhkiG
9w0BAQEFAASCAQARflZ/TDf8+NNvhqae8/BOyRImwwgXpqXEZ6O3OK6tqtcy8QsZ
IP7qzqjXqv0MJWaUCDLNK2KCw7O97GITBDckQCI0gGctJLlFBkegFIwsk+MTpuaV
5mUxG/pihxx9WFpuwyx3APZxasdKmnzOncWY2qgUpUj4IqoqkynU5OJD2U9R9qi+
ub3LkvreK27WRAn9KjsRl6hTlpoFMHM5+jmyE05o4c8oaTVfjwwBDOOBMIKL4JMY
ttncgV2mgq5TxROQuxyf649bbuV5YySJjjxfOHLzTyAOYT2x2VOGEZzd9Uzryniw
W38Tzmm9oflH6+XdjnO6JptjDYM/YGismxBB

------7F351D7B2DF82DAA639F0F4BAF1126B2--

Any returned processing messages from your trading partner's system should be contained within the first segment of the multipart MIME message.

In the above example, the returned message is:

The AS2 message has been received successfully

This returned message will vary from system to system but as long as it is placed within the above multipart MIME structure then you can treat it as a valid and trusted return receipt from your trading partner.

However, when an error occurs, some AS2 or EDI systems may output their error messages into the MDN.

Instead of being correctly formatted, the MDN will contain the "raw" error message, rather than the expected multipart MIME format.

This "raw" error message can look like any typically cryptic error message that gets written to a log file.

You should send this raw error message to your trading partner so that they can troubleshoot their side of the AS2 connection, or their EDI processing system, to find the cause of the error.

Get Instant Access to Files.com

The button below will take you to our Free Trial signup page. Click on the white "Start My Free Trial" button, then fill out the short form on the next page. Your account will be activated instantly. You can dive in and start yourself or let us help. The choice is yours.