- dovecot - dovecot.org

Re: [Dovecot] deliver: Fatal: setgid(114) failed with euid=8, gid=8, egid=8: Operation not permitted
by Charles Marcus 01 Oct '09

01 Oct '09

Please always keep replies on list... On 10/1/2009 7:18 AM, Fredriksson Turbo wrote: >>> But it seems that all mails that was received between 16:52:19 >>> and 11:07:52 (which was the last mail that couldn't be delivered) >>> is lost! >> Without logs, it is impossible to say what happened to the mails... >> >> Were they accepted, then lost? Or were they simply rejected? > The error log say: > > deliver(<EMAIL>): 2009-09-30 11:07:52 Fatal: setgid(114) failed with > euid=8, gid=8, egid=8: Operation not permitted > > The info log say that everything was a-ok... > > So the mail was accepted, put in the spool, picked up for local > delivery, spamchecked etc and when it was supposed to be put in > a file in the mail directory, lost... This may be enough for Timo, but its always better to give the full logs of one of these transactions - not just the dovecot error log, but full system logs, showing the message entering the system, each step of processing, and ending with the final delivery (attempt)... -- Best regards, Charles Marcus I.T. Director Media Brokers International, Inc. 678.514.6200 x224 678.514.6299 fax

1 0

[Dovecot] Compile dovecot 1.2.5 with managesieve patch 0.11.9?
by Seba 01 Oct '09

01 Oct '09

Hi, is it possible to compile dovecot 1.2.5 with the managesieve patch 0.11.9 which is for dovecot 1.2.4 or is it better to wait if a new managesieve patch is released? Maybe 1.2.5 will work too? Thanks, Seba

3 2

[Dovecot] imap crashed, (imap) killed with signal 11
by Robert Gabriel 01 Oct '09

01 Oct '09

There is an error in dovecot 1.2.5 when loggin in: dovecot: Error: child 14816 (imap) killed with signal 11

1 0

[Dovecot] Some issues in Dovecot 1.2.5 after upgrade from 1.0.15
by Chris Wakelin 01 Oct '09

01 Oct '09

We upgraded from Dovecot 1.0.15 to 1.2.5 last night, on Solaris 10 using mboxes, mostly without issues. However I had to trash the index/cache files (too many folders were showing corruption issues which is especially bad for Prayer Webmail ".prayer" folders that store preferences; Prayer sees a disconnection as the folder being missing!). I've had one imap process panic in mailbox sync (as I mentioned above, the index files have been newly created in 1.2.5): > Sep 30 09:57:10 imap-login: Info: Login: user=<xxxxxxxx>, method=PLAIN, rip=134.225.xx.xx, lip=134.225.16.6 > Sep 30 09:57:10 imap-login: Info: Login: user=<xxxxxxxx>, method=PLAIN, rip=134.225.xx.xx, lip=134.225.16.6 > Sep 30 09:57:11 IMAP 25384 xxxxxxxx 134.225.xx.xx : Panic: file mail-index-sync-update.c: line 933 (mail_index_sync_map): assertion failed: (map->hdr.indexid == index->indexid || map->hdr.indexid == 0) > Sep 30 09:57:11 dovecot: Error: child 25384 (imap) killed with signal 6 (core dumped) This looks like it was the user's first connection since the upgrade, as well. Here's the backtrace: > #0 0xff21fe78 in _libc_kill () from /usr/lib/libc.so.1 > (gdb) bt > #0 0xff21fe78 in _libc_kill () from /usr/lib/libc.so.1 > #1 0xff1b5a3c in abort () from /usr/lib/libc.so.1 > #2 0xbe258 in default_fatal_finish (type=LOG_TYPE_PANIC, status=0) at failures.c:160 > #3 0xbeb14 in i_internal_fatal_handler (type=LOG_TYPE_PANIC, status=0, fmt=0x0, args=0xffbee758) at failures.c:440 > #4 0xbe414 in i_panic (format=0xec7f0 "file %s: line %d (%s): assertion failed: (%s)") at failures.c:207 > #5 0x98a00 in mail_index_sync_map (_map=0x1263e4, type=MAIL_INDEX_SYNC_HANDLER_HEAD, force=false) at mail-index-sync-update.c:802 > #6 0x8c618 in mail_index_map (index=0x1263a8, type=MAIL_INDEX_SYNC_HANDLER_HEAD) at mail-index-map.c:934 > #7 0x89e30 in mail_index_refresh (index=0x0) at mail-index.c:551 > #8 0x62bec in mbox_sync_header_refresh (mbox=0x1272d8) at mbox-sync.c:1586 > #9 0x62d28 in mbox_sync_has_changed_full (mbox=0x1272d8, leave_dirty=true, empty_r=0xffbeeab7) at mbox-sync.c:1644 > #10 0x62cb4 in mbox_sync_has_changed (mbox=0xffffffff, leave_dirty=true) at mbox-sync.c:1611 > #11 0x63428 in mbox_sync_int (mbox=0x1272d8, flags=0, lock_id=0xffbeee04) at mbox-sync.c:1701 > #12 0x634f4 in mbox_sync (mbox=0x1272d8, flags=0) at mbox-sync.c:1894 > #13 0x63674 in mbox_storage_sync_init (box=0x1272d8, flags=65) at mbox-sync.c:1936 > #14 0x7ebf4 in mailbox_sync_init (box=0x1272d8, flags=65) at mail-storage.c:562 > #15 0x7ecb8 in mailbox_sync (box=0x1272d8, flags=65, status_items=239, status_r=0xffbeefd0) at mail-storage.c:593 > #16 0x29fc0 in select_open (ctx=0x11ebf0, mailbox=0x1 <Address 0x1 out of bounds>, readonly=false) at cmd-select.c:273 > #17 0x2a294 in cmd_select_full (cmd=0x11eb60, readonly=false) at cmd-select.c:382 > #18 0x2a3d0 in cmd_select (cmd=0x11eb60) at cmd-select.c:389 > #19 0x2d064 in client_command_input (cmd=0x11eb60) at client.c:611 > #20 0x2cf08 in client_command_input (cmd=0x11eb60) at client.c:660 > #21 0x2d0ec in client_handle_next_command (client=0x11e8d8, remove_io_r=0xffbef2b7) at client.c:701 > #22 0x2d1e0 in client_handle_input (client=0x11e8d8) at client.c:713 > #23 0x2d318 in client_input (client=0x11e8d8) at client.c:752 > #24 0xc7ea4 in io_loop_handler_run (ioloop=0x11b370) at ioloop-poll.c:203 > #25 0xc7694 in io_loop_run (ioloop=0x11b370) at ioloop.c:335 > #26 0x36e34 in main (argc=1119232, argv=0xffbef4fc, envp=0xffbef50c) at main.c:327 I'm also seeing some other errors, e.g. : > Sep 30 10:37:06 auth(default): Error: Master request 15820.607 not found > Sep 30 10:51:27 dovecot: Error: child 29959 (login) killed with signal 11 (core not dumped) (latest ip=134.225.1.46) > Sep 30 10:51:38 dovecot: Error: child 11162 (login) killed with signal 11 (core not dumped) (latest ip=134.225.1.46) > Sep 30 10:54:03 imap-login: Warning: Error sending handshake to auth server: Transport endpoint is not connected How do I get the login (presumably imap-login) processes to dump core (or do I need to insert gdbhelper)? Dovecot -n output (%J is a local hash function and we don't use the lda; my start-up script sets the fd limit to 4096 once Dovecot has started): > # 1.2.5: /opt/RDGdovect/etc/dovecot.conf > Warning: fd limit 2048 is lower than what Dovecot can use under full load (more than 4352). Either grow the limit or change login_max_processes_count and max_mail_processes settings > # OS: SunOS 5.8 sun4u ufs > base_dir: /opt/RDGdovect/var/run/ > log_path: /opt/RDGdovect/var/log/dovecot.log > info_log_path: /opt/RDGdovect/var/log/dovecot.log > protocols: imap imaps pop3 pop3s > listen(default): 134.225.16.6:143 > listen(imap): 134.225.16.6:143 > listen(pop3): 134.225.16.6:110 > ssl_listen(default): 134.225.16.6:993 > ssl_listen(imap): 134.225.16.6:993 > ssl_listen(pop3): 134.225.16.6:995 > ssl_cert_file(default): /opt/RDGdovect/ssl/imap.reading.ac.uk.crt.pem > ssl_cert_file(imap): /opt/RDGdovect/ssl/imap.reading.ac.uk.crt.pem > ssl_cert_file(pop3): /opt/RDGdovect/ssl/pop.reading.ac.uk.crt.pem > ssl_key_file(default): /opt/RDGdovect/ssl/imap.reading.ac.uk.key.pem > ssl_key_file(imap): /opt/RDGdovect/ssl/imap.reading.ac.uk.key.pem > ssl_key_file(pop3): /opt/RDGdovect/ssl/pop.reading.ac.uk.key.pem > disable_plaintext_auth: no > shutdown_clients: no > login_dir: /opt/RDGdovect/var/run/login > login_executable(default): /opt/RDGdovect/libexec/dovecot/imap-login > login_executable(imap): /opt/RDGdovect/libexec/dovecot/imap-login > login_executable(pop3): /opt/RDGdovect/libexec/dovecot/pop3-login > login_greeting(default): University of Reading IMAP ready. > login_greeting(imap): University of Reading IMAP ready. > login_greeting(pop3): University of Reading POP3 ready. > login_process_per_connection: no > max_mail_processes: 4096 > verbose_proctitle: yes > mail_location: mbox:/export/folders/%13.h/mail/:INBOX=/export/mail/%13.h/INBOX:INDEX=/export/indexes/%13.h > mail_nfs_storage: yes > mbox_very_dirty_syncs: yes > mail_drop_priv_before_exec: yes > mail_executable(default): /opt/RDGdovect/libexec/dovecot/imap > mail_executable(imap): /opt/RDGdovect/libexec/dovecot/imap > mail_executable(pop3): /opt/RDGdovect/libexec/dovecot/pop3 > mail_plugins(default): zlib mail_log > mail_plugins(imap): zlib mail_log > mail_plugins(pop3): > mail_plugin_dir(default): /opt/RDGdovect/libexec/plugins > mail_plugin_dir(imap): /opt/RDGdovect/libexec/plugins > mail_plugin_dir(pop3): /opt/RDGdovect/lib/dovecot/pop3 > mail_log_prefix: %Us %p %u %r : > imap_client_workarounds(default): delay-newmail > imap_client_workarounds(imap): delay-newmail > imap_client_workarounds(pop3): > pop3_reuse_xuidl(default): no > pop3_reuse_xuidl(imap): no > pop3_reuse_xuidl(pop3): yes > pop3_uidl_format(default): %08Xu%08Xv > pop3_uidl_format(imap): %08Xu%08Xv > pop3_uidl_format(pop3): %08Xv%08Xu > pop3_client_workarounds(default): > pop3_client_workarounds(imap): > pop3_client_workarounds(pop3): outlook-no-nuls > namespace: > type: private > separator: / > inbox: yes > list: yes > subscriptions: yes > namespace: > type: private > separator: / > prefix: mail/ > hidden: yes > list: no > subscriptions: yes > namespace: > type: private > separator: / > prefix: ~/mail/ > hidden: yes > list: no > subscriptions: yes > namespace: > type: private > separator: / > prefix: ~%u/mail/ > hidden: yes > list: no > subscriptions: yes > lda: > postmaster_address: postmaster(a)example.com > auth default: > mechanisms: plain login > username_format: %Lu > verbose: yes > passdb: > driver: passwd-file > args: /export/mailconfig/%Ju/%u/migrating > deny: yes > passdb: > driver: passwd-file > args: /export/mailconfig/%Ju/%u/proxy.%Ls > passdb: > driver: ldap > args: /opt/RDGdovect/etc/dovecot-ldap.conf > userdb: > driver: passwd-file > args: /opt/RDGdovect/etc/userdb Best Wishes, Chris -- --+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+- Christopher Wakelin, c.d.wakelin(a)reading.ac.uk IT Services Centre, The University of Reading, Tel: +44 (0)118 378 8439 Whiteknights, Reading, RG6 2AF, UK Fax: +44 (0)118 975 3094

2 9

[Dovecot] Virtual Plugin
by Darvin Denmian 01 Oct '09

01 Oct '09

I activated Dovecot's Virtual Plugin in my configuration and created dovecot-virtual file with the following content: [quote] # ~/Maildir/virtual/Flagged/dovecot-virtual * flagged [quote] When I flag some messages these messages automatically appears inside my Virtual Folder called "Flagged", but once inside this folder , when I "Unflag" the message, It doesn't disapear from my virtual folder. Is this expected? I'm using dovecot12-1.2.5-2.1 on a Opensuse 11.1 I hope you understand my brazilian english :) Thanks

2 1

[Dovecot] How many concurrent IMAP sessions?
by Patrick Ben Koetter 01 Oct '09

01 Oct '09

Has anybody ever bothered to measure how many concurrent IMAP sessions dovecot can handle? I know it depends on hardware, filesystem, mailbox type etc., but what exactly controls the number and what have people on the list measured? p@rick -- state of mind Digitale Kommunikation http://www.state-of-mind.de Franziskanerstraße 15 Telefon +49 89 3090 4664 81669 München Telefax +49 89 3090 4666 Amtsgericht München Partnerschaftsregister PR 563

5 10

[Dovecot] cant compile dsync
by joakim＠verona.se 30 Sep '09

30 Sep '09

I'm trying to compile dsync, but failing. What am I doing wrong? hg pull pulling from http://hg.dovecot.org/dovecot-2.0/ ... ./configure && make clean all ... make[5]: Entering directory `/mnt/data/build/dovecot-2.0/src/lib-storage/index/maildir' make[5]: *** No rule to make target `maildir-transaction.c', needed by `maildir-transaction.lo'. Stop. make[5]: Leaving directory `/mnt/data/build/dovecot-2.0/src/lib-storage/index/maildir' make[4]: *** [all-recursive] Error 1 make[4]: Leaving directory `/mnt/data/build/dovecot-2.0/src/lib-storage/index' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `/mnt/data/build/dovecot-2.0/src/lib-storage' make[2]: *** [all-recursive] Error 1 make[2]: Leaving directory `/mnt/data/build/dovecot-2.0/src' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/mnt/data/build/dovecot-2.0' make: *** [all] Error 2 -- Joakim Verona

2 5

[Dovecot] deliver doesn't support !include directive, mail is bounced
by Christoph Berkemeier 30 Sep '09

30 Sep '09

Hello, dovecot deliver is used here as a LDA. When I add !include /usr/local/etc/$INCLUDE.FILE to my dovecot.conf I get this error in the maillog: relay=local, delay=0.04, delays=0.02/0/0/0.02, dsn=5.3.5, status=bounced (local configuration error. Command output: Fatal: Error in config file /usr/local/etc/dovecot.conf: deliver doesn't support !include directive /usr/local/etc/$INCLUDE.FILE contains: listen: $HOSTNAME ssl_cert_file: /etc/$FILE ssl_key_file: /etc/$FILE auth_krb5_keytab = /etc/$FILE It would be nice if this bug gets fixed or a comment add, that you can not use include, when you use deliver as your LDA. MfG Christoph dovecot -n: # 1.2.4: /usr/local/etc/dovecot.conf # OS: FreeBSD 7.2-RELEASE-p2 amd64 log_path: /var/log/dovecot.log protocols: imaps pop3s managesieve listen: $HOSTNAME ssl_cert_file: /etc/$FILE ssl_key_file: /etc/$FILE login_dir: /var/run/dovecot/login login_executable(default): /usr/local/libexec/dovecot/imap-login login_executable(imap): /usr/local/libexec/dovecot/imap-login login_executable(pop3): /usr/local/libexec/dovecot/pop3-login login_executable(managesieve): /usr/local/libexec/dovecot/managesieve-login login_processes_count: 6 login_max_processes_count: 256 verbose_proctitle: yes first_valid_uid: $NUMBER first_valid_gid: $NUMBER mail_privileged_group: mail mail_location: maildir:~/maildir mmap_disable: yes mail_nfs_storage: yes mail_nfs_index: yes mail_executable(default): /usr/local/libexec/dovecot/imap mail_executable(imap): /usr/local/libexec/dovecot/imap mail_executable(pop3): /usr/local/libexec/dovecot/pop3 mail_executable(managesieve): /usr/local/libexec/dovecot/managesieve 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 mail_plugin_dir(managesieve): /usr/local/lib/dovecot/managesieve 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): 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): namespace: type: private separator: / inbox: yes list: yes subscriptions: yes namespace: type: private separator: / prefix: mail/ location: mbox:~/mail list: yes subscriptions: yes lda: postmaster_address: postmaster@$DOMAIN log_path: info_log_path: mail_plugins: sieve quota_full_tempfail: yes sendmail_path: /usr/sbin/sendmail auth default: mechanisms: gssapi plain login username_format: %Lu krb5_keytab: /etc/$FILE gssapi_hostname: $Hostname worker_max_count: 120 passdb: driver: pam args: session=yes failure_show_msg=yes max_requests=100 dovecot userdb: driver: passwd args: blocking=yes socket: type: listen client: path: /var/run/dovecot/auth-client mode: 432 master: path: /var/run/dovecot/auth-master mode: 384 plugin: sieve: ~/.dovecot.sieve sieve_dir: ~/.sieve

2 1

[Dovecot] pam_authenticate() failed
by Martijn de Munnik 30 Sep '09

30 Sep '09

Hi List, I have a problem with auth for just one user: dovecot: Sep 30 09:56:16 Info: auth(default): new auth connection: pid=3809 dovecot: Sep 30 09:56:17 Info: auth(default): client in: AUTH 1 PLAIN service=IMAP secured lip=127.0.0.1 rip=127.0.0.1 resp=AGoucnVpc0BtZXJreC12ZXJrZXJrLm5sAGJsb2VtMDEh dovecot: Sep 30 09:56:17 Info: auth(default): pam(j.ruis(a)merkx-verkerk.nl,127.0.0.1): lookup service=dovecot dovecot: Sep 30 09:56:17 Info: auth(default): pam(j.ruis(a)merkx-verkerk.nl,127.0.0.1): pam_authenticate() failed: Authentication failed dovecot: Sep 30 09:56:18 Info: auth(default): client out: FAIL 1 user=j.ruis(a)merkx-verkerk.nl dovecot: Sep 30 09:56:18 Info: imap-login: Disconnected: user=<j.ruis(a)merkx-verkerk.nl>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured this login attempt is done via webmail but also connections with mail clients fail. other users can login successful: dovecot: Sep 30 09:58:36 Info: auth(default): client in: AUTH 1 PLAIN service=IMAP secured lip=127.0.0.1 rip=127.0.0.1 resp=AG1 hcnRpam5AeW91bmdndW5zLm5sADZtdW5zaG9l dovecot: Sep 30 09:58:36 Info: auth(default): pam(martijn(a)youngguns.nl,127.0.0.1): lookup service=dovecot dovecot: Sep 30 09:58:36 Info: auth(default): client out: OK 1 user=martijn(a)youngguns.nl dovecot: Sep 30 09:58:36 Info: auth(default): master in: REQUEST 72 4119 1 dovecot: Sep 30 09:58:36 Info: auth(default): passwd(martijn(a)youngguns.nl,127.0.0.1): lookup dovecot: Sep 30 09:58:36 Info: auth(default): master out: USER 72 martijn(a)youngguns.nl system_user=martijn(a)youngguns.nl uid=1063 gid=1062 home=/home/youngguns.nl/homes/martijn dovecot: Sep 30 09:58:36 Info: imap-login: Login: user=<martijn(a)youngguns.nl>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured dovecot: Sep 30 09:58:36 Info: IMAP(martijn(a)youngguns.nl): Loading modules from directory: /opt/csw/lib/dovecot/imap dovecot: Sep 30 09:58:36 Info: IMAP(martijn(a)youngguns.nl): Module loaded: /opt/csw/lib/dovecot/imap/lib90_antispam_plugin.so dovecot: Sep 30 09:58:36 Info: IMAP(martijn(a)youngguns.nl): Effective uid=1063, gid=1062, home=/home/youngguns.nl/homes/martijn dovecot: Sep 30 09:58:36 Info: IMAP(martijn(a)youngguns.nl): maildir: data=/home/youngguns.nl/homes/martijn/Maildir dovecot: Sep 30 09:58:36 Info: IMAP(martijn(a)youngguns.nl): maildir: root=/home/youngguns.nl/homes/martijn/Maildir, index=/home/youngguns.nl/home s/martijn/Maildir, control=, inbox= dovecot: Sep 30 09:58:36 Info: IMAP(martijn(a)youngguns.nl): Disconnected: Logged out How can I determine why pam_authenticate() failed? output of dovecot -n: # 1.0.13: /opt/csw/etc/dovecot.conf log_path: /var/log/dovecot.log info_log_path: /var/log/dovecot.info.log protocols: imap pop3 imaps pop3s listen(default): * listen(imap): * listen(pop3): *:110 ssl_cert_file: /opt/csw/ssl/secure-youngguns-nl.crt ssl_key_file: /opt/csw/ssl/secure-youngguns-nl.key disable_plaintext_auth: no verbose_ssl: yes login_dir: /opt/csw/var/run/dovecot/login login_executable(default): /opt/csw/libexec/dovecot/imap-login login_executable(imap): /opt/csw/libexec/dovecot/imap-login login_executable(pop3): /opt/csw/libexec/dovecot/pop3-login login_greeting: Welkom bij de YoungGuns postbode. mail_location: maildir:~/Maildir mail_debug: yes mail_executable(default): /opt/csw/libexec/dovecot/imap mail_executable(imap): /opt/csw/libexec/dovecot/imap mail_executable(pop3): /opt/csw/libexec/dovecot/pop3 mail_plugins(default): antispam mail_plugins(imap): antispam mail_plugins(pop3): mail_plugin_dir(default): /opt/csw/lib/dovecot/imap mail_plugin_dir(imap): /opt/csw/lib/dovecot/imap mail_plugin_dir(pop3): /opt/csw/lib/dovecot/pop3 pop3_uidl_format(default): pop3_uidl_format(imap): pop3_uidl_format(pop3): %v.%u auth default: mechanisms: login plain verbose: yes debug: yes debug_passwords: yes passdb: driver: pam userdb: driver: passwd socket: type: listen client: path: /opt/csw/var/spool/postfix/private/auth mode: 432 user: postfix group: postfix plugin: antispam_trash: Trash;trash;TRASH antispam_spam: spam antispam_mail_tmpdir: /tmp antispam_mail_sendmail: /opt/csw/bin/sa-learn antispam_mail_sendmail_args: antispam_mail_spam: --spam antispam_mail_notspam: --ham -- thanks, Martijn

2 1

[Dovecot] deliver: Fatal: setgid(114) failed with euid=8, gid=8, egid=8: Operation not permitted
by Fredriksson Turbo 30 Sep '09

30 Sep '09

I'm calling 'deliver' from Postfix and in some cases from Procmail. I set this system up more than six months ago and it's been working flawlessly until yesterday (16:52:19 local time) when it, without any apparent reason, just stopped delivering mails! Lots of checking and googling (I've forgot how exacly I setup the system :), I made 'deliver' SUID and it worked again... But it seems that all mails that was received between 16:52:19 and 11:07:52 (which was the last mail that couldn't be delivered) is lost! Is there any way to avoid mails being lost for reasons such as this? Is this a Postfix, Procmail or Dovecot thing? This system runs on a Ubuntu Intrepid: Postfix v2.5.5-1 Procmail v3.22-16ubuntu3 Dovecot v1:1.1.4-0ubuntu1.3 Thinking it over again (when double checking this mail), it might have been a automatic "de-SUID thingie or other" in Ubuntu. If memory serves me right, there used to be something like that in Debian long ago... But for whatever reason it DID happen, I'd appreciate an idea on how to avoid loosing mails if something happens to the delivery process...

3 2