- dovecot - dovecot.org

[Dovecot] user lookups not working when using dovecot as lda
by Sven 10 Jun '07

10 Jun '07

Hi Currently I'm using local from postfix for delivering mails. Now I want to change this to using the dovecot lda as I want to use plus addressing. I configured postfix to use dovecot as I found in the wiki and several howtos in the net. My Problem is the following: dovecot delver accepts the mail but bounces it with error: user unknown. Logging in and authentication via imap4 and pop3 works, only deliver seems to be unable to lookup the users from userdb. Has anyone an idea where my mistake is? Here is my actual configuration: dovecot version: 1.0.beta9 postfix version: 2.2.10 system: FreeBSD 6.1-STABLE The system is using maildirs. I changed my postfix/master.cf to the following: dovecot unix - n n - - pipe flags=DRhu user=dovecot:dovecot argv=/usr/local/libexec/dovecot/deliver -d ${recipient} -m ${extension} In my postfix/main.cf I use the following: dovecot_destination_recipient_limit = 1 local_transport = dovecot lda & auth specific settings from my dovecot.conf: protocol lda { postmaster_address = postmaster(a)my-domain.org hostname = mail.my-domain.org #mail_plugins = #mail_plugin_dir = /usr/local/lib/dovecot/imap sendmail_path = /usr/sbin/sendmail auth_socket_path = /var/run/dovecot/auth-master log_path = /var/log/dovecot-deliver.log info_log_path = /var/log/dovecot-deliver.log # syslog_facility = mail } auth_executable = /usr/local/libexec/dovecot/dovecot-auth auth_process_size = 256 auth_debug = yes auth_verbose = yes auth default { mechanisms = plain passdb pam { } userdb passwd { } user = root socket listen { master { path = /var/run/dovecot/auth-master mode = 0666 user = dovecot group = dovecot } client { path = /var/run/dovecot/auth-client mode = 0660 } } } plugin { } Any help is appreciated as I dont know where to look for my mistake. regards, Sven

2 1

[Dovecot] bug in passdb-vpopmail.c
by Moritz Mertinkat 10 Jun '07

10 Jun '07

Hi there, i've tried to compile dovecot-latest.tar.gz (currently dovecot-20070522) with vpopmail support and spotted the following bug (patch is also attached): --- dovecot-20070522/src/auth/passdb-vpopmail.c.orig 2007-05-20 23:11:36.000000000 +0200 +++ dovecot-20070522/src/auth/passdb-vpopmail.c 2007-06-06 09:02:01.968750000 +0200 @@ -66,7 +66,7 @@ password = vpopmail_password_lookup(request, TRUE, &result); if (password == NULL) { - callback(result, "", request); + callback(result, "", 0, request); return; } Greets, Moritz. --- dovecot-20070522/src/auth/passdb-vpopmail.c.orig 2007-05-20 23:11:36.000000000 +0200 +++ dovecot-20070522/src/auth/passdb-vpopmail.c 2007-06-06 09:02:01.968750000 +0200 @@ -66,7 +66,7 @@ password = vpopmail_password_lookup(request, TRUE, &result); if (password == NULL) { - callback(result, "", request); + callback(result, "", 0, request); return; }

2 1

[Dovecot] [Fwd: mulitple instance run problem]
by Stewart Dean 10 Jun '07

10 Jun '07

