search for: pass_s

Good evening everyone, I'd like to paste a problem i experience the last days with a mail cluster system based on three dovecot servers and two directors in front of them. The Directors are proxying the auth requests to the dovecot servers below (LDAP). The protocols i use are imap/managesieve/lmtp.? The setup works as intented, exept one detail. There are a lot of users that happen to

Dear Ioannis, > I've searched around for a solution to this, and figured out that a special > userdb {} section in the protocol lmtp {} section, with driver = ldap etc etc > so that i 'd be able to "show" the correct user to the lmtp might work, but > strangely that userdb {} setting looks like being ignored by lmtp. A very similar issue was discussed on IRC last

hello all, A small patch that fixes Query get_description in testsute3.py. see the attachment. -- Best Regards, Xiaona Han -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.xapian.org/pipermail/xapian-devel/attachments/20120409/18a07efb/attachment-0001.html> -------------- next part -------------- A non-text attachment was scrubbed... Name:

hi.. im just testing 2.0 before upgrading to v1.2 :) in auth-ldap.conf.ext i found # If you don't have any user-specific settings, you can avoid the userdb LDAP # lookup by using userdb static instead of userdb ldap, for example: # <doc/wiki/UserDatabase.Static.txt> #userdb { #driver = static #args = uid=vmail gid=vmail home=/var/vmail/%u #} On 1.2 im using LDAP lookup and

Here is the applicable article: http://www.linux.com/feature/125548 There are links in the above article that explain tests for the system and what is currently known about the rootkit. Apparently initial access is NOT via any vulnerability but just guessed root passwords. There are currently 2 methods to see if you are infected: 1. In some cases, the root kit causes you to not be able to