- dovecot - dovecot.org

[Dovecot] Shared mailboxes (maildir, symlinks) and permissions
by Andreas Ntaflos 28 Jul '07

28 Jul '07

Hello list, I am trying to set up a public mailbox for users to put spam in so that sa-learn can do its job at night. Only I can't seem to fully understand how and which permissions should be set. I've read [1] and am using Dovecot 1.0.1. First some background information: I do not host or care (at the moment) about virtual users or virtual mail hosting. All users have Unix system accounts and shell access. I'd like to have a Spam folder, say /var/mail/public/.Spam that is a maildir where users can put Spam that got through the server-side filter. Spamassassin's sa-learn runs nightly and learns from the contents of the Spam folder. After reading [1] I think I should have under /var/mail/public a file called dovecot-shared that belongs to root:mail and has permissions 0660 (with user dovecot being a member of group mail) so that it looks like this: root@host:/var/mail/public# ls drwxr-sr-x 2 root mail 4096 2007-07-28 03:29 . drwxrwsr-x 3 root mail 4096 2007-07-28 02:19 .. -rw-rw---- 1 root mail 0 2007-07-28 02:46 dovecot-shared root@host:/var/mail/public# The first question arises: should Dovecot have write access to /var/mail/public itself? Now I should create the Spam folder called /var/mail/public/.Spam. Should this directory be in maildir format, i.e. should it already contain the subdirectories cur, tmp and new? What of the permissions of this directory? I am pretty sure Dovecot needs write access to it, so it should look like this: root@host:/var/mail/public# ls drwxr-sr-x 3 root mail 4096 2007-07-28 03:44 . drwxrwsr-x 3 root mail 4096 2007-07-28 02:19 .. -rw-rw---- 1 root mail 0 2007-07-28 02:46 dovecot-shared drwxrwsr-x 2 root mail 4096 2007-07-28 03:44 .Spam root@host:/var/mail/public# The .Spam directory here is completely empty. Now in a user's Maildir (/home/user1/Maildir) there are the user's private folders; a symlink to /var/mail/public/.Spam should be added: root@host:/home/user1/Maildir# ln -s /var/mail/public/.Spam . root@host:/home/user1/Maildir# ls ... drwx------ 5 user1 user1 4096 2007-07-19 16:14 .INBOX.foo drwx------ 5 user1 user1 4096 2007-07-06 23:01 .INBOX.bar ... lrwxrwxrwx 1 user1 user1 22 2007-07-28 03:51 .Spam -> /var/mail/public/.Spam ... root@host:/home/user1/Maildir# Is that all I have to do? Probably not, because I keep getting errors like the following when connecting (after subscribing of course): Jul 28 03:52:35 host dovecot: IMAP(user1): mkdir(/home/user1/Maildir/.Spam/cur) failed: Permission denied Should I have created the cur, tmp and new subdirectories manually and set their permissions like /var/mail/public/.Spam? But that still wouldn't give user1 write access. If I gave the users (or "others": chmod o+w) write permissions then Dovecot's index files would be owned by the first user that connects to the server and uses that folder. Apparently also not a solution. I also don't think I should have to make my users members of the mail group, but I could be wrong here. So I am not sure what I am missing, or if what I want to do is at all possible (without taking out the sledgehammer and setting all permissions to 0777). I also apologise for this lengthy post with many details and little interesting questions. It's getting late and I fear I've reached a dead end. I'd really appreciate it if someone knowledgeable could point me in the right direction here. Thanks in advance! Andreas [1] http://wiki.dovecot.org/SharedMailboxes -- Andreas "daff" Ntaflos Vienna, Austria GPG Fingerprint: 6234 2E8E 5C81 C6CB E5EC 7E65 397C E2A8 090C A9B4

2 1

[Dovecot] Issues upgrading to 1.1alpha1
by Luca Corti 27 Jul '07

27 Jul '07

I'm trying to upgrade from 1.0.2 to 1.1alpha1. I can build and start dovecot correctly. dovecot -n says: # 1.1.alpha1: /usr/local/etc/dovecot.conf protocols: imap pop3 ssl_cert_file: /etc/postfix/server.pem ssl_key_file: /etc/postfix/server.pem login_dir: /usr/local/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 mail_location: maildir:/mnt/shared/mail/%u:INDEX=/var/indexes/%u 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_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 auth default: passdb: driver: pam passdb: driver: passwd userdb: driver: passwd socket: type: listen client: path: /usr/local/var/run/dovecot/auth-client mode: 436 master: path: /usr/local/var/run/dovecot/auth-master mode: 384 user: root group: dovecot When I try to access my 1.4G Maildir via IMAP I can see messages in INBOX, but accessing mail in other folders returns a "resource temporarily unavailable" error in my client. In the server logs I see killed by signal 10 errors for dovecot imap processes. I'm on Linux 2.6.21 sparc64, mail is stored in NFS, indexes on local disk. ciao Luca

