Re: IMAP ANNOTATE MORE support
On Thu, 9 Dec 2004 [EMAIL PROTECTED] wrote: But I need ANNOTATE support. I've found on the website the you were planning to do the support, but I cant found anything in hte documentation. There is currently no support for ANNOTATE and ANNOTATEMORE in c-client. You are the first person who has asked for it. Please note that ANNOTATE and ANNOTATEMORE are still under development in the IETF IMAPEXT working group, and as such the specification is subject to change. I can not predict at the present time when ANNOTATE and/or ANNOTATEMORE support will be added. This is a fairly large capability, and there are other projects. It is possible that a basic IMAP-client only support (as opposed to general c-client support and UW imapd support) can be added soon rather than later. This would be on the lines of the existing support for ACL and QUOTA; meaning that you call internal IMAP driver functions through unofficial interfaces. If this is OK, please let me know. -- 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 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
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 ': ' Mark, which above conditions are accepted or rejected by UW-IMAP ? Thanks. -- 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.
IMAP ANNOTATE MORE support
Hi, I've been using your library for about a month. I'm pretty happy about it. But I need ANNOTATE support. I've found on the website the you were planning to do the support, but I cant found anything in hte documentation. Is it done?? And if not, can you help me to introduce this functionnality to your library Thanks Julien Hamaide -- -- For information about this mailing list, and its archives, see: http://www.washington.edu/imap/c-client-list.html --
Re: mailutil transfer and bad messages
On Dec 8 at 10:58pm, Nicolas Kowalski wrote: NK> Cliff Green <[EMAIL PROTECTED]> writes: NK> NK> > Today at 7:17pm, Nicolas Kowalski wrote: NK> NK> > NK> When I use mailutil transfer to copy a whole mailbox hierarchy from a NK> > NK> uw-imap server to a cyrus one, it sometimes fails with the error NK> > NK> "message contains invalid header", and then stops. NK> > NK> NK> > NK> Is there a way to make mailutil ignore these badly formatted messages NK> > NK> and continue the transfer ? NK> NK> [...] NK> NK> > So, no - you can't make mailutil ignore them, but you can remove them so NK> > it doesn't have to. NK> NK> Yes, that's what I will do. 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. c -- Clifford Green Internet - [EMAIL PROTECTED] Academic Computing ServicesUMDNJ-IST Never wrestle with a pig, for if you do, you will both get dirty, but the pig will enjoy it. -- Charlie Munger
Re: mailutil transfer and bad messages
Quoting Nicolas Kowalski <[EMAIL PROTECTED]>: > 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. > > -- > Nicolas > So these mailboxes were first converted from something else? Interesting. Would you be willing to send one or two of the corrupt files to my email address? I have a morbid curiousity about corrupt files. Send them to [EMAIL PROTECTED], not to the list. thanks tc - Email solutions, MS Exchange alternatives and extrication, security services, systems integration. Contact:[EMAIL PROTECTED]
Re: mailutil transfer and bad messages
[EMAIL PROTECTED] writes: > I have a program you may download from sourceforge which will usually correct > corrupt MBX files. > > The url is http://sourceforge.net/projects/mbxuncorrupter/ > > You may be able to fix the MBX file then mailutil won't gripe. Any > unrecoverable mail fragments will be put into separate text files. Thanks. However, I ran your utility on the specified mailbox, and it did not repair the badness. That's probably because the MBX headers are not corrupted, but because the unix format mailbox (used to create this mbx-format one) already had badness in it. 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. -- Nicolas
