- dovecot - dovecot.org

[Dovecot] How to set MDNSent flag on a large amount of mails?
by Patrick Nagel 03 Jun '08

03 Jun '08

Hi, after having moved a big mail archive to IMAP, I've now got the following problem: The MUA asks to send an MDN on all those old messages that contain the 'Disposition-Notification-To' header when opened. I'd like to set the $MDNSent flag on those (>10000 in a deeply nested directory structure) mails. After having read http://wiki.dovecot.org/MailboxFormat/Maildir I wrote a script that changed the filename of mails in all directories that contained the header, so that the filename contained a 'b' in the last part of the filename (after the comma), because I found '1 $MDNSent' in Maildir/dovecot-keywords. I then discovered that there can be a 'dovecot-keywords' file in each directory, and all of those files can have different flags in different order. Do I really need to write a script that evaluates each dovecot-keywords file, figures out which letter corresponds to the flag and rename the files (per directory) accordingly? Isn't there a more simple way? Patrick. -- STAR Software (Shanghai) Co., Ltd. http://www.star-group.net/ Phone: +86 (21) 3462 7688 x 826 Fax: +86 (21) 3462 7779 PGP key: https://stshacom1.star-china.net/keys/patrick_nagel.asc Fingerprint: E09A D65E 855F B334 E5C3 5386 EF23 20FC E883 A005

4 6

[Dovecot] spamassassin, postfix with dovecot lda?
by George Mamalakis 03 Jun '08

03 Jun '08

Hi all, I am trying to setup a mail server using postfix (virtual_mailboxes), spamassassin and dovecot, along with SQL where appropriate. From my research so far I realized that, for several reasons, it is required for me to use dovecot LDA instead of maildrop, local, procmail or other alternatives. My configuration was working flawlessly, until spamassassin per-user configuration came to play. If I just wanted an MTA anti-spam gateway, I could directly call spamassassin via master.cf, or through some helper "content-filter-application" (like amavis or amavisd-new), and everything would work just fine (I tried and tested many such configurations with success). But when antispam per user preferences became my concern (Bayesian filters and classifier), I realized that spamd should be called by the LDA. With procmail this was a trivial issue, with dovecot-lda I was unable to find any solution on the web or other documentation. So my question is as follows: Is there a way to call spamc from dovecot-LDA (and/or dovecot-sieve), or is there an alternate way to do this for a site with virtual mailboxes configured with dovecot-lda? Thank you all in advance, regards, -- George Mamalakis IT Officer, Department of Electrical and Computer Engineering, Aristotle Univ. of Thessaloniki, Greece

3 4

[Dovecot] v1.1.rc6 released
by Timo Sirainen 03 Jun '08

03 Jun '08

http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc6.tar.gz http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc6.tar.gz.sig This is it. The first v1.1 release that actually deserves the "release candidate" name. It contains everything I require from v1.1.0 release. There are two bugs left that I'd like to get fixed, but they won't block v1.1.0 release: * index_mailbox_set_recent_uid() assert (reported by Diego Liziero) * Maildir not always finding new messages and returning them as empty (reported by Anders). The major change in v1.1.rc6 release is the SORT indexing half-rewrite. I hadn't much stress tested that code before, and once I started I just kept finding more and more weird bugs and it became extremely difficult to figure out how to fix them, so I finally decided to just redesign how it's supposed to work and then implemented that. The resulting sort code is a lot cleaner and it should also perform better (although it could still be improved a bit: the basic binary searching could be replaced with one that first binary searches between already-looked-up sort-strings and only after that binary searches the resulting space which requires slower sort-string lookups). Hopefully there are also no stupid bugs left like returning messages in wrong sort order. :) I've been wasting time this past week getting new stuff for my new apartment, but that's nearly done now. I think (hope) I'm going to be more productive in here, there are less neighbours behind walls/floors (just 1), so less potential for annoying noises. :) Thinking also seems to work better when there's more space to walk around. And finally, the changes since v1.1.rc5: * Index file format changed a bit. If an older Dovecot v1.1 reads index files updated by rc6+, they may give "Invalid header record size" or "ext reset: invalid record size" warnings. v1.0 won't give these errors. * IMAP: LIST .. RETURN (X-STATUS) command return now LIST entries before STATUS entries. * zlib plugin: Uncompress if the message begins with zlib header instead of looking at the 'Z' flag. This fixes copying with hard links. Based on a patch by Richard Platel. + IMAP: SORT index handling code was half-rewritten to fix several bugs when multiple sessions were sorting at the same time. The new code is hopefully also faster. + Maildir: If POP3 UIDL extra field is found from dovecot-uidlist, it's used instead of the default UIDL format (or X-UIDL: header). This allows easily preserving UIDLs when migrating from other POP3 servers. Patch by Nicholas Von Hollen @ Mailtrust. + Maildir: ,W=<vsize> is now always added to maildir filenames + deliver: Avoid reading dovecot-uidlist's contents if possible. + Added %T modifier = Trim whitespace from end of string - IMAP: Fixed some bugs in LIST-EXTENDED implementation. - IMAP: If client tries to change the selected mailbox state while another command is still running, wait until the command is finished. This fixes some crashes and other unwanted behavior. - allow_nets userdb setting was broken with big endian CPUs

6 8

[Dovecot] overview of patches used in Fedora
by Dan Horák 03 Jun '08

03 Jun '08

Hi, I have gone through the patches that are used in the Fedora package and probably only the "mkcert-permissions" [1] can be considered to be included upstream. It is dated into package version 1.0-0.beta2.3, but I cannot find any particular reason for the inclusion (like a bug in bugzilla, etc.). Some (winbind support, quota warnings) were obsoleted by dovecot 1.1, two are used for distro specific settings. So the only real patch that remains is the "pam_setcred" [2] patch that fixes https://bugzilla.redhat.com/show_bug.cgi?id=146198 Current state of the package for Fedora is at http://cvs.fedoraproject.org/viewcvs/rpms/dovecot/devel/ Dan [1] http://cvs.fedoraproject.org/viewcvs/rpms/dovecot/devel/dovecot-1.0.beta2-m… [2] http://cvs.fedoraproject.org/viewcvs/rpms/dovecot/devel/dovecot-1.0.rc2-pam… -- Fedora and Red Hat package maintainer

2 2

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