|
To get the firewall and Mail Router parms, I would need to change the--
Email Directory Type from *SMTPMSF to *SDD. Would that be a problem?
With *SDD setting, I see this in CHGSMTPA:
User ID prefix . . . . . . . . QSM
Address . . . . . . . . . . . QSMRMTAD
System name . . . . . . . . . TCPIP
Alias table type . . . . . . . *SYSTEM
User ID delimiter . . . . . . . '?'
Would I need to make any other changes somewhere when I change from
*SMTPMSF to *SDD?
TomH
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of
Brad Stone
Sent: Monday, August 24, 2020 9:30 AM
To: Midrange Systems Technical Discussion
<midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: How do I change SMTP mail relay server?
Set Firewall to *YES, Mail router and Forwarding hub server both to
your new router.
You didn't mention if there is any SSL/TLS or authentication needed.
Since you're using an in house relay to talk to outlook.com servers, I
would guess not.
Tip... try to use host names (it smtp.yourdomain.com) that resolve
using DNS vs IPs or host table entries. Bad practice.
Set up DNS servers in CFGTCP option 12, get the host names to use
(like your PCs do) and use them.
Having worked with thousands of customers, setting up email and other
things with hard coding IPs and using host table entries have been the
biggest pain the rear for most of them. When the IP changes, there's
a scramble to figure out why things stopped working. With host names
resolvable with DNS, that shouldn't be an issue.
<Vendor>
If you want to bypass using an in house relay and go directly to
outlook.com or office 365/gmail/etc our MAILTOOL solution has been
ahead of the curve for a long time as far as functionality,
flexibility, ease of setup and debugging,etc.
www.bvstools.com/mailtool.html </vendor>
Bradley V. Stone
www.bvstools.com
MAILTOOL Benefit #17 <https://www.bvstools.com/mailtool.html>:
Compatible with Google/Gmail/G Suite, Outlook.com, Microsoft Office
365 as well as most other SMTP servers and relays. No tricks, gimmicks or relays needed.
MAILTOOL is set up just like a PC or mobile device with the
appropriate outgoing mail router information and well as the proper authentication.
On Mon, Aug 24, 2020 at 9:22 AM Tom Hightower <tomh@xxxxxxxxxxx> wrote:
For many years we've relay-routed our IBMi-generated emails to an--
internal email server on a Win10 box (MAILSVR1), and that's worked
fine. Now TPTB have set us up with hosted outlook.com server. To
test it, we've set up another internal mail server on a separate
Win10 box (MAILSVR2). I know that I need to change the forwarding hub info.
MAILSVR1 receives email from the i and relays it to the outlook.com
server
MAILSVR2 will do the same thing, once I get the forwarding hub working...
Here's what we have that works in CHGSMTPA, using MAILSVR2:
Autostart server . . . . . . . . *NO
Clear e-mail on start-up . . . . *NO
E-mail directory type . . . . . *SMTPMSF
Retries by minute:
Number of retries . . . . . . 3
Time interval . . . . . . . . 30
Retries by day:
Number of retries . . . . . . 0
Time interval . . . . . . . . 0
Retries by hour:
Number of retries . . . . . . 0
Time interval . . . . . . . . 0
Coded character set identifier 819
Journal . . . . . . . . . . . . *YES
Support ETRN for server . . . . *NO
Delivery status notification:
Responsible person . . . . . . *NONE
Subsystem description . . . . . QSYSWRK
Library . . . . . . . . . . . QSYS
Realtime Blackhole List . . . . *NONE
Allow relayed mail . . . . . . . *NONE
+ for more values
POP send mail window . . . . . . *NONE
Interface/domain association . . *NONE
Filter mail for virus . . . . . *NONE
Override reject connect list . . *YES
Allow bare line feed . . . . . . *NO
Verify identification . . . . . *YES
Allow authentication . . . . . . *NONE
Verify MSF messages . . . . . . *NO
Verify from user . . . . . . . . *NONE
Forwarding mailhub server . . . 'MAILSVR1'
Allow e-mail over implicit SSL *NO
Max incoming e-mail messages . . *DFT
Max outgoing e-mail messages . . *DFT
Keep until . . . . . . . . . . . *DFT
Maximum e-mail message size . . *DFT
SMTP domain alias . . . . . . . *NONE
However, when I change the FWDHUBSVR value to 'MAILSVR2' and restart
the smtp server, the email is still routed to MAILSVR1. Both
MAILSVR1 and
MAILSVR2 are defined in CFGTCP option 10, Host Table Entries, and
are pingable.
What else should I look at?
Thanks
TomH
--
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
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.