- dovecot - dovecot.org

Re: [Dovecot] v1.1.rc8 released
by Timo Sirainen 03 Jun '08

03 Jun '08

On Mon, 2008-06-02 at 16:04 -0700, Andrew Roberts wrote: > On Tue, 3 Jun 2008, Timo Sirainen wrote: > > > + deliver: Added -c parameter to provide path to delivered mail. > > This allows maildir to save identical mails to multiple recipients > > using hard links. > > According to the wiki, deliver already uses a -c parameter to specify the > path to an alternate configuration file. Is this incorrect, or is this > functionality going away? I meant to say -p parameter.. And thanks for reminding, I'll update the wiki as well.

1 0

[Dovecot] Unsuccessful POP sessions on dovecot-1.0.3-13_60
by Patrick Ben Koetter 03 Jun '08

03 Jun '08

A Client runs a RAS network. Users access mailboxes using Outlook Express. The server runs dovecot-1.0.3-13_60. Almost a week ago users began to report that they can't retrieve their mail. The session starts, they seem to retrieve messages, but then the client reports a problem and the session is terminated. Here's what I have in the log: May 28 08:56:46 server dovecot: pop3-login: Login: user=<user@client>, method=PLAIN, rip=::ffff:10.11.9.18, lip=::ffff:10.11.9.108 May 28 08:59:00 server dovecot: POP3(user@client): Disconnected top=0/0, retr=5/448621, del=0/58, size=8991962 May 28 08:59:29 server dovecot: pop3-login: Login: user=<user@client>, method=PLAIN, rip=::ffff:10.11.9.18, lip=::ffff:10.11.9.108 May 28 09:03:49 server dovecot: POP3(user@client): Disconnected top=0/0, retr=5/448621, del=0/58, size=8991962 May 28 09:04:24 server dovecot: pop3-login: Login: user=<user@client>, method=PLAIN, rip=::ffff:10.11.9.18, lip=::ffff:10.11.9.108 May 28 09:12:11 server dovecot: POP3(user@client): Disconnected top=0/0, retr=5/448621, del=0/58, size=8991962 May 28 09:14:32 server dovecot: pop3-login: Login: user=<user@client>, method=PLAIN, rip=::ffff:10.11.9.18, lip=::ffff:10.11.9.108 May 28 09:17:10 server dovecot: POP3(user@client): Disconnected top=0/0, retr=5/448621, del=0/58, size=8991962 May 28 09:17:52 server dovecot: pop3-login: Login: user=<user@client>, method=PLAIN, rip=::ffff:10.11.9.18, lip=::ffff:10.11.9.108 May 28 09:20:27 server dovecot: POP3(user@client): Disconnected top=0/0, retr=5/448621, del=0/58, size=8991962 May 28 09:23:23 server dovecot: pop3-login: Login: user=<user@client>, method=PLAIN, rip=::ffff:10.11.9.18, lip=::ffff:10.11.9.108 May 28 09:30:05 server dovecot: POP3(user@client): Disconnected top=0/0, retr=5/448621, del=0/58, size=8991962 What I see is that the client seems to try to retrieve the same mails (retr=5/448621) over and over again. If they login using IMAP they don't experience any problems. Any idea what this could be? Rumor has it it's a know problem with Outlook Express and its POP implementation. Is that rumor or a fact? p@rick -- state of mind Agentur für Kommunikation, Design und Softwareentwicklung Patrick Koetter Tel: 089 45227227 Echinger Strasse 3 Fax: 089 45227226 85386 Eching Web: http://www.state-of-mind.de Amtsgericht München Partnerschaftsregister PR 563

2 3

[Dovecot] Purging Deleted Messages
by Carlos Williams 02 Jun '08

02 Jun '08

I noticed today I checked a users mailbox with the mutt command: mutt -f /home/bob/email/ There I saw he had 100 messages that had been deleted but not yet purged from his inbox so they're still using up disk storage on my email server. My question is does Dovecot have a process to automatically delete these messages after a certain period of time? I would like to think that they don't just sit in a users mailbox for years waiting to be purged, right? Does anyone know exactly how this works? I checked my own mailbox using mutt and I see 11 messages that are deleted from my Thunderbird client but are still on the server (marked for deletion). How long do these messages stay there? -- Man your battle stations...

4 4

[Dovecot] renameing users
by Ivan Levchenko 02 Jun '08

02 Jun '08

Hi All, I have a pretty basic question - I'm just getting into this email business =). There is a server that uses virtual users with dovecot. How could I go by allowing the users to change their usernames and to let them save all of their info? Access to the mailboxes is provided via squirrelmail . Thanks in advance! p.s. please cc me in the reply! -- Best Regards, Ivan Levchenko levchenko.i(a)gmail.com

