Re: Some QtmmSendMail weirdness: persistent files in /tmp

James,

What I've seen from things like this is these are temp files created by the
person/job sending the email, but then the SMTP job doesn't have the proper
authority to remove the file when it's done...

OR

the emails are not being delivered.

How things work with the QtmmSendMail API is

1. Create a Mime File
2. Call the API with reference to the Mime file
3. This passes off the work to a batch job(s) to delivery the mail
4. If the email is passed off with no errors, the temp file should be
removed
5. If it errors, the file stays and MSF/SMTP try to resend over and over
and over and over

So, the only reason these files should be there is the email wasn't
successfully delivered or... the job processing the email doesn't have the
proper authority to the temp file to delete it.

You also may want to contact support for the product to let them know.
Maybe they have a fix for it.

Brad
www.bvstools.com

On Mon, Oct 12, 2015 at 5:23 PM, James H. H. Lampert <
jamesl@xxxxxxxxxxxxxxxxx> wrote:

Our CRM product has the ability to send programmatically-generated email
via QtmmSendMail calls.

On a customer box (V7), I've just been informed that, for several months,
QtmmSendMail (or more likely, what it sets into motion) has been leaving
persistent files in /tmp, with generated names in the vein of:

JWaaBN2h.eml
JWaaB2rM.eml
JWaaEzRe.eml
JWaaGXVV.eml

Those are definitely not names we're generating ourselves.

This isn't happening on our box (V6), and we haven't (to date) heard of it
happening elsewhere.

Anybody know what could be doing this? And how to stop it?

--
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.