August 2005 - dovecot

[Dovecot] thanks for changing the name of the alpha tarfile!
by Joakim Verona 28 Aug '05

28 Aug '05

Its much easier to build RPM:s now, thanks :) -- Joakim Verona www.verona.se

1 0

[Dovecot] Permission denied changing to mail directory
by Chris Hogan 28 Aug '05

28 Aug '05

I have 3 domains using one mail server. I've set the dovecot mail directories to be /mail/mail/%d/%n When someone logs on, dovecot attempt to navigate to the domain directory first & we get a permission denied, and we get no further. Its very odd because (a) it was working up until 16:50 on Thursday & (b) the directories now have 777 access. Each user is (at present) a separate unix user & the directories are owned by root & have a file group of mail. I would have thought that the 777 access would have been enough. I don't know what we did on Thursday evening, but any ideas about how to fix the permissions problem? Chris

3 2

[Dovecot] Dovecot and Active Directory Authentication
by Dave Smith 28 Aug '05

28 Aug '05

First off, sorry if this has been asked before - I have looked, honest. Is it possible to get dovecot to authenticate users against active directory, treating the AD as a plain ldap server? I have this working with cyrus saslauthd. Currentlt I get a long delay (30 seconds or so) then * BYE Disconnected for inactivity. All I get in the maillog is imap-login: Disconnected: Inactivity [::ffff:127.0.0.1] I am using dovecot-0.99.11-2.EL4.1 on CentOS 4. If anybody has got this to work then please let me know - otherwise I will be forced to use Cyrus........ Cheers Dave Smith

2 1

[Dovecot] Dovecot Delivery Bug
by Marc Perkel 27 Aug '05

27 Aug '05

Ran into an interesting bug in Dovecot delivery. A friend forwards an email to me as an atachment. When I receive it - it comes in as two separate messages. One is the forwarding message which is empty, and the other is the original message that was forwarded but it comes in as if I had got the email directly. If I use exim to deliver the message to the mailbox it works. But when exim pipes the message into dovecot deliver it gats split. -- Marc Perkel - marc(a)perkel.com Spam Filter: http://www.junkemailfilter.com My Blog: http://marc.perkel.com

1 0

Re: [Dovecot] Authenticate user thru PAM
by Chris Wakelin 27 Aug '05

27 Aug '05

Adrian Mak wrote: > my mailsystem is using postfix and virtual mailbox which stored in mysql db. > SMTP AUTH is using PAM, pam-mysql to authenticate against a mysql db. > > I installed dovecot 0.99-14. In the dovecot example config file > it mentioned that auth_passdb can check against thru PAM but auth_userdb didn't > > Does it mean that auth_userdb should use other means e.g. /etc/passwd, > shadow, vpopmail, etc and in my case it is mysql. Right ? Yes, at least in 1.0-alpha1/stable, so I guess the same for 0.99. Dovecot can authenticate via mysql directly, of course (but I've never done it, so don't ask me how!) Chris -- --+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+- Christopher Wakelin, c.d.wakelin(a)reading.ac.uk IT Services Centre, The University of Reading, Tel: +44 (0)118 378 8439 Whiteknights, Reading, RG6 2AF, UK Fax: +44 (0)118 975 3094

1 0

Re: [Dovecot] Dovecot and Active Directory Authentication
by Chris Wakelin 27 Aug '05

27 Aug '05

Dave Smith wrote: > First off, sorry if this has been asked before - I have looked, honest. > > Is it possible to get dovecot to authenticate users against active > directory, treating the AD as a plain ldap server? I have this working > with cyrus saslauthd. > I have it working with PAM and pam_ldap in 1.0-stable/alpha1, but with userdb = passwd (we have users in NIS as well as AD). Search the mail archives for details! LDAP auth won't work directly as it expects to find a hashed version of the password. > I am using dovecot-0.99.11-2.EL4.1 on CentOS 4. Probably a good idea to upgrade to dovecot-1.0-stable or dovecot-1.0-alpha1 (0.99.11 is pretty old, even 0.99.14 is pretty well obsolete). Best Wishes, Chris -- --+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+- Christopher Wakelin, c.d.wakelin(a)reading.ac.uk IT Services Centre, The University of Reading, Tel: +44 (0)118 378 8439 Whiteknights, Reading, RG6 2AF, UK Fax: +44 (0)118 975 3094

1 0

[Dovecot] Wiki of dovecot.conf file
by Tim Schaefer 26 Aug '05

26 Aug '05

What would be extremely helpful is a really clean explanation of how to set up connections for MySQL. It would have to start with basic information and some real-world examples that make no assumptions, and clearly spell it out without confusion. In fact good examples reduce the need to subscribe to mailing lists and ask dumb questions! The current assumptions in the docs to date are that somehow non-geeks and those of us who have learned far more about email servers than we ever wanted to will somehow "get it" without decent examples. This has got to be the biggest problem using Dovecot. I've tried just about every pop-server I can find and I am about to give up on Dovecot if I can't get the connection to MySQL to work. I just want decent pop server that understands Maildir, now that I went through Cyrus SASL hell and got that working--again with incredibly poor documentation. And I don't give a rats-ass about IMAP, just need a pop server. Maybe IMAP later, for now just a pop server that understands Maildir and comes from open source. I'm using Postfix but it shouldn't matter. So far I've tried the following pop servers: nupop-1.3.9 -- can't compile qmail-1.03 -- a f**ing nightmare cyrus-imap/pop -- poor-to-no docs for pop server -- another nightmare vm-pop3d-1.1.6 -- works only on mbox flexpop-1.0.1 -- no docs , doesn't compile popular-1.5.5 -- docs are too sketchy for installation, too complicated and doesn't work I thought Dovecot would be the last one I have to screw with, but maybe I'm wrong... Thanks, Tim

