- dovecot - dovecot.org

[Dovecot] INBOX stored in AFS
by Hans-Werner Paulsen 30 Oct '08

30 Oct '08

Hello, currently we are storing the incoming mail in the user's home directory, which is within a distributed filesystem called AFS (OpenAFS). Accessing the "mbox" file directly (using the distributed filesystem) works fine with mutt, thunderbird, ... To access the INBOX from a machine, which does not have access to this distributed filesystem, we are using IMAP (UW-imap). Now I wanted to check if dovecot can do the job (maybe faster than UW), and I had the following problem: This is my configuration: ------------------------------------------------------------------------------- # 1.1.4: /opt/dovecot-1.1.4/etc/dovecot.conf log_path: /var/log/dovecot ssl_cert_file: /etc/ssl/certs/imapd.pem ssl_key_file: /etc/ssl/keys/imapd.pem login_dir: /var/run/dovecot/login login_executable: /opt/dovecot-1.1.4/libexec/dovecot/imap-login first_valid_uid: 100 mail_location: mbox:~/Mail:INBOX=~/.maildir/incoming mail_debug: yes mmap_disable: yes mail_nfs_storage: yes mail_nfs_index: yes mbox_write_locks: fcntl mbox_dirty_syncs: no mbox_lazy_writes: no mail_executable: /opt/dovecot-1.1.4/libexec/dovecot/afs-token /opt/dovecot-1.1.4/libexec/dovecot/imap auth default: verbose: yes debug: yes passdb: driver: pam args: setcred=yes session=yes dovecot userdb: driver: passwd ------------------------------------------------------------------------------- When I start my imap-client, I see the content of the INBOX, and I can read, delete, ... the different entries. But when new mail arrives dovecot (and my imap-client) will never notice this. And when I quit my imap-client the dovecot imap server will write back its view of the INBOX, and delete this new mail. This seems to be a problem related to AFS. I poked in the dovecot code and have the following theory: dovecot opens the INBOX R/W, dovecot calls "stat" on the INBOX file periodically to look for modifications. But this does not work, because this machine will stat the local copy (AFS cache) of the INBOX as long as this file is still open R/W. My questions: Is it possible to have a configuration, that the INBOX file is not left open when stat-ing this file? Or is it possible to open the INBOX file R/W only when it us locked? Or is it necessary to modify the code? Thank you for any help, HW -- Hans-Werner Paulsen hans(a)MPA-Garching.MPG.DE MPI für Astrophysik Tel 089-30000-2602 Karl-Schwarzschild-Str. 1 Fax 089-30000-2235 D-85741 Garching

2 2

[Dovecot] read only FS access
by Mathieu Kretchner 30 Oct '08

30 Oct '08

Hello, I would like to know if it's possible to subscribe to a folder that is on a read only File System ? We have a snapshot mechanism that create a .snapshot directly in the user folder. This is done by our NAS and we would like to give an access to this backup to our users. Thanks.

3 7

[Dovecot] dovecot deliver mail bounce problem
by Dhaval Thakar 30 Oct '08

30 Oct '08

Hi list, I am using dovecot deliver for the local mail delivery with qmail. this is working fine. but when mail is sent to invalid user, it gets bounced back with error "I'm not going to try again; this message has been in the queue too long." rather "no mailbox here by that name" I could find proper solution, kindly guide to resolve it. /var/log/maillog Oct 24 23:03:27 backup dovecot: auth(default): master in: USER 1 d(a)arch.xyz.com service=deliver Oct 24 23:03:27 backup dovecot: auth(default): vpopmail(d(a)arch.xyz.com): lookup user=d domain=arch.xyz.com Oct 24 23:03:27 backup dovecot: auth(default): vpopmail(d(a)arch.xyz.com): unknown user Oct 24 23:03:27 backup dovecot: auth(default): prefetch(d(a)arch.xyz.com): passdb didn't return userdb entries, trying the next userdb Oct 24 23:03:27 backup dovecot: auth(default): master out: NOTFOUND 1 no logs in /var/log/dovecot-deliver.log following is the configuration .qmail-default |/var/qmail/bin/preline -f /usr/local/libexec/dovecot/deliver -n -e -d $EXT@$USER dovecot -n # 1.1.5: /etc/dovecot/dovecot.conf protocols: imap ssl_disable: yes disable_plaintext_auth: no login_dir: /usr/local/var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login login_greeting: mail ready. mail_plugins: quota imap_quota trash imap_client_workarounds: delay-newmail outlook-idle namespace: type: private prefix: INBOX. inbox: yes list: yes subscriptions: yes auth default: mechanisms: plain login verbose: yes debug: yes debug_passwords: yes passdb: driver: checkpassword args: /home/vpopmail/bin/vchkpw userdb: driver: vpopmail userdb: driver: prefetch socket: type: listen master: path: /var/run/dovecot/auth-master mode: 384 user: vpopmail group: vchkpw plugin: quota: maildir quota_rule: Trash:ignore