As I explained, I want to be able to run a second instance of DC through another port to do testing while not interrupting the users using the primary instance in the the regular port. I was instructed to create a second config file with different listen ports and a separate base_dir. I did so and invoked dc with -c pointing to dovecot2.conf. Jun 7 10:04:23 mercury mail:info dovecot: Dovecot v1.0.0 starting up I pointed my client at the non-SSL port, and everything worked fine....until 3 hours later. The client wasn't getting things through, so I checked the syslog on the dc server where I saw rapidly repeating errmsgs:... Jun 7 12:51:07 mercury mail:err|error dovecot: login: Authentication process 10 89784 doesn't exist Jun 7 12:58:55 mercury mail:err|error dovecot: login: Authentication process 10 89784 doesn't exist Jun 7 12:58:59 mercury mail:err|error dovecot: login: Authentication process 10 89784 doesn't exist Jun 7 12:59:01 mercury mail:err|error dovecot: login: Authentication process 10 89784 doesn't exist Jun 7 12:59:05 mercury mail:err|error dovecot: login: Authentication process 10 89784 doesn't exist and many more, then...... Jun 7 13:34:20 mercury mail:err|error dovecot: login: Authentication process 10 89784 doesn't exist Jun 7 13:36:30 mercury mail:err|error dovecot: login: Authentication process 10 89784 doesn't exist Jun 7 13:36:54 mercury mail:err|error dovecot: login: Authentication process 10 89784 doesn't exist I kill the second instance.....but things don't clear up....rather I now get a different errmsg....which must be from the primary dc instance, since the 2nd instance and all of its children are gone (I checked the ps) Jun 7 13:39:20 mercury mail:err|error dovecot: login: Authentication process 10 89784 doesn't exist Jun 7 13:40:00 mercury mail:err|error dovecot: imap-login: Can't connect to aut h server at default: Connection refused Jun 7 13:40:06 mercury mail:err|error dovecot: imap-login: Can't connect to aut h server at default: Connection refused Jun 7 13:40:06 mercury mail:err|error dovecot: imap-login: Can't connect to aut h server at default: Connection refused Finally I do a kill -1 of the primary instance and that cleans things up Jun 7 13:45:46 mercury mail:warn|warning dovecot: SIGHUP received - reloading configuration Is there something I'm doing wrong? Have other people run two instances without problem? I tried starting the second instance and killing it immediately thereafter....that wnet OK, but it hasn't been 3 hours yet. -- ==== Stewart Dean, Unix System Admin, Henderson Computer Resources Center of Bard College, Annandale-on-Hudson, New York 12504 sdean(a)bard.edu voice: 845-758-7475, fax: 845-758-7035

4 5

[Dovecot] auth_username_format
by Sergio Souza 10 Jun '07

10 Jun '07

I configured in the archive dovecot.conf the parameter auth_username_format = “%Ld_%Ln” because the users of my server have access yours e-mail accounts based in /etc/passswd where they are registered in format domain.com_user. This configuration work without problems via pop3 and imap (squirrelmail). My server is CentOS 5.0 and dovecot is 1.0.rc15. The problem that occurs currently is: when the users go to have access the interface of change preferences (ISPCONFIG) where the supplied data of authentication are not the data of the email account (eg. user(a)domain.com) and yes of /etc/passwd the dovecot inserts underscore before the domain (eg. _domain.com_user) when it would have to make this only between the domain and the user. Exists a way to solve this problem? Thanks in advance. -- Sergio Souza

1 0

[Dovecot] Listen on several (but not all) Interfaces
by Dominik Schulz 09 Jun '07

09 Jun '07

Hi, I'm using Dovecot 1.0rc15 from Debian stable/etch. I'd like to have Dovecot listen on more than one interface. It shall listen on one IPv4 Interface and on one IPv6 Interface. The comments in the sample configuration file say, that it's not possible to listen on more than one interface at a time. Sadly it's no option to me to listen on all interfaces. So I'd like to ask if there is a chance that Dovecot will support listening on several selected interfaces anytime soon? Thanks in advance for every helpful reply. Best Regards Dominik

5 4

[Dovecot] Dot Lock probelm resolution
by Stewart Dean 08 Jun '07

08 Jun '07

