Re: [Dovecot] Archiving mail
On Thursday, July 18, 2013 07:14 AM CDT, Koenraad Lelong dove...@ace-electronics.be wrote: Hi, I'm going to migrate my company-mailserver to new hardware. I would like to take the opportunity to archive some older mail. But I would like to have it still accessible, would this be possible with dovecot ? I mean, I would like to put that older mail from different users (I got about 50 users) on some read-only media but mount that media in the users mail-dirs. That way I will have less to backup after I backup that old mail and store it safely away. I can't convince my users to really clean up their mailboxes, so I backup more than 100GB mail while the total backup is a bit more than 300GB. Writing this I realise I could give each user a folder oldmail and symlink that to a read-only oldmail folder. Would this work ? I will have to find out how my backup-software can ignore the oldmail-folder. Thanks for any suggestions, Koenraad Lelong It sounds like you are looking for something similar to dbmail: www.dbmail.org. It will allow all the mail to still be readable by the end user but the archived mail will not be deletable or editable. We were looking at something like that but are probably going to end up going with something like enkive: http://www.enkive.org/ -- Donny B.
[Dovecot] Sieve mark message as read
I am trying to get the advanced functionality of managesieve working for our users. If this is not the proper place to ask this, please just say so. I have enabled sieve and it works just fine for basic moving messages to folders. However the problem comes in to play when a user selects something like delete or mark as read in the filter. It just simply does not do that function. I have installed the imapflags and imap4flags and added the needed parts to the dovecot config but it still does not seem to work. We are running Centos 6.3 with dovecot-2.0.9-2.el6_1.1.x86_64 and dovecot-pigeonhole-2.0.9-2.el6_1.1.x86_64 installed. What could I be missing to make this work? -- Donny B.
Re: [Dovecot] Sieve mark message as read
On Wednesday, March 13, 2013 02:43 PM CDT, Robert Schetterer r...@sys4.de
wrote:
Am 13.03.2013 19:51, schrieb Donny Brooks:
I am trying to get the advanced functionality of managesieve working for
our users. If this is not the proper place to ask this, please just say so.
I have enabled sieve and it works just fine for basic moving messages to
folders. However the problem comes in to play when a user selects something
like delete or mark as read in the filter. It just simply does not do
that function. I have installed the imapflags and imap4flags and added the
needed parts to the dovecot config but it still does not seem to work. We
are running Centos 6.3 with dovecot-2.0.9-2.el6_1.1.x86_64 and
dovecot-pigeonhole-2.0.9-2.el6_1.1.x86_64 installed. What could I be
missing to make this work?
try
http://wiki2.dovecot.org/Pigeonhole/Sieve/Configuration?highlight=%28flags%29
sieve_extensions =
Which Sieve language extensions are available to users. By default,
all supported extensions are available, except for deprecated
extensions, extensions that require explicit configuration or those that
are still under development. Some system administrators may want to
disable certain Sieve extensions or enable those that are not available
by default. All supported extensions are listed here. Normally, all
enabled extensions must be listed for this setting, but starting with
Sieve version 0.1.7, this setting can use '+' and '-' to specify
differences relative to the default. For example sieve_extensions =
+imapflags will enable the deprecated imapflags extension in addition to
all extensions enabled by default.
...
From CMUSieve (Dovecot v1.0/v1.1)
For the most part, migration from CMUSieve to Pigeonhole Sieve is just a
matter of changing the used plugin name from cmusieve to sieve in the
mail_plugins option in the protocol lda section of the config file (as
explained above). However, there are a few important differences in the
supported Sieve language features:
The imapflags extension is now called imap4flags. The CMUSieve
implementation is based on an old draft specification that is not
completely compatible with the new version. Particularly, the mark and
unmark commands were removed from the new specification. For backwards
compatibility, support for the old imapflags extension can be enabled
using the sieve_extensions setting (as explained above). This is
disabled by default.
Best Regards
MfG Robert Schetterer
--
[*] sys4 AG
http://sys4.de, +49 (89) 30 90 46 64
Franziskanerstraße 15, 81669 München
Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263
Vorstand: Patrick Ben Koetter, Axel von der Ohe, Marc Schiffbauer
Aufsichtsratsvorsitzender: Joerg Heidrich
Right, my line in /etc/dovecot/conf.d/90-sieve.conf looks like this:
sieve_extensions = +notify +imap4flags +imapflags
I have tried it without the +imapflags, leaving only the first two, also with
same results. Part of my sieve script that has the mark as seen is as follows:
if anyof (header :is subject Check dd) {
fileinto Junk;
addflag \\Seen;
}
When I send myself an email from a different account with the subject Check
dd it is properly filed in the Junk folder but it still remains unseen. Any
ideas?
--
Donny B.
Re: [Dovecot] Sieve mark message as read
On Wednesday, March 13, 2013 03:28 PM CDT, Donny Brooks
dbro...@mdah.state.ms.us wrote:
On Wednesday, March 13, 2013 02:43 PM CDT, Robert Schetterer r...@sys4.de
wrote:
Am 13.03.2013 19:51, schrieb Donny Brooks:
I am trying to get the advanced functionality of managesieve working for
our users. If this is not the proper place to ask this, please just say
so. I have enabled sieve and it works just fine for basic moving messages
to folders. However the problem comes in to play when a user selects
something like delete or mark as read in the filter. It just simply
does not do that function. I have installed the imapflags and imap4flags
and added the needed parts to the dovecot config but it still does not
seem to work. We are running Centos 6.3 with
dovecot-2.0.9-2.el6_1.1.x86_64 and
dovecot-pigeonhole-2.0.9-2.el6_1.1.x86_64 installed. What could I be
missing to make this work?
try
http://wiki2.dovecot.org/Pigeonhole/Sieve/Configuration?highlight=%28flags%29
sieve_extensions =
Which Sieve language extensions are available to users. By default,
all supported extensions are available, except for deprecated
extensions, extensions that require explicit configuration or those that
are still under development. Some system administrators may want to
disable certain Sieve extensions or enable those that are not available
by default. All supported extensions are listed here. Normally, all
enabled extensions must be listed for this setting, but starting with
Sieve version 0.1.7, this setting can use '+' and '-' to specify
differences relative to the default. For example sieve_extensions =
+imapflags will enable the deprecated imapflags extension in addition to
all extensions enabled by default.
...
From CMUSieve (Dovecot v1.0/v1.1)
For the most part, migration from CMUSieve to Pigeonhole Sieve is just a
matter of changing the used plugin name from cmusieve to sieve in the
mail_plugins option in the protocol lda section of the config file (as
explained above). However, there are a few important differences in the
supported Sieve language features:
The imapflags extension is now called imap4flags. The CMUSieve
implementation is based on an old draft specification that is not
completely compatible with the new version. Particularly, the mark and
unmark commands were removed from the new specification. For backwards
compatibility, support for the old imapflags extension can be enabled
using the sieve_extensions setting (as explained above). This is
disabled by default.
Best Regards
MfG Robert Schetterer
--
[*] sys4 AG
http://sys4.de, +49 (89) 30 90 46 64
Franziskanerstraße 15, 81669 München
Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263
Vorstand: Patrick Ben Koetter, Axel von der Ohe, Marc Schiffbauer
Aufsichtsratsvorsitzender: Joerg Heidrich
Right, my line in /etc/dovecot/conf.d/90-sieve.conf looks like this:
sieve_extensions = +notify +imap4flags +imapflags
I have tried it without the +imapflags, leaving only the first two, also with
same results. Part of my sieve script that has the mark as seen is as
follows:
if anyof (header :is subject Check dd) {
fileinto Junk;
addflag \\Seen;
}
When I send myself an email from a different account with the subject Check
dd it is properly filed in the Junk folder but it still remains unseen. Any
ideas?
--
Donny B.
I think I see part of my problem. I am using postfix and dovecot. So in the
postfix main.cf I have this:
mailbox_command = /usr/libexec/dovecot/deliver -a $RECIPIENT
While that was fine when we were on the 1.X branch on our old mail server I
think it needs to be changed to something more like this:
mailbox_command = /usr/libexec/dovecot/dovecot-lda -f $SENDER -a $RECIPIENT
Ideas?
--
Donny B.
Re: [Dovecot] Sieve mark message as read
On Wednesday, March 13, 2013 03:46 PM CDT, Donny Brooks
dbro...@mdah.state.ms.us wrote:
On Wednesday, March 13, 2013 03:28 PM CDT, Donny Brooks
dbro...@mdah.state.ms.us wrote:
On Wednesday, March 13, 2013 02:43 PM CDT, Robert Schetterer r...@sys4.de
wrote:
Am 13.03.2013 19:51, schrieb Donny Brooks:
I am trying to get the advanced functionality of managesieve working
for our users. If this is not the proper place to ask this, please just
say so. I have enabled sieve and it works just fine for basic moving
messages to folders. However the problem comes in to play when a user
selects something like delete or mark as read in the filter. It
just simply does not do that function. I have installed the imapflags
and imap4flags and added the needed parts to the dovecot config but it
still does not seem to work. We are running Centos 6.3 with
dovecot-2.0.9-2.el6_1.1.x86_64 and
dovecot-pigeonhole-2.0.9-2.el6_1.1.x86_64 installed. What could I be
missing to make this work?
try
http://wiki2.dovecot.org/Pigeonhole/Sieve/Configuration?highlight=%28flags%29
sieve_extensions =
Which Sieve language extensions are available to users. By default,
all supported extensions are available, except for deprecated
extensions, extensions that require explicit configuration or those that
are still under development. Some system administrators may want to
disable certain Sieve extensions or enable those that are not available
by default. All supported extensions are listed here. Normally, all
enabled extensions must be listed for this setting, but starting with
Sieve version 0.1.7, this setting can use '+' and '-' to specify
differences relative to the default. For example sieve_extensions =
+imapflags will enable the deprecated imapflags extension in addition to
all extensions enabled by default.
...
From CMUSieve (Dovecot v1.0/v1.1)
For the most part, migration from CMUSieve to Pigeonhole Sieve is just a
matter of changing the used plugin name from cmusieve to sieve in the
mail_plugins option in the protocol lda section of the config file (as
explained above). However, there are a few important differences in the
supported Sieve language features:
The imapflags extension is now called imap4flags. The CMUSieve
implementation is based on an old draft specification that is not
completely compatible with the new version. Particularly, the mark and
unmark commands were removed from the new specification. For backwards
compatibility, support for the old imapflags extension can be enabled
using the sieve_extensions setting (as explained above). This is
disabled by default.
Best Regards
MfG Robert Schetterer
--
[*] sys4 AG
http://sys4.de, +49 (89) 30 90 46 64
Franziskanerstraße 15, 81669 München
Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263
Vorstand: Patrick Ben Koetter, Axel von der Ohe, Marc Schiffbauer
Aufsichtsratsvorsitzender: Joerg Heidrich
Right, my line in /etc/dovecot/conf.d/90-sieve.conf looks like this:
sieve_extensions = +notify +imap4flags +imapflags
I have tried it without the +imapflags, leaving only the first two, also
with same results. Part of my sieve script that has the mark as seen is
as follows:
if anyof (header :is subject Check dd) {
fileinto Junk;
addflag \\Seen;
}
When I send myself an email from a different account with the subject
Check dd it is properly filed in the Junk folder but it still remains
unseen. Any ideas?
--
Donny B.
I think I see part of my problem. I am using postfix and dovecot. So in the
postfix main.cf I have this:
mailbox_command = /usr/libexec/dovecot/deliver -a $RECIPIENT
While that was fine when we were on the 1.X branch on our old mail server I
think it needs to be changed to something more like this:
mailbox_command = /usr/libexec/dovecot/dovecot-lda -f $SENDER -a
$RECIPIENT
Ideas?
--
Donny B.
I found the issue I believe. Instead of my filter filing the message into the
folder first then mark as seen I had to do the opposite. This is the proper
syntax now:
if anyof (header :is subject Check dd) {
addflag \\Seen;
fileinto Junk;
}
Sorry for all the noise.
--
Donny B.
[Dovecot] Best setup for performance and fault tolerance
Hello all. I am in need of some guidance. First a little background. Currently our mail server is on physical hardware (Dell server with 2x 2.8GHz Xeon w/ 4GB ram, raid5 array, single gigabit nic) running on Fedora 11 and postfix-2.5.6-3.fc11.x86_64 with dovecot-1.2.11-3.fc11.x86_64. Mailstore is via Maildir format that was converted from mbox about a year ago. This same machine is also our PDC with samba, Master LDAP, slave MySQL replication, primary DNS, and home server for about 20 users. We have approximately 200 end users that have mailboxes on the server ranging from 1KB to 20GB in size. Total mail store is currently at 300GB. About 75 of the users are currently POP access and their mail will be moved to the server soon and setup as IMAP. This is calculated to add roughly another 150GB of mail for a total of 450GB mail store. Being a state agency we have to keep the mail indefinitely for public record reasons. We use a mixture of Thunderbird as an IMAP client and SOGo for web access. Now to the problem: Recently we have been having super slow access to the mail server. Turns out the load was insanely high partially due to the samba home server portion, which is being moved off as we speak, and the other part is due to people searching their mail. Just yesterday one of our users nearly brought the entire agency to its knees by performing a search on her 8GB of mail via IMAP. Since the server is old in both hardware and software I have been tasked with moving it to newer hardware and a newer OS. We currently have 3 virtual servers running Xen and a SAN. The new setup will be placed in the virtual environment. I will probably run Fedora 16 as the OS but am open to Centos, Fedora, or Ubuntu. Now to the question: What is the best way to setup Dovecot so that it is tuned for performance and high available? We have been running with this single point of failure for years so as long as we are moving the mail server we might as well build in some redundancy. To solve the searching problem I thought of maybe setting up some type of indexing. I do kind of want to break the various services out on to separate virtual machines for a little more fault tolerance, but that is not totally necessary. What do you think of things like iRedmail? I see it's usefulness but the not being able to separate services kind of defeats the purpose, plus I want to setup a high available MySQL cluster and possibly OpenLDAP or 389 cluster so iRedMail may not be the best solution. Sorry for the long email but I am trying to get all the information out there at once so it will help get more directed responses in the shortest amount of time. I look forward to any and all input on this matter -- Donny B MDAH
Re: [Dovecot] web interface for user creation/vacation
On 8/1/2011 8:01 PM, Stephan Bosch wrote: On 8/2/2011 1:55 AM, Chris Cappuccio wrote: Are there any decent front-ends to setup/manage per-user sieve filters? There are several, but so far I am not too impressed by any of them. Most web-based versions are part of a webmail suite. The nicest one I've seen so far is the sieverules plugin for Roundcube. Then there is horde/ingo, which wasn't that fancy last time I looked. There is also squirrelmail/avelsieve, which is a bit ugly in a technical point of view, but it works quite well. There are older ones like smartsieve and websieve, but those are not maintained anymore and not compatible with Dovecot without patching them. I'm hoping that someone writes a proper (native) PHP module for Sieve parsing in the near future. This is something that is currently barely done by web interfaces, with the effect that only one Sieve client can be used at the same time, because competitive clients will overwrite/mangle scripts of others, instead of trying to parse and adjust them. In fact, the only client I know (including the desktop ones) that somewhat parses the script on the server is the sieverules plugin for Roundcube.Therefore such a PHP module solves only part of the problem: web interfaces. Normal mail clients like Thunderbird, Outlook and Evolution don't have (proper) support for Sieve either, let alone script parsing functionality with a user-friendly GUI :/ Perhaps we should make a list of the available clients on the wiki somewhere with some information on how well these work with Dovecot. There is a short list at http://sieve.info/clients. Regards, Stephan. It is not a standalone frontend but the vacation management portion of SOGo (http://sogo.nu/english.html) works well in our tests. Donny B.
Re: [Dovecot] Best way to migrate versions and machines
On 2/17/2011 9:29 AM, Donny Brooks wrote: We are looking to migrate from our current mail server running dovecot-1.2.11-3 to a new mail server running the latest dovecot (2.0.9?). So this would not only be a version change but also a machine change. We currently use Maildir for storing mail and would like to stay that way. Has anyone preformed such a feat and it worked? Looking for any input. I have looked through the docs and can't seem to find anything that would pertain to my situation. Unless I totally missed it. Anyone have any pointers?
Re: [Dovecot] Best way to migrate versions and machines
On 2/21/2011 9:46 AM, Rick Romero wrote: Quoting Ed W li...@wildgooses.com: On 17/02/2011 15:29, Donny Brooks wrote: We are looking to migrate from our current mail server running dovecot-1.2.11-3 to a new mail server running the latest dovecot (2.0.9?). So this would not only be a version change but also a machine change. We currently use Maildir for storing mail and would like to stay that way. Has anyone preformed such a feat and it worked? Looking for any input. I've done it two ways - Rsync and ZFS snapshots. Both methods are pretty much the same. I have multiple satellites doing SMTP incoming/outgoing and dovecot on a primary 'file server' with NFS exports. 1. replicate all data 2. replicate diff data (do this until the update window is small) 3. disable deliveries (for me, disable qmail-send, umount NFS mounts) 4. replicate diff data 5. turn off IMAP/POP 6. replicate diff data 7. Migrate IP address/Change FW rules/etc 8. Turn on IMAP/POP 9. Turn on deliveries For my last ZFS migration I only had 2 minutes of 'downtime' from the user's perspective (Step 5 - Step 8), as the necessary changes were already staged. Rick Sounds similar to what I was thinking. I was just not sure if there was some unforeseen gotchas that others had dealt with before. The move to a new version is usually not that bad but I knew moving machines with versions could be hazardous. I may end up upgrading the local copy to 2.0.9 before the move so they will be similar.
Re: [Dovecot] Best way to migrate versions and machines
On 2/21/2011 1:59 PM, Ed W wrote: Sounds similar to what I was thinking. I was just not sure if there was some unforeseen gotchas that others had dealt with before. The move to a new version is usually not that bad but I knew moving machines with versions could be hazardous. I may end up upgrading the local copy to 2.0.9 before the move so they will be similar. Perhaps, but did you not like my suggestion that you could have basically both versions live at the same time? To recap, rsync (etc) some data across to the new server which has been upgraded to dovecot2. Set proxy to forward some test users to the new server. Test it thoroughly, copy over a few more accounts, repeat testing, etc This keeps both old and new servers running at all times and the proxy feature allows you to push users across even one by one (or do a bulk move). Remember, apart from the slight gremlin that the dovecot index files get made non v1 compatible by the v2 server, the data can be copied back/forward between servers and most MUAs will likely not notice the difference between your v1.2 and v2 installation... Don't get over-fixated on the server version, focus on not ending up without a working server during the process Good luck Ed W That makes better sense. I did not realize you meant to leave both live during the process. Thanks for clarifying that.
Re: [Dovecot] dovecot Digest, Vol 94, Issue 44
On 2/17/2011 9:35 AM, Alan Brown wrote: Date: Wed, 16 Feb 2011 07:04:55 + (GMT) From: Spyros Tsiolis sts...@yahoo.co.uk Subject: [Dovecot] [Off Topic] - Any backup solutions ? To: Dovecot dovecot@dovecot.org Message-ID: 627531.34045...@web27203.mail.ukl.yahoo.com Content-Type: text/plain; charset=utf-8 OK, I know this is not for this list; However, reading all these mails on the topic of filesystems, I thought that it's a good place to ask about backup software on linux. Bacula works very well and scales to both small and large setups extremely easily. www.bacula.org Backuppc is very nice also. http://backuppc.sf.net
Re: [Dovecot] blackberry emails
On 10/27/2010 8:17 AM, dhottin...@harrisonburg.k12.va.us wrote: Does anyone have clients using blackberrys to access their emails on a dovecot server? If so are there any gotcha's that I need to configure in dovecot for this to work? Looks like all emails go to and from a blackberry server before getting to clients. thanks, ddh If you are referring to using a BES (Blackberry Enterprise Server) then I don't think it will work with dovecot. As far as I know BES only works with Exchange and Novell groupwise. If you want to forward the emails to a standard BIS account though that should work except replying to those emails will come from the carrier network and not your own. Donny B.
Re: [Dovecot] blackberry emails
On 10/27/2010 12:06 PM, Frank Bonnet wrote: Le 27/10/2010 15:21, Donny Brooks a écrit : On 10/27/2010 8:17 AM, dhottin...@harrisonburg.k12.va.us wrote: Does anyone have clients using blackberrys to access their emails on a dovecot server? If so are there any gotcha's that I need to configure in dovecot for this to work? Looks like all emails go to and from a blackberry server before getting to clients. thanks, ddh If you are referring to using a BES (Blackberry Enterprise Server) then I don't think it will work with dovecot. As far as I know BES only works with Exchange and Novell groupwise. If you want to forward the emails to a standard BIS account though that should work except replying to those emails will come from the carrier network and not your own. Donny B. I think Blackberry servers are able to connect to Dovecot as many students here use Blackberry and I can see many connections from RIM on my server , so I think there is some mechanisms to configure Blackberry to fetch private emails. Yes you are referring to standard BIS service. That is what any blackberry has when you get it from any carrier. There is a way to have it connect to a personal email account on an imap server. I actually have a dovecot/postfix server doing one of my domains email and have the email delivered to my berry. It just is not instantly pushed to the phone like it is with BIS/BES hosted emails.
Re: [Dovecot] Exchange-replacement with SOGo
On 10/26/2010 12:12 AM, Mohit Chawla wrote: Hi, On Tue, Oct 26, 2010 at 8:08 AM, Timo Sirainent...@iki.fi wrote: They seem to prefer Cyrus, but apparently Dovecot should work too. I have been using Dovecot 1.2.13 with it, works just fine. Plus, sieve support's also there, which is cool. We have been using SOGo for about 9 months now and really like it. We are using our standard Postfix/Dovecot with MySQL backend for calendar and OpenLDAP for contacts. I have to wait for the openchange parts to become part of the release version before I can mess with it too much. It would be nice to be able to have a BES server talking to SOGo through openchange .
Re: [Dovecot] Convert plugin
On 10/15/2010 1:10 PM, Timo Sirainen wrote:
On Wed, 2010-10-06 at 22:01 +0200, Egbert Jan van den Bussche wrote:
I'm trying the example from the wiki:
plugin {
convert_mail = mbox:~/mail:INBOX=/var/mail/%n
}
but have still not succeded.
Did you figure it out already? The problem is that you have no ~/mail/
directory, convert plugin doesn't then do anything because it thinks the
mails are already converted. Either you need to create those dirs, or
maybe it's easier to just use one of the scripts and do all the users at
once some weekend.
Be sure your mail in /home/username is stored in mail and not Mail.
Otherwise change the ~/mail to ~/Mail and it will work. This is what
mine was. Also check the /var/mail/%n portion. Mine was stored in
/var/spool/mail/%n.
Donny B.
Re: [Dovecot] migrate machines and upgrade
On 10/6/2010 4:18 PM, Donny Brooks wrote: I am about to be migrating mail servers and have a few questions. First a little background: Old mail server: Fedora 11 dovecot-1.2.11-3.fc11.x86_64 installed from yum repo mbox mail format OpenLDAP authentication 250+ users New mail server: Fedora 13 dovecot-2.0.1-1_118.fc13.x86_64 installed from atrpm rpm file Maildir mail format OpenLDAP authentication 250+ users I plan to use dsync on the new machine to migrate the mail off the old machine and mbox format to the new machine and Maildir. I think I read where I can do the migration without interfering with normal mail delivery and then when i get ready to do the final move I just kill dovecot on the old machine, dsync once more, and start the service on the new machine. What would be the best way to accomplish this? And as for the configuration changed between 1.2.11 and 2.0.1, where to start? I see there is now a conf.d directory for 2.0.1. How will this tie in to the 1.2.11 config? Any pointers there? Other option is to move the mbox mail as it sits to the new machine, install 1.2.X branch dovecot on new machine, and let the convert plugin do all the work. However I like the idea of the dsync doing the sync with minimal downtime. Thanks in advance. Ok, I found the way to convert the configuration. However I am still having issues trying to get the right way to migrate the users from the old machine on 1.2.11 and mbox to the new one on 2.0.1 and Maildir. I am trying the dsync commands on the wiki to use ssh to no avail due to it still being 1.2.11 on the old server. I am slowly trying various mirror commands, but if anyone has any pointers that can help speed this along I will be much appreciative. Here is what I have tried thus far: As root I su to my user on the new server: -bash-4.1# su - dbrooks then tried the dsync command as in the wiki: -bash-4.1$ dsync -u dbrooks mirror dbro...@roark dsync(dbrooks): Error: userdb lookup: connect(/var/run/dovecot/auth-userdb) failed: Permission denied (euid=879(dbrooks) egid=100(users) missing +r perm: /var/run/dovecot/auth-userdb, euid is not dir owner) dsync(dbrooks): Fatal: User lookup failed: Internal error occurred. Refer to server log for more information. No go so I go back to root login and try it that way, still on the new machine: -bash-4.1$ logout -bash-4.1# dsync -u dbrooks mirror dbro...@roark r...@roark's password: bash: dsync: command not found dsync-local(dbrooks): Error: read() from worker server failed: EOF Now I try the ssh command from the new machine as root: -bash-4.1# ssh dbro...@roark dsync -u dbrooks dbro...@roark's password: bash: dsync: command not found -bash-4.1# I am lost. I am sure it is something simple I am missing. Donny B.
Re: [Dovecot] migrate machines and upgrade
On Friday, October 08, 2010 02:33 PM CDT, Charles Marcus cmar...@media-brokers.com wrote: Please don't top-post... I do apologize, I was using my webmail program and it was not setup properly On 2010-10-08 3:15 PM, Donny Brooks wrote: On Friday, October 08, 2010 02:01 PM CDT, Charles Marcus cmar...@media-brokers.com wrote: On 2010-10-08 2:53 PM, Donny Brooks wrote: I don't think the version matters much at this point though. 2.0 has been a bit buggy, so in this case, it does matter... Gotcha, so should I stay with the 1.2.xx branch and just use the mail_convert plugin? Or upgrade to 2.0.5 on the new server and still use doveadm - this is probably best if you can... The newest I see for an rpm is 2.0.4 on the atrpms site. We try not to build from source due to the way a previous admin messed things up. Any pointers on a source for the 2.0.5 rpm? Honestly though, I'm not really the best one to be advising you on this (I know enough to be dangerous, have played with the tools, but don't provide any warranties, etc)... The only issue I have with that one is that I can't do it gradually and it pegs the server for all it has when a user is converted. You can convert one or a few at a time, and I don't see any reason why you couldn't 'nice' the process somehow (not sure exactly how though)... Is there a better way to migrate from mbox to Maildir and also from old machine to new? That is my end goal, migrate to new machine and to Maildir. Anything else is not really a huge deal. I think the best thing would be to do what you need to do to get 2.0.5 installed on the new server, make sure it is working properly in your environment and for your use case, then migrate the users. How many users do you have? I'm fairly certain there is a good way to do this mostly automated in batches... We have about 160 users I believe at last count. Mail boxes range in size from a few MB to around 8GB. Being a state agency, they tell us we cannot delete any mail. This is why I am wanting to switch to Maildir so I can migrate old messages off to a different machine/disk for archival purposes but still remain accessible. -- Best regards, Charles -- Donny B.
Re: [Dovecot] migrate machines and upgrade
On Friday, October 08, 2010 02:52 PM CDT, Jakob Curdes j...@info-systems.de wrote: Am 08.10.2010 21:15, schrieb Donny Brooks: Gotcha, so should I stay with the 1.2.xx branch and just use the mail_convert plugin? The only issue I have with that one is that I can't do it gradually and it pegs the server for all it has when a user is converted. Is there a better way to migrate from mbox to Maildir and also from old machine to new? That is my end goal, migrate to new machine and to Maildir. Anything else is not really a huge deal. From what I have seen and experienced I would install a 2.0.x, x=5, perhaps waiting until a matching rpm is provided by somebody. The 2.0 series is a huge improvement, but as always with new software, with the first versions a bunch of problems is being uncovered. As for the migration, have you had a look at imapsync? With that tool I migrated lots of mailboxes user-wise from one imap server to another. HTH, Jakob Curdes *insert Homer Simpson sound...* D'OH! I totally forgot about imapsync. I played with it a few months back but totally forgot about it. Thanks for reminding me! -- Donny B.
[Dovecot] migrate machines and upgrade
I am about to be migrating mail servers and have a few questions. First a little background: Old mail server: Fedora 11 dovecot-1.2.11-3.fc11.x86_64 installed from yum repo mbox mail format OpenLDAP authentication 250+ users New mail server: Fedora 13 dovecot-2.0.1-1_118.fc13.x86_64 installed from atrpm rpm file Maildir mail format OpenLDAP authentication 250+ users I plan to use dsync on the new machine to migrate the mail off the old machine and mbox format to the new machine and Maildir. I think I read where I can do the migration without interfering with normal mail delivery and then when i get ready to do the final move I just kill dovecot on the old machine, dsync once more, and start the service on the new machine. What would be the best way to accomplish this? And as for the configuration changed between 1.2.11 and 2.0.1, where to start? I see there is now a conf.d directory for 2.0.1. How will this tie in to the 1.2.11 config? Any pointers there? Other option is to move the mbox mail as it sits to the new machine, install 1.2.X branch dovecot on new machine, and let the convert plugin do all the work. However I like the idea of the dsync doing the sync with minimal downtime. Thanks in advance. -- Donny B.
Re: [Dovecot] Migrating mail from mbox to maildir using dovecot
This actually looks like the way I will look into doing it. That way I can migrate the ones that have close to 8GB of mail on a weekend and the rest that are typical with a few hundred MB any old time. Now just to figure out the proper syntax for ldap. ;) -- Donny B. On Tuesday, September 14, 2010 11:02 AM CDT, Charles Marcus cmar...@media-brokers.com wrote: On 2010-09-14 11:51 AM, Donny Brooks dbro...@mdah.state.ms.us wrote: So once I setup postfix to deliver the mail properly and the dovecot convert plugin is setup, is there a way to gradually migrate the users so I don't kill the server? We have about 220GB or so of mail between about 160+/- users. What would be the best way to migrate it all to maildir? I can't give you precise instructions, but from the bottom of the Plugins wiki page: To enable / disable plugins per user you can make your userdb return mail_plugins extra field. See UserDatabase/ExtraFields for examples. http://wiki1.dovecot.org/UserDatabase/ExtraFields So you could enable the convert plugin on a per user basis and do them one at a time or in small groups... -- Best regards, Charles
Re: [Dovecot] Migrating mail from mbox to maildir using dovecot
I think I will have to stay with the 1.x branch since we have to stick to using approved rpm's (internal policy) and fedora 13 does not have a 2.x branch that I see yet. So maildir it is for now. I see my error on the inbox not getting the new mail. That was one of those all nighter errors that I just plain missed due to lack of sleep. I forgot to point postfix to the proper place to deliver the mail. So once I setup postfix to deliver the mail properly and the dovecot convert plugin is setup, is there a way to gradually migrate the users so I don't kill the server? We have about 220GB or so of mail between about 160+/- users. What would be the best way to migrate it all to maildir? -- Donny B. On Sunday, September 12, 2010 02:56 AM CDT, William Blunn b...@blunn.org wrote: On 11/09/2010 20:17, Donny Brooks wrote: On the old mail server it is: dovecot-1.2.11-3.fc11.x86_64 On the new mail server we are migrating to it is: dovecot-1.2.14-1.fc13.x86_64 currently Is there a repo out there that I can install 2.0 from? The only one I have found is atrpms and it is a pain to get conflict worked out with other packages. If you use Dovecot 2.0 you also get the choice of multi-dbox. http://wiki2.dovecot.org/MailboxFormat/dbox This would give you some advantages: * With multi-dbox, multiple messages are stored in the same file. But once a mail file contains 2 megabytes (configurable), Dovecot moves on to a new file and leaves the old files unchanging. This should be quite nice for your backup strategy because you would only backup the current file for each user, limited to 2 megabytes per user (or whatever amount you think appropriate). * With multi-dbox, if you have many small messages, these are all stored in the same file. This vastly reduces the number of files required to store mail, which means fewer inodes consumed, and I think backup systems often work better with a smaller number of larger files than a larger number of smaller files. If you use multi-dbox, you will need to use a Dovecot delivery software (e.g. dovecot-lda). Bill
[Dovecot] Migrating mail from mbox to maildir using dovecot
Hello, Currently our mail server is setup to use postfix and dovecot, which is fine except it is setup to use mbox format mail. That and procmail as we need to move to sieve but that is a different issue. I have searched until blue in the face and cannot find a 100% working solution that doesn't require alot of manual interaction to move the mail boxes from mbox to maildir. I have tried the mb2md.pl stuff but with over 150+ users that can get tedious having to log in as each one of them to migrate them. I also tried the convert plugin located here: http://wiki.dovecot.org/Plugins/Convert but it kept erroring about not able to convert the box and exiting. We have approx 200GB of mail total that needs to be migrated. Maybe I am just simply missing something but is there a way that we can migrate all the users with minimal end user interaction and minimal administration time? We need this done asap as our backups are killing us with the large mbox style files. Thanks in advance for any and all input to this. -- Donny B.
Re: [Dovecot] Migrating mail from mbox to maildir using dovecot
On Saturday, September 11, 2010 10:28 AM CDT, Charles Marcus cmar...@media-brokers.com wrote: On 2010-09-11 3:14 AM, Donny Brooks dbro...@mdah.state.ms.us wrote: Currently our mail server is setup to use postfix and dovecot, Version of DC? On the old mail server it is: dovecot-1.2.11-3.fc11.x86_64 On the new mail server we are migrating to it is: dovecot-1.2.14-1.fc13.x86_64 currently Is there a repo out there that I can install 2.0 from? The only one I have found is atrpms and it is a pain to get conflict worked out with other packages. I have searched until blue in the face and cannot find a 100% working solution that doesn't require alot of manual interaction to move the mail boxes from mbox to maildir. Dovecot 2.0 would use dsync, and it should be really easy and avoids most problems the other methods can have (haven't used it yet myself, but will on a system I'll be upgrading soon)... http://wiki2.dovecot.org/Migration/MailFormat But either way, to avoid doing each one manually you'll need to use some scripting magic. If I were doing it, I'd probably write a script (or more likely hire someone to do it for me, since my scripting skills are rudimentary at best) that would run at the least busy time of day for your system, and iterate through the user: disable login kill any existing processes for that user run dsync to convert everything re-enable login rinse, repeat. I also tried the convert plugin located here: http://wiki.dovecot.org/Plugins/Convert but it kept erroring about not able to convert the box and exiting. Did you ask here about the errors? Timo could probably address any problems your having very quickly. -- Best regards, Charles Most likely I will need to stick for now to the 1.x branch and just use the convert plugin. I will dig for the error again and see what it was. I will send a new message with the details on that. Thanks for the input. -- Donny B.
[Dovecot] Proper use of convert plugin?
I am trying to convert from mbox to maildir on our mail server here at work.
The specs are as follows:
Fedora 11 x86-64
dovecot-1.2.11-3.fc11.x86_64
postfix-2.5.6-3.fc11.x86_64
dovecot-managesieve-1.2.11-3.fc11.x86_64
We are currently using mbox format with the users INBOX set to
/var/spool/mail/username and other mail is in /home/username/Mail. I would like
to migrate to maildir format. I tried using the convert plugin as the wiki
suggested:
mail_location = maildir:~/Maildir
protocol imap {
mail_plugins = convert
}
protocol pop3 {
mail_plugins = convert
}
plugin {
convert_mail = mbox:/home/%u/Mail:INBOX=/var/spool/mail/%u
}
When doing this I get this scrolling in the /var/log/maillog...
Sep 11 14:41:38 roark dovecot: IMAP(username): Mailbox conversion: Lock
creation timeouted
Sep 11 14:41:39 roark dovecot: IMAP(username): Fatal: Mailbox conversion
failed, exiting
Sep 11 14:56:53 roark dovecot: POP3(otheruser): Mailbox conversion:
rename(/home/otheruser/Mail, /home/otheruser/Mail-converted) failed: Directory
not empty
it does this for some users only. Mine for instance never errored and completed
perfectly from what I can tell (other than the new mail issue below). The
server load has skyrocketed though, so that is most likely part of it.
Also, while testing this, new mail was not delivered to the maildir but rather
to the old mbox in /var/spool/mail/username. The new mail never showed up until
I switched the config back over to the mbox settings. Am I missing something
here?
Thanks for any insight
--
Donny B.
