- dovecot - dovecot.org

[Dovecot] another assertion failure in current 1.1 hg (1.1.3 was working fine) - file message-address.c: line 43 (parse_local_part): assertion failed: (ctx->parser.data != ctx->parser.end)
by Diego Liziero 17 Sep '08

17 Sep '08

file message-address.c: line 43 (parse_local_part): assertion failed: (ctx->parser.data != ctx->parser.end) #0 0x001b3402 in __kernel_vsyscall () No symbol table info available. #1 0x0043ed20 in raise () from /lib/libc.so.6 No symbol table info available. #2 0x00440631 in abort () from /lib/libc.so.6 No symbol table info available. #3 0x080f6968 in default_fatal_finish (type=LOG_TYPE_PANIC, status=0) at failures.c:150 backtrace = 0x90e9ed8 "/usr/libexec/dovecot/imap [0x80f6946] -> /usr/libexec/dovecot/imap [0x80f7207] -> /usr/libexec/dovecot/imap(i_fatal+0) [0x80f6ac0] -> /usr/libexec/dovecot/imap [0x80eaee7] -> /usr/. #4 0x080f7207 in i_internal_fatal_handler (type=LOG_TYPE_PANIC, status=0, fmt=0x8122bf0 "file %s: line %d (%s): assertion failed: (%s)", args=0xbfe92c54 "ï¿½+\022\b+") at failures.c:430 No locals. #5 0x080f6ac0 in i_panic (format=0x8122bf0 "file %s: line %d (%s): assertion failed: (%s)") at failures.c:197 args = 0xbfe92c54 "ï¿½+\022\b+" #6 0x080eaee7 in parse_local_part (ctx=0xbfe92d78) at message-address.c:43 ret = 0 __PRETTY_FUNCTION__ = "parse_local_part" #7 0x080eb373 in parse_addr_spec (ctx=0xbfe92d78) at message-address.c:163 ret = 24 ret2 = -1 #8 0x080eb49d in parse_mailbox (ctx=0xbfe92d78) at message-address.c:200 start = (const unsigned char *) 0x90fba9f "" ret = -1 #9 0x080eb503 in parse_mailbox_list (ctx=0xbfe92d78) at message-address.c:214 ret = 151951304 #10 0x080eb5c9 in parse_group (ctx=0xbfe92d78) at message-address.c:246 ret = 152025736 #11 0x080eb64c in parse_address (ctx=0xbfe92d78) at message-address.c:268 start = (const unsigned char *) 0x90fba88 "undisclosed-recipients:" ret = 151951000 #12 0x080eb68b in parse_address_list (ctx=0xbfe92d78, max_addresses=4294967294) at message-address.c:283 ret = 0 #13 0x080eb78f in message_address_parse_real (pool=0x90e9500, data=0x90fba88 "undisclosed-recipients:", size=23, max_addresses=4294967295, fill_missing=true) at message-address.c:320 ctx = {pool = 0x90e9500, parser = {data = 0x90fba9f "", end = 0x90fba9f "", last_comment = 0x90e9570}, first_addr = 0x90e97c8, last_addr = 0x90e97c8, addr = {next = 0x0, name = 0x0, route = 0x0, mailbox = 0x0, domain = 0x0, invalid_syntax = false}, str = 0x90e9698, fill_missing = true} ret = 1 #14 0x080eb7e0 in message_address_parse (pool=0x90e9500, data=0x90fba88 "undisclosed-recipients:", size=23, max_addresses=4294967295, fill_missing=true) at message-address.c:331 addr = (struct message_address *) 0x90e9500 #15 0x080ac097 in search_header_arg (arg=0x90ef6c0, ctx=0xbfe92f80) at index-search.c:424 addr = (struct message_address *) 0x90ff31c str = (string_t *) 0x17 _data_stack_cur_id = 5 msg_search_ctx = (struct message_search_context *) 0x91032f0 block = {part = 0x0, hdr = 0xbfe92e38, data = 0x0, size = 0} hdr = {name = 0x811a0f0 "", name_len = 0, value = 0x90fba88 "undisclosed-recipients:", value_len = 23, full_value = 0x90fba88 "undisclosed-recipients:", full_value_len = 23, middle = 0x90fdd53 ": ", middle_len = 0, name_offset = 0, full_value_offset = 4, continues = 0, continued = 0, eoh = 0, no_newline = 0, crlf_newline = 0, use_full_value = 0} ret = 0 #16 0x080b537a in search_arg_foreach (arg=0x90ef6c0, callback=0x80abe09 <search_header_arg>, context=0xbfe92f80) at mail-search.c:85 subarg = (struct mail_search_arg *) 0x0 __PRETTY_FUNCTION__ = "search_arg_foreach" #17 0x080b53a4 in mail_search_args_foreach (args=0x90ef6c0, callback=0x80abe09 <search_header_arg>, context=0xbfe92f80) at mail-search.c:98 result = 1 #18 0x080ac2f7 in search_header (hdr=0x90fec80, ctx=0xbfe92f80) at index-search.c:491 No locals. #19 0x080ed97e in message_parse_header (input=0x90fa8f8, hdr_size=0x0, flags=MESSAGE_HEADER_PARSER_FLAG_CLEAN_ONELINE, callback=0x80ac22f <search_header>, context=0xbfe92f80) at message-header-parser.c:389 hdr_ctx = (struct message_header_parser_ctx *) 0x90fec80 hdr = (struct message_header_line *) 0x90fec80 ret = 1 __PRETTY_FUNCTION__ = "message_parse_header" #20 0x080ac691 in search_arg_match_text (args=0x90ef678, ctx=0x90fb7a8) at index-search.c:580 hdr_ctx = {index_context = 0x90fb7a8, args = 0x90ef678, hdr = 0x90fec80, parse_headers = 0, custom_header = 1, threading = 0} input = (struct istream *) 0x90fa8f8 headers_ctx = (struct mailbox_header_lookup_ctx *) 0x90fb068 headers = (const char * const *) 0x90e9458 have_headers = true have_body = false __PRETTY_FUNCTION__ = "search_arg_match_text" #21 0x080ad3e1 in search_match_next (ctx=0x90fb7a8) at index-search.c:967 arg = (struct mail_search_arg *) 0x90fb7a8 ret = -1 #22 0x080ad703 in index_storage_search_next_nonblock (_ctx=0x90fb7a8, mail=0x90f8f68, tryagain_r=0xbfe93083) at index-search.c:1042 _data_stack_cur_id = 4 ctx = (struct index_search_context *) 0x90fb7a8 box = (struct mailbox *) 0x90f7c80 count = 6 ret = 1 #23 0x080b6e1d in mailbox_search_next_nonblock (ctx=0x90fb7a8, mail=0x90f8f68, tryagain_r=0xbfe93083) at mail-storage.c:653 No locals. #24 0x0805f60e in cmd_search_more (cmd=0x90ef600) at cmd-search.c:83 ctx = (struct imap_search_context *) 0x90ef738 end_time = {tv_sec = 151975096, tv_usec = 1} tryagain = false ret = 135224202 #25 0x0805f78e in cmd_search_more_callback (cmd=0x90ef600) at cmd-search.c:132 client = (struct client *) 0x90ef368 finished = false #26 0x08100310 in io_loop_handle_timeouts_real (ioloop=0x90ed9b0) at ioloop.c:298 timeout = (struct timeout *) 0x90fecd8 item = (struct priorityq_item *) 0x90fecd8 tv = {tv_sec = 0, tv_usec = 0} tv_call = {tv_sec = 1221553327, tv_usec = 767240} t_id = 3 #27 0x0810036a in io_loop_handle_timeouts (ioloop=0x90ed9b0) at ioloop.c:309 _data_stack_cur_id = 2 #28 0x0810102c in io_loop_handler_run (ioloop=0x90ed9b0) at ioloop-epoll.c:175 ctx = (struct ioloop_handler_context *) 0x90edaa8 events = (struct epoll_event *) 0x90edae8 event = (const struct epoll_event *) 0x90edae8 list = (struct io_list *) 0x90ef568 io = (struct io_file *) 0x0 tv = {tv_sec = 0, tv_usec = 0} events_count = 4 t_id = 2 msecs = 0 ret = 0 i = 0 j = 3 call = true #29 0x081003ac in io_loop_run (ioloop=0x90ed9b0) at ioloop.c:320 No locals. #30 0x0806debd in main (argc=1, argv=0xbfe93234, envp=0xbfe9323c) at main.c:293 No locals.

