- dovecot - dovecot.org

[Dovecot] Verbose logging
by Daniel 16 Dec '04

16 Dec '04

Hi How can I make dovecot have very verbose logging? Regards Daniel

2 1

[Dovecot] Internal login failure
by Jaeson Schultz 16 Dec '04

16 Dec '04

Hello, I am fairly new to Dovecot, so please forgive me if I am missing something obvious here. I have checked the archived dovecot mailing list messages and have Googled for everything I can think of, and I still have not found anything to help me solve this problem. I am running Postfix+Postgresql+Dovecot on my Fedora FC2 box. I have compiled both Postfix and Dovecot from source. I believe I have postfix running properly. No error messages show up in my logs when starting Postfix or Dovecot. Messages are being delivered by Postfix just fine: Dec 12 11:45:42 co-nundrum postfix/virtual[15759]: 15E82F8EF0: to=<jaeson(a)domain.name>, relay=virtual, delay=1, status=sent (delivered to maildir) However, when I try to login to Dovecot over IMAP I get an "Internal login failure" error: [jaeson@localhost jaeson]$ telnet co-nundrum imap Trying 207.7.137.6... Connected to co-nundrum. Escape character is '^]'. * OK dovecot ready. 1 LOGIN jaeson secret 1 OK Logged in. * BYE Internal login failure. Error report written to server log. Connection closed by foreign host. When I check the dovecot log file I see the following entries: dovecot-auth: Dec 12 01:15:59 Info: PGSQL: Performing query: SELECT password FROM user_accounts WHERE username='jaeson' imap-login: Dec 12 01:15:59 Info: Internal login failure: jaeson [66.159.231.21] dovecot: Dec 12 01:15:59 Error: child 9845 (auth) killed with signal 11 Here are the entries from my dovecot.conf file. As you can see, I have set both auth_verbose and auth_debug = yes, but I don't seem to be getting any log messages with enough verbosity to indicate just what the problem is. base_dir = /var/run/dovecot/ protocols = imap imaps pop3 pop3s imap_listen = * pop3_listen = * ssl_parameters_regenerate = 24 disable_plaintext_auth = no log_path = /var/log/dovecot.log info_log_path = /var/log/dovecot.log login_dir = /var/run/dovecot-login login = imap login_executable = /usr/libexec/dovecot/imap-login login_user = dovecot login_process_size = 16 login_process_per_connection = yes login_processes_count = 3 login_max_processes_count = 128 login_max_logging_users = 256 max_mail_processes = 1024 verbose_proctitle = yes verbose_ssl = yes first_valid_uid = 5000 last_valid_uid = 65535 first_valid_gid = 5000 last_valid_gid = 65535 default_mail_env = maildir:/mail/%d/%u mail_save_crlf = yes maildir_copy_with_hardlinks = no maildir_check_content_changes = no mbox_locks = fcntl umask = 0077 imap_executable = /usr/libexec/dovecot/imap imap_process_size = 256 auth = default auth_mechanisms = plain auth_userdb = pgsql /etc/dovecot-pgsql.conf auth_passdb = pgsql /etc/dovecot-pgsql.conf auth_executable = /usr/libexec/dovecot/dovecot-auth auth_user = root auth_count = 1 auth_username_chars = abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@ auth_verbose = yes auth_debug = yes Additionally, here are the entries in my dovecot-pgsql.conf file: connect = host=localhost dbname=mail_DB user=mailreader password=secret default_pass_scheme = PLAIN password_query = SELECT password FROM user_accounts WHERE username='%u' user_query = SELECT '/mail/'||mailbox AS home, uid, gid FROM user_accounts WHERE username='%u' Finally, here is the configure command I used when building Dovecot from source: ./configure --prefix=/usr --enable-debug --with-pgsql --with-cyrus-sasl2 --with-ssl=openssl --sysconfdir=/etc At this point, I think that the connections to my postgresql tables are all working properly, and the initial authentication with Dovecot appears to be working. Dovecot *does* accept my password and gives me the "OK Logged in." response message, but somewhere before it kicks off the IMAP process it dies with a SIGSEGV. Perhaps I have some file permissions out of whack? Has anyone else encountered this problem, or perhaps has any insight into what might be going wrong or how to find out more information? Thanks, Jaeson Schultz jaeson at jaeson dot net

