|
Thanks Brad.
This doesn't tell us much, there are only a small handful of users that
currently have a SMTP name. However, we will be getting a dump from another
HR system of user email addresses, probably as a spreadsheet. I'm thinking
we may be able to do an SQL update of QATMSMTPA!
That should be handled at the new gateway vs checking for an active name.
Just to clarify what we need, we currently allow just about anyone to send
mails from the IBM i, but we are changing (Corporate policy) to a different
SMTP gateway that will only allow it based on access approvals from another
HR system and a valid Active Directory name. Aside from changing the server
name in CHGSMTPA, we have to set up SMTP names for all current users.
Thanks
Adam DRIVER
GTS/MKT/SSB/AS400
440 S. La Salle, 25th Floor
Chicago, IL 60605
Tel.: +1 312.762.1194
Cell: +1 224.250.9049
Team: +1 312.762.1125
Email: adam.driver@xxxxxxxxxx<mailto:adam.driver@xxxxxxxxxx>
www.sgcib.com<http://www.sgcib.com/>
Primary CI: AS400
Assignment Group: gts-wwi-ssb-app-as400
Team Email: amer-gts-mkt-ssb-as400-team
Tel (24 hrs): 312 762 1125
Any new support request should be sent to the first level at
helpdesk@xxxxxxxxxxxxxxxxxxx<mailto:helpdesk@xxxxxxxxxxxxxxxxxxx>
[
http://insite.fr.world.socgen/ecard/images/logo_legal_l.gif][http://insite.fr.world.socgen/ecard/images/logo_legal_r.gif
]
date: Mon, 14 May 2018 14:44:52 -0500
from: Bradley Stone <bvstone@xxxxxxxxx<mailto:bvstone@xxxxxxxxx>>
subject:
First, Grab the SMTP user name using the User ID from file QAOKP01A.
Field SMTPUID.
Then use that to get the SMTP address from QUSRSYS/QATMSMTPA using SMTPUID
from QAOKP01A = USERID. This should help.
Bradley V. Stone
www.bvstools.com<http://www.bvstools.com>
MAILTOOL Benefit #9 <https://www.bvstools.com/mailtool.html>: Superior
debugging (when using MAILTOOL Plus) - Bypassing the IBM SMTP server means
that we can fully debug and track down sometimes hard to find problems.
Even the Trace TCP/IP Application (TRCTCPAPP) command won't be this
detailed!
*************************************************************************
This message and any attachments (the "message") are confidential, intended
solely for the addressee(s), and may contain legally privileged
information.
Any unauthorized use or dissemination is prohibited. E-mails are
susceptible
to alteration. Neither SOCIETE GENERALE nor any of its subsidiaries or
affiliates shall be liable for the message if altered, changed or
falsified.
Please visit http://sgasdisclosure.com for important information regarding
SG Americas Securities, LLC (“SGAS”). Please visit
http://swapdisclosure.sgcib.com
for important information regarding swap transactions with SOCIETE
GENERALE.
*************************************************************************
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related
questions.
Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD
As an Amazon Associate we earn from qualifying purchases.
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.