- dovecot - dovecot.org

[Dovecot] Mail.app + dovecot 1.2 + POP3
by Rodolfo Gonzalez Gonzalez 10 Dec '09

10 Dec '09

Hello all, I have an user with MacOS X 10.5 Mail.app 3.5, which is connecting using POP3 to a dovecot 1.2 server. He has a 512 kbps link, which he saturates downloading large files. While the bandwidth is saturated, Mail.app shows the POP3 account as "offline" (I haven't used that client, but it seems that it doesn't retry the connection if it fails at some moment). He argues that he has some other POP3 and IMAP4 accounts configured in the same app, and those accounts never go "offline" even if the bw usage is at 100% (those other accounts are not on my servers and I don't know which sw are they using). My question is, could dovecot be somehow involved in this "offline" issue? (something like the past IDLE issues with Outlook 2007?) Thanks in advanced.

2 3

Re: [Dovecot] After upgrading to 1.2 - absolute path questions
by Richard Stockton 09 Dec '09

09 Dec '09

Hi Timo, Okay, I'm confused now... Here is what we are using with 1.1.19: password_query = SELECT password, home as userdb_home, 5000 as userdb_uid, 5000 as userdb_gid FROM mailbox where userid = '%n' mail_location = maildir:/mail/%h:INDEX=MEMORY The "/mail/" dir contains 26 NFS mounted partitions. Will this still work in 1.2? I have been holding off upgrading because it sounded like I would have to add the "/mail/" prefix to all the "home" directories in my user DB, and with 5 instances of Dovecot running off the same DB, I would have to shut down the pop/imap servers for the upgrade, something that would NOT make my boss happy. However, if I can leave the configs and the database as they are, the update will not be a big problem. Please let me know if I can use the old configs with Dovecot 1.2.x, I would love to be using the latest and greatest. And BTW, thanks again for all your hard work, Dovecot is a wonderful piece of software, and we really appreciate it! - Richard

2 12

[Dovecot] v2.0.alpha3 released
by Timo Sirainen 09 Dec '09

09 Dec '09

http://dovecot.org/releases/2.0/alpha/dovecot-2.0.alpha3.tar.gz http://dovecot.org/releases/2.0/alpha/dovecot-2.0.alpha3.tar.gz.sig Nothing horribly exciting since alpha2, but since I did other releases I thought I might as well release this one too. - Most of the stuff in master.conf is now built into binaries so the file itself is small. dovecot -n also doesn't show the defaults anymore. - Settings now have size and time types. So instead of always wondering if the units are bytes or kilobytes or megabytes, you can just use e.g. 100k, 100M values. And the same for 100 secs, 100 mins, 100 hours, etc. - verbose_proctitle=yes was pretty useless in alpha2 after the pre/post-login changes. I've now enabled Linux proctitle hack that allows changing process title (in ps). It now shows e.g. the current command being executed by imap process. There is also some hope of getting a proper setproctitle() function to Linux, the patch just got to -mm code tree today! - anvil process now stays alive across SIGHUPs. So "doveadm who" no longer forgets users after SIGHUP. - remote_ip IP {} and local_ip IP {} changed to remote host|IP {} and local host|IP {}, i.e. if it's not an IP Dovecot does host name lookup. - Using host names is also important to get TLS SNI working. With TLS SNI support if client supports it, you can serve multiple certificates with a single IP address. - LMTP server adds now Received: header - Fixes to LMTP server - Fixes to dsync Some of the larger changes left: - plugin API probably needs to be changed, so that it's possible to handle multiple users by same process but with different plugins - config process is too slow - rawlog no longer works because of how pre/post-login works now. it probably needs to be changed into a service and configured something like: service imap-rawlog { executable = rawlog imap-real /home/%u unix_listener imap { } } service imap { unix_listener imap-real { } } The point would be that when imap-login connects to imap, it actually connects to rawlog which then connects to imap-real and starts proxying the connection. A few problems: 1) userdb lookup is done by imap process, so rawlog doesn't know user's home directory. Perhaps more code could be added so that rawlog requests imap process to send it back, but maybe that's too much trouble. That's why I thought just adding a 3rd /home/%u parameter, where rawlog expands %u to username since that's at least known. 2) Currently it's not possible to remove default internal unix_listeners, so the above config wouldn't actually work anyway. I guess there needs to be some new syntax like "!unix_listener imap" or something that removes it.. Then again, a nice thing about this is that the rawlog will work with all types of services, even imap-logins, although that's going to be almost useless for SSL connections.

3 9

[Dovecot] How do i translate the old default_mail_env setting?
by Gary Kline 09 Dec '09

09 Dec '09

Hi, First, I am new to dovecot. Before my Jan '08 meltdown, sendmail was sufficient. A friend set up dovecot and since things just-worked, I was happy with that. Now I have a new mailserver and what was installed nearly two years ago fails. My pal installed things in dovecot.conf this way: default_mail_env = maildir:~/Maildir but the new mail environment is too different to be readily understood. --At least for me!-- The "%u" variable is confusing; so in the "%h" ($HOME [?]) variable... Would the following edit work on my old conf file: mail_location = maildir:~/Maildir ? tia, gary kline -- Gary Kline kline(a)thought.org http://www.thought.org Public Service Unix http://jottings.thought.org http://transfinite.thought.org The 7.31a release of Jottings: http://jottings.thought.org/index.php

2 9

Re: [Dovecot] fts squat non-english search for 2 words
by vuser1＠test123.ru 09 Dec '09

09 Dec '09

Timo Sirainen <tss(a)iki.fi>: > On Sun, 2009-11-22 at 20:35 +0700, vuser1(a)test123.ru wrote: >> Timo, thank you for answer. Meanwhile I was trying to setup >> horde+dovecot+search. Next step was dovecot 1.2.4 + solr 1.4. It >> works! Now it can find 2 non-latin words. >> 1) I cannot search by substrings - neither "plane" nor "plane*" does >> find "planet" > > Try if attached patch helps? > Quick answer is "no" 8)). Now the story. I debugged and realized that patched plugin generates - for search "xxx yyy": q=body:"XXX YYY*" It should be: q=body:XXX* +body:YYY* (not q=body:"XXX*" +body:"YYY*" - quotation does matter) But this does not work as expected. Prefix searches (with asterisk) are case-sensitive. I googled around and found this post - http://michaelkimsal.com/blog/solr-case-sensitivty/comment-page-1/#comment-… . It is old - 2007, but it looks SOLR is still case-sensitive for *. Because of dovecot capitalizes query (and this is right, I think), the search will never find a thing. I played with Solr admin for 3 evenings and I have to say - its behaviour is strange. For example, if I send several emails with body of 2 words: "xxx yyy", "yyy xxx", "xxX yYY" etc. - different case and different word order - it does not find "xxx" in all emails. Maybe Solr 1.4 is not production-ready yet and 1.3 is better. But it is enough for me, maybe I will return to it in next year. Now I will try to apply your changeset (fts-squat: Fixed searching multi-byte characters) to dovecot 1.2.4 (debian stable). If you think 1.2.8 is better, I will follow your recommendation.

