- dovecot - dovecot.org

[Dovecot] Managing IMAP ACL from script
by Неворотин Вадим 06 Apr '10

06 Apr '10

I need to change ALC for mailboxes from a script on my server. As I understand now I can correctly change ACL only via telnet using IMAP commands. And moreover I need to know user's password for it. Is there any plans to add inheritance of ACL and ability to manage it directly from a server? And if it is in which version? Will 2.0 fully support ACL? Now I use Dovecot 1.2.10.

2 1

[Dovecot] Dovecot index storage question
by Stewart Dean 06 Apr '10

06 Apr '10

I currently run DC V1.2 for some 4K accounts using mbox folder format. I am migrating to maildir. I have a separate filesystem for the indices. Currently, the data there amounts to 4GB. I'm wondering if anyone can tell me how the storage used will change with maildir folder formatting. Will more space be used and if so, could you rough guess what the increase might be? -- ==== Once upon a time, the Internet was a friendly, neighbors-helping-neighbors small town, and no one locked their doors. Now it's like an apartment in Bed-Stuy: you need three heavy duty pick-proof locks, one of those braces that goes from the lock to the floor, and bars on the windows.... ==== Stewart Dean, Unix System Admin, Bard College, New York 12504 sdean(a)bard.edu voice: 845-758-7475, fax: 845-758-7035

1 0

[Dovecot] Cant get the config file just right
by eng15ine 06 Apr '10

06 Apr '10

Hello, I have been trying to get POP3 on my ubuntu server for the past week now (In Las Vegas on a family vacation carrying my netbook from hotel to hotel.) My config file is below I am trying to access pop3 from Outlook Express and Thunderbird with no luck. When ever I try to access pop3 with one of these two programs I get a prompt saying my user/pass is invalid and I am asked to logon again. I cant figure out whats wrong?!? Help would be much appreciated. Thanks in advance!!:-D -=-=-=-=-CONFIG FILE BELOW=-=-=-==-=- # Required on x86_64 kernels login_process_size = 64 protocols = imap imaps pop3 pop3s listen = * ssl_listen = * ssl_disable = yes mail_location = maildir:~/Maildir ssl_cert_file = /etc/postfix/ssl/smtpd.crt ssl_key_file = /etc/postfix/ssl/smtpd.key protocol imap { imap_client_workarounds = outlook-idle delay-newmail listen = 127.0.0.1:10143 } protocol pop3 { pop3_uidl_format = %08Xu%08Xv pop3_client_workarounds = outlook-no-nuls oe-ns-eoh } protocol lda { postmaster_address = postmaster(a)example.com } auth default { mechanisms = plain login passdb pam { } userdb passwd { } # user = root socket listen { client { path = /var/spool/postfix/private/auth mode = 0660 user = postfix group = postfix } } } dict { #quota = mysql:/etc/dovecot-dict-quota.conf } plugin { } mail_extra_groups = carlos admin users -- View this message in context: http://old.nabble.com/Cant-get-the-config-file-just-right-tp28146341p281463… Sent from the Dovecot mailing list archive at Nabble.com.

2 1

[Dovecot] Core dump in 2.0-beta4 and latest Mercurial
by B. Johannessen 06 Apr '10

06 Apr '10

I'm seeing core-dumps with both 2.0-beta4 and a fresh checkout from Mercurial. I'm very new to Dovecot, so there's a good chance this is caused by my limited experience with Dovecot configuration, but it's my understanding that any core-dump is considered a bug (nice policy by the way). The installation seemed to be working as expected until I added the two namespaces and tried to set up shared mailboxes. Timo: The installation is running on a KVM dedicated to testing Dovecot, so if you want to debug anything in my environment, just send me your SSH key, and I'll set it up. Attached files (from test with latest Mercurial): ------------------------------------------------- dialog.txt: IMAP dialogue to reproduce the core dump mail.info.txt: Resulting log entries debug.log.txt: Resulting debug-log entries bt-full.txt: br full for dumped core dovecot-n.txt: Output of dovecot -n sql.txt: passdb/userdb SQL configuration -- Regards B. Johannessen

