This version was developed under OS/2, initially with Perl 5.6, later
with Perl 5.8.2 and most recently with Perl 5.10.0, which is now
required.  The perl510.wpi build from Paul Smedley did not include
all of the CPAN packages that had been in my Perl 5.8.2, and I
downloaded the following from CPAN:

Digest-1.15.tar.gz
Digest-HMAC-1.01.tar.gz
Digest-SHA1-2.11.tar.gz
Email-ARF-0.006.tar.gz
Email::Date::Format
Email::MessageID
Email-MIME-1.910.tar.gz
Email-MIME-ContentType-1.015.tar.gz
Email::MIME::Encodings 1.313
Email-Simple-2.101.tar.gz
HTML-Parser-3.56.tar.gz
HTML-Tagset-3.20.tar.gz
IO-1.25.tar.gz
IO-stringy-2.110.tar.gz
MIME-tools-5.427.tar.gz
MIME::Types 1.13
MailTools-2.04.tar.gz
Net-DNS-0.67.tar.gz
Net-IP-1.25.tar.gz
Net-IP-Match-0.03.tar.gz
Net-IP-Match-Regexp-1.01.tar.gz
Params-Util-1.04.tar.gz
Regexp-Common-2.120.tar.gz
Test-Pod-1.26.tar.gz
Test-Simple-0.98.tar.gz
TimeDate-1.16.tar.gz
URI-1.37.tar.gz

I've added a module to Regexp::Common::URI,
Regexp::Common::URI::badhttp, but no longer use it; you don't need to
extract badhttp.pm into your Regexp\Comon\URI directory.

I currently don't use HTML::*.

To install, extract the three .conf files into the WHOIS subirectory
of %ETC%, copy the two .cmd files into a directory in your path and
configure the files. Normally the ETC directory will be \MPTN\ETC on
the boot drive for OS/2 and /etc for *ix and bsd.

Install all of the packages that I listed above. If you are using
CPANPLUS (CPANPLUS-0.9116), it will resolve dependencies for these:

Data::Dumper                    Data-Dumper-2.131

Dumpvalue                       Dumpvalue-1.16

Email-ARF                       Email-ARF-0.006
    Email::Simple::Creator          Email-Simple-2.101
        Email::Date::Format             Email-Date-Format-1.002
    Email::MIME                     Email-MIME-1.910
        Email::Address                  Email-Address-1.895
        Email::MessageID                Email-MessageID-1.402
        Email::MIME::ContentType        Email-MIME-ContentType-1.015
        Email::MIME::Encodings          Email-MIME-Encodings-1.313
            MIME::QuotedPrint               MIME-Base64-3.13
        Email::Simple::Creator          Email-Simple-2.101
        MIME::Types                     MIME-Types-1.34
    Params::Util                    Params-Util-1.04
                                        ExtUtils-MakeMaker-6.62
            Data-Dumper-2.131               Data-Dumper-2.131

File::Spec                      PathTools-3.33

Getopt::Long                    Getopt-Long-2.38

IO::File                        IO-1.25

IO::Socket                      IO-1.25

MIME::Parser                    MIME-tools-5.502
    Mail::Header                    MailTools-2.08
        Date::Format                TimeDate-1.20
        Test::Pod                   Test-Pod-1.45

MIME::QuotedPrint               MIME-Base64-3.13

MIME::Tools                     MIME-tools-5.502

Mail::Address                   MailTools-2.08
        Date::Format                TimeDate-1.20
        Test::Pod                   Test-Pod-1.45

Net::DNS                       Net-DNS-0.67
    Digest::HMAC_MD5               Digest-HMAC-1.01.tar.gz
        ExtUtils::MakeMaker            ExtUtils-MakeMaker-6.62

Pod::Usage                     Pod-Parser-1.38

Regexp::Common                 Regexp-Common-2011121001

Regexp::Common::URI::RFC2396   Regexp-Common-2.120

Socket                         Socket-1.97

URI::Escape                    URI-1.59

In the future, I expect to need

Mail::DKIM                     Mail-DKIM-0.39
    Crypt::OpenSSL::RSA            Crypt-OpenSSL-RSA-0.28
        Crypt::OpenSSL::Random         Crypt-OpenSSL-Random-0.04
    Mail::Address                  MailTools-2.08
            Date::Format               TimeDate-1.20
            Test::Pod                  Test-Pod-1.45
    Net::DNS                       Net-DNS-0.67
        Digest::HMAC_MD5               Digest-HMAC-1.01.tar.gz
    Test::Pod                   Test-Pod-1.45

Mail::SPF                      Mail-SPF-v2.007
    Error                          Error-0.17016
    Net::DNS                       Net-DNS-0.67
        Digest::HMAC_MD5               Digest-HMAC-1.01.tar.gz
    NetAddr::IP                    NetAddr-IP-4.058
    URI                            URI-1.59

For OS/2 you will need to update the extproc lines to reflect where
your Perl is located; for *ix and bsd you will need to remove the
extproc lines, update the shebang (#!) lines to reflect where your
Perl is located and mark the file executable with chmod.  I don't
know the windoze equivalent.  For *ix and bsd you will also need to
make the .cmd files executable with, e.g., chmod.

For all systems you will need to change the default value of $temp
or override it with the --temp <path> option.



-- 
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:41 PM
To: [email protected] <[email protected]>
Subject: Re: Odd idea?


External Message: Use Caution


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

Reply via email to