Our "subscribers" signup for these alerts by logging into their bank account and selecting the alerts they'd like to receive, so it's purely opt-in for the user. I know we often see addresses entered incorrectly so there's a good chance we're continually pounding invalid addresses if our application team isn't managing the alert lists. I imagine that's probably a good way to eventually get blacklisted. I would hope those that have signed up aren't marking our messages as SPAM, but it's probably not outside the realm of possibility.
I meantioned the complexity in getting whitelisted because I ran across this post regarding Yahoo.... http://www.smartertools.com/forums/p/13531/30555.aspx Thanks! - Sean On Mon, Aug 16, 2010 at 12:01 PM, Michael B. Smith <[email protected]>wrote: > Yahoo, MSN/Hotmail, AOL, Gmail, etc. – it’s actually very easy. There are > online forms to allow you to explain what is going on and request for a few > IPs to be whitelisted. You REALLY NEED TO ENSURE that your subscribers > addresses have been validated, one way or another. Also for the above > “big-4” it’s easy to get blacklisted if users mark your messages as spam. > > > > Local ISPs – good luck with that. > > > > Regards, > > > > Michael B. Smith > > Consultant and Exchange MVP > > http://TheEssentialExchange.com <http://theessentialexchange.com/> > > > > *From:* Sean Martin [mailto:[email protected]] > *Sent:* Monday, August 16, 2010 2:54 PM > > *To:* MS-Exchange Admin Issues > *Subject:* Re: SMTP Delivery Restrictions > > > > 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 < > [email protected]> 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:[email protected]] > *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. > > ************************************************************************************************** > > >
