11 msgReject unknown Sender address
10 msgPostfix and archiving
5 msg-o content_filter overrides main.cf ?
1 msgPostfix 2.4.3 and 2.3.11 available
8 msgSASL authentication via dovecot?
2 msgpostfix/sasl: sql_select option missing - wtf?
3 msgmax connection rate/count/limit issues.
1 msgrequeue mails
6 msgnothing in maillog
9 msglocal and remote storage for same user
7 msgRejecting Invaliud Users - Useful Resource poin...

Distributing map files
\ Martin Schmitt (31 May 2007)
. \ Bastian Blank (31 May 2007)
. \ (Wietse Venema) (31 May 2007)
. . \ Martin Schmitt (31 May 2007)

5 msgrelay_recipient_maps for multiple destinations
13 msgauto-responders with postfix
6 msgMydestination with virtual domains
6 msgSplitting smtpd_proxy_filter in smtpd_recipient...
10 msgCan't Send to Sprint Messaging Users..
1 msgMAAWG meeting anyone?
2 msgbasic postfix 2.4.1 configuration for a simple ...
5 msgStrange persistant 'timeout after DATA' from ma...
Subject:Distributing map files
Group:Postfix-users
From:Martin Schmitt
Date:31 May 2007


 

Hi all!

I have a system in place, where raw map files are copied over to a
number of target machines, and then postmap is executed remotely via
SSH. While this has never failed, I have my issues with this method and
don't feel in control all the time. For a start, I would prefer to not
have to execute commands on a herd of remote machines and not have to be
prepared for every error that might occur.

Wouldn't it be more reliable to prepare the map files on the central
management server, postmap them locally and copy them over via rsync and
leave handling of remote I/O errors to rsync?

Is there anything wrong with the rsync approach and distributon of
ready-made map files? What do you think?

-martin

--
Schmitt Systemberatung Linux/UNIX
Giessener Str. 18 Internet/Intranet
35415 Pohlheim/Germany E-Mail Infrastructure
http://www.scsy.de Antispam/Antivirus




© 2004-2008 readlist.com