Re: Performance of SNDDST vs QtmmSendMail

[Steve <steve@xxxxxxxxxx>]

In article <F68zDv60gxapzhad2Vq0000ec6c@hotmail.com>, M Jull
<fcsltd@hotmail.com> writes
>At my current job there are emails that need to be sent to the internet from 
>CL and RPG programs (mostly CL's right now) and these emails can have a 
>frequency of 30,000 per hour (sometimes more).  Which method of sending will 
>be quicker (less overhead on the AS/400) - SNDDST or QtmmSendMail?  Some of 
>the emails are custom written and some are system generated 'Generic' 
>letters.
>
>Currently this is being (mis)handled by SNDNETSPLF commands....which causes 
>the 720 to slow down considerably.  None of the emails are MIME format - 
>they are just TXT files kept in a folder.  This may be a future requirement 
>(to use MIME or html docs) however.

Big volume... we found using SNDDST to do 200+ emails consecutively on a
8xx 4-way to be a real performance hit. I got round that one by re-
coding to *BCC everyone, but if you're doing your sort of volume, I'd
run a Domino server...

I don't think the OS/400 SMTP server is up to high volume traffic - even
with QtmmSendMail (but of the two options, this is more likely to work,
simply because there is less translation and SNADS queue activity going
on). I've seen MSF really misbehave with volume mailings, too (again
using SNDDST)

SNDDST is a very good, free quick & dirty which is good enough for most
commercial applications, but for your volumes I think you have a
significant requirement which justifies some investment...
-- 
Steve
  -----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GCM/B$ d++(-) s+:+ a+ C++ UL++ L+ P+ W++ N+++ K w--- O V 
PS+++ PE- t+ 5++ X- R* tv+ b+++ DI++ G e h---- r+++ z++++
  ------END GEEK CODE BLOCK------
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---