That's what I was afraid of. I've already went through the process of getting whitelisted with Verizon, which was surprisingly easy. I'm not looking forward to working with Yahoo or some of our local ISPs.
Thanks for the feedback. - Sean On Mon, Aug 16, 2010 at 10:46 AM, Campbell, Rob < rob_campb...@centraltechnology.net> wrote: > That’s going to depend on the recipient’s throttling policy. If you’re > being throttled based on emails/hr or emails/min then I don’t think that’s > going to help. > > > > You probably need to contact them and find out what their policy is set to, > and see if you can get whitelisted. > > > > *From:* Sean Martin [mailto:seanmarti...@gmail.com] > *Sent:* Monday, August 16, 2010 1:40 PM > *To:* MS-Exchange Admin Issues > *Subject:* SMTP Delivery Restrictions > > > > Hey folks, > > > > We have an online banking application that allows users to sign up for > various alerts. Most of the alerts are sent in batches (the total number of > e-mails sent are totalling in the thousands). The application uses an > Exchange 2003 server as a relay. As more and more members sign up for these > alerts, I'm noticing some prominent ISPs placing temporary blocks on e-mails > from our domain (Verizon, Yahoo, etc.). I'm assuming this has something to > do with the number of connections being established in a short period of > time. > > > > The connection limit per domain is currently set to the default of 100. > Would lowering this value be a legitimate workaround for this issue? I've > been unable to find documentation on each ISPs policies for the number of > concurrent SMTP connections. > > > > - Sean > > ************************************************************************************************** > Note: > The information contained in this message may be privileged and confidential > and > protected from disclosure. If the reader of this message is not the intended > recipient, or an employee or agent responsible for delivering this message to > the intended recipient, you are hereby notified that any dissemination, > distribution or copying of this communication is strictly prohibited. If you > have received this communication in error, please notify us immediately by > replying to the message and deleting it from your computer. > ************************************************************************************************** > >