2 1

[Dovecot] Compile trouble with mysql
by Tim Schaefer 26 Aug '05

26 Aug '05

Hi, I had a devil of a time compiling Dovecot with MySQL, but got it as follows: MYSQL=/usr export CPPFLAGS="-I${MYSQL}/include -I${MYSQL}/lib -I/usr/local/ssl/ -I/usr/local/ssl/include/ " export LDFLAGS="-L${MYSQL}/lib -R${MYSQL}/lib -I${MYSQL}/include -I${MYSQL}/lib -L/usr/local/lib -L/usr/local/ssl/lib" export SSL_FLAGS="-I/usr/local/ssl/ -I/usr/local/ssl/include/" export SSL_LIBS="-L/usr/local/lib -L/usr/local/ssl/lib" ./configure --localstatedir=/var --with-mysql=/usr ... Install prefix ...................... : /usr/local File offsets ........................ : 64bit I/O loop method ..................... : poll File change notification method ..... : dnotify Building with SSL support ........... : yes (OpenSSL) Building with IPv6 support .......... : yes Building with pop3 server ........... : yes Building with mail delivery agent .. : yes Building with user database modules . : static passdb passwd passwd-file checkpassword mysql (modules) Building with password lookup modules : passwd passwd-file shadow pam checkpassword mysql (modules) This is basically for somebody who RPM'd MySQL into /usr . I also figured out the less you give ./configure the better off you are. And...maybe you could help **me**.. :-) If you could post a few samples of how to actually connect to MySQL that would be great, for some reason I STILL cannot connect to MySQL even though I know the user/pass works for my dovecot userid. I know MySQL is compiled into dovecot but still cannot get the connect to work. I've tried: my dovecot.conf: auth default { mechanisms = plain passdb sql { args = /usr/local/etc/dovecot-mysql.conf } userdb sql { args = /usr/local/etc/dovecot-mysql.conf } } my dovecot-mysql.conf: driver = mysql connect = host=127.0.0.1 dbname=dovecot user=dovecot password=dovecot port=3306 connect = host=mydomain dbname=dovecot user=postfix password=postfix port=3306 connect = host=mydomain dbname=dovecot user=dovecot password=dovecot port=3306 connect = host=localhost dbname=dovecot user=dovecot password=dovecot port=3306 connect = host=/var/lib/mysql/mysql.sock dbname=dovecot user=dovecot password=dovecot port=3306 I get: Aug 26 10:45:35 dovecot: auth-worker(default_with_listener): mysql: Connect failed to (null) (dovecot): Access denied for user 'dovecot'@'localhost' (using password: YES) - waiting for 1 seconds before retry Aug 26 10:45:35 dovecot: auth-worker(default): mysql: Connect failed to (null) (dovecot): Access denied for user 'dovecot'@'localhost' (using password: YES) - waiting for 1 seconds before retry Aug 26 10:47:17 dovecot: Killed with signal 15 Aug 26 10:47:21 dovecot: auth-worker(default): mysql: Connect failed to (null) (dovecot): Access denied for user 'dovecot'@'localhost' (using password: YES) - waiting for 1 seconds before retry Help! Tim

1 0

[Dovecot] Compile trouble with mysql
by Tim Schaefer 26 Aug '05

26 Aug '05

1 0

[Dovecot] Dovecot.1.0.alpha1+mysql+mysql
by jigen 26 Aug '05

26 Aug '05

Hi, we are trying to track down the problem that prevents two mysql password databases from working. Instead of connecting to each database, it looks like dovecot tries to connect *twice* to the second specified. Do do this we just inserted some i_warning()s in the code. We noticed that passdb_sql_init (auth/passdb-sql.c) is called twice, once per configuration file, with the correct argument (path to config file). However, as you can see in the following maillog piece, this function calls sql_connect with the SAME parameters (the parameters of the second database). So the first call works and dovecot connects to the host correctly (lines 7-8), but in the second call dovecot finds the connection already up and obviously doesn't try again (last line). Could this be the origin of the problem? Now we are trying to understand why the argument to sql_connect isn't updated correctly. Maybe a bug in the linked list of sql_connection's? [...] dovecot: auth-worker(default): passdb_sql_init("/etc/dovecot/dovecot-mysql_django.conf") [...] dovecot: auth-worker(default): now calling sql_connect(passdb_sql_conn->db): [...] dovecot: auth-worker(default): passdb_sql_conn->config_path="/etc/dovecot/dovecot-mysql_debord.conf" [...] dovecot: auth-worker(default): passdb_sql_conn->set.connect="host=debord port=3306 dbname=posta_debord user=posta password=foobar" [...] dovecot: auth-worker(default): driver_mysql_connect: host=debord, user=posta, password=foobar. [...] dovecot: auth-worker(default): driver_mysql_connect: conn=0x3c00a6b0 [...] dovecot: auth-worker(default): actually connecting to debord [...] dovecot: auth-worker(default): mysql: Connected to debord (posta_debord) [...] dovecot: auth-worker(default): passdb_sql_init("/etc/dovecot/dovecot-mysql_debord.conf") [...] dovecot: auth-worker(default): now calling sql_connect(passdb_sql_conn->db): [...] dovecot: auth-worker(default): passdb_sql_conn->config_path="/etc/dovecot/dovecot-mysql_debord.conf" [...] dovecot: auth-worker(default): passdb_sql_conn->set.connect="host=debord port=3306 dbname=posta_debord user=posta password=foobar" [...] dovecot: auth-worker(default): driver_mysql_connect: host=debord, user=posta, password=foobar. [...] dovecot: auth-worker(default): driver_mysql_connect: conn=0x3c00a6b0 [...] dovecot: auth-worker(default): already connected to debord!!!! altivec & jigen

1 0