search for: sieveshell

Hello, I've some difficulties with my installation, specially with sieveshell. O.K., just have a look on my site: intranet : 10.0.10.0/24 DMZ : 10.0.0.0/24 My IMAP-server is based on DMZ-site on my host vml000070 (10.0.0.70): # netstat -penlut Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State Us...

sieveshell cannot connect as any user Mar 14 23:53:45 srv1 saslauthd[22038]: do_auth : auth failure: [user=root] [service=sieve] [realm=] [mech=shadow] [reason=Unknown] Mar 14 23:53:45 srv1 sieve[22047]: Password verification failed Mar 14 23:53:45 srv1 perl: No worthy mechs found Mar 15 00:01:54 sr...

Hi, Do you know if sieve implementation on cyrus-imapd package is working correctly ? When trying to connect to timsieved at localhost with sieveshell I'm getting the following error: $ sieveshell --user=al --authname=cyrus localhost connecting to localhost unable to connect to server at /usr/bin/sieveshell line 169 The configuration on /etc/cyrus.conf is by defult. Port 2000 is listening on all tcp interfaces. This port is not open in Ipta...

...64 GNU/Linux Mail subsystem consists of: sendmail spamassassin spamass-milter cyrus-imap All of these appear to be working. Mail sent to the system appears in the inbox of the user it is sent to. My problem: I am unable to get the cyrus sieve to work. Attempting to run sieveshell to load the filter fails as shown below. [harold at newmick ~]$ sieveshell localhost connecting to localhost unable to connect to server at /usr/bin/sieveshell line 170. [harold at newmick ~]$ I have googled the error message and can find entries going back as far as the early 2000's. Nothin...

...t. Note that only one bogus command has been sent by the client, however the server sends two identical error messages. This seems to be a bug in Pigeonhole 0.3.3. In version 0.2.6, the connection was kept open after the error message. This is actually important to us because we use the "sieveshell" utility which is shipped with the Python "managesieve" package. The managesieve.py module always sends a BOGUS command after the TLS handshake. According to its comments, this is done to work around problems with other server implementations: # Some servers send...

...testing, I have tried other client implementations than horde-ingo, but somehow everyone is very focused on the timsieve daemon and they tend to require its protocol specifics. The only other implementation I got working is smartsieve. The others either crashed or produced protocol errors (i.e. sieveshell). I hope I can get more client implementations to work to ensure the incompatibilies are not my fault. I am very eager to know what you think about the sieve implementation ideas and what you think of the new managesieve patch. Regards, -- Stephan Bosch stephan at rename-it.nl