Vladi Lemurov schrieb:
Thanks a lot, it helped! Thanks to all who tried to find the solution!
Quietly reading this thread as it developed got my hopes up for a
solution that would solve my problem at the same time.
Situation is roughly the same:
debian sarge w/
- Cyrus v2.1.18-IPv6-Debian-2.1.18-1+sarge2 with the following config:
++++++++++++++++++++++++++++++++++++++++++++++++++++++
/etc/imapd.conf:
configdirectory: /var/lib/cyrus
defaultpartition: default
partition-default: /var/spool/cyrus/mail
partition-news: /var/spool/cyrus/news
newsspool: /var/spool/news
altnamespace: no
unixhierarchysep: yes
munge8bit: no
admins: cyrus
allowanonymouslogin: no
popminpoll: 1
autocreatequota: 4000000
quotawarn: 90
umask: 077
sieveusehomedir: false
sievedir: /var/spool/sieve
hashimapspool: true
allowplaintext: yes
sasl_mech_list: PLAIN LOGIN
sasl_minimum_layer: 256
sasl_maximum_layer: 256
sasl_pwcheck_method: auxprop
sasl_auxprop_plugin: sasldb
sasl_auto_transition: no
tls_cert_file: /etc/ssl/certs/mail.artegic.net.crt
tls_key_file: /etc/ssl/keys/mail.artegic.net.key
tls_sieve_cert_file: disabled
tls_sieve_key_file: disabled
tls_ca_file: /etc/ssl/certs/ca.crt
tls_ca_path: /etc/ssl/certs
tls_session_timeout: 1440
tls_cipher_list: TLSv1:SSLv3:SSLv2:!NULL:!EXPORT:!DES:!LOW:@STRENGTH
lmtpsocket: /var/run/cyrus/socket/lmtp
idlesocket: /var/run/cyrus/socket/idle
notifysocket: /var/run/cyrus/socket/notify
++++++++++++++++++++++++++++++++++++++++++++++++++++++
/etc/cyrus.conf:
START {
recover cmd="/usr/sbin/ctl_cyrusdb -r"
delprune cmd="/usr/sbin/ctl_deliver -E 3"
tlsprune cmd="/usr/sbin/tls_prune"
}
SERVICES {
imap cmd="imapd -U 30" listen="localhost:imap"
prefork=0 maxchild=100
imaps cmd="imapd -s -U 30" listen="imaps" prefork=0
maxchild=100
lmtpunix cmd="lmtpd" listen="/var/run/cyrus/socket/lmtp"
prefork=0 maxchild=20
sieve cmd="timsieved" listen="localhost:sieve"
prefork=0 maxchild=100
notify cmd="notifyd"
listen="/var/run/cyrus/socket/notify" proto="udp" prefork=1
}
EVENTS {
checkpoint cmd="/usr/sbin/ctl_cyrusdb -c" period=30
delprune cmd="/usr/sbin/ctl_deliver -E 3" at=0401
tlsprune cmd="/usr/sbin/tls_prune" at=0401
squatter cmd="/usr/sbin/squatter -r *" period=30
}
++++++++++++++++++++++++++++++++++++++++++++++++++++++
Theoretically this should enable sieve for logins from localhost by user
cyrus (who of course has an entry in sasldb), right?
My telnet output shows:
:~# telnet localhost 2000
Trying 127.0.0.1...
Connected to localhost.localdomain.
Escape character is '^]'.
"IMPLEMENTATION" "Cyrus timsieved v2.1.18-IPv6-Debian-2.1.18-1+sarge2"
"SIEVE" "fileinto reject envelope vacation imapflags notify subaddress
relational regex"
OK
but sieveshell still complains:
:~# sieveshell --user=cyrus --auth=cyrus localhost
connecting to localhost
unable to connect to server at /usr/bin/sieveshell line 174.
no matter whether I'm logged in as root or cyrus.
Could it have to do with the sasl_minimum_layer setting?
If TLS is disabled for sieve via the key file settings, does the
sasl_minimum_layer setting still override this?
regards & TIA
Martin
----
Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ: http://cyruswiki.andrew.cmu.edu
List Archives/Info: http://asg.web.cmu.edu/cyrus/mailing-list.html