2 1

[Dovecot] Expire with space in mailbox name
by Jeff Savage 17 Sep '08

17 Sep '08

Hello all, I'm running Dovecot 1.1.3 and trying to make use of the expire plugin on my mbox-based mailboxes. Expire seems to be populating the database when it comes to the trash folder, but I'm having issues with a spam folder (unfortunately) named "Junk E-mail". I've tried quotes and a backslash to account for the space, but it's not happening. Can anyone tell me how I would account for a folder like this? Neither of the following work, and I haven't found an example that addresses this. expire = Trash 7 "Junk E-mail" 7 expire = Trash 7 Junk\ E-mail 7 Thanks in advance.

2 1

[Dovecot] Mail being delivered to mbox instead of Maildir
by Sean Smitz 17 Sep '08

17 Sep '08

I thought I had Dovecot configured to use Maildir instead of mbox, but apparently it is still using mbox. Excerpt from dovecot.conf: mail_location = maildir:~/Maildir Excerpt from sendmail.mc: MAILER(dovecot)dnl dovecot.m4: ######################################## ### DOVECOT Mailer Specification ### ######################################## Mdovecot, P=/usr/local/libexec/dovecot/deliver, F=DFMPhnu9, S=EnvFromSMTP/HdrFromSMTP, R=EnvToSMTP/HdrFromSMTP, T=DNS/RFC822/X-Unix, A=deliver -d $u Thank you Sean Smitz

