Working with Cleo VL Trader

daymon,
I have no idea about
daymon,
I have no idea about this issue so far. Maybe it's a problem of a missing header or something like this the receiver requires. A good idea to analyze this would be to compare a working message with a message m-e-c as2 has created.
If you like to you could send me these information and I will have a look at it.
sh at mendelson dot de
Regards
Heller
© 1999-2008 mendelson-e-commerce GmbH. All right reserved.
Hi all:
I've been able to get mec as2 running for the most part. Using a P3 500MHz with Debian and it runs at an acceptable speed. I have however, run into a problem communicating
with another party running Cleo VL Trader 3.4. The files we send to each other get to their destinations, but I keep receiving an HTTP 204 message from the other end when the system tries to send the MDN.
[5:39:35 PM] mec_as2-1218058774233-6@xxxxxxxxxxx_ACTIVANT3: Sending async
MDN to http://idx3.xxxxxxnet.net:32002/as2.
[5:39:39 PM] mec_as2-1218058774233-6@xxxxxxxxxxx_ACTIVANT3: Transmission
failed, remote AS2 server reports "No Content".
[5:39:39 PM] mec_as2-1218058774233-6@xxxxxxxxxxx_ACTIVANT3: HTTP 204
[5:39:39 PM] mec_as2-1218058774233-6@xxxxxxxxxxx_ACTIVANT3: Raw outgoing
message stored to
"/home/bin/mec-as2/messages/IDX/error/20080806/raw/error45349.raw".
The result being: Outgoing documents are considered "unsent" and
incoming documents stay in the "Pending" folder instead of the In box.
According to my contact one the other end, a 204 message is not really an error in the strictest sense.
10.2.5 204 No Content
The server has fulfilled the request but does not need to return an
entity-body, and might want to return updated metainformation. The
response MAY include new or updated metainformation in the form of
entity-headers, which if present SHOULD be associated with the
requested variant.
If the client is a user agent, it SHOULD NOT change its document view
from that which caused the request to be sent. This response is
primarily intended to allow input for actions to take place without
causing a change to the user agent's active document view, although
any new or updated metainformation SHOULD be applied to the document
currently in the user agent's active view.
The 204 response MUST NOT include a message-body, and thus is always
terminated by the first empty line after the header fields.
Any tweaks out there to get this work?
TIA
D