- dovecot - dovecot.org

[Dovecot] Cosmetic issue with dots in Maildir folder names
by Holger Weiss 08 Sep '08

08 Sep '08

Just a minor cosmetic issue: We use the listescape plugin in order to support "." characters in Maildir++ folder names, and in at least the following case, the escaped representation of the dot character ("\2e") won't be translated back to a "." in messages for the IMAP client: | 1 SELECT non.existent | 1 NO Mailbox doesn't exist: non\2eexistent However, SELECTing an existing folder whose name includes a dot works fine, and it also works in other cases, e.g.: | 2 CREATE does.exist | 2 OK Create completed. | 3 LIST "" does.exist | * LIST (\HasNoChildren) "/" does.exist | 3 OK List completed. This is with Dovecot 1.1.3; we use "separator = /" and we've defined REAL_SEP to '.' and VIRTUAL_SEP to '/' in the plugin. Holger

2 1

[Dovecot] ACL plugin: k permission and sub-subfolders
by Heiko Schlichting 07 Sep '08

07 Sep '08

Hi, I'm trying to disallow the creating of subfolders for some special folder for all users. Using ACL plugin for this seems to work at first glance but is not a full solution or is buggy as it allows the creation of sub-subfolders. I'm using the following ACL and namespace separator is "/": $ cat folder owner lrwstie Note: no "k" permission ("k" = create = Mailboxes can be created under this mailbox) Seems to work: a001 create "folder/subfolder" a001 NO Permission denied But: a002 create "folder/subfolder/subsubfolder" a002 OK Create completed. This is unexpected. Creating a subfolder is not allowed but a sub-subfolder is permitted? If this is intentional, the description in the wiki should mention this. And: How to disallow the creation of any subfolders and any sub-subfolders? Using "folder/.DEFAULT" instead of "folder" to define the ACL does not make any difference for the behavior. My configuration of dovecot is below the signature. Thanks, Heiko. Heiko Schlichting Freie Universität Berlin heiko(a)FU-Berlin.DE Zentraleinrichtung für Datenverarbeitung (ZEDAT) Telefon +49 30 838-54327 Fabeckstraße 32 Telefax +49 30 838454327 14195 Berlin # 1.1.3: /server/dovecot/server/etc/dovecot.conf base_dir: /server/dovecot/server/var/run/ syslog_facility: local6 protocols: imap pop3 listen(default): 130.133.4.84:8143 listen(imap): 130.133.4.84:8143 listen(pop3): 130.133.4.84:8110 ssl_disable: yes disable_plaintext_auth: no shutdown_clients: no nfs_check: no login_dir: /server/dovecot/server/var/logindir login_executable(default): /server/dovecot/server/libexec/dovecot/imap-login login_executable(imap): /server/dovecot/server/libexec/dovecot/imap-login login_executable(pop3): /server/dovecot/server/libexec/dovecot/pop3-login login_greeting: mail.zedat.fu-berlin.de ready. login_chroot: no login_processes_count: 16 login_max_processes_count: 512 max_mail_processes: 1500 verbose_proctitle: yes mail_uid: 865 mail_gid: 865 mail_location: maildir:/server/dovecot/spool/%2Ln/%Ln/maildir maildir_copy_preserve_filename: yes mail_executable(default): /server/dovecot/bin/wrapper imap mail_executable(imap): /server/dovecot/bin/wrapper imap mail_executable(pop3): /server/dovecot/bin/wrapper pop3 mail_plugins(default): acl quota imap_quota listescape mail_plugins(imap): acl quota imap_quota listescape mail_plugins(pop3): quota mail_plugin_dir(default): /server/dovecot/server/lib/dovecot/imap mail_plugin_dir(imap): /server/dovecot/server/lib/dovecot/imap mail_plugin_dir(pop3): /server/dovecot/server/lib/dovecot/pop3 mail_log_prefix: %Ls[%p]: user=<%u>, mail_log_max_lines_per_sec: 50 imap_client_workarounds(default): delay-newmail netscape-eoh imap_client_workarounds(imap): delay-newmail netscape-eoh imap_client_workarounds(pop3): pop3_uidl_format(default): %08Xu%08Xv pop3_uidl_format(imap): %08Xu%08Xv pop3_uidl_format(pop3): %u 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 auth default: mechanisms: plain login user: dovecot username_format: %Lu failure_delay: 1 passdb: driver: checkpassword args: /server/dovecot/bin/checkpassword-zedat userdb: driver: prefetch plugin: quota: maildir quota_rule: *:bytes=2G acl: vfile:/server/dovecot/server/etc/acls

2 1

Re: [Dovecot] Error starting dovecot
by Frank Elsner 06 Sep '08

06 Sep '08

On Sat, 6 Sep 2008 13:23:54 -0200 Diego Ledesma wrote: > On Sat, Sep 6, 2008 at 10:57 AM, Frank Elsner > <frank(a)moltke28.b.shuttle.de> wrote: > > On Fri, 5 Sep 2008 20:09:07 -0300 Diego Ledesma wrote: > > > > [ ... ] > > > >> I only installed dovecot-common package. > >> Also, i setted protocols to "none". > >> > >> Does anyone know why i get that error message? > > > > Protocols "none" also means no "imap". > > > > BTW ... imap is a protocol :-) > > > > > > --Frank Elsner > > > > Oh. According to the comments in my dovecot.conf setting protocols to > "none" means that only dovecot-auth is enabled... > What should i write under Protocols to just enable that? My dovecot.conf contains protocols = imap imaps BTW, Please keep the thread on the mailing list, "Cc"ed here. --Frank Elsner

3 2

[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

[Dovecot] authorizing users
by Wade Smart 03 Sep '08

03 Sep '08

Im trying to clarify if I understand correctly about authorizing users. "The simplest login method is sending the user login info in plain text and allowing access only to users that already have UNIX access (ie. in /etc/passwd) to the machine dovecot is running on." Im using fetchmail postfix dovecot on my own personal computer to get my mail from two servers. What Im wanting to understand is, is this saying that since I am already a user on my own system, that by using /etc/passwd that I would use my username and password in say thunderbird to login to dovecot to get my mail?

2 1

[Dovecot] Dovecot-1.1.2 segfaults in mail_cache_header_fields_get_offset
by Mike Abbott 03 Sep '08

03 Sep '08

Dovecot 1.1.2 crashes reliably for me now on a Mac OS X machine. Here's some info: --- Telnet session --- $ telnet localhost 143 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. * OK Dovecot ready. a login user1 password a OK Logged in. b select inbox * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags permitted. * 1 EXISTS * 1 RECENT * OK [UNSEEN 1] First unseen. * OK [UIDVALIDITY 1218731580] UIDs valid * OK [UIDNEXT 2] Predicted next UID b OK [READ-WRITE] Select completed. c fetch 1 rfc822.size Connection closed by foreign host. --- Error log --- dovecot: Aug 29 11:24:30 Info: imap-login: Login: user=<user1>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured dovecot: Aug 29 11:24:33 Error: IMAP(user1): Corrupted transaction log file /Volumes/Spool/spool/user1/mail/dovecot.index.log: hdr.size too large (75497472) dovecot: Aug 29 11:24:33 Warning: IMAP(user1): fscking index file / Volumes/Spool/spool/user1/mail/dovecot.index dovecot: Aug 29 11:24:48 Error: child 66917 (imap) killed with signal 11 --- Backtrace --- mail_cache_header_fields_get_offset + 214 mail_cache_header_fields_read + 37 mail_cache_open_and_verify + 167 mail_cache_field_exists + 77 index_mail_set_seq + 306 index_storage_search_next_nonblock + 464 mailbox_search_next + 52 imap_fetch + 345 cmd_fetch + 639 client_command_input + 33 client_command_input + 463 client_handle_input + 242 client_input + 151 io_loop_handler_run + 272 io_loop_run + 39 main + 1671 start + 52 If I do the exact same telnet all over again, the imap process crashes in the same place, but without reporting the "fscking index file" error first. Attached are all the post-fsck dovecot* files from the user's inbox maildir. For other users I see this error before imap crashes: dovecot: Aug 29 11:45:23 Error: IMAP(user2): Rebuilding index file / Volumes/Spool/spool/user2/mail/dovecot.index: CPU architecture changed Attached are pre- and post-rebuild copies of that user's dovecot* files, and also a copy from after a second telnet session which also crashed. It's possible this is a 32/64-bit incompatibility issue (imap is a 64- bit program for me; mail might have been delivered by a 32-bit deliver or previously read by a 32-bit imap) but more likely the dovecot* files are just hosed in some way. I can provide more information if you ask soon, but I can't keep this server broken for too long.

2 3

[Dovecot] Authentication problems
by Rodti MacLeary 02 Sep '08

02 Sep '08

Hi there, I'm in a bit of a dilemma and wonder if anyone can help. Over the weekend I bought a new dedicated server and moved my mail/web over to it. I'd used the Sarge[1] tutorial at workaround.org for the old server and as I'd wanted to move to Dovecot for a while I decided to use their Etch[2] tutorial for the new one. For the most part everything's working nicely, but I seem to be having problems with (mostly non-SSL) SMTP authentication. In this install Postfix passes SASL authentication to Dovecot. For most clients using SSL this works fine, but as soon as SSL is off it fails. This is despite having disable_plaintext_auth set to 'no'. Furthermore it appears that some clients w/SSL are also failing. Outlook being the major culprit. I'm completely stumped. I've pasted a copy of the output from dovecot -n below. Thanks in advance! Rodti [1] http://workaround.org/articles/ispmail-sarge [2] http://workaround.org/articles/ispmail-etch --------------------------------------------- # 1.0.13: /etc/dovecot/dovecot.conf 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/lib/dovecot/imap-login login_executable(imap): /usr/lib/dovecot/imap-login login_executable(pop3): /usr/lib/dovecot/pop3-login mail_privileged_group: mail mail_location: maildir:/home/vmail/%d/%n/Maildir mail_executable(default): /usr/lib/dovecot/imap mail_executable(imap): /usr/lib/dovecot/imap mail_executable(pop3): /usr/lib/dovecot/pop3 mail_plugin_dir(default): /usr/lib/dovecot/modules/imap mail_plugin_dir(imap): /usr/lib/dovecot/modules/imap mail_plugin_dir(pop3): /usr/lib/dovecot/modules/pop3 pop3_uidl_format(default): pop3_uidl_format(imap): pop3_uidl_format(pop3): %08Xu%08Xv namespace: type: private separator: . prefix: INBOX. inbox: yes auth default: mechanisms: plain login cram-md5 passdb: driver: sql args: /etc/dovecot/dovecot-sql.conf userdb: driver: passwd userdb: driver: static args: uid=5000 gid=5000 home=/home/vmail/%d/%n allow_all_users=yes 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

3 5

[Dovecot] Dovecot 1.1.2, index_mailbox_set_recent_seq crash again
by Andreas M. Kirchwitz 02 Sep '08

02 Sep '08

Hi folks, after about 3 weeks without any problems, I've found this crash in yesterday's logfile (again related to index_mailbox_set_recent_seq): Aug 16 03:39:58 linux dovecot: IMAP(user1): Raw backtrace: imap [0x80cf8e0] -> imap [0x80cf93a] -> imap [0x80cf26c] -> imap [0x809d11a] -> imap(index_mailbox_set_recent_seq+0x3e) [0x809d15e] -> imap(mbox_sync+0x105d) [0x80823fd] -> imap [0x807a454] -> imap(index_transaction_commit+0x4e) [0x809ddfe] -> imap(cmd_copy+0x35f) [0x805b26f] -> imap(cmd_uid+0x59) [0x805f3d9] -> imap [0x805fd7c] -> imap [0x805fe25] -> imap [0x80605e5] -> imap(client_input+0x5e) [0x80607fe] -> imap(io_loop_handler_run+0x100) [0x80d7230] -> imap(io_loop_run+0x28) [0x80d63c8] -> imap(main+0x4a1) [0x8068321] -> /lib/libc.so.6(__libc_start_main+0xe0) [0x149390] -> imap [0x805a101] I don't know what IMAP operation caused that crash. The client (Thunderbird 2.0.0.16) silently reconnected without any notification. No obvious problems since yesterday. Dovecot 1.1.2 is running on Fedora 8 Linux 32 Bit with all patches and custom OpenSSL 0.9.8h. [ output of "dovecot -n" ] # 1.1.2: /usr/local/dovecot/etc/dovecot.conf ssl_cert_file: /usr/local/dovecot/etc/dovecot.crt ssl_key_file: /usr/local/dovecot/etc/dovecot.key login_dir: /usr/local/dovecot/var/run/dovecot/login login_executable: /usr/local/dovecot/libexec/dovecot/imap-login mail_location: mbox:~/Mail:INBOX=/var/spool/mail/%u auth default: mechanisms: plain login digest-md5 cram-md5 passdb: driver: passwd-file args: /usr/local/dovecot/etc/dovecot.passwd userdb: driver: passwd-file args: /usr/local/dovecot/etc/dovecot.passwd Greetings, Andreas

3 6

[Dovecot] tcp-wrapper patch for managesieve
by Edgar Fuß 02 Sep '08

02 Sep '08

Is there a place to store unofficial patches to ManageSieve? The attached patch is supposed to make ManageSieve (more precisely, managesieve-login) co-operate with a libwrapped (http://www.dovecot.org/patches/1.1/tcp-wrappers.patch) dovecot.

1 0

[Dovecot] "pam_start() failed: system error" with dovecot 1.1.2, cause unknown
by Adam McDougall 02 Sep '08

02 Sep '08

I would guess this is unlikely to be dovecot's fault, but I'm wondering if anyone has any ideas of what might have happened based on the evidence. My best guess is some kind of resource limit was reached but I don't see any evidence in the logs, and the condition is now gone. Suddenly this morning, one (and only one) of my dovecot servers decided to start failing all logins since 08:25:04 until we restarted dovecot, at which point they were working fine. The number of imap-login processes was under the limit, but there were some obvious PAM errors at the time. My account could still ssh to the system so I don't think it was a problem general authentication, and NIS on other systems was working fine. No one was logged into that server at the time the problems occurred, and I don't think anything happened to the actual pam libraries to make them missing since dovecot worked after a restart. I should have used other means to prevent people from using that dovecot instance rather than stopping it, and I'll do so if it happens again in hopes of further debugging. /var/log/maillog: Sep 2 08:25:01 hill dovecot: imap-login: Login: user=<userA>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured Sep 2 08:25:01 hill dovecot: IMAP(userA): Disconnected: Logged out bytes=127/568 Sep 2 08:25:01 hill dovecot: imap-login: Login: user=<userA>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured Sep 2 08:25:01 hill dovecot: IMAP(userA): Disconnected: Logged out bytes=282/9641 Sep 2 08:25:04 hill dovecot: imap-login: Login: user=<userA>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured Sep 2 08:25:04 hill dovecot: IMAP(userA): Disconnected: Logged out bytes=46/543 ***problem started here Sep 2 08:25:04 hill dovecot: auth-worker(default): pam(userA,127.0.0.1): pam_start() failed: system error Sep 2 08:25:04 hill dovecot: auth-worker(default): pam(userB,35.9.37.164): pam_start() failed: system error Sep 2 08:25:05 hill dovecot: auth-worker(default): pam(userC,35.9.37.164): pam_start() failed: system error Sep 2 08:25:06 hill dovecot: imap-login: Aborted login (auth failed, 1 attempts): user=<userB>, method=PLAIN, rip=35.9.37.164, lip=35.9.37.190, TLS Sep 2 08:25:06 hill dovecot: imap-login: Aborted login (auth failed, 1 attempts): user=<userA>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured Sep 2 08:25:07 hill dovecot: imap-login: Aborted login (auth failed, 1 attempts): user=<userC>, method=PLAIN, rip=35.9.37.164, lip=35.9.37.190, TLS ..... /var/log/messages: Sep 2 08:25:04 hill dovecot-auth: in openpam_load_module(): no pam_permit.so found Sep 2 08:25:04 hill dovecot-auth: in openpam_load_module(): no pam_login_access.so found Sep 2 08:25:05 hill dovecot-auth: in openpam_load_module(): no pam_nologin.so found Sep 2 08:25:10 hill dovecot-auth: in openpam_load_module(): no pam_unix.so found Sep 2 08:25:11 hill dovecot-auth: in openpam_load_module(): no pam_unix.so found Sep 2 08:25:20 hill dovecot-auth: in openpam_load_module(): no pam_opieaccess.so found Sep 2 08:25:20 hill dovecot-auth: in openpam_load_module(): no pam_opie.so found Sep 2 08:25:51 hill kernel: Sep 2 08:25:51 hill last message repeated 12 times Sep 2 08:27:52 hill kernel: Sep 2 08:27:52 hill last message repeated 37 times Sep 2 08:38:01 hill kernel: Sep 2 08:38:01 hill last message repeated 144 times Sep 2 08:48:06 hill kernel: Sep 2 08:48:06 hill last message repeated 129 times Sep 2 08:53:36 hill kernel: Sep 2 08:52:51 hill last message repeated 51 times

2 1

[Dovecot] Bad file descriptor with maildir and bzip2 files
by Chris Burton 02 Sep '08

02 Sep '08

Hi, I'm using the zlib plugin with dovecot 1.1.2 (on Centos 4.5, x86, ext3) and some bzip2 (version 1.0.2) compressed mail files are causing the following error to show in the logs when I click on the folder in outlook express. Aug 27 11:39:15 server-2 dovecot: IMAP(marchive): fstat(maildir) failed: Bad file descriptor Aug 27 11:39:17 Info: IMAP(marchive): Loading modules from directory: /usr/local/lib/dovecot/imap/ Aug 27 11:39:17 Info: IMAP(marchive): Module loaded: /usr/local/lib/dovecot/imap//lib20_zlib_plugin.so Aug 27 11:39:17 Info: IMAP(marchive): Effective uid=606, gid=609, home=/home/marchive Aug 27 11:39:17 Info: IMAP(marchive): maildir: data=/var/spool/maildir/marchive Aug 27 11:39:17 Info: IMAP(marchive): maildir++: root=/var/spool/maildir/marchive, index=, control=, inbox=/var/spool/maildir/marchive Aug 27 11:39:18 Info: IMAP(marchive): Disconnected: Internal error occurred. Refer to server log for more information. [20 08-08-27 11:39:18] bytes=246/1040 I attached strace to it and got the following: 11:39:18.193667 open("/var/spool/maildir/marchive/.2003.INBOX.Charlie.Old.OldInbox.2004/cur/1169027932.P30745Q17M499928.server-2:2,S=103418,Z", O_RDONLY|O_LARGEFILE) = 11 11:39:18.194130 fstat64(11, {st_mode=S_IFREG|0644, st_size=47637, ...}) = 0 11:39:18.194494 pread64(11, "BZh91AY&SY\231\206Z\257\0S\360\377\200\177\3746,U\357\377\377\377\377\377\360\277"..., 4096, 0) = 4096 11:39:18.200204 dup(11) = 12 11:39:18.200557 close(11) = 0 11:39:18.200916 fcntl64(12, F_GETFL) = 0x8000 (flags O_RDONLY|O_LARGEFILE) 11:39:18.200971 fstat64(12, {st_mode=S_IFREG|0644, st_size=47637, ...}) = 0 11:39:18.201104 mmap2(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xb7ff2000 11:39:18.201216 _llseek(12, 0, [0], SEEK_CUR) = 0 11:39:18.201355 fstat64(12, {st_mode=S_IFREG|0644, st_size=47637, ...}) = 0 11:39:18.201478 brk(0x9e61000) = 0x9e61000 11:39:18.201612 read(12, "BZh91AY&SY\231\206Z\257\0S\360\377\200\177\3746,U\357\377\377\377\377\377\360\277"..., 4096) = 4096 11:39:18.201694 read(12, "\277\217\261\0g!\273\')/3\343V\336\276}\273/\210I\26^\255\304\323\r\275Wts\3773"..., 4096) = 4096 11:39:18.201793 mmap2(NULL, 3600384, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) = 0xb7c68000 11:39:18.205993 read(12, "~\214\261E*@[\200\245\302\232\201\334\331\272\225NQ\244\260\371\3473cc\312\255\326\246\17\'\222"..., 4096) = 4096 < continues reading from the file > 11:39:18.225970 read(12, "+:E\225\7\217W\264\367\27\226\262i9\34\227=\350\250BcmF\306\'\231m\265\233\337\343\237"..., 4096) = 2581 11:39:18.226040 read(12, "", 4096) = 0 < 26x more of this read > 11:39:18.233913 munmap(0xb7c68000, 3600384) = 0 11:39:18.234070 close(12) = 0 11:39:18.234120 munmap(0xb7ff2000, 4096) = 0 11:39:18.234184 fcntl64(12, F_GETFL) = -1 EBADF (Bad file descriptor) 11:39:18.234255 fstat64(12, 0xbff0a9a0) = -1 EBADF (Bad file descriptor) 11:39:18.234347 write(2, "\1Efstat(maildir) failed: Bad fil"..., 45) = 45 To me it looks like its trying to call fcntl on the handle its just closed? I've since decompressed these files and recompressed with "gzip -9" and they seem to be opening OK. dovecot -n gives: # 1.1.2: /usr/local/etc/dovecot.conf info_log_path: /var/log/dovecot.log protocols: imap imaps pop3 ssl_disable: yes disable_plaintext_auth: no login_dir: /usr/local/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 mail_location: maildir:/var/spool/maildir/%u 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: zlib 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 auth default: passdb: driver: pam userdb: driver: passwd ChrisB.

3 6

[Dovecot] sieve plugin
by Андрей 02 Sep '08

02 Sep '08

I try to cinfigure dovecot run sieve scripts on incoming mail. In my dovecot.conf: <...> protocol lda { # Address to use when sending rejection mails. postmaster_address = root(a)vpcit.ru # Hostname to use in various parts of sent mails, eg. in Message-Id. # Default is the system's real hostname. hostname = vpcit.ru # Support for dynamically loadable plugins. mail_plugins is a space separated # list of plugins to load. #mail_plugins = mail_plugin_dir = /usr/lib/dovecot/modules/lda # Binary to use for sending mails. #sendmail_path = /usr/lib/sendmail # UNIX socket path to master authentication server to find users. auth_socket_path = /var/run/dovecot/auth-master # Enabling Sieve plugin for server-side mail filtering mail_plugins = cmusieve } <...> plugin { sieve = /var/mail/%d/%1n/%n/.dovecot.sieve } Then i set experiments on my maildir. In /var/mail/vpcit.ru/d/dukenukem i created script .dovecot.sieve: require "fileinto"; if header :comparator "i;ascii-casemap" :contains "Subject" "sieve check" { fileinto "Trash"; stop; } Permissions on /var/mail/vpcit.ru/d/dukenukem are: drwx------ 5000 mail So script should put every message that has "sieve check" subject into Trash folder. 1) Trash folder isn't created, should i create it manually? 2) Even when i create Trash folder and make 777 permissions to maildir, nothing happens (message is dropped into inbox dir) 3) Should i configure my Kontact (KMail) e-mail client some way? 4) What i've done incorrect? The mail system works fine at the moment for receive and send, trouble only with sieve scripting. Yours faithfully, Andrey.

3 4

[Dovecot] question about OpenSSL with DC
by Stewart Dean 02 Sep '08

02 Sep '08

IBM recently changed both its delivery package for OpenSSL and the locations it put things. Luckily, I have a second machine other than my mail server that I can test things on and DC 1.0.15 seems to be be running OK (thus I got all the configure/compilation tweaks right), but.....is there anyway to check the DC binaries to determine where it's getting its OpenSSl binaries and libraries (needed at runtime)? -- ==== 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

3 2

[Dovecot] Virtual users, postfix and dovecot deliver LDA
by Petri Asikainen 02 Sep '08

02 Sep '08

Hi, I have question about how to setup ldap-lookups in dovecot. I have done my homework by googling and reading documention and sample configuration files. But cant resolve this issue. Background: I have setup postfix and dovecot. Postix is configured to ldap alias maps and is delivering mails to /var/spool/vmail/username/Maildir correctly . Username is ldap attribute sAMAccountName from active directory. Goal: To use dovecots sieve plugin I have to setup postfix to use dovecots deliver. Changed postfix main.cf to virtual_transport = dovecot and master.cf to include lines: dovecot unix - n n - - pipe flags=DRhu user=vmail:mail argv=/usr/lib/dovecot/lda/deliver -d ${recipient} Problem is that mail get delivered to /var/spool/vmail/users.email@address , not folder named as ldap attribute sAMAccountNameas it should. The question is: How I can configure deliver to do map email address to ldap attribute sAMAccountName? Second question is can I use ldap groups as distribution lists whit deliver? Dovecot version is 1.1.2 and postfix 2.5.1 Cheers, Petri

2 11

[Dovecot] Read-only FS
by Radomir Zoltowski 01 Sep '08

01 Sep '08

Hi all, Imagine an NFS mounted read-only file system containing directories full of plain mboxes. Any recommendations on how to approach the access with dovecot? I believe all NFS recommended options apply, how about index/cache files though? Can I switch them off deliberately for good? Performance degradation is not an issue. Thanks, R. -- _________________________________________________________ Radomir Zoltowski <Radomir.Zoltowski(a)s3group.com> Applications Engineer Silicon & Software Systems Ltd., IT Department South County Business Park, Leopardstown, Dublin 18, IRELAND Tel.: +353 1 291 1224, Fax: +353 1 291 1001 _________________________________________________________ The information contained in this e-mail and in any attachments is confidential and is designated solely for the attention of the intended recipient(s). If you are not an intended recipient, you must not use, disclose, copy, distribute or retain this e-mail or any part thereof. If you have received this e-mail in error, please notify the sender by return e-mail and delete all copies of this e-mail from your computer system(s). Please direct any additional queries to: communications(a)s3group.com. Thank You. Silicon and Software Systems Limited. Registered in Ireland no. 378073. Registered Office: South County Business Park, Leopardstown, Dublin 18

2 2

[Dovecot] Dovecot 1.1.1 + zlib plugin + mbox crash
by Chris Wakelin 01 Sep '08

01 Sep '08

I've tried this on both Solaris 8 and SuSE Enterprise 9 (64-bit). I get a assert-crash when using a gzipped mbox folder . OK Logged in. . SELECT test.gz * FLAGS (\Answered \Flagged \Deleted \Seen \Draft $Label4 $Label2 $Label1 $Label3 $Label5) * OK [PERMANENTFLAGS ()] Read-only mailbox. * 167 EXISTS * 0 RECENT * OK [UNSEEN 2] First unseen. * OK [UIDVALIDITY 1096038620] UIDs valid * OK [UIDNEXT 42890] Predicted next UID . OK [READ-ONLY] Select completed. . FETCH 167 FULL * 167 FETCH (FLAGS () INTERNALDATE "05-Jan-2003 07:05:37 +0000" RFC822.SIZE 4693 ENVELOPE ("Sat, 04 Jan 2003 21:05:48 -0800" "[xxxxxxx] xx: xxxx xxxxxxxxxxx" (("xxxxx xxxxxxxx" NIL "xxxxxxxxxxxx" "xxxxx.xxx")) ((NIL NIL "xxxxxxx-xxxxxx" "xxxxxxxxxx.xx")) (("xxxxx xxxxxxxx" NIL "xxxxxxxxxxxx" "xxxxx.xxx")) (("xxxxxxx xxxx xxxx" NIL "xxxxxxx" "xxxxxxxxxx.xx")) NIL NIL NIL "<xxxxxxxx.xxxxxxx(a)xxxxx.xxx>") BODY ("text" "plain" ("charset" "us-ascii" "format" "flowed") NIL NIL "7bit" 3408 35)) . OK Fetch completed. . FETCH 167 BODY[] Connection closed by foreign host. dovecot: Jul 23 15:35:39 Info: imap-login: Login: user=<xxxxxxxx>, method=PLAIN, rip=xxx.xxx.xxx.xxx, lip=xxx.xxx.xxx.xxx dovecot: Jul 23 15:35:39 Info: auth(default): new auth connection: pid=841 dovecot: Jul 23 15:35:54 Panic: IMAP 888 xxxxxxxx xxx.xxx.xxx.xxx : file istream-raw-mbox.c: line 363 (i_stream_create_raw_mbox): assertion failed: (input->v_offset == 0) dovecot: Jul 23 15:35:54 Error: IMAP 888 xxxxxxxx xxx.xxx.xxx.xxx : Raw backtrace: imap [0x4833b8] -> imap [0x483413] -> imap [0x482e46] -> imap [0x43ce47] -> imap(mbox_file_open_stream+0x40) [0x434f40] -> imap [0x4363c1] -> imap [0x436778] -> imap(mail_get_stream+0xa) [0x4547ea] -> imap(index_mail_set_seq+0x144) [ 0x44b444] -> imap [0x436a79] -> imap(mail_set_seq+0x7) [0x454697] -> imap(index_storage_search_next_nonblock+0xd7) [0x44ef07] -> imap(mailbox_search_next_non block+0x10) [0x455ef0] -> imap(mailbox_search_next+0x20) [0x455f20] -> imap(imap_fetch+0x87) [0x41d457] -> imap(cmd_fetch+0x1f4) [0x4174b4] -> imap [0x41b2e4 ] -> imap [0x41b2d8] -> imap [0x41bc91] -> imap(client_input+0x5f) [0x41bdaf] -> imap(io_loop_handler_run+0xf7) [0x489d97] -> imap(io_loop_run+0x28) [0x48906 8] -> imap(main+0x462) [0x4233b2] -> /lib64/tls/libc.so.6(__libc_start_main+0xea) [0x2a9578caaa] -> imap(__ctype_b_loc+0x4a) [0x415b3a] dovecot: Jul 23 15:35:54 Error: child 888 (imap) killed with signal 6 dovecot -n output: # 1.1.1: /opt/RDGdovect/etc/dovecot.conf base_dir: /opt/RDGdovect/var/run/ log_path: /opt/RDGdovect/var/log/dovecot.log info_log_path: /opt/RDGdovect/var/log/dovecot.log protocols: imap listen: *:143 ssl_disable: yes disable_plaintext_auth: no shutdown_clients: no login_dir: /opt/RDGdovect/var/run/login login_executable: /opt/RDGdovect/libexec/dovecot/imap-login login_greeting: University of Reading IMAP test1.1 ready. login_process_per_connection: no verbose_proctitle: yes mail_location: mbox:/export/folders/%13.h/mail/:INBOX=/export/mail/%13.h/INBOX:INDEX=/export/indexes/%13.h mbox_very_dirty_syncs: yes mail_drop_priv_before_exec: yes mail_plugins: zlib mail_log_prefix: %Us %p %u %r : imap_client_workarounds: outlook-idle delay-newmail auth default: mechanisms: plain login username_format: %Ln verbose: yes debug: yes passdb: driver: ldap args: /opt/RDGdovect/etc/dovecot-ldap.conf userdb: driver: passwd-file args: /opt/RDGdovect/etc/userdb I've attached the relevant test.gz file (anonymised for the test) Has anybody else got it working? Best Wishes, Chris -- --+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+- Christopher Wakelin, c.d.wakelin(a)reading.ac.uk IT Services Centre, The University of Reading, Tel: +44 (0)118 378 8439 Whiteknights, Reading, RG6 2AF, UK Fax: +44 (0)118 975 3094

3 16