- dovecot - dovecot.org

[Dovecot] Dovecot rc9 error (More information)
by Daniel 15 Oct '06

15 Oct '06

Hi This happens when email is copied/moved from the inbox to another folder on the same imap account. The mail client goes into a loop with the below errors logged. This is on a 64bit Linux machine using the Maildir storage format. After doing a 'rm dovecot*' from the Maildir folder of the account having the problem the client can log in again but if the client tries to copy again it gets the same error. RC9 appears to be broken on this box. I have tested connecting form a windows machine and I get the same with thunderbird. I have tried with different accounts and they get the same problem. I have down graded to RC8 and all is working OK so seems to be a problem introduced with RC9. I have a 32bit Linux server with RC9 installed which has around 2000 accounts on it and this has no problems so maybe not affecting 32bit machines. If I can give any more information please let me know. Am getting this error with Dovecot rc9 on a imap account. Oct 15 10:55:28 bajor dovecot: imap-login: Login: user=<rachele>, method=plain, rip=192.168.1.1, lip=192.168.1.254 Oct 15 10:55:28 bajor dovecot: IMAP(rachele): file mail-cache-transaction.c: line 709 (mail_cache_add): assertion failed: (fixed_size == (unsigned int)-1 || fixed_size == data_size) Oct 15 10:55:28 bajor dovecot: child 27632 (imap) killed with signal 6 Oct 15 10:55:28 bajor dovecot: imap-login: Login: user=<rachele>, method=plain, rip=192.168.1.1, lip=192.168.1.254 Oct 15 10:55:29 bajor dovecot: IMAP(rachele): file mail-cache-transaction.c: line 709 (mail_cache_add): assertion failed: (fixed_size == (unsigned int)-1 || fixed_size == data_size) Oct 15 10:55:29 bajor dovecot: child 27636 (imap) killed with signal 6 Oct 15 10:55:29 bajor dovecot: imap-login: Login: user=<rachele>, method=plain, rip=192.168.1.1, lip=192.168.1.254 Oct 15 10:55:29 bajor dovecot: IMAP(rachele): file mail-cache-transaction.c: line 709 (mail_cache_add): assertion failed: (fixed_size == (unsigned int)-1 || fixed_size == data_size) Oct 15 10:55:29 bajor dovecot: child 27638 (imap) killed with signal 6 Oct 15 10:55:30 bajor dovecot: imap-login: Login: user=<rachele>, method=plain, rip=192.168.1.1, lip=192.168.1.254 Oct 15 10:55:30 bajor dovecot: IMAP(rachele): file mail-cache-transaction.c: line 709 (mail_cache_add): assertion failed: (fixed_size == (unsigned int)-1 || fixed_size == data_size) Oct 15 10:55:30 bajor dovecot: child 27641 (imap) killed with signal 6 Oct 15 10:55:30 bajor dovecot: imap-login: Login: user=<rachele>, method=plain, rip=192.168.1.1, lip=192.168.1.254 Oct 15 10:55:31 bajor dovecot: IMAP(rachele): file mail-cache-transaction.c: line 709 (mail_cache_add): assertion failed: (fixed_size == (unsigned int)-1 || fixed_size == data_size) Oct 15 10:55:31 bajor dovecot: child 27645 (imap) killed with signal 6 Oct 15 10:55:31 bajor dovecot: imap-login: Login: user=<rachele>, method=plain, rip=192.168.1.1, lip=192.168.1.254 Oct 15 10:55:31 bajor dovecot: IMAP(rachele): file mail-cache-transaction.c: line 709 (mail_cache_add): assertion failed: (fixed_size == (unsigned int)-1 || fixed_size == data_size) Oct 15 10:55:31 bajor dovecot: child 27649 (imap) killed with signal 6 Oct 15 10:55:31 bajor dovecot: imap-login: Login: user=<rachele>, method=plain, rip=192.168.1.1, lip=192.168.1.254 Oct 15 10:55:32 bajor dovecot: IMAP(rachele): file mail-cache-transaction.c: line 709 (mail_cache_add): assertion failed: (fixed_size == (unsigned int)-1 || fixed_size == data_size) Oct 15 10:55:32 bajor dovecot: child 27653 (imap) killed with signal 6 -- Regards Daniel ----------------------------- Registered Linux user #234279

