jeanmichel dault sgvcjctrevolutionlinuxcom le mercredi 20 février 2008 à 1912 0500 wietse venema écrit jeanmichel dault im trying convert large organization 80000 email entries 72 domainssubdomains sendmail postfix ive hit brick wall theyre using following schema httpwwwsendmailorgm4lasertxt would need map like yqzisythtfidomain ervvrealdomain smtpserverotherdomain use postfix virtual aliases change message headers rewrite yqzisythtfidomain ervvserverotherdomain thanks wietse unfortunately solution work organizations context others use sendmail routing feature think examples help understand problem lets forget postfix ldap particular technology focus available data lets suppose tabdelimited file information need realpublicaddress mailroutingaddress mailhost jbrjvokiexamplecom fywqdllocaldelivery smtp10111213 iwzxrhwasexamplecom fywqdllocaldelivery smtpexchange04int frlgkffcgexamplenet dxcxixlocaldelivery smtpgroupwise01int cxjzsaueszexamplecom aqwdtbotherispcom empty use default need 100 compatible sendmail behavior quoting httpwwwsendmailorgm4lasertxt mailhost mailroutingaddress present mtas must interpret main messages routed host indicated mailhost rewriting envelope per mailroutingaddress requirement lookup must public address since internal routing address duplicated many departments manage accounts mail servers options point 1 find way postfix without much modifications 2 continue use sendmail already working 0 cost spend rest eternity m4 hell 3 tell client modify 80000 users modify ldap schema reconfigure mailservers modify user management code etc know wont easy hope option 1 possible sendmail couldnt postfix thanks advance jeanmichel dault révolution linux inc thu 07 aug 2008 143555 0500 migrating sendmail ldap routing