- dovecot - dovecot.org

[Dovecot] POP3 how do I either retrieve spam or never put mail in spam?
by Tony Nelson 05 Apr '10

05 Apr '10

I retrieve my mail from dovecot over POP3. Sometimes dovecot delivers a message into the spam mailbox, even though I have no spam filtering enabled. I can't find anything in the wiki about "other" mailboxes and POP3. I want to either never deliver mail in any mailbox other than my default inbox, or be able to retrieve mail over POP3 from those other mailboxes. How do I do them? -- ____________________________________________________________________ TonyN.:' <mailto:tonynelson@georgeanelson.com> ' <http://www.georgeanelson.com/>

3 4

[Dovecot] dovecot + Active Directory + LDA
by Christian Lyra 04 Apr '10

04 Apr '10

Hi there, I´m working on a setup with postfix (2.5.5) + dovecot (1.2.11) using a Active Directory user backend. At first, I used the instructions found here[1] to do the base configuration. As I understand, I need to use dovecot as a LDA to be able to use the quota plugin and have a per-user quota configuration, and this led me to two distinct (and opposed) configuration options. It seems that the usual dovecot + AD configuration uses the "auth_bind = yes" option, where the dovecot tries to bind to AD using user credentials. *But* to be able to use LDA, dovecot cant rely on user credentials, as there´s none when a mail arrives, so one need to use "auth_bind = no" and choose a "user" to bind to AD, using the dn and dnpass options. Am I right until here? I could just use auth_bind=no *IF* the "dn" user has the necessary privileges to read other AD users passwords (like a administrator user). Is this correct? Well, antecipating that the AD sysadmin guy will not be happy with this, I thought that maybe I could "mix" the two configurations, since I dont need the user password to find user mailbox (while delivering), but I do while doing his authentication. I may use one configuration for userdb, and another for passdb. BUT (again!) there´s another problem, since delivering needs "email" (user@domain) and authentication needs "user" values (and, it´s perfectly valid that one should use "John Doe" as user, and foo@bar as email!). So, I messed a little with user filters and got this configuration: dovecot.conf: mail_uid = 1001 mail_gid = 1001 passdb ldap { args = /etc/dovecot/dovecot-ldap-pass.conf } userdb ldap { args = /etc/dovecot/dovecot-ldap.conf } dovecot-ldap-pass.conf: hosts = 10.x.x.x base = dc=mydomain,dc=com,dc=br ldap_version = 3 auth_bind = yes auth_bind_userdn = mydomain\%u dovecot-ldap-pass.conf: hosts = 10.x.x.x auth_bind = no dn = cn=Unprivleged User,cn=Users,dc=mydomain,dc=com,dc=br dnpass = 123456 ldap_version = 3 base = dc=mydomain,dc=com,dc=br deref = never scope = subtree user_attrs = sAMAccountName=mail=maildir:/var/vmail/%$/Maildir user_filter = (&(objectClass=person)(|(mail=%u)(sAMAccountName=%u))) pass_attrs = sAMAaccountName=user,userPassword=password pass_filter = (&(objectClass=person)(sAMAaccountName=%u)) The "pass_attrs and pass_filter" in dovecot-ldap-pass.conf is not used. The clever part, or the incredible stupid one, is the the filter (&(objectClass=person)(|(mail=%u)(sAMAccountName=%u))) which means "find some person with email=something OR some person with username=user". I´m not sure of the full implications this could have... Anyway, it´s working, as the system accepts emails and the user can retrieve it using pop3. Is there a better way to doing all this? Is it safe to bind dovecot to AD with the necessary privileges to read user passwords? I´m no AD expert, but can this special user be "read-only" ? thanks in advance [1] http://www.linuxmail.info/postfix-dovecot-ldap-centos-5/ -- Christian Lyra

1 0

[Dovecot] dovecot-2.0.beta4: compiler gets stuck making master-service-settings.o Mac OS X 10.6.2
by Giuliano Gavazzi 03 Apr '10

03 Apr '10

