|
James,
I noticed your thread at the IBM i Community.
I want to say that IBM ships a bunch of certs on the system. They're just
not populated into the CA Store. Follow these simple steps:
Go into New Navigator.
Bookmarks
IBM Digital Certificate Manager for i
Open or Create the *SYSTEM store
"Populate with CAs"
Simple as pie!
Here's where I first ran into this:
https://www.linkedin.com/feed/update/urn:li:activity:6920461817680990208?utm_source=share&utm_medium=member_desktop
Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 7310 Innovation Blvd, Suite 104
Ft. Wayne, IN 46818
Ship to: 7310 Innovation Blvd, Dock 9C
Ft. Wayne, IN 46818
http://www.dekko.com
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
James H. H. Lampert via MIDRANGE-L
Sent: Friday, October 14, 2022 4:40 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Cc: James H. H. Lampert <jamesl@xxxxxxxxxxxxxxxxx>
Subject: Email sending problem
CAUTION: This email originated from outside of the organization. Do not
click links or open attachments unless you recognize the sender and know
the content is safe.
We currently have applications on our V6 box (most notably, the back-end
of our self-service license authorization code webapp) that send email
using QtmmSendMail. Our V6 box is set up with MAILROUTER(*NONE), and I'm
pretty sure I did something with DMARC setup, over a year ago (and I
don't remember what I did, or how).
And we're moving an application with email capability over to a cloud
V7R5 box (the same one that's been giving me problems with TLS for
iNav), on which SMTP is not set up *at all.*
Our email provider is GMail. For years, List members have been telling
me that MAILROUTER(*NONE) is a bad idea, but there wasn't much I could
do about it from a V6 box.
What do I need to do, and where can I learn how to do it?
--
JHHL
--
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.
Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.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.
Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com
As an Amazon Associate we earn from qualifying purchases.
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.