Howie:

In designing the backend submission process for a rewrite of an existing 
broadcast mailing app we've come up against a problem.  Letting the iMSMail.dll 
do all the merging and removals is amazingly efficient ... but it creates 
control files for 'like' domains w/ all the recipients of that domain listed in 
one file (for each domain).

It's my understanding that generating the emails this way will lead to the POST 
server opening up a connection to the recipient domain and sending all the 
emails for that domain in one shot.  This could lead to the remote SMTP server 
to drop the connection and block email from that source (it sees you as a 
spammer).  It's typical that a job submitted (on current system) to do an email 
broadcast could have 20k - 100k recipients.

Is this at all true?  Is there any way to get around this potential issue?  Any 
way to create a 1 for 1 contol/email file result while still using the merging 
within the dll?

We're considering an alternative of iterating over the recipient list in the 
(.Net) code and calling the dll on each pass w/ the appropriate properties.  
Tests show this method to be signifigantly slower (almost 10/1) and we'll have 
to write the code to merge all the dynamic data into the HTML template outside 
the dll (and pass it in as a pre-merged HTML body).

What options are there between the use of the dll and the settings in the POST 
server that would allow us to deal w/ this problem most effectively?

The current system produces a contol/email file pair for each recipient ... as 
if it calls the dll w/ all the neccessary properties to produce the mail for 
each recipient on the list (i don't have access to the orignal source; only the 
results it produces).

Bob
==^=======================================================
This list server is Powered by iMS  "The Swiss Army Knife of Mail Servers"
--------------------------------------------------------------------------------------
This list is provided as a free service.  Although we will try to address issues
in a timely manner, support via this list is not guaranteed.  If you require 
expedited
support then a support contract is required.  Support may be purchased from
http://www.coolfusion.com/commerce.  Details regarding support options may be 
reviewed
at: http://www.coolfusion.com/SupportOptions.cfm
--------------------------------------------------------------------------------------
To leave this list please complete the form at 
http://www.coolfusion.com/Support/
Need an iMS Developer license?  Sign up for a free license here:
http://www.coolfusion.com/Developers/
List archives: http://www.mail-archive.com/infusion-email%40eoscape.com/
Note: You are subscribed as archive_jab_org / [email protected]
==^=======================================================


Reply via email to