RE: Changing processing program of IBM commands - Legality, etc

I will add – Brad’s MAILTOOL and SPLTOOL programs are outstanding – used them for many years on our iSeries…they simply work and are worth the very low cost.

Greg

From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Brad Stone
Sent: Friday, September 12, 2025 12:31 PM
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxxxxxxxx>
Subject: Re: Changing processing program of IBM commands - Legality, etc

When did I say that? MSF? I won't touch that with a 10 foot pole. haha. . I wrote MAILTOOL over 20 years ago to avoid IBM's SMTP all together. :) For those that chose to use SNDDST I am seeing if I can help them with a solution that works and
ZjQcmQRYFpfptBannerStart
This Message Is From an External Sender
This message came from outside your organization.
ZjQcmQRYFpfptBannerEnd

When did I say that? MSF? I won't touch that with a 10 foot pole.

haha.. I wrote MAILTOOL over 20 years ago to avoid IBM's SMTP all

together. :)



For those that chose to use SNDDST I am seeing if I can help them with a

solution that works and has been available for 10 years now. I already

have solutions for those that rolled their own and call QtmmSendMail.



On Fri, Sep 12, 2025 at 12:03 PM Richard Schoen <richard@xxxxxxxxxxxxxxxxx<mailto:richard@xxxxxxxxxxxxxxxxx>>

wrote:

Since you said you might document and share the nuances you're aware of

related to SNDDST, MSF and OAuth I'm sure folks would be quite

appreciative.

Regards,

Richard Schoen

Web: http://www.richardschoen.net

Email: richard@xxxxxxxxxxxxxxxxx<mailto:richard@xxxxxxxxxxxxxxxxx>

----------------------------------------------------------------------

message: 1

date: Fri, 12 Sep 2025 11:51:58 -0500

from: Brad Stone <bvstone@xxxxxxxxx<mailto:bvstone@xxxxxxxxx>>

subject: Re: Changing processing program of IBM commands - Legality,

etc

I'm not trying to copyright SNDDST.. ew. I'd rather not even be related

to that command at all... lol. Just have a lot of customers and potential

customers looking for a quick option and not have to touch any code.

On Fri, Sep 12, 2025 at 11:39?AM Richard Schoen <richard@xxxxxxxxxxxxxxxxx

wrote:

SNDDST - Copyright 2025 Brad Stone

I don't think you want that copright Brad ?

Once in the 80's I put my own SIGNOFF command in the list that would

force capture user joblogs to a database when they logged off.

Them were the days.

Regards,

Richard Schoen

Web: http://www.richardschoen.net

Email: richard@xxxxxxxxxxxxxxxxx<mailto:richard@xxxxxxxxxxxxxxxxx>

----------------------------------------------------------------------

message: 1

date: Thu, 11 Sep 2025 22:00:56 -0400

from: "Art Tostaine, Jr." <atostaine@xxxxxxxxx<mailto:atostaine@xxxxxxxxx>>

subject: Re: Changing processing program of IBM commands - Legality,

etc

You?re worried they have a copyright or trademark on SNDDST?

Putting your own sign off command in front of qsys (and others) has

always been the way I thought.

I think Rob B. mentioned a few times that his email command processors

go somewhere else.

On Thu, Sep 11, 2025 at 5:20?PM Brad Stone <bvstone@xxxxxxxxx<mailto:bvstone@xxxxxxxxx>> wrote:

Yes, that's what I mentioned. I just wonder if IBM would be upset,

or potentially cause legal issues with them. I don't want to poke a

bear. I would rather work WITH them and other ISVs to help, but so

far that doesn't seem like something either wants to do.

I asked AI and it said no, but it may void warranties for the

command(s)..

hehe.

--

This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx<mailto:MIDRANGE-L@xxxxxxxxxxxxxxxxxx> To

subscribe, unsubscribe, or change list options,

visit: https://lists.midrange.com/mailman/listinfo/midrange-l

or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx<mailto:MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx>

Before posting, please take a moment to review the archives at

https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx<mailto:support@xxxxxxxxxxxxxxxxxxxx> for any subscription

related questions.

------------------------------

Subject: Digest Footer

--

This is the Midrange Systems Technical Discussion (MIDRANGE-L) digest list

To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx<mailto:MIDRANGE-L@xxxxxxxxxxxxxxxxxx> To subscribe,

unsubscribe, or change list options,

visit: https://lists.midrange.com/mailman/listinfo/midrange-l

or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx<mailto:MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx>

Before posting, please take a moment to review the archives at

https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx<mailto:support@xxxxxxxxxxxxxxxxxxxx> for any subscription related

questions.

------------------------------

End of MIDRANGE-L Digest, Vol 24, Issue 864

*******************************************

--

This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list

To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx<mailto:MIDRANGE-L@xxxxxxxxxxxxxxxxxx>

To subscribe, unsubscribe, or change list options,

visit: https://lists.midrange.com/mailman/listinfo/midrange-l

or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx<mailto:MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx>

Before posting, please take a moment to review the archives

at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx<mailto:support@xxxxxxxxxxxxxxxxxxxx> for any subscription related

questions.

--

This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list

To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx<mailto:MIDRANGE-L@xxxxxxxxxxxxxxxxxx>

To subscribe, unsubscribe, or change list options,

visit: https://lists.midrange.com/mailman/listinfo/midrange-l

or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx<mailto:MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx>

Before posting, please take a moment to review the archives

at https://archive.midrange.com/midrange-l.



Please contact support@xxxxxxxxxxxxxxxxxxxx<mailto:support@xxxxxxxxxxxxxxxxxxxx> for any subscription related questions.