1 0

[Dovecot] deliver & override homedir
by arne van theemsche 02 Jun '08

02 Jun '08

Hi We're in the phase of converting our existing unix-based users to virtual users. Goal is to make mail-spool totaly independent of home-spool. For that reason, NO files can be written to home. I've solved the problem for all files, except for .dovecot.lda-dupes. I can see in duplicate.c #define DUPLICATE_PATH "~/.dovecot.lda-dupes" I thought being clever and override in the userdb passwd following args = home=/var/spool/mail/%1n/%2n/%n but deliver totaly ignores that. does anybody has tips? kind regards Arne

2 1

[Dovecot] deliver saving mails with hard linking
by Timo Sirainen 02 Jun '08

02 Jun '08

http://dovecot.org/tmp/deliver-multiple.diff for Dovecot v1.1 implements -p <path> parameter for deliver, which reads the input mail from the specified path instead of stdin. With maildir and hardlink copying enabled, it also tries to hard link the file to destination instead of copying it. So to get the same mail delivered to multiple recipients using hard links, you'd have to write a small wrapper script that stored the mail temporarily somewhere and then called deliver for each recipient using the -p parameter. Any thoughts on if this should go to v1.1 like this? Some problems: - If you're not using a single UID/GID you probably have to make the file world-readable. - A wrapper script is kind of ugly, so it would be nice if deliver took a list of all recipients as input. But the deliver code is currently ugly enough that this would require larger changes. - Am I forgetting something?..

4 11

[Dovecot] Problems under opensuse-10.3-x86_64
by Christian Kuehn 02 Jun '08

02 Jun '08

Hi, I have a lot of problems to compile or to run the dovecot on my OpenSUSE 10.3 x86_64. Sometimes the compiled binary cannot read the existing and running config, the dovecot -n results in: ian:/opt/src/build/dovecot-1.1.rc7 # /opt/dovecot/sbin/dovecot -n # 1.1.rc7: /etc/dovecot/dovecot.conf Error: Missing auth section for server default Fatal: Invalid configuration in /etc/dovecot/dovecot.conf The prebuild RPM-daemon (v 10.0.13) said: ian:/opt/src/build/dovecot-1.1.rc7 # dovecot -n # 1.0.13: /etc/dovecot/dovecot.conf listen: *:8088 ssl_listen: *:10943 ssl_disable: yes ssl_cert_file: /etc/exim/www.foo-bar.de.crt ssl_key_file: /etc/exim/www.foo-bar.de.key disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable: /opt/dovecot/libexec/dovecot/imap-login first_valid_uid: 98 mail_location: maildir:~/maildir mail_executable: /opt/dovecot/libexec/dovecot/imap auth default: passdb: driver: sql args: /etc/dovecot/dovecot-sql.conf userdb: driver: sql args: /etc/dovecot/dovecot-sql.conf This looks fine and right, but there is no access to my old maildir (created by courier-imap) and I found several entries like this in my maillog: May 27 19:13:54 ian dovecot: IMAP(tkstest(a)foor-bar.de): Unexpected eof found when reading file 'UNOPENED' (Errcode: 0) or: May 27 16:22:44 ian dovecot: IMAP(tkstest(a)foo-bar.de): Corrupted transaction log file /var/spool/virtuser/xxxxx/mail/INBOX./.imap/Trash/dovecot.index.log: unexpected end of file while reading header or: May 27 18:05:44 ian dovecot: IMAP(tkstest(a)foo-bar.de): file mail-index.c: line 1 900 (mail_index_move_to_memory): assertion failed: (index->fd == -1) May 27 18:05:44 ian dovecot: IMAP(tkstest(a)foo-bar.de): Raw backtrace: imap [0x4648be] -> imap [0x4645fe] -> imap [0x443834] -> imap [0x450b08] -> imap(mail_index_open+0x1df) [0x444e6f] -> imap(index_storage_mailbox_init+0x159) [0x43c119] -> imap [0x41fe0d] -> imap [0x420ab8] -> imap(_cmd_select_full+0xaa) [0x4149ca] -> imap(cmd_select+0xb) [0x414b7b] -> imap [0x415e97] -> imap [0x415f29] -> imap(_client_input+0x6f) [0x4165cf] -> imap(io_loop_handler_run+0x101) [0x46a021] -> imap(io_loop_run+0x18) [0x4691f8] -> imap(main+0x457) [0x41e087] -> /lib64/libc.so.6(__libc_start_main+0xf4) [0x2b5ab1476ae4] -> imap [0x411719] May 27 18:05:44 ian dovecot: child 15320 (imap) killed with signal 6 Tested versions: 1.0.13 RPM by OpenSUSE 1.0.13 self-compiled 1.1.rc7 self-compiled OS: Linux ian 2.6.18.8-0.9-default #1 SMP Sun Feb 10 22:48:05 UTC 2008 x86_64 x86_64 x86_64 GNU/Linux configure: ./configure --prefix=/opt/dovecot --sysconfdir=/etc/dovecot --with-mysql --with-pop3d --with-notify=inotify --with-ioloop=epoll --with-sql CPPFLAGS='-fPIC -I/opt/mysql/include' LDFLAGS='-L/opt/mysql/lib -lmysqlclient -lz -lcrypt -lnsl -lm' Any ideas? Kind Regards Christian -- Christian Kuehn eMail: christian(a)hamburg.gay-web.de

