search for: auth_count

...uration file, I can't find any guides for optimal values to use for dovecot's many configuration options. A few that look like they might need changing are: login_process_size = 32 login_process_per_connection = yes login_processes_count = 3 mbox_dotlock_change_timeout = 30 auth_count = 1 client_workarounds = Does anyone have any pointers to reasonable values for those or other settings? Thanks -- Ian

...tty stable. - Keyword support finally included. Not too well tested, but I couldn't get it to break. Doesn't store the keywords into maildir/mbox yet. Hopefully soon. - Major reorganization of code in dovecot-auth, and not yet finished. Load balancing between multiple auth procsses (ie. auth_count > 1) was before done by connecting to each one's socket separately. Now there's a single socket which a balancer process listens to and distributes the requests to worker processes. What's left to do is make a single auth process support handling multiple auth sections in config fil...

Here's a patch that implements mysql authentication. I started with the pgsql files and tweaked them to use mysql instead. It works for me, but there might be a couple of memory leaks. I'm welcome to suggestions on how to clean it up so it can be committed. Enjoy! Matt -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name:

...config file (stripped comments): protocols = imap imaps pop3 pop3s imap_listen = 192.168.0.2 pop3_listen = 192.168.0.2 imaps_listen = 192.168.0.2 pop3s_listen = 192.168.0.2 login = imap login = pop3 auth = default auth_mechanisms = plain auth_userdb = passwd auth_passdb = shadow auth_user = root auth_count = 1 auth_verbose = yes auth = truc auth_mechanisms = plain auth_userdb = passwd auth_passdb = passwd auth_verbose = yes if i try a user with shadow, it works, but if i try a user without shadow, it fails in the log with dovecot-auth: shadow(taz): unknown user what's wrong, why doesnt it us...

.../pop3 auth = cram-md5 auth_mechanisms = cram-md5 auth_realms = auth_userdb = passwd static uid=8 gid=8 home=/var/mail/virtual/%d/%u auth_passdb = passwd-file /etc/dovecot/cram-md5.pwd auth_user = dovecot auth_chroot = auth_executable = /usr/lib/dovecot/dovecot-auth auth_process_size = 256 auth_count = 1 auth_username_chars = abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@ >> Thank you in advance for any help.

...un/dovecot maildir_copy_with_hardlinks = no maildir_check_content_changes = no overwrite_incompatible_index = yes umask = 0077 auth = default auth_methods = plain #auth_realms = auth_userinfo = shadow auth_executable = /usr/local/lib/dovecot/imap-auth auth_user = root auth_chroot = /var/run/dovecot auth_count = 1 #auth = digest_md5 #auth_methods = digest-md5 #auth_realms = #auth_userinfo = passwd-file /etc/passwd.imap #auth_user = imapauth #auth_chroot = /var/run/dovecot/auth

...executable = /usr/libexec/dovecot/pop3 pop3_process_size = 256 auth = passwd auth_mechanisms = plain auth_realms = auth_default_realm = auth_userdb = passwd: /etc/passwd auth_passdb = passwd: /etc/passwd auth_executable = /usr/libexec/dovecot/dovecot-auth auth_process_size = 256 auth_user = root auth_count = 2 Any help would be greatly appreciated, of course. I'll keep scanning the web site while I am at your mercy. TIA, Andrew L. in Iowa _____________________________________________________________________ Get your own family web site at www.MyFamily.com!

I submitted this question to the Postfix maillist and they suggested that I post to this one. Here's my issue: I have a Postifx email system running on a CentOS 4 box, with Dovecot pop3 and imap. Last week, one of my users reported to me that about a dozen emails suddenly showed up in his in box (as unread messages), but none of them were addressed to him. Under further investigation,

Here's another patch. This one isn't much different from the last patch, except it tries a little harder to make sure that the required fields are returned by the query (like the pgsql module does). One question about how t_strdup works. How and who should memory returned by t_strdup be freed? My patch has a function my_get_str() which returns the value of t_strdup, and then I do

...3 > > auth = default > auth_mechanisms = plain > #auth_realms = > #auth_default_realm = > auth_userdb = passwd > auth_passdb = passwd > #auth_executable = /usr/local/libexec/dovecot/dovecot-auth > #auth_process_size = 256 > auth_user = root > #auth_chroot = > #auth_count = 1 > #auth_username_chars = abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@ > #auth_anonymous_username = anonymous > auth_verbose = yes > > #auth = digest_md5 > #auth_methods = digest-md5 > #auth_realms = > #auth_userdb = passwd-file /etc/passwd.imap &...

