>Yes - I think Len was talking about POST'ing the mail across the network to a
>local SMTP server to relay it from, there in which case the SMTP would
>technically be doing the sending - or relaying to be more accurate. I really
>can't see the point in that

You will, Adrian, you will.  If not "in theory" now, in practice 
later, when iMS is getting hammered with incoming AND AND 
outgoing.  You will be deliriously happy to offload at LAN speed from 
iMS to a dedicated POST relay hub. SQL server will not have to do DNS 
lookups and will not have to battle with deliveries to internet.

>The mail performance of this list is truly amazing - remembering I 
>am on an Island in the Irish sea - when I post to the list it comes 
>back to me instantaneously like it
>is on the end of a long rubber band :-) You compare that to the 
>CF-Talk list or
>any other list for that matter. I also like being able to inject 
>directly to the
>POST queue - that is a big plus.

120 members, chicken feed.

It's pretty clear you have no idea of the problems you will, not 
might, but will have when you try to scale to 100K or 200K mailboxes' 
traffic in/out on SQL server.

The other pb, here I'm less certain but not by much less, will be 
that web msging on CF won't scale for sh@t.  It's very hard to say 
which of your two boxes will box you in first, but have your escape 
route planned carefully.

Do you or Howie have any knowledge of anybody who has done 
large-scale web messaging on CF into iMS?

What protocol will Web Messaging box use to talk to the mailboxes on 
iMS? POP3? or just MS Networking shares into the iMS box?

Len


========================================================================
     This list server is Powered by iMS
   'The Swiss Army Knife of Mail Servers'
   --------------------------------------
To leave this list please complete the form at 
http://www.CoolFusion.com/iMS.htm

List archives: http://www.mail-archive.com/infusion-email%40eoscape.com/
========================================================================

Reply via email to