January 2009 - dovecot

Re: [Dovecot] Sieve filters forwarding erratic after upgrade to 1.1.8
by Pascal Volk 22 Jan '09

22 Jan '09

On 22.01.2009 20:42 David Anderson wrote: > Upon upgrading Dovecot from 1.1.7 to 1.1.8, one of my sieve filters > (generated with avelsieve) no longer works. Please show the filter rule. > The filter is intended to redirect to another address when the header > from contains something like @example.com. However, it simply never > performs the redirection. Here it works: Jan 22 21:49:15 vh3 deliver(user(a)test.tld): Sending a forward to <user(a)example.org> with return path <<john.doe(a)example.com>> Jan 22 21:49:15 vh3 postfix/pickup[13961]: 5C3B165CF: uid=70005 from=<john.doe(a)example.com> Jan 22 21:49:15 vh3 deliver(user(a)test.tld): msgid=<6Zd0$2460.john.doe(a)example.com>: forwarded to <user(a)example.org> Jan 22 21:49:15 vh3 deliver(user(a)test.tld): msgid=<6Zd0$2460.john.doe(a)example.com>: saved mail to INBOX > Tests show that if the filter also has the "keep copy in mailbox as well > as redirecting" open on, then the copy is kept. If that option is off, > then no redirection happens and no copy is kept- i.e. the mail is > simply lost. Works also w/o explicit "keep;" > Deleting and recreating the filter makes no difference, and neither does > moving its order in the list of filters. In the same list of filters a > vacation message works. > On a second mailbox where a filter is redirecting all mail with header > precedence not equal to "list", the redirection always takes place, so > this isn't a generic problem with all redirections. I also updated > avelsieve from 1.9.7 (July 2007) to the latest SVN and this made no > difference. > > I am using the dovecot-1.1.8-0_85.el5 and dovecot-sieve-1.1.5-8.el5 RPMs > from http://atrpms.net. I'm using dovecot-sieve-1.1.6, compiled from source. Regards, Pascal -- Ubuntu is an ancient African word meaning “I can’t install Debian.” -- unknown

1 0

[Dovecot] Intermittent "certificate cannot be verified" error
by Guy 22 Jan '09

22 Jan '09

Hi guys, Not sure where to start looking for this. I've got a few users getting intermittent "certificate cannot be verified" messages when connecting through SSL to Dovecot. Connections go through haproxy to Dovecot 1.1.8 on the back end servers. I've got verbose_ssl and auth_debug enabled. All I'm seeing on the logs for the time the users reported the error is this: Jan 21 23:30:51 mink dovecot: auth(default): new auth connection: pid=28811 Jan 21 23:30:51 mink dovecot: IMAP(user1(a)domain1.net): Disconnected in IDLE bytes=73/4235 Jan 21 23:24:23 mink dovecot: auth(default): new auth connection: pid=28811 Jan 21 23:24:23 mink dovecot: imap-login: Disconnected (no auth attempts): rip=x.x.x.x, lip=x.x.x.x Jan 21 23:24:23 mink dovecot: auth(default): new auth connection: pid=28811 Jan 21 23:24:24 mink dovecot: IMAP(user2(a)domain1.net): Disconnected in IDLE bytes=89/920 Since it's so intermittent I'm not sure where to start. Since there are no real errors in the Dovecot logs I'm suspecting that haproxy is perhaps not routing every packet correctly leading to Dovecot not getting all the data needed for the connection. Are there any other possibilities I've missed? Thanks Guy root@mink:/var/log/mail# dovecot -n # 1.1.8: /etc/dovecot/dovecot.conf # OS: Linux 2.6.24-23-server x86_64 Ubuntu 8.04.1 protocols: imap imaps pop3 pop3s listen(default): *:143 listen(imap): *:143 listen(pop3): *:110 ssl_listen(default): *:993 ssl_listen(imap): *:993 ssl_listen(pop3): *:995 ssl_cert_file: /etc/ssl/certs/imapd.pem ssl_key_file: /etc/ssl/private/imapd.pem disable_plaintext_auth: no 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_process_per_connection: no login_processes_count: 5 login_max_processes_count: 256 max_mail_processes: 1024 verbose_proctitle: yes mail_location: maildir:%h/Maildir/ mail_full_filesystem_access: yes mmap_disable: yes dotlock_use_excl: no mail_nfs_storage: yes mail_nfs_index: yes lock_method: dotlock mail_executable(default): /usr/libexec/dovecot/rawlog /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/rawlog /usr/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/rawlog /usr/libexec/dovecot/pop3 mail_process_size: 128 mail_plugins(default): imap_quota quota mail_plugins(imap): imap_quota quota mail_plugins(pop3): quota mail_log_max_lines_per_sec: 30 imap_client_workarounds: outlook-idle delay-newmail pop3_uidl_format: %08Xv%08Xu pop3_client_workarounds: outlook-no-nuls oe-ns-eoh namespace: type: private separator: / inbox: yes list: yes subscriptions: yes namespace: type: private separator: / prefix: mail/ location: maildir:%h/Maildir/ hidden: yes subscriptions: yes auth default: cache_size: 2048 cache_ttl: 300 cache_negative_ttl: 1 username_chars: abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@' master_user_separator: * debug: yes worker_max_count: 5 passdb: driver: passwd-file args: /etc/dovecot/dovecot-master.pwd master: yes passdb: driver: sql args: /etc/dovecot/dovecot-mysql.conf userdb: driver: sql args: /etc/dovecot/dovecot-mysql.conf plugin: quota: maildir quota_rule: *:storage=100M quota_rule2: Trash:ignore -- Don't just do something...sit there!

