I do not believe this is correct. I do not think Listserv ever did this. I just subscribed from a new address and this is what my confirmation email looks like:
---------------------------------------------------------------------------------------------- From: The University of Alabama LISTSERV Server (16.0) [lists...@listserv.ua.edu] Sent: Thursday, January 26, 2017 5:39 PM To: Evans-Young, Darren Subject: Command confirmation request (FFFFFFFF) Your command: SUBSCRIBE IBM-MAIN Big D has been received. You must now reply to this message (as explained... --------------------------------------------------------------------------------------------- Darren ________________________________________ From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Jesse 1 Robinson [jesse1.robin...@sce.com] Sent: Thursday, January 26, 2017 11:25 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: HMC Mail domain This problem hits close to the heart of IBM-Main. I discovered a while back that a new email address could not successfully be registered from within the company network. This might be for a new person or for someone whose email address had changed. After considerable frustration, I learned that the IBM-Main confirmation email sent to a new registrant has a blank 'From' tag. Not structurally invalid, not unregistered. Empty. I assume that it had always been thus, but we hadn't tried to register a new email address in quite some time. Meanwhile our email nannies had implemented a new 'security' measure to reject any email that did not specify a From id. The sender is not verified AFAIK; there just has to be one. The argument is that this one action filters out a lot of true spam. So the confirmation email from IBM-Main looks like spam and is deleted without notice to the recipient. I take it that this is standard List server software behavior. I cannot imagine a business justification for it, but it requires that any new IBM-Main (or RACF-L) user ask for manual intervention from the List owner to add the user by hand. We are not a giant company, but we have several thousand email users. The idea of asking for an exemption for a literal handful of affected users is daunting, especially because the problem could be solved by a simple software change on the List server. . . 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 robin...@sce.com -----Original Message----- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of R.S. Sent: Thursday, January 26, 2017 8:55 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: (External):Re: EXTERNAL: Re: HMC Mail domain In my humble opinion this is not a problem with HMC but network/email folks in the organisation. Any HMC name and domain has to be somehow "authorized" within company network. So, *some* effort has to be done, irrespectively of the name of HMC. If I could choose I would pay much more effort into customisation of HMC email content, to make it more clear and comfortable for users. -- Radoslaw Skorupka Lodz, Poland ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN