- dovecot - dovecot.org

[Dovecot] 1.2.beta1: expire-tool and 'mail_location' setting
by e-frog 03 Jun '09

03 Jun '09

Hi Timo, Trying 1.2.beta1 with expire plugin currently: When I set mail_location = maildir:~/.maildir the expire plugin doesn't delete messages. #: expire-tool --test Info: auth input: system_user=foo Info: auth input: uid=1000 Info: auth input: gid=1000 Info: auth input: home=/home/foo Info: foo/Trash: no messages left I also noticed that above command creates a new but empty directory 'mail' in user's home dir. However using mail_location = maildir:~/Maildir and of course moving the messages to it works. #: expire-tool --test Info: auth input: system_user=foo Info: auth input: uid=1000 Info: auth input: gid=1000 Info: auth input: home=/home/foo Info: foo/Trash: seq=1 uid=4078: Expunge . . Info: foo/Trash: seq=100 uid=4178: Expunge Info: foo/Trash: seq=101 uid=4179: Expunge Info: foo/Trash: timestamp 1235292536 -> 1235325429 My guess is that mail_location is not respected by expire-tool for some reason and in second case mailbox auto-detection makes it working? Thanks, e-frog ---------------------------------------------------------------------------------------------- #: dovecot -n # 1.2.beta1: /etc/dovecot/dovecot.conf # OS: Linux 2.6.27-11-server i686 Ubuntu 8.10 log_timestamp: %Y-%m-%d %H:%M:%S protocols: imap managesieve 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(managesieve): /usr/lib/dovecot/managesieve-login mail_privileged_group: mail mail_location: maildir:~/.maildir mail_debug: yes mail_drop_priv_before_exec: yes mail_executable(default): /usr/lib/dovecot/imap mail_executable(imap): /usr/lib/dovecot/imap mail_executable(managesieve): /usr/lib/dovecot/managesieve mail_plugins(default): quota imap_quota expire fts fts_squat mail_plugins(imap): quota imap_quota expire fts fts_squat mail_plugins(managesieve): mail_plugin_dir(default): /usr/lib/dovecot/modules/imap mail_plugin_dir(imap): /usr/lib/dovecot/modules/imap mail_plugin_dir(managesieve): /usr/lib/dovecot/modules/managesieve auth default: passdb: driver: pam userdb: driver: passwd socket: type: listen client: path: /var/run/dovecot/auth-client mode: 432 user: dovecot group: Debian-exim master: path: /var/run/dovecot/auth-master mode: 384 plugin: quota: maildir quota_rule: *:storage=1GB quota_rule2: Trash:storage=10%% expire: Trash 1 expire_dict: proxy::expiredict sieve: ~/.dovecot.sieve sieve_dir: ~/.sieve fts: squat fts_squat: partial=4 full=10 dict: expiredict: mysql:/etc/dovecot/dovecot-dict-sql.conf

2 9

[Dovecot] expire tool - individual user/folder?
by Andre Hübner 02 Jun '09

02 Jun '09

Hello, is the expire plugin usable to delete mails with different settings for each individual user? If i view sample config at http://wiki.dovecot.org/Plugins/Expire it looks like expire-data are related to foldernames. Is it possible to let each user "activate" the expire-plugin for different folders with different settings? Thanks, Andre

2 11

[Dovecot] Running imaptest revision 209:939fa886391a built against dovecot revision 9116:9ae55b68cf61 on AIX 5.3 core dumps
by Jonathan Siegle 02 Jun '09

02 Jun '09

# ./imaptest host=127.0.0.1 port=143 user=tstem38 pass=pass4you mbox=/ gpfs/users/t/s/tstem38/IMAP/foo4 Panic: file client.c: line 620: assertion failed: (idx >= array_count(&clients) == NULL) IOT/Abort trap(coredump)

3 3

Re: [Dovecot] Missing IMAP folders after Server reboot
by punit_j 02 Jun '09

02 Jun '09

Did you try looking for the folders by connecting to IMAP using command line. telnet servername 143 a1 login username pass a2 list "" * Check if you could see anything.

3 2

[Dovecot] v1.1.16 released
by Timo Sirainen 02 Jun '09

02 Jun '09

