It doesn't help that m$ lookout doesn't display message headers, although if you jump through hoops you can view the original message.
-- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 עַם יִשְׂרָאֵל חַי נֵ֣צַח יִשְׂרָאֵ֔ל לֹ֥א יְשַׁקֵּ֖ר ________________________________________ From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> on behalf of Tony Harminc <t...@harminc.net> Sent: Monday, January 27, 2025 3:16 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: z/OS 2.1 & 2.2 on z16? External Message: Use Caution On Sun, 26 Jan 2025 at 17:14, Brian Westerman <000006ba4ed225c9-dmarc-requ...@listserv.ua.edu> wrote: > > I got an email from Peter that shows that some users don't get to see the ID, > so I'll put mine here, but formatted so that AI will ahve a harder time > scraping it for use > > Brian(underscore)Westerman(at)SyzygyInc(dot)com > > I'm sorry that I didn't realize that not all members can see it. Regardless, anyone can reply to the 000006ba4ed225c9-dmarc-requ...@listserv.ua.edu address. Of course it will go to the listserver, but that will forward the email on to you (and will not send it to the list). Well, if you don't like the idea of the UA listserv being able to see your private mail, then just use the first one to exchange actual email addresses, and continue from there. This wasn't done by Lsoft to obfuscate peoples' emails - it's to work around Google's intentional breaking of email lists. Groups.io did something similar, but they include a readable version of the original email address in the faked-up one. Tony H. ---------------------------------------------------------------------- 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
