Bug #1600 for Mail-IMAPClient: Possible bug in Mail::IMAPClient (vsn 2.2.4)

Hi, Richard. Thank you for the bug report. I can't find any debug output in this ticket, so I won't be able to give you a definite answer. However, I can tell give you a procedure that will tell you if there is a bug in the client or in the server. (That's assuming that "Message-ID" is an rfc822-compliant spelling. I'll probably check on that later, but for now it's not relevent.) The description of your problem sounds like it may actually be coming from the server. To find out, you should create a special folder, then drag one of the messages with the "Message-ID:" style header into that folder--or do the equivalent in perl with Mail::IMAPClient ;-) Then you can either run a script in debug mode mode, i.e. $imap=Mail::IMAPClient->new( Debug=>1 ,...); and attach the output to this ticket, or log in by hand and fetch the envelope as follows: 0 login userid password 1 select bugFolder 2 fetch 1 envelope 3 logout You should see the message id embedded in the output from FETCH ENVELOPE, which will consist mostly of parentheses and NIL's with the occasional datum thrown in here and there. Meanwhile I will eye-ball the code on Friday. If you need to work around this problem, you may want to read the documentation for the parse_headers method. The method returns a data structure that is a little clumsy, but it runs in my mind I specifically worked around a similar issue when I wrote this method. (The parse_headers method does not rely on FETCH ENVELOPE to obtain the header fields; it uses an alternate FETCH construction.) HTH, Dave Kernen Dave K.