- dovecot - dovecot.org

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