hi there, I?m getting such a headache today, I?ve added myself to three mailing lists trying to figure this out, okay here it goes. I?ve got a Fedora Core 4 box running dovecot imap, squirrel mail, postfix, samba/winbind. I?m running winbind to authenticate against Active Directory, I?ve edited my ?/etc/pam.d/dovecot? pam module so to let my users login with there Active directory password, but

...ec/dovecot/imap imap_process_size = 256 auth = default auth_mechanisms = plain auth_userdb = pgsql /etc/dovecot-pgsql.conf auth_passdb = pgsql /etc/dovecot-pgsql.conf auth_executable = /usr/libexec/dovecot/dovecot-auth auth_user = root auth_count = 1 auth_username_chars = abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@ auth_verbose = yes auth_debug = yes Additionally, here are the entries in my dovecot-pgsql.conf file: connect = host=localhost dbname=mail_DB user=mailre...

...ion # requires roots, so use something else if possible. auth_user = root # Directory where to chroot the process. Most authentication backends don't # work if this is set, and there's no point chrooting if auth_user is root. #auth_chroot = # Number of authentication processes to create #auth_count = 1 # List of allowed characters in username. If the user-given username contains # a character not listed in here, the login automatically fails. This is just # an extra check to make sure user can't exploit any potential quote escaping # vulnerabilities with SQL/LDAP databases. If you want t...

...ion # requires roots, so use something else if possible. auth_user = root # Directory where to chroot the process. Most authentication backends don't # work if this is set, and there's no point chrooting if auth_user is root. #auth_chroot = # Number of authentication processes to create #auth_count = 1 # List of allowed characters in username. If the user-given username contains # a character not listed in here, the login automatically fails. This is just # an extra check to make sure user can't exploit any potential quote escaping # vulnerabilities with SQL/LDAP databases. If you want t...

...ion # requires roots, so use something else if possible. auth_user = root # Directory where to chroot the process. Most authentication backends don't # work if this is set, and there's no point chrooting if auth_user is root. #auth_chroot = # Number of authentication processes to create #auth_count = 1 # List of allowed characters in username. If the user-given username contains # a character not listed in here, the login automatically fails. This is just # an extra check to make sure user can't exploit any potential quote escaping # vulnerabilities with SQL/LDAP databases. If you want t...

...ion # requires roots, so use something else if possible. auth_user = root # Directory where to chroot the process. Most authentication backends don't # work if this is set, and there's no point chrooting if auth_user is root. #auth_chroot = # Number of authentication processes to create #auth_count = 1 # List of allowed characters in username. If the user-given username contains # a character not listed in here, the login automatically fails. This is just # an extra check to make sure user can't exploit any potential quote escaping # vulnerabilities with SQL/LDAP databases. If you want t...

...tion # requires roots, so use something else if possible. auth_user = root # Directory where to chroot the process. Most authentication backends don't # work if this is set, and there's no point chrooting if auth_user is root. #auth_chroot = # Number of authentication processes to create auth_count = 2 # List of allowed characters in username. If the user-given username contains # a character not listed in here, the login automatically fails. This is just # an extra check to make sure user can't exploit any potential quote escaping # vulnerabilities with SQL/LDAP databases. If you want t...

...ess mails. # That user is specified by auth_userdb above. auth_user = root # Directory where to chroot the process. Most authentication backends don't # work if this is set, and there's no point chrooting if auth_user is root. #auth_chroot = # Number of authentication processes to create #auth_count = 1 # List of allowed characters in username. If the user-given username contains # a character not listed in here, the login automatically fails. This is just # an extra check to make sure user can't exploit any potential quote escaping # vulnerabilities with SQL/LDAP databases. If you wan...

...files, which also # requires roots. #auth_user = root auth_user = dovecot # Directory where to chroot the process. Most authentication backends don't # work if this is set, and there's no point chrooting if auth_user is root. #auth_chroot = # Number of authentication processes to create #auth_count = 1 # List of allowed characters in username. If the user-given username contains # a character not listed in here, the login automatically fails. This is just # an extra check to make sure user can't exploit any potential quote escaping # vulnerabilities with SQL/LDAP databases. If you want t...

...tion # requires roots, so use something else if possible. auth_user = root # Directory where to chroot the process. Most authentication backends don't # work if this is set, and there's no point chrooting if auth_user is root. #auth_chroot = # Number of authentication processes to create #auth_count = 1 # List of allowed characters in username. If the user-given username contains # a character not listed in here, the login automatically fails. This is just # an extra check to make sure user can't exploit any potential quote escaping # vulnerabilities with SQL/LDAP databases. If you want t...