× 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.



Nathan,

Don't both those email systems use IBM's SMTP server and MSF?

Unless your IBM i is set up to email directly and not through a mail
router, then we should be looking at the mail router logs as that is what
is doing the final delivery to the destination.

If your IBM i _is_ set up without a router then it could be reverse DNS
setup issues if it's only a couple of domains.

The logging in our MAILTOOL Plus software would tell you what the problem
is if that's the case. That's because we bypass all the IBM email
processes and can spit out a nice communications logs of the email being
sent.

I'm not suggesting the MAILTOOL software is purchased, I'm suggesting it as
a free way to test what could be wrong. Just so we're clear about that.

Brad
www.bvstools.com

On Fri, Mar 13, 2015 at 12:15 PM, Nathan Andelin <nandelin@xxxxxxxxx> wrote:

I tried SNDSMTPEMM to test sending mail to my YAHOO account. It worked
fine. But one problem is that no errors are reported back when sending to
unknown domain names and such erroneous events. So I wouldn't rely on the
command.

I've been very pleased with the error reporting available through
the dtw_sendmail() function.




On Fri, Mar 13, 2015 at 6:52 AM, Bradley Stone <bvstone@xxxxxxxxx> wrote:

Hi, Bob.

There are a few more details needed, such as what are your settings in
the
CHGSMTPA command for Mail Router, Firewall and Forwarding Hub server.
But,
I wrote an article on tracking down email issues on the IBM i since we
deal
with this issue a lot with our MAILTOOL software:

http://fieldexit.com/forum/display?threadid=140

What I find interesting in your case is that only one type of account
isn't
receiving the email. So, that means that if you're using a mail router,
you'll want to contact the admin to see the logs of the actual delivery
from the router to the outlook account.

If you're not using a mail router, then you should contact the people who
put your email package together to see if they can provide a log to see
the
communications between your IBM i and the recipient.

You could also get this trace with our MAILTOOL software as outlined in
the
article above.

I just tested with my outlook.com accounts and everything seems fine.

Brad
www.bvstools.com

On Thu, Mar 12, 2015 at 1:14 PM, Gary Thompson <gthompson@xxxxxxxxxxx>
wrote:

FWIW office 365 is working here in mudville . . .

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Bob Cagle
Sent: Thursday, March 12, 2015 10:32 AM
To: MIDRANGE-L@xxxxxxxxxxxx
Subject: Sending email to Office 365 from System i has died

I have a report distribution utility that sends email from the System i
using the SNDSMTPEMM command. As of yesterday afternoon, the emails
are
no
longer being received in our Office 365 inboxes.

According to the job logs, the reports are being generated and sent to
the
outq that's being monitored.

The email utility sees the reports and is successfully sending the
emails
- everything looks fine.

This setup has been working for over a year. I am a one man shop and I
can say with complete certainty that absolutely nothing has changed on
our
side.

So, did something change on Microsoft's side? I have looked in the
spam
quarantine and our reports aren't there. I can't find any evidence
that
Office 365 is even receiving them.

A possible clue is that I can send successfully to my personal Gmail
account, but not my Hotmail account.

Anyone else running into this same issue? I believe that something was
changed yesterday afternoon in Office 365 to break this.

Thanks

Bob Cagle
IT Manager
Lynk, Inc.


--
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: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take
a
moment to review the archives at
http://archive.midrange.com/midrange-l.

--
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: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


--
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: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


--
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: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.



As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.