For the record/archive, so some other unfortunate dovecot implementer won't spend weeks figuring out this particular way dotlocks can have problems... here is what was trashing our dotlocks Basically, I was seeing this: May 14 15:59:58 mercury mail:warn|warning dovecot: IMAP(sdean): Our dotlock file /var/spool/mail/sdean.lock was deleted (kept it 1 secs) > May 14 15:59:58 mercury mail:err|error dovecot: IMAP(sdean): file_dotlock_delete() failed with mbox file /var/spool/mail/sdean: No such file or directory Timo justifiably blamed the usual suspect, NFS, but when I dug into the maillog to see what was going on when the locks were getting trashed, in almost all cases, NFS wasn't involved. And I had recompiled procmail so that it used the same locking strategy (and checked it), deactivated NFS client attribute caching, etc., etc. It turned out that my predecessor had done something 10 years ago that was arcane, inscrutable and kludgy in the .procmailrc file. This *purposefully* trashed the dotlock. Not knowing what it did when I took over (predecessor long gone, things in disarray), I left it in, because I worried that something would break if we removed it. We have perpetuated it in creation of all new accounts. This procmailrc stanza looks like this: ####### BEGIN SYS ADMIN ADDED LINES ####### ## !!!!!! Do not remove these lines !!!!!! ## They have been placed here by System Admin ## If removed, your mail will run slower and ## generate error messages!!!!!!!! LOCKFILE #removes preexisting lockfile LOG='lockfile $DEFAULT$LOCKEXT ' TRAP="rm -f $DEFAULT$LOCKEXT" :0 $DEFAULT ####### END OF SYS ADMIN ADDED LINES ####### # IF YOU ADD STUFF, DO IT ABOVE THIS BLOCK # I sent a note to the procmail mailing list hoping to get a clue of what is doing. Here are my Qs and their As: >> 2) Is it syntactically correct? > I think so, though highly obfuscated and semantically worthless. >> 3) Is what it's doing real/worthwhile? > No. My guess is it was a kludge to work around some error with an > older version of procmail, if it ever served any function at all. Since we removed it, there have been no dotlocking errmsgs in the syslog. -- ==== Stewart Dean, Unix System Admin, Henderson Computer Resources Center of Bard College, Annandale-on-Hudson, New York 12504 sdean(a)bard.edu voice: 845-758-7475, fax: 845-758-7035

1 0

[Dovecot] User unknown in local recipient table? Dovecot LDA/Postfix
by Yu Chen 08 Jun '07

08 Jun '07