3 4

Re: Re: [Dovecot] login pam and mysql
by Marin Florian 15 Dec '04

15 Dec '04

I try 1.0 vresion, but seems to be a problem at mysql login. I'll look again at this version. Regards, > Hi Marin, > Try the 1.0 test versions, they allow as many login type as you want. > > Regards > Andrew > > > Marin Florian wrote: > > Hy, > > > > I use dovecot 0.99.12 on a FC2 and i try to obtain dual login pam and mysql, but > > seems that it's impossible. I must use or pam or mysql. Do you have any ideea > > how to obtain dual login. Thanks in advance. > > > > > > > > _________________________________ > > Noile abonamente Astral OnLine > > 256 kbps ; 12 USD/luna > > http://www.astral.ro > > > > -- > Andrew Hutchings > Systems Operator / Developer / Linux Guru > Netserve Consultants Ltd. > http://www.domaincity.co.uk/ > _________________________________ Noile abonamente Astral OnLine 256 kbps ; 12 USD/luna http://www.astral.ro

1 0

[Dovecot] login pam and mysql
by Marin Florian 15 Dec '04

15 Dec '04

Hy, I use dovecot 0.99.12 on a FC2 and i try to obtain dual login pam and mysql, but seems that it's impossible. I must use or pam or mysql. Do you have any ideea how to obtain dual login. Thanks in advance. _________________________________ Noile abonamente Astral OnLine 256 kbps ; 12 USD/luna http://www.astral.ro

2 1

[Dovecot] latest debs
by Paul 14 Dec '04

14 Dec '04

Just wondering: Has anyone, or is anyone planning to, build debs for 0.99.12? Jaldhar Vyas, are you still around and doing such things? Paul

2 1

[Dovecot] Re: Corrupted index files in 0.99.12.1
by Brady Wetherington 14 Dec '04

14 Dec '04

--- dovecot-request(a)dovecot.org Wrote: > From: Timo Sirainen <tss(a)iki.fi> > On 13.12.2004, at 21:26, Brady Wetherington wrote: > > > A solution I already tried was having Dovecot run by being invoked from > > a copy of tcpserver, which used a .cdb 'rules' database which set > > certain environment variables based upon the users IP address. I > > patched > > my copy of Dovecot to listen for those environment variables and pay > > attention/ignore NO_IMAP based upon those environment variables, but it > > looks like environment variables get clobbered when dovecot invokes the > > authenticator process from within imap-login (And the code seems to say > > that it blows out the environment, too). And I'm willing to bet that it > > would only work on first invoke of dovecot from imap-login, too, even > > if > > it didn't blow out the environment (because the authentication process > > stays running). > > You could do this by first getting the remote IP address transferred to > dovecot-auth (http://dovecot.org/patches/pam-rhost.patch) then checking > the IP in vpopmail code to see if you want to check NO_IMAP with the > IP. That sounds like that's the direction I want to go - I will definitely take a look into that, and possibly tweak it if I can. The way I was thinking about doing it was either respecting one or the other of NO_IMAP or NO_WEBMAIL depending on if you're coming from a local address or a remote one. I might stick with tcpserver using a tcprules.cdb to set environment variables and modify the patch to pass those environment variable(s) onward...we'll see. Or I might just suffer with my many dovecots. > > > I also _think_ I found out the problem, what was corrupting my indexes, > > though I'm not sure. I think one of the messages in my Maildir was > > 'unreadable' by Dovecot (well, that's what the logs say). Which seems > > to > > completely blow out the index. I got rid of the file, so lets keep > > fingers crossed that that solves it... > > If there's a repeateable way to break Dovecot with some specific > message even after indexes have been recreated, I'd like to see the > message. > > Unless, of course, you meant that 'unreadable' was because there was no > file system permissions to read it? Yes, unfortunately, the file was unreadable because there was no file system permissions to read it. That actually made dovecot make indices which imply there's nothing in the mailbox. How a file with no FS perms got into my maildir is rather embarassing and I'll skip unless it's important, but it was there and it did hose my indexes.

1 0

Re: [Dovecot] Ximian Evolution Issue
by Adam Todorski 14 Dec '04

14 Dec '04

Thanks for your swift replies, I really appreciate it. I looked at my mail logs and couldn't find anything awry. Also, if I use Mozilla Thuderbird from any remote platform or Squirrelmail hosted on the mail server itself I have no problems, regardless of the number of messages in a folder. I realize that I should probably ask on Evolution forums, but I think you guys may be better equiped to answer. Thanks again, Adam

2 1

[Dovecot] RE: Internal login failure
by Jaeson Schultz 14 Dec '04

14 Dec '04

Hello, I should have sent my first message in plain text instead of HTML so it would show up better in the list archives. Anyhow, I am using the latest release of Dovecot, v0.99.12.1. Seeing as how I don't need the cyrus-sasl2 to be compiled in, I have just rebuilt dovecot without it. Unfortunately I am still getting the same results... [jaeson@shell01 ~]$ telnet co-nundrum imap Trying 207.7.137.6... Connected to co-nundrum. Escape character is '^]'. * OK dovecot ready. 1 LOGIN jaeson secret 1 OK Logged in. * BYE Internal login failure. Error report written to server log. Connection closed by foreign host. The dovecot logs still indicate an "Internal login failure", but offers no extra explanation as to why. dovecot-auth: Dec 13 11:43:04 Info: PGSQL: Performing query: SELECT password FROM user_accounts WHERE username='jaeson' imap-login: Dec 13 11:43:04 Info: Internal login failure: jaeson [216.39.112.19] dovecot: Dec 13 11:43:04 Error: child 25784 (auth) killed with signal 11 I am wondering that since I see the auth_passdb query, shouldn't I also be seeing a log entry for the auth_userdb query as well, or does this happen once the imap process is started? Any advice for how to track down the source of the problem is appreciated. ~Jaeson [This E-mail scanned for viruses]

