- dovecot - dovecot.org

[Dovecot] INTERNALDATE call, timezone randomly changes
by Guy 30 Nov '08

30 Nov '08

Hi guys, I've run into an odd little problem. We use SquirrelMail as the basis for our webmail. Recently I've had a user complaining that the "Received" time on mail in the Sent folder has changed between logins. The change is always been by +1 hours or -5 hours. While checking, our developer had a time changed by +2 hours. On refresh it changed back. He poked through the code and it looks like SquirrelMail gets the received date via an IMAP command: A003 FETCH 1:10 (INTERNALDATE FLAGS BODY.PEEK[HEADER.FIELDS (To Content-Type Subject Date)]) I'm running dovecot 1.1.6, and I'm wondering how that function gets the date and time? If I can isolate the source of the timezone I can try and correct it. The server time shown by "date" is correct and /etc/localtime is /usr/share/zoneinfo/Europe/London (which is correct - I've also se the timezone in /etc/conf.d/clock is set to "Europe/London" now), so I'm wondering where else the information could be coming from? Thanks for any information you can give me to help isolate the problem. Guy -- Don't just do something...sit there!

2 1

[Dovecot] v1.2.alpha4 released
by Timo Sirainen 30 Nov '08

30 Nov '08

http://dovecot.org/releases/1.2/alpha/dovecot-1.2.alpha4.tar.gz http://dovecot.org/releases/1.2/alpha/dovecot-1.2.alpha4.tar.gz.sig Note that there are significant changes in this release from alpha3 and I haven't tested everything extensively. Be careful. The next release will hopefully be v1.2.beta1 with a feature freeze. Most importantly shared mailboxes and IMAP ACLs are finally supported. This is mainly thanks to the Kolab people (looks like I forgot your names from NEWS file, the next release will have them). I'll have to write a wiki page about ACLs, but the main thing you need to know is that if you want shared mailboxes to be LISTable by other users, you'll need to specify acl_dict. If you don't expect many shared mailboxes, a file backend is the easiest, but you could also use SQL or Berkeley DB. With a file backend you could also create per-domain files, which will improve performance if you don't need cross-domain shared mailboxes. You could do this with e.g.: acl_file = /home/virtual/%d/shared-mailboxes Also full text searching works now better with virtual mailboxes. Previously the fts would have duplicated the indexes for virtual mailboxes. Now with Solr backend it searches the original mailboxes directly. Although this is still missing some optimizations and also it doesn't check first if mails are missing from the original mailboxes, so it may not find everything. Also this still doesn't work with Squat backend.. Anyway, a bit more code and Dovecot will have fast full text searching from all mailboxes (virtual * mailbox). I implemented also draft-gulbrandsen-imap-response-codes-04, which adds some [codes] for all IMAP command failures, which should make it possible for clients to figure out more easily what caused the failure. Hopefully the draft won't change much anymore. :)

2 2

[Dovecot] Dovecot as proxy for M$ Exchange mailboxes
by Axel Schmalowsky 30 Nov '08

30 Nov '08

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi list, is there a way to use dovecot as proxy for m$ exchange mailboxes? Currently, our clients not only can login to their mailboxes with their e-mail address but also with their accountid. Both the clients e-mail address and accountid are stored in ldap. Now I need a way to let dovecot rewriting the client's accountid to the respective e-mail address. Is this possible with the proxy-feature of dovecot? Any hints would be appreciated. - -- Freundliche Grüße / Kind regards Axel Schmalowsky Platform Engineer ___________________________________ domainfactory GmbH Oskar-Messter-Str. 33 85737 Ismaning Germany Telefon: +49 (0)89 / 55266-356 Telefax: +49 (0)89 / 55266-222 E-Mail: aschmalowsky(a)df.eu Internet: www.df.eu Registergericht: Amtsgericht München HRB 150294, Geschäftsführer Tobias Marburg, Jochen Tuchbreiter -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFJL+JKsuqpduCyZM0RAoFUAJ9mPbv5eI5xP54YhwlmOs40F1RxDQCgir5l jCdaNeXKO8FnOCxaKSI7S4E= =m5WN -----END PGP SIGNATURE-----

3 2

Re: [Dovecot] Dovecot - Vpopmail subdirectories
by Yacoubi Mohamed 28 Nov '08

28 Nov '08

Hello, Thank you for this link, but this is not what I want. Dovecot is only used for imap. Currently, authentication works fine, but new fields are created in a subdirectory. Example: /var/vpopmail/domains/0/domain.com Once authenticated, I just want to be in chroot /var/vpopmail/domains/0/domain.com/user and not in /var/vpopmail/domains/domain.com/user I explained that vpopmail which manages the creation of areas and I can not influence the subdirectory. Sincerely, -- Mohamed YACOUBI

2 2

[Dovecot] ManageSieve and invalid scriptname
by Miguel Filho 28 Nov '08

28 Nov '08

Hello there, I have been using pysieved and avelsieve and it has been working great. I decided to do test with the ManageSieve patch and got this problem: Nov 27 17:21:29 cambui dovecot: MANAGESIEVE(miguel): sieve-storage: using active sieve script path: ~/.dovecot.sieve Nov 27 17:21:29 cambui dovecot: MANAGESIEVE(miguel): sieve-storage: using sieve script storage directory: ~/.sieve Nov 27 17:21:29 cambui dovecot: MANAGESIEVE(miguel): sieve-storage: relative path to sieve storage in active link: .sieve/ Nov 27 17:21:29 cambui dovecot: MANAGESIEVE(miguel): sieve-storage: Active sieve script symlink /home/admsis/miguel/.dovecot.sieve is broken: invalid scriptname (points to .sieve/phpscript). Well as you can see, a file without the .sieve is not welcome :-( I checked the RFC and there is no requirement for a .sieve file extension when considering scriptnames. http://tools.ietf.org/html/draft-martin-managesieve-12#section-1.6 Is this a misplaced restriction or it really should be enforced for any reason? I hope that this can be tolerable, or I will have to rename a lot of scripts and remove all hardcoded "phpscript" strings from avelsieve :-( Regards and thanks for the great work. Miguel

3 6

[Dovecot] Sieve and global scripts
by Allan Cassaro 28 Nov '08

28 Nov '08

Hi Stephan Bosch, there's any way to make the dovecot deliver agent (with sieve) load a "global sieve script" before load the user sieve file? I want to create some rules for every one, like: "if header contais: IS SPAM, move to SPAM BOX"... I made this today with a couple of "sed + awk" and a wraper for managesieve-login... but, this is definily not the best way to do this... This is possible to do? (Even with change in the code) Regards. -- "Não deixe a faculdade atrapalhar seus estudos." http://allan.cassaro.googlepages.com

4 3

Re: [Dovecot] UIDL question
by Timo Sirainen 28 Nov '08

28 Nov '08

On Nov 28, 2008, at 6:43 PM, Wouter van der Schagt wrote: >> This mixes v3 syntax with v1 syntax, won't work. > > You're right, after changing it to the v3 syntax i'm getting exactly > the same output in both servers after issuing the UIDL command in a > telnet session. So far so good. > > However, a 2nd copy of the files is still being downloaded. Is this > because the IP has changed? My steps are. > > - Download emails from IP.IP.IP.1 > - Migrate emails > - Confirm manually that UIDL output is the same > - If so, download emails from IP.IP.IP.2 > > And in the last step, im still getting a 2nd copy of all emails. > Where is the fault in my reasoning? Do i need to give dovecot a > message number that was last downloaded? If the UIDLs are exactly the same, I've no idea why the client would download a duplicate. I haven't heard before that a changed IP would be an issue. Of course that would still be a client-specific issue. Sounds a bit unlikely though. Ccing back to list in case someone else has an idea..

2 1

[Dovecot] Namespaces and shared folders
by bbell2000 28 Nov '08

28 Nov '08

I had a working dovecot install before I tried to implement shared folders using namespaces. I added the following to /etc/dovecot/dovecot.conf: namespace private { separator = prefix = inbox = yes } namespace public { separator = / prefix = location = maildir:/home/public/shared/Maildir } </pre> I created my shared folder using the maildirmake command that came with qmail: maildirmake -S /home/public/shared/Maildir maildirmake -s write -f online /home/public/shared/Maildir chown -R dovecot:shared /home/public/shared find /home/public/shared -type d -exec chmod 0777 {} \; find /home/public/shared -type f -exec chmod 0666 {} \; At this point, the online folder shows up as a subscribable folder in Thunderbird. I can subscribe to online and I can still access my Inbox. But I can't get to any of the folders in my Inbox (Trash, Drafts, etc.). I can access these folders if I comment out the namespaces and revert to the default behavior. There are no clues in mail.err, mail.info or mail.warn -- the only messages are the ones written when my client establishes a successful IMAP connection. What did I do wrong? -- View this message in context: http://www.nabble.com/Namespaces-and-shared-folders-tp20727713p20727713.html Sent from the Dovecot mailing list archive at Nabble.com.

3 4

[Dovecot] UIDL question
by Wouter van der Schagt 28 Nov '08

28 Nov '08

Hi all, I'm migrating a Postfix + Dovecot 1.0 server with mboxes to Qmail + Dovecot 1.4 with Maildirs and encounter the following the problem. Using perfect-maildir.pl from: http://perfectmaildir.home-dn.net/ i can relatively succesfully convert the mbox to a Maildir. The problem, however is that clients with "leave mail on server" set to on retrieve all email a 2nd time. I understand this must be because the email client "sees" a different UIDL and downloads the message again. Looking at the 1.0 configuration, i do not see a "pop3_uidl_format" setting. So was wondering how the UIDL is generated. Is anybody aware of a conversion script that properly maintains the UIDL? Or am I misisng something else here? Sincerely, - Wouter van der Schagt

3 8

[Dovecot] Dovecot - Vpopmail subdirectories
by Yacoubi Mohamed 28 Nov '08

28 Nov '08

Hello, I have several thousand domains on a server. I'm doing now migration to Dovecot to replace courier-authlib. Some email accounts are in subdirectories that are automatically created by vpopmail. Example: / var/vpopmail/domains/0/domain.com How do I configure Dovecot? ###################################################### # 1.1.6: /etc/dovecot/dovecot.conf # OS: Linux 2.6.26.5-sdf103-nfsv4 i686 Gentoo Base System release 1.12.9 ext3 base_dir: /var/run/dovecot/ protocols: imap listen: *:143 ssl_disable: yes disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable: /usr/libexec/dovecot/imap-login login_greeting: Imap ready. first_valid_uid: 89 mail_location: maildir:/var/vpopmail/domains/%d/%n/.maildir auth default: user: vpopmail passdb: driver: vpopmail userdb: driver: static args: uid=89 gid=89 mail=Maildir:/var/vpopmail/domains/%/%d/% n/.maildir ###################################################### Best regards, -- Mohamed YACOUBI

1 0

Re: [Dovecot] anti spam measures
by Johannes Berg 28 Nov '08

28 Nov '08

[please don't drop the list, somebody else might care] On Wed, 2008-11-26 at 07:02 -0700, Trever L. Adams wrote: > Johannes Berg wrote: > > Interesting. Somebody else was reporting the same errors, but I'm not > > seeing them. But I'm still using 1.1.2. I'll review the changes, I > > guess, but if I don't find anything quickly I won't get around to poking > > at it before Christmas. > > > > johannes > > > > I found out what the problem is. In your git tree you have the signature > option set for both dspam and crm114 with both uncommented. Oh, so it's looking for the crm signature? Well, I guess the man-page should have them both commented out, maybe. > Can you provide me with more information on your crm setup? Well, it's a bit complicated, but I'll leave out the SMTP part. When a mail is delivered locally, it's passed to crm114: basically: xfilter "/usr/local/bin/mailreaver" if ( /^X-CRM114-Status: UNSURE/:h ) { to $HOME/Maildir/.UNSURE/ } if ( /^X-CRM114-Status: SPAM/:h ) { to $HOME/Maildir/.SPAM/ } and then in dovecot, I have: plugin { crm114_spam = SPAM crm114_unsure = UNSURE crm114_signature = X-CRM114-CacheID crm114_crm_binary = /usr/local/bin/mailreaver } (I compile my plugin with the option to change the pluginname) johannes

3 6

[Dovecot] Does either version 1.2 or 1.4 support UIDPLUS?
by Robert Nicholson 28 Nov '08

28 Nov '08

My ISP currently runs version 1.2 and I'm looking to make use of UIDPLUS because I want to append and then move the message I've just appended to another folder so then I need the UID in order to address the new message. My ISP says they have plans to upgrade to version 1.4 soon. Do either of these versions support UIDPLUS? ie. give me the new UID as the response to an append?

3 8

[Dovecot] expire tool question
by Jakob Curdes 27 Nov '08

27 Nov '08

Hi, I try to get expire working, with the BDB backend and mbox mailboxes. If I try to invoke the expire-tool like /usr/local/sbin/dovecot --exec-mail ext /usr/local/libexec/dovecot/expire-tool --test I get [root@m ~]# /usr/local/sbin/dovecot --exec-mail ext /usr/local/libexec/dovecot/expire-tool --test Error: read(/var/run/dovecot/dict-server) failed: Remote disconnected Hmm. I searched for hints but could not find a related discussion or problem. Here are the relavant config parts: dict { expire = db:/var/lib/dovecot/expire.db } plugin { # expire plugin expire_dict = proxy::expire expire = backup 7 spam 30 # If you have a non-default path to auth-master, set also: auth_socket_path = /var/run/dovecot/auth-master } Any ideas? Has anybody got this working ? The file /var/lib/dovecot/expire.db doas not exit even though I restarted DC quite a while ago. Regards, Jakob

3 5

Re: [Dovecot] antispam plugin claims "antispam signature not found"
by Eugene 27 Nov '08

27 Nov '08

Jakob Curdes wrote > Some weeks ago I asked a question on the antispam plugin; obviously > nobody could help me. I just worked on it again but made no progress. > Is actually anybody out there running the antispam plugin with dspam?? I > am willing to write a Wiki page for configuring this as soon as I get it > to work. > ..... > - as soon as I move a message into the spam folder it gives an error > message saying "antispam signature not found" Just had this error myself. In my case, the cause was a large spam message (above the configured MaxMessageSize parameter for DSPAM) that was skipped during tests and thus no signature was added. Might this be true in your case? As a general suggestion for Johannes: maybe it is better to ignore this error silently, just move the message and don't call DSPAM? > I checked that the given location for the dspam executable is correct, > that the user executing it (dovecot?) is actually able to execute dspam > and that dspam trusts this user. I triple-checked that the signature is > configured correctly. I have lines like > X-DSPAM-Signature: 1,49084a24139132188715614 Another guess: if that comma is not a misprint, something is wrong in your setup. Regards Eugene

5 5

[Dovecot] Can I import RFC822 messages into Dovecot from file system
by bbell2000 27 Nov '08

27 Nov '08

I'm returning to qmail and dovecot after having suffered a complete failure with a different mail system and I'm now trying to figure out the easiest way to recover our messages from the failed system. The messages are stored as RFC822 in individual files and I can easily identify which message belongs to whom. I have qmail and dovecot configured to use Maildir format. I know I can probably write a script that resends the messages... but in addition to adding another layer of transport headers I really don't want, it's going to be way slow unless I disable my current content filters. I'm new to dovecot and what's got me hung up are the indexes that dovecot maintains in each user's directory. Otherwise, I'd probably try copying the messages into Maildir/cur just to see if it worked. I could sure use some ideas about an efficient, reliable means of getting our old messages back. Thanks. -- View this message in context: http://www.nabble.com/Can-I-import-RFC822-messages-into-Dovecot-from-file-s… Sent from the Dovecot mailing list archive at Nabble.com.

2 1

[Dovecot] Antispam plugin + script sieve
by Allan Cassaro 27 Nov '08

27 Nov '08

Hi guys, I will start a little script that receive via antispam plugin an email, extract the "from" and "return-path" and create alter the sieve script of the user that send the e-mail. Well, I don't speak english very well (I speak like Borat!!!), but with some examples is better to understand: 1) Some user move an "undesirable" mail to "Automatic Block" folder 2) The antispam plugin call my script 3) The script parse the e-mail and extract the from and return-path mail 4) A rule is added to ~/.dovecot.sieve to dicard messages that came from that e-mail 5) If the user remove the mail from "Automatic Block" folder, the script remove this rule So, my question is: anyone is working on something similar with this? (I don't want to reinvent the wheel) Regards. -- "Não deixe a faculdade atrapalhar seus estudos." http://allan.cassaro.googlepages.com

1 0

[Dovecot] deliver segv on sieve redirect
by Andy Howell 27 Nov '08

27 Nov '08

Hello, I've been trying out the bleeding edge, 1.2.alpha4. I'm having a problem with deliver and dovecot-1.2-sieve-0.1.1. I get a segv on this sieve script: require ["fileinto", "reject", "vacation", "envelope", "regex"]; if header :contains "subject" ["urgent"] { redirect "someone(a)somewhere.net"; fileinto "test"; } Seems its happening on the "redirect". If I put the fileinto before the redirect, the fileinto works. I tried putting extra debug statements in plugins/lda-sieve/lda-sieve-plugin.c right after the sieve_execute in lda_sieve_run, but it never prints anything. I'm guessing thats the right place. Its quite possible there is something amiss in my setup. My logs show: Nov 26 02:51:12 marvin dovecot: deliver(andy(a)x.y.org): sieve: using sieve path: /var/mail/vhosts/x.y.org/andy/.dovecot.sieve Nov 26 02:51:12 marvin dovecot: deliver(andy(a)x.y.org): sieve: opening script /var/mail/vhosts/x.y.org/andy/.dovecot.sieve Nov 26 02:51:12 marvin dovecot: deliver(andy(a)x.y.org): sieve: executing compiled script /var/mail/vhosts/x.y.org/andy/.dovecot.sieve Nov 26 02:51:12 marvin postfix/pipe[17027]: 0CA895CB3A: to=<andy(a)x.y.org>, relay=dovecot, delay=0.41, delays=0.33/0.01/0/0.07, dsn=5.3.0, status=bounced (Command died with signal 11: "/usr/libexec/dovecot/deliver") Thanks, Andy

4 5

[Dovecot] Released Sieve v0.1.2 (important bug fixed)
by Stephan Bosch 26 Nov '08

26 Nov '08

Hello Dovecot users, Today, Andy Howell tripped an important bug in the Sieve interpreter that makes it crash when redirect is executed. That is why I quickly release yet another new version to provide a fix for this bug. I really should prevent this from happening again in the future by extending the test suite to test the execution of actions. Changelog v0.1.2: - Fixed important bug in the redirect action (and probably other actions like reject and vacation that only send messages). This was a bug in the handling of context information during the execution of actions. It caused the sieve interpreter to crash with a segfault when redirect was executed. The release is available here: http://www.rename-it.nl/dovecot/1.2/dovecot-1.2-sieve-0.1.2.tar.gz http://www.rename-it.nl/dovecot/1.2/dovecot-1.2-sieve-0.1.2.tar.gz.sig Refer to the initial release mail for more information: http://www.dovecot.org/list/dovecot-news/2008-October/000087.html Regards, -- Stephan Bosch stephan(a)rename-it.nl IRC: Freenode, #dovecot, S[r]us

1 0

[Dovecot] [OT] My appreciation for Dovecot
by Christoph Petersen 26 Nov '08

26 Nov '08

Hi guys! I recently switched to Dovecot from Courier with qmail+vpopmail backend. I'm really happy with the switch as all use-cases are more stable and much much faster than before. And the build process is much better as with Courier :) Just wanted to express my appreciation! BR Christoph

2 1

Re: [Dovecot] anti spam measures
by Johannes Berg 26 Nov '08

26 Nov '08

On Wed, 2008-11-26 at 06:30 -0700, Trever L. Adams wrote: > Trever L. Adams wrote: > > I believe it appears you have gone back to dspam, is this correct? No. > > What backend do you use? What version? I am using 3.8.1. I'm using crm114 still. > > I still have problems with your plugin with the hash driver and the > > sqlite3 driver seems to segfault all the time. > > > > Any ideas? Sorry, no. > I just realized it is the dovecot-antispam plugin that is returning the > error of not finding the signature. > > dovecot-1.1.6-2.fc10.i386 is the version of dovecot I am using. > > Looking at the message source, there is indeed an X-DSPAM-Signature line. Interesting. Somebody else was reporting the same errors, but I'm not seeing them. But I'm still using 1.1.2. I'll review the changes, I guess, but if I don't find anything quickly I won't get around to poking at it before Christmas. johannes

1 0

[Dovecot] Dovecot.1.1.6 Authentication problems using PAM+Kerberos
by Romer Ventura 26 Nov '08

26 Nov '08

Hello, This is my first post and it is to consult about an issue I am having. Here is the error I get in my logs: dovecot-auth: pam_krb5[22949]: error resolving user name 'mike' to uid/gid pair dovecot-auth: pam_krb5[22949]: error getting information about 'mike' If I use kinit to authenticate it works with no problems. Any ideas on the issue above..? Thanks..! Here is the dovecot related info: Dovecot n # 1.1.6: /etc/dovecot/dovecot.conf # OS: Linux 2.6.16.60-0.21-xenpae i686 SUSE Linux Enterprise Server 10 (i586) protocols: pop3 pop3s imap imaps login_dir: /var/run/dovecot/login login_executable(default): /usr/lib/dovecot/imap-login login_executable(imap): /usr/lib/dovecot/imap-login login_executable(pop3): /usr/lib/dovecot/pop3-login mail_location: maildir:~/Maildir/ mail_executable(default): /usr/lib/dovecot/imap mail_executable(imap): /usr/lib/dovecot/imap mail_executable(pop3): /usr/lib/dovecot/pop3 mail_plugin_dir(default): /usr/lib/dovecot/modules/imap mail_plugin_dir(imap): /usr/lib/dovecot/modules/imap mail_plugin_dir(pop3): /usr/lib/dovecot/modules/pop3 imap_client_workarounds(default): delay-newmail outlook-idle netscape-eoh imap_client_workarounds(imap): delay-newmail outlook-idle netscape-eoh imap_client_workarounds(pop3): pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh auth default: mechanisms: plain login passdb: driver: pam userdb: driver: passwd userdb: driver: static args: uid=1002 gid=1002 home=/home/vmail/%d/%Lu socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix

1 0

[Dovecot] Unable to use imapflags in sieve
by Guillaume Hilt 25 Nov '08

25 Nov '08

Hello, I'm using dovecot 1.1.6 with libsieve 2.2.5 and I can't use the imapflags extension. Here's the begginning of my .dovecot.sieve file : require ["fileinto"]; #require "imapflags"; #require "reject"; #if header :contains "X-DSPAM-Probability: 0.9" { # addflag "$label3"; #} # On déplace le spam dans le dossier Spam et on s'arrête là if header :contains "X-DSPAM-Result" "Spam" { fileinto "Spam"; # addflag "\\Seen"; stop; } # Si le destinataire est l'user apache, on discarde le mail if address :is "to" "ftp(a)shadowprojects.fr" { discard; } # Listes de diffusion if header :contains "List-Id" "dovecot.dovecot.org" { fileinto "Listes.Dovecot"; stop; } If i enable imapflags (require ["fileinto","imapflags"];) sieve won't work anymore (same with reject by the way). Only enabling it without using it (with addflag) is enough to stop sieve from working. All my emails will be delivered in my inbox despite the rules I use. If I remove imapflags, everything is working fine. And I don't see anything in my logs explaining the problem.

1 1

[Dovecot] [dovecot] Pre-populate index files for mbox
by Jonathan Siegle 25 Nov '08

25 Nov '08

Is there a program written that can be used to build the index files for a given mbox file without using IMAP/POP? If not I'll be happy to donate it when I'm done. The args would be the userid , the full path to the mbox and where to put the index files. -Jonathan

3 4

[Dovecot] Released Sieve v0.1.1 and ManageSieve v0.11.2 for Dovecot v1.2.alpha4
by Stephan Bosch 25 Nov '08

25 Nov '08

Hello Dovecot users, Since the first release of the new Sieve implementation, not that many bugs were reported. This is probably due to the fact that it is not tried yet by that many people. In the mean time, I did find and fix some more bugs myself, I adapted to changes in Dovecot, wrote some more documentation and started work on the enotify extension. Both Sieve and ManageSieve were changed to match API changes in Dovecot and therefore older versions will not compile against the new Dovecot release. Likewise, these new Sieve and ManageSieve releases will not compile for older Dovecot versions. Changelog Sieve v0.1.1: * Re-enabled support for compiling against dovecot headers. Much like cmusieve, command line tools like sievec and sieved are not compiled in this case. * Started implementation of enotify extension. Not anywhere near finished though. * Adapted to changes in Dovecot on various occasions, making this release dependent on Dovecot >= v1.2.alpa4. + Improved logging of errors at specific occasions and added debug messages to find script execution problems quicker. + Removed code duplication between command line tools and the test suite. Also restructured the sources of the tools. + Added UTF-8 to UTF-7 folder name conversion for compatibility with IMAP. + Created man pages for the command line tools. These are automatically installed upon 'make install' + Incorporated Valgrind support into the test suite and fixed a few memory leaks in the process. - Fixed compile error surfacing for gcc3.4. Forgot mask argument for the open() system call when the O_CREAT flag is specified. Bug found by Sergey Ivanov. - Fixed bug in the sievec tool. -d output was always written to stdout. - Fixed important bug in the imap4flags extension. When no :flags argument is specified, the previous version would always use the final value of the internal variable to set the flags. This means that modifications to the internal variable also affected the bare fileinto/keep actions executed earlier. This does not comply to the RFC. - Fixed bug in the include extension's import/export commands. Duplicate import/exports caused problems. - Fixed bug in the handling of non-existent scripts. Errors were sometimes ignored. - Dovecot omitted unfolding multi-line headers. This was added to the cmusieve plugin after the code was incorporated into the new implementation. This is now implicitly fixed by concurrent change in Dovecot. Changelog ManageSieve v0.11.2: * Adapted to changes in Dovecot, making this release dependent on Dovecot >= v1.2.alpa4 The following files are released: Sieve: http://www.rename-it.nl/dovecot/1.2/dovecot-1.2-sieve-0.1.1.tar.gz http://www.rename-it.nl/dovecot/1.2/dovecot-1.2-sieve-0.1.1.tar.gz.sig ManageSieve package: http://www.rename-it.nl/dovecot/1.2/dovecot-1.2-managesieve-0.11.2.tar.gz http://www.rename-it.nl/dovecot/1.2/dovecot-1.2-managesieve-0.11.2.tar.gz.s… ManageSieve patch: http://www.rename-it.nl/dovecot/1.2/dovecot-1.2.alpha4-managesieve-0.11.2.d… http://www.rename-it.nl/dovecot/1.2/dovecot-1.2.alpha4-managesieve-0.11.2.d… The full story of the new Sieve implementation is available in my previous posting: http://www.dovecot.org/list/dovecot-news/2008-October/000087.html I still need to update the wiki with pointers to the new Sieve implementation. I hope to have some time and motivation to do so in the next few days. Have fun testing the new releases and don't hesitate to notify me when there are problems. Regards, -- Stephan Bosch stephan(a)rename-it.nl IRC: Freenode, #dovecot, S[r]us

1 0

[Dovecot] v1.1.7 released
by Timo Sirainen 25 Nov '08

25 Nov '08

http://dovecot.org/releases/1.1/dovecot-1.1.7.tar.gz http://dovecot.org/releases/1.1/dovecot-1.1.7.tar.gz.sig I should have released this earlier since v1.1.6 had that annoying startup problem, but surprisingly few people complained about it so I kind of forgot about it then. BTW. v1.2 progresses nicely. Now that shared mailboxes are finally fully supported, there aren't any widely used IMAP features missing from Dovecot. v1.2.beta1 shouldn't be in too distant future anymore. * IMAP QUOTA extension now returns "MESSAGE" quota, not "MESSAGES". This makes Dovecot now RFC 2087 compliant. Hopefully this change doesn't break anyone's Dovecot-specific quota checking code.. + Added !include and !include_try directives to config file reader. Note that !include doesn't currently work with deliver. The main point here is that ssl_key_password can be placed to a different file with !include_try that deliver can just ignore. + More error/debug message logging improvements. - v1.1.6 gave "userdb didn't return a home directory" error at startup - Some config file parsers (deliver, passwd-file, acl, trash) ignored the file's last line if it didn't end with LF. - fts: SEARCH SUBJECT didn't search messages that weren't already in fts index. - fts-solr: Don't assert-crash if we couldn't connect to Solr. - IMAP: Mailbox deletion gave an error, but still worked, if mails' control directory wasn't the same as index directory. - Several fixes to rarely used mailbox list layout configurations.

6 11

[Dovecot] Panic from 1.1.7
by Mike Abbott 25 Nov '08

25 Nov '08

dovecot: Nov 24 12:49:06 Panic: IMAP(user): file ioloop-notify- kqueue.c: line 66 (event_callback): assertion failed: (io->refcount == 1) dovecot: Nov 24 12:49:06 Error: IMAP(user): Raw backtrace: 2 imap 0x0000000100068e82 default_fatal_finish + 41 -> 3 imap 0x0000000100068eed i_syslog_fatal_handler + 0 -> 4 imap 0x0000000100068687 i_info + 0 -> 5 imap 0x000000010006fc0a event_callback + 216 -> 6 imap 0x000000010006fdea io_loop_handler_run + 272 -> 7 imap 0x000000010006f1bf io_loop_run + 38 -> 8 imap 0x000000010006a319 dotlock_create + 532 -> 9 imap 0x000000010006ac0f file_dotlock_create + 177 -> 10 imap 0x000000010001a925 maildir_uidlist_lock_timeout + 169 -> 11 imap 0x000000010001aa14 maildir_uidlist_sync_init + 66 -> 12 imap 0x0000000100017d48 maildir_sync_context + 299 -> 13 imap 0x000000010001809a maildir_storage_sync_init + 104 -> 14 imap 0x000000010003e183 mailbox_sync + 31 -> 15 imap 0x000000010000bcca imap_status_get + 132 -> 16 imap 0x0000000100005355 cmd_status + 230 -> 17 imap 0x0000000100006cb5 client_command_input + 33 -> 18 imap 0x0000000100006e62 client_command_input + 462 -> 19 imap 0x0000000100006f61 client_handle_input + 239 -> 20 imap 0x00000001000070e8 client_input + 151 -> 21 imap 0x000000010006fdea io_loop_handler_run + 272 -> 22 imap 0x000000010006f1bf io_loop_run + 38 -> 23 imap 0x000000010000e046 main + 1671 -> 24 imap 0x0000000100001558 start + 52 -> 25 ??? 0x0000000000000001 0x0 + 1 Dovecot-1.1.7 on Mac OS X. Fixed by http://hg.dovecot.org/dovecot-1.2/rev/2c111b572eee ? (Just guessing.)

3 4

[Dovecot] PLAIN password scheme question
by Dmitri V. Ivanov 24 Nov '08

24 Nov '08

Hi, ppls There is some problem with using passwd-like file and plaintext passwords within it. Let's assume we have users speaking russian. They think and remember their passwords also within russian words (they just not change keyboard layout before entering their passwords). So if the user has password like ":jgf" (meaning "ass" in russian) and passwords are stored into passwd-like file within {PLAIN} scheme what will happen? ===== user:{PLAIN}:jgf:1234:1234:.... ===== Isn't it a reason to implement something like {HEX} and why? WBR Dmitri Ivanov

2 4

Re: [Dovecot] mbox file too large error with deliver
by Gokdeniz Karadag 24 Nov '08

24 Nov '08

> Timo Sirainen <tss(a)iki.fi> wrote: >> > Setting mailbox_size_limit to 0 made deliveries possible. a limit of >> > 2000000000 (<2GB) also did not show the errors. Thank you ! :) >> > >> > My issue is fixed but deliver might have a bug, so I will explain >> > things, sorry for not being clear previously. >> > >> > Old mail server was 32 bit(an old version of debian) and used >> > procmail for deliveries, that setup worked with the given limit of >> > 5GB and mailbox sizes above 1GB. >> > >> > After migrating to an 64 bit server (debian etch) and dovecot's >> > deliver, the stated delivery errors appeared for mailboxes above 1 >> > GB. As I stated at the beginning of my reply, setting >> > mailbox_size_limit below 2GB made deliveries possible. I tried with >> > edge values, mailbox_size_limit=2147483648 (exactly 2GB) would give >> > the following error in postfix logs: >> > >> > fatal: main.cf configuration error: mailbox_size_limit is smaller >> > than message_size_limit >> > >> > A limit of 2147483648 - 1 worked fine. >> > >> > There are two distinct bugs probably, one in postfix and one in >> > dovecot. > > Postfix clearly is using signed 32bit integer here, which could be > considered a bug. But why do you think there's a bug in Dovecot? Note > that Dovecot never even sees this value. It's the kernel that enforces > it, Dovecot simply reacts to a write() failure. The logs stating the "File too large" errors belong to dovecot's deliver process. While I was searching for a solution, I read that deliver honors mailbox_size_limit setting of postfix, I'm not sure if that is correct or not. Note that the destination mailboxes are smaller than 2GB here, but still gets "File too large" error. The machine is 64-bit, so no fs related kernel limits on file size. I have not dived into postfix and/or dovecot internals, but my guess is , dovecot gets the mailbox size limit and behaves accordingly. If that is the case, the problem can be fixed in dovecot's deliver code. If postfix sets file size limit with ulimit before execing deliver, OR uses a similar process which is out of deliver's control, then there is nothing concerning dovecot. If someone can clarify the issue I would be happy. -- Gokdeniz Karadag

2 1

[Dovecot] pam auth fail considered mail.error?
by David Halik 24 Nov '08

24 Nov '08

Hello all, Following the Dovecot wiki and migration help, we recently migrated our core IMAP systems from Courier to Dovecot on Solaris. So far it's been working great, but I have one issue that I'm curious about. Just as the docs mention, we also use "syslog_facility = mail" for logging. Unlike in the past, failed PAM auth attempts are now getting logged as mail.error: Nov 24 08:34:34 xxx.xxx.xxx.xxx dovecot: [ID 107833 mail.error] auth-worker(default): pam(dhalik,xxx.xxx.xxx.xxx): pam_authenticate() failed: Authentication failed Is there a reason for this, or a way to configure this behavior? mail.error is a little harsh for pam auth failures and I would think that the auth channel would be used instead similar to other processes (sshd, courier, etc) I'd like to continue using the mail facility, but if every time there is an auth error Dovecot reports to mail.error, my consoles and legitimate error logs are going to be full of something considered a non-issue by most. Any help is appreciated, thanks. -Dave -- ================================ David Halik System Administrator OIT-CSS Rutgers University dhalik(a)jla.rutgers.edu ================================

2 2

[Dovecot] two dovecot server using the same file system
by Osvaldo Alvarez Pozo 24 Nov '08

24 Nov '08

Hi all. I want to use two servers with dovecot using a common file system with drbd. So I have several questions. If one server write a mail to th file system he will use his name as part of the mail identification. the second server will use his own name. Each server will generate it own mail numbers . When an imap or pop user will consult the mails i shoul be confusion. Am I correct. is there a way of solving this issue?? Thanks

5 6

[Dovecot] Indexes recovery failed
by Daniel Watts 24 Nov '08

24 Nov '08

Hi Timo, Was getting the following error repeatedly in my mail client (squirremail) "error: connection dropped by IMAP server" Looked at the logs for this user and found the following: Nov 19 17:11:32 mink dovecot: IMAP(bobuser(a)maildom.com): broken sync positions in index file /virtual/store2/mail/s/bobuser_maildom.com/Maildir/dovecot.index Nov 19 17:11:32 mink dovecot: IMAP(bobuser(a)maildom.com): fscking index file /virtual/store2/mail/s/bobuser_maildom.com/Maildir/dovecot.index Nov 19 17:11:32 mink dovecot: IMAP(bobuser(a)maildom.com): Fixed index file /virtual/store2/mail/s/bobuser_maildom.com/Maildir/dovecot.index: log_file_tail_offset 2273345664 -> 996 Nov 19 17:11:32 mink dovecot: Panic: IMAP(bobuser(a)maildom.com): file mail-transaction-log.c: line 341 (mail_transaction_log_set_mailbox_sync_pos): assertion failed: (file_offset >= log->head->saved_tail_offset) Nov 19 17:11:32 mink dovecot: IMAP(bobuser(a)maildom.com): Raw backtrace: imap [0x46c772] -> imap [0x46c7e3] -> imap [0x46be56] -> imap [0x452d6d] -> imap(mail_index_sync_commit+0x42) [0x44e022] -> imap(maildir_sync_index_finish+0xdd) [0x42b59d] -> imap [0x42ada1] -> imap(maildir_storage_sync_init+0x64) [0x42af44] -> imap(mailbox_sync+0x1c) [0x43e96c] -> imap(cmd_select_full+0xce) [0x41a2be] -> imap(cmd_select+0xb) [0x41a44b] -> imap [0x41bb7c] -> imap [0x41bc32] -> imap [0x41c3ff] -> imap(client_input+0x63) [0x41c633] -> imap(io_loop_handler_run+0xf8) [0x472ed8] -> imap(io_loop_run+0x1d) [0x471ffd] -> imap(main+0x3c2) [0x423a92] -> /lib/libc.so.6(__libc_start_main+0xf4) [0x7f29213711c4] -> imap [0x416349] Looks like dovecot tried to fix the indexes but failed. I manually deleted all the dovecot.index* files and the account started working. Perhaps dovecot could try the fix but if it still fails just go and delete the indexes itself? Dovecot version 1.1.6 Using Maildirs Over NFS mount If you need any more info just let me know. Regards, Daniel

2 3

Re: [Dovecot] dovecot Digest, Vol 67, Issue 60
by Gokdeniz Karadag 24 Nov '08

24 Nov '08

dovecot-request(a)dovecot.org demis ki:: > Send dovecot mailing list submissions to > dovecot(a)dovecot.org > > To subscribe or unsubscribe via the World Wide Web, visit > http://dovecot.org/cgi-bin/mailman/listinfo/dovecot > or, via email, send a message with subject or body 'help' to > dovecot-request(a)dovecot.org > > You can reach the person managing the list at > dovecot-owner(a)dovecot.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of dovecot digest..." > > > Today's Topics: > > 1. mbox file too large error with deliver (Gokdeniz Karadag) > 2. Re: mbox file too large error with deliver (Charles Marcus) > 3. Re: mbox file too large error with deliver (Seth Mattinen) > 4. Re: core in lazy_expunge plugin (Timo Sirainen) > 5. Re: mbox file too large error with deliver (Timo Sirainen) > 6. v1.1.7 released (Timo Sirainen) > 7. Re: v1.1.7 released (Dave McGuire) > 8. Re: v1.1.7 released (Laurent Blume) > 9. v1.2.alpha4 released (Timo Sirainen) > 10. Re: v1.1.7 released (Timo Sirainen) > 11. Re: v1.1.7 released (Timo Sirainen) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Sun, 23 Nov 2008 23:55:15 +0200 > From: Gokdeniz Karadag <gokdenizk(a)gmail.com> > Subject: [Dovecot] mbox file too large error with deliver > To: dovecot(a)dovecot.org > Message-ID: <4929D143.50300(a)gmail.com> > Content-Type: text/plain; charset=UTF-8; format=flowed > > Hi, > > I am using dovecot on debian, with version 1.0.rc15-2etch4. Along with postfix. > > The deliver binary cannot deliver to large mailboxes. I cannot state an exact > size limit but mbox mailboxes above 1GB seem to be affected. > > I have these in in postfix/main.cf > mailbox_command = /usr/lib/dovecot/deliver > mailbox_size_limit = 5120000000 > > The user.log file shows these (I believe if no logging is specified, deliver > binary tries to log with "logger" and they go to user ?) > > user.log.3.gz:Nov 8 21:23:01 guvercin deliver(dummy): write() failed with mbox > file /var/mail/dummy: File too large > user.log.3.gz:Nov 8 21:23:01 guvercin deliver(dummy): > msgid=<4915957C.8090606(a)ceng.metu.edu.tr>: save failed to INBOX > user.log.3.gz:Nov 8 21:23:01 guvercin deliver(dummy): sieve runtime error: > Keep: Generic Error > > The /var/mail/dummy file exists and is 1.9GB, so my filesystem certainly > supports files >1G > > What may be the problem ? > > > dovecot -n output follows : > ---------------------------------------- > > log_timestamp: %Y-%m-%d %H:%M:%S > syslog_facility: local1 > protocols: imaps pop3s > ssl_cert_file(default): /etc/ssl/certs/imap-cert.pem > ssl_cert_file(imap): /etc/ssl/certs/imap-cert.pem > ssl_cert_file(pop3): /etc/ssl/certs/pop-cert.pem > ssl_key_file(default): /etc/ssl/private/imap-key.pem > ssl_key_file(imap): /etc/ssl/private/imap-key.pem > ssl_key_file(pop3): /etc/ssl/private/pop-key.pem > login_dir: /var/run/dovecot/login > login_executable(default): /usr/lib/dovecot/imap-login > login_executable(imap): /usr/lib/dovecot/imap-login > login_executable(pop3): /usr/lib/dovecot/pop3-login > mail_privileged_group: mail > mail_location: mbox:~/mail:INBOX=/var/mail/%u:INDEX=/var/spool/dovecot/indexes/%u > mbox_read_locks: fcntl dotlock > mbox_write_locks: fcntl dotlock > mail_executable(default): /usr/lib/dovecot/imap > mail_executable(imap): /usr/lib/dovecot/imap > mail_executable(pop3): /usr/lib/dovecot/pop3 > mail_plugin_dir(default): /usr/lib/dovecot/modules/imap > mail_plugin_dir(imap): /usr/lib/dovecot/modules/imap > mail_plugin_dir(pop3): /usr/lib/dovecot/modules/pop3 > imap_client_workarounds(default): outlook-idle tb-extra-mailbox-sep > imap_client_workarounds(imap): outlook-idle tb-extra-mailbox-sep > imap_client_workarounds(pop3): outlook-idle > pop3_uidl_format(default): > pop3_uidl_format(imap): > pop3_uidl_format(pop3): %08Xv%08Xu > pop3_client_workarounds(default): > pop3_client_workarounds(imap): > pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh > 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 > master: > > > ------------------------------ > > Message: 2 > Date: Sun, 23 Nov 2008 16:59:08 -0500 > From: Charles Marcus <CMarcus(a)Media-Brokers.com> > Subject: Re: [Dovecot] mbox file too large error with deliver > To: Dovecot Mailing List <dovecot(a)dovecot.org> > Message-ID: <4929D22C.8060401(a)Media-Brokers.com> > Content-Type: text/plain; charset=UTF-8 > > On 11/23/2008, Gokdeniz Karadag (gokdenizk(a)gmail.com) wrote: >> dovecot -n output follows : >> ---------------------------------------- >> >> log_timestamp: %Y-%m-%d %H:%M:%S > > Either this is an old version or you snipped the version from the top of > the dovecot -n output... > > What version of dovecot? > > Also, OS/version info may help too... > > Message: 5 > Date: Mon, 24 Nov 2008 00:12:56 +0200 > From: Timo Sirainen <tss(a)iki.fi> > Subject: Re: [Dovecot] mbox file too large error with deliver > To: Dovecot Mailing List <dovecot(a)dovecot.org> > Message-ID: <1227478376.20835.1017.camel@hurina> > Content-Type: text/plain; charset="us-ascii" > > On Sun, 2008-11-23 at 23:55 +0200, Gokdeniz Karadag wrote: >> > The deliver binary cannot deliver to large mailboxes. I cannot state an exact >> > size limit but mbox mailboxes above 1GB seem to be affected. >> > >> > I have these in in postfix/main.cf >> > mailbox_command = /usr/lib/dovecot/deliver >> > mailbox_size_limit = 5120000000 > > So this is 5 GB. I don't know how exactly the limits work with 32 bit > systems, but if you get the error with >1 GB files then my guess is that > this 5 GB gets wrapped to 1 GB (5 mod 4 = 1). > >> > user.log.3.gz:Nov 8 21:23:01 guvercin deliver(dummy): write() failed with mbox >> > file /var/mail/dummy: File too large > > Kernel gives this error when it reaches the maximum file size limit. > > If you don't want a limit, just set mailbox_size_limit = 0. Hi, Setting mailbox_size_limit to 0 made deliveries possible. a limit of 2000000000 (<2GB) also did not show the errors. Thank you ! :) My issue is fixed but deliver might have a bug, so I will explain things, sorry for not being clear previously. Old mail server was 32 bit(an old version of debian) and used procmail for deliveries, that setup worked with the given limit of 5GB and mailbox sizes above 1GB. After migrating to an 64 bit server (debian etch) and dovecot's deliver, the stated delivery errors appeared for mailboxes above 1 GB. As I stated at the beginning of my reply, setting mailbox_size_limit below 2GB made deliveries possible. I tried with edge values, mailbox_size_limit=2147483648 (exactly 2GB) would give the following error in postfix logs: fatal: main.cf configuration error: mailbox_size_limit is smaller than message_size_limit A limit of 2147483648 - 1 worked fine. There are two distinct bugs probably, one in postfix and one in dovecot. I guess this is result of using integer values for size limit. values greater than 2GB would wrap and cause warnings in postfix. Probably, my previous limit of 5GB would confuse things and no error was reported. (I don't know how, 5GB cannot be stored in an unsigned int, double overrun makes it within limit ? :) ) Maybe moving to "long long int" for mailbox file size is a possible solution. -- Gokdeniz Karadag

2 1

[Dovecot] mbox file too large error with deliver
by Gokdeniz Karadag 24 Nov '08

24 Nov '08

Hi, I am using dovecot on debian, with version 1.0.rc15-2etch4. Along with postfix. The deliver binary cannot deliver to large mailboxes. I cannot state an exact size limit but mbox mailboxes above 1GB seem to be affected. I have these in in postfix/main.cf mailbox_command = /usr/lib/dovecot/deliver mailbox_size_limit = 5120000000 The user.log file shows these (I believe if no logging is specified, deliver binary tries to log with "logger" and they go to user ?) user.log.3.gz:Nov 8 21:23:01 guvercin deliver(dummy): write() failed with mbox file /var/mail/dummy: File too large user.log.3.gz:Nov 8 21:23:01 guvercin deliver(dummy): msgid=<4915957C.8090606(a)ceng.metu.edu.tr>: save failed to INBOX user.log.3.gz:Nov 8 21:23:01 guvercin deliver(dummy): sieve runtime error: Keep: Generic Error The /var/mail/dummy file exists and is 1.9GB, so my filesystem certainly supports files >1G What may be the problem ? dovecot -n output follows : ---------------------------------------- log_timestamp: %Y-%m-%d %H:%M:%S syslog_facility: local1 protocols: imaps pop3s ssl_cert_file(default): /etc/ssl/certs/imap-cert.pem ssl_cert_file(imap): /etc/ssl/certs/imap-cert.pem ssl_cert_file(pop3): /etc/ssl/certs/pop-cert.pem ssl_key_file(default): /etc/ssl/private/imap-key.pem ssl_key_file(imap): /etc/ssl/private/imap-key.pem ssl_key_file(pop3): /etc/ssl/private/pop-key.pem login_dir: /var/run/dovecot/login login_executable(default): /usr/lib/dovecot/imap-login login_executable(imap): /usr/lib/dovecot/imap-login login_executable(pop3): /usr/lib/dovecot/pop3-login mail_privileged_group: mail mail_location: mbox:~/mail:INBOX=/var/mail/%u:INDEX=/var/spool/dovecot/indexes/%u mbox_read_locks: fcntl dotlock mbox_write_locks: fcntl dotlock mail_executable(default): /usr/lib/dovecot/imap mail_executable(imap): /usr/lib/dovecot/imap mail_executable(pop3): /usr/lib/dovecot/pop3 mail_plugin_dir(default): /usr/lib/dovecot/modules/imap mail_plugin_dir(imap): /usr/lib/dovecot/modules/imap mail_plugin_dir(pop3): /usr/lib/dovecot/modules/pop3 imap_client_workarounds(default): outlook-idle tb-extra-mailbox-sep imap_client_workarounds(imap): outlook-idle tb-extra-mailbox-sep imap_client_workarounds(pop3): outlook-idle pop3_uidl_format(default): pop3_uidl_format(imap): pop3_uidl_format(pop3): %08Xv%08Xu pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh 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 master:

4 3

[Dovecot] core in lazy_expunge plugin
by Anton Zakatov 24 Nov '08

24 Nov '08

Hello all! dovecot 1.1.6 Use lazy_expunge plugin call core on connect. Core: bt full #0 lazy_expunge_mail_expunge (_mail=0x2ac06e9b89e8) at lazy-expunge-plugin.c:103 lt = (struct lazy_expunge_transaction *) 0x2ac06e9b86e0 deststorage = <value optimized out> #1 0x000000000041cefc in imap_expunge (box=0x2ac06e988de8, next_search_arg=0x0) at imap-expunge.c:31 ctx = (struct mail_search_context *) 0x2ac06e9b87d0 t = (struct mailbox_transaction_context *) 0x2ac06e9aed10 mail = (struct mail *) 0x2ac06e9b89e8 search_arg = {next = 0x0, type = SEARCH_FLAGS, value = {subargs = 0x0, seqset = 0x0, str = 0x0, time = 0, size = 0, flags = MAIL_DELETED, keywords = 0x0}, context = 0x0, hdr_field_name = 0x0, not = 0, match_always = 0, result = -1} failed = <value optimized out> #2 0x00000000004171da in cmd_expunge (cmd=0x2ac06e982378) at cmd-expunge.c:62 client = (struct client *) 0x2ac06e982000 #3 0x000000000041b53c in client_command_input (cmd=0x2ac06e982378) at client.c:580 client = (struct client *) 0x2ac06e982000 command = <value optimized out> __PRETTY_FUNCTION__ = "client_command_input" #4 0x000000000041b5f2 in client_command_input (cmd=0x2ac06e982378) at client.c:629 client = (struct client *) 0x2ac06e982000 command = (struct command *) 0x0 __PRETTY_FUNCTION__ = "client_command_input" #5 0x000000000041bdaf in client_handle_input (client=0x2ac06e982000) at client.c:670 _data_stack_cur_id = 3 ret = <value optimized out> remove_io = <value optimized out> handled_commands = false #6 0x000000000041bfd3 in client_input (client=0x2ac06e982000) at client.c:725 cmd = <value optimized out> output = (struct ostream *) 0x2ac06e982298 bytes = 11 __PRETTY_FUNCTION__ = "client_input" #7 0x000000000048c568 in io_loop_handler_run (ioloop=<value optimized out>) at ioloop-epoll.c:203 ctx = <value optimized out> event = (const struct epoll_event *) 0x2ac06e93edc0 list = (struct io_list *) 0x2ac06e981cb0 io = (struct io_file *) 0x2ac06e981c50 tv = {tv_sec = 1799, tv_usec = 999456} events_count = <value optimized out> t_id = 2 msecs = <value optimized out> ret = 1 i = 0 call = <value optimized out> #8 0x000000000048b6ad in io_loop_run (ioloop=0x2ac06e93eb60) at ioloop.c:320 No locals. #9 0x0000000000423471 in main (argc=<value optimized out>, argv=0x0, envp=0x49a7f7) at main.c:293 Config: dovecot -n # 1.1.6: /etc/dovecot.conf # OS: Linux 2.6.18-92.1.13.el5 x86_64 CentOS release 5.2 (Final) base_dir: /var/run/dovecot/ log_path: /var/log/dovecot/dovecot.log info_log_path: /var/log/dovecot/dovecot.info.log protocols: imap imaps pop3 pop3s managesieve listen: * ssl_listen: * ssl_cipher_list: ALL:!LOW:!SSLv2 disable_plaintext_auth: yes verbose_ssl: yes login_dir: /var/run/dovecot//login login_executable(default): /usr/libexec/dovecot/imap-login login_executable(imap): /usr/libexec/dovecot/imap-login login_executable(pop3): /usr/libexec/dovecot/pop3-login login_executable(managesieve): /usr/libexec/dovecot/managesieve-login login_greeting_capability(default): yes login_greeting_capability(imap): yes login_greeting_capability(pop3): no login_greeting_capability(managesieve): no verbose_proctitle: yes mail_access_groups: vmail mail_uid: vmail mail_gid: vmail mail_location: maildir:~/:INBOX=~/.INBOX:INDEX=/data/maildata/dovecot/INDEX/%Lu/mail-indexes maildir_stat_dirs: yes maildir_copy_preserve_filename: yes mail_drop_priv_before_exec: yes mail_executable(default): /usr/local/bin/dovecot-imap-proxy mail_executable(imap): /usr/local/bin/dovecot-imap-proxy mail_executable(pop3): /usr/local/bin/dovecot-pop3-proxy mail_executable(managesieve): /usr/local/bin/dovecot-managesieve-proxy mail_plugins(default): quota imap_quota expire fts fts_squat listescape acl antispam zlib autocreate trash mail_plugins(imap): quota imap_quota expire fts fts_squat listescape acl antispam zlib autocreate trash lazy_expunge mail_plugins(pop3): quota expire mail_plugins(managesieve): mail_plugin_dir(default): /usr/lib64/dovecot/imap mail_plugin_dir(imap): /usr/lib64/dovecot/imap mail_plugin_dir(pop3): /usr/lib64/dovecot/pop3 mail_plugin_dir(managesieve): /usr/lib64/dovecot/managesieve imap_client_workarounds(default): outlook-idle delay-newmail imap_client_workarounds(imap): outlook-idle delay-newmail imap_client_workarounds(pop3): imap_client_workarounds(managesieve): pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh pop3_client_workarounds(managesieve): dict_db_config: /etc/dovecot/dovecot-db.conf sieve_storage(default): sieve_storage(imap): sieve_storage(pop3): sieve_storage(managesieve): /data/maildata/dovecot/sieve/%u sieve(default): sieve(imap): sieve(pop3): sieve(managesieve): ~/.dovecot.sieve namespace: type: private separator: / inbox: yes list: yes subscriptions: yes namespace: type: private separator: / prefix: Archive/ location: maildir:~/archive:INDEX=/data/maildata/dovecot/INDEX/%Lu/archive-indexes:CONTROL=/data/maildata/dovecot/CONTROL/%Lu/archive-control list: yes subscriptions: yes namespace: type: private separator: / prefix: EXPUNGED/ location: maildir:~/expunged list: yes subscriptions: yes namespace: type: private separator: / prefix: DELETED/ location: maildir:~/deleted list: yes subscriptions: yes namespace: type: private separator: / prefix: DELETED/EXPUNGED/ location: maildir:~/deleted/expunged list: yes subscriptions: yes namespace: type: public separator: / prefix: Public/ location: maildir:/data/maildata/mailboxes/%d/public/:INDEX=/data/maildata/dovecot/INDEX/%Lu/public list: yes namespace: type: public separator: / prefix: Public/info/ location: maildir:/data/maildata/mailboxes/%Ld/info:INDEX=/data/maildata/dovecot/INDEX/%Lu/public-info list: yes namespace: type: public separator: / prefix: Public/fax/ location: maildir:/data/maildata/mailboxes/abn.ru/fax:INDEX=/data/maildata/dovecot/INDEX/%Lu/public-fax list: yes namespace: type: public separator: / prefix: Public/info/Archive/ location: maildir:/data/maildata/mailboxes/%Ld/info/archive:INDEX=/data/maildata/dovecot/INDEX/%Lu/public-info-archive list: yes namespace: type: public separator: / prefix: Admins/ location: maildir:/data/maildata/mailboxes/abn.ru/root/:INDEX=/data/maildata/dovecot/INDEX/%Lu/root-indexes list: yes namespace: type: public separator: / prefix: Users/ location: maildir:/data/maildata/mailboxes/%d/shared_users/:INDEX=/data/maildata/dovecot/INDEX/%Lu/shared_users list: yes subscriptions: yes auth default: mechanisms: plain login realms: abn.ru default_realm: abn.ru cache_size: 1000 cache_negative_ttl: 0 username_format: %Lu master_user_separator: * worker_max_request_count: 500 passdb: driver: passwd-file args: /etc/dovecot/passwd.masterusers pass: yes master: yes passdb: driver: passwd-file args: username_format=%Ln /etc/dovecot/passwd.static passdb: driver: pam args: cache_key=%u%r username=%Ln nochangeuser=yes dovecot userdb: driver: static args: allow_all_users=yes uid=501 gid=501 username=%Ln domain=%Ld home=/data/maildata/mailboxes/%Ld/%Ln socket: type: listen client: path: /var/spool/postfix/private/dovecot-smtp-auth mode: 432 user: postfix group: postfix master: path: /var/run/dovecot/auth-master mode: 438 user: vmail group: vmail plugin: quota: dict:user:%u:proxy::quotadict quota_rule: *:storage=5G quota_rule2: Trash:storage=500M quota_rule3: spam:ignore quota_rule4: Spam:ignore quota_warning: storage=95%% /usr/local/bin/quota-warn.sh 95 quota_warning2: storage=80%% /usr/local/bin/quota-warn.sh 80 acl: vfile:/data/maildata/dovecot/dovecot-acls:cache_secs=300 trash: /etc/dovecot/trash.conf expire: Trash 7 Trash/* 7 Spam 14 spam 14 spam/* 14 expire_dict: proxy::expiredict lazy_expunge: EXPUNGED/ DELETED/ DELETED/EXPUNGED/ autocreate: spam autosubscribe: spam fts: squat fts_squat: partial=4 full=10 antispam_trash: trash;Trash;Deleted Items; antispam_spam: SPAM;spam;Spam;Junk;&BB0ENQQ2BDUEOwQwBE~E8- &BD8EPgRHBEIEMA-;junk antispam_mail_sendmail: /usr/local/bin/spam-train antispam_mail_sendmail_args: --for;%u antispam_mail_spam: spam antispam_mail_notspam: ham antispam_mail_tmpdir: /tmp dict: quotadict: mysql:/etc/dovecot/dovecot-dict-quota.conf expiredict: mysql:/etc/dovecot/dovecot-dict-expire.conf

2 1

[Dovecot] OT: Run Sieve On A Mailbox Manually
by Neil 22 Nov '08

22 Nov '08

(Apologies for being offtopic.) The subject basically says it all...does anyone know of a tool to run a sieve script on a mailbox (in particular, Maildirs) manually? Ideally, I'd like to do it without adding a bunch of new headers to the mail. So, could I just do a find (or for-loop, if it was just one maildir) command and pipe all the mails into deliver..? Thanks, Neil.

2 3

[Dovecot] folder deletion response problem
by Amr Shahin 22 Nov '08

22 Nov '08

dovecot version: 1.1.6 dovecot -n output # 1.1.6: /etc/dovecot/dovecot.conf # OS: Linux 2.6.18-53.el5PAE i686 CentOS release 5.2 (Final) ext3 log_path: /usr/local/dovecot/log protocols: imap ssl_disable: yes disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable: /usr/local/dovecot/libexec/dovecot/imap-login last_valid_uid: 510 mail_location: maildir:/var/mails/%n:CONTROL=/var/no-quota/%n mail_executable: /usr/local/dovecot/libexec/dovecot/imap mail_plugins: quota imap_quota mail_plugin_dir: /usr/local/dovecot/lib/dovecot imap_capability: IMAP4rev1 SORT THREAD=REFERENCES MULTIAPPEND UNSELECT LITERAL+ IDLE CHILDREN NAMESPACE LOGIN-REFERRALS UIDPLUS LIST-EXTENDED I18NLEVEL=1 AUTH=PLAIN auth default: executable: /usr/local/dovecot/libexec/dovecot/dovecot-auth debug: yes passdb: driver: sql args: /etc/dovecot/dovecot-sql.conf userdb: driver: sql args: /etc/dovecot/dovecot-sql.conf userdb: driver: passwd socket: type: listen client: path: /var/run/dovecot/auth-client mode: 432 master: path: /var/run/dovecot/auth-master mode: 438 plugin: quota: maildir:User quota quota_rule: *:storage=1G quota_rule2: Trash:ignore quota_rule3: Spam:ignore sieve: /var/sieve-scripts/%n.sieve ============================================= grep -v '^ *$#.*$\?$' output: auth_debug=yes protocols = imap disable_plaintext_auth = no log_path = /usr/local/dovecot/log ssl_disable = yes login_user = dovecot mail_location = maildir:/var/mails/%n:CONTROL=/var/no-quota/%n first_valid_uid = 500 last_valid_uid = 510 first_valid_gid = 1 last_valid_gid = 0 protocol imap { login_executable = /usr/local/dovecot/libexec/dovecot/imap-login mail_executable = /usr/local/dovecot/libexec/dovecot/imap imap_capability = IMAP4rev1 SORT THREAD=REFERENCES MULTIAPPEND UNSELECT LITERAL+ IDLE CHILDREN NAMESPACE LOGIN-REFERRALS UIDPLUS LIST-EXTENDED I18NLEVEL=1 AUTH=PLAIN mail_plugins = quota imap_quota mail_plugin_dir = /usr/local/dovecot/lib/dovecot } protocol pop3 { } protocol lda { postmaster_address = amrnablus(a)gmail.com hostname=maktoob.com mail_plugins = quota cmusieve mail_plugin_dir = /usr/local/dovecot/lib/dovecot/lda/ sendmail_path=/usr/sbin/sendmail.postfix auth_socket_path = /var/run/dovecot/auth-master mode = 384 } auth_executable = /usr/local/dovecot/libexec/dovecot/dovecot-auth auth default { mechanisms = plain user = root passdb sql { args = /etc/dovecot/dovecot-sql.conf } userdb sql { args = /etc/dovecot/dovecot-sql.conf } socket listen { master { path = /var/run/dovecot/auth-master mode = 0666 } client { path = /var/run/dovecot/auth-client mode = 0660 } } userdb passwd { } user = root } dict { } plugin { quota = maildir:User quota quota_rule = *:storage=1G quota_rule2 = Trash:ignore quota_rule3 = Spam:ignore sieve = /var/sieve-scripts/%n.sieve } ================================== the problem is that when i try to delete an existing directory in a mailbox, it gets actually deleted, but the response says that the mailbox does not exist, please check this log: 1 login <username> <password> 1 OK Logged in. 1 Create AAA 1 OK Create completed. 1 list "" "*" * LIST (\HasNoChildren) "." "TestDir" * LIST (\HasNoChildren) "." "Contacts" * LIST (\HasNoChildren) "." "Calendar" * LIST (\HasNoChildren) "." "Notes" * LIST (\HasNoChildren) "." "Tasks" * LIST (\HasNoChildren) "." "Spam" * LIST (\HasNoChildren) "." "Draft" * LIST (\HasNoChildren) "." "Trash" * LIST (\HasNoChildren) "." "Journal" * LIST (\HasNoChildren) "." "Sent" * LIST (\HasNoChildren) "." "AAA" * LIST (\HasNoChildren) "." "INBOX" 1 OK List completed. 1 Delete AAA 1 NO Mailbox doesn't exist: AAA 1 list "" "*" * LIST (\HasNoChildren) "." "TestDir" * LIST (\HasNoChildren) "." "Contacts" * LIST (\HasNoChildren) "." "Calendar" * LIST (\HasNoChildren) "." "Notes" * LIST (\HasNoChildren) "." "Tasks" * LIST (\HasNoChildren) "." "Spam" * LIST (\HasNoChildren) "." "Draft" * LIST (\HasNoChildren) "." "Trash" * LIST (\HasNoChildren) "." "Journal" * LIST (\HasNoChildren) "." "Sent" * LIST (\HasNoChildren) "." "INBOX" 1 OK List completed. 1 logout * BYE Logging out 1 OK Logout completed.

3 2

[Dovecot] mail_privileged_group not working for dotlock files (1.1.6)
by Rob Mangiafico 22 Nov '08

22 Nov '08

Hello, Running dovecot 1.1.6 on centOS 5 and RHEL 5. With the settings: pop3_lock_session = yes mail_privileged_group = mail mail_location = mbox:~/:INBOX=/var/spool/mail/%u mbox_read_locks = fcntl mbox_write_locks = dotlock fcntl and /var/spool/mail permissions: drwxrwx--x 2 root mail 4096 Nov 19 10:16 mail/ Trying to connect via POP3 results in this error: --- Nov 19 09:31:01 lexiconn2 dovecot: child 32127 (pop3) killed with signal 11 Nov 19 09:31:01 lexiconn2 dovecot: POP3(cerberus): file_lock_dotlock() failed with mbox file /var/spool/mail/xxx: Permission denied Nov 19 09:31:01 lexiconn2 dovecot: pop3-login: Login: user=<xxx>, method=PLAIN, rip=1.2.3.4, lip=5.6.7.8, secured --- The docs seem to indicate the above config / settings should work. Is this a bug? The reason we have dotlock as the primary format is due to procmail LDA from sendmail: --- procmail -v 2>&1|grep Locking Locking strategies: dotlocking, fcntl() --- I assume we have to make the "mbox_write_locks" match the procmail locking... Thanks. Rob

2 3

[Dovecot] expire-tool fails if mail_location contains %h
by Thorsten Vollmer 21 Nov '08

21 Nov '08

Hi Timo, not long ago you fixed a bug regarding the expansion of ~/ in mail_location that prevented expire-tool from working correctly. A similar problem exists if mail_location contains %h: expire-tool will use the wrong path to access the mailbox. After replacing %h with ~, expire-tool works as expected. Why are there two variables for the home directory? Maybe the use of %h could be discouraged, sparing you some problems. Regards, Thorsten

2 2

[Dovecot] Separate quotas not displayed correctly
by Laurent Blume 21 Nov '08

21 Nov '08

Hello all, My system is set up to have quotas both on /var/mail, where emails are received, and on /export/home, where users' homedirs are. But the client (Thunderbird) shows the same /export/home values both for the Inbox and for the folders in the homedir, so a user cannot know where she stands on her /var/mail use. This is Dovecot 1.1.5. As per the wiki, the dovecot.conf file contains this: quota = fs:INBOX:mount=/var/mail quota2 = fs:Others:mount=/export/home A sample user: # quota -v testimap Disk quotas for testimap (uid 1143): Filesystem usage quota limit timeleft files quota limit timeleft /export/home 6490 10000 15000 0 0 0 /var/mail 0 20000 25000 0 0 0 When Icheck the Quota tab in the Properties of the Inbox, the field contains "Others", and the value are 6490 out of 10000. Any idea why this doesn't display the value of /var/mail? Laurent -- / Leader de Projet & Communauté | I'm working, but not speaking for \ G11N http://fr.opensolaris.org | Bull Services http://www.bull.com / FOSUG http://guses.org |

2 5

[Dovecot] FW: nfs troubles
by Bas van Oosterum 21 Nov '08

21 Nov '08

Hi all, I upgraded to dovecot 1.1.6 to be able to use NFS. Got a little issue: I can't move mail to another IMAP folder (so I can't delete to: moving to .trash does not work. Error message Oct 31 11:07:45 jozua-mailserver dovecot: IMAP(nicolette(a)kerknet.org): fdatasync_path(/var/mail/kerknet.org/nicolette/Maildir/.Trash/cur) failed: Invalid Argument I tried to use ll sorts of locking: no difference Who can help? Regards, Bas

2 3

[Dovecot] Dovecot and Bogofilter
by Matthias-Christian Ott 21 Nov '08

21 Nov '08

Hi, on my small Xen-virtualised server with 48 MiB RAM I use Postfix and Dovecot, because the Debian administrators dislike qmail [1], which is in my opinion despite some maintainability and code quality issues a quite well designed software, because it mostly follows the UNIX principles. Postfix is not able to sort my E-Mail into different Maildir folders and after I looked at procmail's source code, I decided to use Dovecot's LDA, because it supports sieve via a plugin. All in all it worked after some tweaking and Dovecot is now responsible for authentication and delivery. Furthermore I want to setup a spam filter and due to the memory constraints I decided in favour of bogofilter (I made no real world tests, but the authors claim that it's fast and has a small memory footprint). My first idea was train bogofilter via a cronjob that runs bogofilter for each E-Mail in my spam folder and deletes them afterwards. Then I stumbled upon the dovecot antispam [2] plugin and quickly wrote a backend for bogofilter. During the development I realised that bogofilter has to update the X-Bogosity header of the reclassified E-Mails. Johannes Berg told me that he wasn't sure whether dovecot would be able to do this and recommended to ask this on the mailing list. An other problem is that each mail needs to be initially classified and due to the fact that sieve is not able to execute external programmes, deliver has to do this task. I'm currently thinking of possibilities to implement this, so far I came up with the following: 1. Write a generic pipe plugin which can execute an arbitrary number of programmes. The problem with this is that I'm not sure how to integrate this is in Dovecot's configuration file. I thought of something like this: pipe = prg1 | prg2 2. Write a bogofilter-specific plugin for this. Anyhow I would like to take this opportunity to criticise Dovecot for being a bloated (unnecessary abstractions, verbose, pseudo object-oriented, ...), non-suckless [3] and non-unixish (plugin architecture, monolithic design, ...) software which in return works quite well and stable so far. I appreciate any suggestions, ideas or criticism. I would really like to finish configuring my mail server as soon as possible. Regards, Matthias-Christian [1] http://smarden.org/pape/Debian/1215531259.4854_332.werc [2] http://johannes.sipsolutions.net/Projects/dovecot-antispam [3] http://www.suckless.org/common/

9 16

[Dovecot] nfs_flush_fcntl failed: No locks available
by Mark Zealey 21 Nov '08

21 Nov '08

Hi there, I've been seeing this error in our logs quite frequently on our nfs storage (v3): 2008-11-10T13:24:26+00:00 mail8 dovecot: IMAP(XXX(a)YYY.com): nfs_flush_fcntl: fcntl(/var/spool/mail/XXX/Maildir/dovecot.index.cache, F_RDLCK) failed: No locks available Which is because we don't run lockd on our servers. Why is dovecot trying to use fcntl() ? I explicitly set it to use dotlocks in the dovecot config: # 1.1.6: /etc/dovecot.conf # OS: Linux 2.6.18-92.el5 i686 CentOS release 5.2 (Final) base_dir: /var/run/dovecot/ protocols: imap pop3 mail_location: maildir:~/Maildir mmap_disable: yes mail_nfs_storage: yes mail_nfs_index: yes lock_method: dotlock maildir_copy_preserve_filename: yes mbox_write_locks: dotlock This happens for both pop and imap (however more frequently with imap). Thanks, Mark -- Mark Zealey -- Shared Hosting Team Leader Product Development * Webfusion 123-reg.co.uk, webfusion.co.uk, donhost.co.uk, supanames.co.uk This mail is subject to http://www.gxn.net/disclaimer

2 2

[Dovecot] For Configuration Help: per-user quota for virtual users.
by sales＠100n.org 21 Nov '08

21 Nov '08

Dear dovecot list: Could any experts help me on the configuration of per-user for dovecot on FreeBSD 7.x with postfix-2.5.4,1. I followed the howto of http://workaround.org/articles/ispmail-etch/, it is an excellent file, my mailserver worked very well. When I configured per-user quota plug-in, quota_rule with 20MB limits can not be overrided by the Mysql query statement, Although I followed the document at : http://wiki.dovecot.org/Quota. Below is the output of dovecot --version, dovecot -n and dovecot-sql.conf. Could any experts help me? Thanks in advance ! Best Regards, Forrest --------------------------------- ns1# dovecot --version 1.1.2 ns1# dovecot -n # 1.1.2: /usr/local/etc/dovecot.conf protocols: imap pop3 pop3s imaps 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 verbose_proctitle: yes first_valid_gid: 0 mail_privileged_group: mail mail_location: maildir:/home/vmail/%d/%n/Maildir 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(default): quota imap_quota mail_plugins(imap): quota imap_quota mail_plugins(pop3): 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): delay-newmail netscape-eoh tb-extra-mailbox-sep imap_client_workarounds(imap): delay-newmail netscape-eoh tb-extra-mailbox-sep imap_client_workarounds(pop3): pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh auth default: mechanisms: plain login passdb: driver: sql args: /usr/local/etc/dovecot-sql.conf userdb: driver: passwd userdb: driver: static args: uid=5000 gid=5000 home=/home/vmail/%d/%n allow_all_users=yes socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix master: path: /var/run/dovecot/auth-master mode: 384 user: vmail plugin: quota: maildir quota_rule: *:storage=20M quota_rule2: Trash:storage=10M quota_warning: storage=95%% /usr/local/bin/quota-warning.sh 95 quota_warning2: storage=80%% /usr/local/bin/quota-warning.sh 80 ns1# grep -v '^ *$#.*$\?$' dovecot-sql.conf driver = mysql connect = host=127.0.0.1 dbname=****** user=****** password=******** default_pass_scheme = PLAIN-MD5 password_query = SELECT email as user, password FROM view_users WHERE email='%u'; user_query = select 5000 as uid, 5000 as gid, '/home/vmail/%d/%n' as home, \ concat('*:bytes=', quota_bytes) as quota_rule \ from email_quota where email = '%u'

2 1

[Dovecot] Problem witch dovecot-auth continue
by Grzegorz Zalewski 21 Nov '08

21 Nov '08

I`m forgot paste rest of the log: dovecot: 2008-11-07 10:16:44 Panic: auth(default): file auth-worker-server.c: line 54 (auth_worker_idle_timeout): assertion failed: (array_count(&conn->requests) == 0)

2 1

[Dovecot] Per User Quotas
by Peter Fraser 21 Nov '08

21 Nov '08

HI All Asking for a little patience and a bit of help here. I'm using dovecot-1.1.3_1 with postfix and squirrelmail. I have implemented a global quota successfully. That works fine. I want to now implement per user quotas. So far I have read the howto in the documentation and searched several threads but can't seem to get it working properly. My LDAP server is Windows 2003 Active Directory. Is there any documentation specific to AD that I could look at or any other doc that could help me? My last effort was to put this in dovecot-ldap.conf user_attrs = streetAddress=quota_rule4=*:storage=%$M ,=uid=1002,=gid=1002,=home=/home/vmail/%u and this in dovecot.conf in addition to the other quota rules. quota_rule4 = *:bytes=%$ I then put the quota in the streetAddress area of AD. I'd certainly appreciate any help. Thanks.

2 4

[Dovecot] make archive emails undeletable?
by Rob Nichols 21 Nov '08

21 Nov '08

I've been using dovecot for a year or two now, and really like it. I have a fairly simple setup, but I think it's time to get a little more advanced. I keep an "archive" of all my email, both sent and received. Every once in a while I get confused, and accidentally delete something from my archive. I also worry that I'll misconfigure a mail client some day and accidentally wipe out my "trash" folder. I would like some way to prevent deletion in several mailboxes. Is that possible? It looks like ACL could do this, but I can't quite figure out where to start. Any pointers would be greatly appreciated. Thanks, Rob

2 1

[Dovecot] Disconnecting without unbinding?
by Maykel Moya 21 Nov '08

21 Nov '08

Timo Please have a look at this short thread[1]. That message stops appearing whenever I shutdown dovecot. I'm using dovecot 1.0.15. dovecot-ldap.conf ----------------- dn = ... dnpass = ... ldap_version = 3 auth_bind = no base = ... pass_filter = ... pass_attrs = ... user_filter = ... user_attrs = ... default_pass_scheme = MD5-CRYPT user_global_uid = vmail user_global_gid = vmail Regards, maykel [1] http://www.openldap.org/lists/openldap-software/200811/msg00078.html --------------------------------------- Red Telematica de Salud - Cuba CNICM - Infomed

2 1

[Dovecot] Auth Issues - Urgent - Help!
by David Cunningham 21 Nov '08

21 Nov '08

After a few hours of running, I get tons of the following errors in my logs: dovecot: Oct 08 07:41:50 Error: auth(default): ldap(user(a)domain,x.x.x.x): Request queue is full I removed the username and IP, obviously. Any idea how to stop this? I have about 5 Thousand users using horde that login ever 1-5 minutes to refresh their page. I assume it is a setting, but I am confused as to why it doesn't happen almost right away. It seems to take some time to build up. Please help! This is taking my webmail system down hourly.

6 20

[Dovecot] Error message in logs since 1.1.6 upgrade
by Guy 21 Nov '08

21 Nov '08

Hi, I've got two imap boxes, one is running 1.1.5 and hasn't exhibited the error below, but the one that's been upgraded to 1.1.6 is showing them. Nov 14 16:06:31 mink dovecot: imap-login: Disconnected (no auth attempts): rip=x.x.x.x, lip=x.x.x.x, TLS handshaking: SSL_accept() failed: error:1408F119:SSL routines:SSL3_GET_RECORD:decryption failed or bad record mac If this isn't already a known error, is there any extra data I can collect that would help diagnose what's causing it? I haven't a clue where to start with this sort of debugging I'm afraid. Thanks Guy -- Don't just do something...sit there!

2 1

[Dovecot] sieve-body extension support for deliver LDA's sieve plugin
by BrunoM 21 Nov '08

21 Nov '08

Hello, I just read your message about sieve and body-extension in Dovecot. Do you have news on that topic? I just have to filter mails containing a particular text fragment, and I cannot do without sieve body, I think.. Thank you for any clue you'd be able to give me ! Regards, Bruno --- Hi Timo & Co, Is there any time frame for updating the deliver LDA's sieve plugin code to that from Cyrus IMAPd v2.3.x? I ask as I'm looking for the functionality of the sieve-body extension, as described here: http://www.ietf.org/internet-drafts/draft-ietf-sieve-body-06.txt This requirement has come up as we're upgrading from a Courier-IMAP/maildrop configuration that has some filtering based on message body content. As an aside, if that time frame is undefined or will be long, if I use maildrop instead as my LDA, will I loose the instant delivery notification via IMAP IDLE? Thanks very much, Scott

2 1