1 0

[Dovecot] request to have dovecot authenticator driver 'officially' included/supported
by OpenMacNews 14 Oct '06

14 Oct '06

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 hi all, per the exim docs @: http://exim.org/exim-html-4.62/doc/html/spec_html/ch36.html a cyrus_sasl authenticator driveer is 'included' in exim core. given that Dovecot has become a very attractive alternative for an increasing number of folks, and there's a patch against exim 4.43 here: http://www.exim.org/eximwiki/AuthenticatedSmtpUsingDovecot that allows use of Dovecot's native sasl implementation as an authenticator, and that is _seems_ to apply against 4.63 ok, might it be possible to get this integrated into exim core, and have it become 'official'? thanks, richard - -- /"\ \ / ASCII Ribbon Campaign X against HTML email, vCards / \ & micro$oft attachments [GPG] OpenMacNews at gmail dot com fingerprint: 50C9 1C46 2F8F DE42 2EDB D460 95F7 DDBD 3671 08C6 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (Darwin) iEYEARECAAYFAkUC+eIACgkQlffdvTZxCMbG4wCgnczsi9zX6Xkg5MLi6JTez5d+ a+YAn0MIYI7gHW//8N5bxani1CoEAcJm =ZN2w -----END PGP SIGNATURE-----

5 16

[Dovecot] MySQL stored proc authorization
by Chaos Engine 14 Oct '06

14 Oct '06

On my Gentoo box until today I had dovecot-1.0_rc7 and used following entry in /etc/dovecot/dovecot-sql.conf password_query = call Authorize('%u', '%n', '%d') Simply put dovecot is calling my mysql stored routine which handles authorization. Until today, when I updated dovecot to dovecot-1.0_rc8 it worked flawlessly. With this version executing stored proc dies with: Password query failed: PROCEDURE mailsql.Authorize can't return a result set in the given context Replacing stored proc call with select .... statement does the thing, but it's stored procedures are ... generally better to do things on DB imvho :-) Downgrading to dovetot-1.0_rc7 fixes the problem immediately. Of course /etc/dovecot/dovecot.conf remains the same in either case. Is this a bug or change made on purpose? -- Chaos greets U

2 6

[Dovecot] MySQL "access denied" problems
by Timo Sirainen 14 Oct '06

14 Oct '06

Now that I was able to debug it myself, I found that it's caused by the same problem as before: Conflicting sha1_result symbol. This time only linking succeeded without errors, but at runtime it was still using the wrong one. So I updated the wiki page: http://wiki.dovecot.org/MysqlProblems

1 1

[Dovecot] child 29480 (auth) returned error 89, FC5, Postfix, MySql, mbox....arghhhh
by Kent Iverson 14 Oct '06

14 Oct '06

