August 2010 - dovecot

[Dovecot] restricting access by reverse domain name
by Phil Howard 09 Aug '10

09 Aug '10

Is there a feature or plugin to restrict access to IMAP/POP service by the domain name in reverse lookup? It would be even better if this restriction can exclude certain users (e.g. some users can access IMAP from certain networks but other users cannot). -- sHiFt HaPpEnS!

2 2

[Dovecot] Dovecot 2.0.rc4 not generating ssl-parameters.dat on first start
by Andreas M. Kirchwitz 09 Aug '10

09 Aug '10

Dear Dovecot lovers! When starting Dovecot 1.x the first time, it runs "ssl-build-params" to generate a file named "ssl-parameters.dat". This takes a couple of minutes. During this time users have no access to their mail, but this can be planned in advance and users can be notified. This is explained in http://wiki.dovecot.org/SSL/DovecotConfiguration With Dovecot 2.0.rc4, the new command "ssl-params" seems to do this job, but unfortunately it isn't run on first start of Dovecot but the start is delayed until a user connects to port 993 (or does STARTTLS in 143). According to http://wiki2.dovecot.org/SSL/DovecotConfiguration it should behave the same way as Dovecot 1 did. So, with Dovecot 2.0.rc4 it hits the first user who wants to establish a secure connection. It's hard to explain this to users. ;-) Of course, I could simply run "telnet <imaphost> 993" manually after installation. I also tried running "ssl-params" manually before starting Dovecot but it stays in foreground forever and doesn't seem to finish (what is it waiting for?) So it would be really great if Dovecot 2 could do this on its own like Dovecot 1 did. Besides that, Dovecot 2.0 runs like a charm ... Andreas

2 1

[Dovecot] quotactl failed with disk quotas and dovecot 2.0
by Patrick McLean 09 Aug '10

09 Aug '10

Hi, I have a machine running dovecot 2.0 rc4 and I can't seem to get the imap_quota plugin working, every time I try to read the quotas, I get the following in my log: > Aug 7 11:58:43 talyn dovecot: imap(chutz): Error: quotactl(Q_GETQUOTA, rootfs) failed: No such file or directory > Aug 7 11:59:53 talyn dovecot: imap(chutz): Error: quotactl(Q_GETQUOTA, rootfs) failed: No such file or directory > Aug 7 11:59:54 talyn dovecot: imap(chutz): Error: quotactl(Q_GETQUOTA, rootfs) failed: No such file or directory (Once for each try) Here is the output of dovecot -n: > # 2.0.rc4: /etc/dovecot/dovecot.conf > # OS: Linux 2.6.34-gentoo-r3 i686 Gentoo Base System release 2.0.1 > listen = * > mail_location = mdbox:~/.mdbox > mail_plugins = acl quota zlib trash imap_quota > managesieve_notify_capability = mailto > managesieve_sieve_capability = comparator-i;octet comparator-i;ascii-casemap fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date spamtest spamtestplus virustest > passdb { > args = * > driver = pam > } > plugin { > quota = fs:User quota:user > quota_warning = storage=80%% quota-warning 80 %u > sieve = ~/.dovecot.sieve > sieve_dir = ~/.sieve > } > protocols = imap lmtp > service auth { > unix_listener /var/spool/postfix/private/auth { > group = postfix > mode = 0660 > user = postfix > } > } > ssl_cert = </etc/ssl/dovecot/server.pem > ssl_key = </etc/ssl/dovecot/server.key > userdb { > driver = passwd > } > verbose_proctitle = yes > protocol lda { > mail_plugins = sieve quota > }

2 3

[Dovecot] OT Thunderbird
by Benny Pedersen 09 Aug '10

09 Aug '10

