- dovecot - dovecot.org

Re: [Dovecot] ¿DC won't start? "leaked file fd 5:"
by mathemat＠gmx.net 06 Feb '09

06 Feb '09

Hi Timo, >> mail.info dovecot: Dovecot v1.0.15 starting up >> mail.err dovecot: auth(default): Panic: Leaked file fd 5: dev 0.10 >> inode 3 > This happens only when Dovecot has been configured with --enable-devel- > checks (or was it --with-debug in v1.0? I'm not sure anymore). The > easiest way to avoid the problem is to not do that. Well, I read that on the net. But the goal was to get it going *without* recompiling... please! :) > The problem is probably related to running in a special environment > which uses some extra fds for some things (possibly a bug or maybe a > feature, who knows) Maybe. But as i got it from an official repo <http://www.dovecot.org/releases/1.0/dovecot-1.0.15.tar.gz>, the thing obviously works for some folks... i'm afraid, they just configured DC somewhat sensefullier (while not documenting this anywhere). Ideas from the profs (you)? -- Psssst! Schon vom neuen GMX MultiMessenger gehört? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger01

2 1

[Dovecot] NFS - inotify vs kqueue
by Jack Stewart 06 Feb '09

06 Feb '09

Hi, I've seen some chatter on NFS boards about kqueue being more reliable than inotify when used in NFSv3 and NFSv2. The chatter is a bit old so I don't know if it is true anymore. Anyone have pro/con experience with dovecot on the inotify/kqueue question when using NFS storage? I realize that kqueue is probably a bit slower and causes some delay with IDLE. Also, it may not really make any difference which is why I ask the question. ---Jack

3 3

[Dovecot] Hi all,
by Jehan Pagès 06 Feb '09

06 Feb '09

Hi all, as I told earlier, I am installing an email server with postfix/dovecot/dspam (for now that's all, though some programs may come later). For now, what works good enough is that I receive mails and spams are tagged. Dovecot version 1.1.7-r1 compiled from the gentoo depository with debug. The path of a mail is 1/ to be passed to dspam by postfix as a virtual transport with this in master.cf: dspam unix - n n - - pipe flags=DRhu user=vmail argv=/usr/bin/dspam --client --deliver=innocent,spam --user ${recipient} and this in main.cf: virtual_transport = dspam 2/ Then in dspam.conf, I have: TrustedDeliveryAgent "/usr/libexec/dovecot/deliver -d %u" UntrustedDeliveryAgent "/usr/libexec/dovecot/deliver -d %u" QuarantineAgent "/usr/libexec/dovecot/deliver -d %u -m Junk" Now dspam is tagging a lot of my spams, with [SPAM] on the subject and in the header stuffs like this: X-DSPAM-Result: Spam X-DSPAM-Processed: Thu Feb 5 23:49:02 2009 X-DSPAM-Confidence: 0.5232 X-DSPAM-Probability: 0.9869 X-DSPAM-Signature: 498b6cde61901804284693 X-DSPAM-Factors: 27, Subject*watch, 0.99000, a+loved, 0.99000, Subject*for+all, 0.99000, ... ... But I wanted spam to go in my Junk folder (using maildir, this is the directory .maildir/.Junk for my configuration. Hence the above configuration of QuarantineAgent. But it doesn't work as my emails are still deliverd to INBOX. How could I check that dovecot deliver is taking into account the option "-m Junk"? Or maybe I don't use it well? (I tried also "-m .Junk" as it it the name of the directory but it is the same) Note also that I use maildir format, so maybe this option works only with mailbox? The doc says: -m <mailbox>: Destination mailbox (default is INBOX). In my dovecot.conf, I have: protocol lda { hostname = mydomain.tld log_path = /home/vmail/dovecot-deliver.log info_log_path = /home/vmail/dovecot-deliver.log auth_socket_path = /var/run/dovecot/auth-master } And when a deliver occures, that's all I have in dovecot-deliver.log: deliver(recipient(a)mydomain.tld): Feb 06 00:59:47 Info: auth input: recipient(a)mydomain.tld deliver(recipient(a)mydomain.tld): Feb 06 00:59:47 Info: auth input: home=/home/vmail/mydomain.tld/recipient/ deliver(recipient(a)mydomain.tld): Feb 06 00:59:47 Info: auth input: uid=1004 deliver(recipient(a)mydomain.tld): Feb 06 00:59:47 Info: auth input: gid=1004 deliver(recipient(a)mydomain.tld): Feb 06 00:59:47 Info: maildir: data=/home/vmail/mydomain.tld/recipient/.maildir deliver(recipient(a)mydomain.tld): Feb 06 00:59:47 Info: maildir++: root=/home/vmail/mydomain.tld/recipient/.maildir, index=, control=, inbox= =/home/vmail/mydomain.tld/recipient/.maildir deliver(recipient(a)mydomain.tld): Feb 06 00:59:47 Warning: Growing pool 'Cache fields' with: 2048 deliver(recipient(a)mydomain.tld): Feb 06 00:59:47 Info: msgid=<000d01c987ed$879c82f0$6400a8c0@biancauj3>: saved mail to INBOX Is there a way to check the options set on parameters in the logs, so that I check that dspam runs indeed QuarantineAgent? Or would you have other solution/hints? Someone on the dspam ml told me that maildrop or sieve are more flexible. So I explain here that my "reason" was simply that I thought it would be better not to install another software/component to remain simple. Moreover with the "-m" option, dovecot-deliver seemed to do just what I needed (I don't need much more complicated). But maybe I am wrong or it is really better not to use dovecot-deliver. If so, just tell me. Thanks. Jehan

2 1

[Dovecot] Tracing a server problem
by Luigi Rosa 06 Feb '09

06 Feb '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I have a Linux CentOS server, 4 Gb RAM, with 50 IMAP users. The server is connected to LAN via a firewall appliance, no filtering applied. Many users with different clients complain a lot of "server disconnected" errors. On the server side Doveco does not report any kind of error. I just ab an unusual rate of "IMAP(xxxxxx@xxxx): Disconnected: Logged out" entries. Given that I am NOT sure about the ethernet an firewall performance, how can I trace this problem? Dovecot is 1.1.10, configured with --with-mysql --with-ssl=openssl - --disable-ipv6 --sysconfdir=/etc --localstatedir=/var Userbase is mysql only. Ciao, luigi - -- / +--[Luigi Rosa]-- \ Too much blood in my alcohol system. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkmIG1MACgkQ3kWu7Tfl6ZQaawCeJbF4hplK06BcSkNnjqg7Lq60 5wsAoJGLKo0+GUiLLPKbyXD0bAtxderl =LTpZ -----END PGP SIGNATURE-----

4 5

[Dovecot] Expire plugin does not work
by Nicolas Letellier 06 Feb '09

06 Feb '09

Hi. I test expire plugin for my dovecot 1.1.8. But, it seems to not work. I have 3 mailboxes on my machine. I want my messages in Junk and Trash expire after 1 day. I removed all messages in them before installing expire plugin. See my dovecot.conf: expire: Trash 1 Junk 1 expire_dict: proxy::expire My dabatases in /var/lib/dovecot are used. When I launch /usr/local/sbin/dovecot --exec-mail ext /usr/local/libexec/dovecot/expire-tool --test, it says: Info: user3(a)domain.tld/Trash: stop, expire time in future: Wed Feb 4 21:00:50 2009 Why this message? I have 3 mailboxes, and the message appears only with this mailbox. The 2 others mailbox have mails into Trash and Junk folders. And the mail are older than 2 days. An ls -lcs say it. When I launch /usr/local/sbin/dovecot --exec-mail ext /usr/local/libexec/dovecot/expire-tool, no messages appears. Nothing in my dovecot logs. Nothing (and I set mail_debug). No messages are deleted. In a mailbox1, I have this into Junk/cur directory: 4 -rw------- 1 dovecot dovecot 3822 Feb 2 13:39 1233569469.M275631P48216.***.***.net,S=3822,W=3945:2,S 4 -rw------- 1 dovecot dovecot 3004 Feb 2 15:43 1233585799.M730005P46882.***.***.net,W=3078,S=3004:2,S 4 -rw------- 1 dovecot dovecot 3056 Feb 2 17:49 1233587786.M676156P51401.***.***.net,S=3056,W=3132:2,S 4 -rw------- 1 dovecot dovecot 3732 Feb 2 17:49 1233592892.M701994P52459.***.***.net,S=3732,W=3823:2,S We are Feb 4, and these message are always here. No informations with mail_debug, or with --test parameter.These messages were arrived Feb 2, and they might have this date in dovecot.index.cache... How expire plugin is working? I don't understand it... -- -Nicolas.

2 2

[Dovecot] ¿DC won't start? "leaked file fd 5:"
by mathemat＠gmx.net 06 Feb '09

06 Feb '09

Hi Gents, (apologizes, new here...) I didn't find any hint on G**gle nor in the Dovecot archieve (maybe due to the lack of a search function :), so: I installed Doovecot, but can't get it going. The logfile states: > mail.info dovecot: Dovecot v1.0.15 starting up > mail.err dovecot: auth(default): Panic: Leaked file fd 5: dev 0.10 inode 3 > mail.err dovecot: Auth process died too early - shutting down I tried many obscure things to recover, but had no luck so far. As long i am just guessing around (auth? dev 0.10?? maybe SSL config?), i have no clue what happens here :(. To make things more interesting: the installation lives on an embedded device (xscale, aka arm w/4MB RAM), where are no extended debug features available (like ltrace, ldd,...), and no newer packages (if exist) available. Tried so far: * uninstall (ipkg remove) * rm'd all files listed in the package description + /var/run/dc/* * reinstall (ipkg install) * changed the config file (in many ways... but what??) The init-script does mainly "/opt/sbin/dovecot", so i tried that command on the CLI(bash) to be sure no script mangles fd's around. "echo $?" gives "0" then, but no DC process is running- log messages as above. I have no clue what to do abt that- where's the point?? Can this hopefully be done whithout installing the complete gcc toolchain and compiling a newer version from source, but by just adapting the config? 8-| Any helpful hints appreciated!, acend -- -- Psssst! Schon vom neuen GMX MultiMessenger gehört? Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger01

2 1

Re: [Dovecot] The 'dbox' Format
by Alexander Beisig 06 Feb '09

06 Feb '09

Timo Sirainen wrote: > On Thu, 2009-02-05 at 22:42 +0100, Alexander Beisig wrote: > > I'd like to give the dbox format a try, but I could not find any > > information on how to enable it. There's information on how to set > > mail_location for the Maildir and mbox formats in the wiki and also in > > the commented configuration file, but how to set it for dbox is > > strangely missing. I took a guess with 'mail_location = dbox:~/dbox', > > but that didn't work, so it's probably not the right way. > > That's correct. > > > Also, the version of Dovecot that Debian installed was 1.0.15, which > > is kinda old. Should there any serious reasons why I should manually > > install a newer version if I'm going to use dbox? > > v1.0's dbox is completely different from what v1.1 has. It's also not > compiled in by default in v1.0. So don't even try using it. Ok thanks, so I downloaded the recent 1.1.11 release. But I still don't know how to enable the dbox format. I think dovecot-example.conf should explain how to enable it, unless you really don't want people to use this format. ____________________________________________________________________ Psssst! Schon vom neuen WEB.DE MultiMessenger gehört? Der kann`s mit allen: http://www.produkte.web.de/messenger/?did=3123

2 1

[Dovecot] Dovecot performance on GFS clustered filesystem
by Allen Belletti 06 Feb '09

06 Feb '09

Hello All, We are using Dovecot 1.1.3 to serve IMAP on a pair of clustered Postfix servers which share a fiber array via the GFS clustered filesystem. This all works very well for the most part, with the exception that certain operations are so inefficient on GFS that they generate significant I/O load and hurt performance. We are using the Maildir format on disk. We're also using Dovecot's deliver from Postfix to handle local delivery. As best I can determine, the worst problems occur when certain users with very large Inboxes (~10k messages) receive new mail and their client looks up information about that message. GFS doesn't seem to efficiently handle the large directories that contain folders like this. As a result, lots of I/O ops are generated and performance suffers for everyone. I am beginning to wonder if it might be more efficient to revert to the old mbox format, with one file per folder (plus whatever indices are creates.) It seems that this ought to work better with GFS which is geared toward smaller numbers of larger files. Is anyone on the list currently doing that? Alternately, any thoughts regarding tuning or other options would be appreciated. Thanks, Allen -- Allen Belletti allen(a)isye.gatech.edu 404-894-6221 Phone Industrial and Systems Engineering 404-385-2988 Fax Georgia Institute of Technology

3 4

[Dovecot] The 'dbox' Format
by Alexander Beisig 06 Feb '09

06 Feb '09

I'd like to give the dbox format a try, but I could not find any information on how to enable it. There's information on how to set mail_location for the Maildir and mbox formats in the wiki and also in the commented configuration file, but how to set it for dbox is strangely missing. I took a guess with 'mail_location = dbox:~/dbox', but that didn't work, so it's probably not the right way. Also, the version of Dovecot that Debian installed was 1.0.15, which is kinda old. Should there any serious reasons why I should manually install a newer version if I'm going to use dbox? __________________________________________________________________ Deutschlands größte Online-Videothek schenkt Ihnen 12.000 Videos!* http://entertainment.web.de/de/entertainment/maxdome/index.html

2 1

[Dovecot] Deferred emails on alias emails
by Jehan Pagès 05 Feb '09

05 Feb '09

Hi, I am currently making a fresh install of email server. I am having some issue with dovecot-antispam (cf. other emails), and noticed that I was having issues on aliases, which apparently where not forwarded to the actual SMTP server after passing through dspam. Still don't figure why but temporarily disable the dspam filter, which anyway is not useful in the current state of this installation. Now the email to an alias are well forwarded to the real finale server. But I still have many emails which were deferred in the last days and I cannot have them decrease. # ls -l /var/spool/postfix/defer/* | wc -l 297 If I run "postqueue -f" to flush this all, I can see the number down, but fastly comes back to 297. Reading the logs, they are passed to dovecot, which was probably the issue before I disabled dspam. It was trying to deliver a message after filtering it, but in the case of aliases, of course, it cannot because the account is not local (so it does not find the account and defers the email forever)! So it should give it back to postfix so that this one contacts the aliased server (gmail.com in the example below). Feb 4 13:33:18 ks34186 postfix/lmtp[31100]: 82769869FA: to=< someemail(a)gmail.com>, orig to=<someemail(a)mydomain.tld>, relay=mail.mydomain.tld[/var/run/dspam/dspam.sock] conn use=28, delay=142296, delays=142277/19/0/0.41, dsn=4.3.0, status=deferred (host mail.mydomain.tld[/var/run/dspam/dspam.sock] said: 421 4.3.0 <someemail(a)gmail.com> Auto-Whitelisted (in reply to end of DATA command)) Feb 4 13:33:18 ks34186 dovecot: auth(default): master in: USER 1 someemail(a)gmail.com service=deliver Feb 4 13:33:18 ks34186 dovecot: auth(default): passwd(someemail(a)gmail.com): lookup Feb 4 13:33:18 ks34186 dovecot: auth(default): passwd(someemail(a)gmail.com): unknown user Feb 4 13:33:18 ks34186 dovecot: auth-worker(default): sql( someemail(a)gmail.com) SELECT maildir as home, 1004 as uid, 1004 as gid FROM mailbox WHERE username = 'someemail(a)gmail.com' AND active = '1' Feb 4 13:33:18 ks34186 dovecot: auth-worker(default): sql( someemail(a)gmail.com) Unknown user Feb 4 13:33:18 ks34186 dovecot: auth(default): master out: NOTFOUND 1 So is there a way please to flush this whole spool so that it now uses the new method (which is stop using dspam until I figure how to use it) and so that I can forward these emails to their recipient? Thanks. Jehan P.S.: this is maybe more a postfix issue than a dovecot issue though... but you probably all know well postfix as well.

3 10

Re: [Dovecot] dovecot Digest, Vol 70, Issue 16
by Anthony Davis 05 Feb '09

05 Feb '09

Please remove me from the mailing list, i have tried a number of times to un-subscribe, but i still keep getting emails... Tony On 4 Feb 2009, at 19:35, dovecot-request(a)dovecot.org wrote: > dovecot(a)dovecot.org

2 1

[Dovecot] dirsize quota in sql pass db?
by Ken Anderson 05 Feb '09

05 Feb '09

Is there a way to return a per user dirsize quota from a passdb sql lookup? If so, what is the syntax? maybe "select quota as userdb_quota"? ..and in mysql table, quota column would be: "quota=dirsize:storage=10240" ? I'm using mbox, with /etc/passwd userdb, and mysql passdb. Thanks, Ken -- Ken Anderson Pacific.Net

3 4

[Dovecot] Error: Maximum number of mail processes exceeded (see max_mail_processes setting)
by Frank Bonnet 05 Feb '09

05 Feb '09

Hello I have this message repeated several times each *seconds* in /var/log/dovecot/dovecot.log the max_mail_processes is set to 8192 and I can see an average of 500 imap processes on the machine , I think there is a problem somewhere ... Debian 64 bits , IBM X3650 biproc , 7 Gb RAM , RAID5 disks , 2 ethernet Gb ports bonded. Dovecot 1.1.11 has been compiled from scratch on the machine Thanks for any info.

4 5

[Dovecot] 1.1.6: PAM passdb/userdb (mis)configuration
by Oved Ben-Aroya 05 Feb '09

05 Feb '09

I'm sure I'm missing something obvious :-( Dovecot version 1.1.6, pam authentication via ldap (openldap). basicly, we use: passdb pam userdb passwd which work fine, except for Outlook/OL Express users that are asked for their password whenever they "send/receive"... We've had also "passdb shadow" that somehow "fixed" this but allowed also users with expired passwords to login :-( re-added for now, untill the correct configuration is achived). Here is the output of dovecot -n: # 1.1.6: /usr/local/etc/dovecot.conf # OS: Linux 2.6.9-55.ELsmp x86_64 Red Hat Enterprise Linux AS release 4 (Nahant Update 7) info_log_path: /var/log/dovecot protocols: imap imaps pop3 pop3s listen(default): * listen(imap): * listen(pop3): *:110 ssl_listen(default): ssl_listen(imap): ssl_listen(pop3): *:995 ssl_ca_file: /usr/local/etc/dovecot/certs/IPS-IPSCABUNDLE.CRT ssl_cert_file: /usr/local/etc/dovecot/certs/dovecot.pem ssl_key_file: /usr/local/etc/dovecot/private/dovecot.pem disable_plaintext_auth: no verbose_ssl: yes login_dir: /usr/local/var/run/dovecot/login login_executable(default): /usr/local/libexec/dovecot/imap-login login_executable(imap): /usr/local/libexec/dovecot/imap-login login_executable(pop3): /usr/local/libexec/dovecot/pop3-login first_valid_uid: 50 mail_debug: yes mail_full_filesystem_access: yes mmap_disable: yes lock_method: dotlock mbox_read_locks: dotlock mbox_write_locks: dotlock mail_executable(default): /usr/local/libexec/dovecot/imap mail_executable(imap): /usr/local/libexec/dovecot/imap mail_executable(pop3): /usr/local/libexec/dovecot/pop3 mail_plugin_dir(default): /usr/local/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/lib/dovecot/pop3 imap_client_workarounds(default): outlook-idle delay-newmail imap_client_workarounds(imap): outlook-idle delay-newmail imap_client_workarounds(pop3): pop3_uidl_format(default): %08Xu%08Xv pop3_uidl_format(imap): %08Xu%08Xv pop3_uidl_format(pop3): %08Xv%08Xu pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh namespace: type: private separator: / prefix: mail/ location: mbox:%h/mail list: yes subscriptions: yes namespace: type: private separator: / location: maildir:%h/Maildir:INDEX=/var/dovecot/index/%u:CONTROL=/var/dovecot/control/%u inbox: yes list: yes subscriptions: yes auth default: verbose: yes debug: yes worker_max_request_count: 10 passdb: driver: pam args: dovecot passdb: driver: shadow userdb: driver: passwd args: blocking=yes Thank you for your help. -- \Oved Dr. Oved Ben-Aroya, Head Unix group, Taub Computer Center, Technion Phone: +972 (4) 829 3688 FAX: +972 (4) 823 6212 oved(a)technion.ac.il PGP key at http://tx.technion.ac.il/~oved/pgp/pubkey PGP Key fingerprint: A9 52 46 04 E8 70 41 99 60 E3 DA 8F BA 39 C2 C8

2 4

[Dovecot] Script: Moving Maildirs between servers
by Peter Lindgren 05 Feb '09

05 Feb '09

Hi, I just migrated from dovecot 1.0.rc29 to 1.1.7, from Sparc platform to Intel, it went very well. In the process I merged folders and excluded folders from being copied. User rights on folders were kept/set. I thought I'd share my migration script with you folks. If there's an interest to put it on the wiki I can do that, but I'm not sure in what page. Use it as a starter if you need to do this yourselves. Prerequisites: * User names are local unix accounts * Old server's /home must be mounted with nfs * Structure and user names must match between the two systems * Source dovecot must be at least version 1.0.x * Destination dovecot must be 1.1.x * Only dovecot data folders and files are copied, neither dovecot indices nor Sieve scripts etc. Here it goes, have fun! /Peter #!/bin/sh # # Migrates dovecot Maildir folders and settings from older dovecot on # old server to new dovecot on new server. # Prerequisites: # * User names are local unix accounts # * Old server's /home must be mounted with nfs # * Structure and user names must match between the two systems # * Source dovecot must be at least version 1.0.x # * Destination dovecot must be 1.1.x # * Only dovecot data folders and files are copied, neither dovecot indices nor Sieve scripts etc. # # Originally created by Peter Lindgren <peter(a)norrskenkonsult.com> # Use this script at your own risk. No warranties whatsoever, of any kind! # Basic settings: The first one you must definitely change, it's where you have mounted the old server's home: SOURCEBASE=/mnt/casiopea-home DESTBASE=/home # Just an abbreviation: MD=Maildir # Change field separator, for find's sake as there might be folders with spaces: # (doesn't play well together with the for loop otherwise) OLDIFS=${IFS} IFS=' ' # User loop: # Depending on your source system's setup, # you probably have non-interactive users with home directories (one of them # is probably named _dovecot) that shall not be copied. Edit the username # exclusion list according to your needs. # for username in `ls $SOURCEBASE`; do { # This is your username exclude list: case $username in (maildir|_dovecot) continue;; esac # Here starts the real work: SOURCEDIR=$SOURCEBASE/$username/$MD DESTDIR=$DESTBASE/$username/$MD echo "================================" echo "Copying user "$username"..." echo "From "$SOURCEDIR" to "$DESTDIR":" # IMAP Folder loop: # Will create the Maildir folder too, the first echo $SOURCEDIR"/." does that. This way all the copying is in one place only. for sourceimap in `{ echo $SOURCEDIR"/." ; find $SOURCEDIR -type d -name \.\* -maxdepth 1 -print ; } | sort -f`; do { # Folder exlusion and special actions: # .Draft is replaced by .Drafts, so content of .Draft must be copied to .Drafts. # (Probably there were a client in use for a while that used .Draft instead of .Drafts.) # Junk mail folders with various names from clients using different languages shall not be copied. # .Trash shall not be copied either. # Folder .INBOX is a leftover from earlier versions of dovecot, and shall not be copied either. # Add your own exceptions to the list. Be sure to quote spaces and dots. basename=`basename $sourceimap` action=copy case $basename in (\.Junk|\.Junk\ E-mail|\.Correo\ electr\&APM-nico\ no\ deseado|\.Skr\&AOQ-ppost|\.Trash|\.INBOX) action=skip;; esac echo -n "$basename" "$action" if [ $action"X" == copy"X" ]; then { echo -n ":" destname=$basename # Merge contents of .Draft and .Drafts to .Drafts: if [ $basename"X" == .Draft"X" ]; then destname=${destname}"s"; fi destimap=${DESTDIR}/${destname} # If this is the Maildir folder (.), a clean desination name is needed for mkdir: if [ $basename"X" == ."X" ]; then destimap=${DESTDIR}; fi mkdir -m 700 "${destimap}" echo -n "." chown ${username} "${destimap}" echo -n "." chmod go-rx "${destimap}" echo -n "." cp -p "${sourceimap}/dovecot-uidlist" "${destimap}" echo -n "." cp -p "${sourceimap}/dovecot-keywords" "${destimap}" echo -n "." cp -pR "${sourceimap}/cur" "${destimap}" echo -n "." cp -pR "${sourceimap}/new" "${destimap}" echo -n "." cp -pR "${sourceimap}/tmp" "${destimap}" echo " done." } else { echo "" } fi }; done # Copy root folder files last in user loop, since the Maildir is created in the imap loop above: cp -p $SOURCEDIR/subscriptions $DESTDIR echo "User "${username}" done." }; done IFS=${OLDIFS} -- Peter Lindgren http://www.norrskenkonsult.com

7 11

[Dovecot] pop3_lock_session question
by Mark Costlow 04 Feb '09

04 Feb '09

Hello, I'm preparing to convert from qpopper + UW-IMAP to dovecot. So far testing has gone very well. One problem we haven't figured out is that long-running POP sessions keep the mailbox locked, so that the MDA times out while trying to deliver. We're using "maildrop" as our MDA if that matters. We don't see this issue for dovecot IMAP sessions. During long-running IMAP sessions, incoming messages are deilvered tot he user's INBOX without delay. But with POP, the MDA times out and the messages go back to sendmail's queue for later delivery. We though this setting would address the issue: # Keep the mailbox locked for the entire POP3 session. pop3_lock_session = no But it doesn't seem to. Any ideas? Here is our "dovecot -n": ---------------------------------------------------------------------- # 1.1.8: /usr/local/etc/dovecot.conf # OS: FreeBSD 7.1-RELEASE-p2 i386 base_dir: /var/run/dovecot/ protocols: imap imaps pop3 pop3s ssl_cert_file: /etc/mail/certs/mail.swcp.com.pem ssl_key_file: /etc/mail/certs/mail.swcp.com.pem ssl_cipher_list: ALL:!LOW:!SSLv2 disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable(default): /usr/local/libexec/dovecot/imap-login login_executable(imap): /usr/local/libexec/dovecot/imap-login login_executable(pop3): /usr/local/libexec/dovecot/pop3-login login_greeting_capability(default): yes login_greeting_capability(imap): yes login_greeting_capability(pop3): no verbose_proctitle: yes first_valid_uid: 1000 first_valid_gid: 100 mail_privileged_group: mail mail_location: mbox:~/:INBOX=/var/mail/%u:INDEX=/var/dovecot/%u mail_full_filesystem_access: yes mmap_disable: yes mail_nfs_storage: yes mail_nfs_index: yes lock_method: dotlock mbox_lock_timeout: 120 dbox_rotate_days: 0 mail_executable(default): /usr/local/libexec/dovecot/imap mail_executable(imap): /usr/local/libexec/dovecot/imap mail_executable(pop3): /usr/local/libexec/dovecot/pop3 mail_plugin_dir(default): /usr/local/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/lib/dovecot/pop3 imap_client_workarounds(default): delay-newmail netscape-eoh tb-extra-mailbox-sep imap_client_workarounds(imap): delay-newmail netscape-eoh tb-extra-mailbox-sep imap_client_workarounds(pop3): pop3_reuse_xuidl(default): no pop3_reuse_xuidl(imap): no pop3_reuse_xuidl(pop3): yes pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh auth default: mechanisms: plain login username_format: %Lu winbind_helper_path: /usr/local/bin/ntlm_auth verbose: yes debug: yes debug_passwords: yes passdb: driver: pam args: session=yes dovecot userdb: driver: passwd args: blocking=yes socket: type: listen client: path: /var/run/dovecot/auth-client mode: 432 master: path: /var/run/dovecot/auth-master mode: 384 ---------------------------------------------------------------------- Thank, Mark -- Mark Costlow | Southwest Cyberport | Fax: +1-505-232-7975 cheeks(a)swcp.com | Web: www.swcp.com | Voice: +1-505-232-7992 abq-strange.com -- Interesting photos taken in Albuquerque, NM Last post: Cruising San Mateo I - 2009-01-04 15:20:30

4 6

[Dovecot] Starting using LaunchDaemons
by Bruce Bodger 04 Feb '09

04 Feb '09

I've figured this one out... Just wanted to get it into the dovecot mailing list archive so that somebody in the future might find it if they need it. Running Dovecot on Mac OS X 10.4.11 and using LaunchDaemon to start. Following a system crash, dovecot failed to restart with this in the system log... Feb 4 10:04:29 G520X2 launchd: org.dovecot: exited with exit code: 89 Feb 4 10:04:29 G520X2 launchd: org.dovecot: respawning too quickly! throttling Feb 4 10:04:29 G520X2 launchd: org.dovecot: 7 more failures without living at least 60 seconds will cause job removal Feb 4 10:04:29 G520X2 launchd: org.dovecot: will restart in 10 seconds Feb 4 10:04:39 G520X2 launchd: org.dovecot: exited with exit code: 89 Feb 4 10:04:39 G520X2 launchd: org.dovecot: respawning too quickly! throttling Feb 4 10:04:39 G520X2 launchd: org.dovecot: 6 more failures without living at least 60 seconds will cause job removal Feb 4 10:04:39 G520X2 launchd: org.dovecot: will restart in 10 seconds Feb 4 10:04:49 G520X2 launchd: org.dovecot: exited with exit code: 89 Feb 4 10:04:49 G520X2 launchd: org.dovecot: respawning too quickly! throttling Feb 4 10:04:49 G520X2 launchd: org.dovecot: 5 more failures without living at least 60 seconds will cause job removal Feb 4 10:04:49 G520X2 launchd: org.dovecot: will restart in 10 seconds The problem turned out to be an old master.pid file (/usr/local/var/ run/dovecot/master.pid) that was left over from the crash. Deleting the file allowed dovecot to restart. Actually, dovecot told me what the problem was when I attempted to start it from the command line as opposed to starting it with the LaunchDaemon... G520X2:root# /usr/local/sbin/dovecot -F Fatal: Dovecot is already running with PID 59 (read from /usr/local/ var/run/dovecot/master.pid) Hope it helps someone else. B. Bodger

2 1

[Dovecot] auth_debug_passwords
by Josh Gentry 04 Feb '09

04 Feb '09

Hi. I'm new to Dovecot and about to start using it in production. In the config file, I set the option, auth_debug_passwords, to yes. I do not see any failed passwords logged, however. It did cause more verbose authentication logging, but failed passwords are still hidden. I have also set these options to yes, because I thought they might be required for auth_debug_passwords to work: auth_verbose = yes auth_debug = yes Here's an example of what I see with a failed login: Feb 3 17:03:36 ebi5 dovecot: auth-worker(default): pam(jkd,some IP): lookup service=dovecot Feb 3 17:03:36 ebi5 dovecot: auth-worker(default): pam(jkd,some IP): #1/1 style=1 msg=Password: Feb 3 17:03:36 ebi5 dovecot: auth-worker(default): pam(jkd,some IP): pam_authenticate() failed: authentication error (password mismatch?) Feb 3 17:03:38 ebi5 dovecot: auth(default): client out: FAIL 1 user=jkd Feb 3 17:03:38 ebi5 dovecot: pop3-login: Aborted login (auth failed, 1 attempts): user=<jkd>, method=PLAIN, rip=some IP, lip=some IP -------Version and config below---------- host:/var/log# dovecot --version 1.1.8 host:/var/log# dovecot -n # 1.1.8: /usr/local/etc/dovecot.conf # OS: FreeBSD 7.1-RELEASE-p2 i386 base_dir: /var/run/dovecot/ protocols: imap imaps pop3 pop3s ssl_cert_file: /etc/mail/certs/mail.ourdomain.com.pem ssl_key_file: /etc/mail/certs/mail.ourdomain.com.pem ssl_cipher_list: ALL:!LOW:!SSLv2 disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable(default): /usr/local/libexec/dovecot/imap-login login_executable(imap): /usr/local/libexec/dovecot/imap-login login_executable(pop3): /usr/local/libexec/dovecot/pop3-login login_greeting_capability(default): yes login_greeting_capability(imap): yes login_greeting_capability(pop3): no verbose_proctitle: yes first_valid_uid: 1000 first_valid_gid: 100 mail_privileged_group: mail mail_location: mbox:~/:INBOX=/var/mail/%u:INDEX=/var/dovecot/%u mail_full_filesystem_access: yes mmap_disable: yes mail_nfs_storage: yes mail_nfs_index: yes lock_method: dotlock mbox_lock_timeout: 120 dbox_rotate_days: 0 mail_executable(default): /usr/local/libexec/dovecot/imap mail_executable(imap): /usr/local/libexec/dovecot/imap mail_executable(pop3): /usr/local/libexec/dovecot/pop3 mail_plugin_dir(default): /usr/local/lib/dovecot/imap mail_plugin_dir(imap): /usr/local/lib/dovecot/imap mail_plugin_dir(pop3): /usr/local/lib/dovecot/pop3 imap_client_workarounds(default): delay-newmail netscape-eoh tb-extra-mailbox-sep imap_client_workarounds(imap): delay-newmail netscape-eoh tb-extra-mailbox-sep imap_client_workarounds(pop3): pop3_reuse_xuidl(default): no pop3_reuse_xuidl(imap): no pop3_reuse_xuidl(pop3): yes pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh auth default: mechanisms: plain login username_format: %Lu winbind_helper_path: /usr/local/bin/ntlm_auth verbose: yes debug: yes debug_passwords: yes passdb: driver: pam args: session=yes dovecot userdb: driver: passwd args: blocking=yes socket: type: listen client: path: /var/run/dovecot/auth-client mode: 432 master: path: /var/run/dovecot/auth-master mode: 384 host:/var/log# Thanks for any light you could shine on this problem. Josh -- Josh Gentry help(a)swcp.com * jgentry(a)swcp.com * 505-232-7992 Customer service in the 21st century.

3 5

Re: [Dovecot] Dovecot-antispam does not work
by Jehan Pagès 04 Feb '09

04 Feb '09

Hi Marcin and everyone, On Tue, Feb 3, 2009 at 7:08 PM, Marcin Rzepecki <m.rzepecki(a)iem.pw.edu.pl>wrote: > Tue, Feb 03, 2009 at 06:14:08PM +0100, Jehan Pag?s wrote: > > Hi, > > > > first of all, thanks for the answer. > > "(Un)fortunately", I don't have these error messages. For information, I > am > > using dovecot 1.1.7r1, compiled from the Gentoo package repository and > the > > only enabled debug I set was "mail_debug = yes". > > The file where I see all debug messages is /var/log/messages, which is > the > > one where all messages from dovecot and postfix are stored under Gentoo > > apparently. > > > > I am recompiling the package with "debug" to see if I see any more debug > > messages. I will make more tests and try to understand this all better, > > because currently it is pretty messy in my head as well about how all > this > > work together (postfix, dovecot, dspam, antispam plugin, etc.). I will > keep > > you up to date, but if ever you have any idea, don't hesitate... > > Hi, > > please, don't forget to CC: your replies to dovecot(a)dovecot.org, maybe > solution would be helpfull for someone else :) > yes sorry for this. I though I was replying to the whole ml. Apparently the ml is not very well configured because a reply does not reply to the whole ml, but to the single sender. I will take care now. > > Errors which I wrote are sent to IMAP client, so are you getting > getting eg. some pop-up window in your client with error message while > trying to move message? I was using the RoundCube web client on my server and had no such message. It was just telling me that it could not move the message. I configured a Thunderbird then and it displayed indeed this message 'Failed to call dspam'. So I made your trick, I compiled myself the dovecot-antispam library and now I can move messages... But are you sure that it is the right method and that the dspam training is indeed called? Because if I read well this piece of code, it looks like it was checking if the dspam training was successful. We commented out this check, so now maybe it fails and we copy the messages anyway to Junk/ even though no training really occurred. And when I check the logs or the dspam_stats, I don't see any change, even though I guess this retraining should be seen as a change in the stats, no? > > Antispam plugin is easy to understand: when you configure antispam_spam > = SPAM it will set SPAM folder as his special folder to observe. When > You get e-mail that was classified incorrect by DSPAM, you can move it > to SPAM folder. Antispam plugin will trigger dspam command to mark this > message as retrained-spam. You can do this of course in reverse order - > moving message _from_ SPAM folder to another will run dspam and mark > message as innocent. Message you are moving must have X-DSPAM-Signature > header (you can check in msg source to see if dspam adds it correctly) > I have the header on every emails. By the way, when one has the item "X-DSPAM-Result: Innocent" in the header, it means the email is not a spam, does'nt it (right now I am focusing on having this plugin working for training purpose, but currently not much is working perfectly as expected in my email spam system)? > > You can provide some info from your log files, i'll try to help. Debug > flag for plugin should effect with some info in debug-logs: > Dec 15 23:54:18 freebsd imap: antispam: plugin initialising (1.1-notgit) > Dec 15 23:54:18 freebsd imap: antispam: no trash folders > Dec 15 23:54:18 freebsd imap: antispam: "SPAM" is spam folder > Dec 15 23:54:18 freebsd imap: antispam: no unsure folders > Dec 15 23:54:18 freebsd imap: antispam: dspam binary set to > /usr/local/bin/dspam > Dec 15 23:54:18 freebsd imap: antispam: dspam extra arg > --user=dump-capability > Dec 15 23:54:18 freebsd imap: antispam: signature header line is > "X-DSPAM-Signature" > Dec 15 23:54:18 freebsd imap: antispam: will silently move mails with > missing signature > [...] > Me I have: Feb 3 22:10:39 ks34186 dovecot: IMAP(jehan(a)zemarmot.net): antispam: plugin initialising (unknown) Feb 3 22:10:39 ks34186 dovecot: IMAP(jehan(a)zemarmot.net): antispam: "trash" is trash folder Feb 3 22:10:39 ks34186 dovecot: IMAP(jehan(a)zemarmot.net): antispam: "Trash" is trash folder Feb 3 22:10:39 ks34186 dovecot: IMAP(jehan(a)zemarmot.net): antispam: "Deleted Items" is trash folder Feb 3 22:10:39 ks34186 dovecot: IMAP(jehan(a)zemarmot.net): antispam: "SPAM" is spam folder Feb 3 22:10:39 ks34186 dovecot: IMAP(jehan(a)zemarmot.net): antispam: "Junk" is spam folder Feb 3 22:10:39 ks34186 dovecot: IMAP(jehan(a)zemarmot.net): antispam: no unsure folders Feb 3 22:10:39 ks34186 dovecot: IMAP(jehan(a)zemarmot.net): antispam: dspam binary set to /usr/bin/dspam Feb 3 22:10:39 ks34186 dovecot: IMAP(jehan(a)zemarmot.net): Growing pool 'antispam-pool' with: 2048 > Cheers, > > -- > Marcin Rzepecki > m.rzepecki(at)iem.pw.edu.pl > > Thanks. Jehan

5 7

[Dovecot] Permission denied problems
by shacky 04 Feb '09

04 Feb '09

Hi. I'm trying to configure Dovecot for Vpopmail. The authentication works good, but I have some "permission denied" error when I try to open the IMAP folders: dovecot: 2009-02-03 19:16:08 Info: imap-login: Login: user=<test(a)testdomain.com>, method=PLAIN, rip=192.168.246.45, lip=172.16.4.106, TLS dovecot: 2009-02-03 19:16:09 Error: IMAP(prova(a)tuttoenumero.it): stat(/home/vpopmail/domains/testdomain.com/test/Maildir/cur) failed: Permission denied This is my dovecot.conf: protocols = imap imaps disable_plaintext_auth = no log_path = /var/log/dovecot.log log_timestamp = "%Y-%m-%d %H:%M:%S " login_greeting = IMAP server ready. mail_location = maildir:/home/vpopmail/domains/%d/%n/Maildir mail_privileged_group = vchkpw mail_access_groups = vchkpw mail_debug = yes mmap_disable = yes (my maildirs are on a NFS filesystem) first_valid_uid = 89 last_valid_uid = 89 first_valid_gid = 89 last_valid_gid = 89 auth_verbose = yes auth_debug = yes auth default { passdb vpopmail { } userdb passwd { } userdb static { args = uid=89 gid=89 mail=Maildir:/home/vpopmail/domains/% } userdb vpopmail { } user = vpopmail } The /home/vpopmail/domains directory and subdirectories are owned by vpopmail.vchkpw and with the permissions 700. The user vpopmail can access to /home/vpopmail/domains/testdomain.conf without any problem. Could you help me to find the problem, please? Thank you very much! Bye.

1 1

[Dovecot] antispam plugin for Dovecot v1.2
by Steffen Kaiser 04 Feb '09

04 Feb '09

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello Johannes, I wonder if you consider upgrading the antispam plugin to v1.2. I checked out the sources, but it is not sufficient to change some bits and I'm missing the knowledge to hack further. Bye, - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iQEVAwUBSYh78nWSIuGy1ktrAQIfVggAjPCdSU+n2OK0hEpodPfczuMA5lSm9mBB u2xOXxc7CrhEJPtqA2Q3MFXUGNFXnEYLR8lUGIAX57mbbjhIYwMSz5DlI24Z6I0o 6QmghmV3mt0cXax1YH+GzXxhvveKWOh+wMwMOoIzrcu5C81iewqamhOq8Fba4kWO KTNIsKwvftIdw6wtyKQj9O4uRlTGzJf01plgMArY6yGglpu8y3d23qhVdwoM5NQ6 K8+9nMQkGhxGuijJYq3L1KpMdmTgMRJET7gp1aqKUx4grqEuSVwyI2LVcLNWGSuq 7XCelO2UhzYOhzuVCBWk0Hyih1eGqyOFXFYtpw7Uhwl8nQ3D30xU7Q== =G1yT -----END PGP SIGNATURE-----

2 2

[Dovecot] starttls
by Sokvantha Youk 04 Feb '09

04 Feb '09

Dear ALL, Could you tell me how can i get starttls working with dovecot authentication via port 25? --- best regards, sokvantha Make Yahoo!7 your homepage and win a trip to the Quiksilver Pro. Find out more

2 1

[Dovecot] Latest CentOS rpms.
by Roderick A. Anderson 04 Feb '09

04 Feb '09

Along with my post about authentication I was wondering if anyone was building RPMs for the later versions of dovecot (and postfix) than I can find in the usual and not-so-usual yum repos? I already pull from rpmforge but would prefer something later than 1.0.7 Say the 1.1 series. Thanks, Rod --

2 3

[Dovecot] Dovecot on Mac - Entourage cannot fetch emails
by Bijo 03 Feb '09

03 Feb '09

Hi, Dovecot 1.1.3 is running on Mac OS X 10.5 latest version, with Maildir (LAYOUT=fs). I have following issues when Entourage 2008 connects it, over imap/imaps. Entourage does not cache the mails. After every restart the folder contents are fetched fresh. I have enabled the Entourage option to get entire messages. Entourage caches the gmail IMAP folders fine. Also Outlook 2007 does not have this problem while connecting to the same IMAP server. I have some big folders with a few thousands of emails. Entourage fails with Error: 4362 (Mail could not be retrieved this time) while fetching mails from these folders. Restarting and rebuilding the Entourage database did not fix this issue. Any tips to resolve these issues or to debug what is going on would be greatly appreciated. Thanks, Bijoy -- View this message in context: http://www.nabble.com/Dovecot-on-Mac---Entourage-cannot-fetch-emails-tp2175… Sent from the Dovecot mailing list archive at Nabble.com.

2 3

[Dovecot] Dovecot 1.1.10 and chroot
by Michal Soltys 03 Feb '09

03 Feb '09

As it's been a while since I upgraded (1.1rc10, jump to 1.1.10), this might be present in earlier versions as well. Anyway, if one enables mail_chroot in global config file, dovecot will try to access /tmp there. Per-user overrides behave correctly. For example, with: mail_chroot=/home/vmail dovecot will abort with: Fatal: chdir(/home/vmail/tmp) failed with uid 65534: No such file or directory Error: imap dump-capability process returned 89 Fatal: Invalid configuration in /etc/dovecot.conf

2 1