dovecot-2.0.beta4 Environment: MacOS X 10.6.2, Xcode 3.2.1 (gcc-4.2) Problem: ./configure --sysconfdir=/usr/local/conf/ make [...] /bin/sh ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../.. -I../../src/lib -I../../src/lib-settings -DPKG_RUNDIR=\""/usr/local/var/run/dovecot"\" -DSYSCONFDIR=\""/usr/local/conf/dovecot"\" -DBINDIR=\""/usr/local/bin"\" -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -Wstrict-aliasing=2 -MT master-service-settings.lo -MD -MP -MF .deps/master-service-settings.Tpo -c -o master-service-settings.lo master-service-settings.c libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -I../../src/lib -I../../src/lib-settings -DPKG_RUNDIR=\"/usr/local/var/run/dovecot\" -DSYSCONFDIR=\"/usr/local/conf/dovecot\" -DBINDIR=\"/usr/local/bin\" -std=gnu99 -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -Wstrict-aliasing=2 -MT master-service-settings.lo -MD -MP -MF .deps/master-service-settings.Tpo -c master-service-settings.c -fno-common -DPIC -o .libs/master-service-settings.o never ends (well, I let it take over 3 minutes of cpu on a Xserve 2.26GHz Xeon and over 5 minutes on a Core 2 Duo before killing it). Any ideas? Thanks Giuliano

2 2

[Dovecot] Question about SASL auth
by Mark Sapiro 03 Apr '10

03 Apr '10

I have recently upgraded from Dovecot 1.2.10 to 2.0.beta3. I have Postfix 2.3.3 and use Dovecot to provide SASL auth for Postfix. # dovecot -n # 2.0.beta3: /usr/local/etc/dovecot/dovecot.conf # OS: Linux 2.6.18-8.1.14.el5 i686 CentOS release 5 (Final) auth_mechanisms = plain apop login auth_worker_max_count = 5 mail_location = mbox:~/Mail:INBOX=/var/spool/mail/%u mail_privileged_group = mail mbox_write_locks = fcntl dotlock passdb { args = /usr/local/etc/dovecot.passwd deny = no driver = passwd-file master = no pass = no } passdb { deny = no driver = pam master = no pass = no } protocols = imap pop3 service auth { unix_listener /var/spool/postfix/private/auth { mode = 0666 } } ssl_cert = </etc/postfix/sbh16-cert.pem ssl_key = </etc/postfix/sbh16-key.pem userdb { driver = passwd } Since upgrading to 2.0.beta3 I have started seeing notices like Mar 6 07:06:20 sbh16 postfix/smtpd[30273]: warning: SASL: Connect to private/auth failed: Resource temporarily unavailable Mar 6 07:06:20 sbh16 postfix/smtpd[30273]: fatal: no SASL authentication mechanisms in my maillog. I don't see them too often (an average of about 2 occurences per day), and they seem to be related to spam or some kind of attack. I am able to send using SASL authentication from my own client OK. The relevant postfix config settings are smtpd_sasl_auth_enable = yes smtpd_sasl_path = private/auth smtpd_sasl_type = dovecot Postfix and its configuration haven't changed from what I used with Dovecot 1.2.10. With Dovecot 1.2.10, I rarely if ever saw these failures. Is this a case of the socket being in use when another auth request arrives or is it something else? And if it is the socket in use, is there some change in 2.0.beta that would cause the socket to be busy longer? -- Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan

2 7

[Dovecot] simple steps with sieve
by Gavin Hamill 02 Apr '10

02 Apr '10

Today is my first day with sieve, so be gentle :) I'm trying to set up a pretty webmail interface to our Dovecot 1.2.4 server using roundcube. The managesieve config + roundcube 'managesieve' plugin work fine, and I'm able to use roundcube's UI to generate .dovecot.sieve files. We use winbind + LDAP lookups to do some exotic mail rewriting... ultimately user.name(a)domain.com gets rewritten to 'ar-cloh@localhost', and in /home/AD/ar-cloh/.dovecot.sieve there is only this: require ["vacation"]; # rule:[gdh_test] if anyof (header :contains "Subject" "test") { vacation "test away"; } When I send an email to the user, I see this in the mail.log Oct 19 15:39:43 ar-smtp-1 dovecot: deliver(ar-cloh): sieve: msgid=<1255963176.14420.31.camel@gdh-work>: discarding vacation response for message implicitly delivered to <ar-cloh@ar-smtp-1> I don't understand; sending a vacation for implicitly-delivered messages sounds exactly like what I want - is there any way to say 'do this anyway' ? gdh

8 18

[Dovecot] Any info about 1.2->2.0 migration ?
by Michal Hlavinka 02 Apr '10

02 Apr '10

