- dovecot - dovecot.org

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

19 Sep '08

1 0

[Dovecot] sieve discard
by Jim Horner 19 Sep '08

19 Sep '08

Does the keyword/action discard work by default or is there something I have to do in the configuration to get to work... maybe I missed something on http://wiki.dovecot.org/LDA/Sieve I have the following rule: if anyof ( header :contains ["Subject"] ["Test Discard"] ) { discard; stop; } but it delivers to INBOX with or w/o the "stop;". If I change the rule to if anyof ( header :contains ["Subject"] ["Test Discard"] ) { fileinto "spam"; stop; } the message will deliver into my spam folder which makes me think I am doing something wrong with "discard". Using 1.0.2 sieve plug-in. Thanks.

9 21

[Dovecot] error in dovecot.log about ldap
by Antonio Casado Rodríguez 19 Sep '08

19 Sep '08

Hi, i've upgrade dovecot 1.0.10 to 1.1.3 in Red Hat Enterprise Linux AS release 4 I've installed http://dl.atrpms.net/all/dovecot-1.1.3-0_80.src.rpm with http://www.rename-it.nl/dovecot/1.1/dovecot-1.1.3-managesieve-0.10.3.diff.gz patch. And i've installed dovecot-sieve-1.1.5-8.el4.i386.rpm and dovecot-1.1-managesieve-0.10.3.tar.gz I see in dovecot.log: dovecot: Sep 19 12:20:56 Error: auth(default): dlopen(/usr/lib/dovecot/auth/libauthdb_ldap.so) failed: /usr/lib/dovecot/auth/libauthdb_ldap.so: undefined symbol: null_settings_section_callback dovecot: Sep 19 12:20:56 Error: auth-worker(default): dlopen(/usr/lib/dovecot/auth/libauthdb_ldap.so) failed: /usr/lib/dovecot/auth/libauthdb_ldap.so: undefined symbol: null_settings_section_callback # dovecot -n # 1.1.3: /etc/dovecot.conf log_path: /var/log/dovecot/dovecot.log info_log_path: /var/log/dovecot/dovecot.info protocols: imaps managesieve ssl_cert_file: /etc/httpd/conf/ssl.crt/server.crt ssl_key_file: /etc/httpd/conf/ssl.key/server.key login_dir: /var/run/dovecot/login login_executable(default): /usr/libexec/dovecot/imap-login login_executable(imap): /usr/libexec/dovecot/imap-login login_executable(managesieve): /usr/local/libexec/dovecot/managesieve-login login_log_format_elements: user=<%u> method=%m rip=%r rport=%b lip=%l lport=%a %c verbose_proctitle: yes mail_location: maildir:/var/spool/mail/%n mail_executable(default): /usr/sbin/post-login-dovecot mail_executable(imap): /usr/sbin/post-login-dovecot mail_executable(managesieve): /usr/local/libexec/dovecot/managesieve mail_plugins(default): quota imap_quota mail_plugins(imap): quota imap_quota mail_plugins(managesieve): mail_plugin_dir(default): /usr/lib/dovecot/imap mail_plugin_dir(imap): /usr/lib/dovecot/imap mail_plugin_dir(managesieve): /usr/lib/dovecot/managesieve sieve_storage(default): sieve_storage(imap): sieve_storage(managesieve): ~/sieve sieve(default): sieve(imap): sieve(managesieve): ~/.dovecot.sieve namespace: type: private separator: / location: maildir:/var/mail/%n inbox: yes list: yes subscriptions: yes auth default: passdb: driver: pam userdb: driver: passwd plugin: quota: maildir quota_rule: *:storage=50M quota_rule2: Trash:storage=15M

1 0

[Dovecot] squat fts index build problem
by Anton Yuzhaninov 18 Sep '08

18 Sep '08

I tried to use squat index, but got error: Sep 18 19:49:45 mailsupport dovecot: Fatal: IMAP(citrin): pool_system_realloc(): Out of memory Sep 18 19:49:45 mailsupport dovecot: child 77606 (imap) returned error 83 (Out of memory) It is strange because this server has 4 Gb or RAM. some lines from dovecot -n mail_plugins(imap): acl mail_log zlib fts fts_squat plugin: acl: vfile fts: squat OS: FreeBSD 7.0-STABLE #0: Sun May 4 13:15:10 MSD 2008, amd64 Resource limits (current): cputime infinity secs filesize infinity kB datasize 33554432 kB stacksize 524288 kB coredumpsize infinity kB memoryuse infinity kB memorylocked infinity kB maxprocesses 5547 openfiles 11095 sbsize infinity bytes vmemoryuse infinity kB IMHO it will be better to write in log requested memory size: src/lib/mempool-system.c: - "pool_system_realloc(): Out of memory"); + "pool_system_realloc(): Out of memory, when realloc to %"PRIuSIZE_T" bytes", new_size); -- WBR, Anton Yuzhaninov

2 2

[Dovecot] lately pop3 with #define DEBUG needs GDB=1
by Diego Liziero 18 Sep '08

18 Sep '08

I'm not sure when this happened. In yesterday dovecot-1.1 hg if pop3 is compiled with DEBUG defined, it needs GDB=1 otherwise it ends with: Panic: Leaked file fd 4: dev 104.2 inode 3342766 Not sure if this can be caused by the fact that I call pop3 with a bash script. protocol pop3 { mail_executable = /usr/libexec/dovecot/pop3.sh inside I've something like if [ x`id -un` = "xmyuser" -o x`id -un` = "xtestdovecot" ] then exec /usr/libexec/dovecot/pop3-new-test-release else exec /usr/libexec/dovecot/pop3 [..] (gdb) bt full #0 0x006ed402 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 0x080e44a8 in default_fatal_finish (type=LOG_TYPE_PANIC, status=0) at failures.c:150 backtrace = 0x982b160 "/usr/libexec/dovecot/pop3 [0x80e4486] -> /usr/libexec/dovecot/pop3(default_error_handler+0) [0x80e4506] -> /usr/libexec/dovecot/pop3(i_fatal+0) [0x80e4600] -> /usr/libexec/dovecot/. #4 0x080e4506 in default_fatal_handler (type=LOG_TYPE_PANIC, status=0, format=0x810f568 "Leaked file fd %d: dev %s.%s inode %s", args=0xbfee57a4 "\004") at failures.c:162 No locals. #5 0x080e4600 in i_panic (format=0x810f568 "Leaked file fd %d: dev %s.%s inode %s") at failures.c:197 args = 0xbfee57a4 "\004" #6 0x080e519d in fd_debug_verify_leaks (first_fd=4, last_fd=1024) at fd-close-on-exec.c:71 addr = {family = 58360, u = {ip6 = {in6_u = {u6_addr8 = "\225ï¿½\017\b\a\000\000\000ï¿½XGDï¿½ï¿½\017\b", u6_addr16 = {58005, 2063, 7, 0, 22776, 17479, 58362, 2063}, u6_addr32 = {135258773, 7, 1145526520, 135259130}}}, ip4 = {s_addr = 135258773}}} raddr = {family = 2, u = {ip6 = {in6_u = {u6_addr8 = "\031^ï¿½ï¿½Yï¿½ï¿½Xï¿½\005\021D", u6_addr16 = {24089, 49134, 23028, 49134, 22744, 49134, 4357, 68}, u6_addr32 = {3220069913, 3220068852, 3220068568, 4460805}}}, ip4 = {s_addr = 3220069913}}} port = 4274100 rport = 3220068600 st = {st_dev = 26626, __pad1 = 0, __st_ino = 3342766, st_mode = 33152, st_nlink = 1, st_uid = 0, st_gid = 0, st_rdev = 0, __pad2 = 0, st_size = 6654265, st_blksize = 4096, st_blocks = 13032, st_atim = { tv_sec = 1221681411, tv_nsec = 0}, st_mtim = {tv_sec = 1221683098, tv_nsec = 0}, st_ctim = {tv_sec = 1221683098, tv_nsec = 0}, st_ino = 3342766} old_errno = 9 #7 0x0805c817 in main (argc=1, argv=0xbfee5994, envp=0xbfee599c) at main.c:257 No locals.