1 0

[Dovecot] Re: Corrupted index files in 0.99.12.1
by Brady Wetherington 14 Dec '04

14 Dec '04

--- dovecot-request(a)dovecot.org Wrote: > From: Matthias Andree <matthias.andree(a)gmx.de> > Brady Wetherington <brady(a)netservnyc.com> writes: > > > Would my old, corrupted index files be of any use to anyone? I still > > have that directory sitting somewhere. Is it perhaps 'bad' to run two > > copies of Dovecot? I don't know exactly what I was doing, but I can > > easily imagine accessing one of my Dovecots using my webmail setup, and > > one using straight IMAP - is that an unsupported setup? > > I'd think the way to go is to use one Dovecot installation for both IMAP > logins by remote clients as well as the webmail system. > > -- > Matthias Andree I would think the exact same thing, and I would _love_ to run only one copy of Dovecot. But I run vpopmail, and I need to make IMAP available only to users who have IMAP 'enabled' (the guys who pay more money). But I need webmail available for _all_ users (even the cheapskates), and my webmail of course uses IMAP behind the scenes. So my solution is one copy of regular Dovecot on port 143, which respects the NO_IMAP flag from vpopmail, and one copy of modified Dovecot, which I patched to ignore the NO_IMAP flag, on port 144 - and then I configured my webmail software to talk to port 144. That copy of Dovecot will eventually only listen to the local network for connections, though currently it listens for anyone. A solution I already tried was having Dovecot run by being invoked from a copy of tcpserver, which used a .cdb 'rules' database which set certain environment variables based upon the users IP address. I patched my copy of Dovecot to listen for those environment variables and pay attention/ignore NO_IMAP based upon those environment variables, but it looks like environment variables get clobbered when dovecot invokes the authenticator process from within imap-login (And the code seems to say that it blows out the environment, too). And I'm willing to bet that it would only work on first invoke of dovecot from imap-login, too, even if it didn't blow out the environment (because the authentication process stays running). All this stuff is, I'm sure, a thousand times easier in something like courier-imap, but I like Dovecot, so I'd rather run two copies of Dovecot than one of courier-imap. So if anyone has any possible direction to go on a solution that lets me run only one Dovecot, I'd love that. Until then, I'm stuck with my hack-ey two-Dovecot solution. I also _think_ I found out the problem, what was corrupting my indexes, though I'm not sure. I think one of the messages in my Maildir was 'unreadable' by Dovecot (well, that's what the logs say). Which seems to completely blow out the index. I got rid of the file, so lets keep fingers crossed that that solves it...

