- Auto-replys cannot be configured (time out)
- Server-side filters cannot be configures (time out)
Is Sieve reachable?
Yes, I can access it via Telnet without problem.
Use a sniffer and check what kind of traffic occurs to track down the
problem.
Okay, I poked a bit around and found that I get the following error log:
Mär 03 17:42:19 directory1 passwd[1159296]: pam_unix(passwd:chauthtok):
password changed for USER
Mär 03 17:42:26 directory1 cyrus/imaps[1157659]: starttls: TLSv1.2 with
cipher ECDHE-ECDSA-AES256-GCM-SHA384 (256/256 bits new) no authentication
Mär 03 17:42:26 directory1 cyrus/imaps[1157659]: login:
groupware.brace.de [192.168.1.45] USER CRAM-MD5+TLS User logged in
SESSIONID=<cyrus-1741020146-1157659-1-15675365614525333306>
Mär 03 17:42:26 directory1 saslauthd[487]: pam_warn(sieve:auth):
function=[pam_sm_authenticate] flags=0x8000 service=[sieve]
terminal=[<unknown>] user=[USER] ruser=[<unknown>] rhost=[<unknown>]
Mär 03 17:42:26 directory1 saslauthd[487]: DEBUG: auth_pam:
pam_authenticate failed: Authentication failure
Mär 03 17:42:26 directory1 saslauthd[487]: : auth
failure: [user=USER] [service=sieve] [realm=] [mech=pam] [reason=PAM
auth error]
Mär 03 17:42:26 directory1 cyrus/sieve[1131373]: badlogin:
groupware.brace.de [192.168.1.45] PLAIN authentication failure
Mär 03 17:42:26 directory1 cyrus/sieve[1131373]: Lost connection to
client -- exiting
I tried to reset the password of the user to the one used in the
groupware (which should be the one transmitted here), but to no change.
(using passwd, not salspasswd2 as it seems to be a PAM problem, not Sasl2.
Is there a way to trace this better? Or any idea if sieve needs separate
password (how? where?).
Cheers
TB
------------------------------------------
Cyrus: Info
Permalink:
https://cyrus.topicbox.com/groups/info/Tc3db057d31794e3c-M8b902185757a659b66893ab8
Delivery options: https://cyrus.topicbox.com/groups/info/subscription