Hi all, I have been putting a small (simple?)dedicated email server together to (ultimately) host a couple of domains. I am currently getting the configuration to work with one domain w/local mbox users and then plan to extend it to virtual users and an additional domain. Dovecot has been a problem to integrate in the configuration. The basic pieces are FC5, Postfix, Dovecot, with Cyrus-sasl and MySql user/password databases. I have installed, configured, and verified Postfix, Cyrus-sasl, and MySql both separately and working together. All applications are standard Yum sourced FC5 binaries. Dovecot, however, stubbornly refuses to join the party. I have searched for clues on-line and have not found anything that has helped, thus this message. The problem seems to be tied tightly to using mySQL as an access mechanism for passdb/userdb information since if I remove that access mechanism Dovecot runs fine. The reason I am looking to use mySQL is that it seemed an easy way to have a common database for user name and domain identification with a single common FQDN login authentication format for current local users and future virtual users. As I understand it, the default PAM passwd doesn't support FQDN user names. The symptom: =========== Dovecot starts and immediately exits. Maillog shows the following immediately after executing /sbin/service dovecot start Oct 12 21:36:24 Playtime dovecot: Dovecot v1.0.beta8 starting up Oct 12 21:36:25 Playtime dovecot: child 29479 (auth) returned error 89 Oct 12 21:36:25 Playtime dovecot: child 29480 (auth) returned error 89 Oct 12 21:36:25 Playtime dovecot: Auth process died too early - shutting down Oct 12 21:36:25 Playtime dovecot: auth(default): net_connect_unix(/var/run/dovecot/auth-worker.29480) failed: Permission denied Oct 12 21:36:25 Playtime dovecot: auth(default): net_connect_unix(/var/run/dovecot/auth-worker.29479) failed: Permission denied It appears that the dovecot-auth process is immediately exiting with a non-specific error (89) and no collateral info. There are two sets of error 89's because the process count is set to 2 in dovecot.conf (see below). Looking at the messages log, you find a line reflecting the empty sockets as below: Oct 12 21:36:25 Playtime kernel: audit(1160714185.460:373): avc: denied { write } for pid=29479 comm="dovecot-auth" name="auth-worker.29479" dev=dm-0 ino=692358 scontext=user_u:system_r:dovecot_auth_t:s0 tcontext=user_u:object_r:dovecot_var_run_t:s0 tclass=sock_file There is nothing in the auth log other than happy noises from Postfix about its mySQL accesses. I am unaware of any other logs that might shed some light. Troubleshooting: ============= --- I have been using standard FC5 compiled binaries sourced through YUM for all applications. To the best of my knowledge, the package that Yum pulled for Dovecot is built --with-mysql and thus should support mysql access. I found this tidbit of info in the /usr/src/redhat/SPECS/dovecot.spec document. -- I have rolled back the dovecot.conf to remove the mysql passwd/userdb configuration leaving the default PAM configuration and found that Dovecot behaves correctly and joins the party. However, since Postfix is using mySQL data, the client FQDN login user names it uses don't match up with the simple UNIX user names that Dovecot's default PAM password mechanism is supporting (thus my attempt to get them both to use the mySql database.) So from this I know that the problem appears to be basic to startup of dovecot-auth and the mysql configuration. -- I have verified the location of the dovecot-sql.conf file as configured in dovecot.conf -- I have verified that the 'connect' parameters in the dovecot-sql.conf.work from a command line and the password_query syntax from inside mysql. Configuration details: dovecot.conf: ======================================================================= # things uncommented from defaults: base_dir = /var/run/dovecot protocols = imap imaps pop3 pop3s listen = * shutdown_clients = yes #for debug...seems to have made no difference. mail_debug = yes mbox_very_dirty_syncs = yes # authentication section # this next was left at default and I checked the ownership and it is correct. #auth_executable = /usr/libexec/dovecot/dovecot-auth #more debug auth_verbose = yes auth_debug = yes auth_debug_passwords = no # auth-worker process limit auth_worker_max_count = 30 #and into auth default: auth default { mechanisms = plain # default PAM passdb pam { } # SQL passdb sql { args = /etc/dovecot-sql.conf } # userdb userdb static { args = uid=690 gid=768 home=/var/mail/%n } #note there is no SQL userdb access defined. We will always use userdb static for now user = root count = 2 } ============================= dovecot-sql.conf ============================================================================== # Our mysql table actually is: (defined to support postfix password db) # CREATE TABLE users ( # id int(11) unsigned NOT NULL auto_increment, #table index # username varchar(255) NOT NULL default '0', #user part in user@userrealm # userrealm varchar(255) NOT NULL default 'firstdomain.com', #domain part in user@userrealm # userpassword varchar(255) NOT NULL default '94go283xc', #email password # auth tinyint(1) default '1', #Relay authority 1 = yes # active char(1) NOT NULL default 'y' #active Dovecot user? #}; driver = mysql connect = host=127.0.0.1 dbname=user_db user=dovecot password=xxxyy0x0 default_pass_scheme = PLAIN password_query = SELECT password FROM users WHERE username='%n' AND userrealm='%d' AND active='y' # there is no userdb sql access mechanism defined so this is left null user_query = ========================================================================================= Thats about it. I'm stumped....any thoughts or debug suggestions would be appreciated. Thanks -Kent I.

