The correct lookup for sending an e-mail is to first look for an MX record and only to look at the A records if there is no valid MX record.
BTW, WRT nslookup, "Many people nowadays like" dig "instead." Either will work.
RFC 822 is one of the older RFCs; even RFC 2822 is pretty long in the tooth. RFC has been the current specification of the body syntax for years, with RFC 5321 replacing 2821 and 821 for SMTP. RFC 5321 error codes with RFC 3463 extended error codes could be sent for any of the SMTP commands, including DATA, EHLO, HELO, MAIL, and RCPT.
If the sending software is following the rules, then it will pass the error notification on. If it doesn't, then it is broken and the responsibility is then on the admin of the broken sending site.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
________________________________________
From: IBM Mainframe Discussion List <IBM-***@listserv.ua.edu> on behalf of Alan(GMAIL)Watthey <***@GMAIL.COM>
Sent: Wednesday, January 10, 2018 12:49 AM
To: IBM-***@listserv.ua.edu
Subject: Re: Changing password on IBM Link
Jesse,
I fear you may not be looking at the correct DNS record. This looks like the 'A' record (the default for nslookup) and you need to look at the 'TXT' record. The 'A' record has nothing to do with the origin IP address of an email. The 'A' record is the IP address they want you to contact them on.
The commands you need are as follows:
nslookup
set type=txt
us.ibm.com
Others have mentioned the sender being notified of the rejection. Error notifications would go back to the RFC 821 MAIL FROM header specification which may not be set to accept them (I can only see the RFC 822 headers). However, I'm pretty sure the SMTP conversation will show up the failure but someone actually has to be looking out for those errors. It would be mixed in with timeouts, retries, destination errors and loads of other things going wrong so perhaps difficult to spot manually anyway.
Your link is fine for resetting a password you remember but a forgotten password needs the email link. Just don't forget your password I guess.
Regards,
Alan Watthey
-----Original Message-----
From: Jesse 1 Robinson [mailto:***@SCE.COM]
Sent: 09 January 2018 9:02 pm
Subject: Re: Changing password on IBM Link
I got an off-list pointer to this address: https://secure-web.cisco.com/1176m3k1dhhTwan40Ic55x-ZjewO5XQE-bUXdrUNp3AJXnW-KUOdM_y5vRUSUPFzZXBnvQdDBs4XZRFDWKKiKYO66jDCgFHiBAEIGQkw6embfZ89pf1RRR09cuDVi6jntcHFFbR4cPmnYzpfIPy_6tGPgSehFNDNE6E_78VGzC5_NODXEAZ9ZP7WCRrmq8I00DxvX3MUPDL4sFo0OCK7QfojB-MoG2pg3StNkw-1lDQ664YSc3quTyyfDnNcKxLNV2XNtWEmp254rpx4C1_H9KLD4aWN_QVO62E-mPkYgjnu21R0YSmQicwxnUCBdJQGLoR1Z3NHrqQI0SHhRT1TkUnfQE_lcq5DJHsV6TEynsL8zMOgNqr420ua1k0vrbdr-xKk14vTOX5Dv1WeAnJU5B6zXc3YmraX309HoThHibOkJHPj6Zy6pPTJLrVSeZn2W/https%3A%2F%2Fwww.ibm.com%2Faccount%2Fprofile%2Fus%3Fpage%3Dsigninview
It allowed me to change my password without an intervening verification email. As such, it worked for this purpose but might disappear without notice.
In response to the password change, I got a confirmation email from ***@us.ibm.com, which reached my Inbox with no problem. It certainly looks like the same id/domain that the verification email comes from, which leads me back to the idea of a difference in the note construction itself.
BTW NSLOOKUP here (sce.com) for us.ibm.com shows 172.28.128.15 . I get lots of email from us.ibm.com. AFAIK the password verification email is the only one that fails to reach my Inbox.
.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler
SHARE MVS Program Co-Manager
323-715-0595 Mobile
626-543-6132 Office ⇐=== NEW
***@sce.com
-----Original Message-----
From: IBM Mainframe Discussion List [mailto:IBM-***@LISTSERV.UA.EDU] On Behalf Of Alan(GMAIL)Watthey
Sent: Tuesday, January 09, 2018 5:02 AM
To: IBM-***@LISTSERV.UA.EDU
Subject: (External):Re: Changing password on IBM Link
I'm not saying it is the same problem that you are getting but we have the problem of not receiving certain emails from the PMR registration process.
They never get through from anyone (although someone once said they tried 50 times and eventually one got through).
This first raised its head sending from my personal email address to my company email address. When I cornered a Microsoft Exchange guy here he did some checking and said it was being rejected because the email was coming from an origin IP address that was not registered. They had recently added checking to their email system and these failed the check. So, for example, if the email comes from ***@foo.bar then the IP addresses of all the foo.bar email servers have to be registered under the foo.bar name. This is done in the public facing DNS by the owner of the foo.bar domain. I had to go to my personal DNS entry and add the appropriate entry. Since then my emails have got through fine. Fortunately my ISP had a webpage explaining how to add this because it was all new to me.
More and more email systems are apparently checking this DNS entry is correct to prevent spoofing. It stops me sending an email pretending to be from ***@microsoft.com (for example) as that would originate in my ISP's email server which is not an IP address registered by the owners of microsoft.com. I think I can live with that restriction.
If you've never heard of it then read up about SPF (Sender Policy Framework) in Wikipedia.
I have no idea who to contact in IBM to check their end. I tried sending some emails (haha) to no avail. We still have problems.
I tried sending a password reset email from 'Service Request' to my company email 15 minutes ago and it never got through so the problem still appears to exist.
Windows NSLOOKUP (maybe others) will show you the SPF settings for US.IBM.COM (or any other domain).
When I checked just now US.IBM.COM has the following specified:
"v=spf1 ip4:148.163.158.5 ip4:148.163.156.1 a:d25xlcore010.ca.ibm.com a:isource.boulder.ibm.com a:y01exnat001.ahe.pok.ibm.com a:y01acxsmtp001.ahe.pok.ibm.com a:y01acxsmtp002.ahe.pok.ibm.com a:g01zcdsmtp002.ahe.pok.ibm.com ip4:129.33.239.88"
I'm still working on our problem trying to find the correct people to resolve it. At this stage I can confidently say it's either us or IBM!!
However, I can say that I just checked the last PMR update email (header) that got through and it came from srdonotreply @ us.ibm.com from IP
148.163.158.5 which is in their list above. Also I sent a password reset to my personal email address and it said it came from ibmacct @ us.ibm.com from IP 167.89.77.139 which is not in their list. I guess my ISP doesn't check (yet). It appears they might outsource this password service hence the problem lies there as that IP address is someone called sendgrid.net.
I will keep digging but it is low priority.
Anyway, I would advise checking with whoever looks after your email system and ask them to check in their logs as to why the email is being rejected.
It might be as above or it might be something else.
Regards,
Alan Watthey
-----Original Message-----
From: Jesse 1 Robinson [mailto:***@SCE.COM]
Sent: 09 January 2018 1:45 am
Subject: Changing password on IBM Link
I need to change my password on IBM Link. After 20 years managing the same userid, I find that there is now a new confirmation process that did not exist a few months ago. I am sent an email to verify my email address.
Unfortunately that email never reaches my Inbox. I've tried over and over; it never shows up. A problem ticket with my email folks has not resolved the issue.
It's reminiscent of an old problem with IBM Main, where the confirmation email for a new subscription also does not show up. I learned some time ago that just that particular note is lacking a 'Sender' and is therefore treated here as spam. I can't prove it's the same issue with the IBM.COM confirmation, but it smells familiar.
Anyone else having issues?
.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler
SHARE MVS Program Co-Manager
323-715-0595 Mobile
626-543-6132 Office <===== NEW
***@sce.com<mailto:***@sce.com>
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to ***@listserv.ua.edu with the message: INFO IBM-MAIN