On Email Spooling, MX records, and hosting

Hi.  Our company has our own domino email server.  We also have our website hosted externally.
Currently, I have an MX record setup on our hosting provider that points to our mail server.
This works fine, but on occasion i think we are losing email as we have no spooling.
Our hosting provider will not spool email for us either.
Here is what I would like to have:

1. our website hosted externally
2. incoming email cleaned of spam
3. all email for our domain sent directly to our mail server (not POP'ped)
4. when our mail server does not respond, the email will spool

Is it common for hosting providers to offer services that match what I am requesting, and who would you recommend?
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

We have virtually an identical setup.  Until recently, we hosted our own filtering solution but have now outsourced which is working GREAT!  With our particular service, we have just as much control over the filters and it is extremely reliable.  We personally use Berbee Mail Protection Services (www.berbee.com), but I'm sure there are many many out there.  

You get all this information from the provider, but basically just change your MX records to use the provider.  The provider cleans the mail, sends it directly to your mail server.  If your mail server goes down, the provider holds it until you're back up.  With Berbee, it is several days at least.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
there are several providers who offer website and email hosting. they offer different type of plans. so depened on your needs and how many emails you want and the size needed. for example fatcow.com offer plans for $100 a year with 100 emails and hosting a website in addition to some ftp and other service. many others offer similar plans with different prices.

But I would recommand that since you have a server with static ip, then leave it on all the time. that way you won't have problems with space as it is the number 1 problem if you are using third party provider. you can also have another mail server for when the other server is down.

hope this helps!
You DON'T want spooling.  Let the sender's server queue the mail and retry later.  That way, when your server comes back online, the sender's server connects to yours and gives you the mail.  The key is if any of it is addressed to a non-existant address, it gets rejected.

If you spool, the spooling server ends up accepting all of that mail, and then has to deal with the bounceograms (which are often useless anyway).  Worse, spammers will send to your spooling server even when your primary server is reachable, bogging it down further.
SolarWinds® Network Configuration Manager (NCM)

SolarWinds® Network Configuration Manager brings structure and peace of mind to configuration management. Bulk config deployment, automatic backups, change detection, vulnerability assessments, and config change templates reduce the time needed for repetitive tasks.

bctekAuthor Commented:
"The key is if any of it is addressed to a non-existant address, it gets rejected."

Would not this be the case in spooling as well?  Spooling (correct me if I'm wrong) is simply a second MX record of lesser priority, where another company hosts the server that MX record points to.  It simply colllects mail and tries to "push it".  If an address doesn't exist on our server, it gets bounced, spool or no spool.
If the address doesn't exist on your server, it gets bounced.

A spooling server is (as you said) a second MX of lesser priority, configured to RELAY mail to your domain(s) BUT NOT ACCEPT THE MAIL LOCALLY (it doesn't have the mailboxes available to it).

If an email to a non-existant address arrives on the spooling server, it must accept it, since it doesn't know the list of legitimate addresses, then send it to your primary server, at which point it gets bounced, and the spooling server has to try to send the bounceogram back to the sender.  Your spooling server is now doing the work that the spammer's server had to do before.  That's bad.
I respectfully disagree with pjtemplin :)   I understand what he's saying, but you're not eliminating any work for your server since it still has to send the delivery failure.  Yes, the spooling server has added load, but who cares?  You're paying for the spooler/spam filtering service, plus they know what they're getting into and have the infrastructure to support it.  Not all incoming email is spam, almost but not quite ;-)  Without a lesser priority MX record there to hold your mail, you could potentially bounce back valid messages to valid senders.  Now they're wondering why your company is rejecting mail and I don't think that looks real good for your company.  With a spooler, you can have down time and no one is the wiser.  You're not racing the clock so you get back up before delivery failures get sent back to valid senders.  Highly recommended!
The objective was not to lighten the load on the main server, or if it was it was not clear.  Regardless, the main server doesn't have to SEND a delivery failure today; it merely REJECTS the mail before the content is ever sent.

If the spooling server accepts the mail, when it attempts to send the message to the primary, the primary rejects the mail before the content is sent.  Now the spooling server has to attempt to send a delivery failure.  That's the extra load.  Add in the fact that spammers will send to the spooling server without trying the primary, and you've added significantly more load.

How long is your server not accepting mail?  More than a day straight?  More than five days straight?  Why isn't it accepting mail?  If it can't handle the load, the spooler might help but might hurt.  If you're losing connectivity for less than a day, the sender's server will queue the mail and retry for typically 3-5 days, and you're fine.

Learn the intricacies of an actual SMTP conversation, and you'll see what I mean.
bctekAuthor Commented:
thank you both for your very informative posts.  Having the point-counterpoint really helps me have all the tools I need to make an informed decision.  I have to assign an "accepted answer" so I will default to the first answer.

thanks again.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.