MDN Test fails

[zdavatz]

1. Sending this EDIFACT order

   UNA:+.? '
   UNB+UNOC:1+4399901494343+4251800100001+240306:1044+0239++++++1'
   UNH+2+ORDERS:D:96A:UN:EANCOM'
   BGM+220+BS3012078648B++AF'
   DTM+137:20240125:102'
   NAD+BY+4399901494343::9'
   NAD+IV+4399901494343::9'
   NAD+SU+4251800100001::9'
   CUX+2:EUR:9'
   LIN+10++4010222234821:EN'
   PIA+1+3RT3243-4VC30:VP'
   IMD+F++:::3RT3243-4VC30'
   QTY+21:3:PCE'
   DTM+2:20240125:102'
   PRI+AAA:11.44:PU'
   UNS+S'
   UNT+15+2'
   UNZ+1+0239'

2. Response is MDN does not contain AS2-From AS2-To header(s). MDN for - Message ID: <FEGIME-TEST#janico#852_txp00010_119271.dat#196015907649570@server
3. Die MDN Antwort sollte so aussehen

   
   Date=Fri, 23 Feb 2024 10:03:55 GMT
   Message-ID=<431831529101708682635977.SEEBURGER@SCM-QAS-PE1>
   Subject=Message Disposition Notification
   Content-Type=multipart/report; report-type=disposition-notification
   AS2-From=SupplyOnAS2Q
   AS2-Version=1.2
   AS2-To=FEGIME-TEST
   EDIINT-Features=multiple-attachments
   Connection=close
   Server=BIS
   Set-Cookie=dkru6wn1=3197224970.29976.0000; path=/; Httponly; Secure
   Set-Cookie=cdc=8791147; Path=/; Domain=[supplyon.com](http://supplyon.com/); Secure; Httponly; SameSite=None
   Strict-Transport-Security=max-age=16070400; includeSubDomains
   Content-Length=1915

------=_Part_83857_776860852.1708682635977 Content-Type: multipart/report; report-type=disposition-notification; boundary="----=_Part_83856_152994795.1708682635959"

------=_Part_83856_152994795.1708682635959 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: binary

The message you sent on "Fri, 23 Feb, 2024 11:03:55 +0100" from "FEGIME-TEST" to "SupplyOnAS2Q" with subject "SO_INVOIC" has been received successfully on 23 Feb 2024 10:03:55 GMT and will be further processed.

------=_Part_83856_152994795.1708682635959 Content-Type: message/disposition-notification Content-Transfer-Encoding: binary

Reporting-UA: 10.200.145.190; SEEBURGER AS2 Communication Original-Recipient: rfc822; SupplyOnAS2Q Final-Recipient: rfc822; SupplyOnAS2Q Original-Message-ID: FEGIME-TEST#SupplyOnAS2Q#850_txp00010_116069.dat#541732110686954@server Disposition: automatic-action/MDN-sent-automatically; processed Received-content-MIC: VstSgGsqpM9AmkPdNDUiftI/H9U=, sha1

------=_Part_83856_152994795.1708682635959--

------=_Part_83857_776860852.1708682635977 Content-Type: application/pkcs7-signature; name=smime.p7s; smime-type=signed-data Content-Transfer-Encoding: binary Content-Disposition: attachment; filename="smime.p7s" Content-Description: S/MIME Cryptographic Signature

[zdavatz]

Jetzt kommt die Meldung: Read timed out , FileID: 79ea3e2c821d6f84e66fe6f8546db7d0, MessageID: FEGIME-TEST#janico#853_txp00010_119271.dat#205616306308625@server

[zdavatz]

Mein Test mit Curl: curl -k -X POST -H 'AS2-FROM:aaa' -H 'AS2-TO:aaa' -H 'MESSAGE-ID:aaa' -T 2024-03-11_134755 -v https://test.yopenedi.ch/as2

ergibt

-------mdnboundarystring1
Content-Type: text/plain
Content-Transfer-Encoding: 7bit

MDN for -
 Message ID: aaa
  From: "aaa"
  To: "aaa"
  Received on: 2024-03-11T12:54Z
 Status: processed
 Comment: This is not a guarantee that the message has
  been completely processed or &understood by the receiving
  translator

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

Reporting-UA: YOpenedi
Original-Recipient: rfc822; aaa
Final-Recipient: rfc822; aaa
Original-Message-ID: aaa
Received-content-MIC: OUnGZ2t/KJ/hSiwoviQBicyvgdU=, sha1
Disposition: automatic-action/MDN-sent-automatically;
  processed

[zdavatz]

Es hat geklappt!