On 22.12.2010 17:17, Felipe Augusto van de Wiel wrote: > 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,
Hello Bobby I did not read the whole thread, but ... I think the easy way to this, is to set-up the two servers as a qmail-ldap cluster, and use the mailHost LDAP attribute for the accounts, to steer delivery to the right server for any user. The servers then just know what to do by themself, unrelated to address, alternateAddress or domain.No .qmail files or external programs needed. Just my two swiss cents. Alain Wolf
