Hi GrayHat,

thank you for taking your time giving me helpful advice :)

I took another approach. I don't have so many users so I directly export 
the mailservers addressbook into a file via a cronjob (also doing a 
chown and chmod afterwards).
The file consists of just mail addresses, each line an address as described.



Then I changed /LocalAddresses_Flat to file:files/addresses, turned off 
DoLDAP and changed Ldaplistdb to empty./ <javascript:void(0);>
This was yesterday and I restarted ASSP a few times since then.
In the logs, I can see that it correctly looks up valid local addresses 
using the file I specified and mail is coming through. Otherwise it 
would reject all mails of course..

But still, I see that often Workers get stuck at LocalLDAPDomain.

How's that possible? Do you or anyone know what could be the reason for 
that?


Thank you!

Cheers,

Max



(btw: ldLDAP is off anyway)

GrayHat wrote:
>  
>   
>> Sad enough Fritz's simple solution about what to try, which 
>> MIGHT work, doesn't.  Of course it's not an assp issue.
>>     
>
> Yes, I suspected so; sure, setting up the same LDAP server
> as primary/alternate may help a little, but if the server doesn't
> answer for some "long" interval that won't solve the issue, and..
> yes, it definitely isn't an ASSP issue; something isn't working
> as needed in your infrastucture :(
>
>   
>> I will do as you suggested and setup an additional openldap server.
>>     
>
> That may allow to fix the ASSP issue, but the fact that the LDAP
> server is unresponsive at times may indicate some ongoing issue
> and I think you'd better investigate (and solve) before the cause
> of the problem may cause further issues and "explode"; setup
> your LDAP system to monitor performances and also increase
> the various logging levels, that may help you finding out what's
> going on and fixing the issue before it gets worse
>   


------------------------------------------------------------------------------
Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
Assp-test mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/assp-test

Reply via email to