A signal 11 is a segmentation violation. If that log file message is
accurate (sometimes they can be misleading and start a snark-hunt), then
it is likely that you found an imapd bug.
Have you tried imapd directly from the UW ftp server:
ftp://ftp.cac.washington.edu/mail/imap.tar.Z
(for imap-2004g) and/or
ftp://ftp.cac.washington.edu/mail/imap-2006.DEV.tar.Z
(for the imap-2006 development snapshot)?
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.
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.
If the problem does not happen with unmodified imapd directly from the UW
ftp server, then you'll need to contact whomever distributes that patched
version for support, if you want to run that version instead of the
unmodified one.
-- Mark --
http://staff.washington.edu/mrc
Science does not emerge from voting, party politics, or public debate.
Si vis pacem, para bellum.
_______________________________________________
Imap-uw mailing list
[email protected]
https://mailman1.u.washington.edu/mailman/listinfo/imap-uw
