ram wrote:
> On Mon, 2009-03-02 at 09:15 -0600, Dan White wrote:
>
>> You could enable telemetry logging, which should help to rule out a
>> problem with the client.
>>
>>
>
> How do I do that ?
>
>
>
See:
http://cyrusimap.web.cmu.edu/imapd/overview.html
You create a folder with the
On Mar 4, 2009, at 3:52 AM, ram wrote:
> On Mon, 2009-03-02 at 09:15 -0600, Dan White wrote:
>>
>> You could enable telemetry logging, which should help to rule out a
>> problem with the client.
>
> How do I do that ?
# mkdir /var/lib/imap/log/$user
# chown cyrus /var/lib/imap/log/$user
One file
On Mon, 2009-03-02 at 09:15 -0600, Dan White wrote:
> ram wrote:
> > I have problem at a clients end exactly same as described in this
> >
> > http://marc.info/?l=info-cyrus&m=108967188821511&w=2
> >
> > A pop process blocks at write() for any mail at random. And they start
> > getting pop lock is
ram wrote:
> I have problem at a clients end exactly same as described in this
>
> http://marc.info/?l=info-cyrus&m=108967188821511&w=2
>
> A pop process blocks at write() for any mail at random. And they start
> getting pop lock issues
>
> I have checked with the customer , there is no IDS on the
Hi,
On Monday 02 March 2009 12:33:43 ram wrote:
> I have problem at a clients end exactly same as described in this
>
> http://marc.info/?l=info-cyrus&m=108967188821511&w=2
>
> A pop process blocks at write() for any mail at random. And they
> start getting pop lock issues
>
> I have checked with
I have problem at a clients end exactly same as described in this
http://marc.info/?l=info-cyrus&m=108967188821511&w=2
A pop process blocks at write() for any mail at random. And they start
getting pop lock issues
I have checked with the customer , there is no IDS on their network
Is there any
