- dovecot - dovecot.org

[Dovecot] ESORT broken in Dovecot 1.2
by Michael M. Slusarz 20 Mar '09

20 Mar '09

Looks like ESORT is broken (just compiled 1.2 from hg 10 minutes ago). Here is the command I'm using and the corresponding error message: C: 5 UID SORT RETURN (ALL COUNT) (ARRIVAL) US-ASCII UNSEEN S: 5 BAD Error in IMAP command UID: Invalid sort argument. The corresponding UID SORT command (without the RETURN syntax) works fine: 5 UID SORT (ARRIVAL) US-ASCII UNSEEN * SORT 5 OK Sort completed (0.000 secs). michael

2 1

[Dovecot] panic in dovecot 1.1.12
by Martin Preen 20 Mar '09

20 Mar '09

Hello, with some mbox folders I got this error: Mar 18 14:48:12 imap2 dovecot: [ID 107833 mail.crit] Panic: IMAP(xyz): file charset-iconv.c: line 122: unreached I assume that this is related to the folder contents (and not the configration). What does that mean to me ? Martin --------------------------------------------------------------- Martin Preen, Universität Freiburg, Institut für Informatik Georges-Koehler-Allee 52, Raum 00-006, 79110 Freiburg, Germany phone: ++49 761 203-8250 preen(a)informatik.uni-freiburg.de fax: ++49 761 203-8242 www.informatik.uni-freiburg.de

2 2

[Dovecot] Fatal: write() failed to info log: Interrupted system call
by Janos Dohanics 19 Mar '09

19 Mar '09

Last night Dovecot stopped, and the last message in the log was: Fatal: write() failed to info log: Interrupted system call Would you please advise? *** # dovecot -n # 1.1.6: /usr/local/etc/dovecot.conf Warning: mail_extra_groups setting was often used insecurely so it is now deprecated, use mail_access_groups or mail_privileged_group instead # OS: FreeBSD 6.4-PRERELEASE i386 log_path: /var/log/dovecot.log info_log_path: /var/log/dovecot.log protocols: imap pop3 imaps ssl_key_file: /etc/ssl/private/dovecot.key 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 verbose_proctitle: yes first_valid_gid: 0 mail_extra_groups: mail mail_access_groups: mail mail_location: maildir:~/Maildir mail_debug: yes 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 outlook-idle netscape-eoh tb-extra-mailbox-sep imap_client_workarounds(imap): delay-newmail outlook-idle netscape-eoh tb-extra-mailbox-sep imap_client_workarounds(pop3): pop3_client_workarounds(default): pop3_client_workarounds(imap): pop3_client_workarounds(pop3): outlook-no-nuls oe-ns-eoh auth default: verbose: yes debug: yes debug_passwords: yes passdb: driver: passwd-file args: /usr/local/etc/passwd.dovecot userdb: driver: passwd -- Janos Dohanics

2 4

[Dovecot] largefile question
by Martin Preen 19 Mar '09

19 Mar '09

Hello, currently we're using version 1.0.13 with 32bit file offsets. Is it safe to switch to a new version with largefile support enabled ? We want to reuse existing index/cache or do we have to expect errors with that ? Regards. Martin --------------------------------------------------------------- Martin Preen, Universität Freiburg, Institut für Informatik Georges-Koehler-Allee 52, Raum 00-006, 79110 Freiburg, Germany phone: ++49 761 203-8250 preen(a)informatik.uni-freiburg.de fax: ++49 761 203-8242 www.informatik.uni-freiburg.de

2 1

[Dovecot] fchown() error with Public Folders
by Stephen Carville 18 Mar '09

18 Mar '09

I was able to get public folders to work with a dedicated account for the hierarchy and ACL's for individual users. I have location defined so that each user has a local index and control files location = maildir:/usr/mail/public/cs/mail:CONTROL=~/Maildir/CS:INDEX=~/Maildir/CS Now i am seeing the folliwing error in the logs. dovecot: IMAP(stephen): fchown() failed with file /home/stephen/Maildir/CS/.Incoming/dovecot.index.log: Operation not permitted As I understand it, dovecot runs as root but the the IMAP process that servicers the request runs as the user so naturally the fchown() fails. However it seems the file is never even created. It there someting I need to do to get this to work? I am using 1.1.7 # 1.1.7: /etc/dovecot.conf # OS: Linux 2.6.18-92.1.10.el5 x86_64 CentOS release 5.2 (Final) protocols: imaps ssl_cert_file: /etc/pki/dovecot/certs/scacifs02-lnx.dovecot.crt ssl_key_file: /etc/pki/dovecot/private/scacifs02-lnx.dovecot.key login_dir: /var/run/dovecot/login login_executable: /usr/libexec/dovecot/imap-login mail_location: maildir:~/Maildir mbox_write_locks: fcntl namespace: type: private separator: / inbox: yes list: yes subscriptions: yes namespace: type: public separator: / prefix: CS/ location: maildir:/usr/mail/public/cs/mail:CONTROL=~/Maildir/CS:INDEX=~/Maildir/CS list: yes auth default: passdb: driver: pam userdb: driver: passwd-file args: /etc/imap.passwd -- Stephen Carville