This probably is a postfix problem, but I think there are lots of postfix experts/users on this list, and have heard a lot good things about this list, so I am just giving it a try. Thanks in advance! I am using dovecot-1.0.0-8_56.src.rpm downloaded from atrpms.net, and rebuilt from it(rpmrebuild ...). Postfix is 2.4.3. I followed documents at http://wiki.dovecot.org/LDA and LDA/Postfix, and used passwd-file (created /etc/passwd.dovecot file) both as password Database and User database. I can send emails, but not receiving, keep getting the "User unknow error". Do I need to change the "local_recipient_map" in main.cf, and if so, how? Here are some related configuration: ########### dovecot -n ########### # /etc/dovecot.conf log_path: /var/log/dovecot.log ssl_ca_file: /etc/pki/dovecot/certs/ca-bundle.crt verbose_ssl: yes 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/libexec/dovecot/pop3-login login_greeting: Dovecot ready. verbose_proctitle: yes first_valid_uid: 102 mail_extra_groups: mail mail_location: mbox:~/mail:INBOX=/var/mail/%u:INDEX=/var/mail_indexes/%d/%n mail_debug: yes maildir_copy_with_hardlinks: yes mail_executable(default): /usr/local/libexec/dovecot/imap mail_executable(imap): /usr/local/libexec/dovecot/imap mail_executable(pop3): /usr/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/lib64/dovecot/pop3 imap_client_workarounds(default): outlook-idle delay-newmail imap_client_workarounds(imap): outlook-idle delay-newmail imap_client_workarounds(pop3): outlook-idle auth default: mechanisms: plain login executable: /usr/local/libexec/dovecot/dovecot-auth verbose: yes debug: yes debug_passwords: yes passdb: driver: passwd-file args: /etc/passwd.dovecot userdb: driver: passwd-file args: /etc/passwd.dovecot socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: mail master: path: /var/run/dovecot/auth-master mode: 384 ############### postconf -n ################ alias_database = hash:/etc/postfix/aliases alias_maps = hash:/etc/postfix/aliases broken_sasl_auth_clients = yes command_directory = /usr/sbin config_directory = /etc/postfix daemon_directory = /usr/libexec/postfix debug_peer_level = 2 html_directory = /usr/share/doc/postfix-2.4.3-documentation/html inet_interfaces = $myhostname, localhost invalid_hostname_reject_code = 450 mail_owner = postfix mailq_path = /usr/bin/mailq.postfix manpage_directory = /usr/share/man maps_rbl_reject_code = 450 mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain myhostname = my.host.com mynetworks = myip/24, 127.0.0.0/8 newaliases_path = /usr/bin/newaliases.postfix non_fqdn_reject_code = 450 queue_directory = /var/spool/postfix readme_directory = /usr/share/doc/postfix-2.4.3-documentation/readme sample_directory = /etc/postfix sendmail_path = /usr/sbin/sendmail.postfix setgid_group = postdrop smtp_tls_CAfile = /usr/share/ssl/certs/ca-bundle.crt smtp_tls_cert_file = /usr/share/ssl/certs/postfix.pem smtp_tls_key_file = /usr/share/ssl/certs/postfix.pem smtp_tls_session_cache_database = btree:/var/spool/postfix/smtp_tls_session_cache smtpd_recipient_restrictions = permit_mynetworks, permit_sasl_authenticated, permit_tls_clientcerts, reject_unauth_destination, check_relay_domains smtpd_sasl_auth_enable = yes smtpd_sasl_exceptions_networks = $mynetworks smtpd_sasl_path = private/auth smtpd_sasl_security_options = noanonymous smtpd_sasl_type = dovecot smtpd_tls_CAfile = /usr/share/ssl/certs/ca-bundle.crt smtpd_tls_cert_file = /usr/share/ssl/certs/postfix.pem smtpd_tls_key_file = /usr/share/ssl/certs/postfix.pem smtpd_tls_loglevel = 2 smtpd_tls_session_cache_database = btree:/var/spool/postfix/smtpd_tls_session_cache tls_random_source = dev:/dev/urandom unknown_local_recipient_reject_code = 550 virtual_transport = dovecot Regards, C.Y =========================================== Yu Chen Howard Hughes Medical Institute Chemistry Building, Rm 182 University of Maryland at Baltimore County 1000 Hilltop Circle Baltimore, MD 21250 phone: (410)455-6347 (primary) (410)455-2718 (secondary) fax: (410)455-1174 email: chen(a)hhmi.umbc.edu ===========================================

2 1

[Dovecot] PAM info please
by Frank Bonnet 07 Jun '07

07 Jun '07

Hello I'm searching infos on using Dovecot with pam_ldap and FreeBSD 6.2 any pointers welcome :-) Thanks -- Frank

2 2

[Dovecot] Latest MANAGESIEVE patch -- how to start daemon?
by Andreas Ntaflos 07 Jun '07

07 Jun '07

Hello list, I'm using Dovecot 1.0.0 on FreeBSD 6.2-RELEASE and applied the latest MANAGESIEVE patch v3 [1] which seems to have worked smoothly, i.e. all hunks succeeded and no compilation problems. Now this may be stupid question with an obvious answer, but I am at a loss at how to start the daemon? What's the binary called that starts the sieve server? Is there a special way to invoke it? I haven't been able to find anything useful on that matter and there doesn't seem to be a TFM to R yet, the Wiki just links to [1]. What do I have to do? Did I forgot to patch something? I'd appreciate any insight on this subject! Thanks in advance! Andreas [1] http://dovecot.org/list/dovecot/2007-March/021130.html -- Andreas "daff" Ntaflos Vienna, Austria GPG Fingerprint: 6234 2E8E 5C81 C6CB E5EC 7E65 397C E2A8 090C A9B4

5 8

[Dovecot] Quota Warning Message
by Gabriele Fergola 06 Jun '07

06 Jun '07

Hi to everyone, i try to implement in dovecot the quota warning message for the user but withouot success. I do the Patch found on the site but .. nothing happened. Anyone can help me please? Workino

1 0