3 2

[Dovecot] Any sense of whether or not we're close to a V1.1.4 release?
by Stewart Dean 17 Sep '08

17 Sep '08

Am about to make a push to go from V1.0 to V1.1 and wondered. run a simple installation with PAM/passwd authent and mbox folders, no plugins. -- ==== Stewart Dean, Unix System Admin, Henderson Computer Resources Center of Bard College, Annandale-on-Hudson, New York 12504 sdean(a)bard.edu voice: 845-758-7475, fax: 845-758-7035

2 1

Re: [Dovecot] Mail being delivered to mbox instead of Maildir
by Sean Smitz 17 Sep '08

17 Sep '08

Output of dovecot -n: # 1.0.7: /etc/dovecot.conf protocols: imaps ssl_cert_file: /etc/pki/dovecot/certs/mailserv1.cer ssl_key_file: /etc/pki/dovecot/private/mailserv1.pem login_dir: /var/run/dovecot/login login_executable: /usr/libexec/dovecot/imap-login mail_access_groups: mail mail_location: maildir:~/Maildir mail_full_filesystem_access: yes maildir_copy_with_hardlinks: yes auth default: passdb: driver: pam args: cache_key=%u%s dovecot userdb: driver: passwd

2 1

Re: [Dovecot] Connecting to dovecot
by Grant Lowe 17 Sep '08

17 Sep '08

