I have confirmed that cyrus-master is listening on port 2000:

netstat -tulpen | grep 2000

tcp        0      0 0.0.0.0:2000            0.0.0.0:*               LISTEN      0
      8144374    18188/cyrus-master
tcp        0      0 :::2000                 :::*                    LISTEN      0
      8144372    18188/cyrus-master

Which explains why I can telnet in, etc...  To my knowledge, nothing has 
changed, so
I'm puzzled as to why it would stop working all of a sudden.

When I try to use sieveshell to log in, I get this in /var/log/imapd/debug:

Sep 14 11:36:06 rusty master[22152]: about to exec 
/usr/lib/cyrus-imapd/bin/timsieved
Sep 14 11:36:06 rusty sieve[22152]: executed
Sep 14 11:36:06 rusty sieve[22152]: accepted connection


Restarting cyrus doesn't help...

Any ideas?

Mike

On Thu, September 14, 2006 9:44 am, Mike Husmann wrote:
> Hey everyone,
>   This morning, timsieved stopped accepting remote connections.  Using 
> sieveshell
on
> localhost, I can still connect just fine, and remotely I can telnet into port
2000.  However, I cannot use sieveshell from a remote computer, nor will my
avelsieve plugin for squirrelmail connect (running on a remote machine).
>
> Using sieveshell from a remote box results in:
> unable to connect to server at /usr/bin/sieveshell line 169.
>
> There is nothing in any of the imapd logs about sieve, except for the ones 
> where I
successfully logged in locally using sieveshell.  timsieved correctly starts 
when
I
> telnet in or use sieveshell locally.
>
> Any hints/suggestions?
>
> Thanks in advance,
>
> Mike
>
> _______________________________________________
> tsl-discuss mailing list
> [email protected]
> http://lists.trustix.org/mailman/listinfo/tsl-discuss
>
>




_______________________________________________
tsl-discuss mailing list
[email protected]
http://lists.trustix.org/mailman/listinfo/tsl-discuss

Reply via email to