Re: Goggle and LSA (less secure apps) -- MIDRANGE-L

Not my family. One of the tech's family.

We use port 587 outbound with no SSL/TLS. It's originating IP address
authentication.

I went into the IBM case and found this:

<snip>
Aug 16, 2024, 09:59

Tried to import certificate for sendgrid as " server" or client. This
results in error "No request key found"

https://www.ibm.com/support/pages/no-request-key-found-error-when-importing-certificate-dcm

Indicates the clent certificate must be in PKCS #12 format. The only way to
get this format is with the certificate and the private key. There is no
way we will ever obtain the private key from sendgrid.

</snip>

That IBM support page says:

<snip>

"No request key found" error when importing a certificate in DCM
Troubleshooting

Problem
In DCM, importing a server certificate fails with the message: No request
key found.

Resolving The Problem
Problem: When importing a server certificate from a third party in DCM, the
import fails with the message "No request key is found for the certificate.
If you are trying to receive the signed certificate, you must be using the
same certificate store that was used when the certificate was requested. If
this is a CA certificate, you should use the function for importing a CA."
Solution: This typically means the user is importing a certificate which
did not originate from a CSR (Certificate Signer Request) that was created
on this system in this store. The only certificate formats that will import
on the System i without an outstanding certificate request are IBM System i
proprietary format and PKCS#12 (.pfx, .p12) format.

Historical Number
538535302

</snip>

If SMTP2GO ever does get to requiring TLS and together we (Dilgard and
SMTP2GO) can't get the cert in properly, you'll be the first contact. :)

On Thu, Sep 12, 2024 at 1:29 PM Brad Stone <bvstone@xxxxxxxxx> wrote:

For your situation that was probably the best choice since all you probably
had to do was change the SMTP server in IBM's SMTP setup. I imagine you're
using port 25 and no SSL or TLS between your IBM i and SMTP2GO. If I
recall your main issue was you didn't want to change 100s of programs.

The SSL certificate for the other service could have been solved very
quickly. I could have helped with that. No, you don't need a private key
or client certificate. You need to import the CAs that their service uses
(since it appears they require SSL or TLS.) Or, an email application that
can ignore "not trusted" errors (like MAILTOOL can).

Glad you found something. I hope that they aren't required to remove non
secure communications in the future.. but at least for now things are
swell.

So sorry to hear about the accident. Prayers with you and your family.

On Thu, Sep 12, 2024 at 12:19 PM Jeff Crosby <jlcrosby@xxxxxxxxxxxxxxxx>
wrote:

To bring closure to this old thread.

We ended up going with SMTP2GO and it's working as of this morning.

Why did it take this long? Initially we were going to use SendGrid, but

we

couldn't get the certificate imported. Even with IBM help. If we
understood the IBM guy correctly we needed the private key.

Then, at that point, a horrific thing took place. A head on crash
involving 3 relatives of 1 of the 3 people from another company working

on

this with me. A brother is paralyzed from the neck down, sister-in-law

is

in rehab, and a niece (in her 40's) was pronounced dead at the scene.

This

email issue definitely took a back seat for quite some time.

Since the end of September (the deadline) was getting close, I

investigated

SMTP2GO and we got it up and going in 2 days. We have a complete

dashboard

and log of every email. I had to contact SMTP2GO tech support this

morning

and had a response with the correct answer in 6 minutes.

On Fri, Jul 12, 2024 at 4:05 PM Brad Stone <bvstone@xxxxxxxxx> wrote:

It could also be AI, or part AI. From the emails I get from them on an
invoice that I have cancelled I ask them to provide contact with

someone

higher up. It gets forwarded to the same person and then nothing.

Then

I

get another reminder... rinse, repeat over and over.

It's very frustrating.

On Fri, Jul 12, 2024 at 2:59 PM Patrik Schindler <poc@xxxxxxxxxx>

wrote:

Hello Jeff,

Am 12.07.2024 um 19:54 schrieb Jeff Crosby <

jlcrosby@xxxxxxxxxxxxxxxx

:

"Deprivated?"

I presume "Shaik" is not a native English speaker.

It's a nuisance that support people often don't understand the

culprit.

Not because they're dumb but because of "language gap". But the

underlying

problem is that those "front row indians" are much cheaper than

support

staff in the US. More money left for the shareholders, and customers

have

bought the product already anyway…

Don't get me wrong, I'm not racist. But people in jobs needing to
communicate with cutomers should have a thorough understanding of the
language in which they're supposed to listen and talk. And this is

IMO

not

a fault of those people.

--
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.

--

*Jeff Crosby*
Senior Vice President
UniPro FoodService/Dilgard
P.O. Box 13369
Ft. Wayne, IN 46868-3369
260-422-7531
direct.dilgardfoods.com

The opinions expressed are my own and not necessarily the opinion of my
company. Unless I say so.
--
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.

--
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.