Title: Message
You've already gotten it...
 
1. Use another SMTP server on port 587 that is configured to allow more than 50 senders at a time.
2. Upgrade to business class if the current provider allows more than 50 recipients with an upgrade....or switch to a network provider who will
3. Move to a hosted listserv solution
 
I don't know of any solution that would allow what you originally asked...to set up an internal mail server that would batch forward 50 at a time to the current provider's mail servers.  Note that in general, the port 25 blockage prevents you from setting up internal SMTP server solutions except in the gateway scenario above, as server to server traffic would operate on port 25.

Darin.
 
 
----- Original Message -----
Sent: Saturday, October 23, 2004 12:56 PM
Subject: Re: [IMail Forum] Batch Sending

>> Well, his CRM app is out of date and will not function much longer given the spam filtering that's going on. Time to get him into a solution that will work on your servers or send him off to Salesforce.com
 
Funny, we move a BUNCH of people off of Salesforce monthly because Salesforce can't do what this 'outdated' CRM package will do.  Now, the CRM package is GoldMine, which I'll admit has some flaws, but it is hardly outdated except in the fact it still uses BDE, but last I knew the database engine doesn't have much to do with how the emails go out.  Perhaps you know something I don't?
 
Something else I find interesting is that if the CRM app is outdated, why is it the new MSCRM package would have the same issues?  Are we to say Microsoft's push into the CRM market should be ditched because everything they are doing is already outdated?
 
How about some 'constructive' input please.
 
 
 
 

Reply via email to