alexey lobanov wzctiyyscrorctru hi werner run similar configurations many years difference replicated ldap database instead postgres ldap used samba file services sites configured single mail domain declared mx records domain maximal priority assigned biggest site majority workers reside minimize unnecessary intersite traffic actially every postfix works quite simple forwarder identical rules ldapforward_domain exampleru nb exampleru listed mydestination ldapforward_query_filter mailsmailalternateaddresssmailalternateaddressuuiduaccountstatusactiveaccountstatusshared ldapforward_result_attribute mailforwardingaddress ldapforward_bind mailforwardingaddress personal email address internal domain pointing home server user must use internal domain internal ipaddress space via vpn sites external ipaddresses essential important trick lmtp localfinal delivery instead smtp defined transport table internal domains mail sent postfix directly cyrus imap lmtpcapable mda destination server however essential also optimization trick scheme works every postfix knows also unique internal domain name mydestination knows local delivery transport anyway message injected local workstation internet difference postfix server always forwarded home server addressee one lmtp smtp hop site offline reason ones stay operational may receive mail internet normally user migration trivial ldap schema known qmailschema btw next part setup cyrus imap cluster aka murder user connects nearest imap server sees inbox available shared folders branches list alexey 11022008 2132 werner vd merwe пишет would love able cape town remains primary mx domain intelligently routes specified users branch work inversely deliver mail local users local mail branches wed 06 aug 2008 051321 0300 muliple site single domain