3 11

[Dovecot] IMAP ACLs not working
by Seba 18 Mar '09

18 Mar '09

Hi, I've some problems to get folder ACLs working with Dovecot. I've defined some folders (like drafts, spam etc.) for every user and created a dovecot-acl file in every folder so that users can not delete or rename these folders but this does not work as expected. Config ===== Debian Lenny 5.0 Dovecot 1.0.15 dovecot.conf ========= protocols = imap protocol imap { listen = xxx.xxx.xxx.xxx } disable_plaintext_auth = yes log_timestamp = "%Y-%m-%d %H:%M:%S " ssl_disable = yes mail_location = maildir:/home/vmail/%Ld/%Ln namespace private { separator = . prefix = inbox = yes } mail_privileged_group = vmail protocol imap { mail_plugins = acl } protocol lda { postmaster_address = postmaster(a)example.com hostname = hostname(a)example.com mail_plugins = cmusieve } auth_username_translation = %Lu auth default { mechanisms = cram-md5 passdb pam { } passdb sql { args = /etc/dovecot/dovecot-sql.conf } userdb passwd { } userdb static { args = uid=5000 gid=5000 home=/home/vmail/%d/%n allow_all_users=yes } user = root socket listen { master { path = /var/run/dovecot/auth-master mode = 0600 user = vmail } client { path = /var/spool/postfix/private/auth mode = 0660 user = postfix group = postfix } } } Folder structure =========== (For dovecot-acl) /home/vmail/example.com/user/.Spam/dovecot-acl dovecot-acl contains =============== owner lrwstiek For me the config looks OK and I can't find an error... When I change the dovecot-acl to "owner l" for example it seems that this change has no effect. Are there an error in my setup? Seba

3 3

[Dovecot] dovecot1.2beta2( hg tags yields 8834:5284f45c249a) fetch error
by Jonathan Siegle 18 Mar '09

18 Mar '09

Steps to reproduce 1 login testuser testpw 2 select inbox 3 fetch 1 body.peek[HEADER.FIELDS (date)] I get the error 3 BAD Error in IMAP command FETCH: Unknown FETCH modifier This is AIX 5.3 with mbox files. -Jonathan

2 2

[Dovecot] mbox on NFS + automount, folder creation -> mkdir_parents() failed
by Sebastian Kayser 18 Mar '09

18 Mar '09

Hi, i am about to migrate some internal imapd mboxes to dovecot. Regular access is fine, just when i want to create a folder i get the following error message in the logs: Mar 18 17:36:57 pulsar dovecot: [ID 107833 mail.error] IMAP(skayser): mkdir_parents(/home/skayser) failed: Operation not applicable /home/skayser is mounted via autofs. When i set mail_location to a subdirectory within /home/skayser, folder creation works. From looking at the truss output dovecot tries to mkdir() the parent and doesn't seem to like the ENOSYS that is returned when the directoy is an autofs mountpoint. Any chance for a fix, Timo? :) 1549: poll(0x00117818, 3, 1800000) (sleeping...) 1549: poll(0x00117818, 3, 1800000) = 1 1549: read(0, " a 0 0 0 8 S T A T U S".., 3832) = 38 1549: stat64("/home/skayser/foobar3", 0xFFBFF598) Err#2 ENOENT 1549: write(1, " a 0 0 0 8 N O M a i".., 41) = 41 1549: poll(0x00117818, 3, 1800000) = 1 1549: read(0, " a 0 0 0 9 U I D C O".., 3794) = 31 1549: stat64("/home/skayser/foobar3", 0xFFBFF600) Err#2 ENOENT 1549: write(1, " a 0 0 0 9 N O [ T R".., 53) = 53 1549: poll(0x00117818, 3, 1800000) (sleeping...) 1549: poll(0x00117818, 3, 1800000) = 1 1549: read(0, " a 0 0 1 0 C R E A T E".., 3763) = 24 1549: stat64("/home/skayser/foobar3", 0xFFBFF620) Err#2 ENOENT 1549: stat64("/home/skayser/foobar3", 0xFFBFF688) Err#2 ENOENT 1549: mkdir("/home/skayser", 0770) Err#89 ENOSYS 1549: write(2, "01 E m k d i r _ p a r e".., 64) = 64 1549: write(1, " a 0 0 1 0 N O I n t".., 99) = 99 1549: poll(0x00117818, 3, 1799999) (sleeping...) # mount | grep skayser /home/skayser on nfs:/export/home/skayser remote/read/write/setuid/xattr/dev=490000a # dovecot -n # 1.1.11: /opt/csw/etc/dovecot.conf # OS: SunOS 5.9 sun4u disable_plaintext_auth: no login_dir: /var/opt/csw/run/dovecot/login login_executable: /opt/csw/libexec/dovecot/imap-login mail_location: mbox:~/:INBOX=/mail/%u mmap_disable: yes mail_nfs_storage: yes mail_nfs_index: yes mail_drop_priv_before_exec: yes mail_executable: /usr/local/bin/dovecot-imap-wrapper.sh auth default: passdb: driver: pam userdb: driver: passwd Sebastian

