On Jul 13, 2006, at 2:28 PM, Mark Crispin wrote:
Have you tried imapd directly from the UW ftp server:
No, and the issue is on an in-production server with lots of inter-
dependent software. So I'm *very* hesitant to do as you suggest.
I'd be willing to do that on a test server (e.g. the old server that
the data was moved off of). The problem is that this is the only box
with these symptoms.
To make things more confusing, the symptom has become rarer. I
don't know why. At this point, its closer to 1 out of 5 times
instead of 4 out of 5. If I see the symptoms again, I can try some
tests.
Distributions from other places often have patches of varying
quality. So it's important to make sure that the problem isn't due
to a third-party patch.
FWIW, I'm using the code from FreeBSD 6.1's ports collection as of
Tuesday. I cvsup'd the code that afternoon.
If you can make the problem happen with unmodified imapd directly
from the UW ftp server, please let me know. Also, if possible, see
if you can get a trace log from your PHP application of the IMAP
protocol that it is sending to the IMAP server.
Can you explain how to make a trace log? I'm far from a developer,
but I'm comfortable using root for basic sysadmin work, shell
scripting, etc.
Thanks for the reply. In several days of trying every resource that
I could think of (FreeBSD mailing list, Usenet, Web, local Linux
group, etc.) this was the most productive response that I've had.
Jaime
_______________________________________________
Imap-uw mailing list
[email protected]
https://mailman1.u.washington.edu/mailman/listinfo/imap-uw
