Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Doing real time backup....with recipient_bcc_maps.

79 views
Skip to first unread message

Christophe Dumonet

unread,
Jun 20, 2005, 2:54:41 AM6/20/05
to
Hello,
I 'm looking to do real time backup with postfix,
Actually, I'm doing backup every hour with an RSYNC automated script,
but It is very long to perform....

I think it is possible with recipient_bcc_maps, which copy mails to an
other mailbox for each user,

Is there another possibilities ?Howto do backups with recipient_bcc_maps ?

Thanks a lot for your help.

Best Regards, From French network admin ;-)
----------------------------------------------------
Christophe Dumonet
Centre de Ressources Informatiques
Institut Français de Mécanique Avancée - IFMA
Campus de Clermont-Ferrand - Les Cézeaux
BP 265
63175 AUBIERE Cedex
Tel : 04-73-28-80-64
Fax : 04-73-28-81-00
Mail : Christoph...@ifma.fr
----------------------------------------------------


Damien Mascord

unread,
Jun 20, 2005, 5:21:06 AM6/20/05
to
Christophe Dumonet wrote:
> Hello,
> I 'm looking to do real time backup with postfix,
> Actually, I'm doing backup every hour with an RSYNC automated script,
> but It is very long to perform....
>
> I think it is possible with recipient_bcc_maps, which copy mails to an
> other mailbox for each user,
>
> Is there another possibilities ?Howto do backups with recipient_bcc_maps ?
>
> Thanks a lot for your help.
>
> Best Regards, From French network admin ;-)

Hi Christophe,


Other than using recipient_bcc_maps [
http://www.postfix.org/postconf.5.html#recipient_bcc_maps ] , you can
use maildrop.

I would probably recommend the recipient_bcc_maps rather than using
maildrop (so that your headers aren't munged too much!).

recipient_bcc_maps behaves the same as any of the other map types, such
as your virtual_alias_maps, so a hash file of bcc recipients based on
your recipient should be easy enough to figure out?

This would be also possible using maildrop, and having all mail go
through the maildroprc.

So, virtual_transport = maildrop

Then in your maildroprc:

cc "! backup_ema...@example.com"
to $DEFAULT

You can even have it backup to a Maildir/ rather than have it bounce for
each email address.

You can also use the courier-mta version of maildrop, and along-side
userdb, have a seperate .mailfilter file that allows you to specify a
different.

Damien

0 new messages