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



Hi Jeff,

If you're looking for an explanation, the closest thing I've found is the following APAR:
http://www-01.ibm.com/support/docview.wss?uid=nas244e9357c28dca0e286257763003c733e

It's not a great explanation (to put it mildly). But it provides some information, at least.


On 5/2/2011 9:54 AM, Jeff Crosby wrote:
All,

Upgraded to V7R1 over the weekend. I tested email sending yesterday by
sending emails to my gmail address and it worked, so I thought all was well.
It was not.

The System i was unable to send emails this morning to anyone with a
dilgardfoods.com email address. I opened a PMR with IBM and they solved it.

Among the many parameters on the CHGSMTPA ("Change SMTP Attributes") command
on the System i, there are 2 parameters that confuse customers. They are:

1) "Mail router" which was set to oursmtprelay.nottellingyou.blahblah. This
parameter tells the System i "Where should I send mail when I can't resolve
the recipient?"
2) "Forwarding mailhub server" which specifies where ALL mail should be
sent. This was blank.

He said customers tend to see "mail router" and think all mail will be sent
there. Not the case. We put oursmtprelay.nottellingyou.blahblah in the
forwarding mailhub server parameter as well because that's where we want all
email to go. Cycled SMTP and all was well.

Evidently something changed from V6R1 to V7R1 in the functionality of these
2 parameters.




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.