Re: Getting Sieve to Run from cyrus.conf

2005-07-02 Thread Ken Murchison
Forrest Aldrich wrote: Okay, I commented out "callback" in /etc/services and used Sieve. I can connect with "sieveshell", but this appears to be a problem still: # sieveshell myserver.domain.com connecting to myserver.domain.com Please enter your password: Please enter your pa

Re: Getting Sieve to Run from cyrus.conf

2005-07-01 Thread Forrest Aldrich
Okay, I commented out "callback" in /etc/services and used Sieve.  I can connect with "sieveshell", but this appears to be a problem still: # sieveshell myserver.domain.com connecting to myserver.domain.com Please enter your password: Please enter your password: perl in free(): error: junk p

Re: Getting Sieve to Run from cyrus.conf

2005-07-01 Thread Forrest Aldrich
No it is not, but would that prevent it from running. Port 2000 is allocated to "callback" (tcp|udp) in /etc/services. Ken Murchison wrote: > Forrest Aldrich wrote: > >> I installed the lastest cyrus, compiled from the FreeBSD port. >> >> I'm having a problem with timsieved not running as it's

Re: Getting Sieve to Run from cyrus.conf

2005-07-01 Thread Ken Murchison
Forrest Aldrich wrote: I installed the lastest cyrus, compiled from the FreeBSD port. I'm having a problem with timsieved not running as it's configured: sieve cmd="timsieved" listen="sieve" prefork=0 From the docs I read, this is correct. If I telnet to my local machine (by IP, not 127