Re: [Dovecot] backup dovecot
On Fri, 23 Nov 2007, Nikolay Shopik wrote: Links how to use rsync will be appreciated. Others have posted how to do a single backup using rsync. I will mention here a program I use called dirvish which lets you easily do incremental backups at only a fractionally-increased storage cost over a single backup. It's quite nice and gives me warm fuzzy feelings. I believe http://dirvish.org/ will point you the right way. -- Asheesh. -- He's just a politician trying to save both his faces...
[Dovecot] imap process killed with signal 11
Hi! Using the latest cvs from HEAD, I'm experiencing problems after sending a message and the client is trying upload the message to the appropriate (Sent/Queue) folder. I get only one error in dovecot.log: dovecot: Nov 25 14:21:31 Error: child 19554 (imap) killed with signal 11 So my client disconnects, and asks for the password again, and in dovecot.info I get nothing, but the logs of the new connection attempt. What else info should I provide? System is OpenBSD 4.2 $ dovecot -n # 1.1.beta8: /etc/dovecot.conf base_dir: /var/run/dovecot/ log_path: /var/log/mail/dovecot.log info_log_path: /var/log/mail/dovecot.info protocols: pop3 pop3s imap listen: 212.92.15.17 ssl_cert_file: /etc/ssl/dovecot_cert.pem ssl_key_file: /etc/ssl/private/dovecot_key.pem login_dir: /var/run/dovecot/login login_executable(default): /usr/local/libexec/dovecot/imap-login login_executable(imap): /usr/local/libexec/dovecot/imap-login login_executable(pop3): /usr/local/libexec/dovecot/pop3-login login_user: _dovecot login_processes_count: 1 login_max_processes_count: 10 max_mail_processes: 100 first_valid_uid: 8000 first_valid_gid: 8000 mail_location: maildir:~/Maildir/ mail_debug: yes dotlock_use_excl: yes mail_executable(default): /usr/local/libexec/dovecot/imap mail_executable(imap): /usr/local/libexec/dovecot/imap mail_executable(pop3): /usr/local/libexec/dovecot/pop3 mail_plugins: quota mail_plugin_dir(default): /usr/local/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/lib/dovecot/pop3 imap_client_workarounds(default): tb-extra-mailbox-sep imap_client_workarounds(imap): 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 digest-md5 ntlm user: _dv_auth master_user_separator: * verbose: yes passdb: driver: passwd-file args: /etc/dovecot.passdb_master pass: yes master: yes passdb: driver: passwd-file args: /etc/dovecot.passdb userdb: driver: passwd-file args: /etc/dovecot.userdb socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: _postfix group: _postfix master: path: /var/run/dovecot/auth-master mode: 432 user: vmail group: vmail plugin: quota: maildir quota_rule: *:storage=100M quota_rule2: Trash:storage=50M -- Lévai Dániel Key ID: 0x4AC0A4B1 (wwwkeys.eu.pgp.net) Fingerprint: D037 03B9 C12D D338 4412 2D83 1373 917A 4AC0 A4B1
Re: [Dovecot] recalculation of maildir Quota
On Fri, Nov 23, 2007 at 06:47:41PM +0100, Ingo Rogalsky wrote: > But one more question: Would it be possible to disable the recalculation > and do this with a nightly cronjob, which scans all mail accounts? Depending on your needs you could always use your (Linux?) OS tools and do a du -s * or if supported du -sm * to get the size im MB. Adding a | sort -nr gives a nice list with top users of disk space first. Doing it on the machine that serves the NFS should speed it up significantly. \Maex
Re: [Dovecot] dovecot with ldap and allow_nets
Charles Marcus wrote: > On 11/23/2007, Marc Cuypers ([EMAIL PROTECTED]) wrote: >> # dovecot --version >> 1.0.rc15 > > Extremely old... > > Upgrade... > Does your reply mean that allow_nets didn't work with version 1.0. -- Marc
Re: [Dovecot] backup dovecot
> Benjamin R Haskell <[EMAIL PROTECTED]> writes: [...] >> An example of syncing 2 directories over ssh, keeping all permissions >> intact. This command run on the source maildir server. >> rsync -av -e"ssh" /source_maildirs/ [EMAIL PROTECTED]:/destination/maildirs/ > Couple tips (not criticisms): Nowadays, ssh is the default (unless > compiled otherwise). So, the '-e"ssh"' is likely unneccessary. As is the > 'username@' part, if the username is the same. ... Or if it's different, but one took care to provide an entry in ~/.ssh/config, like: $ cat ~/.ssh/config ... Host alias remote.host HostName remote.host User remote.user ... $ > And something to watch out for as a new rsync user: > The trailing slash is important on the source path. From the rsync 'man' > page (read it!): A trailing slash on the source changes this behavior to > avoid creating an additional directory level at the destination. To put it short, SRC-DIR refers to a directory, and SRC-DIR/ -- to its contents. > (But, it doesn't do anything on the destination path.) > That'd shorten the command to: > rsync -av /source_maildirs/ hostname:/destination/maildirs
Re: [Dovecot] dovecot with ldap and allow_nets
On 11/25/2007, Marc Cuypers ([EMAIL PROTECTED]) wrote: Charles Marcus wrote: On 11/23/2007, Marc Cuypers ([EMAIL PROTECTED]) wrote: # dovecot --version 1.0.rc15 Extremely old... Upgrade... Does your reply mean that allow_nets didn't work with version 1.0. Not necessarily - it means its so old that I (and most likely more than a few others) don't want to hassle with checking to see what possible problems/bugs it had that are fixed in current releases. Unlike myself, Timo could I'm sure answer a lot of question like this off the top of his head, but I'm also sure even he gets irritated by people who come here asking for help when they are running an ancient version. In other words, as with all free software - the more current version, you are running, the easier it will be to get support... -- Best regards, Charles
Re: [Dovecot] backup dovecot
On Mon, 26 Nov 2007, Ivan Shmakov wrote: Benjamin R Haskell <[EMAIL PROTECTED]> writes: [...] > And something to watch out for as a new rsync user: > The trailing slash is important on the source path. From the rsync 'man' > page (read it!): A trailing slash on the source changes this behavior to > avoid creating an additional directory level at the destination. To put it short, SRC-DIR refers to a directory, and SRC-DIR/ -- to its contents. That always seemed like an odd way to put it. Saying "its contents" implies (or at least leads me to suspect) that SRC-DIR/ would be synonymous with SRC-DIR/* But, it's not. The former updates the permissions/attributes on DEST-DIR, but the latter doesn't. Illustration by example, (now that we're way off topic) :-) $ mkdir foo $ cd foo $ umask 077 $ mkdir -p sa/sb $ echo foo > sa/sb/sc $ chmod 770 sa $ mkdir with-slash without-slash with-star $ rsync -av sa without-slash $ rsync -av sa/ with-slash $ rsync -av sa/* with-star $ tree -p -L 2 . |-- [drwxrwx---] sa | `-- [drwx--] sb |-- [drwxrwx---] with-slash | `-- [drwx--] sb |-- [drwx--] with-star | `-- [drwx--] sb `-- [drwx--] without-slash `-- [drwxrwx---] sa The important bits: No 'sa' directory in with-slash or with-star. Permissions on with-slash are the same as 'sa', but with-star doesn't match. Best, Ben
[Dovecot] Configuration Error
Hello, I am a newbie when it comes to Dovecot, and in following this ( http://workaround.org/articles/ispmail-etch/ ) document in setting these things up, I have run into an error that I am not quite certain what to do... I am running Ubuntu Gutsy Gibbon, and using 1.0.5 for Dovecot. The message I am getting when I try to 'restart' Dovecot (using '/etc/init.d/dovecot restart') is: Error: Error in configuration file /etc/dovecot/dovecot.conf line 505: Protocol section not allowed here (section changed at line 505) Fatal: Invalid configuration in /etc/dovecot/dovecot.conf ...fail! Does this mean that I need to move this section of the configuration file to a different spot in the file? All I did was uncomment these things, and make the changes described in the link above, I would think that because this is just an edited version of the configuration file, that something like this shouldn't happen. Any help would be appreciated. Thank you, Mike -- Peace may sound simple—one beautiful word— but it requires everything we have, every quality, every strength, every dream, every high ideal. —Yehudi Menuhin (1916–1999), musician
Re: [Dovecot] Configuration Error
Sorry for this, but I found a few braces that I forgot to uncomment. Guess I should have checked my work a little more closely. Thanks, Mike On Nov 25, 2007 4:09 PM, Mike McGonagle <[EMAIL PROTECTED]> wrote: > Hello, > I am a newbie when it comes to Dovecot, and in following this ( > http://workaround.org/articles/ispmail-etch/ > ) document in setting these things up, I have run into an error that I am > not quite certain what to do... > > I am running Ubuntu Gutsy Gibbon, and using 1.0.5 for Dovecot. The message > I am getting when I try to 'restart' Dovecot (using '/etc/init.d/dovecot > restart') is: > > Error: Error in configuration file /etc/dovecot/dovecot.conf line 505: > Protocol section not allowed here (section changed at line 505) > Fatal: Invalid configuration in /etc/dovecot/dovecot.conf >...fail! > > Does this mean that I need to move this section of the configuration file > to a different spot in the file? All I did was uncomment these things, and > make the changes described in the link above, I would think that because > this is just an edited version of the configuration file, that something > like this shouldn't happen. > > Any help would be appreciated. > > Thank you, > > Mike > > > -- > Peace may sound simple—one beautiful word— but it requires everything we > have, every quality, every strength, every dream, every high ideal. > —Yehudi Menuhin (1916–1999), musician > -- Peace may sound simple—one beautiful word— but it requires everything we have, every quality, every strength, every dream, every high ideal. —Yehudi Menuhin (1916–1999), musician
Re: [Dovecot] Wanting to seperate MTA and Imap
Brent Clark wrote: I read the documentation on NFS, but from other sites i have read. Most say this is NOT the best solution. I use NFS, as do quite a number of people - it may not be the best solution, but there are few others for realising shared storage at all sensibly. Most of the cluster filesystems I've tested have not performed well, and I'm guessing you don't have access to a quality SAN to make this sensible. If you read the doco in the Dovecot wiki regarding NFS you should be moving in the right direction. My only suggestion is that creating local caches/indexes (ie - not residing on NFS) on your IMAP servers is a good idea - hint: check out the Dovecot doco on 'mail_location'.
Re: [Dovecot] Users w/o acl access appear to be subscribed to public folders (1.1b8)
On Tue, Nov 20, 2007 at 10:20:49PM -0500, Adam McDougall wrote: I noticed this today, I had a user outside of our department test out dovecot. They were using squirrelmail and I noticed that dovecot thinks this user is subscribed to ALL public folders even though a dovecot ACL prevents all access. I'm pretty sure access is still denied. I was able to reproduce this with a guest account I added: l lsub "" "#shared/decs/%" * LSUB (\Noselect) "/" "#shared/decs/linuxadmin" * LSUB (\Noselect) "/" "#shared/decs/jbossadmin" * LSUB () "/" "#shared/decs/support" * LSUB () "/" "#shared/decs/receipts" * LSUB (\Noselect) "/" "#shared/decs/pcadmin" * LSUB () "/" "#shared/decs/network" * LSUB (\Noselect) "/" "#shared/decs/printmaster" * LSUB () "/" "#shared/decs/postmaster" * LSUB (\Noselect) "/" "#shared/decs/unixadmin" * LSUB () "/" "#shared/decs/security" * LSUB (\Noselect) "/" "#shared/decs/webmaster" l OK Lsub completed. This only seems to happen when the acl plugin is enabled. Without the acl plugin, these are not listed as subscriptions. After deleting /egr/mail/shared/decs/dovecot-acl-list and re-enabling the acl plugin, I get this: l lsub "" "#shared/decs/%" * LSUB () "/" "#shared/decs/unixadmin" * LSUB () "/" "#shared/decs/support" * LSUB () "/" "#shared/decs/security" * LSUB () "/" "#shared/decs/printmaster" * LSUB () "/" "#shared/decs/postmaster" * LSUB () "/" "#shared/decs/pcadmin" * LSUB () "/" "#shared/decs/network" * LSUB () "/" "#shared/decs/linuxadmin" * LSUB () "/" "#shared/decs/webmaster" * LSUB () "/" "#shared/decs/jbossadmin" l OK Lsub completed. Is it related, or is it different just because a new dovecot-acl-list got created by another user already (but is mode 700?) I found a workaround, if I add "authenticated l" to the top level acl in each namespace (currently only have one enabled) then users aren't force-subscribed to every public folder. It does however grant them the ability to subscribe to my empty top level fake folder which they have no permissions for anyway. This doesn't seem to reduce the level of access by any valid users.
Re: [Dovecot] migrating from mbox to maildir
On Saturday, November 24 at 10:13 PM, quoth mouss: If for some reason you are completely stuck with 0.99.x, then yes, changing to Maildir format is pretty easy, and there are plenty of conversion scripts out there in the world. Just ask Google. Keep in mind if the real problem is some bug in Centos that prevents Dovecot from using locks, then the Maildir conversion may not help much, because Maildir (in Dovecot) uses locks as well. why lock? To quote the Dovecot wiki (http://wiki.dovecot.org/MailboxFormat/Maildir): Although maildir was designed to be lockless, Dovecot locks the maildir while doing modifications to it or while looking for new messages in it. This is required because otherwise Dovecot might temporarily see mails incorrectly deleted, which would cause trouble. Basically the problem is that if one process modifies the maildir (eg. a rename() to change a message's flag), another process in the middle of listing files at the same time could skip a file. The skipping happens because readdir() system call doesn't guarantee that all the files are returned if the directory is modified between the calls to it. This problem exists with all the commonly used filesystems. ~Kyle -- The most important thing a father can do for his children is to love their mother. -- Fr. Theodpre Hesburgh pgpG2BgD58zmL.pgp Description: PGP signature