3 3

[Dovecot] fcntl Bad file descriptor
by Bill Boebel 13 Oct '06

13 Oct '06

I've seen a couple of these in the log while testing the proxy too. Do you know what would cause this? Aug 10 23:30:29 director5 dovecot: imap-login: fcntl(-1, F_GETFL) failed: Bad file descriptor Aug 10 23:30:29 director5 dovecot: imap-login: fd_set_nonblock(-1) failed: Bad file descriptor Aug 10 23:30:29 director5 dovecot: child 14016 (login) returned error 89

2 1

Re: [Dovecot] Dovecot LDA
by Steven F Siirila 13 Oct '06

13 Oct '06

On Sun, Oct 08, 2006 at 10:25:53PM +0300, Timo Sirainen wrote: > On Fri, 2006-10-06 at 21:00 -0500, Steven F Siirila wrote: > > I am running Dovecot 1.0-rc6 along with dovecot-sieve from 2006-10-05 CVS. > > I am calling dovecot deliver from Postfix (main.cf): > > > > mailbox_command = /opt/dovecot/libexec/dovecot/deliver > > > > Upon switching to dovecot deliver, I observed two problems: > > > > 1) An extraneous "From " header now appears at the top of each message > > delivered, e.g.: > > > > From dovecot.deliver Fri Oct 06 19:59:57 2006 > > From sfs(a)tc.umn.edu Fri Oct 6 19:59:57 2006 > > Return-Path: <sfs(a)tc.umn.edu> > > > > Using Postfix delivery the first of these lines does not appear. > > This, of course, confuses MUAs. > > Don't give F flag to Postfix's pipe command. In looking into this further, I see what you're getting at. There are commands in postfix/master.cf which specify different flags depending on what external delivery program is used. However, I haven't touched that and none of the entries that came with the standard master.cf file reference Dovecot, so I'm not sure if any of those entries even apply. What I changed to cause Dovecot delivery to be initiated was simply the mailbox_command in postfix/main.cf: mailbox_command = /opt/dovecot/libexec/dovecot/deliver I have been unable to determine what, if any, changes are necessary in the master.cf file to customize what parameters are sent to Dovecot deliver. Anyone? > Although this reminds me that the "dovecot.deliver" is wrong in there.. > Hmm. I think I'll add a maildrop-compatible -f <envelope> parameter > here. Great. Now if I could only figure out how to get Postfix to specify that. :) > There, done in CVS. I'll also make 1.0rc8 release today. > > > 2) The "Content-Length:" header appears after a blank line, essentially > > putting it into the RFC822 body, e.g.: > > > > User-Agent: Mutt/1.4.2.1i > > X-UID: 11510 > > Status: > > X-Keywords: > > > > Content-Length: 200 > > > > test > > Are you sure it's a blank line? Dovecot adds lots of spaces after > X-Keywords which could just make it look like that. > > If it really is a blank line, then it's most likely something else than > Dovecot that changes the spaces that way. -- Steven F. Siirila Office: Lind Hall, Room 130B Internet Services E-mail: sfs(a)umn.edu Office of Information Technology Voice: (612) 626-0244 University of Minnesota Fax: (612) 626-7593

