Re: V5R4 SMTP Authentication -- MIDRANGE-L

If Help Systems said that, then they're using the QtmmSendMail API (or
heaven forbid calling SNDDST with QCMDEXC in the background). Both which
use the IBM SMTP server. In other words, using a system that I personally
have seen maybe 50% success rate with (and the reason I wrote my tools
over 10 years ago because I needed them personally, as well as other
customers of mine).

If IBM told you that you needed to create a self-signed certificate
because gmail requires SSL for mail delivery, they are wrong and like a
lot of folks, don't understand the difference between a certificate and a
Certificate Authority (CA). Or, they understand but still get the
terminology wrong. But a self signed certificate is a completely
different ballgame and a server side function mostly used for testing, or
Client Access over SSL in some cases.

I personally have used gmail (google apps premier) for over 3 years now.
Love it. I have other customers that also switched to it and love it and
since my tools incorporate what is needed, the switch was as easy as a
couple CHGCMDDFT commands. Possibly importing Google's CA as well.

When I switched to gmail it forced me to add SSL to my MAILTOOL Plus
product (since I use it exclusively for email on the i).

I'd be curious if you tried it before you created the self signed cert.
:) And if it WAS required, then they have some wild and wacky/hack stuff
going on with their email delivery system or it was something different
all together.

Curious is:

1. ALWAUTH(*NONE). This appears to only apply to receiving emails (ie
SMTP server, not delivery). and this value says "no, I don't want to use
SSL". should have no affect on sending.. and if it did, it is saying to
not use SSL.

2. You specified the authentication user in iNav. But no where else can
this be done that I can find. Besides this, according to what you did, I
don't see anywhere where for mail delivery you changed anything to use SSL
and I "thought" was required by google apps/gmail.

Who knows.. if it works, something is set up right! :) while still
fundamentally wrong IMHO (and it's been a while since I've shared MHO on
these lists.. lol)

Bradley V. Stone
BVSTools, Inc.
[1]www.BVSTools.com
[2]www.eRPGSDK.com

Jeff Crosby wrote:

Well, Help Systems said the i SMTP server was _required_ for ESEND to work.

And IBM is the one who said I needed the certificate.

On Tue, Jun 30, 2009 at 4:59 PM, Bradley V. Stone[3]<bvstone@xxxxxxxxxxxx> wrote:

Jeff,

First, you shouldn't need to create a self-signed Certificate for google
apps email. It does use SSL, but since you are the client all you need to
do is import the CA from the cert they use into your certificate store (if
it's not there by default).

Second, iNav sounds like it has options not on the green screen then.
Interesting! The only issue is you're still using the IBM SMTP server
which is a crapshoot. :)

Bradley V. Stone
BVSTools, Inc.
[1]www.BVSTools.com
[2]www.eRPGSDK.com

Jeff Crosby wrote:

It is new for V6R1.

We recently (just over a week) switched from using the i as our mail
server to Google Apps Premier. I had to open a PMR to get everything
working correctly, but it has been wonderful since then.

I had to:

CHGSMTPA MAILROUTER("smtp.gmail.com") FIREWALL(*YES) ALWAUTH(*NONE)
FWDHUBSVR("smtp.gmail.com")

Set up a self-signed security certificate.

ADDSMTPLE TYPE(ACCEPT) INTNETADR('192.168.0.0') SUBNETMASK('255.255.0.0')

We use ESEND from Help Systems as well as the Advanced Job Scheduler
("AJS"). AJS emails stuff under user profile "jsuser", so I set up
jsuser as a user in Google Apps. In iNav I was able to tell it to
authenticate as [[4]3]jsuser@xxxxxxxxxxxxxxxxx Had to pay for an additional
user in Google Apps, but what I did was to let my
Windows/networking/support consultant use it as well. He can then do
support work while I'm on vacation. (Serendipitously, his initials
are "js".)

On Tue, Jun 30, 2009 at 10:06 AM, Jim Bostwick[4][5]<jim.bostwick@xxxxxxxxxxx> wrote:

We have just changed email service providers, so all outbound email must
provide a userid and pwd for the senders email account. I have not seen
that i5/OS supports this natively at V5R4******Any help would be greatly
appreciated.

Jim Bostwick

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: [[6]5]MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: [6][7]http://lists.midrange.com/mailman/listinfo/midrange-l
or email: [[8]7]MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at [8][9]http://archive.midrange.com/midrange-l.

References

Visible links
1. [10]http://www.bvstools.com/
2. [11]http://www.erpgsdk.com/
3. [12]mailto:jsuser@xxxxxxxxxxxxxxxx
4. [13]mailto:jim.bostwick@xxxxxxxxxxx
5. [14]mailto:MIDRANGE-L@xxxxxxxxxxxx
6. [15]http://lists.midrange.com/mailman/listinfo/midrange-l
7. [16]mailto:MIDRANGE-L-request@xxxxxxxxxxxx
8. [17]http://archive.midrange.com/midrange-l
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: [18]MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: [19]http://lists.midrange.com/mailman/listinfo/midrange-l
or email: [20]MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at [21]http://archive.midrange.com/midrange-l.

References

Visible links
1. http://www.bvstools.com/
2. http://www.erpgsdk.com/
3. mailto:bvstone@xxxxxxxxxxxx
4. mailto:3]jsuser@xxxxxxxxxxxxxxxx
5. mailto:jim.bostwick@xxxxxxxxxxx
6. mailto:5]MIDRANGE-L@xxxxxxxxxxxx
7. http://lists.midrange.com/mailman/listinfo/midrange-l
8. mailto:7]MIDRANGE-L-request@xxxxxxxxxxxx
9. http://archive.midrange.com/midrange-l
10. http://www.bvstools.com/
11. http://www.erpgsdk.com/
12. mailto:jsuser@xxxxxxxxxxxxxxxx
13. mailto:jim.bostwick@xxxxxxxxxxx
14. mailto:MIDRANGE-L@xxxxxxxxxxxx
15. http://lists.midrange.com/mailman/listinfo/midrange-l
16. mailto:MIDRANGE-L-request@xxxxxxxxxxxx
17. http://archive.midrange.com/midrange-l
18. mailto:MIDRANGE-L@xxxxxxxxxxxx
19. http://lists.midrange.com/mailman/listinfo/midrange-l
20. mailto:MIDRANGE-L-request@xxxxxxxxxxxx
21. http://archive.midrange.com/midrange-l