Still not sure what you are referring to.  I check a lot of the fields and the 
actual path back to the starting server, which has to be known to the process.  
Maybe I'm missing something, but I don't know what.

Brian

On Sat, 22 Aug 2026 23:21:27 +0000, Seymour J Metz <[email protected]> wrote:

>The From: header field is worthless, and the envelope from can also be 
>spoofed; include a sanity check on the Received header fields. See 
><https://mason.gmu.edu/~smetz3/source/unobfuscate.zip>
>
>
>-- 
>Shmuel (Seymour J.) Metz
>http://mason.gmu.edu/~smetz3
>עַם יִשְׂרָאֵל חַי
>נֵ֣צַח יִשְׂרָאֵ֔ל לֹ֥א יְשַׁקֵּ֖ר
>
>
>
>
>________________________________________
>From: IBM Mainframe Discussion List <[email protected]> on behalf of 
>Charles Mills <[email protected]>
>Sent: Saturday, August 22, 2026 7:02 PM
>To: [email protected] <[email protected]>
>Subject: Re: Odd idea?
>
>
>External Message: Use Caution
>
>
>I'm not an expert oeee-mail but on the negative side isn't the "from" pretty 
>easy to spoof? There are reality checks you can do on the IP addresses and so 
>forth, but is it bulletproof enough?
>
>On the positive side, the email body is potentially a pretty rich interface. 
>You could accept a "command" with a syntax that allowed all kinds of options: 
>email always, or just on failure? Override job class and scheduling? Etc.
>
>Charles
>
>On Sat, 22 Aug 2026 18:46:09 +1000, Peter Vlss <[email protected]> wrote:
>
>>Hi Brian,
>>
>>A colple of quick thoughts:
>>
>>1. Security.  How do you determint that the incoming email is legitimate?
>>2. Yes, tell the user whether it was successful or not,  but give them a
>>choice, make it a keyword or flag? If you don't tell them it was
>>successful,  how do they know it even executed?
>>3. Same goes for the output; give the user a choice.
>>
>>Regards,
>>Peter
>>
>>
>>On Sat, 22 Aug 2026, 17:09 BrianeWesterman, <
>>[email protected]> wrote:
>>
>>> I was wondering.  Since IBM is unlikely to ever change CSSMTP to create
>>> the ability to send email to the mainframe, what do you think about adding
>>> the ability for sending email to our automation system to have it execute
>>> functions and/or commands on the mainframe?  We have supported using FTP to
>>> do that for many years, and have provided trigger commands, but this would
>>> be creating the ability to send an email to what would be the "inbox" for
>>> talking with the Syzygy automation system and having it confirm if the
>>> email sender was authorized to issue commands and of what type, and then
>>> pass them on to the automation system on the various LPARs that automation
>>> is executing on for processing.
>>>
>>> I have a prototype created that I have been testing for a while and I am
>>> looking for volunteers to try it out.  The only restriction is that you
>>> have to be running the Syzygy Automation package, (shame on you if you
>>> aren't :).
>>>
>>> I'm trying to decide if the process needs to reflect back to the user that
>>> the process was successful.  I current tell them if it wasn't, and there is
>>> no reason that I couldn't tell them that it was as well, but can't decide
>>> if that's necessary.
>>>
>>> I found that I could also ask automation to send the output of jobs in the
>>> queue, but didn't know if that's something that would be useful because the
>>> automation system already can send email when any job ends that contains
>>> the output already.  So it could be a "feature" I keep to the side to add
>>> later.
>>>
>>> Even if (for some odd reason) you don't run the Syzygy Automation system,
>>> I would be interested in your thoughts on this process.
>>>
>>> Brian
>>>
>>> ----------------------------------------------------------------------
>>> For IBM-MAIN subscribe / signoff / archive access instructions,
>>> send email to [email protected] with the message: INFO IBM-MAIN
>>>
>>
>>----------------------------------------------------------------------
>>For IBM-MAIN subscribe / signoff / archive access instructions,
>>send email to [email protected] with the message: INFO IBM-MAIN
>
>----------------------------------------------------------------------
>For IBM-MAIN subscribe / signoff / archive access instructions,
>send email to [email protected] with the message: INFO IBM-MAIN
>
>
>
>
>----------------------------------------------------------------------
>For IBM-MAIN subscribe / signoff / archive access instructions,
>send email to [email protected] with the message: INFO IBM-MAIN

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to