2 1

[Dovecot] imap-login: memory corruption
by Ralf Hildebrandt 22 Jan '09

22 Jan '09

>From my logs (dovecot-1.1.8) Jan 14 08:42:52 postamt dovecot: imap-login: *** glibc detected *** imap-login: malloc(): memory corruption: 0x0844e778 *** Jan 14 08:42:52 postamt dovecot: child 15380 (login) killed with signal 6 Jan 14 10:06:42 postamt dovecot: Panic: imap-login: file ioloop.c: line 71 (io_remove_full): assertion failed: (io->callback != NULL) Jan 14 10:06:42 postamt dovecot: child 15389 (login) killed with signal 6 Jan 14 10:53:15 postamt dovecot: Panic: imap-login: file ioloop.c: line 71 (io_remove_full): assertion failed: (io->callback != NULL) Jan 14 10:53:15 postamt dovecot: child 15367 (login) killed with signal 6 Jan 14 12:05:20 postamt dovecot: imap-login: *** glibc detected *** imap-login: malloc(): memory corruption: 0x0882fe40 *** Jan 14 12:05:20 postamt dovecot: child 2263 (login) killed with signal 6 Jan 14 12:35:13 postamt dovecot: imap-login: *** glibc detected *** imap-login: free(): invalid pointer: 0x08a46620 *** Jan 14 12:35:13 postamt dovecot: child 4169 (login) killed with signal 6 Jan 14 13:08:27 postamt dovecot: imap-login: *** glibc detected *** imap-login: free(): invalid pointer: 0x08f5b5b0 *** Jan 14 13:08:27 postamt dovecot: child 6316 (login) killed with signal 6 Jan 14 13:18:00 postamt dovecot: imap-login: *** glibc detected *** imap-login: malloc(): memory corruption: 0x085f3d48 *** Jan 14 13:18:00 postamt dovecot: child 15378 (login) killed with signal 6 -- Ralf Hildebrandt (Ralf.Hildebrandt(a)charite.de) snickebo(a)charite.de Postfix - Einrichtung, Betrieb und Wartung Tel. +49 (0)30-450 570-155 http://www.arschkrebs.de IMPORTANT - ANTI-DISCLAIMER - This email is not and cannot, by its nature, be confidential. En route from me to you, it will pass across the public Internet, easily readable by any number of system administrators along the way. If you have received this message by mistake, it would be ridiculous for me to tell you not to read it or copy to anyone else, because, let's face it, if it's a message revealing confidential information or that could embarrass me intensely, that's precisely what you'll do. Who wouldn't? Likewise, it is superfluous for me to claim copyright in the contents, because I own that anyway, even if you print out a hard copy or disseminate this message all over the known universe. I don't know why so many corporate mail servers feel impelled to attach a disclaimer to the bottom of every email message saying otherwise. If you don't know either, why not email your corporate lawyers and system administrators and ask them why they insist on contributing so much to the waste of bandwidth? To say nothing of making the presence of your mail on public discussions or mailinglists of explicitly contratictory nature. May as well just delete it, eh? Oh, and this message is probably plagued with viruses as well.

2 25

[Dovecot] Courier->dovecot migration script
by Warren Baker 22 Jan '09

22 Jan '09

