|
Rob, the QtmmSendMail forces the programmer to play some games with the file that contains the MIME formatted email message. The api deletes the IFS file after it has been sent. And since the send is actually done by who knows what job on the system, that delete will not happen until some time after the api returns to the caller. So if you want to use the api in the following way: - create an ifs file - write your MIME stream to the file - call QtmmSendMail with the ifs file name as a parm - loop back to step 1 and send the next message you have to pause at step 4 until QtmmSendMail gets around to deleting the IFS file. Most programmers dont deal with this at all. One of my attempts at it had to do with cycling thru a set of temporary IFS files that would be filled and passed to the API. Whichever way it is done, there is going to be a timing issue where the file passed to the API might become refilled with the next email message before the QtmmSendMail api gets around to sending the first message. One way to solve this problem is to simply delay a number of seconds after calling the api. Or before calling the api, read a dtaara containing the time of the last send. If the duration since the last send is less than, say, 5 seconds, delay for that amount of time. -Steve -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of rob@xxxxxxxxx Sent: Wednesday, July 07, 2004 12:02 PM To: midrange-l@xxxxxxxxxxxx Subject: SNDEMAIL - Volume testing Is anyone using Dave Leland's SNDEMAIL in a high volume environment? I have some emails that seem to be exchanging properties. The following is what I put in my incident to Lotus (after changing the email domain prior to posting it here): We use the QtmmSendMail API to send mail from our iSeries to our Notes users. Sometimes strange things happen. For example, Traci sent an email to Melinda and it arrived in Renee's mailbox. The email, as it appears in Renee's mailbox has the following: Traci Lxxxx <TRACIL@xxxxxxxxxx> Sent by: TRACIL@xxxxxxxxxx To: MCANNADY@xxxxxxxxxx Document Properties, Fields tab, Field SMTPOriginator shows "RENEER@xxxxxxxxxx" I followed the directions at: http://publib.boulder.ibm.com/infocenter/iseries/v5r3/ic2924/index.htm Networking, TCP/IP applications, E-mail, Troubleshoot 9....+....0....+....1....+....2....+ 126 EH SNDMAIL TO MSF 126 E1 O TRACIL@xxxxxxxxxx 126 E2 R KIMG@xxxxxxxxxx 126 EX /TMP/EMHDR065.TXT 126 ET MSG SIZE 766 126 126 P2 R SMTP MsgFwd KIMG@xxxxxxxxxx 126 C6 FWD TO QTMSOUTQ 126 C1 O TRACIL@xxxxxxxxxx 126 C2 R <KIMG@xxxxxxxxxx> 126 8B QTMSOUTQ TO CLNT 127 EH SNDMAIL TO MSF 127 E1 O TRACIL@xxxxxxxxxx 127 E2 R MCANNADY@xxxxxxxxxx 127 EX /TMP/EMHDR066.TXT 127 ET MSG SIZE 770 127 126 000010000100000 127 P2 R SMTP MsgFwd MCANNADY@xxxxxxxxxx 128 EH SNDMAIL TO MSF 128 E1 O TRACIL@xxxxxxxxxx 128 E2 R MCANNADY@xxxxxxxxxx 128 EX /TMP/EMHDR067.TXT 128 ET MSG SIZE 712 128 128 P2 R SMTP MsgFwd MCANNADY@xxxxxxxxxx 127 C6 FWD TO QTMSOUTQ 127 C1 O TRACIL@xxxxxxxxxx 127 C2 R <MCANNADY@xxxxxxxxxx> 127 8B QTMSOUTQ TO CLNT 127 000010000100000 128 C6 FWD TO QTMSOUTQ 128 C1 O TRACIL@xxxxxxxxxx 128 C2 R <MCANNADY@xxxxxxxxxx> 128 8B QTMSOUTQ TO CLNT 129 EH SNDMAIL TO MSF 129 E1 O TRACIL@xxxxxxxxxx 129 E2 R MCANNADY@xxxxxxxxxx 129 EX /TMP/EMHDR068.TXT 129 ET MSG SIZE 840 129 129 P2 R SMTP MsgFwd MCANNADY@xxxxxxxxxx 128 000010000100000 130 EH SNDMAIL TO MSF 130 E1 O RENEER@xxxxxxxxxx 130 E2 R RENEER@xxxxxxxxxx 130 EX /TMP/EMHDR069.TXT 130 ET MSG SIZE 827 130 130 P2 R SMTP MsgFwd RENEER@xxxxxxxxxx 129 C6 FWD TO QTMSOUTQ 129 C1 O TRACIL@xxxxxxxxxx 129 C2 R <MCANNADY@xxxxxxxxxx> 129 8B QTMSOUTQ TO CLNT 130 8B QTMSOUTQ TO CLNT 130 C6 FWD TO QTMSOUTQ 130 C1 O RENEER@xxxxxxxxxx 130 C2 R <RENEER@xxxxxxxxxx> 129 000010000100000 131 EH SNDMAIL TO MSF 131 E1 O TRACIL@xxxxxxxxxx 131 E2 R MCANNADY@xxxxxxxxxx 131 EX /TMP/EMHDR070.TXT 131 ET MSG SIZE 694 131 132 EH SNDMAIL TO MSF 132 E1 O RENEER@xxxxxxxxxx 131 P2 R SMTP MsgFwd MCANNADY@xxxxxxxxxx 132 E2 R RENEER@xxxxxxxxxx 132 EX /TMP/EMHDR071.TXT 132 ET MSG SIZE 825 132 132 P2 R SMTP MsgFwd RENEER@xxxxxxxxxx 126 88 DLVED 10.10.1.141 126 82 R <KIMG@xxxxxxxxxx> 130 000010000100000 127 88 DLVED 10.10.1.141 127 82 R <MCANNADY@xxxxxxxxxx> 128 88 DLVED 10.10.1.141 128 82 R <MCANNADY@xxxxxxxxxx> 131 8B QTMSOUTQ TO CLNT 131 C6 FWD TO QTMSOUTQ 131 C1 O TRACIL@xxxxxxxxxx 131 C2 R <MCANNADY@xxxxxxxxxx> 133 EH SNDMAIL TO MSF 133 E1 O RENEER@xxxxxxxxxx 133 E2 R RENEER@xxxxxxxxxx 133 EX /TMP/EMHDR072.TXT 133 ET MSG SIZE 827 133 ... Rob Berendt -- Group Dekko Services, LLC Dept 01.073 PO Box 2000 Dock 108 6928N 400E Kendallville, IN 46755 http://www.dekko.com -- 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.
As an Amazon Associate we earn from qualifying purchases.
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.
midrange.com
