-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 On 15-12-2010 22:14, Bobby Reyes wrote: >> It is not clear to me how you configured your DNS servers. >> >> If you have SRV1 dealing with all email for pb.xxx.com and SRV2 >> dealing with all email for pb2.xxx.com, email will be forwarded >> according to your settings. > > My two servers (SVR1/old and SVR2/new) are part of an internal network. > SVR2 relays to SVR1 which then relays to our corporate MX server for > external mails. > Internet <--> Corporate MX <--> SVR1 <--> SVR2 > @pb.xxx.com @pb.xx.com/@pb2.xx.com > > Suffice to say that mails from the outside addressed to pb.xxx.com gets > relayed to SVR1. > > Both SVR1 and SVR2 are intended to serve pb.xxx.com. SVR1 has all the mail > accounts but just forwards mails (using .qmail) for the migrated accounts > to SVR2 as @pb2.xxx.com. This part is already working. > > Anyway, my pending concern is how to setup SVR2 (qmail-ldap) so that mails > from it addressed to pb.xxx.com is delivered locally (i.e. do not have to > be relayed to SVR1) if the addressed mail account has a > mailAlternateAddress pb2.xxx.com in LDAP.
That's exactly what I said in the beginning of the thread, I'm not sure you can do it without using an external program and a .qmail. When SRV2 gets a new message to pb.xxx.com is queries if the DOMAIN is local or not and then proceeds to relay (or not). Considering this, the mailAlternatedAddress won't be checked by qmail services themselves. You should try the other way around, same thing you did in SRV1. Make pb.xxx.com a local domain and for the accounts no migrated you force-relay it to SRV1. > Here are my config files: > 1. qmail-ldap configuration > > $ /var/qmail/bin/qmail-showctl > > me: My name is pb.xxx.com > defaultdomain: Default domain name is pb2.xxx.com > defaulthost: (Default.) Default host name is pb.xxx.com This is rather strange. :) > locals: > Messages for pb2.xxx.com are delivered locally. > me: My name is pb.xxx.com. > rcpthosts: > SMTP clients may send messages to recipients at pb.xxx.com. > SMTP clients may send messages to recipients at .com. > SMTP clients may send messages to recipients at .net. > SMTP clients may send messages to recipients at .org. > SMTP clients may send messages to recipients at .edu. > SMTP clients may send messages to recipients at .ph. > SMTP clients may send messages to recipients at .es. > SMTP clients may send messages to recipients at .hk. > SMTP clients may send messages to recipients at .sg. > SMTP clients may send messages to recipients at .tw. > SMTP clients may send messages to recipients at .au. > SMTP clients may send messages to recipients at .ca. > SMTP clients may send messages to recipients at .uk. > SMTP clients may send messages to recipients at .us. > SMTP clients may send messages to recipients at .bs. Are you really sure about the above setup? [...] > Thanks a lot for the assist. I hope this helps. Kind regards, - -- Felipe Augusto van de Wiel <felipe.w...@complexopequenoprincipe.org.br> Tecnologia da Informação (TI) - Complexo Pequeno Príncipe http://www.pequenoprincipe.org.br/ T: +55 41 3310 1747 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQIcBAEBCgAGBQJNEiSnAAoJECCPPxLgxLxPfIsP/iF8A5dh/y6OHEWuby1v/Z3w Csx4UIn94329jkm4sfp9U6auDMl/LHKwYoFzYqRNocsaYnftvAL1fv/vXlgpFDeC sM7ub1A9LqRFTJUthXtThHgaM1Fhu697Ot3aUxOvx84Ime2nu/Hl/v9EwfOr563F 6YNkB11yvVrolKDq7/KojVQViyEOqFChhFDJkps+3N4e7Gmi5IPLCkvmNN32h8IS oXpxiT72o+Qu/bcHjiIRyo9dllRgKxU54SUUbAQvEGtVM/09SBxKDjwqCa8ZI45m 2uBd3S7HztH9Aa39b2gJ7KSrHga72JunXVP0sJyv6Fz0G+JvKbs0GuqWGSrKGt1E tFuXmMvR92v0YIuqGJY/QIVkkb1k523rE+lPjyqO6yRVY2e61wphq0KvcAFB0aTl 77ZvZAhQhMMlFGvzJWmOKYg33jPxk93YzNGbK5M+Ym1Tf0lvqrD1Ne5IzcNhHEzV DF/3NlrSEnbD9iK7ceFRqtK4s54J0CgThpXR1dsdW0FHXBQ/L13lxgEpRoShFXHS OnmK9Ifyf+LEQsyAC10wGFlnXZwIy8NsTGRHTGvtWQ21H4hvpN65oNG5jWpvMCjM 7AFgNf9/uKlDVwG8xFndD+8pBJbzetMzoUcR+cNBqjsJCVrRUJn3D+42naNlMhb2 yP2lMGQFtnaypvceVo/i =b+PL -----END PGP SIGNATURE-----
