- dovecot - dovecot.org

[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

[Dovecot] Multiple DBs
by Sebastian Chociwski 18 Mar '09

18 Mar '09

Welcome, I'm new one here . I've switch to dovecot in order to get mysql auth to recive emails. And I am not sure about one thing : may I configure dovecot to user more then one DB to authorize users ? I have suse 11.1/postfix/mysql system where the users exist in 2 separate DBs. Delivering works well, I'm just not sure if everyone could revive the emails ? Any tips ? reagards, Sebastian

2 1

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

18 Mar '09

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: base_dir= /var/run/dovecot/ login_process_per_connection = no max_mail_processes = 2048 mail_process_size = 1024 protocols = imap imaps pop3 pop3s shutdown_clients = yes log_path = /var/log/dovecot info_log_path = /var/log.dovecot.info log_timestamp = "%b %d %H:%M:%S " ssl_cert_file = /etc/ssl/certs/ssl-cert-snakeoil.pem ssl_key_file = /etc/ssl/private/ssl-cert-snakeoil.key ssl_disable = no disable_plaintext_auth = no login_dir = /var/run/dovecot/login login_chroot = yes login_user = dovecot login_greeting = Dovecot ready mail_location = maildir:/home/vmail/%d/%n mmap_disable = no valid_chroot_dirs = /var/spool/mail protocol lda { postmaster_address = kat(a)amtpolitics.com log_path = /home/vmail/dovecot-deliver.log # UNIX socket path to master auth server to find users: auth_socket_path = /var/run/dovecot/auth-master # Enabling Sieve plugin for server-side mail filtering # Will be handy for Spam - will be implemented later. #mail_plugins = cmusieve #global_script_path = /home/vmail/globalsieverc } protocol imap { login_executable = /usr/lib/dovecot/imap-login mail_executable = /usr/lib/dovecot/imap } protocol pop3 { login_executable = /usr/lib/dovecot/pop3-login mail_executable = /usr/lib/dovecot/pop3 pop3_uidl_format = %08Xu%08Xv } auth_executable = /usr/lib/dovecot/dovecot-auth auth_verbose = yes auth_debug = yes auth default_with_listener { 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 } } mechanisms = plain login passdb sql { # Path for SQL configuration file, see /etc/dovecot/dovecot-sql.conf for example args = /etc/dovecot/dovecot-sql.conf } userdb static { args = uid=5000 gid=5000 home=/home/vmail/%d/%n allow_all_users=yes } } imap_client_workarounds = delay-newmail outlook-idle netscape-eoh pop3_client_workarounds = outlook-no-nuls oe-ns-eoh login_process_size = 64 namespace private { separator = . prefix = INBOX. inbox = yes } 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) Mar 16 09:52:47 byron postfix/smtpd[24082]: disconnect from unknown[216.70.186.80] Mar 16 09:52:47 byron postfix/pipe[24096]: C75E84F006D: to=<xxxx(a)amtpolitics.com>, orig_to=<nonexistantemail(a)amtpolitics.com>, relay=dovecot, delay=0.27, delays=0.2/0.01/0/0.06, dsn=2.0.0, status=sent (delivered via dovecot service) Mar 16 09:52:47 byron postfix/pipe[24092]: C75E84F006D: to=<xxxxx(a)amtpolitics.com>, orig_to=<nonexistantemail(a)amtpolitics.com>, relay=dovecot, delay=0.27, delays=0.2/0.01/0/0.07, dsn=2.0.0, status=sent (delivered via dovecot service) Mar 16 09:52:47 byron postfix/pipe[24107]: C75E84F006D: to=<xxxxx(a)amtpolitics.com>, orig_to=<nonexistantemail(a)amtpolitics.com>, relay=dovecot, delay=0.3, delays=0.2/0.04/0/0.06, dsn=2.0.0, status=sent (delivered via dovecot service) Mar 16 09:52:47 byron postfix/pipe[24098]: C75E84F006D: to=<xxxxx(a)amtpolitics.com>, orig_to=<nonexistantemail(a)amtpolitics.com>, relay=dovecot, delay=0.3, delays=0.2/0.02/0/0.08, dsn=2.0.0, status=sent (delivered via dovecot service) Mar 16 09:52:47 byron postfix/pipe[24102]: C75E84F006D: to=<kat(a)amtpolitics.com>, orig_to=<nonexistantemail(a)amtpolitics.com>, relay=dovecot, delay=0.3, delays=0.2/0.03/0/0.08, dsn=2.0.0, status=sent (delivered via dovecot service) Mar 16 09:52:47 byron postfix/pipe[24086]: C75E84F006D: to=<xxxx(a)amtpolitics.com>, orig_to=<nonexistantemail(a)amtpolitics.com>, relay=dovecot, delay=0.31, delays=0.2/0/0/0.1, dsn=2.0.0, status=sent (delivered via dovecot service) Mar 16 09:52:47 byron postfix/pipe[24094]: C75E84F006D: to=<xxxxx(a)amtpolitics.com>, orig_to=<nonexistantemail(a)amtpolitics.com>, relay=dovecot, delay=0.31, delays=0.2/0.01/0/0.09, dsn=2.0.0, status=sent (delivered via dovecot service) Mar 16 09:52:47 byron postfix/pipe[24105]: C75E84F006D: to=<xxxx(a)amtpolitics.com>, orig_to=<nonexistantemail(a)amtpolitics.com>, relay=dovecot, delay=0.31, delays=0.2/0.03/0/0.07, dsn=2.0.0, status=sent (delivered via dovecot service) Mar 16 09:52:47 byron postfix/pipe[24109]: C75E84F006D: to=<xxxxx(a)amtpolitics.com>, orig_to=<nonexistantemail(a)amtpolitics.com>, relay=dovecot, delay=0.31, delays=0.2/0.04/0/0.06, dsn=2.0.0, status=sent (delivered via dovecot service) Mar 16 09:52:47 byron postfix/pipe[24101]: C75E84F006D: to=<xxxxx(a)amtpolitics.com>, orig_to=<nonexistantemail(a)amtpolitics.com>, relay=dovecot, delay=0.33, delays=0.2/0.02/0/0.1, dsn=2.0.0, status=sent (delivered via dovecot service) Mar 16 09:52:47 byron postfix/qmgr[19409]: C75E84F006D: removed Thanks for any help, Kat

4 3

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

17 Mar '09

Timo wrote: > So Postfix delivers bounces to everyone by calling Dovecot LDA > separately for each bounce? Looks like a Postfix configuration problem > to me. I should have been more specific... because we'd also changed domain names at the time we moved over to using Dovecot as the LDA, I temporarily disabled automatically bouncing mail addressed to invalid users because I figured that we'd have at least one who decided that they didn't want the standard formation of email addresses... What I'd wanted to happen was for Postfix to accept the message(s) and then for them to be delivered to the postmaster address so that I could address the issue. I'm still unsure as to why, when Dovecot couldn't find the user in the tables, it copied the message to every user of the system - that seems like odd behavior, which indicates that even though the system is "working", I need to fine-tune something. And at Charles request, here's the output of dovecot -n: # 1.0.10: /etc/dovecot/dovecot.conf base_dir: /var/run/dovecot/ log_path: /var/log/dovecot info_log_path: /var/log.dovecot.info protocols: imap imaps pop3 pop3s 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(pop3): /usr/lib/dovecot/pop3-login login_greeting: Dovecot ready login_process_per_connection: no valid_chroot_dirs: /var/spool/mail max_mail_processes: 2048 mail_location: maildir:/home/vmail/%d/%n mail_executable(default): /usr/lib/dovecot/imap mail_executable(imap): /usr/lib/dovecot/imap mail_executable(pop3): /usr/lib/dovecot/pop3 mail_process_size: 1024 mail_plugin_dir(default): /usr/lib/dovecot/modules/imap mail_plugin_dir(imap): /usr/lib/dovecot/modules/imap mail_plugin_dir(pop3): /usr/lib/dovecot/modules/pop3 imap_client_workarounds: delay-newmail outlook-idle netscape-eoh pop3_uidl_format(default): pop3_uidl_format(imap): pop3_uidl_format(pop3): %08Xu%08Xv pop3_client_workarounds: outlook-no-nuls oe-ns-eoh namespace: type: private separator: . prefix: INBOX. inbox: yes auth default_with_listener: mechanisms: plain login verbose: yes debug: yes passdb: driver: sql args: /etc/dovecot/dovecot-sql.conf userdb: driver: static args: uid=5000 gid=5000 home=/home/vmail/%d/%n allow_all_users=yes socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix master: path: /var/run/dovecot/auth-master mode: 384 user: vmail

3 2

[Dovecot] ACLs are applied recursively to sub mailboxes
by Sascha Wilde 17 Mar '09

17 Mar '09

Hi *, The problem is most noticeable when a user shares his INBOX[0][1] with others: User A sets his INBOX acls to "eilprwtsd" Now User B can see _all_ sub mailboxes and sub sub [...] mailboxes and their contents of User A: User A: g getacl INBOX * ACL "INBOX" "A(a)example.com" akxeilprwtscd "B(a)example.com" eilprwtsd "A(a)example.com" lrwstipekxacd g OK Getacl completed. g getacl INBOX/foobar * ACL "INBOX/foobar" "1(a)aztec.intevation.de" lrwstipekxacd User B: l list "" "*" * LIST (\Noselect \HasChildren) "/" "user" * LIST (\Noselect \HasChildren) "/" "user/1(a)aztec.intevation.de" * LIST (\HasChildren) "/" "INBOX" * LIST (\HasNoChildren) "/" "INBOX/Gesendet" * LIST (\HasChildren) "/" "user/1(a)aztec.intevation.de/foobar" * LIST (\HasNoChildren) "/" "user/1(a)aztec.intevation.de/foobar/barbaaz" * LIST (\HasNoChildren) "/" "user/1(a)aztec.intevation.de/INBOX" l OK List completed. The RfC is not to verbose on this topic of scope, but I think the following excerpt from RfC4314: 2. Access Control [...] An access control list is a set of <access identifier,rights> pairs. An ACL applies to a mailbox name. indicates that ACLs are only valid for individual mailboxes (name) and not for sub mailboxes. cheers sascha [0] Yes, there are really actual users wanting to do this. [1] There is actually another bug in this context I'll report in my next mail... -- Sascha Wilde OpenPGP key: 4BB86568 http://www.intevation.de/~wilde/ http://www.intevation.de/ Intevation GmbH, Neuer Graben 17, 49074 Osnabrück; AG Osnabrück, HR B 18998 Geschäftsführer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner

3 12

[Dovecot] how about my setup
by Stacker Hush 17 Mar '09

17 Mar '09

Hello to tall. Can someone please confirm if my config is secure? Thanks, Wilson dovecot -n # 1.0.7: /etc/dovecot.conf login_dir: /var/run/dovecot/login login_executable(default): /usr/libexec/dovecot/imap-login login_executable(imap): /usr/libexec/dovecot/imap-login login_executable(pop3): /usr/libexec/dovecot/pop3-login mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_plugin_dir(default): /usr/lib/dovecot/imap mail_plugin_dir(imap): /usr/lib/dovecot/imap mail_plugin_dir(pop3): /usr/lib/dovecot/pop3 auth default: passdb: driver: pam userdb: driver: passwd

2 1

[Dovecot] Dovecot as a POP3-/POP3SSL-proxy in front of exchange 2003
by south africa 17 Mar '09

17 Mar '09

Dear all, im looking for a solution to protect an Exchange 2003 email server from direct "pop3-internet-connects". Is it possible that Dovecot act as a POP3-/POP3SSL-Proxy, "LDAP-authenticate" all user logins to a Windows 2003 domain controller and forward then all POP3-connects to a single Exchange 2003 server? Could someone give me some advices or a link for howtos for this solution? The howto on www.dovcot.org (http://wiki.dovecot.org/HowTo/ImapProxy) does not fit in my situation because it prefere a mysql server and not a LDAP-server/domain-controller. Greetings Paul _____________________________________________________________ Get your FREE TheDoghouseMail email address at http://www.thedoghousemail.com

2 1