Yeah, I'd considered that, which is why I actually divided things up into 3 different categories. There's critical updates, which are mandatory and would include extremely important and urgent information (basically anything that might create downtime). There's maintenance alerts, which are optional and are mainly informational maintenance notices (ie: we upgrade PHP). Then there's the actual newsletter, which is optional and I intended for things like feature announcements, future plans, etc...Boltzmann said:My answer would be just like Kane's.
But the problem with company's newsletters is that they're usually full of crap. 90% of the stuff they send to you is useless.
But there's nothing you could have done, though.
I only class the other two as "newsletters" because they're included in the same newsletter system. So, really when I send out a critical update, it's usually marked "IMPORTANT" and there should be no "crap" with it.
I guess this is really what I expected to hear. I really hoped somebody would have a better idea. Like, maybe they saw another company do something that they thought was a great idea and worked better than the standard email announcement. We do have a forum that I could use for announcements, however, only about 4 people have bothered to register there and it doesn't seem to be visited very often. I've actually been trying to use the newsletters to push people to the forum, so it's like a catch 22. If they don't read the emails, how can they find out about the forum? I just think the forum would be great because that kind of environment usually takes care of itself if you know what I mean.