2 2

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

18 Sep '08

Scott, That worked! Thanks again for the help! ----- Original Message ---- From: Scott Silva <ssilva(a)sgvwater.com> To: dovecot(a)dovecot.org Sent: Wednesday, September 17, 2008 3:57:39 PM Subject: Re: [Dovecot] Connecting to dovecot on 9-17-2008 3:48 PM Grant Lowe spake the following: > We have home directories on the server. Virtual user's can login (at least I've been able to verify that from using telnet to port 143). Yes the earlier mail was different. I can go back to that configuration if I need to. Meanwhile I'll take a look at the link you sent. Thank you! > Then try this; mail_location = mbox:~/mail:INBOX=/var/mail/%u Make sure the home directories map properly and not to /var/mail/%u from however you auth. The above puts IMAP folders in a folder called mail in the users home directory, and the inbox in /var/mail/%u. Dovecot will also store its indexes in the ~/mail directory, so it has to be a folder. -- MailScanner is like deodorant... You hope everybody uses it, and you notice quickly if they don't!!!!

1 0

[Dovecot] two server and dbox
by a.testa＠wifisolution.it 18 Sep '08

18 Sep '08

Dear users, I have a question about the storage dbox. Is it possible to deliver e-mails from two different lda? I would have two independent servers working at the same time on nfs. Is it possible since the e-mails name will be the same? Thanks in advance Alex

3 3

[Dovecot] Outlook 2003 and Thunderbird IMAP + getting new headers
by Jan van den Berg 18 Sep '08

18 Sep '08

Hi, We run 1.1.3 and I use Outlook to connect to my IMAP box and a couple of times per day (randomly) when I click certain folders IMAP will start retrieving ALL headers for that folder again ('retrieving new headers')! I don't understand this. What triggers IMAP to do so, why not just retrieve only the NEW headers? Is it Dovecot or Outlook (probably) and what can be done about this? I already use the Dovecot Outlook workarounds. I have also gotten word that this behavior happens with Thunderbird. This is really a problem causing a lot of load on our storage (I am not the only user). Cheers, Jan

3 16

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

18 Sep '08

> Date: Wed, 17 Sep 2008 12:41:31 -0400 > From: Charles Marcus <CMarcus(a)Media-Brokers.com> > Subject: Re: [Dovecot] Mail being delivered to mbox instead of Maildir > To: Dovecot Mailing List <dovecot(a)dovecot.org> > Message-ID: <48D1333B.8060907(a)Media-Brokers.com> > Content-Type: text/plain; charset=ISO-8859-1 > > On 9/17/2008, Sean Smitz (sean.smitz(a)us.fujitsu.com) wrote: > >> mail_location: maildir:~/Maildir >> > > Maybe it is case sensitive... > > Try: > > mail_location: Maildir:~/Maildir > > -- > > Best regards, > > Charles > > > ------------------------------ > I will try, but that is how the examples are capitalized. > Message: 9 > Date: Wed, 17 Sep 2008 22:25:07 +0300 > From: Timo Sirainen <tss(a)iki.fi> > Subject: Re: [Dovecot] Mail being delivered to mbox instead of Maildir > To: Dovecot Mailing List <dovecot(a)dovecot.org> > Message-ID: <8E304E7D-48BF-405F-93C8-1374FD483E8F(a)iki.fi> > Content-Type: text/plain; charset="us-ascii" > > On Sep 17, 2008, at 5:22 PM, Sean Smitz wrote: > > >> 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 >> > > You sure sendmail is really calling deliver? In that case you should > see deliver logging "saved mail to INBOX" lines. > > Timo, I don't see that in the /var/log/maillog file. do I need to increase the default logging level? Sep 16 15:09:00 mailserv1 sendmail[20848]: m8GJ90bl020846: SMTP outgoing connect on mailserv1.fla.fujitsu.com Sep 16 15:09:06 mailserv1 sendmail[20848]: m8GJ90bl020846: to=<david(a)torrisi.org>, ctladdr=<mailtest(a)mailserv1.fla.fujitsu.com> (10295/10297), delay=00:00:06, xdelay=00:00:06, mailer=relay, pri=120363, relay=fujitsu1.fnanic.fujitsu.com. [192.240.0.1], ds n=2.0.0, stat=Sent (m8GJ95rd028033 Message accepted for delivery) Sep 16 15:09:06 mailserv1 sendmail[20848]: m8GJ90bl020846: done; delay=00:00:06, ntries=1

2 1

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

18 Sep '08

We have home directories on the server. Virtual user's can login (at least I've been able to verify that from using telnet to port 143). Yes the earlier mail was different. I can go back to that configuration if I need to. Meanwhile I'll take a look at the link you sent. Thank you! ----- Original Message ---- From: Scott Silva <ssilva(a)sgvwater.com> To: dovecot(a)dovecot.org Sent: Wednesday, September 17, 2008 3:01:51 PM Subject: Re: [Dovecot] Connecting to dovecot on 9-17-2008 2:43 PM Grant Lowe spake the following: > We want to have just inboxes in /var/mail/%u. > > I'm not sure how well that is going to work. You might need some sort of home directory, but your earlier conf had mail location and home directory pointing to the same place. That location can't be a directory AND a file. Do users have home directories on this server or is it all virtual? Maybe this has more clues; http://wiki.dovecot.org/MailLocation -- MailScanner is like deodorant... You hope everybody uses it, and you notice quickly if they don't!!!!

2 1

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

18 Sep '08

We want to have just inboxes in /var/mail/%u. ----- Original Message ---- From: Scott Silva <ssilva(a)sgvwater.com> To: dovecot(a)dovecot.org Sent: Wednesday, September 17, 2008 2:27:49 PM Subject: Re: [Dovecot] Connecting to dovecot on 9-17-2008 1:13 PM Grant Lowe spake the following: > As far as ls -la: > > # ls -la /var/mail/wfoatst > -rw------- 1 wfoatst users 1406 Sep 16 15:13 /var/mail/wfoatst > # > > As far as the LDA, I'm using the dovecot LDA. Here's the line from /etc/mail/sendmail.cf: > > ######################*****############## > ### 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 > > > Are you trying to have *all* mail in /var/mail/%u or just inboxes? Your ls looks like you have mbox format storage. -- MailScanner is like deodorant... You hope everybody uses it, and you notice quickly if they don't!!!!

2 1

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

18 Sep '08

As far as ls -la: # ls -la /var/mail/wfoatst -rw------- 1 wfoatst users 1406 Sep 16 15:13 /var/mail/wfoatst # As far as the LDA, I'm using the dovecot LDA. Here's the line from /etc/mail/sendmail.cf: ######################*****############## ### 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 ----- Original Message ---- From: Scott Silva <ssilva(a)sgvwater.com> To: dovecot(a)dovecot.org Sent: Wednesday, September 17, 2008 12:57:02 PM Subject: Re: [Dovecot] Connecting to dovecot on 9-17-2008 12:44 PM Grant Lowe spake the following: > Hi Scott. > > Thanks for the help! Appricate the feedback. > > I reset the dovecot.conf. Here's the output of dovecot -n now: > > # > # 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 > auth default: > verbose: yes > passdb: > driver: pam > userdb: > driver: passwd > # > > I'm still getting the same error as before: > > ovecot: Sep 17 12:42:43 Info: imap-login: Login: user=<wfoatst>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured > dovecot: Sep 17 12:42:43 Error: IMAP(wfoatst): mail_location not set and autodetection failed: Mail storage autodetection failed with home=/var/mail/wfoatst > dovecot: Sep 17 12:42:43 Fatal: IMAP(wfoatst): Namespace initialization failed > > Any more thoughts? How about a "ls -la /var/mail/wfoatst" What do you use for your LDA? -- MailScanner is like deodorant... You hope everybody uses it, and you notice quickly if they don't!!!!

2 1

[Dovecot] procmail -> deliver: file too large
by Jim Rosenberg 17 Sep '08

17 Sep '08