http://dovecot.org/releases/1.1/dovecot-1.1.16.tar.gz http://dovecot.org/releases/1.1/dovecot-1.1.16.tar.gz.sig Fixes a couple of bugs in v1.1.15's changes. Hopefully the last v1.1 release before v1.2.0. - v1.1.15 could have crashed if mailbox-closing command was pipelined after a mailbox-accessing command. - v1.1.15's zlib plugin may have caused crashes when fetching INTERNALDATE. - Maildir: If messages had been deleted externally from new/ directory and mailbox was opened with EXAMINE, Dovecot didn't immediately notice that the messages were deleted. - If message body started with a space, some operations could have assert-crashed.

3 3

[Dovecot] Log filenames of saved files to inbox by dovecot-deliver
by Sven Eulberg 02 Jun '09

02 Jun '09

Hello, Is it possible to log the filenames into deliver.log where dovecot- deliver saved incoming emails? If not so, please add this as a feature request. Thanks in advance! Regards, Sven

2 1

[Dovecot] recipient delimiter and lmtp
by John Fawcett 02 Jun '09

02 Jun '09

I read in the list archives about work in progress on an lmtp delivery agent.As a previous cyrus user where that was the preferred delivery method from postfix, this sounds interesting. I was wondering whether it will handle recipient delimiters. ie will it be able to map user+foo(a)example.com to user(a)example.com? I'm not interested in the delivery into folder stuff, just the plain delivery to inbox. thanks, John

6 10

[Dovecot] IMAP labeling sometimes not taken into account
by Olivier Cailloux 02 Jun '09

02 Jun '09

Dear Dovecot list, I recently switched from uw-imapd to dovecot to manage my huge mbox files (about 1 GB). I now observe a very strange behavior, difficult to reproduce reliably, which might be related to some misunderstanding on my part on how either dovecot works or imap labeling works. What I call "labeling" is the fact of marking some e-mail, in my e-mail client (currently Thunderbird), with a label, which can be chosen among five labels (plus the "no-label" case). Evolution also supports labeling. As far as I understood until a few days ago, when I put a label, say, number five, on an e-mail, a keyword "$Label5" is added on the "X-Keywords:" line of the corresponding e-mail in my mbox file. Removing the label simply removes the keyword on the same line. That is, at least, what happened with uw-imapd (not that I have seen that documented somewhere but this is what I observed). The label is thus stored on the e-mail server, not on the client hard disk, which is important for me as I extensively use that feature to sort e-mails, and need to access them from several different places (and find the same labels at the same places, naturally, whatever client I use). Since the change for dovecot, however, things are going strange. Sometimes the labels disappear for some reasons. Sometimes they stay there. And I can't reproduce the behavior, it just seems random. This is very annoying as it totally breaks my e-mail management. Currently there is something strange I can reproduce however, and if someone could explain me what is happening I guess it would be a good step towards a solution. I see a specific e-mail as being labeled in thunderbird, having label number five. I also tried with evolution, accessing the same imap folder, evolution also sees that e-mail as having a label number five. I tried running these clients from my imap server, and I tried thunderbird on a Windows box at home, and every clients agree: this e-mail has a "5" label. BUT when I open the mbox file directly on the imap server (using "less"), and scroll to that given e-mail, I see NO "X-Keywords: " line. How then can the e-mail clients know that this e-mail is labeled? Please note that this behavior does not happen with only one specific e-mail, but I take it as an example of what is strange. In fact I can see, especially at the end of the mbox file (thus the latest e-mails), that plenty of e-mails have either no "X-Keywords: " line or a line with "X-Keywords: " and nothing else, whereas they are seen as being labeled (and indeed I remember having labeled most of those through thunderbird). The former e-mails I checked in the m-box (for example, one month ago) all correctly have an X-Keywords line indicating "$Label5" or other appropriate labels. It seems like dovecot is keeping some track of labeled e-mails somewhere which is NOT in the mbox file, probably related to its indexing capabilities. But I don't know how that works and where these index files are stored, how to purge them and rebuild the index, and so on. Apparently these index files have remembered some e-mails as being labeled (which is good, because I indeed labeled them). But I'd like to know how that works to be able to better troubleshoot why sometimes the label disappear. Note that restarting dovecot does not change the label status of the e-mail, so the status must be stored somewhere on disk and not only in memory. Or is all these labeling stuff some unsupported, non-standard extension to IMAP that only uw-imapd supports? (I hope not because I find it very practical and I'd like to use it with dovecot as well!) Thank you for any help. (Technical informations follow.) Olivier ------ 2-12h38-~#dovecot --version 1.0.15 ------ 2-12h38-~#dovecot -n # 1.0.15: /etc/dovecot/dovecot.conf log_timestamp: %Y-%m-%d %H:%M:%S ssl_cert_file: /etc/ssl/certs/imapd.pem ssl_key_file: /etc/ssl/private/imapd.pem login_dir: /var/run/dovecot/login login_executable: /usr/lib/dovecot/imap-login mail_privileged_group: mail auth default: passdb: driver: pam userdb: driver: passwd ------

