× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



You still have the option to use app passwords with gmail and outlook, but
I imagine that will go away sometime too.

Jeff's issue is that he has ESEND in hundreds or thousands of places. It
would be quite an undertaking to switch to any other command/product. But
I guess without more details on the current relay (and what it uses for
authentication, if any) it's hard to say. I would think it would user/pw
authentication and that means the PW portion could be replaced to use an
app password generated from Gmail.

I think in this case maybe it's using the gmail relay (smtp-relay.gmail.com
or something) that was proposed a few years ago on this list by someone
(and which I am sure I said was a bad idea). The gmail relay was set up
for things like printers, etc that don't have a real interface or could use
any authentication.

I'm sure there's a solution, such as overriding the command processing
program for ESEND to use something else for example.

<vendor>
MAILTOOL has had the option to send email with OAuth 2.0 for years now.
But even if you're already using MAILTOOL Plus it's an easy transition to
OAuth 2.0 which is what they recommend.

If you do try the option overriding of the ESEND command processing program
MAILTOOL and the OAuth applications (G4G for google and G4MS for office
365) have ILE functions that can be used. They also allow the use of
config files for settings, so that could be fairly easy to put all the
authentication items in the config file leaving your commands as they are.
</vendor>

On Wed, Jul 10, 2024 at 12:00 PM Jeff Crosby <jlcrosby@xxxxxxxxxxxxxxxx>
wrote:

See this blog post.


https://workspaceupdates.googleblog.com/2023/09/winding-down-google-sync-and-less-secure-apps-support.html

Google did this with @gmail.com addresses a couple of years ago and, as
Brad Stone predicted at the time, they are now doing it for google
workspace users.

We are HEAVY users of ESEND (Fortra, formerly HelpSystems) which uses the
IBM i SMTP server to send hundreds of emails a day for us via gmail SMTP
relay. I assume this will affect that relay, though I don't know that
for a fact. The time is short enough that I could not begin to do
something else.

I contacted Fortra/HelpSystems a couple of years ago when it first happened
to the @gmail.com addresses and they told me to contact IBM. Yea, right.

Years ago (before we figured out how to use outbound port 587 on the IBM i
SMTP server) we used a program on a local Windows system to perform the
relay into gmail. The IBM i pointed all email to this system which
then sent it to google. That software was cleverly named Email Server and
no longer exists.

Suggestions? Is there a relay service out there I could use? I would
prefer that as opposed to installing something on a local desktop. Or
(best case scenario) something installed on the IBM I itself to perform the
relay from the IBM i SMTP server.

Thanks.


--


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



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.