Re: Job nnnn/QMSF/QMSF stopped processing MSF message.

I've found over the years if people think email is working, they assume
it's working for everyone/every recipient. It's not something people want
to think about. Setup for IBM SMTP can be confusing, especially with the
new security requirements (and impossible with OAuth for something like
office 365).

It's why I created an alternative years ago.. almost 25 years now. I
needed it, and found others did too. :) It totally bypasses IBM's SMTP
system. Better logging, debugging, and as technologies change, so does my
solution.

On Tue, Jun 17, 2025 at 3:45 PM Michael Quigley <MichaelQuigley@xxxxxxxxxx>
wrote:

Thanks Brad! I think that will do the trick. I'll set it up to do a clear
about once a week.

I'm not really sure what the emails were that it's complaining about. So
to quit using SMTP becomes problematic. I've been seeing these messages
since the administration of the system fell to me. (Although I've done
SysAdmin work in the past, I'm actually a systems analyst. It's just that
all the trained system admins have retired or moved on to other things. I'm
really the most knowledgeable person on IBM i here.)

Thanks,
Michael Quigley
Computer Services
www.TheWay.org

-----Original Message-----
----------------------------------------------------------------------

message: 1
date: Tue, 17 Jun 2025 08:42:53 -0500
from: Brad Stone <bvstone@xxxxxxxxx>
subject: Re: Job nnnn/QMSF/QMSF stopped processing MSF message.

Once in a while start MSF with the *CLEAR option to get the unsent emails
out of the queue.

Or stop using IBM SMTP. :)

On Tue, Jun 17, 2025 at 8:21?AM Michael Quigley
<MichaelQuigley@xxxxxxxxxx>
wrote:

Every time we start up the system QSYSOPR is flooded with the message
in the subject-literally hundreds and hundreds of the messages. If I
check the joblog (which the second level text directs me to do), it
says "SMTP distribution not sent. SMTP jobs not active." The system
starts up in the wee hours of the morning, so I'm not there. I'm
thinking it's a timing issue as the server jobs are running. But it
looks like the server jobs might be starting shortly after the

messages in

QSYSOPR start getting sent.

I'm not aware of any messages sent from the system which aren't being
delivered. (I'm sure someone would reach out to me if they didn't get
something they expected.) But it would be nice to have QSYSOPR clean.

Any suggestions on how to address this situation would be greatly
appreciated.

Thanks,
Michael Quigley
Computer Services

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