2 1

[Dovecot] back soon / clang static analyzer
by Timo Sirainen 05 Apr '10

05 Apr '10

I had a flu (or something) last week and couldn't get almost anything done. I'm pretty much healed now, and today I spent some time fixing bugs already, but then I got stuck fixing issues reported by clang's static analyzer. The good thing is that it found several real bugs from error handling paths too. I'm now planning on getting the false positive list down to zero and maybe then "make distcheck" could also run the analyzer and fail if there are any warnings, so releases would be less buggy. (I guess I should make some kind of nightly check do that too and email me the results.) Anyway, I'll try to start answering some mails tomorrow. Although I'm also now lagged in my studies and there's an exam on Thursday, so it'll probably take a while to go through all the 100+ mails again..

2 1

[Dovecot] Dovecot+LDAP issues
by Daniel Gomes 05 Apr '10

05 Apr '10

Dear list members, I am having some problems with a LDAP passdb authentication on Dovecot. Before I forget, the specs: it's a Ubuntu 7.10 server running Dovecot 1.0.5 connecting to 2 different machines running LDAP servers: gold with OpenLDAP 2.4.19 and extra with OpenLDAP 2.4.9 (extra is a replication slave of gold). The initial setup of dovecot was with a MySQL passdb, which is still the first passdb, now followed by my new LDAP passdb, all with a static userdb. Here is my dovecot-ldap.conf (the LDAP passdb) (I switched the domain with example.com for privacy sake): ----------------------------------------------------------------- #Servidor hosts = gold.example.com extra.example.com tls = yes ldap_version = 3 base = ou=people,dc=example,dc=com scope = onelevel #uid/gid user_global_uid = 5000 user_global_gid = 5000 #Bind para ler coisas dn = cn=dovecot,ou=people,dc=example,dc=com dnpass = secret sasl_bind = no sasl_mech = #passdb: usar password lookups para autenticar utilizadores auth_bind = no pass_attrs = userPassword=password #, =userdb_home=/home/vmail/%d/%n pass_filter = (&(maildrop=%u)(mailacceptinguser=1)) default_pass_scheme = PLAIN-MD5 ----------------------------------------------------------------- This setup is currently working for some tests users (the others are still being auth'ed with the old MySQL passdb). Unfortunately, I seemed to have run into a big problem on an occasion when dovecot was unable to connect my first server (gold) and hence went to the second one (extra). Backtracking from the logs (starting with dovecot-error.log): Mar 31 13:11:50 bunker dovecot: auth(default): LDAP: ldap_result() failed: Can't contact LDAP server Mar 31 13:11:50 bunker dovecot: auth-worker(default): LDAP: ldap_result() failed: Can't contact LDAP server -------------------- This is when the users stopped being able to login via imap, with the following message being shown on dovecot-info.log: Mar 31 13:13:00 bunker dovecot: auth(default): ldap(user(a)domain.com,xxx.xxx.xxx.xxx): unknown user (I know, an auth_debug log would be handy here, but it wasn't activated at the time). I went on to investigate and from the slapd logs I noticed that the second LDAP server (extra) was being contacted for the passdb lookups, thus proving that dovecot considered the gold to be dead (it wasn't, but that's a different matter). Anyway, the problem is that dovecot doesn't seem to be able to retrieve the user information from extra. As the slapd log shows: Mar 31 13:41:37 extra slapd[31473]: conn=4 op=140 SRCH base="ou=people,dc=example,dc=com" scope=1 deref=0 filter="(&(?=undefined)(?=undefined))" Mar 31 13:41:37 extra slapd[31473]: conn=4 op=140 SRCH attr=userPassword Mar 31 13:41:37 extra slapd[31473]: conn=4 op=140 SEARCH RESULT tag=101 err=0 nentries=0 text= For some reason, dovecot sends an undefined filter to extra, even though the same filter works without issues with gold (and remember they are "clones"). I just can't see how this is caused by any of my configurations! Any ideas? Thanks in advance, -- Daniel Gomes

3 5

[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 04 Apr '10

04 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