- dovecot - dovecot.org

[Dovecot] v1.1.3 released
by Timo Sirainen 05 Sep '08

05 Sep '08

http://dovecot.org/releases/1.1/dovecot-1.1.3.tar.gz http://dovecot.org/releases/1.1/dovecot-1.1.3.tar.gz.sig This fixes several mbox problems previous v1.1 releases have had. * mail_max_userip_connections limit no longer applies to master user logins. + login_log_format_elements: Added %k to show SSL protocol/cipher information. Not included by default. + imap/pop3-proxy: If auth_verbose=yes, log proxy login failures. + deliver: Added -s parameter to autosubscribe to autocreated mailboxes. - message parser fixes - hopefully fixes an infinite looping problem - SORT: One more assert-crashfix when renumbering index sort IDs. - mbox: Saving may have truncated the mail being saved - mbox: Several other bugfixes - mail_full_filesystem_access=yes was broken when listing mailboxes (it still is with maildir++ layout). - maildirlock utility was somewhat broken - zlib plugin: bzip2 support was somewhat broken - NFS: Make sure writing to files via output streams don't assert-crash when write() returns only partial success.

3 6

[Dovecot] Time Moved Backwards Error Keeps Happening
by JackyC＠umac.mo 05 Sep '08

05 Sep '08

Hi all, I am running dovecot version 1.1.1 (dovecot --version) and keeps to have time moved backwards problem. I first found dovecot dead without obvious error message, but see the following when restart dovecot service by # service dovecot restart >Stopping Dovecot Imap: [FAILED] >Starting Dovecot Imap: Warning: Last died with error (see error log for more information): Time just moved backwards by 4398 seconds. This might cause a lot of problems, so I'll just kill myself now. http://wiki.dovecot.org/TimeMovedBackwards [ OK ] I followed the above official wiki link and apply the ntpd service for adjusting the server timestamp. After running the ntpd service, I found the server timestamp drift is only 14.333 microsecond, I think which would be reasonable. But I still get the captioned error. Does anyone have the same experience? BTW, I couldn't find the error log message even I confirmed the info, error and debug log file by visiting this wiki document http://wiki.dovecot.org/Logging, does it really not log at the log file? I can just keep monitoring the log and use the following command to determine whether dovecot is running or not. # service dovecot status Thank you very much! Yours Sincerely, Jacky, Hoi Kei Chan,

2 1

Re: [Dovecot] filename format question
by Giorgenes Gelatti 05 Sep '08

05 Sep '08

> There's no config option for it, but it's theoretically possible to do just about anything. Generally, though, the format of those filenames is defined by the Maildir standard. Changing the filename as you suggest would likely break other mail programs that might access those Maildir folders. > > I suppose the question is: why would you want to change that? My company's current system (unfortunally) uses that non-standard format. The MTA writes in that format. I guess it would require a patch then? tks. gpg

2 1

[Dovecot] filename format question
by Giorgenes Gelatti 05 Sep '08

05 Sep '08

Hello, Is it possible to configure the filename format in dovecot? For example, to change from "unique,W=size:2,FLAGS" to "unique,size.hostname:2,FLAGS_unique2"? Thanks in advance.

2 1

[Dovecot] Integrating Dovecot SASL into Postfix
by Diego Ledesma 04 Sep '08

04 Sep '08

Hello. I have a linux system (Ubuntu 7.04 server edition) running as a mail server with Postfix. SMTP authentication is not configured so users have to be connected to the lan to download/send mails. I´m considering on enabling SMTP authentication and i have heard that by installing Dovecot i can do this pretty straight forward. First of all, some details about how the mail server is configured: - Running Linux OS Ubuntu 7.04 - Currently running Postfix version 2.3.8 - No virtual users or domains . Every system user has a mail account (to create a new mail account i have to create a new system user. I belive this is called PAM, right?). According to postfix´s website the version of postfix i have supports Dovecot 1.0 SASL protocol. What would happen if i try to install Dovecot through apt-get?. I mean, i most definitely get a version of Dovecot above 1.0. Would my postfix still support it?. Before posting this i have posted on the postifx mailing list and they have to told me that after installing Dovecot i don´t need to configure it as a pop/iamp server. How would i accomplish this?. Any help is greatly appreciated. Thanks. Diego.

