- dovecot - dovecot.org

[Dovecot] 1.1r1: auth-worker(default): BUG: PASSV had missing parameters, sig11
by Adam McDougall 10 Mar '08

10 Mar '08

I don't know how this happened. I'm not sure if there is a coredump somewhere because I don't know what user, and I have nothing for 'root' or 'dovecot'. Any advice, or should I make all my coredumps go to a central writable directory so I have better chance of catching it if it happens again? Is it maybe from someone connecting to postfix and causing a SMTP-AUTH to timeout? Although that is unlikely because users should not know how to reach this server's SMTP ports. I cut most of the surrounding log entries below because they seemed unrelated normal activity, but two of the lines below I left because of the timestamp. socket: type: listen client: path: /var/spool/postfix/private/auth mode: 384 user: postfix group: postfix Mar 8 17:02:17 boomhauer dovecot: auth-worker(default): BUG: PASSV had missing parameters Mar 8 17:03:47 boomhauer dovecot: auth-worker(default): BUG: PASSV had missing parameters Mar 8 17:05:17 boomhauer dovecot: imap-login: Disconnected: Inactivity: method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured Mar 8 17:05:17 boomhauer dovecot: child 72819 (login) killed with signal 11 Mar 8 17:06:47 boomhauer dovecot: imap-login: Disconnected: Inactivity: method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured Mar 8 17:06:47 boomhauer dovecot: child 72857 (login) killed with signal 11

2 5

[Dovecot] (no subject)
by Brent Clark 10 Mar '08

10 Mar '08

Hi Im trying something new with my test dovecot. I set my mail_location to to a new location mail_location = maildir:/var/maildir/%u/Maildir But with this new setup i too am authenticating against Mysql. This worked fine till i decided to move the mail. So now i have moved the mail, deleted the account from /etc/passwd,, but now in my mail client, i cant view my test mail. Here is my DB set up : +-----------------------------+--------+ | home | user | +-----------------------------+--------+ | /var/maildir/bclark/Maildir | bclark | +-----------------------------+--------+ dovecot-sql set up password_query = SELECT username as user, password, home , uid as userdb_uid, gid as userdb_gid FROM user WHERE username = '%u' and domain = '%d' I have removed Mar 8 15:42:56 eccostorage dovecot: auth(default): client out: CONT^I1^I Mar 8 15:42:56 eccostorage dovecot: auth(default): client in: CONT^I1^IAGJjbGFyawBxYXo= Mar 8 15:42:56 eccostorage dovecot: auth-worker(default): sql(bclark, 192.168.111.31): query: SELECT username as user, password, home , uid as userdb_uid, gid as userdb_gid FROM user WHERE username = 'bclark' and domain = 'eccotours.biz' Mar 8 15:42:56 eccostorage dovecot: auth(default): client out: OK^I1^Iuser=bclark^Ihome=/var/maildir/bclark/Maildir Mar 8 15:42:56 eccostorage dovecot: auth(default): master in: REQUEST^I15^I24965^I1 Mar 8 15:42:56 eccostorage dovecot: auth(default): passwd(bclark, 192.168.111.31): lookup Mar 8 15:42:56 eccostorage dovecot: auth(default): passwd(bclark, 192.168.111.31): unknown user Mar 8 15:42:56 eccostorage dovecot: auth(default): userdb(bclark, 192.168.111.31): user not found from userdb Mar 8 15:42:56 eccostorage dovecot: auth(default): master out: NOTFOUND^I15 Mar 8 15:42:56 eccostorage dovecot: imap-login: Internal login failure: user=<bclark>, method=PLAIN, rip=192.168.111.31, lip=192.168.111.11

2 1

Re: [Dovecot] Wrong message information reported shortly after delivery
by Ron Avriel 10 Mar '08

10 Mar '08

