> I can strongly consider Alligate in front of Declude. So let's say I build a dedicated Alligate box to live in front of my two Declude enabled servers. How much of a load would it be able to handle? I would need it to handle close to 250k messages per day (current combined load) with room to grow, and it looks like Alligate is yet-another-thousand-dollar-thing-that-will-need-yearly-subscriptions-of-hun dreds-of-dollars.
I'd be happier if I could just send my money to one company. So would Declude, I'm sure. But hey. If that's what you gotta do. I was thinking of using a home built postfix gateway to go in front of the boxen, and if I need more I was just going to add more identical postfix boxen a la round robin DNS. Bad idea? Good idea? But my customers could use some help today, which is why I was thinking of using Declude to do some recipient verification. Conceptually, that would cut down the work load considerably, right? I've been having trouble with my Message Sniffer (in persistent mode) going into a cascading failure during peak periods because of the volume; so I leave it off most of the time, which is a huge waste. I'm just wondering how to go about using Declude to do this. Thanks for all the feedback! I've got an open mind. -- Michael Cummins --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type "unsubscribe Declude.JunkMail". The archives can be found at http://www.mail-archive.com.