2 1

[Dovecot] auth_cache_...
by Frank Elsner 26 Jul '07

26 Jul '07

Hello, the dovecot-example.conf states: # Authentication cache size in kilobytes. 0 means it's disabled. # Note that bsdauth, PAM and vpopmail require cache_key to be set for caching # to be used. #auth_cache_size = 0 # Time to live in seconds for cached data. After this many seconds the cached # record is no longer used, *except* if the main database lookup returns # internal failure. We also try to handle password changes automatically: If # user's previous authentication was successful, but this one wasn't, the # cache isn't used. For now this works only with plaintext authentication. #auth_cache_ttl = 3600 auth_cache_size = 0, does it mean "cache can grow ad infinitum" or does it mean "no cache at all" ? Kind regards ______________________________________________________________ Frank Elsner / c/o Technische Universitaet Berlin | ____________/ tubIT [BD], Sekr. E-N 50 | | Einsteinufer 17 | | Phone: +49 30 314 23897 D-10587 Berlin | | eMail: Frank.Elsner(a)TU-Berlin.DE Germany __________________| |_________________________________________________________| in dubio pro exim

4 4

[Dovecot] quota: maildrop + dovecot. dovecot doesn't update maildirsize file
by Frittella Laurento 26 Jul '07

26 Jul '07

Hi all, I'm trying to implement quota support in postfix using maildrop + dovecot but I think dovecot doesn't update info stored in maildirsize file. # 1.0.2: /etc/dovecot/dovecot.conf base_dir: /var/run/dovecot/ listen: 127.0.0.1 ssl_listen: * ssl_ca_file: ... ssl_cert_file: ... ssl_key_file: ... ssl_cipher_list: ALL:!LOW:!SSLv2 login_dir: /var/run/dovecot/login login_executable: /usr/libexec/dovecot/imap-login valid_chroot_dirs: /home/vmail/domains first_valid_uid: 1001 last_valid_uid: 1001 first_valid_gid: 1001 last_valid_gid: 1001 mail_location: maildir:/home/vmail/domains/%d/%n auth default: user: dovecot-auth passdb: driver: ldap args: /etc/dovecot/dovecot-ldap.conf userdb: driver: ldap args: /etc/dovecot/dovecot-ldap.conf plugin: quota: maildir:ignore=Trash When a mail arrives maildrop delivers it and update info in the maildirsize file, but when I delete messages through dovecot (using thunderbird) the maildirsize remains the same and so users reach overquota very soon. What's wrong? Thanks in advance, Laurento

4 8

[Dovecot] migration from cyrus to dovecot
by Dirk Müller 26 Jul '07

26 Jul '07