some senders on this maillist use a version of thunderbird that adds more then one references header and this imho breaks threading :( -- xpoint

7 14

[Dovecot] IMAP namespace and Courier migration
by Yves Goergen 09 Aug '10

09 Aug '10

Hello, the migration guide from Courier-IMAP to Dovecot says that I should change the folders namespace to "INBOX." if I want a seamless migration. Isn't it that e-mail clients determine that namespace automatically? At least I never needed to enter one in Thunderbird and then it was there. What happens if I copy the database, all the Maildir files, run the migration script to convert the special files and don't change that namespace - will clients show an error message and stop working or will it still work? -- Yves Goergen "LonelyPixel" <nospam.list(a)unclassified.de> Visit my web laboratory at http://beta.unclassified.de

2 1

[Dovecot] Dovecot 2.0.rc4 core dumped with Alpine 2.00
by Andreas M. Kirchwitz 09 Aug '10

09 Aug '10

Hi Timo and all others! The current Dovecot 2.0.rc4 did really well with Mutt 1.5.20 and Thunderbird 3.1.2, but a user with Alpine 2.00 crashed it immediately. I'm running Fedora 13 (Linux) and compiled Dovecot 2.0.rc4 manually like I did before with Dovecot 1.2.13. When switching from 1.2 to 2.0 I removed all those ".imap" folders with internal cache data (didn't know for sure if it's compatible between both version). All folders are in mbox format. When Alpine is started, the first crash happens. Alpine notifies the user that there was a problem connecting the IMAP server. No mail is display. And then the second crash happens. Looks like Alpine starts a second try to connect to the IMAP server before displaying the (empty) screen with (no) folders. Excerpt from syslog: Aug 8 18:07:56 mailserver dovecot: imap-login: Login: user=<mailuser>, method=CRAM-MD5, rip=138.201.2.2, lip=138.201.2.2, mpid=2676, TLS Aug 8 18:07:56 mailserver dovecot: imap(mailuser): Panic: file istream-header-filter.c: line 81 (read_mixed): assertion failed: (pos > 0) Aug 8 18:07:56 mailserver dovecot: imap(mailuser): Error: Raw backtrace: /usr/local/Dovecot-2.0.rc4/lib/dovecot/libdovecot.so.0(+0x350c1) [0xa410c1] -> /usr/local/Dovecot-2.0.rc4/lib/dovecot/libdovecot.so.0(+0x3512f) [0xa4112f] -> /usr/local/Dovecot-2.0.rc4/lib/dovecot/libdovecot.so.0(i_error+0) [0xa1b46e] -> /usr/local/Dovecot-2.0.rc4/lib/dovecot/libdovecot.so.0(+0x1f373) [0xa2b373] -> /usr/local/Dovecot-2.0.rc4/lib/dovecot/libdovecot.so.0(+0x1f4ff) [0xa2b4ff] -> /usr/local/Dovecot-2.0.rc4/lib/dovecot/libdovecot.so.0(i_stream_read+0x77) [0xa47967] -> /usr/local/Dovecot-2.0.rc4/lib/dovecot/libdovecot.so.0(i_stream_read_copy_from_parent+0x9a) [0xa47dfa] -> /usr/local/Dovecot-2.0.rc4/lib/dovecot/libdovecot-storage.so.0(+0x60520) [0x1ef520] -> /usr/local/Dovecot-2.0.rc4/lib/dovecot/libdovecot.so.0(i_stream_read+0x77) [0xa47967] -> /usr/local/Dovecot-2.0.rc4/lib/dovecot/libdovecot.so.0(i_stream_read_data+0x3e) [0xa47c8e] -> /usr/local/Dovecot-2.0.rc4/lib/dovecot/libdovecot.so.0(message_parse_header_next+0x78) [0xa2eb08] -> /usr/local/Dovecot-2.0.rc4/lib/dovecot/libdovecot.so.0(+0x2472a) [0xa3072a] -> /usr/local/Dovecot-2.0.rc4/lib/dovecot/libdovecot.so.0(message_parser_parse_next_block+0x32) [0xa2fc82] -> /usr/local/Dovecot-2.0.rc4/lib/dovecot/libdovecot.so.0(message_parser_parse_header+0x2c) [0xa2fe8c] -> /usr/local/Dovecot-2.0.rc4/lib/dovecot/libdovecot-storage.so.0(index_mail_parse_headers+0x102) [0x1f40d2] -> /usr/local/Dovecot-2.0.rc4/lib/dovecot/libdovecot-storage.so.0(+0x6571a) [0x1f471a] -> /usr/local/Dovecot-2.0.rc4/lib/dovecot/libdovecot-storage.so.0(index_mail_get_first_header+0x3d) [0x1f4a6d] -> /usr/local/Dovecot-2.0.rc4/lib/dovecot/libdovecot-storage.so.0(mail_get_first_header+0x25) [0x1ab2a5] -> /usr/local/Dovecot-2.0.rc4/lib/dovecot/libdovecot-storage.so.0(+0x61a31) [0x1f0a31] -> /usr/local/Dovecot-2.0.rc4/lib/dovecot/libdovecot-storage.so.0(index_mail_get_date+0x68) [0x1f2008] -> /usr/local/Dovecot-2.0.rc4/lib/dovecot/libdovecot-storage.so.0(mail_get_date+0x25) [0x1ab1f5] -> /usr/local/Dovecot-2.0.rc4/lib/dov Aug 8 18:07:56 mailserver dovecot: master: Error: service(imap): child 2676 killed with signal 6 (core dumped) Aug 8 18:08:02 mailserver dovecot: imap-login: Login: user=<mailuser>, method=CRAM-MD5, rip=138.201.2.2, lip=138.201.2.2, mpid=2682, TLS Aug 8 18:08:02 mailserver dovecot: imap(mailuser): Panic: file istream-header-filter.c: line 81 (read_mixed): assertion failed: (pos > 0) Aug 8 18:08:02 mailserver dovecot: imap(mailuser): Error: Raw backtrace: /usr/local/Dovecot-2.0.rc4/lib/dovecot/libdovecot.so.0(+0x350c1) [0x81d0c1] -> /usr/local/Dovecot-2.0.rc4/lib/dovecot/libdovecot.so.0(+0x3512f) [0x81d12f] -> /usr/local/Dovecot-2.0.rc4/lib/dovecot/libdovecot.so.0(i_error+0) [0x7f746e] -> /usr/local/Dovecot-2.0.rc4/lib/dovecot/libdovecot.so.0(+0x1f373) [0x807373] -> /usr/local/Dovecot-2.0.rc4/lib/dovecot/libdovecot.so.0(+0x1f4ff) [0x8074ff] -> /usr/local/Dovecot-2.0.rc4/lib/dovecot/libdovecot.so.0(i_stream_read+0x77) [0x823967] -> /usr/local/Dovecot-2.0.rc4/lib/dovecot/libdovecot.so.0(i_stream_read_copy_from_parent+0x9a) [0x823dfa] -> /usr/local/Dovecot-2.0.rc4/lib/dovecot/libdovecot-storage.so.0(+0x60520) [0x1a1520] -> /usr/local/Dovecot-2.0.rc4/lib/dovecot/libdovecot.so.0(i_stream_read+0x77) [0x823967] -> /usr/local/Dovecot-2.0.rc4/lib/dovecot/libdovecot.so.0(i_stream_read_data+0x3e) [0x823c8e] -> /usr/local/Dovecot-2.0.rc4/lib/dovecot/libdovecot.so.0(message_parse_header_next+0x78) [0x80ab08] -> /usr/local/Dovecot-2.0.rc4/lib/dovecot/libdovecot.so.0(+0x2472a) [0x80c72a] -> /usr/local/Dovecot-2.0.rc4/lib/dovecot/libdovecot.so.0(message_parser_parse_next_block+0x32) [0x80bc82] -> /usr/local/Dovecot-2.0.rc4/lib/dovecot/libdovecot.so.0(message_parser_parse_header+0x2c) [0x80be8c] -> /usr/local/Dovecot-2.0.rc4/lib/dovecot/libdovecot-storage.so.0(index_mail_parse_headers+0x102) [0x1a60d2] -> /usr/local/Dovecot-2.0.rc4/lib/dovecot/libdovecot-storage.so.0(+0x6571a) [0x1a671a] -> /usr/local/Dovecot-2.0.rc4/lib/dovecot/libdovecot-storage.so.0(index_mail_get_first_header+0x3d) [0x1a6a6d] -> /usr/local/Dovecot-2.0.rc4/lib/dovecot/libdovecot-storage.so.0(mail_get_first_header+0x25) [0x15d2a5] -> /usr/local/Dovecot-2.0.rc4/lib/dovecot/libdovecot-storage.so.0(+0x61a31) [0x1a2a31] -> /usr/local/Dovecot-2.0.rc4/lib/dovecot/libdovecot-storage.so.0(index_mail_get_date+0x68) [0x1a4008] -> /usr/local/Dovecot-2.0.rc4/lib/dovecot/libdovecot-storage.so.0(mail_get_date+0x25) [0x15d1f5] -> /usr/local/Dovecot-2.0.rc4/lib/dov Aug 8 18:08:02 mailserver dovecot: master: Error: service(imap): child 2682 killed with signal 6 (core dumped) Is this information enough to track down the problem or do you want me to run additional tests? Just let me know what you need. Greetings, Andreas

2 1

[Dovecot] Dovecot and Active Directory separate domain data stores.
by Andrew Bruce 09 Aug '10

09 Aug '10

Hi, I've got Dovecot setup to auth my AD users fine via Winbind and I've also tried it using LDAP and can get this working also. The problem lies in the way we store our email for our virtual users in this setup. We run a flat domain for AD (lets call it newzealand.local), and then under each users account that gets email, in the E-mail field in AD, they have an email address like user1@auckland, user2@wellington, user3@chch and so on. With Postfix, I've set it up so that each email domain ends up being stored in a different path - /mail/auckland/user1, /mail/wellington/user2, /mail/chch/user3. This was done using a query filter that returned a person's email address from AD, chopped it into separate user/domain parts around the '@' symbol and using these to determine where the mail should be stored. This seems to work well for our purposes. But now I need to get Dovecot to be able to do the same thing in order to present the email to the user. I'm fairly certain this isn't going to work with Winbind, so I implemented the LDAP passdb and got that working, but I can't seem to quite work out how to get it to work with the domain part from the email address. Could someone give me a pointer in the right direction if this is possible. I'm thinking it has to do with the user_attrs variable, but can't quite workout how I would split this. Or is there a better way to do this? Thanks, Andrew

2 3

[Dovecot] Setting up webmail in DMZ
by Phill Edwards 09 Aug '10

09 Aug '10

I have a Smoothwall server on my network and am running three network interfaces off it. 1) local LAN 192.168.0.0 with PCs and an internal dovecot server on 192.168.0.154. 2) internet interface 3) DMZ 192.168.2.0 which has a linux web server 192.168.2.1 on which I want to install a webmail so I can access my email remotely. Originally 192.168.2.1 couldn't see the 192.168.0.0 network but with some help from the Smoothwall forums I have fixed that. The problem now is that 192.168.2.1 can't connect to the dovecot server on 192.168.0.154. When I "telnet 192.168.0.154 993" or "telnet 192.168.0.154 143" I get a "Connection refused" error. But these commands work fine from PCs on the 192.168.0.0 network. I'm pretty sure there's no firewall on the dovecot server and /etc/hosts.allow and /etc/hosts.deny are empty. Is there a default setting that I need to change in Dovecot that only allows connections from machines on the same subnet?

