Re: [Dovecot] Released v1.1.beta3
Sergey wrote: Hi Timo I've triedt to compile v1.1.beta3 on OpenSolaris (x86) with SunStudio 12. options invalid; UNIX 03 and POSIX.1-2001 applications require the use of c99" export CFLAGS="-x03 -xtarget=native -xc99" ./configure ..etc.. Your optimization flags may vary. Tomi
[Dovecot] Problems with dovecot 1.1b3
I am testing dovecot 1.1 betas on a testing system, hoping to take advantage
of self repairing and NFS-capable indexes when 1.1 is sensible to put into
production. I ran into a number of issues that I did not have with 1.0,
and I think I'll just pick one or more at a time and report them rather than
try to report every single issue at once, hoping that some of the fixes will
solve more than one problem.
I started with 1.1b2 just for record, but the issues seem to be present in
1.1b3 as well. I realized yesterday that using the acl plugin may be
complicating
my testing and results, so I have disabled it for now and am connecting with
plaintext IMAP just so I can sniff connections and see what is happening.
I am running it on FreeBSD 6.2-stable from Sep 19 2007.
First my dovecot -n output:
# 1.1.beta3: /usr/local/etc/dovecot.conf
ssl_cert_file: /usr/local/etc/apache2/ssl/ssl.pem
ssl_key_file: /usr/local/etc/apache2/ssl/ssl.pem
disable_plaintext_auth: no
login_dir: /var/run/dovecot/login
login_executable: /usr/local/libexec/dovecot/imap-login
verbose_proctitle: yes
first_valid_uid: 1000
first_valid_gid: 0
mail_location:
maildir:%h/Maildir:CONTROL=%h/Maildir/dovecot/private/control:INDEX=%h/Maildir/dovecot/private/indexes
mail_debug: yes
mmap_disable: yes
mail_nfs_storage: yes
mail_nfs_index: yes
mail_plugins: mail_log
mail_log_max_lines_per_sec: 0
imap_client_workarounds: delay-newmail netscape-eoh tb-extra-mailbox-sep
namespace:
type: private
separator: /
prefix: mail/
location:
maildir:%h/Maildir:CONTROL=%h/Maildir/dovecot/private2/control:INDEX=%h/Maildir/dovecot/private2/indexes
hidden: yes
list: yes
namespace:
type: private
separator: /
inbox: yes
list: yes
auth default:
mechanisms: plain login
passdb:
driver: pam
userdb:
driver: passwd
socket:
type: listen
client:
path: /var/spool/postfix/private/auth
mode: 384
user: postfix
group: postfix
plugin:
acl: vfile:/usr/local/etc/dovecot-acls
The first thing I did was to try to update my dovecot.conf from 1.0 to work with
1.1. When I started dovecot 1.1 for the first time, I noticed it was listening
to
143 but not 993, even though my config was designed for ssl/tls in 1.0 without
any
listen ports specified:
# netstat -a | grep LISTEN | grep imap
tcp4 0 0 *.imap *.*LISTEN
So, I thought I would try specifying the ports in the config:
protocol imap {
listen = *:143
ssl_listen = *:993
# ..
}
Success!
# netstat -a | grep LISTEN | grep imap
tcp4 0 0 *.imaps*.*LISTEN
tcp4 0 0 *.imap *.*LISTEN
Initially I was then testing using ACLs, but I disabled it to simplify.
One of the more basic problems I've seen is the behavior from "list = no/yes".
For the sake of simplicity and example, I've disabled most of the additional
public and private namespaces from my 1.0 config.
I have some private namespaces with prefix "mail/" and "Mail/" that I wish to
provide for users for compatability with clients set with those prefixes.
In dovecot 1.0, this worked as expected:
namespace:
type: private
separator: /
prefix: mail/
hidden: yes
But in 1.1b2 or b3, I never seem to get a list of the contents under mail/
when I tell mutt to default to servername/mail/ as the default folder path.
Cases:
hidden = yes
list = yes
a0006 LIST "" "mail"
* LIST (\Noselect \HasChildren) "/" "mail"
a0006 OK List completed.
a0007 LIST "" "mail/%"
a0007 OK List completed.
mutt lists contents of only "../" and selecting it brings me to the imap root
with the expected folders. When ../ is followed, I see all my folders as well
as all my folders repeated under mail/ prefix.
hidden = yes
list = no
a0006 LIST "" "mail"
a0006 OK List completed.
a0007 LIST "" "mail/%"
a0007 OK List completed.
mutt claims "No such folder"
hidden = no
list = yes
a0006 LIST "" "mail"
* LIST (\Noselect \HasChildren) "/" "mail"
a0006 OK List completed.
a0007 LIST "" "mail/%"
a0007 OK List completed.
mutt lists contents of only "../" and selecting it brings me to the imap root
with the expected folders. When ../ is followed, I see all my folders as well
as all my folders repeated under mail/ prefix.
[Dovecot] Per-user quota (with local users)
I'm migrating to LDAP mi local users, there is the auth section of my
dovecot.conf
--
auth default {
mechanisms = plain
socket listen {
master {
path = /var/run/dovecot/auth-master
mode = 0660
user = dovecot
group = nusers
}
}
passdb ldap {
args = /etc/dovecot/dovecot-ldap.conf
}
passdb pam {
}
userdb ldap {
args = /etc/dovecot/dovecot-ldap.conf
}
userdb prefetch {
}
userdb passwd {
}
user = root
}
--
The idea is to try to find the user in the directory and if it isn't
found then fallback to a local user lookup.
My quota configuration is
--
plugin {
quota = maildir:storage=10240:ignore=Trash
}
--
I have some users with particular quotas. With LDAP lookups, there is no
problem, in those cases I simply put their particular quota values in
their entries and pass it to dovecot via user_attrs.
I wonder how to do the same for local users, I mean, to have the ability
of specifying particular quotas for some local users.
Another doubt is how to express to Dovecot that a user have no quota at
all, could I use 0?
Regards,
maykel
Re: [Dovecot] Migration to Dovecot
How much mail do you have to migrate? Do you convert mbox to Maildir? Please, let us know how did it go. Good luck with it!!! FiL Frank Bonnet wrote: Hello all Tomorrow is the day , I'm gonna migrate all our mailboxes and imap folders from our old mailhub to the new one. In the same time I will migrate from UW to Dovecot , I've read all the stuff about it on the Dovecot web site. I have one question , do I have to care about the .imap cache directory created by Dovecot in any way or will it be "all automatic" when starting Dovecot ? Many thanks
Re: [Dovecot] iPhone 1.1.1 problems.
Mike Meyer wrote: Apparently, the 1.0.2 settings moved to 1.1.1 didn't like something in my SSL setup. Letting 1.1.1 set things up itself solved the problem. Thanks for the update. I can confirm that a new 1.1.1 that does its own setup against dovecot with SSL on port 993 works just fine. Mark
[Dovecot] dovecot and imap session forwarding
Hi, I was trying to install a qmail-ldap cluster. I have successfully setup dovecot to authenticate against ldap directory. But what I need is to enable imap session forwarding for qmail-ldap. For example when a user connects to a imapserver if the real mailhost of this user is different than the one that is connected so session is forwarded to real mailhost. Normally we can do that with courirer imap using auth_imap binary that comes with qmail-ldap which handles session forwarding. I have done this but got error auth_executable = /var/qmail/bin/auth_imap . Obviously it won't work. But I am not sure where to put /var/qmail/bin/auth_imap http://www.qmail-ldap.info/dovecot.php and http://www.qmail-ldap.info/imap_courier.php page shows a bit information about where to put it. -- Best regards, Omer mailto:[EMAIL PROTECTED]
Re: [Dovecot] thunderbird and email duplication
For what it's worth I had a similar problem with deliver (thunderbird was not involved) for userids whose email aliases were mixed-case versions of the userid (Rich vs rich). It went away when I lowercased the alias. Dovecot 1.0.3. Rich
[Dovecot] Sometimes Dovecot v1.0.3 does not accept new connections
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, occasionally Dovecot stops to accept new connections. Already existing ones do function properly. Strace'ing dovecot-auth reveals that it is running and is authentificating users, the logfile logs new connections. However, lots of other connects just stall, before the IMAP server responds with the greeting. My user backend is a LDAP server. I've sniffed the interface, but I also don't see numerous connection attempts, so I suppose, that there is no DoS attack running. The logfile contains no warning or error except: dovecot: Oct 17 15:34:44 Warning: auth(default): Growing pool 'plain_auth_request' with: 2048 dovecot: Oct 17 15:34:49 Warning: auth(default): Growing pool 'plain_auth_request' with: 2048 dovecot: Oct 17 15:34:52 Warning: auth(default): Growing pool 'plain_auth_request' with: 2048 dovecot: Oct 17 15:35:02 Warning: auth(default): Growing pool 'plain_auth_request' with: 2048 dovecot: Oct 17 15:35:05 Warning: auth(default): Growing pool 'plain_auth_request' with: 2048 dovecot: Oct 17 15:35:12 Warning: auth(default): Growing pool 'plain_auth_request' with: 2048 dovecot: Oct 17 15:35:19 Warning: auth(default): Growing pool 'plain_auth_request' with: 2048 dovecot: Oct 17 15:35:20 Warning: auth(default): Growing pool 'plain_auth_request' with: 2048 dovecot: Oct 17 15:35:25 Warning: auth(default): Growing pool 'plain_auth_request' with: 2048 dovecot: Oct 17 15:35:26 Warning: auth(default): Growing pool 'plain_auth_request' with: 2048 dovecot: Oct 17 15:35:27 Warning: auth(default): Growing pool 'plain_auth_request' with: 2048 dovecot: Oct 17 15:35:27 Warning: auth(default): Growing pool 'plain_auth_request' with: 2048 dovecot: Oct 17 15:35:41 Warning: auth(default): Growing pool 'plain_auth_request' with: 2048 dovecot: Oct 17 15:35:42 Warning: auth(default): Growing pool 'plain_auth_request' with: 2048 dovecot: Oct 17 15:35:47 Warning: auth(default): Growing pool 'plain_auth_request' with: 2048 dovecot: Oct 17 15:35:49 Warning: auth(default): Growing pool 'plain_auth_request' with: 2048 dovecot: Oct 17 15:35:49 Warning: auth(default): Growing pool 'plain_auth_request' with: 2048 dovecot: Oct 17 15:35:50 Warning: auth(default): Growing pool 'plain_auth_request' with: 2048 dovecot: Oct 17 15:35:56 Warning: auth(default): Growing pool 'plain_auth_request' with: 2048 dovecot: Oct 17 15:36:03 Warning: auth(default): Growing pool 'plain_auth_request' with: 2048 Does somebody has an idea, where to go to look into the issue? Bye, - -- Steffen Kaiser -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iQEVAwUBRxYYSi9SORjhbDpvAQL8JQf+KWGlq9ic5ufFKcc/hZu6ZUQCpvDTzQHy YGyCFWXNsMoumMEXieiUw6plGDqEWajrhuDNbWHLtc8NPykpopT29lBaxIL2up1R uY0FV02AIjtNbexoRnC9Fk+0z+keDBb9DtrgHDZeNeK+vizxFQeLIM2xtWgXky9t MjoUVYeuXPAb8kZPm3ryW10SadDIJOi7mmnPZFWscaBgN/3Pvf9/oakAaEJyezFj HJY3bYVj2SeblVnn8xFXxszFTV1I3IOM/vIQAtA6gJ4p5D5xXabGzyERgSck1jz6 OtdUIyLJmLdFq5jRdP2FtYyLyOdb27z7krxfFGXeAMbHxf3TCefaiA== =TVVY -END PGP SIGNATURE-
Re: [Dovecot] thunderbird and email duplication
Alexander Banthien wrote: > Hi all, > > I have recently switched over to Dovecot from CourierIMAP trying for > some speedup, which I did get. Installation went OK, so all seemed fine. > > But suddenly I realised, that incoming emails are replicating > themselves. This seems only to happen when connected with Thunderbird. I > am also using Squirrelmail and KMail as clients which don't seem to show > the behaviour. > It seems to happen only for mails received during a Thunderbird session. > When I close TBird and reopen it, only newly received messages will show > the funny behaviour. > The emails are real file copies in the Maildir, I have checked that. > > Running Dovecot on Debian Etch: dovecot --version: 1.0.0 (this is Debian > package 1:1.0.0-1~bpo.1 from backports. I have tried the main package > from Debian aswell, same result) with qmail delivering the mails to a > Maildir without Dovecot's LDA. > Clients: > Thunderbird 2.0.0.6 on WinXP over Wireless LAN (tried > Thunderbird/Iceweasel on Debian aswell) > Squirrelmail and KMail (both running on the same box as Dovecot) don't > show that behaviour. > > Has anybody seen anything similar or have any advice on what to look > for? I would like to stick with Dovecot but the way it is looking now, I > find working with emails near impossible. Hi, I had the same issue. Take a look at the logs of the smtp server. It was delivered again and again by my postfix. I don't know if this is related to dovecot and Thunderbird. But this was my first thought too. > > Thanks in advance, > > Alexander > -- andreas -- http://www.cynapses.org/ - cybernetic synapses signature.asc Description: OpenPGP digital signature
[Dovecot] thunderbird and email duplication
Hi all, I have recently switched over to Dovecot from CourierIMAP trying for some speedup, which I did get. Installation went OK, so all seemed fine. But suddenly I realised, that incoming emails are replicating themselves. This seems only to happen when connected with Thunderbird. I am also using Squirrelmail and KMail as clients which don't seem to show the behaviour. It seems to happen only for mails received during a Thunderbird session. When I close TBird and reopen it, only newly received messages will show the funny behaviour. The emails are real file copies in the Maildir, I have checked that. Running Dovecot on Debian Etch: dovecot --version: 1.0.0 (this is Debian package 1:1.0.0-1~bpo.1 from backports. I have tried the main package from Debian aswell, same result) with qmail delivering the mails to a Maildir without Dovecot's LDA. Clients: Thunderbird 2.0.0.6 on WinXP over Wireless LAN (tried Thunderbird/Iceweasel on Debian aswell) Squirrelmail and KMail (both running on the same box as Dovecot) don't show that behaviour. Has anybody seen anything similar or have any advice on what to look for? I would like to stick with Dovecot but the way it is looking now, I find working with emails near impossible. Thanks in advance, Alexander -- - Alexander Banthien ParentPay Ltd. Project Manager +44 1926 812704 (o) +44 7787 562694 (m) - This e-mail is from ParentPay Limited. The e-mail and any files transmitted with it may be confidential and are intended solely for the individual entity or entities to whom they are addressed. If you have received the e-mail in error please notify [EMAIL PROTECTED] or telephone 08700 420 550, and destroy the original. If you are not the intended recipient any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is prohibited and may be unlawful. Any contracts attached to this e-mail are in draft form only and are subject to legal review. They do not necessarily constitute an offer or commitment to do business on the part of ParentPay Limited. Any opinion expressed in this email is personal to the sender and does not necessarily represent the views of ParentPay Limited. This email cannot be relied upon to create a contract or any obligation on the part of ParentPay Limited.
[Dovecot] Problem with bodystructure/partial fetch using 1.1*
Hi there I'm using dovecot-1.1b2/b3 with deliver. All information is stored in an SQL database and no errors related to this issue are written to the logs (actually I get no errors at all). I've run into at problem; FETCH BODYSTRUCTURE is broken after upgrading to dovecot 1.1b2 (same issue with 1.1b3). BODUSTRUCTURE only returns information from the first section (with incorrect content-type/disposition) and discards everything else. This problem is somehow related to deliver; IMAP returns the correct BODYSTRUCTURE for e-mails received before the upgrade, but an incorrect for ones received after the upgrade. This tells me that IMAP is working properly but somehow the MIME sections are being corrupted doing mail delivery (if I fetch the complete body nothing seems to be wrong). Also if I fetch a section something is not right - instead of just the section I get part of the Content-type header as well (but only half the header). Obviously this makes various webmail clients go somewhat crazy while Outlook/Thunderbirds dont mind (since they fetch the complete body and do the MIME parsing themselves). These are my compile options (GCC 3.4.3 on Solaris 10): CPPFLAGS=-I/opt/pkgsrc/pkg/include/mysql LDFLAGS=-L/opt/pkgsrc/pkg/lib/mysql ./configure --prefix=/opt/freeware/dovecot-1.1b2 --with-pop3d --with-deliver --with-mysql --with-prefetch-userdb --with-sql --with-gnu-ld --with-ssl=no --enable-header-install make; make install Everything else works flawlessly. Have anyone else experienced at problem like this? Best wishes, Mikkel Configuration: /opt/freeware/dovecot-1.1b3/sbin/dovecot -c /local/config/dovecot2.conf -n # 1.1.beta3: /local/config/dovecot2.conf Warning: fd limit 256 is lower than what Dovecot can use under full load (more than 768). Either grow the limit or change login_max_processes_count and max_mail_processes settings log_path: /local/log/dovecot.run info_log_path: /local/log/dovecot.run protocols: imap pop3 ssl_disable: yes disable_plaintext_auth: no login_dir: /opt/freeware/dovecot-1.1b3/var/run/dovecot/login login_executable(default): /opt/freeware/dovecot-1.1b3/libexec/dovecot/imap-login login_executable(imap): /opt/freeware/dovecot-1.1b3/libexec/dovecot/imap-login login_executable(pop3): /opt/freeware/dovecot-1.1b3/libexec/dovecot/pop3-login login_process_per_connection: no first_valid_uid: 105 first_valid_gid: 105 mmap_disable: yes dotlock_use_excl: yes mail_nfs_storage: yes mail_nfs_index: yes mail_executable(default): /opt/freeware/dovecot-1.1b3/libexec/dovecot/imap mail_executable(imap): /opt/freeware/dovecot-1.1b3/libexec/dovecot/imap mail_executable(pop3): /opt/freeware/dovecot-1.1b3/libexec/dovecot/pop3 mail_plugins(default): quota imap_quota trash mail_plugins(imap): quota imap_quota trash mail_plugins(pop3): quota mail_plugin_dir(default): /opt/freeware/dovecot-1.1b3/lib/dovecot/imap mail_plugin_dir(imap): /opt/freeware/dovecot-1.1b3/lib/dovecot/imap mail_plugin_dir(pop3): /opt/freeware/dovecot-1.1b3/lib/dovecot/pop3 imap_client_workarounds(default): outlook-idle delay-newmail tb-extra-mailbox-sep imap_client_workarounds(imap): outlook-idle delay-newmail tb-extra-mailbox-sep imap_client_workarounds(pop3): pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh auth default: mechanisms: plain login digest-md5 cram-md5 ntlm rpa apop anonymous passdb: driver: sql args: /local/config/dovecot-sql2.conf userdb: driver: prefetch userdb: driver: sql args: /local/config/dovecot-sql2.conf socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix master: path: /var/run/dovecot/auth-master mode: 384 user: vmail plugin: quota: maildir quota_rule: *:storage=102400:messages=5000 quota_rule2: Trash:storage=10M trash: /local/config/dovecot-trash.conf
Re: [Dovecot] Released v1.1.beta3
Quoting Timo Sirainen: > Please try and report any bugs. Beta2 still had a few bad bugs, but I'm > hoping this release is near a usable state. I have the current revision from hg running and get this occasionally (already happened with beta2 revisions, I only never got around to report it): > Oct 17 04:51:18 seba dovecot: IMAP(jh): Disconnected in IDLE bytes=2596/34526 > Oct 17 04:51:18 seba dovecot: IMAP(jh): file client.c: line 105 > (client_destroy): assertion failed: (!client->destroyed) > Oct 17 04:51:18 seba dovecot: IMAP(jh): Raw backtrace: imap [0x80c1520] -> > imap [0x80c142c] -> imap [0x805ec7c] -> > imap(client_continue_pending_input+0x86) [0x805efd6] -> imap [0x805ac1d] -> > imap [0x805ae13] -> imap(client_command_cancel+0x1a) [0x805e2fa] -> > imap(client_destroy+0x60) [0x805eb00] -> imap [0x805acf0] -> > imap(io_loop_handler_run+0x107) [0x80c7437] -> imap(io_loop_run+0x28) > [0x80c67e8] -> imap(main+0x4ac) [0x806605c] -> > /lib/libc.so.6(__libc_start_main+0xe0) [0x948f70] -> imap [0x8058f61] > Oct 17 04:51:18 seba dovecot: child 31519 (imap) killed with signal 6 > Oct 17 04:51:18 seba dovecot: IMAP(jh): Disconnected in IDLE > bytes=7713/1170797 > Oct 17 04:51:18 seba dovecot: IMAP(jh): file client.c: line 105 > (client_destroy): assertion failed: (!client->destroyed) > Oct 17 04:51:18 seba dovecot: IMAP(jh): Raw backtrace: imap [0x80c1520] -> > imap [0x80c142c] -> imap [0x805ec7c] -> > imap(client_continue_pending_input+0x86) [0x805efd6] -> imap [0x805ac1d] -> > imap [0x805ae13] -> imap(client_command_cancel+0x1a) [0x805e2fa] -> > imap(client_destroy+0x60) [0x805eb00] -> imap [0x805acf0] -> > imap(io_loop_handler_run+0x107) [0x80c7437] -> imap(io_loop_run+0x28) > [0x80c67e8] -> imap(main+0x4ac) [0x806605c] -> > /lib/libc.so.6(__libc_start_main+0xe0) [0x948f70] -> imap [0x8058f61] > Oct 17 04:51:18 seba dovecot: IMAP(jh): Disconnected in IDLE > bytes=8203/1591288 > Oct 17 04:51:18 seba dovecot: IMAP(jh): file client.c: line 105 > (client_destroy): assertion failed: (!client->destroyed) > Oct 17 04:51:18 seba dovecot: IMAP(jh): Raw backtrace: imap [0x80c1520] -> > imap [0x80c142c] -> imap [0x805ec7c] -> > imap(client_continue_pending_input+0x86) [0x805efd6] -> imap [0x805ac1d] -> > imap [0x805ae13] -> imap(client_command_cancel+0x1a) [0x805e2fa] -> > imap(client_destroy+0x60) [0x805eb00] -> imap [0x805acf0] -> > imap(io_loop_handler_run+0x107) [0x80c7437] -> imap(io_loop_run+0x28) > [0x80c67e8] -> imap(main+0x4ac) [0x806605c] -> > /lib/libc.so.6(__libc_start_main+0xe0) [0x948f70] -> imap [0x8058f61] > Oct 17 04:51:19 seba dovecot: IMAP(jh): Disconnected in IDLE > bytes=99674/607896 > Oct 17 04:51:19 seba dovecot: IMAP(jh): file client.c: line 105 > (client_destroy): assertion failed: (!client->destroyed) > Oct 17 04:51:19 seba dovecot: child 17809 (imap) killed with signal 6 > Oct 17 04:51:19 seba dovecot: child 17810 (imap) killed with signal 6 > Oct 17 04:51:19 seba dovecot: child 17812 (imap) killed with signal 6 > Oct 17 04:51:19 seba dovecot: child 18171 (imap) killed with signal 6 > Oct 17 04:51:19 seba dovecot: IMAP(jh): Disconnected in IDLE > bytes=102318/1343347 > Oct 17 04:51:19 seba dovecot: IMAP(jh): file client.c: line 105 > (client_destroy): assertion failed: (!client->destroyed) > Oct 17 04:51:19 seba dovecot: IMAP(jh): Raw backtrace: imap [0x80c1520] -> > imap [0x80c142c] -> imap [0x805ec7c] -> > imap(client_continue_pending_input+0x86) [0x805efd6] -> imap [0x805ac1d] -> > imap [0x805ae13] -> imap(client_command_cancel+0x1a) [0x805e2fa] -> > imap(client_destroy+0x60) [0x805eb00] -> imap [0x805acf0] -> > imap(io_loop_handler_run+0x107) [0x80c7437] -> imap(io_loop_run+0x28) > [0x80c67e8] -> imap(main+0x4ac) [0x806605c] -> > /lib/libc.so.6(__libc_start_main+0xe0) [0x948f70] -> imap [0x8058f61] The "Disconnected in IDLE" seems to be legit, so the following crash is not that bad, only that it looks horrible...
[Dovecot] feedback ?
Hello guys, I chose Dovecot to run on an RHEL 5, comunicating with an AD server for users query over LDAP. Any tips ? What version you suggest could fit the best on that distro ?
Re: [Dovecot] Migration to Dovecot
Hi Frank, Tomorrow is the day , I'm gonna migrate all our mailboxes and imap folders from our old mailhub to the new one. In the same time I will migrate from UW to Dovecot , I've read all the stuff about it on the Dovecot web site. I have one question , do I have to care about the .imap cache directory created by Dovecot in any way or will it be "all automatic" when starting Dovecot ? I handle a few courier-imap to dovecot migration recently and the only thing I had to care about was the indox namespace (perhaps not an issue on UW), subscription files, and shared folders. Everything else was transparent. Cheers, Denis Many thanks -- Denis Cardon Tranquil IT Systems 44 bvd des pas enchantés 44230 Saint Sébastien sur Loire tel : +33 (0) 2.40.97.62.67 http://www.tranquil-it-systems.fr
