Thanks to everyone for helping me out! Now I know what was wrong.. stupid me had set a very high limit to URIBLMaxTime. I can't remember how that happened or why I did that as I have only 3 uribl providers in use anyway.
After changing the value to default settings of 10 seconds, "worker stuck at LocalLDAPdomain" never happened again! I think this error message/category is VERY misleading as the root cause of those problems had nothing to do with any LDAP or verify issues.. I have set ASSP to validate through LDAP again and everything works really good since a week. It never happened again. I'm very glad that this issue is gone. Thanks for all your support! Max On 04/22/2010 12:19 PM, GrayHat wrote: > > >> Thanks a lot for ANY help you can give me as this >> is really really bad :( >> > I'd start from "scratch"; I mean; make a backup of your > ASSP, wipe the folder and start with a full scratch install > ensuring to run the modules installation script; next run > the ASSP from cmdline (no daemon/service mode) > and proceed configuring it; don't set up LDAP just set > up VRFY/EXPN (ensure to use the correct syntax in > your localdomains file, that is domain=>vrfy_host:port) > and check if that solves the issue, then move on setting > the other parameters referring to your backed up config > file and... in case of issues roll back the config from the > last change you made :) > > > > ------------------------------------------------------------------------------ > _______________________________________________ > Assp-test mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/assp-test > ------------------------------------------------------------------------------ _______________________________________________ Assp-test mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-test
