× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.




On 4/1/2010 1:04 PM, Mike wrote:
It happened again! This time we were sending out AP payment notices and
some
customers received other customers' water bills or invoices from AR.
From
9/09 in both cases. Is there a queue somewhere that may hold these
emails
that could get cleared out?

--
Mike Wills
http://mikewills.info
P: (507) 933-0880 | Skype: koldark

Hi Mike,

We had the same problem happen when emailing reports out to our stores -
reports would intermittently be delivered to the wrong location. After
looking at the SMTP QZMF logs, we came to the same conclusion as Scott,
that it is a timing issue. Looking at my old notes, I found the following
information which may help.

If you look at your QZMF log, you should see the following series of codes
in three jobs submitted to send SMTP e-mail from the 400.

1st job - from our email application
EH - Email from as/400 program to as/400 SMTP server
E1 - designates the from SMTP address
E2 - designates the to SMTP address
EX - location and name of the attachment
ET - size of message

2nd job - user QMSF pgm QZMFBIGE job QMSF
P2 - MSF (message switching facility) doing the address/name resolution
C6 - from MSF to QTMSOUTQ (output queue of SMTP)
C1 - designates the from SMTP address
C2 - designates the to SMTP address

3rd job - user QTCP pgm QTMSCLCP job QTSMTPCLTP
8B - Out queue to recipient SMTP server
88 - email delivered to Recipient;s SMTP server
82 - recipient accepted
88 - successful delivery

What we would see is the first job (codes EH thru ET) run for a store, then
before the QMSF job started (code P2), we would see codes EH thru ET for a
second store, followed by the QMSF and QTSMTPCLTP jobs for the first store.
This pattern of interleaved job log entries corresponded to misdelivered
email. Note, there were no errors when we looked at the job log. It always
said the mail had been successfully delivered.

Our quick and dirty solution was to insert a 1 second delay between sending
each email, since that was how long it took from the initial EH to 88
successful delivery. It's been a couple of years now and it does seem to
have worked. I'd really like to find a better email solution though.

Regards,
Paula Martin
Godiva Chocolatier, Inc
Manager Information Technology


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.