Andrew Morgan pisze:
> We had a similar behavior occur that turned out to be caused by a
> firewall. We use a Cisco FWSM. The culprit was a "fix-up" for the
Thank you very much!
I've changed port from 2000 to 2002 and sieve started to work again.
It looks like my provider routers/firewalls are
Hi,
I am observing strange problem with timsieved daemon.
This is on small mail server running cyrus-imapd 2.2.12.
For most hosts, timsieved does not respond to commands at all. It sits in
select() and never read any data. Data written at start of daemon is not
readed to telnet client too.
But
On Wed, 14 Nov 2007, Lukasz Michalski wrote:
> Hi,
>
> I am observing strange problem with timsieved daemon.
> This is on small mail server running cyrus-imapd 2.2.12.
>
> For most hosts, timsieved does not respond to commands at all. It sits in
> select() and never read any data. Data written at
