×
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.
We are in the process of moving from internally hosting our email on
Exchange to a hosted Exchange setup. We have various applications that
do need to send email through a relay and the new mail provider has set
one up for us with a user and password to be used for authentication to
relaying.
Other applications I've switched to this setup are working OK but I
can't seem to get our System i to send through it properly.
To start simple, I'll say that when I have our internal (still up and
running) Exchange server set up as the Forwarding Mailhub Server
(FWDHUBSVR), everything works just fine.
I change the Mailhub value to the external provider's address and mail
does not send. Here are some things I have checked or done.
I did check that the DNS name for the external provider does resolve to
an IP properly.
Because we must authenticate to the new relay server (internal one did
not need that), I did also use ADDSMTPLE with List Type *HOSTAUTH to
specify a logon to the external provider's server.
I thought that's all I needed to do, but if I did, then I would not need
to be emailing all of you for help :)
With the configuration set to the outside provider and trying SNDDST, I
dumped the SMTP journal to a file and that looks like this:
87 CLNT(UNDELV) TO QTMSINQ
7A QTMSINQ TO BRSR
7P CRT UNDEL NOTICE OR DSN
7H BRSR TO MSF
71 O @
72 R <QTCP@QTCP>
7G MSGID MAP TO ID 062C97R1504161346230000000130
P2 R QTCP@QTCP
I'm hoping someone may have some expertise to lend me on this setup.
Thanks much!
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.