Re: QTmmSendMail weirdness

I've used it for years and the only time I've seen it act weird is when I
told it to do so (unknowingly). When it's called it queues the email to be
sent, but that's where the issue can arise.

Your description of the problem isn't very clear, but here's an example of
what can happen:

1. You create your MIME file with a name using something like a timestamp
for the MIME file name. This email will go to Bob.

2. You call QtmmSendMail. Passing the MIME file name and tell it to send
to Bob.

3. Another process does the same thing, but it's sending to Joe. Even
though you're using a timestamp for the filename (thinking it will be
unique) it just so happens that the MIME file ends up with the same name as
the one used to send to Bob, overwriting the MIME file you created in step
1. So the first email goes to the correct recipient, but it gets Joe's
email, not the one intended for Bob.

In a nutshell, if you're not naming your MIME file with a Unique name (and
I mean unique such as a sequential number, not a timestamp or random id)
then weirdness can arise.

Brad
www.bvstools.com

On Tue, Aug 9, 2016 at 4:09 PM, James H. H. Lampert <
jamesl@xxxxxxxxxxxxxxxxx> wrote:

Question:

Has anybody ever heard of QTmmSendMail going crazy, such that when called
repeatedly from the same program, with different messages going to
different recipients, it sends everything to the recipient from the first
time it was called?

--
JHHL
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.