MDN is not signed error

Trying to send a functional ack aback to my trading partner and get the following message. Does this mean the TP is not signing the MDN?

[Jan 5, 2017 3:00:05 PM] 0A40170315970378C64000006E1B3490@SPSCommerce: Inbound MDN is not signed.
[Jan 5, 2017 3:00:05 PM] 0A40170315970378C64000006E1B3490@SPSCommerce: Inbound transmission is a MDN [SPSCommerce - Cas].
[Jan 5, 2017 3:00:05 PM] 0A40170315970378C64000006E1B3490@SPSCommerce: Inbound MDN is the answer to AS2 message "mendelson_opensource_AS2-1483646405309-12@CasAS2_SPSCommerce".
[Jan 5, 2017 3:00:05 PM] 0A40170315970378C64000006E1B3490@SPSCommerce: Inbound MDN state is [processed/error: unexpected-processing-error].
[Jan 5, 2017 3:00:05 PM] 0A40170315970378C64000006E1B3490@SPSCommerce: Inbound MDN details received from SPSCommerce: "This MDN response message is for:
Message id:
From: Casd
Date received: Thu, 05 Jan 2017 20:00:05 GMT"

Forum
AS2

Comments

Permalink

Yes, but that's not the problem. MDN can be signed or not, you can configure the partner to have signed or unsigned MDN.
The fourth line anyway says that the message you sent hasn't been accepted by your partner.
"[processed/error: unexpected-processing-error]" is something that happened on the other side. You must ask them what it means. It's not a problem in your station.

Permalink

I told them that initially. definitely on their end, but they deny. Oh well. I changed the AS2-to ID to another ID and it works. They apparently have multiple partnerships and the one isn't set up properly.

One final question, I am getting "MDN seems not to be in right format. Missing header value "as2-to." Ive seen different posts concerning this error but nothing seem applicable to my configuration. Everything looks correct. Not sure what else to look at and this is Amazon.com so Im not sure they will change anything on their side. Any ideas on what might be the cause of this or what I can look for?

Permalink

Jan 6, 2017 2:40:32 PM] mendelson_opensource_AS2-1483731631898-5@ThamesAS2_SN1T2Y7AO1Z3QK: Sending AS2 message to http://as2.amazonsedi.com/e3fcfdf9-fe98-4006-ba90-3f47f11274eb, sync MDN requested.
[Jan 6, 2017 2:40:32 PM] mendelson_opensource_AS2-1483731631898-5@ThamesAS2_SN1T2Y7AO1Z3QK: Message sent successfully (HTTP 200); 3.71 KB transfered in 537ms [6.91 KB/s].
[Jan 6, 2017 2:40:32 PM] mendelson_opensource_AS2-1483731631898-5@ThamesAS2_SN1T2Y7AO1Z3QK: The received sync MDN seems not to be in right format. Missing header value "as2-to".
[Jan 6, 2017 2:40:32 PM] mendelson_opensource_AS2-1483731631898-5@ThamesAS2_SN1T2Y7AO1Z3QK: Message payload stored to "C:\mendelson\opensource\as2\messages\Amazon046\error\Thames\20170106\AS2Message5894322210851293681.as2".
[Jan 6, 2017 2:40:32 PM] mendelson_opensource_AS2-1483731631898-5@ThamesAS2_SN1T2Y7AO1Z3QK: Raw outgoing message stored to "C:\mendelson\opensource\as2\messages\Amazon046\error\Thames\20170106\raw\error8890091728423010263.raw".

Permalink

OK thank you both for the help.

So, service, what is my fix here? Amazon accounts for a large number of my edi trading partners. Id like to use Mendelson for them if possible.

Permalink

yes, this is a problem. Mendelson AS2 seems to be incompatible with Amazon's software. "service" will reply saying that the other side must update their software (read my post about the b49 bug). There is not even support for those who wants to edit the sources to fix this kind of problems (read my post about recompiling sources). So the better option for you is to look for another product.

Profile picture for user service
Permalink

albertom,

Thank you for your help, albertom - but just want to clarify some issues.
As already mentioned: There is no such bug in b49, it just sets the algorithm protection attribute which is highly recommended, please have a look at RFC 6211 from 2011 (https://tools.ietf.org/html/rfc6211). There is beneath that no known incompatibility between amazons AS2 and mendelson AS2?

The problem with the unsigned MDN of the thread opener results of an internal server error of the partner - it this case it seems to chose an error path that returns an unsigned MDN.

Regards