Re: Secure connection error, return code 6000 (FTP)

[Brad Stone <bvstone@xxxxxxxxx>]

They haven't done anything for 20+ years about it.  I was happy to find
that you could bypass this if you're using the APIs yourself as I did with
GETURI and MAILTOOL...

IBM should do the same (simple yes/no flag to ignore not trusted errors).
That would be at least a step further for them.  I even think Scott Klement
has code out there in HTTPAPI and other stuff to ignore the "not trusted"
errors, so there's no excuse not to do it.

On Mon, Mar 30, 2026 at 7:35 AM Greg Wilburn <
gwilburn@xxxxxxxxxxxxxxxxxxxxxxx> wrote:

> I know there was a lengthy discussion about this a while back.
>
> We have a hosted FTP server that is used extensively by our processes.
> The wheels fell off this weekend (again) because the certificate updated,
> and is not trusted in our DCM.
>
> What, if anything, is IBM doing about this?  This is not an issue in the
> PC world.
> This is only getting worse with the rapid expiration of certs.
>
> Greg
>
>
>
> [Logo]<https://www.totalbizfulfillment.com/>    Greg Wilburn
> Director of IT
> 301.895.3792 ext. 1231
> 301.895.3895 direct
> gwilburn@xxxxxxxxxxxxxxxxxxxxxxx<mailto:gwilburn@xxxxxxxxxxxxxxxxxxxxxxx>
> 1 Corporate Dr
> Grantsville, MD 21536
> www.totalbizfulfillment.com<http://www.totalbizfulfillment.com>
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: https://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at https://archive.midrange.com/midrange-l.
>
> Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
> questions.