search for: authtest

Hi to all! I?ve changed position to client auth socket to enable postfix authentication. The socket is now created in /var/spool/postfix/private/auth. authtest do not catch up the change. Reading source I?ve seen that path to auth sockets is written explicitly in function authtest_passdb in util/authtest.c to: if (auth_socket_path == NULL) auth_socket_path = PKG_RUNDIR"/auth-client?; I know I can launch authtest specifing path to socket...

.../include -I/usr/local/ssl/include -D_XPG6 -L/usr/local/lib -L/usr/local/ssl/lib -KPIC -lm -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -xc99 -I/usr/local/include -I/usr/local/ssl/include -L/usr/local/lib -L/usr/local/ssl/lib -D_XPG6 -xstrconst -KPIC -lm -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -c authtest.c "authtest.c", line 164: warning: implicit function declaration: getopt "authtest.c", line 167: undefined symbol: optarg "authtest.c", line 167: warning: improper pointer/integer combination: op "=" "authtest.c", line 170: warning: improper pointer...

Where do you think the following binaries should be installed to? The possible locations are: - bin/ - sbin/ - libexec/dovecot/ (or lib/dovecot/ in most Linux distros) So the binaries are: 1) These probably belong to bin/ or sbin/ or both: - authtest - dovecotpw - doveadm 2) Binaries that you might want to call from mail_executable setting: - rawlog - gdbhelper 3) Index file dumping programs, mostly meant for debugging problems: - idxview - listview - logview - mailboxlogview - threadview 4) Some extra tools that might be useful som...

Hi all, Im new and have a problem, With authtest, i have Authentication [root at dc9f8f585 ~]# authtest esimon at example.tld Authentication succeeded. Authenticated: esimon at example.tld (uid 501, gid 501) Home Directory: /home/vmail/domains/ Maildir: (none) Quota: (none) Encrypted Password: (none) Cleartext...

...y time (for the newer type of failure delay) was intended to start at 2 seconds and double for each failure (see auth_penalty_to_secs), but be capped at 15 seconds. However, a simple test which tries to log in 5 times with a random password and times each attempt shows something different: $ cat authtest.py import imaplib import time import random conn = imaplib.IMAP4('localhost') for i in range(5): try: start = time.time() conn.login('testusers', str(random.random())) except Exception, e: print e print time.time() - sta...

.../dovecot.org/releases/1.2/dovecot-1.2.6.tar.gz.sig A couple of random things: - I decided to start using "hg sign" to gpg sign all releases in mercurial repository. - v2.0.alpha1 will hopefully be released in a week or two. Changes since 1.2.5: * Upgraded to Unicode 5.2.0 + Added authtest utility for doing passdb and userdb lookups. + login: ssl_security string now also shows the used compression. - quota: Don't crash with non-Maildir++ quota backend. - imap proxy: Fixed crashing with some specific password characters. - dovecot --exec-mail was broken. - Avoid assert-crashi...

.../dovecot.org/releases/1.2/dovecot-1.2.6.tar.gz.sig A couple of random things: - I decided to start using "hg sign" to gpg sign all releases in mercurial repository. - v2.0.alpha1 will hopefully be released in a week or two. Changes since 1.2.5: * Upgraded to Unicode 5.2.0 + Added authtest utility for doing passdb and userdb lookups. + login: ssl_security string now also shows the used compression. - quota: Don't crash with non-Maildir++ quota backend. - imap proxy: Fixed crashing with some specific password characters. - dovecot --exec-mail was broken. - Avoid assert-crashi...

...ot server and have run the script 'courier-dovecot-migrate.pl', which was found at http://www.dovecot.org/tools/courier-dovecot-migrate.pl In a nutshell: If I have the password_query string in the SQL config file (shown below) set to return only 1 field, i.e. the password, then the Dovecot authtest app succeeds. But if more than 1 field is returned (i.e.: user and password) the test fails. And if testing with telnet I get the message of "* BYE Internal login failure. Refer to server log for more information.". The logs indicate that the password check returned OK but the userdb r...