So should I comment out the "mail_location = /var/mail/%u" line? ----- Original Message ---- From: Scott Silva <ssilva(a)sgvwater.com> To: dovecot(a)dovecot.org Sent: Wednesday, September 17, 2008 7:53:43 AM Subject: Re: [Dovecot] Connecting to dovecot on 9-17-2008 7:48 AM Scott Silva spake the following: > on 9-17-2008 7:25 AM Grant Lowe spake the following: >> Hi All, >> >> I've got a brand new dovecot installation. I'm new to dovecot, so >> please be gentle :-) >> >> Anyway, >> I'm getting some errors when I try to connect to dovecot. I've tried >> searching the web and haven't been able to find a lot of information. >> Here's the config info: >> >> # dovecot --version >> 1.1.2 >> # dovecot -n >> sudo dovecot -n >> # 1.1.2: /usr/local/etc/dovecot.conf >> base_dir: /var/run/dovecot/ >> log_path: /var/log/dovecot.log >> ssl_disable: yes >> disable_plaintext_auth: no >> login_dir: /var/run/dovecot//login >> login_executable: /usr/local/libexec/dovecot/imap-login >> mail_location: /var/mail/%u > You need to fix your mail location setting; > see http://wiki.dovecot.org/MailLocation > >> auth default: >> verbose: yes >> passdb: >> driver: passwd-file >> args: /etc/dovecot/passwd >> userdb: >> driver: static >> args: uid=vmail gid=vmail home=/var/mail/%u > Since you are also setting mail location here with home setting, you are > probably resolving to /var/mail/%u/var/mail/%u Forget this last comment, but the mail location is not set properly. -- MailScanner is like deodorant... You hope everybody uses it, and you notice quickly if they don't!!!!

2 1

[Dovecot] rejecting mail due to quota exceeded
by martin f krafft 17 Sep '08

17 Sep '08

Hi, we are using dovecot's deliver to deliver mails to a virtual mailbox tree owned by the vmail user, by piping the message to the following command spawned by vmail: /usr/bin/env HOME=/srv/vmail/mydomain.ch/myaccount /usr/lib/dovecot/deliver When a message is delivered to an account that has reached its quotum, deliver issues a failure message saying: From: Mail Delivery Subsystem <postmaster(a)seamus.madduck.net> To: $ENVELOPE_SENDER Message-ID: <dovecot-1221640816-796581-0@seamus> Subject: Automatically rejected mail Your message to <vmail> was automatically rejected: Quota exceeded The original message is attached, which is nice, however, I don't like the dovecot rejection message for two reasons: 1. there was no message to <vmail> sent, dovecot should use the envelope recipient considering that it doesn't know the envelope recipient, this would best be solved by 2. don't accept the mail and send out a rejection, just exit 69 and write the reason to stderr! Did I miss something and is this already possible with dovecot's deliver in a virtual setting? Thanks, -- martin | http://madduck.net/ | http://two.sentenc.es/ "how do you feel about women's rights?" "i like either side of them." -- groucho marx spamtraps: madduck.bogus(a)madduck.net

2 2

[Dovecot] iphone connection problem
by dovecot＠feb17.org 17 Sep '08

17 Sep '08

Hi, I recently changed from uw imap to dovecot on the sound recommendation of a friend and have mostly succeeded in getting all of my clients up and running, but am really stuck with the iPhone which is failing to make connections. I run certificates on all of my clients and thunderbird happily connects both locally and remotely. I installed the certificate on the iPhone after great pain (pk12 via the Web administration utility). When you open the configurations on the phone , it tries to make a test connection to the server and fails with a generic SSL error. Dovecot reports just a generic disconnected error (imap-login/client.c line 333), and it appears to be dropping the connection. Sep 2 09:38:17 inchoate dovecot: imap-login: Disconnected (auth failed, 0 attempts): rip=209.204.139.116, lip=192.168.0.252, TLS I have run ssldump and here is the relevant section. If anybody has any insights they would be greatly appreciated Darren ssldump tail.. ServerHelloDone 1 5 0.1128 (0.0838) C>SV3.1(7) Handshake Certificate 1 6 0.1629 (0.0500) C>SV3.1(134) Handshake ClientKeyExchange 1 7 0.1629 (0.0000) C>SV3.1(1) ChangeCipherSpec 1 8 0.1629 (0.0000) C>SV3.1(48) Handshake 1 9 0.1677 (0.0048) S>CV3.1(1) ChangeCipherSpec 1 10 0.1677 (0.0000) S>CV3.1(48) Handshake 1 11 0.1761 (0.0084) S>CV3.1(48) application_data 1 12 0.2650 (0.0889) C>SV3.1(32) Alert 1 13 0.2651 (0.0000) S>CV3.1(32) Alert 1 0.2651 (0.0000) S>C TCP FIN 1 0.2675 (0.0024) C>S TCP FIN [root@inchoate src]# /tools/dovecot/sbin/dovecot -n # 1.1.2: /tools/dovecot-1.1.2/etc/dovecot.conf ssl_ca_file: /etc/mail/certs/cacert_plus_crl.pem ssl_cert_file: /etc/mail/certs/cert.pem ssl_key_file: /etc/mail/certs/key.pem ssl_verify_client_cert: yes login_dir: /tools/dovecot-1.1.2/var/run/dovecot/login login_executable: /tools/dovecot-1.1.2/libexec/dovecot/imap-login auth default: verbose: yes ssl_require_client_cert: yes passdb: driver: pam userdb: driver: passwd