2 1

[Dovecot] NFS-error with dovecot 1.1.12
by Martin Preen 18 Mar '09

18 Mar '09

Hello, I'm testing version 1.1.12 and occasionally there is Mar 18 14:40:44 imap2 dovecot: [ID 107833 mail.error] IMAP(xyz): nfs_flush_file_handle_cache_dir: rmdir(/home/xyz) failed: Device busy It seems that it is related to a crash of the previous imap process of that user. And it doesn't seem to cause any problems. So can it safely be ignored ? It is on Solaris 10. Index storage is local (UFS) and mailbox storage is NFS (mail_nfs_storage=yes). Martin --------------------------------------------------------------- Martin Preen, Universität Freiburg, Institut für Informatik Georges-Koehler-Allee 52, Raum 00-006, 79110 Freiburg, Germany phone: ++49 761 203-8250 preen(a)informatik.uni-freiburg.de fax: ++49 761 203-8242 www.informatik.uni-freiburg.de

2 1

Re: [Dovecot] Dovecot LDA and "undeliverable" emails
by Kat Wisnosky 18 Mar '09

18 Mar '09

> Date: Wed, 18 Mar 2009 00:31:32 -0400 > From: Bill Cole <dovecot-20061108(a)billmail.scconsult.com> > Subject: Re: [Dovecot] Dovecot LDA and "undeliverable" emails > To: Dovecot Mailing List <dovecot(a)dovecot.org> > Message-ID: <49C07924.7080707(a)billmail.scconsult.com> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > Kat Wisnosky wrote, On 3/16/09 1:35 PM: >> >> I googled around looking for this, apparantly my google-fu is failing >> this >> morning. I just switched over to using a Postfix/Dovecot virtual set-up >> with Dovecot as the delivery agent. One of my users mistyped his email >> address when he paid for something through Paypal and the reciept got >> forwarded to everyone. It didn't bounce or just go to Postmaster, it was >> delivered to every valid user on the system. >> >> Below is my conf comments stripped: > > Dovecot config is irrelevant. This is a Postfix configuration issue. > You've > provided the proof of that: > > >> And here's the mail.log from a test message that I sent out: >> Mar 16 09:52:46 byron postfix/smtpd[24082]: C75E84F006D: >> client=unknown[xxx.xx.xxx.xx], sasl_method=LOGIN, >> sasl_username=kat(a)amtpolitics.com >> Mar 16 09:52:46 byron postfix/cleanup[24085]: C75E84F006D: >> message-id=<46497375E9264D2BA3BFB31BE37918BC@Kat> >> Mar 16 09:52:46 byron postfix/qmgr[19409]: C75E84F006D: >> from=<kat(a)amtpolitics.com>, size=887, nrcpt=10 (queue active) > > That says that the message from you had 10 recipients as Postfix was > queueing it, *BEFORE* it tried any delivery. It is not possible for the > Dovecot LDA to be involved in whatever caused the message to have 10 > recipients. > > If you cannot figure out why that is happening from looking at your > Postfix > config, I would suggest a visit to the Postfix Users' list. Uhg, I win the CluelessnUnobservant Award for this. Thanks everyone for the followups. I caught that myself yesterday and fixed the problem on Postfix's side. To sum up in case anyone else runs in to this, the mistake I made was in assuming that Postfix just made the handoff to Dovecot and that Dovecot would handle the rest, so I commented out the parts of the old config where Postfix handled this when I was using Postfix virtual transport. Once I restored those and gave Postfix the query it needed, it worked fine. Thanks for bearing with me, everyone. Kat

1 0