How to test timsieved

[Dan White]

On 14/08/09 09:59 +0200, Paul van der Vlis wrote:
>Dan White schreef:
>I used the "-d" option in /etc/default/saslauthd and restarted saslauthd.
>
>In another terminal I tried sivtest, where the authentication was wrong.
>
>But, in the debug I see that the authentication was OK for saslauthd.
>
>---------
>paul at sigmund:/root$ sivtest -v localhost
>S: "IMPLEMENTATION" "Cyrus timsieved v2.1.18-IPv6-Debian-2.1.18-5.1"
>S: "SASL" "PLAIN"
>S: "SIEVE" "fileinto reject envelope vacation imapflags notify
>subaddress relational regex"
>S: "STARTTLS"
>S: OK
>Please enter your password:
>C: AUTHENTICATE "PLAIN" {20+}
>AHBhdWwAZXJ1NGJjZw==
>S: NO "Authentication Error"
>Authentication failed. generic failure
>Security strength factor: 0
>---------
>
>----------
>sigmund:/etc/pam.d# /etc/init.d/saslauthd restart
>Restarting SASL Authentication Daemon: saslauthdsaslauthd[29778] :main
>          : num_procs  : 5
>saslauthd[29778] :main            : mech_option: NULL
>saslauthd[29778] :main            : run_path   : /var/run/saslauthd
>saslauthd[29778] :main            : auth_mech  : pam
>saslauthd[29778] :cache_alloc_mm  : mmaped shared memory segment on
>file: /var/run/saslauthd/cache.mmap
>saslauthd[29778] :cache_init      : bucket size: 92 bytes
>saslauthd[29778] :cache_init      : stats size : 36 bytes
>saslauthd[29778] :cache_init      : timeout    : 28800 seconds
>saslauthd[29778] :cache_init      : cache table: 944764 total bytes
>saslauthd[29778] :cache_init      : cache table: 1711 slots
>saslauthd[29778] :cache_init      : cache table: 10266 buckets
>saslauthd[29778] :cache_init_lock : flock file opened at
>/var/run/saslauthd/cache.flock
>saslauthd[29778] :ipc_init        : using accept lock file:
>/var/run/saslauthd/mux.accept
>saslauthd[29778] :detach_tty      : master pid is: 0
>saslauthd[29778] :ipc_init        : listening on socket:
>/var/run/saslauthd/mux
>saslauthd[29778] :main            : using process model
>saslauthd[29779] :get_accept_lock : acquired accept lock
>saslauthd[29778] :have_baby       : forked child: 29779
>saslauthd[29778] :have_baby       : forked child: 29780
>saslauthd[29778] :have_baby       : forked child: 29781
>saslauthd[29778] :have_baby       : forked child: 29782
>saslauthd[29779] :rel_accept_lock : released accept lock
>saslauthd[29780] :get_accept_lock : acquired accept lock
>saslauthd[29779] :cache_get_rlock : attempting a read lock on slot: 1682
>saslauthd[29779] :cache_lookup    : [login=paul] [service=]
>[realm=sieve]: not found, update pending
>saslauthd[29779] :cache_un_lock   : attempting to release lock on slot: 1682
>saslauthd[29779] :cache_get_wlock : attempting a write lock on slot: 1682
>saslauthd[29779] :cache_commit    : lookup committed
>saslauthd[29779] :cache_un_lock   : attempting to release lock on slot: 1682
>saslauthd[29779] :do_auth         : auth success: [user=paul]
>[service=sieve] [realm=] [mech=pam]
>saslauthd[29779] :do_request      : response: OK
>----------

I just did some quick testing on my system and cannot authenticate to
timsieved as a user who's mailbox does not exist.

I have a mailbox for dwhite at olp.net, but not dwhite. Here's the results of
a few tests:

Works:
imtest -a dwhite -m PLAIN localhost
imtest -a dwhite at olp.net -m PLAIN localhost
sivtest -a dwhite at olp.net -m PLAIN localhost

Doesn't work:
sivtest -a dwhite -m PLAIN localhost

Based on that, I'm assuming that a mailbox for paul needs to exist to
authenticate. Is that that the case?

-- 
Dan White
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
Url : http://lists.andrew.cmu.edu/pipermail/info-cyrus/attachments/20090814/3adc25ff/attachment.bin