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

List:       kolab-users
Subject:    Re: master/slave setup via VPN?
From:       Thorsten Schnebeck <thorsten.schnebeck () gmx ! net>
Date:       2008-07-21 15:14:15
Message-ID: 200807211714.15159.thorsten.schnebeck () gmx ! net
[Download RAW message or body]

Am Monday 21 July 2008 um 13:19:39 schrieb Thorsten Schnebeck:
> Am Monday 21 July 2008 um 12:35:37 schrieb Thorsten Schnebeck:
> BUT...
> now some mail servers do not like my server anymore:
> status=deferred (connect to gmx.net[213.165.65.50]: Connection timed out)
>
> If I change this back to "no" everything is fine
> relay=mx0.gmx.de[213.165.64.100]:25, delay=1087,
> delays=1087/0.05/0.13/0.17, dsn=2.6.0, status=sent (250 2.6.0 Message
> accepted {mx007})

> So, while this option helps for my local vpn setup, is a showstopper for my
> global system.

master to slave transport is explicit controlled by
/kolab/etc/postfix/ldaptransport.cf
This generates an smtp:[slave-domainname] transport for every multi domain 
user with home server != master server. 

But when I know this is a master-slave connection nobody forbids me to disable 
DNS lookups in master.cf as special service:

ms_smtp    unix  -       -    n    -    -   smtp -o disable_dns_lookups=yes

and in ldaptransport.cf
--  result_filter = smtp:[%s]
++  result_filter = ms_smtp:[%s]

Looks like this works. Objections from anyone?

Bye

  Thorsten


_______________________________________________
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]