> Can you reproduce it without your IMAP client? For example using > imaptest (http://imapwiki.org/ImapTest) as the client and running: > Hi, Here's some more information on how to easily reproduce the problem. First, I'd like to describe my environment: OS - RHEL4, FS - ext3, dovecot 1.0.12. See dovecot -n at end of message. Messages are delivered via dovecot deliver invoked by postfix. The problem is reproduced when the system is completely idle - no user is logged in, except the test user. I wrote a short python script (attached) that reproduces the problem very easily. The script sends an email via SMTP, then IMAP fetches from inbox to check when message arrives. Once it arrives it checks if the size is zero and reports it. The script ends when dovecot reports a non-zero message size. The script consistently reproduces the problem on every RHEL4 server I tested (weak and strong) and with any file size. The script is run as ./send_fetch_test.py USER PASSWORD FILE [SERVER] FILE - any file. Contents doesn't matter. NOTE - The script initially deletes all messages from inbox just to minimize output. The problem occurs also when other messages exist. Here's a sample output: 2008-03-09 17:00:41.449833 Sent 1011 bytes to test1(a)imap4test.com 2008-03-09 17:00:41.472034 No messages in INBOX. Waiting... 2008-03-09 17:00:42.480654 No messages in INBOX. Waiting... 2008-03-09 17:00:43.487617 **** ERROR: Got invalid RFC822.SIZE 0: 1 (FLAGS (\Recent) INTERNALDATE "01-Jan-1970 00:00:00 +0000" RFC822.SIZE 0 UID 63) 2008-03-09 17:00:44.494382 **** ERROR: Got invalid RFC822.SIZE 0: 1 (FLAGS (\Recent) INTERNALDATE "01-Jan-1970 00:00:00 +0000" RFC822.SIZE 0 UID 63) 2008-03-09 17:00:45.501444 **** ERROR: Got invalid RFC822.SIZE 0: 1 (FLAGS (\Recent) INTERNALDATE "01-Jan-1970 00:00:00 +0000" RFC822.SIZE 0 UID 63) 2008-03-09 17:00:46.550623 **** ERROR: Got invalid RFC822.SIZE 0: 1 (FLAGS (\Recent) INTERNALDATE "01-Jan-1970 00:00:00 +0000" RFC822.SIZE 0 UID 63) 2008-03-09 17:00:47.593704 Got valid RFC822.SIZE 1509: 1 (FLAGS (\Recent) INTERNALDATE "09-Mar-2008 17:00:41 +0200" RFC822.SIZE 1509 UID 63) For this output I attached also the IMAP network capture and a strace of the imap process. dovecot -n: # 1.0.12: /usr/local/etc/dovecot.conf log_timestamp: “%Y-%m-%d %H:%M:%S ” protocols: imap listen: *:143 ssl_disable: yes disable_plaintext_auth: no login_dir: /usr/local/var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login login_process_per_connection: no first_valid_uid: 150 last_valid_uid: 150 dotlock_use_excl: yes fsync_disable: yes maildir_copy_with_hardlinks: yes maildir_copy_preserve_filename: yes mail_plugins: quota imap_quota auth default: mechanisms: plain login user: nobody master_user_separator: * passdb: driver: sql args: /usr/local/etc/dovecot-sql.conf passdb: driver: passwd-file args: /usr/local/etc/dovecot.masterusers master: yes userdb: driver: prefetch userdb: driver: sql args: /usr/local/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: mail plugin: quota: maildir:storage=1024 I hope this helps, Thanks, Ron ____________________________________________________________________________________ Never miss a thing. Make Yahoo your home page. http://www.yahoo.com/r/hs

2 1

[Dovecot] suspect valgrind error in mail-index-map.c
by Diego Liziero 10 Mar '08

10 Mar '08

Hi At line 1118 of src//lib-index/mail-index-map.c, inside the function mail_index_map_move_to_memory, there is: mail_index_map_copy_header(map, map); Valgrind is stating that "Source and destination overlap in memcpy". I'm wondering if this code is just coping the same memory over itself, or if it is doing something useful. Regards, Diego Liziero. --- 1104 void mail_index_map_move_to_memory(struct mail_index_map *map) 1105 { 1106 struct mail_index_record_map *new_map; 1107 1108 if (map->rec_map->mmap_base == NULL) 1109 return; 1110 1111 i_assert(map->rec_map->lock_id != 0); 1112 1113 new_map = array_count(&map->rec_map->maps) == 1 ? map->rec_map : 1114 mail_index_record_map_alloc(map); 1115 1116 mail_index_map_copy_records(new_map, map->rec_map, 1117 map->hdr.record_size); 1118 mail_index_map_copy_header(map, map); 1119 1120 if (new_map != map->rec_map) { 1121 mail_index_record_map_unlink(map); 1122 map->rec_map = new_map; 1123 } else { 1124 mail_index_unlock(map->index, &new_map->lock_id); 1125 if (munmap(new_map->mmap_base, new_map->mmap_size) < 0) 1126 mail_index_set_syscall_error(map->index, "munmap()"); 1127 new_map->mmap_base = NULL; 1128 } 1129 }

2 4

[Dovecot] Automatic Debian repository with packages for Dovecot-1.1 including Sieve and ManageSieve support.
by Stephan Bosch 10 Mar '08

10 Mar '08

Hello Dovecot users, For those of you who like to live on the edge, there is now a Debian-testing repository available with hourly updates from recent Dovecot-1.1 changes in the Mercurial repositories. It automatically releases a new set of packages if it notices any changes in any of the repositories. The packages are built with dovecot-sieve-1.1 and dovecot-1.1-managesieve included. Currently, it only provides binaries for the i386 architecture and no source packages are available. The small Debian-specific patches that are included in the official Debian packages are currently not included for this repository. Also, the packages are currently not PGP signed. I've built this repository to obtain continuous updates on whether the managesieve patch and package still compile and work with the latest Dovecot release. I get an e-mail if anything goes wrong during the build. I implemented the cron script right at the release of dovecot-1.1.rc1 and now that it successfully upgraded the package versions to 1.1.rc2, I decided to release the repository to the world. Needless to say: do **NOT** use this repository for systems that need to be **STABLE**. Usage should be similar to the backports.org repository (http://www.backports.org/dokuwiki/doku.php?id=instructions) but add the following line to your /etc/apt/sources.list: deb http://xi.rename-it.nl/debian/ testing-auto main Package versions look as follows: 1:<upstream-version>~auto+<build number> Current latest version: 1:1.1.rc2~auto+1 For questions, comments and requests, you can send me an e-mail. Regards, -- Stephan Bosch stephan(a)rename-it.nl IRC: Freenode, #dovecot, S[r]us

2 2

[Dovecot] Telephone systems and Dovecot
by Jonathan Knight 10 Mar '08

10 Mar '08

Hi folks, We're looking to integrate our telephone system with our email system. The telephone system will use IMAP4 to store WAV files in a users mailbox and then retrieve them for playing if necessary. This is usually called "unified messaging". The manufacturers are claiming full integration with Microsoft Exchange and Lotus Notes using IMAP4 and a single username and password to access all the users mailboxes. I can see that Dovecot has a master user feature that looks like it will do the job. Has anyone had any experience of using dovecot as a unified message server for a telephone system and has anyone any experience of configuring dovecot so that an MS exchange IMAP4 client using a master user can use dovecot without changing the client? Jon.

3 4

[Dovecot] newbie question dovecot and ldap
by Joseph Norris 09 Mar '08

09 Mar '08

Hello, Please let me know how I can troubleshoot this - driving me crazy! I have the following dovecot-ldap.conf file: hosts = ldap.ucmerced.edu dn=cn=natsciadmin,ou=Special Users,dc=ucmerced,dc=edu dnpass=******** ldap_version = 3 base = ou=People,dc=ucmerced,dc=edu deref = never scope = subtree user_attrs = uid user_filter = (&(ou=Natural Sciences)(organizationalStatus=active)(uid=%u)) pass_attrs = uid=user,userPassword=password pass_filter = (&(ou=Natural Sciences)(organizationalStatus=active)(uid=%u)) default_pass_scheme = CRYPT I am getting the following errors in my log for my test user: Mar 7 11:09:44 malaga dovecot: auth(default): LDAP: binding failed (dn cn=natsciadmin,ou=Special Users,dc=ucmerced,dc=edu): No such object Mar 7 11:10:26 malaga dovecot: auth(default): client in: AUTH 1 PLAIN service=IMAP secured lip=169.236.129.236 rip=169.236.128.182 Mar 7 11:10:26 malaga dovecot: auth(default): client out: CONT 1 Mar 7 11:10:26 malaga dovecot: auth(default): client in: CONT 1 AGpub3JyaXMAQSR0cjAxZGtpbGxlcg== Mar 7 11:10:28 malaga dovecot: auth(default): pam(jnorris,169.236.128.182): pam_authenticate() failed: Authentication failure Mar 7 11:10:28 malaga dovecot: auth(default): passwd(jnorris,169.236.128.182): password mismatch Mar 7 11:10:28 malaga dovecot: auth(default): ldap(jnorris,169.236.128.182): pass search: base=ou=People,dc=ucmerced,dc=edu scope=subtree filter=(&(ou=Natural Sciences)(organizationalStatus=active)(uid=jnorris)) fields=uid,userPassword Mar 7 11:10:28 malaga dovecot: auth(default): LDAP: binding failed (dn cn=natsciadmin,ou=Special Users,dc=ucmerced,dc=edu): No such object Mar 7 11:10:30 malaga dovecot: auth(default): client out: FAIL 1 user=jnorris temp Mar 7 11:10:30 malaga dovecot: auth(default): client in: AUTH 2 PLAIN service=IMAP secured lip=169.236.129.236 rip=169.236.128.182 resp=AGpub3JyaXMAQSR0cjAxZGtpbGxlcg== -- Cell: 209.201.3410 Desk: 209.228.4576 email: jnorris(a)ucmerced.edu #Joseph Norris (Linux/Apache/Mysql/Perl - what else is there?) print @c=map chr $_+100,(6,17,15,16,-68,-3,10,11, 16,4,1, 14,-68,12,1,14,8, -68,4,-3,-1,7,1,14,-68, -26,11,15,1,12, 4,-68,-22,11,14,14,5,15,-90);

3 3

[Dovecot] v1.1.rc2 released
by Timo Sirainen 09 Mar '08

09 Mar '08

http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc2.tar.gz http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc2.tar.gz.sig Changes since rc1: * mail_extra_groups setting was commonly used insecurely. This setting is now deprecated. Most users should switch to using mail_privileged_group setting, but if you really need the old functionality use mail_access_groups instead. + Expire plugin now supports wildcards in mailbox names. + dbox: Expire plugin supports moving old mails to alternative dbox directory + Maildir++ quota: quota_rule=?:<rule> specifies a default rule which is used only if the maildirsize file doesn't exist. + If SSL/TLS connection isn't closed cleanly, log the last error in the disconnection line. + EXPUNGE: If new \Deleted messages were found while expunging, do it again and expunge them as well (Outlook workaround) - IMAP: SEARCH, LIST and THREAD command correctness fixes - Maildir++ quota: Quota rules and warnings with % rules didn't work if the default limits were taken from maildirsize file. - Maildir++ quota: If both byte and message limits weren't specified, maildirsize file was recalculated all the time - mbox: Flag and keyword updates may have gotten lost in some situations (happens with v1.0 too) - ldap: Don't crash if userdb lookup fails - Squat fixes and performance improvements Things left to do for v1.1.0: - dbox has a metadata corruption bug, find and fix it - Squat has some locking issues that causes errors when stress testing with multiple connections - Squat doesn't do NFS cache flushing and has some other NFS problems.

4 22

[Dovecot] v1.0.13 and v1.1.rc3 released
by Timo Sirainen 09 Mar '08

09 Mar '08

http://dovecot.org/releases/1.0/dovecot-1.0.13.tar.gz http://dovecot.org/releases/1.0/dovecot-1.0.13.tar.gz.sig http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc3.tar.gz http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc3.tar.gz.sig Note that the changes for the security hole fix were quite large. I tested with several auth configurations myself and they seemed to work, but it's possible I left a bug somewhere in there breaking someone's configuration. So make sure to test that it works after upgrading. Of course it would be really nice if Dovecot had a proper test suite where testing all configurations could be automated and run before each release. I've already started this with my imaptest tool (http://imapwiki.org/ImapTest) but it only does IMAP tests and a lot of things are still missing. Some help would be nice here. * Fixed a security hole in blocking passdbs (MySQL always. PAM, passwd and shadow if blocking=yes) where user could specify extra fields in the password. The main problem here is when specifying "skip_password_check" introduced in v1.0.11 for fixing master user logins, allowing the user to log in as anyone without a valid password. - mail_privileged_group was broken in some systems (OS X, Solaris?) - IMAP THREAD: Fixed some correctness problems

1 0

[Dovecot] Security hole #6: Some passdbs allowed users to log in without a valid password
by Timo Sirainen 09 Mar '08

09 Mar '08

This affects only blocking passdbs: - MySQL - PAM, passwd and shadow if blocking=yes The underlying bug exists in all v1.0.x versions, but I couldn't figure out a way to exploit it except with v1.0.11, v1.0.12 and v1.1.rc2. Probably a good idea to upgrade in any case. The main problem is that Dovecot's internal protocols use TAB character as a delimiter, but passwords were sent unescaped through them. So passwords containing TAB characters allowed to add new internal fields. The main problem here is a new "skip_password_check" field added in v1.0.11 to fix problems with master user logins. Specifying this field allowed the user to skip the password check, as the name implies. This has been fixed thoroughly in v1.0.13 and v1.1.rc3 to make sure there are no more escaping problems with any fields, but it can be also fixed with a less intrusive patch for v1.0: http://hg.dovecot.org/dovecot-1.0/raw-rev/da2a9372e26e

1 0