[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kolab-users
Subject:    Re: master/slave setup via VPN?
From:       "Alain Spineux" <aspineux () gmail ! com>
Date:       2008-07-18 22:46:57
Message-ID: 71fe4e760807181546v704106d1p13d34051bcdba055 () mail ! gmail ! com
[Download RAW message or body]

On Fri, Jul 18, 2008 at 10:38 PM, Thorsten Schnebeck
<thorsten.schnebeck@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@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

> So, I need a config that transfers the Std-IP of slave to its VPN-IP but only
> for postfix. IMHO I can not use transport.db cause I have users of
> maildomain2.com on master _and_ slave.(?)
>
> Suggestions?
>
> Bye
>
>  Thorsten
>
> _______________________________________________
> Kolab-users mailing list
> Kolab-users@kolab.org
> https://kolab.org/mailman/listinfo/kolab-users
>



-- 
Alain Spineux
aspineux gmail com
May the sources be with you

_______________________________________________
Kolab-users mailing list
Kolab-users@kolab.org
https://kolab.org/mailman/listinfo/kolab-users
[prev in list] [next in list] [prev in thread] [next in thread]