2 1

[Dovecot] 1.0-test57 LDAP dovecot-auth SIGABRT
by Thomas Hummel 14 Dec '04

14 Dec '04

Hi, I'm experiencing the following problem when runnig dovecot-1.0-test set up to authenticate users against openldap, while the corresponding setup with dovecot-0.99.11 works fine : . my platform : FreeBSD 5.3-RELEASE-p1 . dovecot version : dovecot-1.0-test57 . openldap version : openldap-2.1.27 - Description : When I talk IMAP to the dovecot server, I can connect on port 143 and receive the 'Dovecot ready' greeting message, but when I issue the command 'x LOGIN username userpass', the following message is written to the log file : ---------------------------------------------------------------------- 'dovecot: Dec 13 16:40:26 Error: auth(default): dovecot-auth in free(): error: chunk is already free dovecot: Dec 13 16:40:26 Error: child 17260 (auth) killed with signal 6' ---------------------------------------------------------------------- - here's a gdb backtrace of the dovecot-auth running process as it happens : (gdb) continue Continuing. Program received signal SIGABRT, Aborted. 0x1826e1d7 in kill () from /lib/libc.so.5 (gdb) bt full #0 0x1826e1d7 in kill () from /lib/libc.so.5 No symbol table info available. #1 0x1826327e in raise () from /lib/libc.so.5 No symbol table info available. #2 0x182d5627 in abort () from /lib/libc.so.5 No symbol table info available. #3 0x18279389 in ldexp () from /lib/libc.so.5 No symbol table info available. #4 0x182793cd in ldexp () from /lib/libc.so.5 No symbol table info available. #5 0x1827a2c1 in ldexp () from /lib/libc.so.5 No symbol table info available. #6 0x1827a513 in ldexp () from /lib/libc.so.5 No symbol table info available. #7 0x1827a644 in free () from /lib/libc.so.5 No symbol table info available. #8 0x080502c7 in ldap_input (context=0x2c) at db-ldap.c:172 request = (struct ldap_request *) 0x806a580 timeout = {tv_sec = 0, tv_usec = 0} res = (LDAPMessage *) 0x806a5a0 ret = 0 msgid = 405650150 #9 0x0805cea8 in io_loop_handler_run (ioloop=0x8075340) at ioloop-poll.c:184 data = (struct ioloop_handler_data *) 0x806a160 pollfd = (struct pollfd *) 0x2 tv = {tv_sec = 0, tv_usec = 268537} io = (struct io *) 0x806a300 t_id = 2 msecs = 0 ret = 0 call = 1 #10 0x0805c8e5 in io_loop_run (ioloop=0x8075340) at ioloop.c:218 No locals. #11 0x08051174 in main (argc=1, argv=0x0) at main.c:296 master = (struct auth_master_connection *) 0x8075500 i = 1 env = 0x4598 <Error reading address 0x4598: Bad address> pid = 0 master_p = (struct auth_master_connection **) 0x8075400 size = 1 (gdb) detach Detaching from program: /usr/local/dovecot-1.0-test57/libexec/dovecot/dovecot-auth, process 17804 (gdb) - here are the configure options I passed when compiling openldap and dovecot : - dovecot ./configure --prefix=/usr/local/dovecot-1.0-test57 --with-ldap --with-cyrus-sasl2 --with-rawlog --with-ssl=openssl --with-storages=mbox,maildir - openldap ./configure --prefix=/usr/local/openldap-2.1.27 --with-threads --with-tls=openssl --enable-dynamic --with-cyrus-sasl --enable-ldbm --enable-crypt --enable-lmpasswd --enable-ldap --enable-meta --enable-rewrite --enable-null --enable-monitor --enable-bdb --with-ldbm-api=berkeley --enable-spasswd --enable-wrappers -- Thomas Hummel <hummel(a)pasteur.fr>

1 0