|
All on this thread:
Listen to Brad – his tools work!!!!!
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
Brad Stone
Sent: Wednesday, July 2, 2025 12:15 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: Emails never arrive
The problem I've seen over the past 25+ years is people get email
"working" and they don't care if it's correct or not. If it works, move on
to the next project. Things change with email (reverse DNS, new
authentication requirements, and now
ZjQcmQRYFpfptBannerStart
This Message Is From an External Sender
This message came from outside your organization.
ZjQcmQRYFpfptBannerEnd
The problem I've seen over the past 25+ years is people get email "working"
and they don't care if it's correct or not. If it works, move on to the
next project. Things change with email (reverse DNS, new
authentication requirements, and now with Office 365 the requirement to use
OAuth 2.0.. no more passwords, not even app passwords. I'm sure GMail is
next).
Then emails stops working, or only works for a few recipients, etc...
you're right, IBM's SMTP stuff is simplistic and bandaid over bandaid. And
setting it up is a cluster.
Most of these shops don't have email set up properly. Not by their own
fault. Partially, but also partially because the IBM SMTP system is so
cumbersome.
<vendor>
Yes, I sound like a broken records, but my MAILTOOL software was created to
get around this because I just got sick of dealing with SMTP on the IBM i.
I've been on this list for 30 years now and I will continue to offer what I
feel is the best solution for sending IBM i email.
It has command and ILE interfaces... works with any mail router, even OAuth
2.0 which IBM has said they will not implement. Very easy setup, lots of
documentation, FAQs, easy debugging and great support from yours truly. If
you have a question or issue, I guarantee I've seen it at least 100 times
before.
From around $1400 a year to $2000 a year per partition depending on your
requirements (and discounts for dev, test, HA/DR, etc). That's less than
most spend on coffee. Way less actually.
Do yourself a favor and check it out:
https://www.bvstools.com/mailtool
</vendor>
On Wed, Jul 2, 2025 at 12:05 PM Jack Woehr via MIDRANGE-L <
midrange-l@xxxxxxxxxxxxxxxxxx<mailto:midrange-l@xxxxxxxxxxxxxxxxxx>>
wrote:
Friends, this is happening all over, not just IBM i, but also IBM Z.
SNDSMTPEMM is simplistic, and the requirements of industrial-strengthSMTP
relays are becoming increasingly stringent.
The bottom line (at the moment) is that you can either figure all this
out, fix various configuration factors in SNDSMTPEMM, possibly find a new
SMTP relay (in house?) that can feed Comcast / Microsoft Exchange / Gmail
etc. what it eats, possibly write an SMTP sending program in PHP orPython,
keep up with changing rules promulgated by the major relayers.
Or you can stop sending email directly from the legacy server (IBM i, IBM
Z).
Seiden Group (with whom I also consult) consults on this and has been
stop-gapping for various organizations in this problem domain.
Jack Woehr
Independent Consulting Programmer
[icon] 303-847-8442<tel:303-847-8442>
[icon] jack.woehr@xxxxxxxxxxx<mailto:jack.woehr@xxxxxxxxxxx<mailto:jack.woehr@xxxxxxxxxxx%3cmailto:jack.woehr@xxxxxxxxxxx>>
[icon] http://www.procern.com/<https://www.procern.com/<http://www.procern.com/%3chttps:/www.procern.com/>>
[icon] Stay Connected!<
https://www.linkedin.com/company/procern-technology-solutions/>
[photo]
Upgrade your IT state of mind!<
https://procern.com/24-7-monitoring-itil-management/>
NON-DISCLOSURE NOTICE: This communication including any and all
attachments is for the intended recipient(s) only and may contain
confidential and privileged information. If you are not the intended
recipient of this communication, any disclosure, copying further
distribution or use of this communication is prohibited. If you received
this communication in error, please contact the sender and delete/destroy
all copies of this communication immediately.
[__tpx__]
________________________________
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx<mailto:midrange-l-bounces@xxxxxxxxxxxxxxxxxx>> on behalf of
tgarvey@xxxxxxxxxx<mailto:tgarvey@xxxxxxxxxx> <tgarvey@xxxxxxxxxx<mailto:tgarvey@xxxxxxxxxx>>
Sent: Wednesday, July 2, 2025 10:57
To: 'Midrange Systems Technical Discussion' <midrange-l@xxxxxxxxxxxxxxxxxx
Subject: RE: Emails never arrive
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.
Follow-up to emails never arriving...
I figured out how to turn on a trace to SMTP. And doing so has somehownow
allowed using the SNDSMTPEMM to WORK, but only for one of the email
addresses I've tried.
It will send to my unpath.com address but not to my personal accounts at
comcast.net.
I've tried the SPAMHAUS site and none of my IP addresses have issues.
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx<mailto:midrange-l-bounces@xxxxxxxxxxxxxxxxxx>> On Behalf Of
Brad Stone
Sent: Friday, June 27, 2025 5:42 AM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx<mailto:midrange-l@xxxxxxxxxxxxxxxxxx>>
Subject: Re: Emails never arrive
What are you using for email? If its Office 365 they don't allow
user/password authentication anymore
<vendor>
We have had a plugin for O365 and Auth 2.0 for a few years now. MAILTOOL
is the base product and G4MS (GreenTools for Microsoft) has a plugin that
allows you to set up OAuth 2.0 and have all the token processing be
transparent in the background.
Here's an article:
https://fieldexit.com/forum/display?threadid=635<<https://fieldexit.com/forum/display?threadid=635%3c>
https://fieldexit.com/forum/display?threadid=635>
MAILTOOL - https://www.bvstools.com/mailtool<<https://www.bvstools.com/mailtool%3c>
https://www.bvstools.com/mailtool> </vendor>
On Thu, Jun 26, 2025 at 10:21 AM <tgarvey@xxxxxxxxxx<mailto:tgarvey@xxxxxxxxxx>> wrote:
I apologize for bringing this up again.
I'm using SMTPSendMail (on OS v5) and the SNDSMTPEMM command (on OS
v7) to send emails with attachments from within a RPGLE program.
Reviewing the joblog indicates the emails are sent successfully (email
server engages and responds with expected messages). But emails never
arrive. This used to work a few years ago.
I've tried sending to several different domains, including personal,
business, and gmail accounts.
I've also tried this on servers that are not mine. No emails arrive.
Can someone point me in a direction to figure out why? Where else can
I look?
Kind Regards,
Thomas Garvey
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
MIDRANGE-L@xxxxxxxxxxxxxxxxxx> Tolist To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx<mailto:
subscribe, unsubscribe, or change list options,
https://lists.midrange.com/mailman/listinfo/midrange-l%3c>visit: https://lists.midrange.com/mailman/listinfo/midrange-l<<
https://lists.midrange.com/mailman/listinfo/midrange-l>
MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx>or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx<mailto:
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l%3c>https://archive.midrange.com/midrange-l<<
https://archive.midrange.com/midrange-l>.
support@xxxxxxxxxxxxxxxxxxxx> for any subscriptionPlease contact support@xxxxxxxxxxxxxxxxxxxx<mailto:
related questions.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx<mailto:MIDRANGE-L@xxxxxxxxxxxxxxxxxx> To subscribe,
unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l<<https://lists.midrange.com/mailman/listinfo/midrange-l%3c>
https://lists.midrange.com/mailman/listinfo/midrange-l>
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx<mailto:MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx>
Before posting, please take a moment to review the archives at
https://archive.midrange.com/midrange-l<<https://archive.midrange.com/midrange-l%3c>
https://archive.midrange.com/midrange-l>.
Please contact support@xxxxxxxxxxxxxxxxxxxx<mailto:support@xxxxxxxxxxxxxxxxxxxx> for any subscription related
questions.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailinglist
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx<mailto:MIDRANGE-L@xxxxxxxxxxxxxxxxxx>
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l<<https://lists.midrange.com/mailman/listinfo/midrange-l%3c>
https://lists.midrange.com/mailman/listinfo/midrange-l>
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx<mailto:MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx>
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l<<https://archive.midrange.com/midrange-l%3c>
https://archive.midrange.com/midrange-l>.
Please contact support@xxxxxxxxxxxxxxxxxxxx<mailto:support@xxxxxxxxxxxxxxxxxxxx> for any subscription related
questions.
Jack Woehr
Independent Consulting Programmer
303-847-8442
jack.woehr@xxxxxxxxxxx<mailto:jack.woehr@xxxxxxxxxxx>
http://www.procern.com/
Stay Connected!
Upgrade your IT state of mind!
NON-DISCLOSURE NOTICE: This communication including any and all
attachments is for the intended recipient(s) only and may contain
confidential and privileged information. If you are not the intended
recipient of this communication, any disclosure, copying further
distribution or use of this communication is prohibited. If you received
this communication in error, please contact the sender and delete/destroy
all copies of this communication immediately.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailinglist
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx<mailto: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<mailto: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<mailto: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<mailto:
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<mailto:
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<mailto:
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.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.