In no way should a client sending mail need a client side certificate.
But send me a link to the docs that state that if you find it.


Okay, here's a link:

http://www-01.ibm.com/support/docview.wss?uid=nas8N1018618

Part 1: Assigning a Digital Certificate to the SMTP Client...

The certificate that is assigned to the IBM i SMTP Client must be a "server
certificate" - not a "client certificate", and the certificate must be
signed (self-signed is okay).

I've run a number of test while sending mail through the
smtp-relay.gmail.com host, and can positively assert that when TLS
encryption is configured as "required" at the Gmail host, the SMTP Client
must present the certificate, and present account+password credentials.

These are the smtp-relay.gmail.com host requirements. Otherwise the host
reports error text in the communications trace.

You can "require TLS" for your mail relay with google, but that's on the
server side, optional, and using the gmail relay is really just a
workaround (ie quick bandaid) for using the proper mail router for your
organization when your email client can't handle authentication and/or
SSL/TLS.


Gmail relay is a workaround? A quick bandaid? Why would Google recommend it
over their other options?

https://support.google.com/a/answer/176600?hl=en

What is a "proper mail router"?

HTH,

Nathan.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.