10 23

[Dovecot] Errors on high load
by Allan Cassaro 17 Sep '08

17 Sep '08

Hi, always when my server is on high load I saw this errors on logs: curie:~# uptime 10:22:38 up 19 days, 19:19, 2 users, load average: 207.01, 169.27, 94.41 Sep 15 17:00:26 curie dovecot: imap-login: *** glibc detected *** imap-login: malloc(): memory corruption: 0x00000000009f8560 *** Sep 15 17:00:26 curie dovecot: child 24012 (login) killed with signal 6 Sep 15 18:48:36 curie dovecot: auth(default_with_listener): BUG: Authentication client said it's PID 0 Sep 15 18:48:36 curie dovecot: child 24014 (login) killed with signal 11 Sep 16 09:05:19 curie dovecot: imap-login: *** glibc detected *** imap-login: malloc(): memory corruption: 0x00000000008c4bc0 *** Sep 16 09:05:19 curie dovecot: child 24013 (login) killed with signal 6 Sep 16 10:17:14 curie dovecot: imap-login: *** glibc detected *** imap-login: malloc(): memory corruption: 0x000000000098bb30 *** Sep 16 10:17:14 curie dovecot: child 24015 (login) killed with signal 6 Sep 16 10:19:02 curie dovecot: child 24002 (login) killed with signal 6 Sep 16 10:19:02 curie dovecot: managesieve-login: *** glibc detected *** managesieve-login: double free or corruption (!prev): 0x000000000066d700 *** Sep 16 10:19:18 curie dovecot: Panic: IMAP(geduardo): file maildir-save.c: line 241 (maildir_get_updated_filename): assertion failed: (ctx->keywords_sync_ctx != NULL || mf->keywords_count == 0) Sep 16 10:19:18 curie dovecot: IMAP(geduardo): Raw backtrace: /usr/libexec/dovecot/imap [0x47a7f2] -> /usr/libexec/dovecot/imap [0x47a863] -> /usr/libexec/dovecot/imap [0x479f16] -> /usr/libexec/dovecot/imap [0x43295b] -> /usr/libexec/dovecot/imap(maildir_transaction_save_commit_pre+0x19a) [0x4331ea] -> /usr/libexec/dovecot/imap [0x42d0b7] -> /usr/libexec/dovecot/imap(index_transaction_commit+0x3f) [0x44b16f] -> /usr/lib/dovecot/imap/lib10_quota_plugin.so [0x2b70f72e90d7] -> /usr/libexec/dovecot/imap(cmd_copy+0x344) [0x4181f4] -> /usr/libexec/dovecot/imap(cmd_uid+0x52) [0x41c072] -> /usr/libexec/dovecot/imap [0x41ca4c] -> /usr/libexec/dovecot/imap [0x41cb02] -> /usr/libexec/dovecot/imap [0x41d2cf] -> /usr/libexec/dovecot/imap(client_input+0x63) [0x41d503] -> /usr/libexec/dovecot/imap(io_loop_handler_run+0xf8) [0x481448] -> /usr/libexec/dovecot/imap(io_loop_run+0x1d) [0x4805ad] -> /usr/libexec/dovecot/imap(main+0x3c2) [0x424962] -> /lib/libc.so.6(__libc_start_main+0xe6) [0x2b70f6d9e1a6] -> /usr/libexec/dovecot Sep 16 10:19:18 curie dovecot: child 20481 (imap) killed with signal 6 I have about 1000 users. To me, this is not a problem, nothing strange occurs (except the slowly, but under heavy load this is normal). But I think this is interesting to developers... :D Regards. -- http://allan.cassaro.googlepages.com

