I recently upgraded from Cyrus 2.3.10 to 2.3.14 on an Ubuntu 9.04 server. Since doing this upgrade, I can no longer connect to timsieved to update my Sieve script. The symptom is that the connection gets dropped right after the client (I'm using sieve-connect) sends an AUTHENTICATE command. Here's sample debugging output from sieve-connect: =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= (05/26 15:19 richw@whodunit /var/log 119) sieve-connect --debug localhost connection: remote host address is 127.0.0.1 <<< "IMPLEMENTATION" "Cyrus timsieved v2.3.14"\r\n <<< "SASL" "DIGEST-MD5"\r\n <<< "SIEVE" "comparator-i;ascii-numeric fileinto reject vacation imapflags notify include envelope body relational regex subaddress copy"\r\n <<< "STARTTLS"\r\n <<< OK\r\n >>> STARTTLS\r\n <<< OK "Begin TLS negotiation now"\r\n --- TLS activated here >>> NOOP\r\n <<< "IMPLEMENTATION" "Cyrus timsieved v2.3.14"\r\n <<< "SASL" "CRAM-MD5 DIGEST-MD5 LOGIN PLAIN"\r\n <<< "SIEVE" "comparator-i;ascii-numeric fileinto reject vacation imapflags notify include envelope body relational regex subaddress copy"\r\n <<< OK\r\n >>> AUTHENTICATE "DIGEST-MD5"\r\n ... no line read, connection dropped? Connection dropped unexpectedly when trying to read. (05/26 15:19 richw@whodunit /var/log 120) =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= and here is the relevant syslog output: =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= May 26 15:19:37 whodunit cyrus/master[5625]: about to exec /usr/cyrus/bin/timsieved May 26 15:19:37 whodunit cyrus/sieve[5625]: executed May 26 15:19:37 whodunit cyrus/sieve[5625]: accepted connection May 26 15:19:37 whodunit cyrus/sieve[5625]: skiplist: recovered /cyrus/config/tls_sessions.db (5 records, 1180 bytes) in 0 seconds May 26 15:19:37 whodunit cyrus/sieve[5625]: imapd:Loading hard-coded DH parameters May 26 15:19:37 whodunit cyrus/sieve[5625]: SSL_accept() incomplete -> wait May 26 15:19:37 whodunit cyrus/sieve[5625]: SSL_accept() succeeded -> done May 26 15:19:37 whodunit cyrus/sieve[5625]: starttls: TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits new) no authentication May 26 15:19:37 whodunit cyrus/sieve[5625]: Lost connection to client -- exiting =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= and just in case it matters, here are the Sieve-related lines in my imapd.conf file: =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= sieve_extensions: fileinto reject vacation imapflags notify include envelope body relational regex subaddress copy sieve_maxscripts: 1000 sieve_maxscriptsize: 100 sieve_sasl_send_unsolicited_capability: 1 sievedir: /cyrus/config/sieve sieveusehomedir: false =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= and in my cyrus.conf file: =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= sieve cmd="timsieved" listen="sieve" prefork=0 proto=tcp4 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= Specifying another authentication mechanism doesn't seem to help. I tried LOGIN and CRAM-MD5, with the same result. When I tried PLAIN, I got a "Broken pipe" error right after sieve-connect's AUTHENTICATE command. Does anyone have any ideas here? Is there any way to make timsieved (or sieve-connect) produce more debugging output which might help pinpoint the problem? -- Rich Wales / richw@xxxxxxxxx / richw@xxxxxxxxxxxx Wikipedia: http://en.wikipedia.org/wiki/User:Richwales Facebook: http://www.new.facebook.com/profile.php?id=206680 ---- Cyrus Home Page: http://cyrusimap.web.cmu.edu/ Cyrus Wiki/FAQ: http://cyrusimap.web.cmu.edu/twiki List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
