master/slave setup via VPN?

Thorsten Schnebeck thorsten.schnebeck at gmx.net
Sun Jul 20 13:32:57 CEST 2008


Am Samstag 19 Juli 2008 schrieb Alain Spineux:
> On Fri, Jul 18, 2008 at 10:38 PM, Thorsten Schnebeck
>
> <thorsten.schnebeck at gmx.net> wrote:
> > Hi,
> >
> > I'm trying to use a Kolab-2.2 master/slave multi-domain setup with one
> > special detail: The smtp communication is only via vpn available.
> >
> > Lets create an example:
> >
> > master.domain1.com: IP 1.2.3.4 + VPN 10.10.10.1
> > slave.domain2.com: IP 4.3.2.1 + VPN 10.10.10.2
> >
> > on master I have users of the mail-domains maildomain1.com,
> > maildomain2.com on slave I have users of the mail-domains
> > maildomain2.com(!), maildomain3.com
> >
> > master collects all mails of all 3 maildomains.
> > If the users has its mailbox on slave if see something like this in the
> > master postfix log:
> >
> > connect to slave.domain2.com[4.3.2.1]: Connection timed out (port 25)
> > Jul 18 21:48:39 master <info> postfix/smtp[5227]: 72668274971:
> > to=<test at maildomain3.com>, relay=none, delay=3350, delays=3320/0.06/30/0,
> > dsn=4.4.1, status=deferred (connect to slave.domain2.com[4.3.2.1]:
> > Connection timed out)
>
> You can add this entry in /etc/hosts
>
> 10.10.10.2               slave.domain2.com

Hmm, does not work :-(
When I ping to slave.domain2.com now it pings to 10.10.10.2
but postfix still want to deliver to the real IP. I also insert

smtp_host_lookup = native,dns

into  /kolab/etc/postfix/main.cf but this somehow does not change anything.
Using transport does also not work. Maybe a conflict with Kolabs homeserver 
ldap settings? 

Any ideas?

Bye

  Thorsten




More information about the users mailing list