2 1

[Dovecot] log analyzers
by maximatt 04 Sep '08

04 Sep '08

hi... ¿you have some log analyzer to recommend? (for dovecot obviously) thanks in advance!!!! -- Salu2 ;)

1 0

[Dovecot] Sieve problem with 1.1.2
by justin＠ma3x.net 04 Sep '08

04 Sep '08

Hello, I am new here, so excuse me if i am asking something already asked. I am using dovecot 1.1.2 along with postfix 2.6 and a pgsql backend. So far everything is great, until i wanted to try out the sieve implementation. I am using dovecot for deliver and i have set global_script_path = /home/vmail/globalsieverc The script IS working until a given user defines his own sieve script ( for example ) : require ["fileinto"]; # Move mail from my gmail account to gmail folder if header :contains "From" ["xxxxx(a)gmail.com"] { fileinto "gmail"; } This ( or any other script for all i know ) breaks up the global one, and it stops working. The global script looks like this : require ["fileinto"]; # Move spam to spam folder if header :contains "X-Spam-Flag" ["YES"] { fileinto "spam"; stop; } Am i missing something, or this is the desired behaviour ?

3 3

[Dovecot] Dovecot ManageSieve + ingo or avelsieve
by Olivier Dijoux 03 Sep '08

03 Sep '08

