- dovecot - dovecot.org

Re: [Dovecot] While searching: Assertion failed (offset > = ctx- >input->v_offset)
by Timo Sirainen 20 Jun '08

20 Jun '08

On Fri, 2008-06-20 at 09:42 +0200, Diego Liziero wrote: > On 6/20/08, Patrick Nagel <patrick.nagel(a)star-group.net> wrote: > > Hi, > > [..] > > > > Now I get this with 1.1.rc10: > > > > Jun 20 11:53:53 stshamail1 dovecot: Panic: IMAP(username): file > > message-parser.c: line 770 (message_parser_parse_next_block): assertion > > failed: (ctx->input->eof || ctx->input->closed || ctx->input->stream_errno != 0) > > [..] > > > > Patrick. > > Timo, > here is an anonymized mbox file that causes it at every body search > (tested with rc12). Did you test it without index files? I couldn't reproduce the crash. Do you use 32bit or 64bit Dovecot?

3 4

[Dovecot] v1.1.rc12 released
by Timo Sirainen 20 Jun '08

20 Jun '08

http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc12.tar.gz http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc12.tar.gz.sig Sorry, one more RC because of the mbox+quota bug. v1.1.0 still planned for tomorrow. - mbox: Don't give "Can't find next message offset" warnings when plugin (e.g. quota) accesses the message being saved. - deliver: Settings inside protocol imap {} weren't ignored.

5 5

[Dovecot] While searching: Assertion failed (offset >= ctx->input->v_offset)
by Patrick Nagel 20 Jun '08

20 Jun '08

Hi, while a user is searching through his (1.2 GB, >150000) mails, I get a lot of these messages in the log, and the search (with Thunderbird) doesn't finish: Jun 19 14:35:45 stshamail1 dovecot: Panic: IMAP(username): file message-parser.c: line 620 (preparsed_parse_body_init): assertion failed: (offset >= ctx->input->v_offset) Jun 19 14:35:45 stshamail1 dovecot: IMAP(username): Raw backtrace: imap [0x80ce9f4] -> imap [0x80ce60c] -> imap [0x80c83f4] -> imap(message_parser_parse_next_block+0x1d) [0x80c802d] -> imap(message_search_msg+0x5f) [0x80c9a7f] -> imap [0x8098e0b] -> imap [0x809e42b] -> imap(mail_search_args_foreach+0x40) [0x809e540] -> imap(index_storage_search_next_nonblock+0x256) [0x80989f6] -> imap [0x805dc96] -> imap [0x805e0d6] -> imap(io_loop_handle_timeouts+0x80) [0x80d59c0] -> imap(io_loop_handler_run+0x82) [0x80d6522] -> imap(io_loop_run+0x28) [0x80d5828] -> imap(main+0x4ac) [0x806809c] -> /lib/libc.so.6(__libc_start_main+0xdc) [0x4003adec] -> imap [0x805a021] Jun 19 14:35:45 stshamail1 dovecot: child 30070 (imap) killed with signal 6 What's wrong here? How to proceed with debugging? Thanks, Patrick. -- STAR Software (Shanghai) Co., Ltd. http://www.star-group.net/ Phone: +86 (21) 3462 7688 x 826 Fax: +86 (21) 3462 7779 PGP key: https://stshacom1.star-china.net/keys/patrick_nagel.asc Fingerprint: E09A D65E 855F B334 E5C3 5386 EF23 20FC E883 A005

2 3

[Dovecot] v1.1.rc11 released
by Timo Sirainen 20 Jun '08

20 Jun '08

http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc11.tar.gz http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc11.tar.gz.sig This is the final v1.1 RC. Tomorrow I'll change only the version number, update the documentation and call it v1.1.0. But please test this anyway to make sure I didn't happen to break anything since rc10 :) - dovecot-uidlist is now recreated if it results in file shrinking over 25%. - Some other minor fixes

5 8

[Dovecot] Compile failure on Dovecot 1.1-rc12
by Erinn Looney-Triggs 20 Jun '08

20 Jun '08

