text_combined: alexey lobanov wzctiyyscrorctru hi werner 12022008 2329 werner vd merwe пишет hi alexey thank much response must admit though fairly new postfix never worked ldap commands bit foreign sure really need ldap current sql setup may exactly ldap standard option corporate environment many applications able use database directly ie addressbook muas samba fileshare mswindows domain controller etc understand correctly assign user remote branch alternate email address correct store address ldap sql address purely internal neither used humans visible humans used mua settings specify postfix server domain transport either postfix via smtp intelligent mail storage system via lmtp depends upon mail storage system really hope use pop3 downloads workstation corporate environment happens remote side though inverse side map users primary site alternate email address actually primary site system postfix configurations identical except unique myhostname mydestination names delivery really twostage first stage original treated locally destinated translated routed specificserverexamplecom machine second stage treated local mydestination delivered local mailbox second stage done postfix lmtpcapable storage system success inverse yes also feasible use independent postfix feature sender_canonical_maps rewrite nonuniform sender addresses mailalternateaddress qmail schema corporatestandard canonical mail however really necessary beginning deploy system set correct domain local parts individual mua settings real need sender_canonical_maps appears maintenance stage change corporate mail domain management orders mandatory pelhkiyexamplecom instead staff apologies misunderstood must say setup sounds nifty well done seems quite natural use postfix lookup tables alexey thank advance werner original message alexey lobanov mailtowzctiyyscrorctru sent 11 february 2008 0933 pm werner vd merwe rljdsngxyqohpostfixorg subject muliple site single domain 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 065011 0300 muliple site single domain