2 1

[Dovecot] postfix+sasl+dovecot script help!
by Tudod Ki 09 Dec '09

09 Dec '09

postfix+sasl+dovecot script help! Hi everybody! I am trying to get the solution for days now, and I don't know what to do really :S I just want to write a script, what does automatically install postfix, dovecot, and it configures sasl authentication for the clients. I'm here right now [the script!!]: #################### http://pastebin.ca/1687824 [I have written the reference howto in the script.] #################### I run it after a fresh Lenny netinstall, on VirtualBox. If someone knows, what am I missing, please help me :\ I can see with "netstat -tulpn", that the server is listeing on port 993,955,25. #################### 1.) But: when I want to get the e-mails through imap, with Thunderbird, on another machine, it just waits, and waits, and waits...[and finally it gives this: "Connection to server debian.lan timed out."] :\ logs: mail.info log: http://pastebin.com/f6c486374 mail.log: http://pastebin.com/f6e60f9b other logs are empty #################### 2.) When I want to send a message from a testuser to a testuser, with Thunderbird, on the client, it just keeps asking for the password, when I want click send. :S logs: mail.info: http://pastebin.com/f1bca774f mail.log: http://pastebin.com/f5c0be27c mail.warn: http://pastebin.com/f46806d2f other logs are empty #################### Info about the os & softwares [e.g.: "dpkg -l | grep postfix"]: http://pastebin.com/f1d0cefd2 192.168.56.4 is the client 192.168.56.5 is the server [VirtualBox, Host-Only networking, they can ping each other] #################### Later I want to use it with Squirrel Mail [plus spam filtering + antivirus], but first, I just want to get it work :( Thank you for any help :S [_good_ docs, howtos, solution, or anything please! :S :( ]

