- dovecot - dovecot.org

[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