[Nolug] Re[2]: [SAGE] Backup mail hosts?

I guess I don't understand the real problem here. If a mail server is
setup as the backup MX for my server, and accepts any and all mail to
my domain for store-and-forward, then when the mail hits my mail
server we will perform spam/virus filtering and bounce any mail to bad
email addresses. So, other than resource usage, why would the backup
MX server need to know more details about my mail service? :-)

---
Puryear Information Technology, LLC
Baton Rouge, LA * 225-706-8414
http://www.puryear-it.com
Author:
  "Best Practices for Managing Linux and UNIX Servers"
  "Spam Fighting and Email Security in the 21st Century"
Download your free copies:
  http://www.puryear-it.com/publications.htm
Tuesday, September 26, 2006, 1:27:15 PM, you wrote:
> At 11:18 AM -0500 9/26/06, Dustin Puryear wrote:
>>  As with many small companies, at times our mail server goes down
>>  (repairs, etc) and we end up getting deferred mail destined for us.
>>  That would be fine, but a lot of people (and automated processes)
>>  don't like getting the Delayed Delivery messages.
> Problem is that the backup mail server needs to implement all the 
> exact same anti-spam policies that the primary does, and also needs 
> to know who all the valid local users are from the primary mail 
> server.
> These days, hardly anyone I know of tries to use an alternative 
> backup MX that they don't operate themselves, so that they can make 
> sure that the two sets of systems are in complete sync.
> Another alternative is to out-source your primary mail service, for 
> example to a mail filtering company like Postini.  Let them handle 
> the mail backlog, should your primary go down.
>>  To counter that, we are interested in a backup mail service. There are
>>  some offerings from companies that provide DNS service (e.g.,
>>  zoneedit.com). There may be others. Does anyone have suggestions,
>>  comments, or criticisms about these services?
> I've actually been thinking about ways that we might be able to put 
> together a co-op to do backup MX services for our members, and try to 
> provide tools to them to automatically and adaptively handle the 
> problems mentioned above.
> If you want to discuss this concept in more depth, please let me know.
___________________
Nolug mailing list
nolug@nolug.org