Re: FTP actual delivery confirmation

[Mike Wills <mike@xxxxxxxxxxxx>]

I use it to check for error codes. It works well.

--
Mike Wills
http://mikewills.me

Sent from my mobile

On Nov 2, 2011, at 10:33 AM, "rob@xxxxxxxxx" <rob@xxxxxxxxx> wrote:

> I've not used it, but does this tell you what confirmation messages may be
> received?
> http://www.scottklement.com/ftpapi/
>
>
> Rob Berendt
> --
> Group Dekko
> Dept 1600
> Mail to:  2505 Dekko Drive
>          Garrett, IN 46738
> Ship to:  Dock 108
>          6928N 400E
>          Kendallville, IN 46755
> http://www.dekko.com
>
>
>
>
>
> From:   jmoreno@xxxxxxxxxxxxxxxx
> To:     midrange-l@xxxxxxxxxxxx,
> Date:   11/02/2011 10:10 AM
> Subject:        FTP actual delivery confirmation
> Sent by:        midrange-l-bounces@xxxxxxxxxxxx
>
>
>
> Hello group,
>
> Is it possible to get an actual delivery confirmation of an FTP function
> after I have delivered IFS files to a remote location?
> Can this be achieved in a single command stream?
>
> We had an incident were the remote location effectively responded the PING
>
> but the documents were lost.
> At the moment our Batch FTP outbound process only checks for an abnormal
> error of the plain FTP command.
>
> Would it be sufficient and reliable to inspect the verbose of the FTP
> Output?
>
> Just wondering and looking for your assistance.
>
> Thanks in advance for your answers and recommendations
>
>
>
> Jorge Moreno
> Military Car Sales, Inc
> Woodbury, New York
>
> This email, including its attachments, may contain information that is
> confidential and may be protected by federal and/or state laws and
> regulations, or other confidentiality privileges. This email, including
> its attachments, may contain non-public information, therefore it is
> intended to be conveyed only to the designated recipient(s). If you are
> not an intended recipient, please delete this email, including its
> attachments, and notify the sender. The unauthorized use, dissemination,
> distribution or reproduction of this email, including its attachments, is
> prohibited and may be unlawful.
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
>
>
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.