Re: Email sending problem -- any Google Relay experts here? -- MIDRANGE-L

I can appreciate "rolling your own" but MMAIL isn't rolling your own
either. It's just a simple wrapper for the QtmmSendMail API as are most
"free" solutions. Many articles (some written by me) were published back
in the day showing how to use that API... That's a reason it's popular to
use. But it relies on the IBM SMTP server and MSF as well. My solution
does not and is scalable when OAuth is required.

I know people think email is simple, but it's not. And I know for some
reason my software rubs you the wrong way, but it's ok if you don't reply
with your negative responses once in a while. I know you're paying a 3rd
party service to get around a lot of these issues too... I provide a
native one for less than a cup of coffee a day.

On Tue, Oct 18, 2022 at 6:28 AM Rob Berendt <rob@xxxxxxxxx> wrote:

Brad,
I think James is really into rolling his own. For example, he even writes
his own terminal emulation versus iACS. Often because he likes to bundle
such stuff into his own product. Using another vendor supplied product
complicates software distribution. So, don't be frustrated if he doesn't
bite that bait.

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
Brad Stone
Sent: Monday, October 17, 2022 6:25 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: Email sending problem -- any Google Relay experts here?

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.

<Vendor>
From this link:
https://fieldexit.com/forum/display?threadid=425

Sending to Gmail with MAILTOOL is as easy as this:
MAILTOOL TOADDR(MauriceMoss@xxxxxxxxxxxxx) FROMADDR(bvstone@xxxxxxxxxxxx)
SUBJECT('Info for Weekend')
MESSAGE('Hi, are you and Roy making it this weekend?')
SENDWITH(*MAILTOOL)
MAILRTR(SMTP.GMAIL.COM) USERTR(*ONLY) SSL(*TLS) PORT(587)
AUTHUSER(bvstone@xxxxxxxxxxxx) AUTHPW(<password>) DEBUG(*YES)

If you set up a config file, it's even cleaner (and easier to change items
like passwords, etc without having to change parameters in your command)
MAILTOOL TOADDR(MauriceMoss@xxxxxxxxxxxxx)
SUBJECT('Info for Weekend')
MESSAGE('Hi, are you and Roy making it this weekend?')
CONFIG('/bvstools/bvstools_test2.json')

There are many other options such as using a predefined IFS stream file as
the body, attachments, etc... but this is how easy it is to use MAILTOOL
with GMail (and Office 365) as well as ILE interfaces for all of it so you
don't have to use QCmdExc.

And, when they start to require OAuth 2.0, it's an easy transition. See
the article posted for more info on that.
</vendor>

On Mon, Oct 17, 2022 at 5:08 PM James H. H. Lampert via MIDRANGE-L <
midrange-l@xxxxxxxxxxxxxxxxxx> wrote:

On 10/17/22 4:41 AM, Rob Berendt wrote:

James,
Do all of your devices connect to gmail directly or do some of them

relay through another server?

Everything we have that goes through GMail goes directly to it. Nothing
in between but routers, firewalls, modems, &c.

Our V6 box bypasses GMail entirely, and goes straight to the recipient.

This morning, I put the MMAIL from our V6 box onto the cloud box, for
more convenient testing.

I've been informed that whatever grandfather clause we were under for
GMail has expired, and we are paying users of Google Workspace.
Accordingly, I've followed the instructions given at

<

https://www.ibm.com/support/pages/configuration-ibm-i-smtp-client-relay-email-office365-and-gmail

including setting up a Google Relay, in an attempt to bring up
mail-sending capability on the new cloud box. So far, no joy.

I've run out of ideas. I'm running out of ideas in other areas, too, and
it's depressing.

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