2 2

[Dovecot] Capability problems dovecot 2.0
by ja nein 01 Jun '09

01 Jun '09

Hi, I had some problems connecting TB 2.x with dovecot 2.0. TB2 complained about not being an IMAP4 server. TB 3 worked. It seems that dovecot 2.0 doesn't return capabilities when queried. Maybe some wrong config, thoug? Here are the debug logs from TB2 comparing dovecot 2.0 (not working) and dovecot 1.2 (working): Dovecot 2.0: NA:CreateNewLineFromSocket: * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE AUTH=PLAIN AUTH=LOGIN AUTH=DIGEST-MD5 AUTH=CRAM-MD5] Dovecot ready. NA:SendData: 1 capability ReadNextLine [stream=26c2d60 nb=15 needmore=0] NA:CreateNewLineFromSocket: * CAPABILITY ReadNextLine [stream=26c2d60 nb=28 needmore=0] NA:CreateNewLineFromSocket: 1 OK Capability completed. ProcessCurrentURL: aborting queued urls NA:SendData: 2 logout Dovecot 1.2: NA:CreateNewLineFromSocket: * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE AUTH=PLAIN AUTH=LOGIN AUTH=DIGEST-MD5 AUTH=CRAM-MD5] Dovecot ready. NA:SendData: 1 capability ReadNextLine [stream=27dcf50 nb=303 needmore=0] NA:CreateNewLineFromSocket: * CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE SORT THREAD=REFERENCES THREAD=REFS MULTIAPPEND UNSELECT IDLE CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH QUOTA AUTH=PLAIN AUTH=LOGIN AUTH=DIGEST-MD5 AUTH=CRAM-MD5 ReadNextLine [stream=27dcf50 nb=28 needmore=0] NA:CreateNewLineFromSocket: 1 OK Capability completed. NA:SendData: 2 authenticate plain ReadNextLine [stream=27dcf50 nb=4 needmore=0] NA:CreateNewLineFromSocket: + NA:SendData: Logging suppressed for this command (it probably contained authentication information) ReadNextLine [stream=27dcf50 nb=266 needmore=0] NA:CreateNewLineFromSocket: 2 OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE SORT THREAD=REFERENCES THREAD=REFS MULTIAPPEND UNSELECT IDLE CHILDREN NAMESPACE UIDPLUS LIST-EXTENDED I18NLEVEL=1 CONDSTORE QRESYNC ESEARCH ESORT SEARCHRES WITHIN CONTEXT=SEARCH QUOTA] Logged in A:SendData: 3 namespace And all goes well... TB3 seems to be fine without extra capability stuff. Regards, Sebastian

5 20

[Dovecot] For the record: Postfix+Spamassassin+ClamAV+Dovecot
by James Butler 01 Jun '09

01 Jun '09

Postfix 2.5.5 SpamAssassin 3.2.5 (under Perl 5.10.0) ClamAV 0.95.1 Dovecot 1.2.rc2 works fine on Fedora 10. Installed Dovecot and ClamAV from source and everything else using yum. I'm using the ClamAV plugin for Spamassassin: http://wiki.apache.org/spamassassin/ClamAVPlugin I'm calling Spamassassin with: /etc/postfix/main.cf: mailbox_command = /usr/bin/spamc -f -e /usr/local/libexec/dovecot/deliver Postfix hands off to Spamassassin, which processes ALL mail (not just attachments) through the ClamAV plugin before parsing for spam, and then hands the whole mess off to Dovecot for 'deliver' to handle. How simple is that? Since ClamAV scanns all mail, it might be too processor-intensive for really large mail systems, but it is working great for our 120+ user system with lots of spam coming in. If you're using Procmail or some other preprocessor that can hand off to a pipe, then you could skip the plugin and pipe messages over a certain size (i.e. >1024) to clamd, instead. Enjoy! James

4 3