Thanks Christos for the info!
--- Christos Soulios <[EMAIL PROTECTED]> wrote:
> I fell into the same bug and from what I found using gdb was that
> after a
> SELECT command, the function cmdloop() of imapd calls
> proxy_check_input().
>
>
> Then the following function calls are performed :
> p
Patrick, all,
--- Patrick Radtke <[EMAIL PROTECTED]> wrote:
> We had the same problem a few weeks back.
> I filed a bug at
> https://bugzilla.andrew.cmu.edu/show_bug.cgi?id=2669
Ah, who would think to check there. :)
>
> Our solution was to have the backends and murder master run the 2.3
> c
I fell into the same bug and from what I found using gdb was that after a
SELECT command, the function cmdloop() of imapd calls proxy_check_input().
Then the following function calls are performed :
proxy_check_input() -> prot_read() -> prot_fill() -> read()
Then read() blocks while waiting from
We had the same problem a few weeks back.
I filed a bug at
https://bugzilla.andrew.cmu.edu/show_bug.cgi?id=2669
Our solution was to have the backends and murder master run the 2.3
code, and the frontends run the 2.2 code.
This works for us since the 2.3 features that we want (replication,
une
Hello,
There is a 2.2-imapd (2.2.12) murder enabled environment (front ends,
murder master, back ends) working nice, and so I set up another front
end with the 2.3 cvs code for testing. After setting it all up, I'm
having problems fetching mail through it. What happens is, a mail
client (tried mut