4 3

Re: [Dovecot] First release (v0.1.0) of the new Sieve implementation for Dovecot v1.2
by seriv＠parkheights.dyndns.org 30 Oct '08

30 Oct '08

Thank you Timo, it was my mistake. In 'plugin {}' section line 'sieve = /var/sievescripts/%n/sieve' worked for both cmusieve and sieve plugins. Command 'fileinto "INBOX/foo/bar"' with private namespace configuration you proposed - also worked in both plugins. I suspected that they have different behavior: cmusieve saved message into INBOX/foo/bar, while sieve - into foo/bar as in the deliver log I'm pasting here. But both messages were filed into the same mail folder. Difference in the logging, I think, is not a big problem. --- ls -l Maildir/.foo.bar/new total 8 -rw------- 1 seriv seriv 513 Oct 30 01:57 1225331850.M790093P1351.sisyphus.office.omniti.com,W=526 -rw------- 1 seriv seriv 518 Oct 30 01:59 1225331966.M468658P1400.sisyphus.office.omniti.com,W=531 tail -n 18 /var/log/deliver/dovecot-deliver.log --- deliver(seriv): Oct 30 01:57:30 Info: Loading modules from directory: /usr/lib64/dovecot/modules/lda/ deliver(seriv): Oct 30 01:57:30 Info: Module loaded: /usr/lib64/dovecot/modules/lda//lib90_cmusieve_plugin.so deliver(seriv): Oct 30 01:57:30 Info: Namespace: type=private, prefix=INBOX/, sep=/, inbox=yes, hidden=no, list=yes, subscriptions=yes deliver(seriv): Oct 30 01:57:30 Info: maildir: root exists (/home/seriv/Maildir) deliver(seriv): Oct 30 01:57:30 Info: maildir++: root=/home/seriv/Maildir, index=, control=, inbox=/home/seriv/Maildir deliver(seriv): Oct 30 01:57:30 Info: cmusieve: Using sieve path: /var/sieve-scripts/seriv.sieve deliver(seriv): Oct 30 01:57:30 Info: cmusieve: Executing script /var/sieve-scripts/seriv.sievec deliver(seriv): Oct 30 01:57:30 Info: Namespace INBOX/: Using permissions from /home/seriv/Maildir: mode=0644 gid=-1 deliver(seriv): Oct 30 01:57:30 Info: msgid=<20081030015649.B7936140A88(a)sisyphus.office.omniti.com>: saved mail to INBOX/foo/bar deliver(seriv): Oct 30 01:59:26 Info: Loading modules from directory: /usr/lib64/dovecot/modules/lda/ deliver(seriv): Oct 30 01:59:26 Info: Module loaded: /usr/lib64/dovecot/modules/lda//lib90_sieve_plugin.so deliver(seriv): Oct 30 01:59:26 Info: Namespace: type=private, prefix=INBOX/, sep=/, inbox=yes, hidden=no, list=yes, subscriptions=yes deliver(seriv): Oct 30 01:59:26 Info: maildir: root exists (/home/seriv/Maildir) deliver(seriv): Oct 30 01:59:26 Info: maildir++: root=/home/seriv/Maildir, index=, control=, inbox=/home/seriv/Maildir deliver(seriv): Oct 30 01:59:26 Info: sieve: using sieve path: /var/sieve-scripts/seriv.sieve deliver(seriv): Oct 30 01:59:26 Info: sieve: opening script /var/sieve-scripts/seriv.sieve deliver(seriv): Oct 30 01:59:26 Info: sieve: executing compiled script /var/sieve-scripts/seriv.sieve deliver(seriv): Oct 30 01:59:26 Info: sieve: msgid=<20081030015911.576FC140A88(a)sisyphus.office.omniti.com>: stored mail into mailbox 'foo/bar' -- WBR, Sergey Ivanov. ----- "Timo Sirainen" <tss(a)iki.fi> wrote: > On Wed, 2008-10-29 at 20:31 +0100, Stephan Bosch wrote: > > sergey ivanov schreef: > > > Hi Stephan, > > > Thank you for quick fix. I've built it (from changeset > > > 646:747107b816dc) and it looks like working with dovecot-1.2. > > > I'm doing some testing before put it into Sisyphus repository > > > (http://en.altlinux.org) > > > What I saw - it does not recognize lines like: > > > --- > > > sieve = /var/sievescripts/%n/sieve > > Is this inside protocol lda {} or plugin {}? In former it's not > supposed > to be expanded (shouldn't have been with cmusieve either), in latter > it > should be. > > > > where cmusieve did > > > --- > > > fileinto fileinto "Inbox/R/Commits"; > > > --- > > > this new plugin require changing slashes to dots: > > > --- > > > fileinto fileinto "Inbox.R.Commits"; > > With a namespace configuration like: > > namespace private { > separator = / > prefix = INBOX/ > inbox = yes > } > > And a script: > > require ["fileinto"]; > fileinto "INBOX/foo/bar"; > > It seems to work just fine: > > deliver(tss): Oct 30 00:04:36 Info: sieve: msgid=unspecified: stored > mail into mailbox 'foo.bar' > > Although it probably should use the full untranslated INBOX/foo/bar > name > when logging (same with deliver -m INBOX/foo/bar).

1 0

Re: [Dovecot] First release (v0.1.0) of the new Sieve implementation for Dovecot v1.2
by Stephan Bosch 30 Oct '08

30 Oct '08

sergey ivanov schreef: > Hi Stephan, > Thank you for quick fix. I've built it (from changeset > 646:747107b816dc) and it looks like working with dovecot-1.2. > I'm doing some testing before put it into Sisyphus repository > (http://en.altlinux.org) > What I saw - it does not recognize lines like: > --- > sieve = /var/sievescripts/%n/sieve > --- > as cmusieve did. But it works ok with default .dovecot.sieve files in > user home directories Hmm, I'll look into that. This is not intended and would be a bug. > Then, it reports > --- > error: failed to store into mailbox 'Inbox/R/Commits': Invalid mailbox name. > --- > where cmusieve did > --- > fileinto fileinto "Inbox/R/Commits"; > --- > this new plugin require changing slashes to dots: > --- > fileinto fileinto "Inbox.R.Commits"; This doesn't look like something that has changed for the Sieve implementation specifically. Did you try dovecot-sieve-1.1 with dovecot 1.2 to verify? I'll ask Timo about this. What is the configuration of your mail store. Did you perhaps migrate from mbox to maildir? > I think this changes should be described somewhere. May be, it's > already needed to create wiki page for libsieve at wiki.dovecot.org? Well, first one is probably a bug. The second one I am not sure about yet. I'll get back to you when I do. PS: please reply to the mailing list as well. Your problems and solutions may interest others as well. Regards, -- Stephan Bosch stephan(a)rename-it.nl

4 4

[Dovecot] FTS index generation
by Dave McGuire 30 Oct '08

30 Oct '08

Hi folks. I'm experimenting with the Squat plugin. I can execute search commands via direct interaction with IMAP, but I never see the expected dovecot.index.search index file appear in the spool. I'm concerned that I've misconfigured something that is preventing the creation of those indices. Is there a facility to have the squat plugin generate debugging messages so I can see what it's doing? Thanks, -Dave -- Dave McGuire Ahh, you voted for Bush? Port Charlotte, FL Happy now?

2 3

[Dovecot] Embedded "From<space>" Lines
by Lennart Lövstrand 29 Oct '08

29 Oct '08

Hi. As some of you may remember, I reported a problem a while back where dovecot 1.1.beta14 (as well as dovecot 1.0) would corrupt mbox-style mailboxes by ignoring the Content-Length header and breaking up messages with embededed "From<space>" lines. I recently downloaded Dovecot 1.1.5 and noted to my pleasure that this bug now has been fixed. That's great! This fix envolves checking to see if the expected_body_size (from the Content-Length header) is larger than the body_size produced by the "From<space>" scanner, and if so, if there is a valid "From<space>" line at the "expected" end of the message. However, I also noted that there's a case which the fix doesn't cover, and that's where the "From<space>" line appears as the first line of the body of the message. When this happens, the body_offset will point to the blank line between the headers and the body and not the actual first line of the body. This will cause the stream to be mispositioned at the time of the "From<space>" verification check in istream_raw_mbox_get_body_size and the (actually correct) expected_body_size will be rejected. I have enclosed a simple diff that will work around this by adjusting the body_offset to point to the next line at the time of call to istream_raw_mbox_is_valid_from in istream_raw_mbox_get_body_size. This appears to handle the problem correctly in all the test cases I have. To anyone else who has run into this problem and gotten corrupted mailboxes as a result, I can also offer an mbox checker that will attempt to detect and repair this problem in existing mailboxes as well as inspect them for other problems. I'm not ready to send it out for a full release yet, but interested beta testers are invited to contact me directly. Cheers, --Lennart

2 1

[Dovecot] quota warning not working
by Claudio Prono 29 Oct '08

29 Oct '08

Hi all, I have finally get working the quota with dovecot. Now i am setting up the quota warning, with this in dovecot.conf: quota_warning = storage=70%% /usr/bin/quota_warning.sh 70 In the plugin section naturally. All seems to work fine, the quota is calculated right, but seems the script is not executed... In dovecot logs i have this: deliver(test(a)test.com): Oct 27 15:14:53 Info: Quota warning: bytes=10752000 (70%) messages=0 (0%) command=/usr/bin/quota_warning.sh 70 But...nothing happens. My quota_warning.sh is this: #!/bin/bash PERCENT=$1 echo "/usr/lib/dovecot/deliver -d "$USER" -c /usr/local/etc/dovecot-nowarning.conf" > /var/log/quotanotify cat << EOF | /usr/lib/dovecot/deliver -d "$USER" -c /usr/local/etc/dovecot-nowarning.conf From: postmaster(a)mediaservice.net Subject: quota warning Your mailbox is now $PERCENT% full. EOF I have added the echo for debug pourpose, but no file was created, so the script is not executed. I thinked is a permission problem, but seems not. Now the script is like this: -rwx--x--x 1 dovecot dovecot 317 Oct 27 15:30 /usr/bin/quota_warning.sh What can be the problem? Stuck!!! Claudio. -- ------------ Claudio Prono Systems Development @ Atpss.net Srl, Divisione Implementazione Sistemi Via San Bernardino, 17 - 10137 Torino (TO) - IT Tel +39-011.32.72.100 Fax +39-011.32.46.497 PGP Fingerprint: 75C2 4049 E23D 2FBF A65F 40DB EA5C 11AC C2B0 3647 Disclaimer: http://atpss.net/disclaimer ------------

2 2

[Dovecot] Dovecot pop3 and SonicWall?
by Brandon Lamb 29 Oct '08

29 Oct '08

Hello Has anyone else run into a problem with dovecot pop3 and sonicwall? A week after switching to dovecot we had two local customers call and report they could no longer download emails with attachments. It turned out to be the email macro filter on the router. After the first report I thought maybe the customer had just changed something or it was a fluke, but then a day later we had the second call with the same issue. For some reason, after us switching the sonicwall's email macro filter was catching any attachments as a threat. I couldnt see how changing pop3 servers could affect that, but I guess anything is possible. I just emailed sonicwall and am waiting for a response from them now as well. Hopefully maybe someone has heard of this before. Unfortunately, I dont know if this was pure coincidence, or if both customers happened to have updated their sonicwall software, or maybe it autoupdates, I have no information on it.Of course to them it looks like we broke it. We just had them both turn this rule off for now.

2 1

[Dovecot] Panic: pop3-login: file sasl-server.c: line 75 (authenticate_callback): assertion failed: (client->auth_request == request)
by Mike Abbott 29 Oct '08

29 Oct '08

Running Dovecot-1.1.5, I see this assertion failure: Panic: pop3-login: file sasl-server.c: line 75 (authenticate_callback): assertion failed: (client->auth_request == request) Error: pop3-login: Raw backtrace: 2 pop3-login 0x000000010000ac41 default_fatal_finish + 41 -> 3 pop3-login 0x000000010000acac i_syslog_fatal_handler + 0 -> 4 pop3-login 0x000000010000a446 i_info + 0 -> 5 pop3-login 0x00000001000053a2 authenticate_callback + 126 -> 6 pop3-login 0x000000010000841c auth_client_input_fail + 280 -> 7 pop3-login 0x0000000100007910 auth_client_input + 358 -> 8 pop3-login 0x000000010000e074 io_loop_handler_run + 272 -> 9 pop3-login 0x000000010000d449 io_loop_run + 38 -> 10 pop3-login 0x0000000100004864 main + 1572 -> 11 pop3-login 0x00000001000012fc start + 52 Error: child 1302 (login) killed with signal 6 This happens when I feed multiple user/pass lines to Dovecot all at once like this: $ telnet gromit 110 Connected. Escape character is '^]'. +OK Dovecot ready. user x pass y user x pass y +OK +OK Connection closed by foreign host. The four user/pass lines I pasted in all at once. IMAP login does not crash when presented with multiple login commands, but it does not read them all at once and needs prodding (in the form of extra command lines sent later on) to read them. Actually it appears to read the first two lines then stops reading until more data comes in: $ telnet gromit 143 Connected. Escape character is '^]'. * OK Dovecot ready. a login a b b login c d c login e f d login g h e login i j a NO Authentication failed. b NO Authentication failed. c NO Authentication failed. d NO Authentication failed. e NO Authentication failed. * BAD Error in IMAP command received by server. * BAD Error in IMAP command received by server. * BAD Error in IMAP command received by server. * BAD Error in IMAP command received by server. ^] telnet> q Connection closed. You probably don't care about the odd imap-login behavior, but I tried it and mentioned it just for completeness after seeing pop3-login crash.

2 1