From: Alain Spineux (aspineuxgmail.com)
Date: Tue Jul 18 2006 - 17:27:36 CDT

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

I'm not looking for a CLUSTER!

I just want to keep a copy of all emails going through the MX backup, and
keep them in mailboxes for one or two week.
I never need to resynchronize anything after.
If users want to keep a copy of the SentItems (when using the webmail), they
will need to BCC to themself.
This is just, when the main server is down, to answer the customer question
: I need to urgenly access my emails !

Maybe I did'nt explained well.

Best regards

On 7/18/06, Jorey Bump <listjoreybump.com> wrote:
>
> Alain Spineux wrote:
>
> > I would like to setup my secondary MX as a full email backup server.
> >
> > Each email reaching the secondary server must be queued to be sent to
> > the primary MX BUT also be delivered into a local mailbox. These emails
> > will be available through a webmail during the time the primary MX is
> > unavailable (and also after). The relayed emails will reach the primary
> > MX and be delivered localy as normal.
>
> Don't do this. There is a reason (actually many) why mail transport is
> separated from mail access. Look at solutions to replicate your mail
> store instead, or you will create a huge unfathomable mess for your users.
>
> > Something I dont have to forget: The secondary MX will be
> > configured to never report any problems when delivering emails locally
> > (mailbox over quota, user not found ...)
>
> Ugggh... And how do you expect to reconcile all of this when your
> primary comes back up? A secondary MX is intended to be a backup for
> SMTP, not POP/IMAP. Keep the concepts cleanly divided, even if you
> implement them on the same machine.
>
>
--
--
Alain Spineux
aspineux gmail com
May the sources be with you

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]