AS2 transfers can have more than a simple success or failure outcome. For example, an outbound AS2 file transfer may succeed, but no MDN is received from the remote host. This could be considered an outright failure in some cases. Another example may include a successful file send followed by MDN received, but the received MDN’s signature cannot be verified. Some AS2 systems do not consider these failures as an overall failure, but others will. For example, a remote host may accept an inbound file and log that the signature is bad, yet still accept the file. Likewise, EFT Server by default accepts most AS2 transmissions, even if there is a MIC mismatch or the signature used to sign the payload was not found; however, the overall transaction is not considered a success unless every part of the transmission succeeds.
EFT Server always rejects inbound unencrypted transmissions over plaintext HTTP protocol, and upload attempts to a folder to which the user has no write permissions. EFT Server considers these overall permanent failures.