I am using procmail with deliver as recommended on the wiki to send mail snagged by SpamAssassin straight to a spam folder. It seemed to be working fine, but now I'm finding messages like this: Sep 17 12:13:47 hosty deliver(whoey): write() failed with mbox file /var/mail/whoey: File too large I don't think this is a setrlimit problem -- the host operating system is OpenBSD 4.0. My dovecot version is 1.0.13. Is there a maximum size used by deliver? Or is this a procmail problem? It looks like the message is coming from deliver. I don't think this is a postfix problem -- my max message size 33M in postfix. -Thanks, Jim

3 3

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

17 Sep '08

Hi Scott. Thanks for the help! Appricate the feedback. I reset the dovecot.conf. Here's the output of dovecot -n now: # # 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 auth default: verbose: yes passdb: driver: pam userdb: driver: passwd # I'm still getting the same error as before: ovecot: Sep 17 12:42:43 Info: imap-login: Login: user=<wfoatst>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured dovecot: Sep 17 12:42:43 Error: IMAP(wfoatst): mail_location not set and autodetection failed: Mail storage autodetection failed with home=/var/mail/wfoatst dovecot: Sep 17 12:42:43 Fatal: IMAP(wfoatst): Namespace initialization failed Any more thoughts? ----- Original Message ---- From: Scott Silva <ssilva(a)sgvwater.com> To: dovecot(a)dovecot.org Sent: Wednesday, September 17, 2008 7:48:39 AM Subject: Re: [Dovecot] Connecting to dovecot 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 -- MailScanner is like deodorant... You hope everybody uses it, and you notice quickly if they don't!!!!

2 1

