|
I have used a technique similar to this
https://www.wikihow.com/Send-Email-Using-Telnet
for some testing.
Replacing the DOS telnet command with
TELNET RMTSYS(MAIL.DOMAIN.COM) PORT(25)
You may have to use a service like
http://www.zmailer.org/mxverify-cgi.html
to figure out a MX server to use in the RMTSYS() parameter.
Kind of funny to see that service use those same telnet commands, and show
them to you, as part of their test.
Just don't expect to use backspace to correct any typos. You'll probably
have to start over. Or RSET.
-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Jon
Paris
Sent: Monday, February 25, 2019 4:00 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: Delayed email (sent through QtmmSendMail, either directly or
via MMail)
Just to add further to what Brad has said.
The other problem of sending the emails directly is that increasingly
recipients are demanding higher verification levels through the DNS entries
among other things.
The switch to managed servers such as gmail and Office365 has exacerbated
this and emails that used to reach an address will often fail to do so
after the recipient switches to (say) a gmail hosted server. We gave up
trying in the end - meeting the ever changing requirements was costing more
than the monthly cost of a gmail server and using that for all outbound
traffic. A few $s a month and all my problem emails disappeared. Or rather
they didn't disappear - they actually got to the recipient in a meaningful
timeframe!
Jon Paris
www.partner400.com
www.SystemiDeveloper.com
On Feb 25, 2019, at 2:39 PM, B Stone <bvstone@xxxxxxxxx> wrote:about.
On Mon, Feb 25, 2019 at 1:22 PM James H. H. Lampert <
jamesl@xxxxxxxxxxxxxxxxx> wrote:
I've managed to find the QZMF journal, but I'm not having much luck
making sense of the entries, and the Knowledge Center page on the
subject isn't helping.
Some other thoughts:
If I have
then where does the outgoing email go, directly out of our box? OurMail router . . . . . . . . . . *NONE
ISP's SMTP server? Someplace I don't know about?
Directly to the recipient's mail server.
Normal: IBM i ----> Email Server/Router ---> recipient (good)
You: IBM i ----> recipient (bad)
Normally email will go from your box to your mail router. In the old
days that was an Exchange server. A lot these days use a cloud
service like Office 365 or GMail.
Once at the mail router/service, then the mail is delivered to the
recipient.
Exchange servers were easy to get email working with. There as
normally no authentication or encryption (ssl/tls).
Office 365 and Gmail and other cloud servers require authentication
and encryption.
Why use a mail router? So email is funneled through one server to every
possible recipient you want to send to. Any PC, Mac, tablet, Phone, and
even your IBM i should funnel email through that mail router. That
mail router is normally set up so it's trusted by end recipients using
reverse DNS and other means. Things we don't want to have to worry
lot different.
Its just like giving your mail to the mail man, and then having them
deliver it, vs you putting every piece of mail directly in the
recipients mail box/PO box.
I deal with this many times a week with customer. "It's always worked
before" is the one answer I get from all of them. Why? Because
before it wasn't a big deal. Now with the cloud services things are a
questions.
MAILTOOL has worked with cloud servers for over 15 years. Since I
needed it with GMail back then.
You have a couple options...
1. Call IBM and ask them to help you set it up.
2. Use a 3rd party product, like MAILTOOL, and be done with it.
#2 shouldn't take more than 30 minutes to get set up and installed and
working. Very cheap too.
More reading:
https://www.fieldexit.com/forum/display?threadid=425
I put that article together as a FAQ for my customers and others with
questions on how to set things up so things will work as expected.
www.bvstools.com
Bradley V. Stone
Need to interface with Braintree with your IBM i? Contact me
<https://www.bvstools.com/contact.html> for more information!
--
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@xxxxxxxxxxxx for any subscription related
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@xxxxxxxxxxxx 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@xxxxxxxxxxxx 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.