Hi, there are few documents on the wiki ( http://wiki.dovecot.org/Upgrading ) about migration between old versions. Is there any document for 1.2->2.0 or list of configuration changes (especially the missing ones) in 2.0? Regards, Michal Hlavinka

2 1

[Dovecot] IMAP extensions & their meanings
by Jerry 01 Apr '10

01 Apr '10

I know that is is not really a Dovecot problem; however, I was wondering where I could get a complete list of the terms used in the 'capability' line. I have not had any success in finding out what things like "XLIST" refer to. I don't believe that is one that Dovecot uses; however, I have seen it with other IMAP servers, plus lots of other flags that I do not understand. I tried Googling but only got a few sporadic and basically useless answers. Thanks! -- Jerry Dovecot.user(a)seibercom.net Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __________________________________________________________________ The economy depends about as much on economists as the weather does on weather forecasters. Jean-Paul Kauffmann

3 2

Re: [Dovecot] New install authentication probs
by Andy Smith 01 Apr '10

01 Apr '10

Ola Daniel, thanks for the idea, but actually within the config file the settings are not within the auth default section, its just shown that way from the output of dovecot -n cheers Andy. Quoting Daniel Gomes <daniel.gomes(a)ist.utl.pt>: > Hey Andy, > > I might be way over my head here, but unlike you, in my setup I set > "auth_debug", "auth_verbose" and "auth_debug_password" to "yes" > outside the "auth default" section. Try that and see if you get the > verbose logging you're looking for! > > Cheers, > > On 31-03-2010 19:46, Andy Smith wrote: >> Hi Brad, >> >> thanks for the reply, here is the output: >> >> dovecot -n >> # 1.2.10: /usr/local/etc/dovecot.conf >> # OS: FreeBSD 6.1-RELEASE i386 nfs >> log_path: /tmp/dovecot.log >> protocols: imap >> ssl: no >> disable_plaintext_auth: no >> login_dir: /var/run/dovecot/login >> login_executable: /usr/local/libexec/dovecot/imap-login >> verbose_proctitle: yes >> first_valid_uid: 1000 >> first_valid_gid: 1000 >> mail_privileged_group: mail >> mail_location: maildir:/var/spool/mail/%d/%u >> mail_debug: yes >> imap_client_workarounds: delay-newmail netscape-eoh tb-extra-mailbox-sep >> lda: >> sendmail_path: /usr/sbin/sendmail >> auth default: >> mechanisms: plain digest-md5 cram-md5 >> username_format: %Lu >> verbose: yes >> debug: yes >> debug_passwords: yes >> passdb: >> driver: sql >> args: /usr/local/etc/dovecot-sql.conf >> userdb: >> driver: passwd >> args: blocking=yes >> userdb: >> driver: sql >> args: /usr/local/etc/dovecot-sql.conf >> socket: >> type: listen >> client: >> path: /var/run/dovecot/auth-client >> mode: 432 >> master: >> path: /var/run/dovecot/auth-master >> mode: 384 >> > > -- > Daniel Gomes, 55350 >

4 7

[Dovecot] doveadm {user,auth} {segfaults,hangs}
by Pascal Volk 01 Apr '10

01 Apr '10

Since the last changes from yesterday, there are at least two new problems in doveadm (4e527339da8b). doveadm user aaa doveadm(pvo): Error: userdb lookup: connect(/usr/local/dovecot20/var/run/dovecot/auth-userdb) failed: Permission denied (euid=1000(pvo) egid=1000(pvo) missing +r perm: /usr/local/dovecot20/var/run/dovecot/auth-userdb, euid is not dir owner) Segmentation fault (core dumped) doveadm auth xxxx Password: doveadm(pvo): Error: auth: connect(/usr/local/dovecot20/var/run/dovecot/auth-client) failed: Permission denied (euid=1000(pvo) egid=1000(pvo) missing +r perm: /usr/local/dovecot20/var/run/dovecot/auth-client, euid is not dir owner) [hang until]^C Backtraces are attached Regards, Pascal -- The trapper recommends today: beeffeed.1009120(a)localdomain.org (gdb) bt full: #0 0x00000000004063b7 in cmd_user_input (auth_socket_path=0x4117f8 "/usr/local/dovecot20/var/run/dovecot/auth-userdb", input=0x7fff41c65320) at doveadm-auth.c:41 conn = 0x998f50 pool = 0x997ac0 username = 0x0 fields = 0x0 p = 0x0 ret = -1 #1 0x0000000000406ab6 in auth_cmd_common (cmd=0x61a940, argc=2, argv=0x921048) at doveadm-auth.c:201 first = false auth_socket_path = 0x0 input = {username = 0x92107b "aaa", password = 0x0, info = {service = 0x4119da "doveadm", local_ip = {family = 0, u = {ip6 = {__in6_u = {__u6_addr8 = '\000' <repeats 15 times>, __u6_addr16 = {0, 0, 0, 0, 0, 0, 0, 0}, __u6_addr32 = {0, 0, 0, 0}}}, ip4 = {s_addr = 0}}}, remote_ip = {family = 0, u = {ip6 = {__in6_u = {__u6_addr8 = '\000' <repeats 15 times>, __u6_addr16 = {0, 0, 0, 0, 0, 0, 0, 0}, __u6_addr32 = {0, 0, 0, 0}}}, ip4 = {s_addr = 0}}}, local_port = 0, remote_port = 0}} c = -1 #2 0x0000000000406b3e in cmd_user (argc=2, argv=0x921048) at doveadm-auth.c:214 No locals. #3 0x000000000040602f in doveadm_try_run (cmd_name=0x921076 "user", argc=2, argv=0x921048) at doveadm.c:83 cmd__foreach_end = 0x986650 cmd = 0x986590 #4 0x00000000004062da in main (argc=2, argv=0x921048) at doveadm.c:169 set_roots = {0x413860, 0x0} service_flags = 10 cmd_name = 0x921076 "user" error = 0x411685 "H\205\355t\034\061\333\017\037@" c = -1 (gdb) bt full #0 0x00007f114d21cc93 in __epoll_wait_nocancel () from /lib/libc.so.6 fstab_state = {fs_fp = 0x0, fs_buffer = 0x0, fs_mntres = {mnt_fsname = 0x0, mnt_dir = 0x0, mnt_type = 0x0, mnt_opts = 0x0, mnt_freq = 0, mnt_passno = 0}, fs_ret = {fs_spec = 0x0, fs_file = 0x0, fs_vfstype = 0x0, fs_mntops = 0x0, fs_type = 0x0, fs_freq = 0, fs_passno = 0}} __elf_set___libc_subfreeres_element_fstab_free__ = 0x7f114d254220 #1 0x00007f114dd90674 in io_loop_handler_run (ioloop=0x17aaf60) at ioloop-epoll.c:175 ctx = 0x17cdfc0 events = 0x17ce800 event = 0x17aaf60 list = 0x21 io = 0x1 tv = {tv_sec = 2147483, tv_usec = 0} events_count = 1 t_id = 4220376 msecs = 2147483647 ret = -1 i = 0 j = 1306179422 call = false #2 0x00007f114dd8f451 in io_loop_run (ioloop=0x17aaf60) at ioloop.c:350 No locals. #3 0x00000000004067c6 in cmd_auth_input (auth_socket_path=0x411950 "/usr/local/dovecot20/var/run/dovecot/auth-client", input=0x7fff059a42c0) at doveadm-auth.c:136 client = 0x17d0fc0 #4 0x0000000000406a79 in auth_cmd_common (cmd=0x61a920, argc=2, argv=0x175c048) at doveadm-auth.c:191 auth_socket_path = 0x0 input = {username = 0x175c07b "xxxx", password = 0x179d088 "sdfghjk", info = {service = 0x4119da "doveadm", local_ip = {family = 0, u = {ip6 = {__in6_u = {__u6_addr8 = '\000' <repeats 15 times>, __u6_addr16 = {0, 0, 0, 0, 0, 0, 0, 0}, __u6_addr32 = {0, 0, 0, 0}}}, ip4 = {s_addr = 0}}}, remote_ip = {family = 0, u = {ip6 = {__in6_u = {__u6_addr8 = '\000' <repeats 15 times>, __u6_addr16 = {0, 0, 0, 0, 0, 0, 0, 0}, __u6_addr32 = {0, 0, 0, 0}}}, ip4 = {s_addr = 0}}}, local_port = 0, remote_port = 0}} c = -1 #5 0x0000000000406b1a in cmd_auth (argc=2, argv=0x175c048) at doveadm-auth.c:209 No locals. #6 0x000000000040602f in doveadm_try_run (cmd_name=0x175c076 "auth", argc=2, argv=0x175c048) at doveadm.c:83 cmd__foreach_end = 0x17c8650 cmd = 0x17c8570 #7 0x00000000004062da in main (argc=2, argv=0x175c048) at doveadm.c:169 set_roots = {0x413860, 0x0} service_flags = 10 cmd_name = 0x175c076 "auth" error = 0x411685 "H\205\355t\034\061\333\017\037@" c = -1 (gdb)

1 0

[Dovecot] Mbox limit the size
by Karthick G 01 Apr '10

01 Apr '10

Hi, I want to set size limit for the inbox of all users in my mail server. Please send me the steps to be followed or how to configure dovecot to enable limiting the inbox size. Thanks in advance. -- *Regards, Karthick.G *

2 1