I just had the same problem my solution for the moment is : MTA following LDAP mailhost attribute : SENDMAIL mailbox servers : QMAIL-LDAP, NMS
I don't know if you have the same situation than I, but my mailbox servers have to own some common domains. That's a big trouble in case of mail-forwarding from a server to the other ; because in that case QMAIL-LDAP forward the mail locally if it is for a domain that it own locally and no on the MTA. Or I don't know how configure that !! if you know !! thanx -----Message d'origine----- De : felipe [mailto:[EMAIL PROTECTED]] Envoy� : mercredi 12 d�cembre 2001 23:29 � : [EMAIL PROTECTED] Objet : routing hello, I'm in little complicated situation where I have a big _single_ domain, with multiple mta on multiple platform (m$ exchange servers too....) and I wont to migrate all my mta to qmail-ldap except the exchange one (obviously this choice didn't depend on me). For this reason I can't enable the clustering (I can enable it only for the qmail servers) function in qmail-ldap and I can't do routing based on the mailHost attribute in ldap. In this way, I don't know how to distribute correctly the incoming email to the appropriate server, having some problem designing a clean solution. I accurately (maybe) browsed the ml archive, and before making my own patch to enable the smtp routing based on the mailhost I try to ask for some hint. I undestand that the qmqp is a better solution for a lot of reason but sometimes it's not applicable, loosing some really nice features (this is only my tought, I don't want to start a war about it). Now is there a clean way to solve this problems in my situation ? Is there a combination of controls/ldapvalues that solve this problem ? Every hint is appreciated. tia felipe.
