Re: mailutil transfer and bad messages
Hi, Also, when running test transfers, I am experiencing more weird error messages from mailutil, such as message contain NUL character. It seems that my users mailboxes contain a lot of crap. I remember, I had those a lot when I converted my old Unix mailboxes that had NeXTMail attachments in them. - Lars
Re: mailutil transfer and bad messages
On Wed, 8 Dec 2004, Mark Crispin wrote: I suggest that you ask the maintainers of the Cyrus server if there is a way to disable that check. Otherwise, there is no way that you can truly copy your messages. I disabled myself these checks in the cyrus source, and then all the transfers went fine, very quickly, perfectly keeping all mail attributes (internal dates, flags, ...). :-) Thanks Mark, you showed me the right direction. Regards. -- Nicolas
Re: mailutil transfer and bad messages
On Thu, 9 Dec 2004, Cliff Green wrote: Just a note - that's okay for an mbox-format folder, mbx folders are a different story; you'll probably need to copy those messages to an mbox folder, remove the extra header, then move them back to the mbx folder. What's OK for an mbox format mailbox is also OK for mbx; the problem is that it is not OK for Cyrus. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum.
Re: mailutil transfer and bad messages
Mark Crispin [EMAIL PROTECTED] writes: On Thu, 9 Dec 2004, Cliff Green wrote: Just a note - that's okay for an mbox-format folder, mbx folders are a different story; you'll probably need to copy those messages to an mbox folder, remove the extra header, then move them back to the mbx folder. What's OK for an mbox format mailbox is also OK for mbx; the problem is that it is not OK for Cyrus. I found on the web some tips about it, it requires patching imap/message.c in the cyrus source directory. It shows that Cyrus reject unconditionnaly: 1 - message body containing the '\0' character 2 - header name not terminated by a ':', such as 'From ' 3 - empty line in headers 4 - null-name header like ': value' Mark, which above conditions are accepted or rejected by UW-IMAP ? Thanks. -- Nicolas
Re: mailutil transfer and bad messages
On Thu, 9 Dec 2004, Nicolas Kowalski wrote: Mark, which above conditions are accepted or rejected by UW-IMAP ? UW imapd does not reject any of these; it will accept whatever garbage you throw at it. Whether it does anything useful with that garbage subsequently depends upon the nature of that garbage. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum.
Re: mailutil transfer and bad messages
On Wed, 8 Dec 2004, Nicolas Kowalski wrote: When I use mailutil transfer to copy a whole mailbox hierarchy from a uw-imap server to a cyrus one, it sometimes fails with the error message contains invalid header, and then stops. Is there a way to make mailutil ignore these badly formatted messages and continue the transfer ? That problem (the check for invalid header) is not in mailutil; it's in the Cyrus server. The Cyrus server is refusing to accept the message in question. Mailutil, in turn, stops when it ceases to be able to do what it was told to do. Mailutil has no way of knowing that the problem is just that silly check, or some more serious matter. I doubt very much that you would want to have mailutil tell you that a copy was done, only to find that most messages were not copied due to a serious problem. I suggest that you ask the maintainers of the Cyrus server if there is a way to disable that check. Otherwise, there is no way that you can truly copy your messages. -- Mark -- http://staff.washington.edu/mrc Science does not emerge from voting, party politics, or public debate. Si vis pacem, para bellum.
Re: mailutil transfer and bad messages
Mark Crispin [EMAIL PROTECTED] writes: Is there a way to make mailutil ignore these badly formatted messages and continue the transfer ? That problem (the check for invalid header) is not in mailutil; it's in the Cyrus server. The Cyrus server is refusing to accept the message in question. Yes, but the message really seems to be bad. When I look the offending mailbox (mbx format) with Pine, I get this: R 1999-01-28 obscured (4530) Re: subject obscured RA 1999-05-07 obscured (4063) R (1155) R 1999-05-08 obscured (4883) Re: The third message contains the text body from the previous message, and begins with a 'From ' line. I believe some crap happened when I converted from unix format to mbx two years ago. Mailutil, in turn, stops when it ceases to be able to do what it was told to do. Mailutil has no way of knowing that the problem is just that silly check, or some more serious matter. I doubt very much that you would want to have mailutil tell you that a copy was done, only to find that most messages were not copied due to a serious problem. You are right, there is a serious problem in this case. -- Nicolas
Re: mailutil transfer and bad messages
Cliff Green [EMAIL PROTECTED] writes: Today at 7:17pm, Nicolas Kowalski wrote: NK When I use mailutil transfer to copy a whole mailbox hierarchy from a NK uw-imap server to a cyrus one, it sometimes fails with the error NK message contains invalid header, and then stops. NK NK Is there a way to make mailutil ignore these badly formatted messages NK and continue the transfer ? [...] So, no - you can't make mailutil ignore them, but you can remove them so it doesn't have to. Yes, that's what I will do. Thanks. -- Nicolas
