Using email for alerting and such is a Good Thing(tm).
But ... "Really Clever(tm) spammers", the bane of my existence.
After a multi-year hiatus, I am again running my own email server, and I
find the most dain-bread restrictions against it.
The worst of consumer internet/email is services which send email _on
your behalf_.
Like, "I found thus-and-so on this web site and thought you would be
interested, so here" in their mailbox as if from you.
There is no reliable way to affirm that such a sender is legit, yet they
continue to get away with it (while at-home email servers are shot down).
Here are some of the assurances which WOULD provide solid verification.
THEY DO WORK, but when the major carriers lay on yet more constraints,
email delivery fails.
* SPF, originally "sender policy framework", identifies IP addresses
which are recognized "okay" senders for your domain
* DKIM, domain keys identified mail, an asymmetric key pair which YOUR
sending email server uses for signing outbound email
* DMARC, "Domain-based Message Authentication, Reporting and
Conformance", more of a reporter than anything, but useful (and
often expected)
DKIM alone should suffice (depending on the strength of the signing
algorithms).
SPF has been around since 2002, with highly respected luminaries such as
Paul Vixie chiming in at the time.
DMARC allows for review and a form of audit.
But ... when I send from home to (e.g.) Yahoo! the transaction gets shut
down. HARD.
"You're connecting from a residential address. Go away." Seriously? This
is another case of the policy hindering the wrong people. (Those "Really
Clever(tm) spammers" don't use residential IP addresses, at least not US
residential addresses.) Something about "yet more constraints" goes here.
So ... why not simply move my email server to the outside. (i.e., to a
cloud based container or virtual machine)
Hard pass: my email server holds the private half of that DKIM pair (and
other "secrets" which I don't want to reside in the cloud).
Acorse, the lords of email security (no longer just Yahoo!) don't seem
to recognize the security problem in this case.
Few people in any IT sector recognize the profound risks of credentials
and other secrets off-prem.)
I would use IPv6 but have found that the major carriers do not answer IPv6.
Anyway, for sending email OUTSIDE your organization, good luck.
INSIDE, viability depends on your IT/security team. (Maybe "good luck"
there too?)
But there are three bullets which everyone should use, whether internal
or external.
-- R; <><
On 8/22/26 7:53 PM, Phil Smith III wrote:
RFCs.
Really Clever(tm) spammers even fake some Received: headers, making it
harder to validate.
How about an HMAC of the command itself? Still DOS-attackable but at
least you won't be executing bad commands.
On August 22, 2026 7:41:59 PM Charles Mills <[email protected]> wrote:
Thanks for the link. Any umm, you know, documentation?
CM
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
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
--
-- R; <><
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN