I have access to all of the header fields already, and I can (and do) check to 
make sure that the user passed the SPF, DKIM and DMARC checks successfully.

On Sun, 23 Aug 2026 10:46:31 +0000, Seymour J Metz <[email protected]> wrote:

>How do you check either of those without looking at the Received header 
>fields?  PGP signing?
>
>
>-- 
>Shmuel (Seymour J.) Metz
>http://mason.gmu.edu/~smetz3
>עַם יִשְׂרָאֵל חַי
>נֵ֣צַח יִשְׂרָאֵ֔ל לֹ֥א יְשַׁקֵּ֖ר
>
>
>
>
>________________________________________
>From: IBM Mainframe Discussion List <[email protected]> on behalf of 
>Brian Westerman <[email protected]>
>Sent: Sunday, August 23, 2026 12:42 AM
>To: [email protected] <[email protected]>
>Subject: Re: Odd idea?
>
>
>Exterall Message: Use Caution
>
>
>I'm not exactly sure what you mean, but I do check that they email address was 
>valid and that it came from an authorized server (the email server has to be 
>known in advance), I don't bother with verifying any other parts, but I do 
>keep them as variables just in case you want them during the automation 
>process, (subject, times dates, etc.).  I also validate the unicode messageid 
>and the size, but that's more for me to make sure that I don't get the same 
>message multiple times or get someone trying to play with the connection to 
>see if they can screw things up.
>
>Brian
>
>On Sat, 22 Aug 2026 2::43:12 +0000, Seymour J Metz <[email protected]> wrote:
>
>>Do a aanity check on the Received header fields for starters.
>>
>>
>>--
>>Shmuel (Seymour J.) Metz
>>http://mason.gmu.edu/~smetz3
>>עַם יִשְׂרָאֵל חַי
>>נֵ֣צַח יִשְׂרָאֵ֔ל לֹ֥א יְשַׁקֵּ֖ר
>>
>>
>>
>>
>>________________________________________
>>From: IBM Mainframe Discussion List <[email protected]> on behalf of 
>>Peter Vels <[email protected]>
>>Sent: Saturday, August 22, 2026 4:46 AM
>>To: [email protected] <[email protected]>
>>Subject: Re: Odd idea?
>>
>>
>>External Message: Use Caution
>>
>>
>>Hi Brann,
>>
>>A couple of quick thoughts:
>>
>>1. Security.  How do you determine 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 S,t, 22 Aug 2026, 17:09 Brian Westerman, <
>>[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 heve 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

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

Reply via email to