Mail_IMAP - How to Report Bugs

To report bugs with Mail_IMAP, please follow these guidelines.

• Always report your bug through the PEAR interface. This ensures that I won't lose the bug or forget about it.
• If the bug involves problems with how Mail_IMAP parses a message, send the problem message in its original form to mail-imap (at) smilingsouls (dot) net. It's important that you don't send the message as an attachment, or in its raw MIME form. The message needs to be exactly as you see it. This makes it easier to run debugging tools already in place on my server and helps expedite a speedy bug fix.
• Alter the subject line of test messages sent to my demo mailbox, describe the problem if possible and include the bug number to the corresponding PEAR bug report. This helps to ensure that I won't think the message is spam and delete it.
• Aside from viruses, I do not care what your test message contains, so don't be leary of sending objectionable material. I'm only interested in finding and correcting anomolies with Mail_IMAP's message parsing algorithms. If a message contains viruses, obviously, don't send it. While it is unlikely that I would be infected by such a virus, my demo mailbox is provided as a live demo of Mail_IMAP and I don't want users of my website to get infected with viruses.
• Sending your test messages is important, a diverse base of messages to test each Mail_IMAP release on helps ensure its stability and quality.

Known Issues

• Mail_IMAP is unable to pick the text/html part of a message over the text/plain part of the message in certain multipart/related messages.

Problem messages appear in the demo mailbox.