Re: [Dovecot] great disappearing email mystery
dhottin...@harrisonburg.k12.va.us wrote: Quoting Jack Stewart : dhottin...@harrisonburg.k12.va.us wrote: On Wed, 2009-02-11 at 17:27 -0500, dhottin...@harrisonburg.k12.va.us wrote: Have there been any issues with dovecot and using outlook express (imap) as an email client? I have had a couple of users come up with random missing emails. Im trying to figure out if it is user error, or something wacky in my mailserver. I cant find anything telling in maillog files or my messages. Dovecot version is 1.0.3. Its ok to reply to me, I get list messages digest. Is it missing in the mail server or just on the client? What does your server layout look like? We had a similar issue with Outlook and AppleMail where the uidlist would change just enough to wipe out their local index. People would tell us that they could see the E-mail in webmail but not in their client. We haven't had the issue in a long while, but it was painful while it lasted. The key to resolving the issue had to do with upgrades to the dovecot version - we currently just made the jump to 1.1.11 and it seems to be working well. Shes been up almost a year now without a reboot, with close to 750 accounts. ---Jack Jack, My server is a linux box running sendmail, procmail, and dovecot, I use ldap on the backend. Most of my clients use Horde for webmail, but I have some that use outlook. The emails are missing, missing. Neither on client or server. Thing is I looked on my backups (7 days worth) and supposedly missing emails werent there either. So its hard to tell how long they have been missing. Also, this server was put online 2 years ago, so all mailboxes were migrated from the oldserver to the new one and renamed oldmail. Nothing in their either. Were there any gotcha's on the upgrade? Im not one to upgrade unless there are security issues or problems and my mailserver has been extremely stable That is a mystery - nothing to do with my environment. If I understand you correctly, nothing has changed in two years and some users are now having missing messages. Assuming that this is the case, my money is on the E-mail clients.
Re: [Dovecot] great disappearing email mystery
Quoting Jack Stewart : dhottin...@harrisonburg.k12.va.us wrote: On Wed, 2009-02-11 at 17:27 -0500, dhottin...@harrisonburg.k12.va.us wrote: Have there been any issues with dovecot and using outlook express (imap) as an email client? I have had a couple of users come up with random missing emails. Im trying to figure out if it is user error, or something wacky in my mailserver. I cant find anything telling in maillog files or my messages. Dovecot version is 1.0.3. Its ok to reply to me, I get list messages digest. Is it missing in the mail server or just on the client? What does your server layout look like? We had a similar issue with Outlook and AppleMail where the uidlist would change just enough to wipe out their local index. People would tell us that they could see the E-mail in webmail but not in their client. We haven't had the issue in a long while, but it was painful while it lasted. The key to resolving the issue had to do with upgrades to the dovecot version - we currently just made the jump to 1.1.11 and it seems to be working well. Shes been up almost a year now without a reboot, with close to 750 accounts. ---Jack Jack, My server is a linux box running sendmail, procmail, and dovecot, I use ldap on the backend. Most of my clients use Horde for webmail, but I have some that use outlook. The emails are missing, missing. Neither on client or server. Thing is I looked on my backups (7 days worth) and supposedly missing emails werent there either. So its hard to tell how long they have been missing. Also, this server was put online 2 years ago, so all mailboxes were migrated from the oldserver to the new one and renamed oldmail. Nothing in their either. Were there any gotcha's on the upgrade? Im not one to upgrade unless there are security issues or problems and my mailserver has been extremely stable -- Dwayne Hottinger Network Administrator Harrisonburg City Public Schools "Everything should be made as simple as possible, but not simpler." -- Albert Einstein "The hottest places in Hell are reserved for those who, in times of moral crisis, preserved their neutrality." -- Dante
Re: [Dovecot] dbox redesign
On Wed, 2009-02-11 at 17:35 -0500, Timo Sirainen wrote: > On Wed, 2009-02-11 at 14:32 -0800, Seth Mattinen wrote: > > Timo Sirainen wrote: > > > This is about how to implement multiple msgs/file dbox format. The > > > current v1.1's one msg/file design would stay pretty much the same and > > > it would be compatible with this new design. > > > > > > > Out of curiosity, what's the advantage to going to multiple messages per > > file? Wouldn't this have the same problems as mbox? > > Multiple per file, not everything in one file. As long as the file size > is set "right", it's probably faster than one per file. We'll see :) Also there are no locking issues since reading doesn't require locking and write locks are very short lived. Corruption isn't possible because data is never copied within a file. A crash can happen at any point and Dovecot will be able to recover from it 100%. The worst that can happen is that some extra garbage is left lying around for some time wasting disk space. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] great disappearing email mystery
dhottin...@harrisonburg.k12.va.us wrote: On Wed, 2009-02-11 at 17:27 -0500, dhottin...@harrisonburg.k12.va.us wrote: Have there been any issues with dovecot and using outlook express (imap) as an email client? I have had a couple of users come up with random missing emails. Im trying to figure out if it is user error, or something wacky in my mailserver. I cant find anything telling in maillog files or my messages. Dovecot version is 1.0.3. Its ok to reply to me, I get list messages digest. Is it missing in the mail server or just on the client? What does your server layout look like? We had a similar issue with Outlook and AppleMail where the uidlist would change just enough to wipe out their local index. People would tell us that they could see the E-mail in webmail but not in their client. We haven't had the issue in a long while, but it was painful while it lasted. The key to resolving the issue had to do with upgrades to the dovecot version - we currently just made the jump to 1.1.11 and it seems to be working well. ---Jack
Re: [Dovecot] great disappearing email mystery
Thanks I'll check it out. Just what I need, more log files ;-]. take care, ddh Quoting Timo Sirainen : On Wed, 2009-02-11 at 17:27 -0500, dhottin...@harrisonburg.k12.va.us wrote: Have there been any issues with dovecot and using outlook express (imap) as an email client? I have had a couple of users come up with random missing emails. Im trying to figure out if it is user error, or something wacky in my mailserver. I cant find anything telling in maillog files or my messages. Dovecot version is 1.0.3. Its ok to reply to me, I get list messages digest. You may find it helpful to enable mail_log plugin: http://wiki.dovecot.org/Plugins/MailLog With v1.0 you can't get it to log e.g. message subject, but perhaps message-id is enough. At least you'll see if the user is deleting some messages. -- Dwayne Hottinger Network Administrator Harrisonburg City Public Schools "Everything should be made as simple as possible, but not simpler." -- Albert Einstein "The hottest places in Hell are reserved for those who, in times of moral crisis, preserved their neutrality." -- Dante
Re: [Dovecot] dbox redesign
On Wed, 2009-02-11 at 14:32 -0800, Seth Mattinen wrote: > Timo Sirainen wrote: > > This is about how to implement multiple msgs/file dbox format. The > > current v1.1's one msg/file design would stay pretty much the same and > > it would be compatible with this new design. > > > > Out of curiosity, what's the advantage to going to multiple messages per > file? Wouldn't this have the same problems as mbox? Multiple per file, not everything in one file. As long as the file size is set "right", it's probably faster than one per file. We'll see :) signature.asc Description: This is a digitally signed message part
Re: [Dovecot] great disappearing email mystery
On Wed, 2009-02-11 at 17:27 -0500, dhottin...@harrisonburg.k12.va.us wrote: > Have there been any issues with dovecot and using outlook express > (imap) as an email client? I have had a couple of users come up with > random missing emails. Im trying to figure out if it is user error, > or something wacky in my mailserver. I cant find anything telling in > maillog files or my messages. Dovecot version is 1.0.3. Its ok to > reply to me, I get list messages digest. You may find it helpful to enable mail_log plugin: http://wiki.dovecot.org/Plugins/MailLog With v1.0 you can't get it to log e.g. message subject, but perhaps message-id is enough. At least you'll see if the user is deleting some messages. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] dbox redesign
Timo Sirainen wrote: > This is about how to implement multiple msgs/file dbox format. The > current v1.1's one msg/file design would stay pretty much the same and > it would be compatible with this new design. > Out of curiosity, what's the advantage to going to multiple messages per file? Wouldn't this have the same problems as mbox? ~Seth
[Dovecot] great disappearing email mystery
Have there been any issues with dovecot and using outlook express (imap) as an email client? I have had a couple of users come up with random missing emails. Im trying to figure out if it is user error, or something wacky in my mailserver. I cant find anything telling in maillog files or my messages. Dovecot version is 1.0.3. Its ok to reply to me, I get list messages digest. thanks, ddh -- Dwayne Hottinger Network Administrator Harrisonburg City Public Schools "Everything should be made as simple as possible, but not simpler." -- Albert Einstein "The hottest places in Hell are reserved for those who, in times of moral crisis, preserved their neutrality." -- Dante
[Dovecot] dbox redesign
This is about how to implement multiple msgs/file dbox format. The current v1.1's one msg/file design would stay pretty much the same and it would be compatible with this new design. dbox directories with multiple msgs/file would be like: ~/dbox/storage/ has the actual mail data for all mailboxes ~/dbox/mailboxes/ has subdirectories containing mailboxes and their indexes Also since dbox supports already the single msg per file, those files would be stored in the mailboxes/ directory. So the idea would be that either you use multiple msgs per file using a global storage, or you use single msg per file without a global storage (or it's also possible to be in a mixed setup with some mails in storage/ and some in mailboxes/, mainly to allow migration between those configurations). The storage/ directory would have a new "map index" which is a regular dovecot index (dovecot.index and dovecot.index.log). So the mailbox index would point to mails using an intermediary "map UID". This way if mails are moved to another file only the map index needs to be updated. GUID would be a globally unique 128 bit ID for messages. So if map indexes get corrupted for any reason it's possible to rebuild it by finding the mails using GUIDs. v1.1 dbox has this "dbox.index" file which I was originally planning on using with multiple msgs/file. It had complex file range locking stuff. Now I'm thinking that it's pretty much useless. The only reason for its existence with the new design is for listing metadata for files converted from Maildir. Map index record would contain: - 32 bit map UID - 8 bit flags (MAIL_DELETED flag = message marked as expunged) - 8 bit unused wasted space - 16 bit refcount - 32 bit file sequence - 32 bit file offset --> total 128 bits/msg Mailbox index: - IMAP UID, flags, keywords, etc. - 32 bit map UID - 128 bit GUID dbox file metadata: - 128 bit GUID - size, vsize, received time, saved time, etc. - initial mailbox name (if all indexes get trashed, we can still figure out at least one mailbox where to put the mail. copies would get lost though.) (- no map UID, no imap UID) How to save a message with multiple msgs/file: 1. Find dbox file where to append to: 1.1. Look up the last message from map index 1.2. Is the file "too old"? (or doesn't exist at all) - Yes -> Create new dbox file 1.3. Is the file "too large"? - Yes -> Look at the previous file (one sequence less) and goto 1.2. 1.4. Try to lock the file. - Fail -> Look at prev file and goto 1.2. Now we have a locked/new dbox file where we can write to. Because 1.4. step only tries to lock the file, there's no waiting on locks. This also means that if e.g. two processes are writing new messages rapidly they may be appending actively to two different files. I don't think that's a problem, better than waiting for locks. 2a) We're using an existing file and we need to find the append offset. Since we found the file by finding the last msg in the file, we also know the last message's offset. I wasn't really planning on saving the message sizes in the index file, so to get the append offset I guess it needs to do an extra read on the last msg's header to find the size and skip over it. Hmm. Or would it be less disk I/O to store the size on the index so it could be found directly? I'm not really sure.. In any case, after we find the append offset, check to see if it's at EOF. If not, that means that either another process just saved a new message there or a process crashed previously and left garbage lying around. Refresh the map index to see if this file+offset exists in it. If not, truncate the file and just continue writing there. If it exists, figure out the new append offset and see again if the file limit would be reached. If the file would become too large, unlock the file and goto step 1. 2b) We're writing to a new file. No need to worry about anything in 2a) 3. Write the message and its metadata to dbox file (including generated 128 bit GUID). 4. Assign map UIDs for the written mails and write APPEND records to map index's transaction log. The record would contain the map UID, file seq, offset, refcount=1. The transaction is saved with a "weak" flag (wonder if there's a better name for this) and its offset is remembered. - If we're creating a new dbox file, it's assigned the file seq and rename()d to the final file name while the map index is locked. 5. Write APPEND record to mailbox index's transaction log with IMAP UID, map UID and GUID (and flags, keywords, etc). 6. Write "commit offset=x" record where x is the offset remembered in step 4. This marks the 4's weak transaction as being fully finished. 7. dbox file is unlocked (if we weren't creating a new file). When reading the index and we see a weak transaction without a commit record, call a resolve() function in dbox code. It finds the dbox file in the weak transaction and tries to lock it. If it can't lock it, it (probably) means that there's still a process
[Dovecot] dovecot 1.2.beta1: Fatal: io_loop_handle_add: epoll_ctl(1, 11): Bad file descriptor
I'm currently trying out 1.2.beta1 and get the following error in 'mail.err' log file as soon as I stop dovecot: Feb 11 20:28:30 server dovecot: Fatal: io_loop_handle_add: epoll_ctl(1, 11): Bad file descriptor Is that anything critical? Thanks, e-frog >: dovecot -n # 1.2.beta1: /etc/dovecot/dovecot.conf # OS: Linux 2.6.27-11-server i686 Ubuntu 8.10 log_timestamp: %Y-%m-%d %H:%M:%S protocols: imap managesieve disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable(default): /usr/lib/dovecot/imap-login login_executable(imap): /usr/lib/dovecot/imap-login login_executable(managesieve): /usr/lib/dovecot/managesieve-login mail_privileged_group: mail mail_location: maildir:~/.mail mail_executable(default): /usr/lib/dovecot/imap mail_executable(imap): /usr/lib/dovecot/imap mail_executable(managesieve): /usr/lib/dovecot/managesieve mail_plugins(default): quota imap_quota expire fts fts_squat mail_plugins(imap): quota imap_quota expire fts fts_squat mail_plugins(managesieve): mail_plugin_dir(default): /usr/lib/dovecot/modules/imap mail_plugin_dir(imap): /usr/lib/dovecot/modules/imap mail_plugin_dir(managesieve): /usr/lib/dovecot/modules/managesieve auth default: passdb: driver: pam userdb: driver: passwd socket: type: listen client: path: /var/run/dovecot/auth-client mode: 432 user: dovecot group: Debian-exim master: path: /var/run/dovecot/auth-master mode: 384 plugin: quota: maildir quota_rule: *:storage=1GB quota_rule2: Trash:storage=10%% expire: Trash 10 expire_dict: proxy::expiredict sieve: ~/.dovecot.sieve sieve_dir: ~/.sieve fts: squat fts_squat: partial=4 full=10 dict: expiredict: mysql:/etc/dovecot/dovecot-dict-sql.conf
Re: [Dovecot] Panic in dovecot 1.2.beta1
Timo Sirainen wrote: > >On Wed, 2009-02-11 at 10:29 -0800, Mark Sapiro wrote: >> I tried Dovecot 1.2.beta1 yesterday. I had been using 1.1.11. >>=20 >> I started getting "Panic: POP3(xxx): Trying to allocate 0 bytes" > >Yeah, stupid bug: http://hg.dovecot.org/dovecot-1.2/rev/22d70947597c Thanks Timo. I've applied the patch and everything is looking good so far. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan
Re: [Dovecot] Dovecot 1.1.11 imap namespaces .... access rights
On 2/11/2009, Harry Lachanas (grha...@freemail.gr) wrote: > Here is my conf Please don't snip critical info from dovecot -n output... There hsould be a version line and a line with info about your system. -- Best regards, Charles
Re: [Dovecot] Panic in dovecot 1.2.beta1
On Wed, 2009-02-11 at 10:29 -0800, Mark Sapiro wrote: > I tried Dovecot 1.2.beta1 yesterday. I had been using 1.1.11. > > I started getting "Panic: POP3(xxx): Trying to allocate 0 bytes" Yeah, stupid bug: http://hg.dovecot.org/dovecot-1.2/rev/22d70947597c signature.asc Description: This is a digitally signed message part
[Dovecot] Panic in dovecot 1.2.beta1
I tried Dovecot 1.2.beta1 yesterday. I had been using 1.1.11. I started getting "Panic: POP3(xxx): Trying to allocate 0 bytes" There are two kinds of pop3 users. In the attached log.txt file, user u1 is using a pop3 MUA. For users u2, u3, u4 and u5 fetchmail is coming through an ssh tunnel and retrieving their mail. u1 is able to interact normally with dovecot, but the fetchmail users encountered the panics in the log. dovecot -n is attached as dovecot-n.txt. At first I thought it was a locking issue as .lock files were being left behind, so I changed pop3_lock_session to no, and restarted dovecot, but this didn't help so I reverted to 2.1.11. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan Feb 10 17:31:52 sbh16 dovecot: Dovecot v1.2.beta1 starting up (core dumps disabled) Feb 10 17:32:35 sbh16 dovecot: pop3-login: Login: user=, method=APOP, rip=68.183.193.239, lip=72.52.113.16, TLS Feb 10 17:32:35 sbh16 dovecot: POP3(u1): Disconnected: Logged out top=0/0, retr=1/5832, del=0/285, size=5554299 Feb 10 17:32:36 sbh16 dovecot: pop3-login: Login: user=, method=APOP, rip=68.183.193.239, lip=72.52.113.16, TLS Feb 10 17:32:36 sbh16 dovecot: POP3(u1): Disconnected: Logged out top=0/0, retr=0/0, del=0/285, size=5554299 Feb 10 17:35:38 sbh16 dovecot: Panic: POP3(u2): Trying to allocate 0 bytes Feb 10 17:35:38 sbh16 dovecot: pop3-login: Login: user=, method=PLAIN, rip=72.52.113.36, lip=72.52.113.36, secured Feb 10 17:35:38 sbh16 dovecot: POP3(u2): Raw backtrace: pop3 [0x80d72e0] -> pop3 [0x80d733a] -> pop3 [0x80d6c3c] -> pop3 [0x80e14b8] -> pop3(i_malloc+0x1b) [0x80db9eb] -> pop3(client_create+0x56a) [0x805c6da] -> pop3(main+0x410) [0x805e2c0] -> /lib/libc.so.6(__libc_start_main+0xdc) [0x4614cdec] -> pop3 [0x805b921] Feb 10 17:35:38 sbh16 dovecot: child 21405 (pop3) killed with signal 6 Feb 10 17:35:39 sbh16 dovecot: pop3-login: Login: user=, method=PLAIN, rip=72.52.113.36, lip=72.52.113.36, secured Feb 10 17:35:39 sbh16 dovecot: Panic: POP3(u3): Trying to allocate 0 bytes Feb 10 17:35:39 sbh16 dovecot: POP3(u3): Raw backtrace: pop3 [0x80d72e0] -> pop3 [0x80d733a] -> pop3 [0x80d6c3c] -> pop3 [0x80e14b8] -> pop3(i_malloc+0x1b) [0x80db9eb] -> pop3(client_create+0x56a) [0x805c6da] -> pop3(main+0x410) [0x805e2c0] -> /lib/libc.so.6(__libc_start_main+0xdc) [0x4614cdec] -> pop3 [0x805b921] Feb 10 17:35:39 sbh16 dovecot: child 21406 (pop3) killed with signal 6 Feb 10 17:35:39 sbh16 dovecot: pop3-login: Login: user=, method=PLAIN, rip=72.52.113.36, lip=72.52.113.36, secured Feb 10 17:35:39 sbh16 dovecot: Panic: POP3(u4): Trying to allocate 0 bytes Feb 10 17:35:39 sbh16 dovecot: POP3(u4): Raw backtrace: pop3 [0x80d72e0] -> pop3 [0x80d733a] -> pop3 [0x80d6c3c] -> pop3 [0x80e14b8] -> pop3(i_malloc+0x1b) [0x80db9eb] -> pop3(client_create+0x56a) [0x805c6da] -> pop3(main+0x410) [0x805e2c0] -> /lib/libc.so.6(__libc_start_main+0xdc) [0x4614cdec] -> pop3 [0x805b921] Feb 10 17:35:39 sbh16 dovecot: child 21407 (pop3) killed with signal 6 Feb 10 17:35:39 sbh16 dovecot: pop3-login: Login: user=, method=PLAIN, rip=72.52.113.36, lip=72.52.113.36, secured Feb 10 17:35:39 sbh16 dovecot: Panic: POP3(u5): Trying to allocate 0 bytes Feb 10 17:35:39 sbh16 dovecot: POP3(u5): Raw backtrace: pop3 [0x80d72e0] -> pop3 [0x80d733a] -> pop3 [0x80d6c3c] -> pop3 [0x80e14b8] -> pop3(i_malloc+0x1b) [0x80db9eb] -> pop3(client_create+0x56a) [0x805c6da] -> pop3(main+0x410) [0x805e2c0] -> /lib/libc.so.6(__libc_start_main+0xdc) [0x4614cdec] -> pop3 [0x805b921] Feb 10 17:35:39 sbh16 dovecot: child 21414 (pop3) killed with signal 6 Feb 10 17:37:36 sbh16 dovecot: pop3-login: Login: user=, method=APOP, rip=68.183.193.239, lip=72.52.113.16, TLS # 1.2.beta1: /usr/local/etc/dovecot.conf # OS: Linux 2.6.18-8.1.14.el5 i686 CentOS release 5 (Final) ext3 protocols: pop3 pop3s ssl_cert_file: /etc/postfix/grizz-cert.pem ssl_key_file: /etc/postfix/grizz-key.pem login_dir: /usr/local/var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/pop3-login mail_access_groups: mail mail_location: /var/spool/mail/%u mbox_write_locks: fcntl dotlock mail_executable: /usr/local/libexec/dovecot/pop3 mail_plugin_dir: /usr/local/lib/dovecot/pop3 pop3_lock_session: yes auth default: mechanisms: plain apop login worker_max_count: 5 passdb: driver: passwd-file args: /usr/local/etc/dovecot.passwd passdb: driver: pam userdb: driver: passwd socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix
Re: [Dovecot] Dovecot 1.1.11 imap namespaces .... access rights
On Wed, 2009-02-11 at 20:12 +0200, Harry Lachanas wrote: > > So you're using multiple UIDs? How about just removing filesystem write > > permissions from /home/Public? > > > > > But this would disable users from dumping mails into the folders right > ??? No, for example if you had a folder called "box" it would exist in /home/Public/.box/ directory and that would need to have write permissions. Dovecot doesn't need to write anything directly under /home/Public/. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Dovecot 1.1.11 imap namespaces .... access rights
Kiitos Timo ,,, On Wed, 2009-02-11 at 19:22 +0200, Harry Lachanas wrote: Is there a way to prohibit users of creating subfolder(s) under a Public Namespace ??? .. namespace: type: public separator: / prefix: Public/ location: maildir:/home/Public:INBOX=~/Maildir:INDEX=~/Maildir/p-idx:CONTROL=~/Maildir/p-ctrl You don't need to specify INBOX here, since this namespace has no INBOX. passdb: driver: pam userdb: driver: passwd So you're using multiple UIDs? How about just removing filesystem write permissions from /home/Public? But this would disable users from dumping mails into the folders right ??? Thanks Harry.
Re: [Dovecot] Dovecot 1.1.11 imap namespaces .... access rights
Thomas Hummel wrote: On Wed, Feb 11, 2009 at 07:22:50PM +0200, Harry Lachanas wrote: Is there a way to prohibit users of creating subfolder(s) under a Public Namespace ??? Isn't that (for users (as opposed to admins) to create subfolders in a public namespacejust impossible with 1.1.x) ? You got me ! :-( puzzled ? er.! Now I am not so sure what I really meant when I asked the question! :-) :-) Not to mention yours !!! Cheers Harry
Re: [Dovecot] Dovecot 1.1.11 imap namespaces .... access rights
On Wed, 2009-02-11 at 19:22 +0200, Harry Lachanas wrote: > Is there a way to prohibit users of creating subfolder(s) under a > Public Namespace ??? .. > namespace: > type: public > separator: / > prefix: Public/ > location: > maildir:/home/Public:INBOX=~/Maildir:INDEX=~/Maildir/p-idx:CONTROL=~/Maildir/p-ctrl You don't need to specify INBOX here, since this namespace has no INBOX. > passdb: > driver: pam > userdb: > driver: passwd So you're using multiple UIDs? How about just removing filesystem write permissions from /home/Public? signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Dovecot 1.1.11 imap namespaces .... access rights
On Wed, Feb 11, 2009 at 07:22:50PM +0200, Harry Lachanas wrote: > Is there a way to prohibit users of creating subfolder(s) under a > Public Namespace ??? Isn't that (for users (as opposed to admins) to create subfolders in a public namespacejust impossible with 1.1.x) ? -- Thomas Hummel | Institut Pasteur | Pôle informatique - systèmes et réseau
[Dovecot] Dovecot 1.1.11 imap namespaces .... access rights
Hi all, Is there a way to prohibit users of creating subfolder(s) under a Public Namespace ??? Here is my conf #-- log_timestamp: %Y-%m-%d %H:%M:%S protocols: imaps ssl_ca_file: /etc/postfix/sasl/cacert.pem ssl_cert_file: /etc/postfix/sasl/cert.pem ssl_key_file: /etc/postfix/sasl/key.pem login_dir: /var/run/dovecot//login login_executable: /usr/local/dovecot-1.1.11/libexec/dovecot/imap-login valid_chroot_dirs: /var/mail mail_privileged_group: mail mail_location: maildir:~/Maildir mail_debug: yes imap_client_workarounds: outlook-idle namespace: type: private separator: / location: maildir:~/Maildir inbox: yes list: yes subscriptions: yes namespace: type: public separator: / prefix: Public/ location: maildir:/home/Public:INBOX=~/Maildir:INDEX=~/Maildir/p-idx:CONTROL=~/Maildir/p-ctrl list: yes auth default: mechanisms: plain login passdb: driver: pam userdb: driver: passwd socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix # Cheers Harry.
Re: [Dovecot] v1.2: Can't subscribe to shared user folder
On Wed, 2009-02-11 at 11:04 +0100, Sascha Wilde wrote: > a003 subscribe "user/b...@example.com/foobar" > a003 NO Unknown subscription namespace. What kind of namespace configuration do you have? This sounds like your shared namespace has subscriptions=no, but you don't have a namespace with empty prefix that has subscriptions=yes. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] v1.2.beta1 released
On Wed, 2009-02-11 at 11:00 +0100, Sascha Wilde wrote: > Timo Sirainen writes: > > http://dovecot.org/releases/1.2/beta/dovecot-1.2.beta1.tar.gz > > http://dovecot.org/releases/1.2/beta/dovecot-1.2.beta1.tar.gz.sig > > Great news! :-) > > [...] > > There isn't really much left to do for v1.2.0 except some small fixing > > to shared mailbox code. And writing documentation for it.. > > Could we by any chance get the latest small changes/enhancements: > - 'c' and 'd' in setacl Yes, this will definitely be included. I just wanted to do some tests before including it and thought it wasn't important enough to delay beta1 release because of it. > - Displaying the actual user name instead of meta name "owner" on getacl > output (see Bernhards patch in the "IMAP ACLs and global ACLs in v1.2" > thread) That patch appears to be also changing owners to user=x? I wouldn't mind a patch that showed them to clients as user=x, but I don't want them to change when something else gets changed. Also I'm not entirely sure how it should be handled when user=x ACL is changed. Should it remove the owner? Should it change the owner instead? I think the owner ACLs are usually in global ACL files, so it's probably not possible to remove or change it, only add a new user=x. signature.asc Description: This is a digitally signed message part
Re: [Dovecot] Adding new storage
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Wed, 11 Feb 2009, Romer Ventura wrote: So all the mail gets stored at /home/vmail/%Ud/%Ln/Maildir/ so if i add a new volume to the VM lets say /dev/disk3 and mount it to /srv/vmail and then change the user_attrs = sAMAccountName=mail=maildir:/home/vmail/%Ud/%Ln/Maildir/ to user_attrs = sAMAccountName=mail=maildir:/srv/vmail/%Ud/%Ln/Maildir/ would it work with no problem..? Yep, make sure, too, that /srv and /srv/vmail have at least x-permission for the UIDs you store/access the mails with. I would also need to move all the mailboxes already in the old location... Yep. Keep the permissions with the copy. For convenience, I'd keep a symlink /home/vmail pointing to /srv/vmail . Bye, - -- Steffen Kaiser -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) iQEVAwUBSZLvF3WSIuGy1ktrAQI6FQf/fc+upeJwavaT8eCRre0z8hZj6eekROrM F0F3eraY0smPuGsL6Gu+WReqcImFdlIrHvL+Kvz5kFLxBCWJoS+xiWHrSc/5KOmU w3F2+30A0RrvzQOqFbz/MYRjaQqGKkAAFvgtzDXbltEvd0W61sjJp1rHdIUbndB8 0C2vmsBZbZ5TUUStKqY3PYG3dIsn2QTJwlxoDmoXzmdndH7W51KO+ryvVIoQM79m 6/1dtWTVHUombqu10L2u0o0oG173jht1+NqHHEVBAGmgHNFXNgLWubwOB9PlmG5T 7O1bUtCdGl5vln76ILsBX+Me4x8412RXhJjvMNICVP+NZFEM52yFDw== =ZDcO -END PGP SIGNATURE-
[Dovecot] Adding new storage
Hello, I am about to add more storage to the mail server and would like to know if it is as simple as it sounds..? I have: dovecot.conf mail_location: maildir:~/Maildir/ and /etc/dovecot/dovecot-ldap.conf with: user_attrs = sAMAccountName=mail=maildir:/home/vmail/%Ud/%Ln/Maildir/ So all the mail gets stored at /home/vmail/%Ud/%Ln/Maildir/ so if i add a new volume to the VM lets say /dev/disk3 and mount it to /srv/ vmail and then change the user_attrs = sAMAccountName=mail=maildir:/ home/vmail/%Ud/%Ln/Maildir/ to user_attrs = sAMAccountName=mail=maildir:/srv/vmail/%Ud/%Ln/Maildir/ would it work with no problem..? I would also need to move all the mailboxes already in the old location... I just want to make sure before i do anything.. Thanks
[Dovecot] How many namespaces for several groups of shared mailboxes ?
Hello Timo,
let's say you want to implement several distinct groups of shared mailboxes via
one (several) public namespace(s) with dovecot-1.1.x/Maildir. For instance,
team1, team2 and team3 work on different projects (project1, project2,
project3).
Obviously, as many public namespaces (#team1, #team2, #team3) would do the
trick, but then, any user (including users who don't belong to any above team)
would 'see' useless non-selectionable folders #team*.
So my idea would be to create only one public namespace (#Public) into which I'd
store directories team1, team2, team3, into which I'd put the needed shared
mailboxes. Something like
/courriel/boites/public/team1/.shared-project1/
/team2/.shared-project2/
/team3/.shared-project3/
with something like
namespace public {
separator = /
prefix = '#Public/'
location = maildir:/courriel/boites/public
inbox = no
hidden = no
list = yes
subscriptions = yes
}
I guess if unix right and ACL are set up correctly, other people would only see
non-selectionable '#Public'.
The only problem is the subscription file : my understanding is that you have
only one subscription file per namespace.
Maybe unless you specify something like
location = maildir:/courriel/boites/public:CONTROL=
But wouldn't that induce another problem : such a CONTROL directive would put
dovecot-uidlist and dovecot-keywords in the same user dependent location.
As I want to share the \Seen flag, I have to
. put a dovecot-shared file
. not specify INDEX (or at least, not to some user dependent location)
So I would end up with
. uid lists in some user dependant location (as a side effect of having
several subscriptions files)
. but indexes shared
as uid is listed in index : wouldn't that be a problem ?
thanks
--
Thomas Hummel | Institut Pasteur
| Pôle informatique - systèmes et réseau
Re: [Dovecot] Understanding dovecot ACLs
Achim Hut writes: [...] > What i need is a scenario, where user1 can get (for example) full > access to the folders of user2, read-only access to user3 etc. > A real world example: > Secretary has full access to the mailfolders of her boss, boss has > read-only acces to the sales-department folder. Full support for shared user folders (like in your example) is a new feature in the upcoming dovecot 1.2 release. It might be possible to hack up what you need with dovecot 1.1.x but I'd say it isn't worth the trouble -- instead I'd recommend to beta-test 1.2. :-) cheers sascha -- Sascha Wilde OpenPGP key: 4BB86568 http://www.intevation.de/~wilde/ http://www.intevation.de/ Intevation GmbH, Neuer Graben 17, 49074 Osnabrück; AG Osnabrück, HR B 18998 Geschäftsführer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner pgp2MF1Ohfiyu.pgp Description: PGP signature
[Dovecot] v1.2: Can't subscribe to shared user folder
Hi *, I stumbled across a small bug (missing feature?) in the new shared name space stuff: a001 list "" "*" * LIST (\Noselect \HasChildren) "/" "user" * LIST (\Noselect \HasChildren) "/" "user/b...@example.com" * LIST (\HasChildren) "/" "INBOX" * LIST (\HasNoChildren) "/" "INBOX/bar" * LIST (\HasNoChildren) "/" "user/b...@example.com/brooklebookle" * LIST (\HasNoChildren) "/" "user/b...@example.com/foobar" a001 OK List completed. a002 lsub "" "*" a002 OK Lsub completed. a003 subscribe "user/b...@example.com/foobar" a003 NO Unknown subscription namespace. I'm quite sure this once worked in our original code (but of cause I could be mistaken). cheers sascha -- Sascha Wilde OpenPGP key: 4BB86568 http://www.intevation.de/~wilde/ http://www.intevation.de/ Intevation GmbH, Neuer Graben 17, 49074 Osnabrück; AG Osnabrück, HR B 18998 Geschäftsführer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner pgpOGtYG01wn7.pgp Description: PGP signature
Re: [Dovecot] v1.2.beta1 released
Timo Sirainen writes: > http://dovecot.org/releases/1.2/beta/dovecot-1.2.beta1.tar.gz > http://dovecot.org/releases/1.2/beta/dovecot-1.2.beta1.tar.gz.sig Great news! :-) [...] > There isn't really much left to do for v1.2.0 except some small fixing > to shared mailbox code. And writing documentation for it.. Could we by any chance get the latest small changes/enhancements: - 'c' and 'd' in setacl - Displaying the actual user name instead of meta name "owner" on getacl output (see Bernhards patch in the "IMAP ACLs and global ACLs in v1.2" thread) in 1.2? I know it's a little late but I think that would greatly extend the compatibility with existing clients -- and would enable us to use the current upstream dovecot without any changes ... ;) Oh and one more thing, I just discovered another small problem: one can't subscribe to shared user folders. I'll put the report in a new mail. cheers sascha -- Sascha Wilde OpenPGP key: 4BB86568 http://www.intevation.de/~wilde/ http://www.intevation.de/ Intevation GmbH, Neuer Graben 17, 49074 Osnabrück; AG Osnabrück, HR B 18998 Geschäftsführer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner pgpzoISWy1j7L.pgp Description: PGP signature
[Dovecot] Expire plugin does not delete expired mail
Hello. I use expire plugin with dovecot 1.1.10. See my dovecot -n: # 1.1.10: /usr/local/etc/dovecot.conf # OS: FreeBSD 6.3-RELEASE-p9 i386 ufs syslog_facility: local6 protocols: imap imaps managesieve ssl_cert_file: /etc/ssl/mail/mail.domain.net.cert ssl_key_file: /etc/ssl/mail/mail.domain.net.key disable_plaintext_auth: no 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(managesieve): /usr/local/libexec/dovecot/managesieve-login login_user: dovecot-auth login_greeting: Domain mail server login_processes_count: 2 verbose_proctitle: yes first_valid_uid: 143 last_valid_uid: 143 first_valid_gid: 143 last_valid_gid: 143 mail_access_groups: mail mail_location: maildir:/var/mail/vmail/%u/ mail_debug(default): no mail_debug(imap): no mail_debug(managesieve): yes mail_executable(default): /usr/local/libexec/dovecot/imap mail_executable(imap): /usr/local/libexec/dovecot/imap mail_executable(managesieve): /usr/local/libexec/dovecot/managesieve mail_plugins(default): quota imap_quota mail_log expire mail_plugins(imap): quota imap_quota mail_log expire mail_plugins(managesieve): mail_plugin_dir(default): /usr/local/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/lib/dovecot/imap mail_plugin_dir(managesieve): /usr/local/lib/dovecot/managesieve imap_client_workarounds(default): delay-newmail outlook-idle netscape-eoh tb-extra-mailbox-sep imap_client_workarounds(imap): delay-newmail outlook-idle netscape-eoh tb-extra-mailbox-sep imap_client_workarounds(managesieve): sieve(default): sieve(imap): sieve(managesieve): ~/dovecot.sieve auth default: mechanisms: plain login master_user_separator: * passdb: driver: passwd-file args: /usr/local/etc/dovecot.masterusers master: yes passdb: driver: sql args: /usr/local/etc/dovecot/dovecot-sql.conf userdb: driver: sql args: /usr/local/etc/dovecot/dovecot-sql.conf socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix master: path: /var/run/dovecot/auth-master mode: 432 user: dovecot group: mail plugin: quota: maildir quota_rule: *:storage=1000M quota_rule2: Trash:storage=50M quota_warning: storage=80%% /usr/home/scripts/mail_quota-warning.sh 80 quota_warning2: storage=90%% /usr/home/scripts/mail_quota-warning.sh 85 quota_warning3: storage=95%% /usr/home/scripts/mail_quota-warning.sh 90 quota_warning4: storage=95%% /usr/home/scripts/mail_quota-warning.sh 95 sieve: /var/mail/vmail/%u/dovecot.sieve expire: Trash 7 Pubs 15 Junk 1 expire_dict: proxy::expire dict: expire: mysql:/usr/local/etc/dovecot/dovecot-dict-expire.conf The expire plugin works with mysql database. The mysql table is used, and expire_stamp are written on it: us...@domain.net/Trash 1234701558 us...@domain.net/Junk 1234386055 us...@domain.net/Trash 1234874172 us...@domain.net/Junk 1234400921 us...@domain.net/Pubs 1235576243 I launch /usr/local/sbin/dovecot --exec-mail ext /usr/local/libexec/dovecot/expire-tool every 4 hours. For 3 days, no mails were deleted. However, I have date_stamp in mysql table. I dropped ALL my mails in Junk/Trash folder ; and delete all dovecot.index* in these folders. After, I restarted dovecot with expire plugin, and when a first mail arrived in one of these folder, a line is created in mysql table. But nothing is deleted in my Trash/Pubs/Junk folder. I'm waiting for 3 days. (first mail arrived in these folder on 2009/02/08). Any ideas? Have I to use cronjob/find to delete the expired mail? Regards, -- -Nicolas.