hi there, just a short question. ;-) are the tools mentioned in the wiki for migration from cyrus (http://wiki.dovecot.org/Migration/Cyrus) still working fine with the latest dovecot release 1.0.2? i remember there have been some internal changes from 1.0.1 to 1.0.2 to keep compatible with the upcoming 1.1. thanks and best regards, dirk

2 1

[Dovecot] dspam plugin
by Oliver Kohll 26 Jul '07

26 Jul '07

Hello, I'm trying to install the dspam plugin to dovecot. So far, I've Installed dovecot 1.0.2 from RPM and set up Installed dspam 3.8.0, set up and integrated with postfix, using dspam as local delivery agent before dovecot's deliver Downloaded the dovecot 1.0.2 source in order to compile the C file http://johannes.sipsolutions.net/Projects/dovecot-dspam-integration/ beta7-code with the command cc -fPIC -shared -Wall -I../src/ -I../src/lib -I.. -I../src/lib- storage -I../src/lib-mail -I../src/lib-imap -I../src/imap/ - DHAVE_CONFIG_H -DDSPAM=\"/usr/local/bin/dspam\" dspam.c -o lib_dspam.so and copied the resulting lib_dspam.so to /usr/lib/dovecot/imap/ In dovecot.conf, set protocol imap { mail_plugins = dspam mail_plugin_dir = /usr/lib/dovecot/imap } Created a SPAM folder. However, when I move a message into or out of the SPAM folder, dspam doesn't seem to execute. Nothing appears in /usr/local/var/dspam/system.log or /var/log/maillog and "SELECT * FROM dspam_stats;" in the dspam database returns unchanged numbers: dspam=> select * from dspam_stats ; uid | spam_learned | innocent_learned | spam_misclassified | innocent_misclassified | spam_corpusfed | innocent_corpusfed | spam_classified | innocent_classified -----+--------------+------------------+-------------------- +------------------------+----------------+-------------------- +-----------------+--------------------- 505 | 18 | 1870 | 3 | 3 | 0 | 3 | 0 | 0 (1 row) One thing that may be relevant is that I have a namespace in dovecot.conf namespace private { prefix = INBOX. inbox = yes } Any ideas? Regards Oliver p.s. the page http://johannes.sipsolutions.net/Projects/dovecot-dspam- integration seems to be blank now but the Google cache http:// 216.239.59.104/search?q=cache:K_yW5wV88uwJ:johannes.sipsolutions.net/ Projects/dovecot-dspam-integration+dovecot +dspam&hl=en&ct=clnk&cd=3&client=safari is still there for now. oliver(a)gtwm.co.uk / 0845 456 1810 / 07814 828608 The Old Bank, 4 Ravenhill Rd, Swansea SA5 5AW, UK NOTE No contracts may be concluded on behalf of GT webMarque by means of e- mail communications. The contents of this e-mail are confidential to the intended recipient at the e-mail address to which it has been addressed; it may not be disclosed to or used by anyone other than this addressee, nor may it be copied in any way. If received in error please return to sender via e-mail. DISCLAIMER Please note that neither GT webMarque Ltd nor the sender accept any responsibility for viruses transmitted via e-mail. It is your responsibility to scan attachments (if any).

1 1

[Dovecot] Vacation message functionality
by Charles Marcus 25 Jul '07

25 Jul '07

Hi, Since I will soon be attempting to get this working on one of my client's systems, I posed a question on the postfix list - since they mostly dislike vacation messages - but *ardent haters* of badly configured vacation message systems - as to the quality of the dovecot vacation message function. The only response I got did seem to have a few very good suggestions for additional conditions to test for, so I'm posting the response here to see if they can be incorporated (I'm not a coder or I'd attempt it myself). The original text (prefixed by double quote characters) in the following exchange is what I copied/pasted from the wiki, and the reply (prefixed by one quote character) is the suggested change/enhancement (this reply is from a trusted source on the postfix list): >> Vacation auto-reply >> >> The vacation replies are sent to the envelope sender. Currently this >> is taken from the Return-Path: header in the message. > comment: > or from the command line if this is supported. > > also, if the envelope sender is not available, no reply should be > sent. >> List of autoreplied senders is stored in .dovecot.lda-dupes file in >> user's home directory. When you're testing the vacation feature, it's >> easy to forget that the reply is sent only once in the number of >> configured days. If you've problems getting the vacation reply, try >> deleting this file. If that didn't help, make sure the problem isn't >> related to sending mails in general by trying the "reject" Sieve >> command. > if you support extensions, you can test using a unique sender each > time: foo+12345(a)domain.example. >> The automatic replies aren't sent if any of the following is true: >> >> <snip> >> >> o begins with "owner-" (case-sensitive) > replace with: > o starts with "${token}-" (not case sensitive), where token > is one of: owner, request, bounces > > It is safer to send nothing than send a risky one. >> o contains the string "-request" anywhere within it >> (case-sensitive) > replace with: > o contains "-${token}@" (not case sensitive), where token is > one of: owner, request, bounces >> * The envelope sender and envelope recipient are the same >> * The envelope recipient is not found in the message To:, Cc: or >> Bcc: fields. > add: > * There is a "Sender:" header containing one of the tokens listed > above. > * There is a List-Id or List-Post header > * There is no header suggesting that this is possible spam > > Unlike delivery, safety here is to not send a reply if the message > may be spam. so you don't rely on recipient preferences, and you > don't fear false positives too much (the guy who receives your > auto-rep may have a better filter, and besides annoying him, would > find you stupid to miss an obvious spam ;-p) >> The envelope sender is taken from a Return-Path: header in the >> message. The envelope recipient is taken from the recipient user >> (-d parameter with virtual user setup). A bare username without a >> domain gets canonicalised by the libsieve code to >> "<username>@unspecified-domain", which means it is highly unlikely >> to pass the last two tests in the list above. > note: > the envelope recipient can also be retrieved in the Delivered-To > header if this is available ('D' flag). Comments appreciated... -- Best regards, Charles

3 4

[Dovecot] Thunderbird body search and multiple imap process
by Oliver Schulze L. 25 Jul '07

25 Jul '07

Hi, I'm having an issue with dovecot and Thunderbird and it is reproducible all the time. You do many body search from TB and you end up with multiple imap processess consuming all the CPU and with linux load 20+ Setup: - Centos 4.5 - Thunderbird 2.0.0.5 - Dovecot 1.0-7_53.rc29 and 1.0.1-1_58.el4 How to reproduce: - have an imap account in Thunderbird with 12000+ emails - user maildir in dovecot - do a: ps auwx|grep user1|grep imap|wc -l - in the main window of TB, in the sarch box select "Entire Message" - search one random word and wait 30 seconds - search another random word and wait 30 seconds - search another random word and wait 30 seconds - search another random word and wait 30 seconds - do another: ps auwx|grep user1|grep imap|wc -l - watch that the user1 have now more imap process - watch the linux load, it just rocketed from 1 to 20 - killall -9 imap - watch the linux load return to 1 I'm thinking its TB fault, anyone has seen this issue too? Thanks Oliver -- Oliver Schulze L. | http://tinymailto.com/oliver Asuncion - Paraguay | http://www.solojuegos.mobi

2 2

Re: [Dovecot] Move deleted to trash
by Timo Sirainen 25 Jul '07

25 Jul '07

On 25.7.2007, at 16.02, Donald Nash wrote: > I do have to point out that you didn't actually answer my > question. :-) You originally asserted as fact that a server-managed > trash folder is evil from IMAP's point of view. However, when > asked to explain this, you changed from an assertion of fact to a > statement of personal preference: "I hate the move-to-Trash feature." > > Don't get me wrong, I'm not trying to say that your opinion is > wrong, nor am I trying to brow-beat you into implementing something > you don't think should be implemented. I'm just curious to know > what your motivation is. Why is it evil? Why do you hate it? EXPUNGE command is specified to expunge the mails, not move them to another mailbox. This would make having the message really gone a 4 stage operation: Mark deleted, expunge, mark deleted in Trash, expunge Trash. In many clients when you mark a message deleted it also copies it to Trash. So a server side expunge-to-trash feature causes the message to get copied there twice. A Trash mailbox also has the problem that all of your messages get there. There's no way to have an easy "unexpunge" operation, because the original mailbox isn't saved anywhere. You have to manually copy the message to the wanted mailbox. Perhaps lazy-expunge is a bit similar, but it preserves the mailboxes and doesn't conflict with clients' move-to-Trash feature. Also the concept in general is about having easily restorable backups of mails and not some kind of a idea that mails should go to a Trash mailbox when they're deleted. Maybe that whole Trash concept is the reason I consider it evil. I don't like that Trash concept in desktop environments either. I wish the undelete feature was in filesystems, so that when disk is full, the oldest deleted files would automatically get overwritten with new data, but until then the files would be undeletable. >> I think having a virtual Trash mailbox that contained all messages >> marked >> as deleted in all mailboxes would be a good solution for this. > > That's not quite the same thing. All the trash folders I've seen > are for messages which have been expunged from other folders, not > just marked for deletion. It's to give you one last chance to > retrieve a message that you realize shouldn't have been deleted. I think I'd prefer the lazy-expunge way for that more than having everything go to Trash. The virtual Trash would make client-side "delete=mark deleted + copy to Trash" feature unnecessary. >> It's not a requirement to subscribe to post. The messages to go to >> moderation queue and I approve them from there. > > Quoting from your web site: > > * You can post to the list without subscribing. The mail then > waits > in a moderator queue. However a lot of spam arrives there, > so it's > possible that your message gets accidentally discarded as spam. > > I didn't want to take a chance on my message getting lost in the > spam. If you want, I will join the mailing list and we can replay > this discussion there so everyone else can benefit from it. Well, I Cc'd the list now. > I hadn't anticipated that it would evolve into this much of a > discussion (I was hoping for a simple "It's evil because of X, Y, > and Z" sort of answer), or I would have done that in the first place. Evilness is subjective. :)

2 1

[Dovecot] Errors logging in
by Cassidy B. Larson 25 Jul '07

25 Jul '07

Out of the blue my proxy installations started showing this: dovecot: login: tried to change state 2 -> 2 (if you can't login at all, see src/lib/fdpass.c) Nobody can login. Running 1.0.0 on the proxy and 1.0.2 on my storage boxes. Anybody have any insights? -c

1 1