HI All, We have the latest Dovecot 1.1.6 running and I need to migrate some POP3 users over from Courier to Dovecot and would need to convert the courierpop3dsizelist to maintain the UIDs. I just need to confirm that the script (http://www.dovecot.org/tools/courier-dovecot-migrate.pl) only works for Dovecot v1.0 and not for v1.1? As the dovecout-uidlist file that is created (by the script) is not in the same format as dovecot-uidlist file that is created by the 1.1.6 server. Thanks, Warren

5 8

[Dovecot] Probleme decoding attachements with Apple mail client
by Frank Bonnet 22 Jan '09

22 Jan '09

Hello folks An Apple user here have troubles between Dovecot and its Apple mail client that presents ALL attachements inline inside emails instead of "Attachements" the problem occurs only when using IMAP , when using POP3 attachements appears as they are supposed to do. I would like to know if other Apple users in this list has experienced and solved that problem , the machine in running MacOS 10.5 Thanks a lot. -- Cordialement Frank Bonnet ESIEE Paris

1 0

[Dovecot] dovecot bulletins?
by Maciej Uhlig 21 Jan '09

21 Jan '09

As a long term user of qpopper with bulletins, I'd like to know if the bulletin feature is planned for dovecot? I really miss bulletins :-), this is very convenient way of providing information to users. Best regards, MU

6 11

[Dovecot] docecot managesieve global filter, service name
by Wolfgang.Friebel＠desy.de 21 Jan '09

21 Jan '09

I do have two questions related to the managesieve setup in dovecot 1) I did setup a global sieve filter, that is invoked if a user has no other sieve filter. If a user installs a sieve filter and activates it (PUTSCRIPT, SETACTIVE) then the sieve filter gets compiled (.sievec) and deliver does use it. If I want to deactivate the filter (SETACTIVE "") only the symlink (to the .sieve script) is removed, the .sievec file remains intact. On the other hand the dovecot documentation reads (http://wiki.dovecot.org/LDA/Sieve) To stop using sieve, both the .sieve source file and the compiled .sievec file must be deleted How can I let a user switch between the globally installed sieve filter and an own filter. Activation seems to be ok, but deactivation would not result in the switch back to the global filter if I believe the docs. 2) To use the SASL authentication with managesieve the name of the service has to be given. In the managesieve RFC http://tools.ietf.org/html/draft-ietf-sieve-managesieve-09 I can read (page13): The service name specified by this protocol's profile of SASL is "sieve". On the other hand I can find in managesieve-0.10.4 in client-authenticate.c #define MANAGESIEVE_SERVICE_NAME "managesieve" The name is important for the Kerberos5 auth I am doing, as I have to provide a service key for managesieve.hostname@REALM instead of sieve.hostname@REALM. Currently I have adapted my auth to the "managesieve" service name but maybe that should be changed. My Installation: dovecot 1.1.8 patched for dovecot-1.1-managesieve-0.10.4 Authentication using SASL (GSSAPI), contained in the perl Module Net::ManageSieve on CPAN. -- Wolfgang Friebel Deutsches Elektronen-Synchrotron DESY Phone/Fax: +49 33762 77372/216 Platanenallee 6 Mail: Wolfgang.Friebel AT desy.de D-15738 Zeuthen Germany

2 1

[Dovecot] dovecot 1.1.8 compile error
by CJ Keist 21 Jan '09

21 Jan '09

I'm trying to compile 1.1.8 with dovecot-1-1-989789b2afd8 patches applied on Solaris 10 sparc using gcc 2.95.3 and also tried version 3.4.3. This is error I'm getting: gcc -DHAVE_CONFIG_H -I. -I../.. -I../../src/lib -I../../src/lib-auth -DPKG_RUNDIR=\""/userM/mail-services/dovecot/var/run/dovecot"\" -DSBINDIR=\""/userM/mail-services/dovecot/sbin"\" -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -I/usr/sfw/include -c ssl-proxy-openssl.c In file included from ssl-proxy-openssl.c:21: /usr/sfw/include/openssl/ssl.h:172: warning: ignoring pragma: "@(#)ssl.h 1.4 05/10/11 SMI In file included from /usr/sfw/include/openssl/ssl3.h:120, from /usr/sfw/include/openssl/ssl.h:951, from ssl-proxy-openssl.c:21: /usr/sfw/include/openssl/ssl.h:172: warning: ignoring pragma: "@(#)ssl.h 1.4 05/10/11 SMI ssl-proxy-openssl.c: In function `ssl_params_corrupted': ssl-proxy-openssl.c:85: `PKG_STATEDIR' undeclared (first use in this function) ssl-proxy-openssl.c:85: (Each undeclared identifier is reported only once ssl-proxy-openssl.c:85: for each function it appears in.) ssl-proxy-openssl.c: In function `ssl_info_callback': ssl-proxy-openssl.c:658: warning: passing arg 1 of `SSL_get_ex_data' discards qualifiers from pointer target type *** Error code 1 make: Fatal error: Command failed for target `ssl-proxy-openssl.o' Current working directory /userM/src/dovecot-1.1.8/src/login-common *** Error code 1 The following command caused the error: failcom='exit 1'; \ for f in x $MAKEFLAGS; do \ case $f in \ *=* | --[!k]*);; \ *k*) failcom='fail=yes';; \ esac; \ done; \ dot_seen=no; \ target=`echo all-recursive | sed s/-recursive//`; \ list='lib lib-dict lib-sql lib-ntlm lib-otp lib-settings lib-charset lib-mail lib-imap lib-index lib-storage lib-auth auth dict master login-common imap-login imap pop3-login pop3 deliver tests util plugins'; for subdir in $list; do \ echo "Making $target in $subdir"; \ if test "$subdir" = "."; then \ dot_seen=yes; \ local_target="$target-am"; \ else \ local_target="$target"; \ fi; \ (cd $subdir && make $local_target) \ || eval $failcom; \ done; \ if test "$dot_seen" = "no"; then \ make "$target-am" || exit 1; \ fi; test -z "$fail" make: Fatal error: Command failed for target `all-recursive' Current working directory /userM/src/dovecot-1.1.8/src *** Error code 1 The following command caused the error: failcom='exit 1'; \ for f in x $MAKEFLAGS; do \ case $f in \ *=* | --[!k]*);; \ *k*) failcom='fail=yes';; \ esac; \ done; \ dot_seen=no; \ target=`echo all-recursive | sed s/-recursive//`; \ list='src doc'; for subdir in $list; do \ echo "Making $target in $subdir"; \ if test "$subdir" = "."; then \ dot_seen=yes; \ local_target="$target-am"; \ else \ local_target="$target"; \ fi; \ (cd $subdir && make $local_target) \ || eval $failcom; \ done; \ if test "$dot_seen" = "no"; then \ make "$target-am" || exit 1; \ fi; test -z "$fail" make: Fatal error: Command failed for target `all-recursive' Current working directory /userM/src/dovecot-1.1.8 *** Error code 1 make: Fatal error: Command failed for target `all' Does anyone have work around for this on Solaris 10? -- C. J. Keist Email: cj.keist(a)colostate.edu UNIX/Network Manager Phone: 970-491-0630 Engineering Network Services Fax: 970-491-5569 College of Engineering, CSU Ft. Collins, CO 80523-1301 All I want is a chance to prove 'Money can't buy happiness'

2 4

[Dovecot] How to interpret quota log entries?
by Pascal Volk 21 Jan '09

21 Jan '09

Hi, I've configured a global quota rule, with low limits for testing purpose: quota_rule = *:storage=10M:messages=10 Why is the percentage value always 0? What does 'enforcing' mean in this context? Is it not only relevant if one uses fs-quota? Jan 21 17:54:44 vh3 dovecot: IMAP(user(a)test.tld): Quota root: name=user backend=dict args=:proxy::quotadict Jan 21 17:54:44 vh3 dovecot: IMAP(user(a)test.tld): dict quota: user=user(a)test.tld, uri=proxy::quotadict, enforcing=0 Jan 21 17:54:44 vh3 dovecot: IMAP(user(a)test.tld): Quota rule: root=user mailbox=* bytes=10485760 (0%) messages=10 (0%) Jan 21 17:54:49 vh3 deliver(user(a)test.tld): Quota root: name=user backend=dict args=:proxy::quotadict Jan 21 17:54:49 vh3 deliver(user(a)test.tld): dict quota: user=user(a)test.tld, uri=proxy::quotadict, enforcing=0 Jan 21 17:54:49 vh3 deliver(user(a)test.tld): Quota rule: root=user mailbox=* bytes=10485760 (0%) messages=10 (0%) The current quota usage for user(a)test.tld: mailsys=# SELECT * FROM quota WHERE username = 'user(a)test.tld'; username | path | current ---------------+----------------+--------- user(a)test.tld | quota/storage | 9977225 user(a)test.tld | quota/messages | 4 # 1.1.9: /usr/local/etc/dovecot.conf # OS: OpenBSD 4.2 i386 login_dir: /usr/local/var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login login_user: _dovecot first_valid_uid: 70000 first_valid_gid: 70000 mail_location: maildir:~/Maildir mail_debug: yes mail_plugins: quota imap_quota auth default: mechanisms: plain login cram-md5 user: nobody passdb: driver: sql args: /usr/local/etc/dovecot-sql.conf userdb: driver: sql args: /usr/local/etc/dovecot-sql.conf socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: _postfix group: _postfix master: path: /usr/local/var/run/dovecot/auth-master mode: 384 plugin: quota: dict:user::proxy::quotadict quota_rule: *:storage=10M:messages=10 mail_debug: yes dict: quotadict: pgsql:/usr/local/etc/dovecot-dict-quota.conf mail_debug: yes Regards, Pascal -- Ubuntu is an ancient African word meaning “I can’t install Debian.” -- unknown

2 1

[Dovecot] dovecot and signal SIGUSR1
by maximatt 21 Jan '09

21 Jan '09

hi.. i want to know how is defined signal "SIGUSR1" for dovecot. i want to know what dovecot do when the comand kill was executed in "Rotating logs" in http://wiki.dovecot.org/Logging.. thanks in advance!! -- Salu2 ;)

1 1