I am getting this failure when trying to compile dovecot on Sparc Solaris 8: make[4]: Entering directory `/home/systems/looneytr/dovecot-1.1.rc12/src/lib' source='str-find.c' object='str-find.o' libtool=no \ DEPDIR=.deps depmode=gcc /bin/bash ../../depcomp \ gcc -DHAVE_CONFIG_H -I. -I../.. -I/usr/local/openssl/include -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -c str-find.c str-find.c:17: field `goodtab' has incomplete type make[4]: *** [str-find.o] Error 1 This problem has occurred on two separate systems. Have you run into this issue, or are you aware of this issue? Dovecot 1.0.14 builds just fine. Thanks, -Erinn

3 2

Re: [Dovecot] Compile failure on Dovecot 1.1-rc12
by Chris Wakelin 20 Jun '08

20 Jun '08

Erinn Looney-Triggs wrote: > Chris Wakelin wrote: > >> What version of gcc? What configure options? I had no problems with gcc >> 3.3.2 (well, a still a few compiler warnings; see >> http://www.dovecot.org/list/dovecot/2008-June/031350.html) >> >> Chris >> > > Hello, > > gcc --version 2.95.3 > > Had to set LDFLAGS and CPPFLAGS to include the openssl in > /usr/local/openssl. > > ./configure --prefix=/usr/local/dovecot --with-ssl=openssl > > I am guessing that it probably has something to do with the old version > of gcc. > > Thanks for your time, > -Erinn > No, *my* version is 'old' - yours is prehistoric :) I've just checked, and yes, gcc 2.95.2 breaks in exactly the same way for me! 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

1 0

[Dovecot] debugging dovecot and sieve
by Frank Church 19 Jun '08

19 Jun '08

I have install dovecot and sieve and it doesn't appear to be working. Below is my dovecot.conf Are there some debugging settings I can use to test if dovecot is linking with sieve properly. Nothing appears to show up in the logs start dovecot.conf ======================= cat /usr/local/etc/dovecot.conf base_dir = /var/run/dovecot/ auth_verbose=yes auth_debug=yes mail_debug=yes auth_debug_passwords=yes disable_plaintext_auth=no protocols = imap imaps pop3 pop3s protocol imap { mail_plugins = quota imap_quota imap_client_workarounds = outlook-idle delay-newmail } protocol pop3 { mail_plugins = quota pop3_client_workarounds = outlook-no-nuls oe-ns-eoh pop3_uidl_format = %08Xu%08Xx } protocol lda { postmaster_address = postmaster(a)abc.meripol.net mail_plugins = quota cmusieve log_path = /var/log/vmail/dovecot-deliver.log info_log_path = /var/log/vmail/dovecot-deliver.log } ## ## Logging ## # Log file to use for error messages, instead of sending them to syslog. # /dev/stderr can be used to log into stderr. log_path = /var/log/dovecot/error_log # Log file to use for informational and debug messages. # Default is the same as log_path. info_log_path = /var/log/dovecot/general_log # Prefix for each line written to log file. % codes are in strftime(3) # format. #log_timestamp = "%b %d %H:%M:%S " # Syslog facility to use if you're logging to syslog. Usually if you don't # want to use "mail", you'll use local0..local7. Also other standard # facilities are supported. #syslog_facility = mail #ssl_listen = ssl_disable = no ssl_cert_file = /etc/ssl/certs/dovecot.pem ssl_key_file = /etc/ssl/private/dovecot.pem #ssl_key_password = #ssl_ca_file = #ssl_verify_client_cert = no #ssl_parameters_regenerate = 168 # SSL ciphers to use #ssl_cipher_list = ALL:!LOW # Show protocol level SSL errors. #verbose_ssl = no #ssl_ca_file = /etc/pki/dovecot/certs/ca-bundle.crt mail_location = maildir:/var/vmail/%d/%u mail_extra_groups = mail first_valid_uid = 601 last_valid_uid = 601 maildir_copy_with_hardlinks = yes auth default { mechanisms = plain passdb sql { args = /etc/dovecot/sql.conf } userdb sql { args = /etc/dovecot/sql.conf } userdb prefetch { } user = nobody socket listen { master { # path = /var/run/dovecot/auth-master path = /usr/local/var/run/dovecot/auth-master mode = 0660 user = vmail group = mail } client { path = /var/spool/postfix/private/auth mode = 0660 user = postfix group = mail } } } dict { } plugin { quota = maildir:storage=10240:messages=1000 acl = vfile:/etc/dovecot/acls trash = /etc/dovecot/trash.conf sieve = /var/vmail/%d/%u/.dovecot.sieve } ===================== end dovecot.conf Thanks vfclists

2 1

[Dovecot] Can't find next message offset
by Dean Brooks 19 Jun '08

19 Jun '08

Hi, I am getting a lot of warnings since upgrading to 1.1rc10 (from rc4): mbox /home2/seta/Mail/Sent: Can't find next message offset for uid=12 Almost always, it is the Sent or Trash folders that are giving these. Users aren't experiencing any problems, but the errors continue to come. Is this something I should be concerned about? Here is output of "dovecot -n": # 1.1.rc10: /usr/local/dovecot/etc/dovecot.conf base_dir: /var/run/dovecot/ protocols: imap login_dir: /var/run/dovecot//login login_executable: /usr/local/dovecot/libexec/dovecot/imap-login login_user: daemon mail_max_userip_connections: 5 first_valid_uid: 100 last_valid_uid: 128000 mail_privileged_group: mail mail_location: mbox:~/Mail:INBOX=/var/mail/%u:INDEX=/var/indexes/local/%u mail_nfs_storage: yes mbox_write_locks: fcntl mbox_lock_timeout: 180 mbox_lazy_writes: no mail_plugins: quota imap_quota namespace: type: private separator: / inbox: yes list: yes subscriptions: yes namespace: type: private separator: / prefix: Mail/ hidden: yes subscriptions: yes auth default: mechanisms: plain login failure_delay: 5 debug: yes passdb: driver: shadow userdb: driver: passwd plugin: quota: fs -- Dean Brooks dean(a)iglou.com

2 2

[Dovecot] Migrate to 1.1 from 1.0.14
by Nicolas Letellier 19 Jun '08

19 Jun '08

Hello. I see dovecot 1.1 will be release very soon. I'm thinking about a migration from my 1.0.14. The migration job will be hard/long? I see in http://wiki.dovecot.org/Upgrading/1.1 that dovecot-uidlist file are in a new format. It will be problem for Courier (pop/imap) upgrades? (today, I often upgrade old mailboxes in Courier to my Dovecot server). Best regards, -- - Nicolas.

2 1

[Dovecot] Using checkpassword to block ips?
by Larry Ludwig 19 Jun '08

19 Jun '08

Hi new to the list, but we are a long time user of Dovecot via DirectAdmin control panel. We, like everyone else, are seeing an increase in dictionary attacks of POP/IMAP. We want to block them. I've searched the mailing list and found a few recommended fail2ban, which really won't work for our case. We need to do this over many machines and not one or two. We also like to gather info at the network wide level. Hackers know about attacking specific server/ips too often and we've seen much more distributed attacks that go under the radar of one server monitoring setup. We've designed our own system and use a local RBL to distribute the blocked IPs. For ftp and ssh attacks it's worked very well. We would like to use the RBL to do the same with dovecot. >From my research it appears the best way to do this (and only currently) is with the checkpassword option. I haven't gotten it to work yet. We have: passdb checkpassword { args = /usr/local/bin/checkpassword deny = yes } As the first auth.. This should reject the connection if the IP matches. checkpassword can see TCPREMOTEIP enviornmental variable. In the checkpassword script we have: #!/usr/bin/perl sub read_uinfo { my($user,$passwd,$apop_ts); open X,"<&=3" or exit 111; $_ = <X>; # ugly; should use sysread instead ($user,$passwd,$apop_ts) = /^(.*)\0(.*)\0(.*)\0/; while (<X>) {}; close X; return ($user,$passwd,$apop_ts); } ($user,$passwd,$apop_ts)=$debug?(shift,shift,shift):read_uinfo; $ipaddr=$ENV{TCPREMOTEIP}; $result=system("/usr/sbin/checkdnsbl $ipaddr"); if ( $result == 0) { @ENV{"SHELL","USER","HOME"} = ($shell,$user,$home); exit 0; } else { exit 1; } My questions are as follows: - Can the deny = yes be used with checkpassword? - What am I doing wrong with the script? It should reject only the connections that are in the RBL. It blocks all -L -- Larry Ludwig Empowering Media 1-866-792-0489 x600 Managed and Unmanaged Xen VPSes http://www.hostcube.com/

2 2