4 12

[Dovecot] you got chocolate in my peanut butter?!
by Logan Shaw 13 Oct '06

13 Oct '06

Hey everyone, Ran into something positively perplexing today. A user came to me and said that this morning when they checked their mail, they got about 120 strange new messages. Upon further inspection, it seems the "new" messages are all addressed to a certain other different user and are all 3 or 4 months old. And looking in that other user's /var/mail/(username) mailbox, I see the same messages that arrived mistakenly. And they're not in the /var/mail mailbox of the user whose desktop computer they ended up on. So it would appear that, possibly, when this user connected to the server, they got someone else's messages! Messages that, in fact, came from an account they don't even have the password to! I'm really curious if anyone has seen something like this before. We're using dovecot-1.0.beta9, and have been since mid-June. I've never seen anything happen like this before. I'm perfectly willing to upgrade to the latest release candidate, but it's hard for me to "upgrade and see if that fixes it", because it happens so rarely and it won't be easy to know empirically. So what I'm really hoping for is confirmation that this is/was a known problem, if in fact it is. Of course, I don't know that this is a dovecot bug, but I could imagine that it might be (maybe a daemon forgets to switch users after one session is closed and another is opened?), so I thought I'd ask. I did see what looked like TLS fixes and login fixes in the changelogs, so it doesn't seem out of the question that such a bug could've existed. Some more information: I checked the user's settings on their desktop computer, where the unexpected messages appear, and sure enough, there is only one POP server account configured there, and it has the correct username. What's more, I asked them what time this happened, and they said probably at 7:00am or maybe a little earlier. Looking at my dovecot logs, I see this (where 'theuser' is the user who received the messages): Sep 28 06:59:49 myhostname dovecot: pop3-login: Disconnected: user=<theuser>, method=PLAIN, rip=192.168.1.245, lip=192.168.1.20, TLS Sep 28 06:59:55 myhostname dovecot: pop3-login: Login: user=<theuser>, method=PLAIN, rip=192.168.1.245, lip=192.168.1.20, TLS Sep 28 06:59:55 myhostname dovecot: POP3(theuser): Disconnected: Logged out top=0/0, retr=0/0, del=0/9, size=130585 So, it would seem that the user did login at the time they claimed and it was at that time (or close to it) that the weird messages appeared. Also, I checked the logs for logins from the person whose messages accidentally got downloaded, and it doesn't show them logging in until several hours later. Oh, and there are no log entries for either of the two users in question before that, at least not for over 12 hours before that. The user is running Outlook 2003, with POP3 + TLS access to the mailbox. My dovecot.conf has nothing fancy in it: base_dir = /var/run/dovecot/ ssl_cert_file = /etc/mail/certs/server.crt ssl_key_file = /etc/mail/certs/server.key protocols = imap imaps pop3 pop3s disable_plaintext_auth = no login_dir = /var/run/dovecot/login syslog_facility = local0 first_valid_uid = 100 protocol imap { } protocol pop3 { pop3_lock_session = yes pop3_uidl_format = %08Xv%08Xu } auth default { mechanisms = plain user = root passdb shadow { } userdb passwd { } } The accounts are all coming out of LDAP via nsswitch (and this is all happening on Slackware 10.2), but I'm fairly sure that's irrelevant since "getent passwd", etc. all show the right stuff. Thanks for any help anyone can give... - Logan

5 9

[Dovecot] Login process died before initialization - FIX
by Timo Sirainen 13 Oct '06

13 Oct '06

I think this should do it: http://dovecot.org/list/dovecot-cvs/2006-October/006504.html

1 0

[Dovecot] parser bug
by DINH Viêt Hoà 13 Oct '06

13 Oct '06

hello Timo (and maybe other Dovecot developers), It looks like the MIME parser won't parse this correctly : Content-type: text/html Note the lower-case '-type' in 'Content-type'. -- DINH V. Hoa

2 1