Christopher Broderick

Fix released in V4.0.0

Released in version 4.0.0 today.

There is an open issue that is the same as yours here which you c an subscribe to and I will update it when the issue is fixed: https://github.com/OpenAS2/OpenAs2App/issues/379

Many thousands are.

The file ending up in the sent dor in its binary form was inherrent in the original design of the software. Since I took over the project 13 years ago I have slowly changed some frustrating behaviour but have not got around to making it possible to store the unecrypted version of the file in the sent folder. At the moment there are other priorities but perhaps some day I weill get there. The error moving the pending MDN file is something I am aware of and will work on a fix ASAP. NOTE: It is best...

No idea what you are asking.

It looks like something is going wrong on the partner side and it is responding with a zero length content: Content-Length: 0 You can see the other rservers esponse actually contains data: Content-Length: 3318 It may be anyu one of: 1. that the certificate or AS2_ID are somehow mismatched 2. The partnership is configured for the remote end to respond using ASYNC MDN (in that situation the response from the partner to the sent AS2 message would be a zero length HTTP 200 OK and so what you are seeing...

I have logged this for tracking purposes: https://github.com/OpenAS2/OpenAs2App/issues/391