________________________________

From: owner-postfix-us...@postfix.org
[mailto:owner-postfix-us...@postfix.org] On Behalf Of Kenneth Kalmer
Sent: Tuesday, 6 January 2009 11:49 PM
To: Postfix users
Subject: Re: Using Postfix for business continuity


        On Mon, Jan 5, 2009 at 3:25 PM, Wietse Venema
<wie...@porcupine.org> wrote:
        

                Kenneth Kalmer:
                
                > Hi all
                >
                > Just got asked by one our sales guys if we could
implement a Postfix
                > business continuity service, by his definition it
means that Postfix acts as
                > a normal backup MX but gives the users access to their
email via webmail of
                > sorts.
                >
                > I understand the issues of user authentication,
validating users, etc.
                >
                > I'd just like to find out if anyone has implemented
something similar, or
                > have any pointers for implementing something like
this.
                
                


        The way we envisioned it it would be an offsite server acting as
a normal backup MX, giving the users access to their email through a web
interface. This would involve reading through the spool files, which for
high volumes would be horribly slow.
        
        Most of our potential clients would be running MS Exchange (I
see this as the continuity issue) and we'll be far removed from them.
         

________________________________

Exchange 2007 has pretty good clustering and cross-site replication
(using log-shipping) these days. Of course, any replication partner
would need to be in the same domain, but it might be possible to host
several instances on one box using a virtual server solution. Naturally,
if a business has multiple sites, they'd be much better off doing any
replication internally anyway.

Otherwise, Victor's suggestion about BCCing everything and hosting an
IMAP server is the best other option (given all the account
co-ordination hassles).

Reply via email to