2 1

[Dovecot] LDA: handling non-existent mail dirs
by Edgar Fuß 09 Dec '09

09 Dec '09

We have users existing in LDAP but not supposed to receive mail. We used to handle that (somewhat ungracefully) by simply not creating the top mail directory for those accounts. Since switching to Dovecots LDA, these non-existing dirs are considered temporary failures and so the junk mails pile up in postfix' queue Would it be possible for deliver to optionally treat this as a permanent error? I know the clean solution woud be checking for an LDAP attribute in postfix before even accepting the mail.

3 2

[Dovecot] FTBFS with binutils-gold
by Marco Nenciarini 09 Dec '09

09 Dec '09

As reported in debian bug #554306 [1] dovecot fails to build with GNU binutils-gold or setting LDFLAGS=-Wl,--no-add-needed http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=554306 The problem is that liblber isn't explicitly declared as a dependence when dovecot is compiled with ldap support. The attached patch fixes this little error. Regards, Marco -- --------------------------------------------------------------------- | Marco Nenciarini | Debian/GNU Linux Developer - Plug Member | | mnencia(a)prato.linux.it | http://www.prato.linux.it/~mnencia | --------------------------------------------------------------------- Key fingerprint = FED9 69C7 9E67 21F5 7D95 5270 6864 730D F095 E5E4

2 1

[Dovecot] dovecot v 1.28 and virtual folders
by Jim Richard 09 Dec '09

09 Dec '09

I haven't been able to make this work. I've experimented with different settings in my dovecot.conf for hours. I have a simple single user ubuntu setup, nothing fancy and would just like to have a virtual "unread" folder of my main INBOX, for use with Squirrelmail So, with just this, all good... subfolders look like .INBOX.duplicates for example in the file system namespace private { separator = . location = maildir:~/Maildir inbox = yes } now, when I try to add a virtual namespace namespace private { subscriptions = yes list = yes inbox = no prefix = virtual. separator = . location = virtual:~/Maildir/virtual } ~/Maildir/virtual does exist in the filesystem, I can "subscribe" to virtual but if I try to create a sub folder of it I get ERROR: Could not complete request. Query: CREATE "virtual.test" Reason Given: [CANNOT] Can't create virtual mailboxes Squirrelmail is great because it has some nice IMAP testing tools, so for example, with my current dovecot config I can test the NAMESPACE command, is that the correct response? Request: A003 NAMESPACE Response: * NAMESPACE (("" ".")("virtual." ".")) NIL NIL Namespace completed. I'm sure the issue is a fundamental lack of understanding of a concept here ... Any help would be appreciated. thank you, -Jim

2 1

[Dovecot] mailboxcasecmp()
by Frank Cusack 09 Dec '09

09 Dec '09

I remember way back, i'd modified the dspam training plugin to compare mailbox names case-insensitively. that patch wasn't accepted. i didn't understand why since it was obviously correct and had no negative impact, at least i didn't think so. Now I've hit another case where case-insensitive mailbox names would be useful: +addressing. If I have a mailbox 'Ext' and I send mail to frank+Ext@, the LHS is lowercased to 'frank+ext' and the +extension delivery doesn't find the 'Ext' mailbox. If the +extension is going to be lowercased, then the mailbox names should be lowercased when looking for them. Or, since 'ext' and 'Ext' can co-exist, the +extension shouldn't be lowercased when looking for the mailbox. I prefer the former (lowercase everything), since it's unlikely a user would create both 'mailbox' and 'Mailbox', however I can envision plenty of times where users would try to use '+ext' yet create the '+Ext" mailbox and never be able to figure out why it doesn't work. I know the latter solution (case sensitive extensions and case sensitive mailboxes) is more correct but really it will be harder to debug user problems. -frank

2 1