2 1

[Dovecot] Requested CRAM-MD5 scheme, but we have only MD5-CRYPT
by Richard Pyne 01 Jun '08

01 Jun '08

After upgrading my dovecot installation about a month ago, I have started seeing "Requested CRAM-MD5 scheme, but we have only MD5-CRYPT" message from dovecot in my logs. Any help in finding and correcting the cause will be greatly appreciated. --Richard

2 4

Re: [Dovecot] Segfault in imap_bodystructure_write when searching
by Christer Mjellem Strand 01 Jun '08

01 Jun '08

>> Whenever I try to search on my dovecot test install, dovecot dies. It >> immediately spawns a new process, which the client tries to connect to, >> and send search commands to, causing that to die, and so forth. This loop >> means I have to kill either the server or the client. > > Your dovecot.index.cache file is probably broken somehow. Try moving > dovecot.index* files elsewhere and see if it works then? If it does and > dovecot.index.cache doesn't contain anything too sensitive > (subjects/from/to addresses), could you send me the dovecot.index* > files? > > If it crashes even without dovecot.index* files then the mails > themselves contain a broken message. It would help if I could get that > message. Bullseye. Why did I fail to mention that I was trying to use uiddb from Courier? :P Using your conversion script fixed it, but simply copying the Courier file crashed Dovecot. According to http://wiki.dovecot.org/Migration/Courier this is supposed to work though, so either that page is wrong, or Dovecot has a bug. >> betty - ~vpopmail/domains/bar.com/foo # gdb /usr/lib/dovecot/imap core > .. >> (no debugging symbols found) >> Core was generated by `imap'. >> Program terminated with signal 11, Segmentation fault. >> #0 0x080a539d in imap_bodystructure_write () >> (gdb) bt full >> #0 0x080a539d in imap_bodystructure_write () >> No symbol table info available. >> #1 0x08083b5c in ?? () > > Unfortunately this backtrace is almost completely broken and it doesn't > really help.. You also could try compiling Dovecot itself with debug > symbols and getting backtrace from it. That'd probably work. I tried reproducing now, but it seems it's started working even when moving all dovecot files and copying courierimapuiddb to dovecot-uidlist. If I see it again I'll send you a copy of the file offlist. Thanks. -- -==- -=- -==- Christer Mjellem Strand yitzhaq System administrator ICQ: 9557698 GSM +47 922 000 12 JID: yitzhaq(a)jabber.no -==- -=- -==-

2 7

Re: [Dovecot] Dovecot hard link problem
by Timo Sirainen 01 Jun '08

01 Jun '08

On Sun, 2008-06-01 at 23:27 +0900, 도원철 wrote: > My company recently changed mail server from cyrus to dovecot. > > The problem is that dovecot does not support hard links for message > files with same message ID. > > I turned on the ‘maildir_copy_with_hardlinks’ option in dovecot.conf, > but it does not seems to have relation to this problem, am I > misunderstood? > > Hard links are created when move or copy messages from one folder to > other folder, but when deliver creates messages this option does not > works. Right. This isn't implemented yet. Also I don't think it should rely on Message-ID: header proving the uniqueness. There are two ways this can be implemented reliably: 1) If the message is sent to multiple recipients using same RCPT TO command, all the recipients could be given to deliver as parameters, and deliver would know that it's the same message and they could be hard linked. 2) Keep some kind of a hash database where hash is e.g. SHA1 sum of the entire message. All messages could be then stored in some global directory and hard linked from there to users' mailboxes. When receiving a new message using an existing hash, it could still compare byte-by-byte the files to make sure that it's not a hash collision before hard linking the file. 1) probably wouldn't be too difficult to implement and probably would solve your problem (assuming the problem is that people are mailing 100MB attachments to everyone inside a company). But I don't think I have time to do it myself..

1 0