4 4

[Dovecot] Moving from cyrus to dovecot (a story)
by Steinar Bang 16 Sep '08

16 Sep '08

The transition was quick, and also (so far) seemingly painless. The server is an old Pentium II 233 machine that sits between my home LAN and the internet, and have sitting there, and running night and day since 1999. For the first two years it was running SuSE linux, but since 2001 it has been running debian and been continously upgraded. It was originally installed with potato, but have been apt-get dist-upgrade'd to woody, and then to sarge, and then etch, which is what it's currently running I've been using cyrus imapd since 1999 (compiled by hand on SuSE and using the debian packaged version on debian). But in all these years I've never become really friendly with it. In the years leading up to 1999 I had been running UoW imapd at work, and I wasn't too impressed with it at that point in time. The alternative choices were courier and cyrus, and I picked cyrus more or less arbitrarily. By "never become really friendly", I mean - I've never really gotten a good understanding of the configuration - I've never quite understood what the documentation have said about authentication and SSL support. I've gotten things to work by trial and error - Four times the seen data bases have become corrupt. Two times during upgrades (one of them after I had switched to skip lists), and two times on their own, while I was still running BDB - Since delivery was to a central spool and database, owned by user cyrus, has meant that I had to use sieve (which is another thing I've never quite understood) for mail filtering, instead of dear old procmail Cyrus has lots of stuff related to scaling and having mailboxes for users that have no users on the host, but that's not really relevant to my home server. Around six months ago I stumbled over dovecot, which from my POV have the following crucial features: 1. folders under the users' home directories, either as mbox or as maildir, which allows me to do list filtering with procmail, and no central databases that can become corrupt 2. understandable configuration (the only change I'd had to do in the debian dovecot, is to allow for cram-md5 authentication) I decided om maildir as the folder format. I like the simplicity of mbox folders, but I have some archive folders with around 20k of articles each, and maildir would scale a bit better for them. Also mail delivery without locking is a very nice feature. Here's how I proceeded: - I set up dovecot on my daughter's Ubuntu Hardy machine - I ran imapsync on this machine to extract everything I had on the cyrus server to Maildir folders in the users' home directories on the Ubuntu box - I shut down fetchmail on my gateway box (since ISP port filtering and blacklisting of dynamic addresses stops direct SMTP delivery I have to use ISP gateways and mail drops) - I changed the exim conf on my gateway from using cyrdeliver to delivering to a maildir folder in the users' home directory - I restored my old .procmailrc file from subversion (my home directory is checked into subversion, this was originally a CVS repo that went subversion a couple of years ago), merged in the last version of the .procmailrc that used cyrdeliver (I gave up on that because the .procmailrc file had to be owned by user cyrus, which was very impractical), and changed the filtering rules to deliver to maildir folders - I tested some delivery - I apt-get install'd dovecot from the etch back ports pointed to from the dovecot install page http://wiki.dovecot.org/PrebuiltBinaries#head-477d52d96fcf34ad3033b13e5e5a2… This uninstalled cyrus22-imapd, but not the rest of cyrus 2.2, which blocked dovecot from starting after the install - I stopped cyrus22 and uninstalled all of the cyrus22 packages - I rsync'd the maildir folders from the Ubuntu box to the old mail server - I started dovecot - I use Gnus as my MUA. I had removed all nnimap groups related to the home server in Gnus, and resubscribed them. All folders came up in the state I had left them. Gnus stores article state on the server as custom marks, and imapsync had preserved the custom flags. I unsubscribed the groups to avoid article caching confusion, because imapsync changes the UIDs. However, all folders except INBOX had changed their names, so that didn't matter much - I started fetchmail and sent som test emails, and observed that they ended up in the right Maildir folders, and that dovecot picked them up as expected And today I accessed the server from work. So it looks like I'm back in business. This time with a server I understand a lot better. Thanx for writing it, Timo! - Steinar

2 1