Sorry. Just following up on this idea.

I'm getting a third server, and was planning on having it do only SMPT email 
delivery for the websites, which, right now, all totalled probably come to more 
like 250,000 a month. I know this isn't a lot, but about 50,000 are released in 
a big spurt every Wednesday morning. What with all the spam blocking etc as 
several people mentioned, I'm thinking that keeping the bulk delivery on a 
separate IP from the real-people Outlook-originated emails would be a good 
idea. Yes, I do pay attention to the spam blocking via a couple different 
services who email me a daily report, and I'm on AOL's scomp feedback loop, but 
I think this will keep my email eggs in two baskets, and minimize the amount of 
minute-by-minute monitoring that would otherwise be required.

So, this is what i'm thinking:

S1: CF
S2: SQL / SmarterMail (for individual client emails)
S3: Bulk SMTP (generated by all the websites doing bulk emails)

It keeps the bulk stuff sequestered, delivering it at very quick speeds, and 
lightens the load on the SQL server, which is currently handling the bulk mail.

Rational? Or not?

MM



At 04:08 PM 4/11/2013, Justin wrote:

>> The current concept is for me to get another server specifically
>> for their email delivery, and to move their app to my CF machine...
>
>First, the volumes of e-mail you're talking about may sound like a
>lot, but they're really not.  We have CF apps that do close to half a
>million messages a day during peak times. (Marketing around holidays,
>primarily)
>
>We use the IIS SMTP service for outgoing delivery.  If their e-mails
>are pretty spread out, 300k/mo would work out to about 830/hour if
>spread out over 12 hours a day.  The IIS SMTP service won't even
>notice load like that.  Install the IIS SMTP service on a server that
>doesn't already have mail services, ensure it has reverse DNS
>configured, add its IP to any SPF records you may have for domains
>you're sending for, configure it to allow relay from your localhost
>and any other IPs you control, and point ColdFusion at it for e-mail
>delivery.  Simple and no extra hardware needed.
>
>All of this assumes you're running Windows, of course.  If you're on a
>*nix platform look at Exim as it can also handle low volume like that
>without breaking a sweat.
>
>
>-Justin
>
>

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Order the Adobe Coldfusion Anthology now!
http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion
Archive: 
http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:355532
Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm
Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm

Reply via email to