Re: SNDDST / Send Email fails on Certificate error

Thanks Don for confirming what I expected.
Anyway good to know as we are due to upgrade to V7R3, although from V7R1.

I have never come across a signed server certificate without associated CAs.
If that were the case then the client should just reject the
certificate so bit of a puzzle why it was working previously.


On 25 June 2017 at 16:32, Bradley Stone <bvstone@xxxxxxxxx> wrote:

I would be curious where they got the certificate from... very odd
there are no CAs associated with it. Is that what a self-signed
certificate looks like from another platform?

I've seen one other like it on an FTP server. Importing it to the
*SYSTEM store solved that problem, so I didn't pursue things any
further. :)

Bradley V. Stone
www.bvstools.com
Native IBM i e-Mail solutions for Microsoft Office 365, Gmail, or any
Cloud Provider!


On Sun, Jun 25, 2017 at 8:03 AM, Don Brown <DBrown@xxxxxxxxxx> wrote:

Thanks Keith,

But it appears DCM was not set up at R610.

Which makes this error even more difficult to understand.

An OS upgrade will not remove any certificates or remove the system store.

And the certificates on the Exchange server are not new so how did it work
previously - Great question!!

Thanks

Don Brown




From: Keith McCully <keithmccully@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 25/06/2017 07:44 PM
Subject: Re: SNDDST / Send Email fails on Certificate error
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



Going back to Don's original post he mentioned that everything was
working fine until the V7R3. Wouldn't the DCM configuration data
normally be retained from the previous release unless explicitly
removed?

Or does it always have to be reinstalled on upgrade?
--