Howdy. I was in the process of turning up a new dbmail install when I
ran into a rather large problem. When I upload more than two messages
from my local inbox onto the server via IMAP, the server spins in a
tight loop and runs forever, which is something of a problem when I
want to mass-
Sean Chittenden wrote:
Howdy. I was in the process of turning up a new dbmail install when I
ran into a rather large problem. When I upload more than two messages
from my local inbox onto the server via IMAP, the server spins in a
tight loop and runs forever, which is something of a prob
Howdy. I was in the process of turning up a new dbmail install when
I ran into a rather large problem. When I upload more than two
messages from my local inbox onto the server via IMAP, the server
spins in a tight loop and runs forever, which is something of a
problem when I want to mass-
Sean Chittenden wrote:
Hrm... alright... any ideas/workarounds? I'm pretty handy with C and
PostgreSQL if you want me to test anything or hack something into
place. -sc
Sean,
Are you sure you limited your syslog trace to a single process? I don't
want to end up chasing the wrong trail
Hrm... alright... any ideas/workarounds? I'm pretty handy with C
and PostgreSQL if you want me to test anything or hack something into
place. -sc
Are you sure you limited your syslog trace to a single process? I
don't want to end up chasing the wrong trail here.
Yup. I can guarantee tha
Sean Chittenden <[EMAIL PROTECTED]> said:
>> Other than that, _ic_search is already under scrutiny because of poor
>> performance.
>
> It'd require a change in the database structure, but did you see my
> other post about breaking things down by header? That'd get rid of the
> need for any LI
Hrm... alright... any ideas/workarounds?
In case people missed it in my other message, HEAD doesn't seem to be
having this problem. -sc
--
Sean Chittenden
Hrm... alright... any ideas/workarounds?
In case people missed it in my other message, HEAD doesn't seem to be
having this problem. -sc
Nope, spoke too soon: still having this problem. I'm wondering if this
has something to do with the parseability of messages. With gmime2, it
took lon
