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

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

Hello

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.

I thing a way is to use

recipient_bcc_maps

with entries like

domain1_to_backup.com domain1.local_domain.net
domain2_to_backup.com domain2.local_domain.net
domain3_to_backup.com domain3.local_domain.net

and having

mydestination=domain1.local_domain.net, domain2.local_domain.net,
domain3.local_domain.net
relay_domains=domain1_to_backup.com domain2_to_backup.com
domain3_to_backup.com

But this way, I cannot reuse any database, for example a LDAP user
database used by the primary MX (for aliases)

The thing I need is something like

domain1_to_backup.com :[localhost]:10025
domain2_to_backup.com :[localhost]:10025
domain3_to_backup.com :[localhost]:10025

with another smtp instance running on port 10025 and configured the
same way as the PRIMARY MX, reusing the same user database, aliases ...

BUT recipient_bcc_maps doesn't accept this kind of notation used by
transport_maps

Any idea ?

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 ...)

Alain

--
Alain Spineux
aspineux gmail com
May the sources be with you

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