strace did the job.
i had the wrong permissions on the certkey, the postfix user cant read it.
thx for help
2010/2/2 Wietse Venema :
> spamv...@googlemail.com:
>> thx Wietse
>>
>> trying it as user postfix i get (Can't contact LDAP server)
>>
>> hmm strange
>
> You have some incorrect file permi
On Wed, Feb 03, 2010 at 12:47:31AM +0100, Bernhard Schmidt wrote:
> On 02.02.2010 15:29, Victor Duchovni wrote:
>
> Hi,
>
>> And, use "proxy:ldap:${config_directory}/ldap-aliases.cf", LDAP servers
>> typically don't like the connection concurrency that results from each
>> smtpd(8) and cleanup(8)
Bernhard Schmidt:
> On 02.02.2010 15:29, Victor Duchovni wrote:
>
> Hi,
>
> > And, use "proxy:ldap:${config_directory}/ldap-aliases.cf", LDAP servers
> > typically don't like the connection concurrency that results from each
> > smtpd(8) and cleanup(8) using a separate connection. Don't do this,
On 02.02.2010 15:29, Victor Duchovni wrote:
Hi,
And, use "proxy:ldap:${config_directory}/ldap-aliases.cf", LDAP servers
typically don't like the connection concurrency that results from each
smtpd(8) and cleanup(8) using a separate connection. Don't do this,
however, with tables that are used b
spamv...@googlemail.com:
> thx Wietse
>
> trying it as user postfix i get (Can't contact LDAP server)
>
> hmm strange
You have some incorrect file permission, or some "security" software
such as SeLinux or AppArmor is mis-configured.
Try:
# service selinux stop
# service apparmor stop
thx Wietse
trying it as user postfix i get (Can't contact LDAP server)
hmm strange
2010/2/2 Wietse Venema :
>> [r...@testmail postfix]# postmap -q myn...@example.com
>
> Don't run the test as root.
On Tue, Feb 02, 2010 at 09:13:36AM -0500, Wietse Venema wrote:
> spamv...@googlemail.com:
> > hi..
> >
> > my postfix checks against openldap.
> > postfix first uses the ldap-aliases.cf to check if its a valid user
> > email, that works.
> > then i tried to use the same ldap-aliases.cf for smtpd_
spamv...@googlemail.com:
> hi..
>
> my postfix checks against openldap.
> postfix first uses the ldap-aliases.cf to check if its a valid user
> email, that works.
> then i tried to use the same ldap-aliases.cf for smtpd_sender_login_maps
>
> But that doesnt work.
> I get a:
> postfix/local[7683]:
hi..
my postfix checks against openldap.
postfix first uses the ldap-aliases.cf to check if its a valid user
email, that works.
then i tried to use the same ldap-aliases.cf for smtpd_sender_login_maps
But that doesnt work.
I get a:
postfix/local[7683]: warning: dict_ldap_connect: Unable to bind t
On Tue, Oct 21, 2008 at 12:06 AM, mouss <[EMAIL PROTECTED]> wrote:
> Steven Truong a écrit :
>> Dear, all. I am running into a scenario where I might need to deliver
>> the same incoming email for a user to 2 different IMAP servers.
>>
>> Is there anyway to implement it with Postfix with its vario
Steven Truong a écrit :
> Dear, all. I am running into a scenario where I might need to deliver
> the same incoming email for a user to 2 different IMAP servers.
>
> Is there anyway to implement it with Postfix with its various transport maps?
>
> I have for example [EMAIL PROTECTED] and I would
Dear, all. I am running into a scenario where I might need to deliver
the same incoming email for a user to 2 different IMAP servers.
Is there anyway to implement it with Postfix with its various transport maps?
I have for example [EMAIL PROTECTED] and I would like all emails for
this user to be
12 matches
Mail list logo
