>No problem. The diversity of solutions is what makes newsgroups invaluable.
>A solution for a small company like ours may not work for a larger company.
>Here's why this solution worked for us.
>If the T1 goes down, sometimes it could take hours to a day to bring it back
>up, depending on the cause. We are not staffed 24/7, so an outage over the
>weekend spells trouble for us.
"Normal" priority SMTP messages don't usually time out in that short a
period of time. "Urgent" messages might, but if they're urgent, why
would the originator want them to sit on a secondary MX until you get
around to getting your server back on line.
Quote:>If we reported it Mon am, it is possible that our mailserver has been
>unavailable for several days (Fri eve- Mon afternoon, assuming a quick fix
>to the T1 problem). A second server wouldn't help in this situation.
I think I'd be looking for another provider if that happened more than
once. Of course, if e-mail is that important, a second connection from
another provider would fix the problem and give you nice warm feeling
Quote:>Our AV solution wouldn't have helped with the luv virus. It took several
>hours for Symantec to release a definition, and a good portion of our
>customer base (gov't) was spewing propagation messages wildly.
We all suffer from these problems, occasionally. Stopping the MTA
would have prevented any outbound leakage. Inbound mail could have
waited a few hours on the originator's servers until you had the new
Quote:>Our ISP is very helpful and provides a number of addon services to
>compliment our own. They are happy to do it, and less overhead for us. For
>example, we host our website with the ISP instead of internally. No DMZ
>issues, no outage headaches, and most importantly, reduced cost.
HTTP and SMTP are pretty different. Letting someone else host your web
site is usually not a bad idea since they've already spent the money
to harden (you hope) their servers.
Quote:>The cost of
>a high bandwidth connection to support a website and all your corporate
>traffic vs the cost of having a high bandwidth ISP host your site, and not
>worrying about the Sat am calls because the mission critical website is down
>is heavily weighted towards using the service of the ISP.
Mission critical and outsourced don't usually go well together.
Quote:>I started and operated an ISP years ago. I sold it when the market was hot.
>The early am and weekend troubleshooting gets old really fast :-)
I spend over 20 years in tech support. Tell me about it.
>Bounced email happens. It depends upon the resend settings on the sending
>server, and the weekend scenario I mentioned could definitely exceed the
>typical 48hr threshold.
>You are correct in saying that unanswered emails can cause a similar poor
>impression. It's sort of like calling a business' telephone number and not
>getting an answer. That's bad. But it's worse to call and hear, "...number's
>been disconnected..." Lesser of two evils, I guess.
But your server being offline would be the equivilent of "all our
circuits are busy", not a disconnected number. :)
Quote:>People like you with lots of knowledge and probably lots of resources can
>setup redundant solutions and creative configurations, and that's great.
Well, it's the company with the resources, not me. :)
>probably works better. But I get the impression from reading many of the
>postings that there are a lot of people here who don't have you degree of
>knowledge and are looking for easy, cheap solutions.
If you find that combination, let me know. Most are hard and
Quote:>Call your ISP and in
>about 5 minutes you're finished. They'll most likely have it up within a
>day. Doesn't get much easier :-)
I guess you haven't been reading all the problems /caused/ by ISP's,
then? I'll quote someone else: "All ISP's suck. Some just suck less
Quote:>Our ISP charges $25/month for the backup MX. In my book that's a nobrainer.
>Saves cost of server, hassle of outages, etc, etc.
Most folks here can't even find an ISP that'll handle SMTP at all!
Quote:>Basically, if you've got the extra server and resources, build a better
>solution. Else, some of us operating on a tight budget are looking for
>inexpensive and simple solutions.
An even cheaper solution is to find another company (or whatever)
that's willing to provide that service to you if you'll provide it to
Quote:>BTW, I look forward to reading ALL solutions and suggestions for issues,
>even though it may not fit my situation. Keep the alternatives coming!
MCSE+I, Exchange MVP
MS Exchange FAQ at http://www.swinc.com/resource/exch_faq.htm