[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

[Dovecot] Quota, maildir, MySQL,
by Bart Dorlandt 16 Sep '08

16 Sep '08

Hi everybody, I am trying to work with quota. I use postfix and dovecot with a sql backend. Below you'll find my configuration. Everything works except for the quota part. It doesn't seem to see the quota and doesn't respond to the sender that the client is over its quota. versions: postfix-2.5.20070531-mysql dovecot-1.0.2-mysql Thanks for the help in advance. My Settings: # 1.0.2: /etc/dovecot.conf base_dir: /var/dovecot/ log_path: /var/log/dovecot.log protocols: imap imaps pop3s listen(default): 127.0.0.1:143 listen(imap): 127.0.0.1:143 listen(pop3): * ssl_listen: * ssl_cert_file: /etc/ssl/dovecotcert.pem login_dir: /var/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_user: _dovecot first_valid_uid: 2000 last_valid_uid: 2000 first_valid_gid: 2000 last_valid_gid: 2000 mail_location: maildir:/var/mail/vhosts/%d/%n maildir_copy_with_hardlinks: yes mbox_write_locks: fcntl 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_plugins(default): quota imap_quota mail_plugins(imap): quota imap_quota mail_plugins(pop3): quota 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 imap_client_workarounds(default): delay-newmail outlook-idle netscape-eoh tb-extra-mailbox-sep imap_client_workarounds(imap): delay-newmail outlook-idle netscape-eoh tb-extra-mailbox-sep imap_client_workarounds(pop3): outlook-idle pop3_uidl_format(default): pop3_uidl_format(imap): pop3_uidl_format(pop3): %08Xu%08Xv pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh auth default: mechanisms: plain login digest-md5 debug: yes passdb: driver: sql args: /etc/dovecot-sql.conf userdb: driver: prefetch userdb: driver: sql args: /etc/dovecot-sql.conf socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: _postfix group: _postfix master: path: /var/run/dovecot/auth-master mode: 432 user: vmail group: vmail plugin: quota: maildir: my /etc/dovecot-sql.conf: user_query = SELECT uid, gid, home, maildir as mail, concat('maildir:storage=',quota) AS quota FROM users WHERE login = '%u' password_query = SELECT password, uid AS userdb_uid, gid AS userdb_gid, home AS userdb_home, maildir as userdb_mail, concat('maildir:storage=', quota) AS userdb_quota FROM users WHERE login = '%u' My postfix config: # postconf -n alias_database = hash:/etc/postfix/aliases alias_maps = hash:/etc/postfix/aliases bounce_template_file = /etc/postfix/bounce.cf command_directory = /usr/local/sbin config_directory = /etc/postfix content_filter = smtp-amavis:[127.0.0.1]:10024 daemon_directory = /usr/local/libexec/postfix disable_vrfy_command = yes html_directory = /usr/local/share/doc/postfix/html inet_interfaces = all inet_protocols = all invalid_hostname_reject_code = 554 mail_owner = _postfix mailq_path = /usr/local/sbin/mailq manpage_directory = /usr/local/man maximal_queue_lifetime = 40d message_size_limit = 20480000 multi_recipient_bounce_reject_code = 554 mydestination = localhost.$mydomain, localhost mydomain = bamweb.nl myhostname = bama.bamweb.nl mynetworks = 127.0.0.0/8, 82.173.141.217/32 myorigin = $myhostname newaliases_path = /usr/local/sbin/newaliases non_fqdn_reject_code = 554 permit_mx_backup_networks = zoph.getmyip.com queue_directory = /var/spool/postfix readme_directory = /usr/local/share/doc/postfix/readme recipient_delimiter = + relay_domains = $mydestination, hash:/etc/postfix/relay_domains relay_domains_reject_code = 554 relay_recipient_maps = sample_directory = /etc/postfix sendmail_path = /usr/local/sbin/sendmail setgid_group = _postdrop smtpd_banner = $myhostname ESMTP $mail_name smtpd_helo_required = yes smtpd_recipient_restrictions = permit_mynetworks, permit_mx_backup, reject_invalid_hostname, check_relay_domains, reject_non_fqdn_hostname, reject_non_fqdn_sender, reject_non_fqdn_recipient, reject_unknown_sender_domain, reject_unknown_recipient_domain, reject_unauth_destination, reject_rbl_client relays.ordb.org, reject_rbl_client opm.blitzed.org, reject_rbl_client list.dsbl.org, reject_rbl_client sbl.spamhaus.org, reject_rbl_client cbl.abuseat.org, reject_rbl_client dul.dnsbl.sorbs.net, reject_rbl_client dev.null.dk, reject_rbl_client virbl.dnsbl.bit.nl, reject_rbl_client smtp.dnsbl.sorbs.net, reject_rbl_client socks.dnsbl.sorbs.net, reject_rbl_client http.dnsbl.sorbs.net, reject_rbl_client web.dnsbl.sorbs.net, check_policy_service inet:127.0.0.1:60000 permit strict_rfc821_envelopes = yes unknown_address_reject_code = 554 unknown_client_reject_code = 554 unknown_hostname_reject_code = 554 unknown_local_recipient_reject_code = 554 unknown_relay_recipient_reject_code = 554 unknown_virtual_alias_reject_code = 554 unknown_virtual_mailbox_reject_code = 554 unverified_recipient_reject_code = 554 unverified_sender_reject_code = 554 virtual_alias_maps = mysql:/etc/postfix/mysql_virtual_alias_maps.cf mysql:/etc/postfix/mysql_virtual_email2email.cf virtual_gid_maps = static:2000 virtual_mailbox_base = /var/mail/vhosts virtual_mailbox_domains = mysql:/etc/postfix/mysql_virtual_domains.cf virtual_mailbox_maps = mysql:/etc/postfix/mysql_virtual_mailboxes.cf virtual_minimum_uid = 2000 virtual_uid_maps = static:2000 -- www.bamweb.nl

2 1

[Dovecot] How to recover sieve files?
by David Reid 16 Sep '08

16 Sep '08

I'm seeing a lot of these messages in my log files... deliver(...): Aug 10 15:18:34 Error: sieve_execute_bytecode(.../.dovecot.sievec) failed I'm guessing the file needs to be updated/recreated, but what's the "correct" way to do it? should I just remove the existing one and let the server recreate it? Thanks, david

2 1

[Dovecot] Authentication fails
by CJ Keist 16 Sep '08

16 Sep '08

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Been running dovecot 1.1.2 for about a month now. I Have strange issue that I have not been able to trouble shoot. What I'm seeing is that dovecot runs along just fine for about 4 days, and then it will just stop authenticating everyone (IMAP and POP). No errors in the logs other than all authentication attempts comes out as password mismatch. The only fix is to stop and restart dovecot. % ./dovecot -n # 1.1.2: /userM/mail-services/dovecot/etc/dovecot.conf Warning: fd limit 256 is lower than what Dovecot can use under full load (more than 3072). Either grow the limit or change login_max_processes_count and max_mail_processes settings base_dir: /userM/mail-services/dovecot/var/run/dovecot/ protocols: imap imaps pop3 pop3s ssl_cert_file: /userM/mail-services/dovecot/etc/ssl/dovecot.pem ssl_key_file: /userM/mail-services/dovecot/etc/ssl/privkey.pem ssl_parameters_regenerate: 0 ssl_cipher_list: MEDIUM:!LOW disable_plaintext_auth: no login_dir: /userM/mail-services/dovecot/var/run/dovecot/login login_executable(default): /userM/mail-services/dovecot/libexec/dovecot/imap-login login_executable(imap): /userM/mail-services/dovecot/libexec/dovecot/imap-login login_executable(pop3): /userM/mail-services/dovecot/libexec/dovecot/pop3-login login_greeting: Cyrus ready. login_max_processes_count: 1024 max_mail_processes: 1024 mail_location: mbox:~/:INBOX=/userM/mail/%u mail_debug: yes mmap_disable: yes mail_nfs_index: yes mbox_lock_timeout: 60 mbox_dotlock_change_timeout: 60 mail_executable(default): /userM/mail-services/dovecot/libexec/dovecot/imap mail_executable(imap): /userM/mail-services/dovecot/libexec/dovecot/imap mail_executable(pop3): /userM/mail-services/dovecot/libexec/dovecot/pop3 mail_plugin_dir(default): /userM/mail-services/dovecot/lib/dovecot/imap mail_plugin_dir(imap): /userM/mail-services/dovecot/lib/dovecot/imap mail_plugin_dir(pop3): /userM/mail-services/dovecot/lib/dovecot/pop3 auth default: mechanisms: plain login verbose: yes debug: yes passdb: driver: pam passdb: driver: passwd args: blocking=yes userdb: driver: passwd args: blocking=yes socket: type: listen client: path: /var/lib/postfix/private/auth mode: 438 user: postfix group: postfix master: path: /userM/mail-services/dovecot/var/run/dovecot//auth-master mode: 384 This is on Solaris 10, using LDAP for authentication. Any ideas on how to trouble shoot what might be going on? - -- 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' -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFIzrciA29OFr7C6jcRAk/NAJoDKskvI4GpQg2yQPrUyH9AdzmFNACgjPTI rsWVRV8WuuH/RFx+1YOnzEY= =toPK -----END PGP SIGNATURE-----

3 3

[Dovecot] IMAP traffic logging
by fp＠onwebworx.net 16 Sep '08

16 Sep '08

Hi! Is there any known way I can log traffic caused by IMAP sessions? First it is adequate to have a rough overall statistic let's say traffic per hour - this is easily done with iptables. But on the long term I also need information on account basis. I thought of rawlogging every IMAP session and then simply count the filesizes. But the created logs have dropouts because dovecot doesn't log whole FETCH commands what is a problem. Thanks for every idea you have! Paul

2 2

[Dovecot] Dovecot cannot unlink non-empty directory
by Włodek Waligórski 16 Sep '08

16 Sep '08

Hi, Currently I use dovecot 1.1.3 on Debian Testing. CPU arch is x86. Mail is stored on ext3 fs. I'm having a following problem with deleting folders (there is no problem with creation of folders): Error: IMAP(test(a)laptop.aonet.pl): unlink_directory(/home/vpopmail/domains/laptop.aonet.pl/test/.//Maildir/..DOVECOT-TRASHED) failed: Permission denied HOW TO REPRODUCE 1. Create a fresh new account 2. Login to a new account and create folder say 'TestFolder' 3. When I try to delete TestFolder - it is deleted and ..DOVECOT-TRASHED appears in user's Maildir AND Error: IMAP(test(a)laptop.aonet.pl): unlink_directory(/home/vpopmail/domains/laptop.aonet.pl/test/.//Maildir/..DOVECOT-TRASHED) failed: Permission denied message appears - it is triggered from line 815 of dovecot-1.1.3/src/lib-storage/index/maildir/maildir-storage.c 4. Create 'TestFolder2' 5. Trying to delete 'TestFolder2' gives the same error: Error: IMAP(test(a)laptop.aonet.pl): unlink_directory(/home/vpopmail/domains/laptop.aonet.pl/test/.//Maildir/..DOVECOT-TRASHED) failed: Permission denied this one however, is triggered from line 806 of dovecot-1.1.3/src/lib-storage/index/maildir/maildir-storage.c 6. The folder 'TestFolder2' is not deleted and from this point no other newly created folders can be deleted too. --------------------------------------------------------- I. Yes, the file permissions are fine - all are writeable to (mail_uid = vpopmail) II. The problem is - dovecot cannot unlink non-empty directory, I artificially deleted contents of ..DOVECOT-TRASHED and dovecot allowed folder deletion from client. After that situation was like in point 4. -My-config------------------------------------------------------ # 1.1.3: /usr/local/etc/dovecot.conf base_dir: /usr/local/var/run/dovecot/ log_path: /dev/stderr info_log_path: /dev/stderr log_timestamp: listen: 127.0.0.1:143 ssl_listen: 0:993 ssl_cert_file: /var/qmail/control/servercert.pem ssl_key_file: /var/qmail/control/servercert.pem ssl_cipher_list: ALL:!LOW verbose_ssl: yes login_dir: /usr/local/var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login verbose_proctitle: yes first_valid_uid: 89 last_valid_uid: 89 mail_uid: vpopmail mail_gid: vchkpw mail_location: maildir:~/Maildir mail_debug: yes mail_plugins: quota imap_quota imap_client_workarounds: outlook-idle auth default: user: vpopmail verbose: yes debug: yes passdb: driver: vpopmail args: quota_template=quota_rule=*:backend=%q userdb: driver: vpopmail plugin: quota: maildir quota_rule: ?:storage=110485760 quota_rule2: Trash:ignore quota_rule3: SPAM:ignore quota_warning: storage=90%% /usr/local/bin/imap-quota-warning 90 ---------------------------------------------------------------------- is this my mistake in configuration or is dovecot doing something wrong? tnx for help, -Włodek

2 5

[Dovecot] fail2ban 0.8
by Luigi Rosa 15 Sep '08

15 Sep '08

Does anyone have the filter strings for Fail2Ban 0.8 to block Dovecot 1.1 login failures? Thanks! Ciao, luigi -- / +--[Luigi Rosa]-- \ If the odds are a million to one against something occurring, chances are 50-50 it will.

2 2

[Dovecot] Blackberry suggestions?
by Ed W 14 Sep '08

14 Sep '08

Hi, I'm not a Blackberry user, but we have some customers currently using an Exchange server with some kind of blackberry and interested in moving their service over to our dovecot 1.1 server Does anyone have any notes or recommendations on getting a (UK) Blackberry to talk effectively to a normal Dovecot server, and are there any things to consider in order to get whatever features they are normally using on their Exchange link working on the Dovecot server? (It's just a small couple of person office on an Exchange server) Thanks for any thoughts/tips Ed W

2 1

[Dovecot] Corrected permissions for login directory message
by Nicolas Letellier 14 Sep '08

14 Sep '08

Hello. I already have this warn message when I start dovecot (1.1.3). I saw some message in mailing list about this warning, but nothing which solve my problem. See the message: root@machine dovecot $ /usr/local/etc/rc.d/dovecot restart Stopping dovecot. Waiting for PIDS: 47494. Starting dovecot. Warning: Corrected permissions for login directory /var/run/dovecot/login See the permissions: ls -l /var/rundrwxr-xr-x 3 root wheel 512 Sep 11 15:42 dovecot ls -l /var/run/dovecot/ srw-rw---- 1 dovecot mail 0 Sep 11 15:42 auth-master srw------- 1 root wheel 0 Sep 11 15:42 auth-worker.47529 srwxrwxrwx 1 root wheel 0 Sep 11 15:42 dict-server drwxr-x--- 2 root dovecot-auth 512 Sep 11 15:42 login -rw------- 1 root wheel 6 Sep 11 15:42 master.pid ls -l /var/run/dovecot/login/ srw-rw---- 1 root dovecot-auth 0 Sep 11 15:42 default -rw-r--r-- 2 root wheel 230 Sep 11 15:41 ssl-parameters.dat And the dovecot conf: # 1.1.3: /usr/local/etc/dovecot.conf syslog_facility: local6 ssl_cert_file: /etc/ssl/mail/mail.nicoelro.net.cert ssl_key_file: /etc/ssl/mail/mail.nicoelro.net.key disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login login_user: dovecot-auth login_greeting: Mail Server login_processes_count: 2 verbose_proctitle: yes first_valid_uid: 143 last_valid_uid: 143 first_valid_gid: 143 last_valid_gid: 143 mail_access_groups: mail mail_location: maildir:/var/mail/vmail/%u/ mail_plugins: quota imap_quota imap_client_workarounds: delay-newmail outlook-idle netscape-eoh tb-extra-mailbox-sep auth default: mechanisms: plain login passdb: driver: sql args: /usr/local/etc/dovecot/dovecot-sql.conf userdb: driver: sql args: /usr/local/etc/dovecot/dovecot-sql.conf socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix master: path: /var/run/dovecot/auth-master mode: 432 user: dovecot group: mail plugin: quota: maildir sieve: /var/mail/vmail/%u/sieve Thanks for your informations. -- - Nicolas.

2 4

[Dovecot] cram-md5 and users maintaining their own passwords?
by Steinar Bang 13 Sep '08

13 Sep '08

Is there any other mechanism than using passwd files with md5-hashed passwords created by dovecotpw that will support cram-md5 authentication? Has anyone created setups where the passwd databases reside in the individual users home directories? Is it possible to persuade dovecotpw to update the passwd databases automatically. Having to use a text editor to paste in the passwords sets a high user treshold on using the cram-md5 authentication mechanism. Thanx! - Steinar

2 7

[Dovecot] Questions about using sieve
by Robin Atwood 13 Sep '08

13 Sep '08

I am trying to filter my imap mail sent to my phone by using sieve. Currently everything is set up and works well using mbox and sendmail as the lda. I have re-installed dovecot with sieve included and updated dovecot.conf, which gives # dovecot -n # 1.1.3: /etc/dovecot/dovecot.conf ssl_cert_file: /etc/ssl/dovecot/server.pem ssl_key_file: /etc/ssl/dovecot/server.key disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable: /usr/libexec/dovecot/imap-login mail_privileged_group: mail mail_location: mbox:~/mail:INBOX=/var/mail/%u auth default: passdb: driver: pam args: * userdb: driver: passwd and I have added "mail_plugins = cmusieve" to protocol lda{}. I then created a ".dovecot.sieve" script but am not sure where to place it. I tried ~/ and ~/.imap but it never seems to get compiled. Dovecot is running as a root service so it should have access. Setting mail_debug=yes produces no clues, so what should I be looking at? TIA -Robin -- ---------------------------------------------------------------------- Robin Atwood. "Ship me somewheres east of Suez, where the best is like the worst, Where there ain't no Ten Commandments an' a man can raise a thirst" from "Mandalay" by Rudyard Kipling ----------------------------------------------------------------------

3 3

[Dovecot] Dovecot Ldap Logs
by Proskurin Kirill 13 Sep '08

13 Sep '08

Hello all! One question about ldap. In my logs im see this: Info: auth(default): ldap(sysadmin(a)domain.off,172.16.1.80): user search: base=dc=CAS scope=subtree filter=(&(objectClass=mailUser)(mail=sysadmin(a)domain.off)) fields=(all) Info: auth(default): ldap(sysadmin(a)domain.off,172.16.1.80): result: accountStatus(?unknown?)= cn(?unknown?)= givenName(?unknown?)= initials(?unknown?)= l(?unknown?)= o(?unknown?)= objectClass(?unknown?)= telephoneNumber(?unknown?)= sn(?unknown?)= title(?unknown?)= uid(?unknown?)= userPassword(?unknown?)= mail(?unknown?)= --- What is that mean? And how can im get a rid of this? -- Best regards, Proskurin Kirill

2 3

[Dovecot] API Examples?
by tcowin 13 Sep '08

13 Sep '08

I need to write a little client to just get the 5 most recent email headers (and \Seen status) from the INBOX of a given user. Are there any API examples anywhere that would speed this process along, or any spots in the source that would give me a jump start? or would it be better to act as an IMAP client? Many Thanks In Advance, Tom -- View this message in context: http://www.nabble.com/API-Examples--tp19444931p19444931.html Sent from the Dovecot mailing list archive at Nabble.com.

2 1

[Dovecot] version 1.1.3 assertion on index-sort-string
by Nuno Lopes 13 Sep '08

13 Sep '08

Hi, I am seeing the following log lines on some accounts on my setup: Sep 11 01:42:36 xxxx dovecot: Panic: IMAP(xxxxxxxxxxxxxxxx): file index-sort-string.c: line 610 (index_sort_add_ids_range): assertion failed: (skip > 0) Sep 11 01:42:36 xxxx dovecot: IMAP(xxxxxxxxxxxxxx): Raw backtrace: imap [0x5555555d3690] -> imap [0x5555555d36f7] -> imap [0x5555555d2d58] -> imap(index_sort_list_finish_string+0xf13) [0x5555555a04b3] -> imap(index_storage_search_next_nonblock+0x432) [0x55555559cd22] -> imap(mailbox_search_next+0x21) [0x5555555a42b1] -> imap(imap_sort+0xdc) [0x555555577ddc] -> imap(cmd_sort+0x33d) [0x555555570ead] -> imap(cmd_uid+0x54) [0x555555571934] -> imap [0x55555557234c] -> imap [0x555555572402] -> imap [0x555555572c1f] -> imap(client_input+0x62) [0x555555572e42] -> imap(io_loop_handler_run+0xf8) [0x5555555da6d8] -> imap(io_loop_run+0x1d) [0x5555555d972d] -> imap(main+0x462) [0x55555557a5f2] -> /lib64/libc.so.6(__libc_start_main+0xf4) [0x2b7c871d8154] -> imap [0x55555556c8c9] these assertions happen when ordering by from and go away by deleting index files. As usual if you wish I can send you the index files as they were when this error happened. Thanks, -- Nuno Lopes

2 2

[Dovecot] Dovecot 1.1.3 Kerberos5 GSSAPI bug (with patch)
by Matthew Wesley 12 Sep '08

12 Sep '08

The functionality added in changeset 818a638fa9a3 has a bug for x86_64 on line 103. The src/auth/mech-gssapi.c file must now include stdlib.h to have the declaration for getenv(). Otherwise, the compiler uses the implicit return type (int), which truncates the 8-byte pointer getenv() returns to a 4-byte value. This causes a segfault on subsequent reads. Here is debugger output illustrating the problem: (gdb) list 106 101 const char *path; 102 103 path = getenv("KRB5_KTNAME"); 104 if (path != NULL) { 105 #ifdef HAVE_GSSKRB5_REGISTER_ACCEPTOR_IDENTITY 106 gsskrb5_register_acceptor_identity(path); 107 #elif defined (HAVE_KRB5_GSS_REGISTER_ACCEPTOR_IDENTITY) 108 krb5_gss_register_acceptor_identity(path); 109 #endif 110 } (gdb) p/x getenv("KRB5_KTNAME") $32 = 0xb0d7aef7 (gdb) x/s 0xb0d7aef7 0xb0d7aef7: <Address 0xb0d7aef7 out of bounds> (gdb) x/s 0x7fffb0d7aef7 0x7fffb0d7aef7: "/etc/dovecot/dovecot.keytab" A Mercurial bundle with a fix is attached, and here is the trivial patch to put in the needed #include: diff -r 43e55b9af85b src/auth/mech-gssapi.c --- a/src/auth/mech-gssapi.c Mon Sep 01 15:02:49 2008 +0300 +++ b/src/auth/mech-gssapi.c Wed Sep 03 11:37:33 2008 -0400 @@ -22,6 +22,8 @@ #include "safe-memset.h" #ifdef HAVE_GSSAPI + +#include <stdlib.h> #ifndef HAVE___GSS_USEROK # define USE_KRB5_USEROK -- UNIX was not designed to stop you from doing stupid things, because that would also stop you from doing clever things. -- Doug Gwyn

2 2

[Dovecot] error in 1.1.2
by Cor Bosman 12 Sep '08

12 Sep '08

Ive been getting a LOT of these errors since 1.1.2: So far ive seen this with 1800 customers, and we're getting active complaints about errors in imap clients. When I check the users log I always see this error.. This always happens with COPY commands in Squirrelmail. Sep 2 20:09:35 userimap4.xs4all.nl dovecot: IMAP(xxxxxxx): rename(/var/spool/mail/dovecot-control/indexes/j/jd/xxxxxxx/.Inveztor/dovecot.index.cache.lock, /var/spool/mail/dovecot-control/indexes/j/jd/xxxxxxx/.Inveztor/dovecot.index.cache) failed: No such file or directory Sep 2 20:09:35 userimap4.xs4all.nl dovecot: IMAP(xxxxxxx): rename(/var/spool/mail/dovecot-control/indexes/j/jd/xxxxxxx/.Inveztor/dovecot.index.cache.lock, /var/spool/mail/dovecot-control/indexes/j/jd/xxxxxxx/.Inveztor/dovecot.index.cache) failed: No such file or directory Sep 2 20:09:35 userimap4.xs4all.nl dovecot: IMAP(xxxxxxx): file_dotlock_replace() failed with index cache file /var/spool/mail/dovecot-control/indexes/j/jd/xxxxxxx/.Inveztor/dovecot.index.cache: No such file or directory Sep 2 20:09:35 userimap4.xs4all.nl dovecot: IMAP(xxxxxxx): file_dotlock_replace() failed with index cache file /var/spool/mail/dovecot-control/indexes/j/jd/xxxxxxx/.Inveztor/dovecot.index.cache: No such file or directory Sep 1 20:14:06 userimap4.xs4all.nl dovecot: IMAP(xxxxxxx): rename(/var/spool/mail/dovecot-control/indexes/j/jd/xxxxxxx/.Inveztor/dovecot.index.cache.lock, /var/spool/mail/dovecot-control/indexes/j/jd/xxxxxxx/.Inveztor/dovecot.index.cache) failed: No such file or directory Sep 1 20:14:06 userimap4.xs4all.nl dovecot: IMAP(xxxxxxx): rename(/var/spool/mail/dovecot-control/indexes/j/jd/xxxxxxx/.Inveztor/dovecot.index.cache.lock, /var/spool/mail/dovecot-control/indexes/j/jd/xxxxxxx/.Inveztor/dovecot.index.cache) failed: No such file or directory Sep 1 20:14:06 userimap4.xs4all.nl dovecot: IMAP(xxxxxxx): file_dotlock_replace() failed with index cache file /var/spool/mail/dovecot-control/indexes/j/jd/xxxxxxx/.Inveztor/dovecot.index.cache: No such file or directory Sep 1 20:14:06 userimap4.xs4all.nl dovecot: IMAP(xxxxxxx): file_dotlock_replace() failed with index cache file /var/spool/mail/dovecot-control/indexes/j/jd/xxxxxxx/.Inveztor/dovecot.index.cache: No such file or directory FreeBSD 6.2, NFS storage for everything. Any idea? Cor

6 41

[Dovecot] Dovecot 1.1.12 ignores auth_krb5_keytab settings
by christop 12 Sep '08

12 Sep '08

Hello, i am using here a FreeBSD 7.0 amd64 with latest dovecot from ports. It ignores the krb5_keytab settings, which looks like this in the logs: dovecot: Aug 02 18:56:54 Error: auth(default): gssapi(?,130.149.58.145): While processing incoming data: Miscellaneous failure (see text) dovecot: Aug 02 18:56:54 Error: auth(default): gssapi(?,130.149.58.145): While processing incoming data: /etc/krb5.keytab: No such file or directory dovecot: Aug 02 18:56:59 Info: imap-login: Aborted login (auth failed, 1 attempts): method=GSSAPI, rip=130.149.58.145, lip=130.149.58.162, TLS It is the same errror i got with dovecot 1.0.13. MfG Christoph Below my config: # 1.1.2: /usr/local/etc/dovecot.conf log_path: /var/log/dovecot.log protocols: imaps managesieve listen: mail2.physik-pool.tu-berlin.de ssl_cert_file: /etc/CERT ssl_key_file: /etc/KEY 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(managesieve): /usr/local/libexec/dovecot/managesieve-login verbose_proctitle: yes first_valid_uid: 200 mail_privileged_group: mail mail_location: maildir:~/maildir:INDEX=/var/dovecot/%1n/%n 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(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(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(managesieve): sieve_storage(default): sieve_storage(imap): sieve_storage(managesieve): ~/sieve sieve(default): sieve(imap): sieve(managesieve): ~/.dovecot.sieve namespace: type: private separator: / inbox: yes list: yes subscriptions: yes namespace: type: private separator: / prefix: mail/ location: mbox:~/mail list: yes subscriptions: yes auth default: mechanisms: gssapi plain login krb5_keytab: /etc/mail2.krb5.keytab worker_max_count: 120 passdb: driver: pam userdb: driver: passwd args: [blocking=yes]

2 4

[Dovecot] Public (Shared Folders) ACL Questions
by Mailing List 11 Sep '08

11 Sep '08

I'm trying to set up a public namespace so that a set of IMAP folders are available to all staff - similar to MS Exchange Public Folders. I've managed to set up the namespace correctly but I'm having trouble with the ACLs. The global ACL file is the only method I can get to work. All I want to do is to allow 1 user admin privileges to create & delete anything but all other users should only be able to create not delete. Reading through the mailing list I thought a /etc/dovecot-acls/.DEFAULT file would be suitable but what should be put in here to achieve what I want? Are you able to use wildcards somehow within this file, i.e.: ---------------------------------------- owner lrwstiekxa user=admin(a)domain.com lrwstiekxa user=*(a)domain.com lrw ---------------------------------------- Does this .DEFAULT file only apply to the public (shared) namespace or will it effect private mailboxes also? If I was to create a specific global acl file for a specific folder which would take precedence, the .DEFAULT acls or the specific folder acls? Also an "INBOX" is shown within the public folders namespace but no folder exists in the public folders maildir hierarchy - any ideas how I can stop this? Any help would be greatly appreciated. Gavin

2 1

[Dovecot] Stumped on adding X-Header...
by Brian Hayden 11 Sep '08

11 Sep '08

Recently I posted about wanting to add an x-header recording a timestamp for changing the \Deleted flag, for purposes of doing expiry on mbox mailboxes. Timo replied: > Be sure to add it to mbox_hide_headers[] and mbox_save_drop_headers[] > arrays in mbox-storage.c and hope that it doesn't exist in any of your > existing mails. :) Other than that there shouldn't be problems. I looked at the two places where X-Status was being written--mbox-save.c and mbox-sync-update.c--and tried adding this header. It didn't work. To test my sanity, I changed the string 'X-Status' in each of these to something else. The mbox file still ended up with 'X-Status' written in it, and I can't for the life of me find any other code that might write that string. Timo? Anyone? -- Brian Hayden UMN OIT Internet Services

2 1

[Dovecot] 1.1.3 panics
by Dean Brooks 11 Sep '08

11 Sep '08

Hi, Installed Dovecot 1.1.3 today and started receiving panic errors on a few of our users: dovecot: [ID 107833 mail.crit] Panic: IMAP(xx): file mail-index-transaction-view.c: line 204: unreached When I upgraded, I deleted all of our users index files so it started with a clean slate. We are running mbox format over NFS with fsquota plugin on Solaris 8. Here is output of dovecot -n: base_dir: /var/run/dovecot/ protocols: imap ssl_disable: yes disable_plaintext_auth: no login_dir: /var/run/dovecot//login login_executable: /usr/local/dovecot/libexec/dovecot/imap-login login_user: daemon login_log_format_elements: user=%u ip=%r 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 debug_passwords: yes passdb: driver: shadow userdb: driver: passwd plugin: quota: fs -- Dean Brooks dean(a)iglou.com

3 8

[Dovecot] SSL fields as variables for SQL statements ...
by XhE 11 Sep '08

11 Sep '08

Hi, I was wondering if there is any possibility to access the status if a user has provided a certificate, that has been accepted or not via variables. And further if there is any way to get the value of SSL certificate fields by use variables. I'd like to use those variables in sql statements. I then could assign a single certificate to a user, and make up passdb sql statements, that allow him to access multiple (but not all) mailboxes without the need to issue any further certificates. --- Michael

2 2

[Dovecot] How to propelry restore a Maildir
by Thomas Hummel 11 Sep '08

11 Sep '08

Hello, I would like to know what is the proper way to restore a Maildir : Assuming someone has got a foobar/[cur|new|tmp] maildir, loses for some reason its content and that some new mail (seen and/or unseen) comes into that mailbox inbetween (that is before the restore procedure takes place, thus creating the need to merge restored messages and new ones). I'd like to check the following (I don't use deliver but procmail) : 1. the messages filenames are unique in time (meaning that a new message cannot be assigned a name already existing in the backup (the name of an old message), at least for the same mailbox instance : if that's not the case : how can we merge safely ? 2. what naming scheme is used (the left part of the name, before the :2,) ? I've got something like : 1215166123.52887_0.host.dom.ain:2,[...] what are the 1215166123, the 52887 and 0 ? 3. what can we deduce from the last modified date of the file as seen in ls -l ? . when in new/, is it the same as the one in the Received: header or is it when in tmp/ ? . when in cur/, is it the date the client "saw" the message ? What would "saw" mean in that case ? 4. should the dovecot-uidlist and dovecot-keywords be updated after the restore or is it better to let dovecot rearrange them itself ? 5. same question for the index and cache files ? Thanks -- Thomas Hummel | Institut Pasteur <hummel(a)pasteur.fr> | Pôle informatique - systèmes et réseau

3 8

[Dovecot] Panic in Dovecot 1.1.3: index-mail.c: line 1091: assertion failed: (!mail->data.destroying_stream)
by Peter Eriksson 11 Sep '08

11 Sep '08

Dovecot 1.1.3 Solaris 10 SPARC (Sun Fire T1000) Compiled with Sun Studio 12 compilers. Maildir on NFS Indexes on local disk (UFS). 'dovecot -n' output attached. IMAP process crashes for certain (many, but not all) users when accessing certain folders (in the example below, in crashes when accessing my INBOX, about 1700 mails). I could access other mailboxes without problems. And a simple telnet to the imap port followed by a login works fine. Erased the coredumps (was filling up the system too quickly) so I can't really produce a backtrace right now (had to back down to 1.0.13 again even though that one has another core-dump-generating problem - but that is atleast limited to only one specific user so far). Going to set up a separate test server to test things more without disturbing our normal operations... I started with an empty INDEX directory to make sure there weren't problems with old corrupted indexes. Output from syslog: Sep 9 12:34:44 ifm.liu.se dovecot: [ID 107833 mail.info] imap-login: Login: user=<peter>, method=GSSAPI, rip=130.236.160.102, lip=130.236.160.6, secured Sep 9 12:34:44 ifm.liu.se dovecot: [ID 107833 mail.crit] Panic: IMAP(peter): file index-mail.c: line 1091: assertion failed: (!mail->data.destroying_stream) Sep 9 12:34:44 ifm.liu.se dovecot: [ID 107833 mail.error] IMAP(peter): Raw backtrace: 0x1000b5188 -> 0x1000605ac -> 0x1000605e4 -> 0x100060734 -> 0x1000657b8 -> 0x100070470 -> 0x1000204e0 -> 0x100020868 -> 0x100016e78 -> 0x10001dab8 -> 0x10001debc -> 0x10001e0a4 -> 0x1000bf4b4 -> 0x1000bea68 -> 0x10002933c -> 0x100014c9c Sep 9 12:34:48 ifm.liu.se dovecot: [ID 107833 mail.info] auth(default): client out: OK 1 user=peter Sep 9 12:34:48 ifm.liu.se dovecot: [ID 107833 mail.info] auth(default): passwd(peter,130.236.160.102): lookup Sep 9 12:34:48 ifm.liu.se dovecot: [ID 107833 mail.info] auth(default): master out: USER 241 peter system_user=peter uid=103 gid=10 home=/home/peter Sep 9 12:34:48 ifm.liu.se dovecot: [ID 107833 mail.info] imap-login: Login: user=<peter>, method=GSSAPI, rip=130.236.160.102, lip=130.236.160.6, secured Sep 9 12:34:48 ifm.liu.se dovecot: [ID 107833 mail.crit] Panic: IMAP(peter): file index-mail.c: line 1091: assertion failed: (!mail->data.destroying_stream) Sep 9 12:34:48 ifm.liu.se dovecot: [ID 107833 mail.error] IMAP(peter): Raw backtrace: 0x1000b5188 -> 0x1000605ac -> 0x1000605e4 -> 0x100060734 -> 0x1000657b8 -> 0x100070470 -> 0x1000204e0 -> 0x100020868 -> 0x100016e78 -> 0x10001dab8 -> 0x10001debc -> 0x10001e0a4 -> 0x1000bf4b4 -> 0x1000bea68 -> 0x10002933c -> 0x100014c9c - Peter # 1.1.3: /etc/dovecot.conf.new base_dir: /var/run/dovecot/ protocols: imap pop3 imaps pop3s ssl_ca_file: /ifm/etc/certs/dovecot-CA.cert.pem ssl_cert_file: /ifm/etc/certs/dovecot-ifm.cert.pem ssl_key_file: /ifm/etc/certs/dovecot-ifm.key.pem login_dir: /var/run/dovecot/login login_executable(default): /ifm/libexec/dovecot/imap-login login_executable(imap): /ifm/libexec/dovecot/imap-login login_executable(pop3): /ifm/libexec/dovecot/pop3-login login_greeting: Welcome to the IFM Dovecot Server. first_valid_uid: 100 mail_location: maildir:Maildir:INDEX=/var/indexes/%u mmap_disable: yes mail_nfs_storage: yes mail_nfs_index: yes mbox_write_locks: fcntl mail_executable(default): /ifm/libexec/dovecot/imap mail_executable(imap): /ifm/libexec/dovecot/imap mail_executable(pop3): /ifm/libexec/dovecot/pop3 mail_plugin_dir(default): /ifm/lib/dovecot/imap mail_plugin_dir(imap): /ifm/lib/dovecot/imap mail_plugin_dir(pop3): /ifm/lib/dovecot/pop3 imap_client_workarounds(default): outlook-idle delay-newmail imap_client_workarounds(imap): outlook-idle delay-newmail imap_client_workarounds(pop3): pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh namespace: type: private separator: / inbox: yes list: yes subscriptions: yes namespace: type: private separator: / prefix: mail/ hidden: yes subscriptions: yes namespace: type: private separator: / prefix: Mail/ hidden: yes subscriptions: yes namespace: type: private separator: / prefix: ~/mail/ hidden: yes subscriptions: yes namespace: type: private separator: / prefix: ~/Mail/ hidden: yes subscriptions: yes namespace: type: private separator: / prefix: ~%u/mail/ hidden: yes subscriptions: yes namespace: type: private separator: / prefix: ~%u/Mail/ hidden: yes subscriptions: yes auth default: mechanisms: plain login gssapi executable: /ifm/libexec/dovecot/dovecot-auth verbose: yes debug: yes passdb: driver: pam userdb: driver: passwd

3 11

[Dovecot] Panic: file sieve-cmu.c: line 262 (part_save): assertion failed: (buf->used - 1 == part->body_size.physical_size)
by Maciej Polewczyński 11 Sep '08

11 Sep '08

Hello Dovecot v1.1.3 Sieve plugin v1.1.5 Debian Lenny Virtual users in mysql db dovecot -n at the end of email I have problem with sieve body rules during delivery. When I test rule if body :raw :contains [ ".exe" ] { discard; } deliver die with panic: Sep 10 15:14:37 mail deliver(user): Panic: file sieve-cmu.c: line 262 (part_save): assertion failed: (buf->used - 1 == part->body_size.physical_size) Sep 10 15:14:37 mail deliver(user): Raw backtrace: /usr/local/libexec/dovecot/deliver [0x80ca1a1] -> /usr/local/libexec/dovecot/deliver(i_syslog_fatal_handler+0x34) [0x80ca274] -> /usr/local/libexec/dovecot/deliver [0x80c9bb9] -> /usr/local/lib/dovecot/lda/lib90_cmusieve_plugin.so [0xb7e44bce] -> /usr/local/lib/dovecot/lda/lib90_cmusieve_plugin.so [0xb7e44fc4] -> /usr/local/lib/dovecot/lda/lib90_cmusieve_plugin.so [0xb7e4ef4a] -> /usr/local/lib/dovecot/lda/lib90_cmusieve_plugin.so(sieve_eval_bc+0x3a8) [0xb7e50558] -> /usr/local/lib/dovecot/lda/lib90_cmusieve_plugin.so(sieve_execute_bytecode+0xe2) [0xb7e56282] -> /usr/local/lib/dovecot/lda/lib90_cmusieve_plugin.so(cmu_sieve_run+0x326) [0xb7e46166] -> /usr/local/lib/dovecot/lda/lib90_cmusieve_plugin.so [0xb7e43bf6] -> /usr/local/libexec/dovecot/deliver(main+0x111a) [0x805dfda] -> /lib/i686/cmov/libc.so.6(__libc_start_main+0xe5) [0xb7e81455] -> /usr/local/libexec/dovecot/deliver [0x805bc11] Is there a bug or I have done something wrong. /usr/local/sbin/dovecot -n # 1.1.3: /usr/local/etc/dovecot.conf base_dir: /var/run/dovecot/ log_timestamp: %Y-%m-%d %H:%M:%S protocols: imap imaps pop3 pop3s disable_plaintext_auth: no 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 first_valid_uid: 150 mail_privileged_group: mail mail_location: maildir:%h/Maildir mail_debug: 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_plugins(default): quota imap_quota mail_plugins(imap): quota imap_quota mail_plugins(pop3): quota 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 imap_client_workarounds(default): delay-newmail imap_client_workarounds(imap): delay-newmail 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 username_chars: abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@+% debug: yes passdb: driver: sql args: /usr/local/etc/dovecot-sql.user.conf passdb: driver: sql args: /usr/local/etc/dovecot-sql.alias.conf userdb: driver: sql args: /usr/local/etc/dovecot-sql.user.conf userdb: driver: sql args: /usr/local/etc/dovecot-sql.alias.conf socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix master: path: /var/run/dovecot/auth-master mode: 384 user: vmail plugin: quota: maildir -- Pozdrowienia Maciej Polewczynski Registered Linux user #117725

1 0

[Dovecot] Support of client specific flags?
by Steinar Bang 11 Sep '08

11 Sep '08

Gnus use a lot of custom flags to represent the messages state wrt. Gnus. How well are these flags supported in dovecot? How fast are access to them? (Ie. will dovecot have to open the message and parse the headers) Are they supported when using imapsync to transfer messages from a different IMAP server? (I guess I'll find out soon, because I'm using imapsync to transfer messages from a cyrus imap daemon to a dovecot one, as I'm writing this)

2 2

[Dovecot] 1.2.alpha1: file_dotlock_open() failed with subscription file
by Frank Elsner 11 Sep '08

11 Sep '08

Hi *, running dovecot 1.2.alpha1 I find the following messages in the log: Sep 10 01:28:38 seymour dovecot: IMAP(steffen,192.168.28.31): fchown(/home/Mail/steffen/subscriptions.lock) failed: Operation not permitted Sep 10 01:28:38 seymour dovecot: IMAP(steffen,192.168.28.31): file_dotlock_open() failed with subscription file /home/Mail/steffen/subscriptions: Operation not permitted Sep 10 01:28:38 seymour dovecot: IMAP(steffen,192.168.28.31): fchown(/home/Mail/steffen/subscriptions.lock) failed: Operation not permitted Sep 10 01:28:38 seymour dovecot: IMAP(steffen,192.168.28.31): file_dotlock_open() failed with subscription file /home/Mail/steffen/subscriptions: Operation not permitted Sep 10 01:28:52 seymour dovecot: IMAP(steffen,192.168.28.31): fchown(/home/Mail/steffen/subscriptions.lock) failed: Operation not permitted Sep 10 01:28:52 seymour dovecot: IMAP(steffen,192.168.28.31): file_dotlock_open() failed with subscription file /home/Mail/steffen/subscriptions: Operation not permitted File permissions are: -rw------- 1 steffen elsner 124 Aug 22 12:51 /home/Mail/steffen/subscriptions And finally the output of "dovecot -n" reads: # 1.2.alpha1: /usr/local/dovecot/etc/dovecot.conf base_dir: /var/run/dovecot/ ssl_cert_file: /usr/local/etc/seymour.crt ssl_key_file: /usr/local/etc/seymour.key disable_plaintext_auth: no login_dir: /var/run/dovecot//login login_executable: /usr/dovecot/libexec/dovecot/imap-login login_greeting: c64.shuttle.de - Dovecot ready. login_log_format_elements: %u %r %c login_processes_count: 2 verbose_proctitle: yes first_valid_uid: 100 last_valid_uid: 65534 mail_location: maildir:/home/Mail/%u:INDEX=MEMORY maildir_copy_preserve_filename: yes mail_executable: /usr/dovecot/libexec/dovecot/imap mail_plugin_dir: /usr/dovecot/lib/dovecot/imap mail_log_prefix: %Us(%u,%r): mail_log_max_lines_per_sec: 100 imap_client_workarounds: netscape-eoh tb-extra-mailbox-sep imap_logout_format: [%i/%o] auth default: executable: /usr/dovecot/libexec/dovecot/dovecot-auth master_user_separator: / passdb: driver: pam args: dovecot passdb: driver: passwd-file args: /usr/dovecot/etc/masters userdb: driver: passwd plugin: mail_log_events: delete undelete expunge copy mailbox_delete What's behind? Critical? How to solve? Regards, Frank Elsner

3 4

Re: [Dovecot] Panic: IMAP: Trying to allocate 2273345672 bytes
by Mark Zealey 11 Sep '08

11 Sep '08

> > About our setup: These are on an nfs-mounted file system. > It's shared > > between two computers and connections are randomly > redirected to either > > box; so potentially it could be an nfs type corruption > issue. Timo, I'll > > send you a tarball of the dovecot* files off-list > > Sounds like it could be because of NFS caching issues. You've set > mail_nfs_index=yes, right? What OS? Linux should be OK, but > FreeBSD has > some issues. Thanks for the patch; I've not seen any issues to do with nfs caching before and we've had this live on very heavily loaded systems for several months now. We use exim with deliver to deliver the messages (maildir only). Relevant config: mail_location: maildir:~/Maildir mmap_disable: yes mail_nfs_storage: yes mail_nfs_index: yes lock_method: dotlock maildir_copy_preserve_filename: yes Linux (centos5.2 w/updates). Mount options: rw,noatime,nodiratime,hard,intr,rsize=32768,wsize=32768,tcp,nocto Mark

1 0