similar to: UW-IMAP -> Dovecot : patch to remove nasty

Hello there, We want to move from UW-IMAP to Dovecot (mbox format), works like a charm, but UW-IMAP has that bloody habbit to make a stupid message in all his mailbox files : From MAILER-DAEMON Thu Apr 19 10:30:01 2001 Date: 19 Apr 2001 10:30:01 +0200 From: Mail System Internal Data <MAILER-DAEMON at mailhub2-vil.isdnet.net> Subject: DON'T DELETE THIS MESSAGE -- FOLDER INTERNAL DATA

Though there are conversion scripts, I'd like to give the convert plugin a chance. I have Dovecot 1.0.1 on Trustix Secure Linux 2.2 (Linux 2.4.27), and we had UW IMAP 2002e. Dovecot seems to work OK (e.g. I can add copy messages to it), but things break when I activate the convert plugin. The Wiki suggests convert_mail = mbox:~/:INBOX=/var/mail/%u # <--- locally changed to

Hello! In this email you can find a configuration primer for a Migration from UW IMAP with pine, Thunderbird and squirrelmail as client. For compatibility the mbox format is used. A description for pine with imap acces without entering any password is also discussed. Please use dovecot 1.0beta1 or later for correct handling with pine. Short overview of Mail folders:

After migrating our mail server from uw-imap to dovecot at the weekend we've had a few corrupted mbox folders. I assume this is due to messages with bad Content-length headers. Is there any way of checking the Content-length of messages in mbox folders? Thanks -- Ian

Hello, I am trying to migrate existing UW-IMAP installation to dovecot 1.1.14 and I am having troubles with namespaces. As you know UW-IMAP allows full system access to home directory of a user and you can set up dovecot to do that as well, but I would like to use namespaces. If I set my namespaces like this: namespace private { separator = / prefix = inbox = yes location =

With a INBOX mbox created by UW IMAP the messages in INBOX mbox contains the X-UIDL field When I use Dovecot POP3 with pop3_uidl_format = %08Xv%08Xu on the first run, X-UID is inserted, but all messages are downloaded again. What am I missing, I don't want the clients to download the read messages again. Thanks Bertrand Leboeuf leboeuf at emt.inrs.ca

Hello! I've just subscribed and I'd like to ask. Is there any troubles if I change my imap-uw with davecot? Will davecot pick up imap-uw created folders (mboxes)? I use all protocols: imap, imaps, pop and pops. I've seen some problems with mbox was mention on this maillist. What kind of problem? -- Sem.

Greetings. I've got a poorly conceived and implemented system I'm trying to migrate off of. Right now we've got 20K accounts or so, in mbox form, under UW-IMAP. Eventually we're going to move to Maildir format, but the first step is to move to Dovecot on one of our imap servers as a proof of concept. In other words, all config changes have to take place on the dovecot

Hi all, I've read so much information on this that I'm a little confused as to what to follow. Here's what's going on: We just migrated away from our AIX machines which were running Postfix and UW-IMAP. We're now running Postfix with Dovecot. I already converted everyone's mbox file to maildir, but now I'm having a little troubles with how to exactly populate

Hey, I'm trying to sort out how to make dovecot replace uw-imap cleanly. But I have the following problems/questions: 1. Why is mbox support limited to user-owned directories? 2. Would it be possible to have dovecot target a different place than ~user/mail by default, specfically some place like /var/path/to/maildirs/userdir/ I'd like to move all my mail storage out of user homedirs and

i plan to switch from uw-imap to dovecot on a couple of medium size systems and so i have written a conversion tool that understands mbox, mbx, and mix formats and converts to maildir format while trying to preserve uid info, keywords, flags, subscriptions, etc. it seems to work for me now, but i think some feedback might be useful. so if you have some files to convert and a desire to help,

I am attempting to test out dovecot on a server on a separate IP address from the live, functioning UW-IMAP. I am having mixed results with dovecot. An entirely new account that's never been used with UW-IMAP seems to work fine, but that's really not the point of the exercise. If I try changing over an existing account to use dovecot, I get a variety of issues. Testing with Apple

I've just replaced our ancient (10-year old) mail server running Sendmail/UW-IMAP on Solaris with Postfix/Dovecot 2.1.10 running on Linux on new hardware. I opted to go with virtual users and I didn't want to create system accounts and I might end up hosting another department's mail as well. We have a mix of POP3 and IMAP users, roughly 90 total. The POP3 user mailboxes migrated

http://dovecot.org/patches/mbox-snarf-plugin.c Also committed to CVS HEAD. Usage: mail_location = mbox:~/mail:INBOX=/var/mail/%u protocol imap { mail_plugins = mbox_snarf } protocol pop3 { mail_plugins = mbox_snarf } plugin { mbox_snarf = ~/mbox } If ~/mbox doesn't exist, nothing special is done. If ~/mbox exists, it's treated as INBOX and mails are moved from /var/mail/%u

Hi all Apologies if this question has already been asked before... I'm migrating from a uw-imap setup where the mail folders were in a subdir mail/ in the users' home directories. All of the clients are configured with 'IMAP server directory' set to mail/ (Thunderbird) and it would be difficult to change this on the clients (there are 1000s of them) I want to use maildir and I

FWIW, the Dovecot 1.0.1 convert plugin works with all my UW-IMAP mboxes moved to ~/mail. At least that shows that my system otherwise works. Also, I wrote a script to move the mboxes and preserve the IMAP subscriptions. (I hope the list accepts the attached script.) -------------- next part -------------- A non-text attachment was scrubbed... Name: move_mail.sh Type: application/x-sh Size: 1750

How does IMAP lock the /var/spool/mail/user file? Here's my problem: I'm writing a script to expire old or oversize mail through a series of archive folders. I don't want to take the whole server down to do this, nor does it seem like I would have to lock the user out entirely if I can manage to emulate the locks correctly. I am able to lock /var/spool/mail/user (and ~user/mail/*)

Hi I am trying directly to replace old uw-imap + GNU pop3d with Dovecot. Problems I am having with new (1.0-stable 22.02.2005) are: - How to get SSL working with new config? imaps_listen doesn't exist anymore. cannot add protocol imaps for some reason. - need to get Dovecot run on another port the test-phase, ie 144 for imap, 994 for IMAPs - need to use .mailboxlist (modified the source

Hi, I'm trying to add some sanity to a badly thought out mail system that, for various reasons, cant be fixed from the bottom up at this moment in time. The system is debian sarge, exim 4.5, doing virtual domains and delivering into mboxes in /var/spool/virtual/$domain/$user , there is webmail access and this allows user to create folders in (dont shoot me!)

From: Matt Hyclak <hyclak at math.ohiou.edu> > Actually, the more direct replacement would be Dovecot. > Cyrus can be complicated to set up and get running. I actually modified the old UW IMAP 2002 SPEC file from RHL9/FC1, and modified a few config files, to support UW IMAP 2004b. I made one with both RFC3501 (no text passwords over SSL) and non-RFC3501 (legacy, text passwords