3 2

[Dovecot] dovecot v2 rc build and run dependencies
by Bradley Giesbrecht 09 Aug '10

09 Aug '10

I'm building a dovecot v2 Portfile for MacPorts. Where can I read up on dovecot v2 build and run dependencies? Are they the same as dovecot v1? Regards, Bradley Giesbrecht

2 1

[Dovecot] piegonhole seg fault with NULL user
by Eray Aslan 08 Aug '10

08 Aug '10

dovecot-2.0-piegonhole commit cac6acdc4d0e: Crash when USER is NULL. Backtrace is below. Perhaps, we should check for NULL and bail out early? Eray [...] (gdb) cont Continuing. Program received signal SIGSEGV, Segmentation fault. t_strcut (str=0x0, cutchar=64 '@') at strfuncs.c:277 277 for (p = str; *p != '\0'; p++) { (gdb) bt full #0 t_strcut (str=0x0, cutchar=64 '@') at strfuncs.c:277 p = <value optimized out> #1 0x4009c28b in get_var_expand_table (service=<value optimized out>, input=<value optimized out>) at mail-storage-service.c:478 static_tab = {{key = 117 'u', value = 0x0, long_key = 0x400f12ce "user"}, {key = 110 'n', value = 0x0, long_key = 0x400f0966 "username"}, {key = 100 'd', value = 0x0, long_key = 0x400f096f "domain"}, {key = 115 's', value = 0x0, long_key = 0x400f129c "service"}, {key = 108 'l', value = 0x0, long_key = 0x400f0976 "lip"}, { key = 114 'r', value = 0x0, long_key = 0x400f097a "rip"}, {key = 112 'p', value = 0x0, long_key = 0x400f097e "pid"}, { key = 105 'i', value = 0x0, long_key = 0x400f8aec "uid"}, {key = 0 '\000', value = 0x0, long_key = 0x0}} tab = 0x85f737c #2 0x4009c364 in user_expand_varstr (service=0x8603cf4, input=<value optimized out>, str=0x8603e88 "0") at mail-storage-service.c:501 ret = 0x85f71f0 __FUNCTION__ = "user_expand_varstr" #3 0x4009c8fc in mail_storage_service_next (ctx=0x8603470, user=0x8603cf0, mail_user_r=0x8601e40) at mail-storage-service.c:835 user_set = 0x8603d90 home = <value optimized out> chroot = <value optimized out> error = <value optimized out> len = <value optimized out> temp_priv_drop = <value optimized out> #4 0x4009dde4 in mail_storage_service_lookup_next (ctx=0x8603470, input=0xbfb98524, user_r=0x8601e3c, mail_user_r=0x8601e40, error_r=0xbfb9855c) at mail-storage-service.c:925 user = 0x8603cf0 ret = <value optimized out> #5 0x08055e35 in sieve_tool_init_finish (tool=0x8601e10) at sieve-tool.c:210 storage_service_flags = 144 service_input = {module = 0x80586c7 "mail", service = 0x8601e58 "testsuite", username = 0x0, local_ip = {family = 0, u = { ip6 = {__in6_u = {__u6_addr8 = '\000' <repeats 15 times>, __u6_addr16 = {0, 0, 0, 0, 0, 0, 0, 0}, __u6_addr32 = {0, 0, 0, 0}}}, ip4 = {s_addr = 0}}}, remote_ip = {family = 0, u = {ip6 = {__in6_u = { __u6_addr8 = '\000' <repeats 15 times>, __u6_addr16 = {0, 0, 0, 0, 0, 0, 0, 0}, __u6_addr32 = {0, 0, 0, 0}}}, ip4 = {s_addr = 0}}}, userdb_fields = 0x0} username = <value optimized out> errstr = 0x4013d4cc "\205\300u%\203\304\020[^]\303\307D$\004" #6 0x08054f5b in main (argc=2, argv=0x85ff1c0) at testsuite.c:147 svinst = 0x4001da98 scriptfile = 0x85f7058 "./tests/testsuite.svtest" dumpfile = 0x0 tracefile = 0x0 tr_config = {level = SIEVE_TRLVL_ACTIONS, flags = 0} sbin = <value optimized out> sieve_dir = <value optimized out> log_stdout = false ret = <value optimized out> c = <value optimized out>

2 2