So was I Murray, so was I... Not for profit - check. Only "blasted" our membership - check. Professional community - check. Emails on-point to organziation activiities - check. No ads - check. Etc.
Dont do it. 5-10 times a month is too much. Sending spam from your production network and servers is a monumental mistake that you do not want to make. When/if email flow stops because or DNSBL listings and/or ISPs block you entirely (happened to me from multiple ISPs) you will have a hard time explaining this if you were not originally against the idea. Being classified as spam comes multiple ways: 1. Direct reporting because a recipient is sick of it. This can happen if you have proper opt-out policies or not. Some people report spam instead of unsubscribing. Im pretty sure there are admins on this very list that promote the practice. Google in fact has features in Gmail to dissuade it. 2. Localized blacklisting because of content plus volume. 3. Global blacklisting because of undetermined variables for reporting. 4. ... it goes on. Blocking can and will take place in an unending variety of ways. There are no rules, and there are no standards. Every ISP, every mail domain, will all have varying anti-spam policies for blocking and reporting. This is a game you cannot afford to play with your production environment. -- ME2 On Thu, Sep 17, 2009 at 11:30 AM, Murray Freeman <mfree...@alanet.org>wrote: > WOW! First, let me give some additional info. We are a not-for-profit > association and only do blast email to our membership. Our plan is to do all > our 'blasts at night when the email server is quiet. Finally, our blasts are > in rather small numbers, as we only have 10,000 members and rarely blast to > the entire membership. Typical blasts are less than 2000, and then only > about 5 to 10 times per month. The reason for bringing the blasts in house > is to save money and thus have more funding for IT stuff! With that in mind, > any suggestions to the software I might need to provide stats? However, I do > appreciate your warnings! > > > *Murray * > > > ------------------------------ > *From:* Erik Goldoff [mailto:egold...@gmail.com] > *Sent:* Thursday, September 17, 2009 8:16 AM > *To:* MS-Exchange Admin Issues > *Subject:* RE: BLAST EMAIL STATISTICS SOFTWARE > > +1 > > why would you want to risk your business continuity ( and viability ) by > 'blast email' in-house ??? > > Erik Goldoff > > *IT Consultant* > > *Systems, Networks, & Security * > > > ------------------------------ > *From:* Campbell, Rob [mailto:rob_campb...@centraltechnology.net] > *Sent:* Thursday, September 17, 2009 9:09 AM > *To:* MS-Exchange Admin Issues > *Subject:* RE: BLAST EMAIL STATISTICS SOFTWARE > > Indeed. It’s not worth the disruption of your critical business email > by having your company mail servers blacklisted and RBL’d. > > > > *From:* Martin Blackstone [mailto:mblackst...@gmail.com] > *Sent:* Thursday, September 17, 2009 7:48 AM > *To:* MS-Exchange Admin Issues > *Subject:* RE: BLAST EMAIL STATISTICS SOFTWARE > > > > I think you will find many of us who had it in house fought for ages to get > it out. > > Consider yourself lucky and leave it out. > > > > *From:* Micheal Espinola Jr [mailto:michealespin...@gmail.com] > *Sent:* Wednesday, September 16, 2009 10:13 PM > *To:* MS-Exchange Admin Issues > *Subject:* Re: BLAST EMAIL STATISTICS SOFTWARE > > > > + a billion. From personal experience. Dont do it. > > -- > ME2 > > On Wed, Sep 16, 2009 at 11:07 PM, Martin Blackstone <mblackst...@gmail.com> > wrote: > > Murray, > > Unless you want to end up on a bunch of RBL’s and other fun things that go > along with doing your own email blasts, I would keep doing things just the > way you are doing them. > > Nothing good comes out of bringing this inhouse. > > > > *From:* Murray Freeman [mailto:mfree...@alanet.org] > *Sent:* Wednesday, September 16, 2009 2:37 PM > *To:* MS-Exchange Admin Issues > *Subject:* BLAST EMAIL STATISTICS SOFTWARE > > > > We currently outsource our blast email. I'd like to consider doing it > internally. The outsource company reports on such things as who opened the > email, who didn't, etc. Anyone here doing their own blast email and > collecting statistics? Obviously I need to be able to provide much the same > info if I'm to take over blast email activities. > > > > *Murray* > > > > > > ************************************************************************************************** > 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. > ************************************************************************************************** > >