Hi, does anyone got Dovecot ManageSieve and Horde/Ingo working together ? i'm running Dovecot 1.1.2 with managesieve patch (dovecot-1.1.2-managesieve-0.10.3.diff) following intructions at http://wiki.dovecot.org/ManageSieve now my Dovecot have ManageSieve available :-) I've setup Horde/Ingo (ingo-h3-1.1.5-1.el5) when I specify some new filtering rules in Ingo, they are successfully uploaded using managesieve to Dovecot server and seems to be working. But when I logout/login back to Ingo, no rules are visible. Previously defined rules are still working with dovecot (because the ingo.sieve which links to .dovecot.sieve contains them), but Ingo is ignoring them at all. also my Dovecot managesieve setup is working well with avelsieve-1.9.4 plugin for Squirrelmail, but not with latest avelsieve-1.9.7 (see http://article.gmane.org/gmane.mail.squirrelmail.plugins/13818 ) : in avelsieve-1.9.7 same as Ingo, it forget rules ! any suggestion ? Ingo backends.php is : ---- $backends['sieve'] = array( 'driver' => 'timsieved', 'preferred' => 'localhost', 'hordeauth' => true, 'params' => array( // Hostname of the timsieved server 'hostspec' => 'localhost', // Login type of the server 'logintype' => 'PLAIN', // Enable/disable TLS encryption 'usetls' => false, // Port number of the timsieved server 'port' => 2000, // Name of the sieve script 'scriptname' => 'ingo', ), 'script' => 'sieve', 'scriptparams' => array() ); ---- PS : any ManageSieve patch for Dovecot v1.1.3 ? thanks -- Olivier

1 1

[Dovecot] umask and mails
by Nicolas Letellier 03 Sep '08

03 Sep '08

Hello. I would like to have rights like 750 in my mailboxes (in /var/mail/vmails/domain.tld/user). http://wiki.dovecot.org/DovecotServerInstallations/RHEL/2_Users?highlight=(… I see an option called umask (in dovecot.conf). I set umask = 0750 in dovecot.conf. This option add good rights to directories, but not to the mail received (always in 700). Do you have a solution? Thanks. -- - Nicolas.

2 2

[Dovecot] checkpassword migration script in Python
by Dan Udey 03 Sep '08

03 Sep '08

Hey all, First post to the list, so here goes, hope I don't break any rules (I didn't see any rules about not being overly verbose) I spent a long time looking for anything that would help me migrate from our old IMAP server to our new one without a lot of client-side fuss, multiple e-mail accounts, and so on. I find that a lot of our users get confused by having two 'inboxes' in Outlook (one local, unused, and one IMAP), so I figured the easier I could make it, the better. I figured there must be some way to do what I was looking for, but I couldn't find it, so I hacked up a little something to do the job. As the saying goes, it's nasty, brutish, and short, but in my tests it's done everything I needed it to. The problem: Our old mail system is hosted by another company, outsourced before I was hired, so I don't have access to the old user/ passwd database, nor to their e-mail store; thus, I cannot do a clean, simple migration by upgrading in-place as I have done on other servers. The solution IMAP authentication proxying. The idea is that I don't need to know the password, because the user's mail client knows the password, so all I need is for it to tell me, and then I can create their user. That is what this script is for. To use, set up your authentication backend (passdb) first, and then after that section, add a 'passdb checkpassword' section containing this script. Thus, the following will happen. 1. Valid users who log into your system will be authenticated as you would expect. 2. Users who could not be authenticated will fall through to the checkpassword section 3. Checkpassword will look for the user in the password database; if they exist, it is assumed that it is a valid user, but incorrect password, and checkpassword fails the user as well. 4. If the user is not currently in the database, it will initiate an IMAP4 connection to the remote host specified. If it succeeds in logging in to the remote host, then we assume that the user is a valid user and can be migrated to the local server. They are added to the database, along with their password. It then **fails the user's login regardless** 5. It /logs the username and password into the database/ so that another process can use that information to migrate their e-mail over to the new server (not yet implemented). 6. If the IMAP connection fails, the login is failed as well, and dovecot continues as normal until it has exhausted all other passdb backends. Interested? A few things to note about the script: 1. It's a brutal hack. Really, ugly stuff. However, it gets the job done, if your system is similar enough to mine. 2. It only works on MySQL. I only use MySQL in our system, so there's no point for me to add other DBs, nor any way to test. 3. It doesn't support remote servers using SSL. Our current system doesn't use it, so again, it's hard to test. 4. It does not currently migrate mailboxes. I'm working on this (see below). 5. If your schema is at all different from mine, you will likely have to rewrite all of the SQL. There's not much I can do about this. 6. If your backend database doesn't use MySQL, you're largely boned. Exception: rewrite add_user() to do whatever you need to do to add users to your system. 7. The script will **ALWAYS RETURN A FAILED LOGIN TO DOVECOT**. This is because there are too many variables on every configuration, and writing code for all of them is absurd. This way, the user's first login will always fail, and their second login will always succeed. If you want to avoid this, place your normal passdb authentication **both before and after this checkpassword section**. That way, it will check once, fail, pass to checkpassword, and then check again, success. TODO: 1. Make it not ugly. Break more junk off into functions (e.g. IMAP verification) 2. Send the user an e-mail ('Welcome to the server, sorry your mail is gone, we'll fix that soon') 3. Spawn another process to run imapsync in the background to migrate the user's old mailboxes over. This would be very site-dependent, as there are a lot of variables. It might be best done as a cronjob that polls the database every however often (1 minute? 2 minutes?) or a daemon that sits in the background watching the db for changes, or even accepting the data directly. 4. Stop being so verbose in my first postings to mailing lists. 5. Lots of other things. URLS Blah blah blah where's the code. Here you go. Pretty syntax-highlighted version for browsing before you download, in case I'm an evil hacker: http://cdslash.net/temp/python/checkpassword.py Ugly monochrome version for downloading so you don't get line numbers in your junk: http://cdslash.net/temp/python/checkpassword.raw Questions, comments? I probably won't be on the list very long, so if you want to ask something or have a suggestion, feel free to let me know by e-mail at the address listed in the file's license notification. Alternately, find me on Freenode, occasionally in #dovecot or always in #macosx, as Darien, or some variant thereof. PS: The code is licensed under a boilerplate MIT license lifted from the OSI license page. If you want it under a different license, let me know. ;) Thanks, Dan

1 0