- dovecot - dovecot.org

[Dovecot] [OTAnn] Feedback
by shenanigans 09 Nov '05

09 Nov '05

I was interested in getting feedback from current mail group users. We have mirrored your mail list in a new application that provides a more aggregated and safe environment which utilizes the power of broadband. Roomity.com v 1.5 is a web 2.01 community webapp. Our newest version adds broadcast video and social networking such as favorite authors and an html editor. It?s free to join and any feedback would be appreciated. S. ------------------------------------------------------------------------------------------------------------------------------------------ Broadband interface (RIA) + mail box saftey = <a href="http://Dovecot_Discussion_List.roomity.com">Dovecot_Discussion_List.roomity.com</a> *Your* clubs, no sign up to read, ad supported; try broadband internet. ~~1131474877246~~ ------------------------------------------------------------------------------------------------------------------------------------------

3 2

[Dovecot] dovecot and passwd-file migration
by Erick Perez 09 Nov '05

09 Nov '05

Hi, Im using dovecot with passwd-file authentication and would like to provide some kind of interface/script to let the users change their password. currently my passwd-file looks like: user@domain.com:{PLAIN}password I would also like to change the password to the same I use in my Linux user(a)domain.com: {MD5}password ??? What do I need to change in the .conf? Las thing, I just cant find a RPM or Source RPM for dovecot compiled with MySQL support. Our office uses MySQL and not Postgres. doing rpmbuild --rebuild --with mysql to the .src.rpm of dovecot does not work. dovecot fails telling he has no idea of what mysql is. If I get a dovecot with mysql rpm I will move from passwd-file to Mysql auth. Thanks, -- ------------------------------------------- Erick Perez Linux User 376588 http://counter.li.org/ (Get counted!!!) Panama, Republic of Panama

2 5

[Dovecot] dovecot crash after upgrade on FreeBSD
by Marko Lerota 08 Nov '05

08 Nov '05

Updated from ports collection from ver. dovecot-1.0.a3 to 1.0.a4_1. And it wan't work. Here's the log Nov 8 10:51:07 ot-group dovecot: Dovecot v1.0.alpha4 starting up Nov 8 10:51:08 ot-group dovecot: Auth process died too early - shutting down Nov 8 10:51:08 ot-group dovecot: auth(default): Unknown userdb driver 'passdb' Nov 8 10:51:08 ot-group dovecot: child 17872 (auth) returned error 89 -- One cannot sell the earth upon which the people walk Tacunka Witco

3 4

[Dovecot] error 89 Failed to create storage with data
by Nicolas 07 Nov '05

07 Nov '05

Hello, I have this error message in logs : dovecot: Nov 07 21:49:34 Error: POP3(manager(a)mydomain.com): Failed to create storage with data: manager(a)mydomain.com dovecot: Nov 07 21:49:34 Error: child 27834 (pop3) returned error 89 When I try to retrieve email of manager(a)mydomain.com kmail says there is no new message although this email box is not empty. I don't understand why. In my dovecot.conf I have default_mail_env = maildir:/home/Courrier/%d/%n with mutt on the server I can read all emails in /home/Courriel and for example : /home/Courrier/mydomain/manager/ Does anyone have an idea where I have to look for ? Thank you for your help and your response Nicolas

1 0

[Dovecot] 1.0alpha4 uploaded to Debian unstable
by Jaldhar H. Vyas 07 Nov '05

07 Nov '05

I finally got some free time and uploaded 1.0alpha4. It will arrive in the archive by tomorrow afternoon. Together with the most recent libssl0.9.8 upgrade I think this will fix the SSL problems users have been facing. -- Jaldhar H. Vyas <jaldhar(a)debian.org> La Salle Debain - http://www.braincells.com/debian/

4 7

[Dovecot] major pop3+ldap problem with alpha3 and alpha4
by Udo Rader 07 Nov '05

07 Nov '05

hi, For some of our customers we provide a pop3 access, and after an upgrade to alpha3, it is not working anymore. All of our data is ldap based and everything is working as before for our IMAP customers, but our POP3 users fail. Obviously the pop3 login process does not read the data correctly that comes from ldap. after enabling mail_debug, I saw the following error in our log: --------CUT-------- dovecot: Nov 02 18:01:32 Info: pop3(some.one.at.work): mbox: data=/virtual/at.work/home/some.one/mail/:INBOX=/var/mail/some.one.at.work --------CUT-------- The INBOX should be /virtual/at.work/var/mail/some.one.at.work, yet the POP3 process obviously uses the default_mail_env settings. the relevant line in our dovecot-ldap configuration looks like this: -------CUT-------- user_attrs = uid,homeDirectory,MailMessageStore,,uidNumber,gidNumber -------CUT-------- As I said, the IMAP process uses the ldap data correctly. any ideas? Udo -- bestsolution.at EDV Systemhaus GmbH http://www.bestsolution.at

1 2

[Dovecot] deleteing e-Mail, quota and dovecot
by Götz Reinicke 07 Nov '05

07 Nov '05

Hi, we run a RHEL4 E-Mail-Server with dovecot-0.99.11-2.EL4.1. we use mbox and most users use imap. So I have set quota for the devices where the user mailfiles are saved. No I'm getting the situation, that users exide there quota but yet not the grace limit and the user isn't able to delete messages. e.g. the the soft limit is 100 MB, the hard limit is 110 MB. So there should be some space to delete unneeded emails. Am i thinking the wrong way? Or how should the quota-system work in this situation? Thanks for any ideas! Regard Götz -- Götz Reinicke IT Koordinator - IT OfficeNet Tel. +49 (0) 7141 - 969 420 Fax +49 (0) 7141 - 969 55 420 goetz.reinicke(a)filmakademie.de Filmakademie Baden-Württemberg Mathildenstr. 20 71638 Ludwigsburg www.filmakademie.de

1 0

[Dovecot] Setup help
by Patrick Ernst 06 Nov '05

06 Nov '05

I'd previously had dovecot running on a Debian server but recently migrated to Suse. The nice, simple setup for dovecot on debian is not as easy using the dovecot sources. My lack of experience I'm afraid! I'd like to continue to use dovecot, especially as my current maildir directories are all set up ready to be use again. On suse (sles9) I have users authenticating by LDAP. In /var/log/dovecot I am getting errors like dovecot: Oct 27 22:17:41 Warning: Killed with signal 2 dovecot: Oct 27 22:28:03 Error: auth(default): LDAP: ldap_simple_bind_s() failed (dn uid=dovecot,ou=people,dc=aro,dc=home): Protocol error The errors also include the same LDAP error but with signal 11 or 15 I cannot get dovecot working. I've tried the 1.0 alpah and also found an earlier version on the suse 10 DVD. Basically I'm looking to use the IMAP server to centrally store emails on our home/business server. Previously we've been downloading mails (POP) from various mail accounts and moving them to dovecot (debian). In the future, I'd like to use fetchmail to do this part and locally deliver mail. My LDAP domain base is dc=aro,dc=home. I generally use this as the local mail/DNS domain as well. I have edited both /usr/local/etc/dovecot.conf and dovecot-ldap.conf. When I run dovecot it fails to start. I wonder if someone, in fairly broad ters could give me the steps for getting dovecot running with LDAP authenticated users? Regards Patrick

2 1

[Dovecot] cache
by Lucas 05 Nov '05

05 Nov '05

Hi, I just update from 0.99 to 1.alpha4. I combined with squirrel since several years ago and all was like a charm. Now dovecot is like catching mails. I explain: - I sent an email to my account. I login to webmail and I could see the mail. - Then, I check my mail with an email client through pop3 (vpopmail). - After that the mail isnŽt in the server, but in the webmail appears one msg in Inbox folder and the header. When click to see the msg an error ocurred: Query: FETCH 1 (FLAGS BODYSTRUCTURE) I try this in my config file: mail_never_cache_fields = flags date.sent date.received size.virtual size.physical mime.parts imap.body imap.bodystructure But no success :( Thank you in advance, Lucas

1 0

[Dovecot] forcing a default namespace
by Glenn Leavell 04 Nov '05

04 Nov '05

According to the Dovecot documentation, a "default namespace" is defined by simply configuring the namespace with an empty prefix, as in: namespace private { separator = / prefix = inbox = yes hidden = no } But my experience has been that this doesn't provide a true default, and that this namespace will only be selected when the client actually provides an empty ("") prefix. Is there a way to configure a default namespace that will always be chosen no matter what prefix the client provides, as long as there isn't an explicit match? I'd like to be able to have clients find mailboxes in a particular location no matter what they provide as their folder prefix. Thanks very much, -- Glenn Leavell <glenn(a)usg.edu> Office of Information and Instructional Technology Board of Regents of the University System of Georgia

1 0

[Dovecot] Dovecot 1.0a4 + pam + winbind ?
by Stephen Lee 04 Nov '05

04 Nov '05

Hi, I would like dovecot/pop3 to authenticate against a Windows ADS server. I've got authentication working for Samba and ssh using pam_winbind.so. Here's what my /etc/pam.d/dovecot file looks like: #%PAM-1.0 auth sufficient pam_winbind.so #auth required pam_nologin.so auth required pam_stack.so service=system-auth account required pam_stack.so service=system-auth account sufficient pam_winbind.so session required pam_stack.so service=system-auth session sufficient pam_winbind.so and this is what a portion of the dovecot.conf file looks like: auth default { # Space separated list of wanted authentication mechanisms: # plain digest-md5 cram-md5 apop anonymous mechanisms = plain passdb pam { args = dovecot } userdb passwd { } user = root } To get SSH to authenticate against ADS, the user name has to be prefaced with the domain name like "domain\user1". This is what I get when I attempt to login to Dovecot via Outlook/pop3 with the same naming scheme: Nov 3 20:09:45 server2 dovecot: auth(default): client in: AUTH 1 PLAIN service=POP3 lip=192.168.0.3 rip=192.168.0.227 resp=AHZjXGpvYW5uZQBqb2FubmU= Nov 3 20:09:45 server2 dovecot: auth(default): plain(domain\user1,192.168.0.227): Username contains disallowed characters Nov 3 20:09:46 server2 dovecot: auth(default): client out: FAIL 1 user=domain\user1 Nov 3 20:09:46 server2 dovecot: pop3-login: Disconnected: user=<domain\user1>, method=PLAIN, rip=192.168.0.227, lip=192.168.0.3 Dovecot does not like the "\" character and I'm note sure authentication gets past that step to get to the pam phase. Any experiences and suggestions with Dovecot authentication against Windows Active Directory? Thanks, Stephen

3 2

[Dovecot] courier2dovecot migration script
by Arto Bendiken 03 Nov '05

03 Nov '05

Howdy, I've just migrated a couple of servers to Dovecot, and am loving it so far. I thought I'd share the courier2dovecot shell script I whipped together (based on the instructions I found in the wiki.dovecot.org migration how-to), for converting Courier-IMAP maildirs to Dovecot format. It can be downloaded from my home page: http://bendiken.net/scripts/ While the script is rather simple, it can save a fair bit of typing when migrating some hundreds of mail accounts... especially since Courier stores some of its own state files recursively in each folder of the maildir hierarchy, making it a real pain to otherwise manually rename or remove all of them. Here's a plain-English summary of what the script currently does, when given a Courier maildir path as an argument: - check that the given path is indeed a valid Courier maildir, and exit if not - rename the file 'courierimapsubscribed' to 'subscriptions', and strip the 'INBOX.' prefix from its contents - recursively rename all of files of the name 'courierimapuiddb' to 'dovecot-uidlist' - recursively delete all of files of the name 'courierimaphieracl', 'courierimapacl' and 'courierimapkeywords' The script will also verbosely print out each action it does, handy for redirecting the output to a log file for a large migration. I hope people about to jump ship from Courier to Dovecot find this useful. If anyone comes up with improvements to the script, please send them my way :-) Arto

2 1

[Dovecot] Ambiguous ..... problem using Dovecot v1.0.alpha4 on OpenBSD 3.8
by snoop＠email.it 03 Nov '05

03 Nov '05

I verified that "default_mail_env" on my dovecot configuration file are "maildir:" correctly prefixed and ... permissions of /var/mail/mydomain and /var/mail/mydomain/myuser are 2755 and owner is root:mail. Dovecot user is member of mail group. I'm sure that isn't an authentication problem. I've tried some days to understand and to find over internet but I've not find a solution and now ... doesn't want to work. Someone can help me? _________________________________ Log output: dovecot: Nov 03 20:20:39 Error: imap(myuser(a)mydomain.com): Ambiguous mail location setting, don't know what to do with it: /var/mail/mydomain.com/myuser (try prefixing it with mbox: or maildir:) dovecot: Nov 03 20:20:39 Error: imap(myuser(a)mydomain.com): Failed to create storage with data: /var/mail/mydomain.com/myuser -- Email.it, the professional e-mail, gratis per te: http://www.email.it/f Sponsor: Registrazione dominio, 500 MB per la posta elettronica, spazio web a partire da 2,92 Euro al mese e in pi� assistenza gratis! clicca qui Clicca qui: http://adv.email.it/cgi-bin/foclick.cgi?mid=4079&d=3-11

1 0

[Dovecot] assertion problems w/ 1.0alpha4
by Jeremy Brown 03 Nov '05

03 Nov '05

Hey list, I have been using 0.99.14 for a while now but recently decided to try to upgrade to 1.0alpha4 to get the latest and greatest. I'm building from source myself on a Slackware 10.0 machine. Slackware ships with UW-IMAP configured to keep your inbox in /var/spool/mail and your other folders in ~/. I've been using the same setup for dovecot so that the migration is smooth...so my default_mail_env is set to: default_mail_env = mbox:~/:INBOX=/var/mail/%u I'm able to connect to both pop and imap servers and authenticate myself, but as soon as I attempt to get a listing of my emails my dovecot setting crashes with the following in the mail logs: Nov 3 10:52:40 shallowhal dovecot: imap(jeremy): file mail-index-sync-ext.c: line 155 (get_ext_header): assertion failed: (memcmp((char *)(ext_hdr + 1), ext->name, strlen(ext->name)) == 0) I can trigger this over POP3 just by logging in, then issuing "USER username", "PASS password", and then "LIST". Anyone experienced anything like this before? Any ideas on what might be going on? I can include more debug information (like my dovecot.conf file) if it would help. Jeremy

2 1

FW: [Dovecot] How to log POP3 events
by Cliff Hayes 03 Nov '05

03 Nov '05

Ok, I think I have that figured out. I made the following mods: disable_plaintext_auth = no pop3_uidl_format = %08Xu%08Xv and it seems to work. Now...about those enhanced logging capabilities. As promised, I see the enhanced logging. What does TOP and RETR mean? (I checked the manual first) Cliff -----Original Message----- From: Cliff Hayes [mailto:chayes@afo.net] Sent: Thursday, November 03, 2005 1:05 PM To: Chris Wakelin Subject: RE: [Dovecot] How to log POP3 events Logs say (with enhanced debugging turned on): Nov 3 12:58:38 sendmail dovecot: pop3-login: Login failed: Plaintext authentication disabled -----Original Message----- From: dovecot-bounces(a)dovecot.org [mailto:dovecot-bounces@dovecot.org]On Behalf Of Chris Wakelin Sent: Thursday, November 03, 2005 12:56 PM To: Cliff Hayes Cc: dovecot(a)dovecot.org Subject: Re: [Dovecot] How to log POP3 events Hmm, so what appears in the logs when you fail to authenticate? Have you tried the "debug" POP client :) ? telnet server 110 +OK University of Reading POP3 Server USER chris +OK PASS chrispassword +OK Logged in LIST 1 +OK 1 1234 QUIT +OK Logging out. Chris Cliff Hayes wrote: > Yes, that's what I have. I also found this: > > userdb prefetch { > } > > I must have missed that, so I commented that out and still had the same > problem. > > There is also this > > user = root > > in the auth default section. > > Cliff > > -----Original Message----- > From: dovecot-bounces(a)dovecot.org [mailto:dovecot-bounces@dovecot.org]On > Behalf Of Chris Wakelin > Sent: Thursday, November 03, 2005 11:27 AM > To: Cliff Hayes > Cc: dovecot(a)dovecot.org > Subject: Re: [Dovecot] How to log POP3 events > > > So what do you have for passdb and userdb? > > They should look something like > > auth default { > mechanisms = plain > > passdb shadow { > } > > userdb passwd { > } > > ... > > > (Earlier versions of 1.0, e.g. 1.0-stable, have just > > passdb shadow > userdb passwd > > ) > > 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] How to log POP3 events
by Cliff Hayes 03 Nov '05

03 Nov '05

Hello all, Thanks for your help getting me started. I have Dovecot running now. When I troubleshoot customer email problems, I need to be able to see the number of emails they popped. In /var/log/maillog, Dovecot just tells me that they authenticated, but not what happened after they authenticated. With pop3d, I saw how many emails they popped. Can I set that in Dovecot? I checked the documentation and couldn't find anything. I also turned on the "auth_verbose = yes" and "auth_debug = yes" -- but as the name implies, I only got more authentication info. Nothing about files tranferred. Thanks, Cliff

3 10

[Dovecot] Vpopmail authentication problem
by [Mailclub] Laurent Bauer 03 Nov '05

03 Nov '05

Hello, I have a problem setting dovecot-1.0 / vpopmail authentication with virtual users. Here is my dovecot.conf (the part related to vpopmail) : passdb = vpopmail userdb = vpopmail default_mail_env = maildir:/home/domains/%d/users/%n I recompiled dovecot with "verbose" option and keep getting this error : Nov 3 11:10:58 ***** dovecot: auth(default): vpopmail(lb(a)mm.fr): unknown user (lb(a)mm.fr) whatever user/domain/password I am testing (including the correct one, of course) This is in src/auth/userdb-vpopmail.c line 35 : vpw = vauth_getpw(vpop_user, vpop_domain); According to the makefile, the binary was built with -L/home/vpopmail/lib and -I/home/vpopmail/include options ("standard" qmail/vmailmgr/vpopmail installation) so it should be ok ? I checked the permissions by setting a shell for vpopmail user, then 'su vpopmail' and read/write the password.cdb file. What could be wrong ? Has anybody got a sample config file / dovecot version working with vpopmail and virtual users, or an idea of what could be wrong in my config ? Thanks a lot. Laurent

1 0

[Dovecot] double posts
by Chris L. Franklin 02 Nov '05

02 Nov '05

Is any one else getting double posts from this list ? -- -- Chris L. Franklin -- ________________________________________________________________________ This email was scanned by the server at NomadCF.com, And has been deemed clean of invaild and or dangerous email attachment type and virus'. Although this is by no means a guarantee. ________________________________________________________________________

2 2

RE: [Dovecot] New Fedora/Sendmail Install Assistance
by Jakob Hirsch 02 Nov '05

02 Nov '05

Please keep list traffic on the list! Cliff Hayes wrote: > We are using Dovecot 0.99.14 Ok. Haven't used this for quite a while, so I don't know if I can really help you. > auth_userdb = passwd > auth_passdb = shadow Dovecot uses the homedir that's in your passwd then. But I wonder how you want to use IMAP. AFAIK, it needs a separate directory for every user anyway. At least the indexes etc. have to be stored somewhere. You should really read doc/mail-storages.txt: "mbox storage requires an IMAP root directory where to store IMAP folders and some other information..." I you can't provide a directory for every user, dovecot is probably not the software for you.

3 3

[Dovecot] Still corrupt indexes in 1A4
by Alen Salamun 02 Nov '05

02 Nov '05

Hello All! Well I still have users which almost daily get corrupt dovecot files in their IMAP folders (Maildir style) and are unable to read their mail in this particular folders. When I delete dovecot files in this folder (rm -rf dove*) user can again read all messages. This is regular Linux CentOS 4.2 with SAN storage (boot from SAN) as disks. So this is EXT3 on LVM. BUT it is VERY interesting that than happens only to two users which are connected to the server via slow links (reading via Thunderbird or Squirrelmail). It never happened (now for weeks) to other 10 users which use it localy or at home (on speedy links). It's very hard for me to exactly pinpoint the problem, since it never happens to me. But when it happened to one user again I asked him to send me screenshoot of it. I could see there that SquirrelMail said: "Warning: fgets() [function fgets]: SSL: fatal protocol error in /usr/share/squirrelmail/functions/imap_general.php on line 93." Examining this file this line is in function: --------SQUIRRELMAIL PHP SOURCE------------ /** * Custom fgets function: gets a line from the IMAP server, * no matter how big it may be. * @param stream imap_stream the stream to read from * @return string a line */ function sqimap_fgets($imap_stream) { $read = ''; $buffer = 4096; $results = ''; $offset = 0; while (strpos($results, "\r\n", $offset) === false) { if (!($read = fgets($imap_stream, $buffer))) {<- THIS IS LINE 93 /* this happens in case of an error */ /* reset $results because it's useless */ $results = false; break; } if ( $results != '' ) { $offset = strlen($results) - 1; } $results .= $read; } return $results; } } ------------------------------------------- Looks like dovecot drops connection or something. Well must be related to corrupt dovecot files in particular folder, since deleting them solves the problem. BR, Alen Salamun

2 3

[Dovecot] New Fedora/Sendmail Install Assistance
by Cliff Hayes 02 Nov '05

02 Nov '05

Hello everyone, I've narrowed down my problem, so this should be an easy one for some smart person out there. I am moving from an old sendmail/Fedora 2 box to a new sendmail/Fedora 4 box and want to try Dovecot for pop3. The problem is, I can't get it to work. I have 9000 email accounts I will be moving to the new box. I've already tried and failed once. The problem is, Dovecot wants a home directory for each one. We don't use home directories. So, when I try to pop one of the accounts that was moved over, /var/log/maillog shows: Nov 1 14:33:47 sendmail pop3(chayes): mkdir_parents(/home/chayes/mail/.imap/INBOX) failed: Permission denied Nov 1 14:33:47 sendmail pop3(chayes): Couldn't open INBOX: Internal error occured. Refer to server log for more information. [2005-11-01 14:33:47] -or- Nov 1 14:29:18 sendmail pop3(chayes): mbox: Can't create root IMAP folder /home/chayes/mail: Permission denied Nov 1 14:29:18 sendmail pop3(chayes): Failed to create storage with data: mbox:/var/spool/mail/chayes ******** But if I create folders /home/chayes/ and /home/chayes/mail with user and group set to chayes, then it works. By the way, I've tried about 20 different iterations of the default_mail_env parameter. This is the one I'm using at the moment: default_mail_env = mbox:/var/spool/mail/%u Bottom line is, if Dovecot has to have a home directory, then I guess I'll have to go back to pop3d, which doesn't. Thanks, Cliff

2 1

[Dovecot] 1.0.alpha4 released
by Timo Sirainen 02 Nov '05

02 Nov '05

The actual alpha4 release this time. With a few changes since the pre-release. The important changes again: - Default lock_method changed to flock instead of the old fcntl. Solaris users will need to set it back to fcntl. This makes sure that Dovecot's indexes aren't accidentally used with NFS. - IMAP: We might have sent extra EXPUNGE messages when output buffer got full. This could have caused various sorts of very bad behavior. This is the main reason why everyone should upgrade as soon as possible. - POP3: We sent duplicate replies for LIST command when output buffer got full. Probably caused Thunderbird's duplicate deletion bugs? (Although I thought someone checked that Dovecot's reply was correct when the bug occurred?) - pop3_uidl_format setting is now required to be explicitly set in configuration file for pop3 to work at all. I want to get rid of the old default setting which breaks Outlooks, and simply changing the default would break existing setups. - Multiple passdbs and userdbs of same type can now be added with different parameters. Some people asked about this earlier. - Authentication cache works now with other than SQL and LDAP passdbs. Some passdbs such as PAM require some additional settings to work. See example config file. - Some other fixes to authentication cache related to failure handling and non-plaintext authentication. - deny passdb wasn't working for non-plaintext authentication. New changes since alpha4 pre-release: - imap/pop3 proxy feature was broken - fixed an assert-crash in ostream-file.c that was only in the pre-release And some more changes since alpha3 that I didn't mention before: - zlib plugin updated in http://dovecot.org/patches/1.0/zlib-plugin.tar.gz to be much faster than before - Added ssl_username_from_cert setting. Not actually tested yet, does it work? - epoll was broken with 64bit systems - Added deny password databases. - Dovecot can be run from inetd again - Index breakage/crashfix related to adding new keywords

9 29

[Dovecot] Cannot build rpm with mysql support from dovecot.spec
by Erick Perez 02 Nov '05

02 Nov '05

I've been playing for hours with the dovecot.spec file to build --with-mysql. The resulting RPM builds fine but when dovecot runs it does not recognize the passdb mysql statement. I also noted that the spec file has a version of 1.0-stable and rpmbuild complains about an invalid '-' in the version. Being a newbie in rpmbuild, can someone assist me in building for CentOS 4 on i386? standard build options but --with-mysql added. I also tried to install it from sources and it does not work (at least for me). Being a RPM user now I have to clean what the source installation did and i have no clue where the 'make install' placed files. BTW I am trying to build a manual (pdf, html) with the following config and im only stuck with dovecot, the other daemons are ready. Target Server: CentOS 4 with apache, postfix, mysql, dovecot, openwebmail,clamav, clamd, php,zlib,openssh, webmin and samba. All virtual running from mysql where possible, no local users no local storage (all to the mysql db/tables). Not wanted: postgresql, courier,vpopmail,kerberos,sasl,ssl (that might be in manual v2.0 if 1.0 ever sees the light) The system does not have X (no need for fancy graphs) file used: http://www.dovecot.org/nightly/stable/dovecot-stable-20051102.tar.gz RPMs Used: All RPMs that can be located in the CentOS 4 CDs so new users (like me) can do as much as needed without downloading. Devel RPMs: All devel (mysql, pam, openssl) are installed and they are recognized at building time. Your help will be appreciated in this task. Thanks, -- ------------------------------------------- Erick Perez Linux User 376588 http://counter.li.org/ (Get counted!!!) Panama, Republic of Panama

2 3

[Dovecot] failed to start
by Export TheGeek 02 Nov '05

02 Nov '05

greetings, I'm having a bit of trouble running dovecot, I receive the error; "Fatal: Can't create directory /usr/local/var/run/dovecot: No such file or directory" with an unmodified install save for disabling imap and allowing secure imap and pop3, I uncommented the base_dir in the .conf, although that did nothing. Does anybody have any suggestions? Many thanks, -Ex

2 1

[Dovecot] Error: auth(default): Unknown userdb type 'mysql'
by Erick Perez 02 Nov '05

02 Nov '05

Hi there, I have configured dovecot with mysql but when I restart (Redhat enterprise 4) the following error appears: dovecot: Nov 01 18:47:08 Info: Dovecot v1.0-stable starting up dovecot: Nov 01 18:47:09 Error: Auth process died too early - shutting down dovecot: Nov 01 18:47:09 Error: auth(default): Unknown userdb type 'mysql' dovecot: Nov 01 18:47:09 Error: child 30738 (auth) returned error 89 I have all RPMs for mysql installed, as well as mysql-devel. how can I verify that mysql support was correctly compiled in? sugestions? Thanks in advance.

1 0

[Dovecot] Problems with dual ldap auth
by Stian Jordet 01 Nov '05

01 Nov '05

Hi, I can't seem to figure this out. Is it impossible to use two different ldap auth? It works if I use one ldap and one pam, but I do need to use ldap for both. This is from my config: auth default { mechanisms = plain passdb ldap { args = /etc/dovecot/ldap-virtual.conf } passdb ldap { args = /etc/dovecot/dovecot-ldap.conf } userdb ldap { args = /etc/dovecot/ldap-virtual.conf } userdb ldap { args = /etc/dovecot/dovecot-ldap.conf } user = root #chroot = #count = 1 #ssl_require_client_cert = no } It works well if I only use one of them (so they seem to be correct), but together, only the last (dovecot-ldap) is used. Anyone see a reason for that? Best regards, Stian

2 3

[Dovecot] dovecot-lda - sieve notify support
by Sebastjan Trepca 01 Nov '05

01 Nov '05

Hi, does current implementation of dovecot-lda supports sieve script like this: require ["notify"]; if header :contains "from" "boss(a)example.org" { notify :high "This is probably very important"; } And if it does, what happens in this case ? Is there any configuration for other notification methods? I didn't notice anything in configuration file. Thanks, Sebastjan

1 0

[Dovecot] Usernames and Passwords for Virtual Users Request
by Matt 01 Nov '05

01 Nov '05

A feature I think would be nice. When a single IP hosts email for multiple domains the solution is usually to use the complete email address as the username. I have users that have migrated from Cobalt RAQ's which do not work like that. If a user trys to authenticate with just there username such as "joeb" instead of joeb(a)dirt.com I would like Dovecot to check all the domains it hosts and if it only finds one with the username "joeb" assume thats the one. If multiple domains have the username "joeb" refuse to authenticate without the "@domain" part. Perhaps this is not possible. Sure would be handy though. Oh, it would also be nice to automatically lowercase all usernames before authentication. Matt

4 4

[Dovecot] popa3d migration problem
by Janusz Batko 01 Nov '05

01 Nov '05

Hello, I tried to migrate from popa3d to dovecot but I couldn't manage with 'pop3_reuse_xuidl = yes' option. First of all it turned out that the feature is not supported in dovecot for Fedora Core 4 (dovecot-0.99.14-4.fc4). So I downloaded latest stable release of Dovecot but it didn't have this option included too. Then I compiled the newest alpha version (dovecot 1.0.alpha4) and I tried to login with 'pop3_reuse_xuidl = yes' option enabled and I've got in my logfile the following output: Nov 1 00:58:33 sneogg dovecot: pop3-login: Login: user=<test2>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured Nov 1 00:58:33 sneogg dovecot: pop3(test2): Set pop3_uidl_format setting in config file Nov 1 00:58:33 sneogg dovecot: child 32067 (pop3) returned error 89 And my session was disconnected immediately each time after sucessful authentication.. I tried to set up pop3_uidl_format to MD5 (%m) but it didn't work... Let me ask if there is a possibility to migrate from popa3d to dovecot (by using a proper patch maybe?)? I'd thankful for any response... Janusz

3 3

[Dovecot] errors after 1.0a3 -> 1.0a4
by Jakob Hirsch 31 Oct '05

31 Oct '05

Hi, somebody else seeing these? Oct 21 09:14:06 ymmv dovecot: imap-login: Login: user=<xxxx>, method=CRAM-MD5, rip=84.162.151.124, lip=85.214.25.134, TLS Oct 21 09:14:07 ymmv dovecot: imap-login: epoll_ctl(): No such file or directory Oct 21 09:14:07 ymmv dovecot: child 11419 (login) returned error 89 mailbox access fails after that. Had this already yesterday, then downgraded to alpha3 and it worked again, upgraded again and it kept working. Strange thing is, access through squirrelmail works perfect, but using Thunderbird gives these errors. I'm using maildir with epoll and inotify, if that matters.

3 7

[Dovecot] login_user & first_valid_uid
by Alexander Shikoff 30 Oct '05

30 Oct '05

Hi all, I have next settings in .conf file ... # # Login user for SQL-based virtual users # login_user = dovecot first_valid_uid = 100 first_valid_gid = 100 ... System user dovecot has UID/GID = 101/101. But every time when user logins I see in log file Oct 29 15:51:25 orion dovecot: Logins with login process UID 101 (user elnino) not permitted (see login_user in config file). Oct 29 15:51:25 orion dovecot: auth(default): Growing pool 'plain_auth_request' with: 1024 Why dovecot generate these warnings and how I can get rid of them? Thanks in advance, Alexander -- Kind Regards, Alexander Shikoff minotaur(a)crete.org.ua

4 8

[Dovecot] [info] Spamcop listing
by /dev/rob0 30 Oct '05

30 Oct '05

Smtp1.song.fi and smtp2.song.fi, our list servers, seem to have gotten listed in the bl.spamcop.net RBL. Spamcop listings are temporary and will time out, and because of occasional major false positives (or perhaps collateral damage?) like this I don't use it to reject mail. Anyone who IS using Spamcop to reject mail has missed much of today's list traffic. -- mail to this address is discarded unless "/dev/rob0" or "not-spam" is in Subject: header

8 13

[Dovecot] Dovecot Alpha 4
by Marcus Don 30 Oct '05

30 Oct '05

Hi We've been using Dovecot as our primary IMAP and POP3 server for around 70,000 users for a couple of months now. On the whole, we've been very pleased with the performance of Dovecot - and are extremely grateful to the developers! However, we have had a few issues, some of which we have yet to resolve. We chose Dovecot because it was the only IMAP/POP3 server we could find that supported direct mysql authentication and both mboxes and maildirs. With exim as our main SMTP server, we were able to convert the inboxes and imap folders for all 70,000 users from mboxes to maildirs without any downtime whatsoever! For those who are interested, we have a cluster of 5 web/imap servers (running our own webmail software) and a further 5 pop servers all placed behind 2 Zeus load balancers and running RHEL 4 (actually CentOS 4.1). Storage is provided by an EMC Clariion device, which is mounted via NFS onto all servers in the cluster over gigabit ethernet. 1. index files The main problem has always been the index files becoming corrupted. This seems to have improved with the Alpha 4 release, but still happens for several users each day. Perhaps it would be possible for Dovecot to just delete index files and re-create them when they are corrupted, rather than just erroring? Also, how do you turn off index files altogether? Even when mail_never_cache_fields is set for all available fields, they still get created. Another issue relating to the index files is that, if a user is deleted and then another user created with the same name, dovecot doesn't have permissions to re-write the index files, because it has a different uid. So, whenever a user is deleted, we have to delete the index files from every machine in the cluster. We could store index files on the NFS device, but this would affect performance (and might cause locking problems). A better solution would be to make the uid one of the variables available in default_mail_env. By naming index files by uid rather than username, this wouldn't be an issue. 2. initgroups() We use an nss-mysql to store all non-administrative system users in a mysql database. We often encounter problems with applications that use the initgroups() function, since this returns all users and groups - which in our case returns masses of data from mysql. When using mysql (or ldap etc) for authentication, it would be useful if there were an option to prevent additional system lookups. At present, we have to comment out the following in /src/lib/restrict-access.c, or the server load goes through the roof: if (initgroups(env, gid) != 0) { i_fatal("initgroups(%s, %s) failed: %m", env, dec2str(gid)); } 3. base_dir permissions bug Since the alpha 4 release, it seems that the permissions dovecot automatically sets for the base_dir are not sufficient to allow the authentication user to access sockets, unless this user belongs to the same group as the login user - which is contrary to the instructions in the documentation. I'm pretty sure this is a bug, but perhaps someone could confirm. 4. authentication caching Also since the alpha 4 release, we have found that, once the authentication cache is full, all subsequent login attempts for users that haven't been cached return "password mismatch". I though this might be a conflict with nscd, but it happens whether nscd is running or not. So, for the time being, we have had to disable the authentication cache. I'd be very keen to hear from anyone who has any feedback on any of the points above. Thanks Marcus -- Marcus Don Applications Development Manager Namesco Limited Main Line: +44 (0)870 120 8888 Main Fax: +44 (0)870 120 8008 Tech Support: +44 (0)870 162 4950 Email: mdon(a)names.co.uk Website: http://www.names.co.uk Address: Acton House, Perdiswell Park, Worcester, WR3 7GD This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender immediately. If you are not the intended recipient you are notified that disclosing, copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. Please note that any views or opinions presented in this email are solely those of the author and do not necessarily represent those of the company. Finally, the recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. ------------------------------------------------------------------------ --------------------------------------- | Free Dial-up - no need to register! | --------------------------------------- Namesco Limited provides Free dialup access to anyone that wishes to use it. You do not even have to be a customer, there is no need to register and is especially handy if you are unable to connect with your current provider. Simply use the following details: Dialup Number: 0844 535 2100* Username: namesco Password: easydialup * Local call rate charges apply, 33% Cheaper than BT's 0845 local call rate. If you need any help in configuring the Free Dial-up service on your computer, please do not hesitate to call us on 0870 162 4950.

4 4

[Dovecot] Dovecot RPMs for Redhat Enterprise 3 repository?
by Erick Perez 30 Oct '05

30 Oct '05

Where can I find RPMs for RHEL 3? -- ------------------------------------------- Erick Perez Linux User 376588 http://counter.li.org/ (Get counted!!!) Panama, Republic of Panama

3 3

[Dovecot] Dovecot reports zero messages erroneously
by Chris Spiegel 29 Oct '05

29 Oct '05

On October 11, Mark Farmer reported a problem about not being able to see new mails. I'm running into the same issue. Even though cur/ and new/ contain messages, Dovecot reports that there aren't any. This problem seemed to start happening in alpha3 (and persists in alpha4). When I revert back to alpha2, the messages show up again. It looks like a problem with the dovecot.index* files. When I delete them, alpha4 can serve up the mails just fine, and will in fact keep working for a little while. Eventually (within a few hours, although I'm not sure what causes it), dovecot thinks things are empty again. Like Mark, I'm using Postfix.. I'm not sure if that has anything to do with the problem but I thought it'd be worth pointing out. If there are any specific things you'd like me to do to try to pin down this problem, let me know. Chris

2 4

[Dovecot] Some errors with 1.0.alpha4
by Nicolas STRANSKY 29 Oct '05

29 Oct '05

Hi, I'm getting three types of errors with latest Dovecot compiled for x86_64 GNU/Linux Debian. Oct 29 12:47:57 rouge imap-login: unable to dlopen /usr/lib/sasl2/libntlm.so.2: /usr/lib/sasl2/libntlm.so.2: failed to map segment from shared object: Cannot allocate memory Oct 29 12:47:57 rouge pop3-login: unable to dlopen /usr/lib/sasl2/libntlm.so.2: /usr/lib/sasl2/libntlm.so.2: failed to map segment from shared object: Cannot allocate memory I have no idea why there is this error, but it comes each time a user logs in, with no other severe effect. Oct 29 01:28:54 rouge dovecot: imap(glondu): pool_system_malloc(): Out of memory Oct 29 01:28:54 rouge dovecot: child 5642 (imap) returned error 83 (Out of memory) Oct 29 01:38:10 rouge dovecot: imap(glondu): pool_system_malloc(): Out of memory Oct 29 01:38:10 rouge dovecot: child 5639 (imap) returned error 83 (Out of memory) Oct 29 01:49:22 rouge dovecot: imap(glondu): pool_system_malloc(): Out of memory Oct 29 01:49:22 rouge dovecot: child 8839 (imap) returned error 83 (Out of memory) The mailbox for this user is not bigger that 10MB and dovecot mail_process_size is set to default setting so I don't see why there could be a "Out of memory" error. Oct 28 18:00:45 rouge dovecot: imap(vidal): Lost transaction log file /var/dovecot-indexes/vidal/.INBOX/dovecot.index.log seq 1 Oct 28 18:00:45 rouge dovecot: imap(vidal): Lost transaction log file /var/dovecot-indexes/vidal/.INBOX/dovecot.index.log seq 1 Oct 28 18:00:56 rouge dovecot: imap(vidal): Lost transaction log file /var/dovecot-indexes/vidal/.INBOX/dovecot.index.log seq 1 Oct 28 18:00:56 rouge dovecot: imap(vidal): Lost transaction log file /var/dovecot-indexes/vidal/.INBOX/dovecot.index.log seq 1 This error caused the user's mailbox to be unreadable, and erasing the indexes resolved the problem, but I would have expected Dovecot to have done it itself if the indexes were corrupted ? Hope this feedback helps, -- Nico

1 0

[Dovecot] Basic Configuration
by Ashvin Meetoo 29 Oct '05

29 Oct '05

Hi, Been setting up a backup mail server just in case... using FC4... basic configuration... postfix/dovecot... imap pop3... When I send an external email, example(a)gmail.com, everything works well. When I send an internal email, i.e. to another user, user receives a blank email? Everytime he clicks on get mail a new empty email is added... checked /<user>/Mailbox/new folder email is there and header is ok. What can be the matter? Did this thousand times before and even reinstalled FC4... same problem. Also, I have tried: echo test | mail root but mail gives me : No mail for root Help please. __________________________________ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com

1 0

[Dovecot] dovecot-lda cvs
by Rene Luria 28 Oct '05

28 Oct '05

I am using dovecot-lda from cvs (checked out on september the 21st) and dovecot 1.0alpha2 (not yet upgraded ok). I have a strange feeling about "redirect" feature. Let's see two sieve scripts examples: # ex1 require ["fileinto", "vacation"]; if header :is ["blabla"] "blabla" { fileinto "blabla"; } redirect "user(a)domain.com"; keep; # ex2 require ["fileinto", "vacation"]; redirect "user(a)domain.com"; keep; In both cases, I redirect mail to an external address, keeping a copy. (this would emulate redirect :copy "user(a)domain.com"; which is still not implemented). In first example I run a test on headers, but not on the second. The effect is that in the second example, the forwarded mail is "complete" (exactly the original one with routing header modified), but in the first one, the forwared mail is completely messed up: no Subject header, and so on. This could be because as tests are run on the incoming mail, the working in memory of the mail is changed, and then, forwarded. So when no tests are run, the mail remains intact. How can I deal with this ? Is there some nice hotfix that would prevent a few (like 100'000) users to kill me ? Best regards. -- Rene Luria

3 5

[Dovecot] 1.0alpha3: fcntl() complaints?
by Jeff A. Earickson 28 Oct '05

28 Oct '05

Hi, Since installing 1.0alpha3 this morning, I've seen this syslog complaint a few times. Anything to worry about? A "server too busy" issue? imap(user): fcntl() failed with mbox file /var/mail/user: Resource temporarily unavailable Jeff Earickson Colby College

2 4

[Dovecot] DoveCot 1.0a3 hangs at login
by Justin Finkelstein 28 Oct '05

28 Oct '05

I've just upgraded to 1.0a3 via a freebsd port, and I've begun to notice odd behaviour from Dovecot. After converting my config file settings over to the new format, everything runs fine for an hour or so, then dovecot stops responding: oot@toejamfootball# telnet localhost 143 Trying ::1... telnet: connect to address ::1: Connection refused Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. * OK Dovecot ready. 1 login justin(a)redwiredesign.com password [dovecot then just stops doing anything] * BYE Disconnected for inactivity. Connection closed by foreign host. in the logs, it says: Oct 13 09:43:22 toejamfootball dovecot: imap-login: Disconnected: Inactivity: method=PLAIN, rip=192.168.2.11, lip=192.168.2.43 Oct 13 09:43:22 toejamfootball dovecot: auth(default): client in: AUTH 1 PLAIN service=IMAP lip=192.168.2.43 rip=192.168.2.11 resp=AGp1c3RpbkByZWR3aXJlZGVzaWduLmNvLnVrAHBhc3N3b3Jk Oct 13 09:43:22 toejamfootball dovecot: auth-worker(default): sql(x,192.168.2.11): query: SELECT username AS user, MD5(clear) AS password FROM users LEFT JOIN domains ON domains.domain_id = users.domain_id WHERE domain="x" AND username="x" AND users.enabled = 1 AND domains.enabled = 1 Oct 13 09:43:22 toejamfootball dovecot: auth(default): pam(justin(a)x,192.168.2.11): pam_authenticate() failed: authentication error Any clues? I don't use pam for auth anyway, so I just ignore that. When I restart the server and login again it's fine. j.

2 1

[Dovecot] 1.0.alpha3 plaintext authentication problem
by Sergey Redin 28 Oct '05

28 Oct '05

Hello everyone, Since the upgrade to 1.0.alpha3 I experience a strange problem with plaintext authentication. I successfully login first few (2-5) times after the dovecot restart, and then on a reason I cannot login any more (both via POP3 and IMAP). I tried to find out what could be the reason for this but I failed. Nothing is changed inside the user's home directory or /var/run/dovecot, but I cannot login any more. I guess there is something wrong inside dovecot-auth od dovecot process itself. I just start to receive "01 NO Authentication failed." or "-ERR Authentication failed." from dovecot and "Authenticate PLAIN failed: Unsupported authentication mechanism.: method=PLAIN" in my logs, even though I used the same PLAIN two minutes ago without a problem. Here is my dovecot.conf: nevoservice# egrep -v '^[ ]*(\#.*)?$' /usr/local/etc/dovecot.conf protocols = imap pop3 ssl_disable = no ssl_cert_file = /etc/mail/certs/server.crt ssl_key_file = /etc/mail/certs/server.key disable_plaintext_auth = no log_path = /var/log/dovecot/log info_log_path = /var/log/dovecot/info login_user = dovecot login_processes_count = 1 verbose_proctitle = no first_valid_gid = 0 mail_extra_groups = mail mail_debug=yes default_mail_env = mbox:/var/mail/%u maildir_copy_with_hardlinks = yes protocol imap { imap_client_workarounds = delay-newmail outlook-idle netscape-eoh tb-extra-mailbox-sep } protocol pop3 { pop3_uidl_format = %08Xu%08Xv pop3_client_workarounds = outlook-no-nuls oe-ns-eoh } auth_verbose = yes auth_debug = yes auth default { mechanisms = plain passdb passwd-file { args = /usr/local/etc/dovecot.passwd } userdb passwd-file { args = /usr/local/etc/dovecot.passwd } user = root } Here are two lines in dovecot.passwd which define the user that I use: wail:password-hash:1050:1032:Administrator wail.spb.ru:/home/wail.spb.ru:::/var/mail/wail wail@nevoservice.ispvds.com:password-hash:1050:1032:Administrator wail.spb.ru:/home/wail.spb.ru:::/var/mail/wail A few lines from my /var/log/dovecot/info file: dovecot: Oct 10 02:03:11 Info: auth(default): client in: AUTH 1 PLAIN service=POP3 lip=82.146.50.34 rip=82.146.63.23 resp=AHdhaWwAVGxNSFRuUlI2 dovecot: Oct 10 02:03:11 Info: auth(default): client out: OK 1 user=wail dovecot: Oct 10 02:03:11 Info: auth(default): master in: REQUEST 3 53919 1 dovecot: Oct 10 02:03:11 Info: auth(default): master out: USER 3 wail uid=1050 gid=1032 home=/home/wail.spb.ru mail=/var/mail/wail dovecot: Oct 10 02:03:11 Info: pop3(wail): Effective uid=1050, gid=1032 dovecot: Oct 10 02:03:11 Info: pop3(wail): maildir autodetect: stat(/var/mail/wail/cur) failed: Not a directory dovecot: Oct 10 02:03:11 Info: pop3(wail): mbox autodetect: data=/var/mail/wail dovecot: Oct 10 02:03:11 Info: pop3(wail): mbox autodetect: INBOX file: yes (/var/mail/wail) dovecot: Oct 10 02:03:11 Info: pop3(wail): mbox: data=/var/mail/wail dovecot: Oct 10 02:03:11 Info: pop3(wail): mbox: root exists (/home/wail.spb.ru/mail) dovecot: Oct 10 02:03:11 Info: pop3(wail): mbox: root=/home/wail.spb.ru/mail, index=/home/wail.spb.ru/mail, inbox=/var/mail/wail dovecot: Oct 10 02:03:11 Info: pop3-login: Login: user=<wail>, method=PLAIN, rip=82.146.63.23, lip=82.146.50.34 dovecot: Oct 10 02:03:13 Info: pop3(wail): Logout. top=0/0, retr=0/ del=0/3, size=5372 dovecot: Oct 10 02:03:20 Info: auth(default): client in: AUTH 1 PLAIN service=POP3 lip=82.146.50.34 rip=82.146.63.23 resp=AHdhaWwAVGxNSFRuUlI2 dovecot: Oct 10 02:03:20 Info: auth(default): client out: OK 1 user=wail dovecot: Oct 10 02:03:20 Info: auth(default): master in: REQUEST 4 53918 1 dovecot: Oct 10 02:03:20 Info: auth(default): master out: USER 4 wail uid=1050 gid=1032 home=/home/wail.spb.ru mail=/var/mail/wail dovecot: Oct 10 02:03:20 Info: pop3(wail): Effective uid=1050, gid=1032 dovecot: Oct 10 02:03:20 Info: pop3(wail): maildir autodetect: stat(/var/mail/wail/cur) failed: Not a directory dovecot: Oct 10 02:03:20 Info: pop3(wail): mbox autodetect: data=/var/mail/wail dovecot: Oct 10 02:03:20 Info: pop3(wail): mbox autodetect: INBOX file: yes (/var/mail/wail) dovecot: Oct 10 02:03:20 Info: pop3(wail): mbox: data=/var/mail/wail dovecot: Oct 10 02:03:20 Info: pop3(wail): mbox: root exists (/home/wail.spb.ru/mail) dovecot: Oct 10 02:03:20 Info: pop3(wail): mbox: root=/home/wail.spb.ru/mail, index=/home/wail.spb.ru/mail, inbox=/var/mail/wail dovecot: Oct 10 02:03:20 Info: pop3-login: Login: user=<wail>, method=PLAIN, rip=82.146.63.23, lip=82.146.50.34 dovecot: Oct 10 02:03:21 Info: pop3(wail): Logout. top=0/0, retr=0/ del=0/3, size=5372 dovecot: Oct 10 02:03:28 Info: pop3-login: Authenticate PLAIN failed: Unsupported authentication mechanism.: method=PLAIN, rip=82.146.63.23, lip=82.146.50.34 dovecot: Oct 10 02:03:30 Info: pop3-login: Aborted login: method=PLAIN, rip=82.146.63.23, lip=82.146.50.34 We see here two successfull logins with PLAIN and then suddenly PLAIN becomes unsupported. I run dovecot 1.0.alpha3 on FreeBSD 4.11, it was installed from ports and then I edited dovecot.conf (and created dovecot.passwd). Any help would be really appreciated. Sergey Redin.

2 1

Re: [Dovecot] Dovecot Alpha 4
by Tomi Hakala 28 Oct '05

28 Oct '05

Marcus Don wrote: > How confident are you of the CVS? Any idea when the next (perhaps beta?) > release will be? I run CVS code most of the time, but only with handful of users and with them it has been working OK. I wouldn't use CVS code in production without thorough stress testing in a lab first. >>Have you thought of clustered file system to go with your Dovecot >>hosts and CLARiiON device? > I'm not sure why this would benefit us at the moment. Before we switched to > maildirs, the bottleneck we were experiencing at busy times was the ethernet > speed, not the storage device speed. > Is there another reason you suggested this? No, I'm just not very fond of NFS myself but it seems that for you it is doing job pretty well. Your CLARiiON is a normal SAN device and you have some singe host providing NFS? It didn't quite open to me how your mail spool is set up, is it some meta LUN distributed over two disk arrays or do you just have one huge LUN and mirror it between two arrays? -- Tomi Hakala

1 0

[Dovecot] problem with thunderbird
by Alfonso Sparano 28 Oct '05

28 Oct '05

Hi all, I've a problem with thunderbird 1.0.6/7/1.5 and dovecot pop3 I've tried dovecot alpha 3 and 1.0 stable but neither one is capable of downloading mails. Nothing is written into the log. I've tried also to delete dovecot.index* and dovecot-uidlist into the Maildir directory. The cur directory contains more than 8100 messages (single files) Anyone has founded this problem? Alfonso

3 3

[Dovecot] Corrupted index cache file [...] invalid record size
by Lorens 28 Oct '05

28 Oct '05

I get this error every single time some of my users log in: Error: POP3(${user}): Corrupted index cache file /${userdir}/dovecot.index.cache: invalid record size The named file seems to be deleted as soon as corruption is found. This only affects some users. I thought the affected users had in common that they are using POP3 in "leave-messages-on-server" mode, and that their mailboxes are big ( > 100 MB). However I've found a few counterexamples, few and far between (not every login) but still. Google's no help, for once :-) Could this be a locking problem, a bug with big Maildirs (counterexamples being few), or what? I know some of my users have had problems logging several IMAP clients into the smae account at the same time, wouldn't put it past some of those with problems to be trying the same with POP. I know that a detected cache corruption is merely that, but I find the error message annoying :-) Configuration: v1.0-stable (0.99.20050712-2 from debian unstable) Maildir only Default locking (nothing mentioned in conf file) Access over NFS mmap_disable = yes (wiki says to disable mmap to use indexes on NFS). Thanks for any pointers.

2 1

[Dovecot] 1.0alpha3: assert and core
by Jeff A. Earickson 28 Oct '05

28 Oct '05

Hi, An assert and core with 1.0alpha3 on Solaris 9, mbox format, imap only, compiled with gcc 4.0.1. The syslog message was: imap(user): file message-body-search.c: line 393 (message_body_search_ctx): assertion failed: (input->v_offset <= part->physical_pos) gdb core dump analysis is attached. Jeff Earickson Colby College

2 1

[Dovecot] hangup with corrupted indexes
by Sergey Redin 28 Oct '05

28 Oct '05

Hello everyone, I remember that Timo wrote in this maillist that if index files are corrupted, dovecot should be OK and just recreate it. So I report here a bug: I have corrupted indexes which make pop3 and imap processes to hangup right after the first list command. The process does not respond and eats 90% of CPU. Just unpack http://redin.info/dovecot-corrupted-index.tgz (10 Kb) into a user's IMAP root (I have mbox storage, but the same thing for maildir with this indexes), do the chown, and try to check the email. I know that the problem can be fixed by removing the index files or using INDEX=MEMORY, but it is claimed that dovecot is failsafe and can deal with any kind of corrupted index files. This is the only reason why I report it here. I have 1.0.alpha4 on FreeBSD 4.11 (installed from ports). Best regards, Sergey Redin.

2 1

[Dovecot] Dovecot problems on Debian
by Jaldhar H. Vyas 28 Oct '05

28 Oct '05

If you have been bitten by bug #334180 and dovecot 1.0alpha3-2.0.1 rest assured the problem is being worked on. In the meantime you should downgrade to -2 which can be found at: http://snapshot.debian.net/archive/2005/10/08/debian/pool/main/d/dovecot/ -- Jaldhar H. Vyas <jaldhar(a)debian.org> La Salle Debain - http://www.braincells.com/debian/

1 0

[Dovecot] Weirdness with authentication/1.0a4.
by Ashley Penney 28 Oct '05

28 Oct '05

Hi, FreeBSD has recently upgraded their port from 0.99 to 1.0a4, and this has caused me an absolute nightmare of a situation. In a nutshell I replaced my conf with the -example, and modified almost nothing. I made some SSL certs and put them in place, left it with imap/pop/pam etc. Whenever users tried to connect to the remote address, cara.untaken.net, I would get: Oct 27 18:31:14 cara dovecot: Dovecot v1.0.alpha4 starting up Oct 27 18:31:33 cara dovecot: imap-login: Login failed: Plaintext authentication disabled: rip=217.206.62.50, lip=217.206.62.50 Oct 27 18:31:33 cara dovecot: imap-login: Disconnected: rip=217.206.62.50, lip=2 17.206.62.50 However, plaintext authenication was most definitely not disabled. Using www.untaken.net/mail/ which is hosted on the same box as dovecot I could get this plaintext failure constantly using cara.untaken.net, but switching to 'localhost' instead would work fine, despite being the same physical machine. I'm baffled at what could cause this, I put my currently conf over at www.untaken.net/dovecot/ just for reference, I've modified various bits now from the default in a desperate attempt to get it working. Has anyone else seen anything like it? -- <EisernLint> i am considering taking pilates classes.

2 1

[Dovecot] Authentication using native MySQL PASSWORD() function
by Tom Sommer 28 Oct '05

28 Oct '05

Hi, I have a little problem, I need to adapt a setup that currently uses the native MySQL PASSWORD() function to encrypt passwords for e-mail accounts. I plan on using Dovecot with SQL to authenticate on my server, is there a password scheme that fits this authentication method? Any help is appreciated -- Tom Sommer

3 11

[Dovecot] Strange Disconnect Problem
by Marc Perkel 27 Oct '05

27 Oct '05

It's only happening with one user but for some reason I can't get this person logged in. And I'm using his ID on my computer and my ID works. Using two different IMAP clients. What would be causeing the "disconnected" to happen? dovecot: Oct 17 10:56:43 Info: imap-login: Login: user=<lowsley(a)cbsyellowpgs.com>, method=PLAIN, rip=65.37.192.182, lip=69.50.231.10 dovecot: Oct 17 10:56:47 Info: imap-login: Disconnected: user=<john(a)sembrot.com>, method=PLAIN, rip=204.95.16.61, lip=69.50.231.10

2 1

[Dovecot] Shared Folder usage alpha3
by Ralf Zerres 27 Oct '05

27 Oct '05

Dear List, this is my first mail to this list. I'v tried to carefully review all given information towards the Shared Folder subject I could find in the archive / mailing list / wiki. And so far I'm also aware that Timo hasn't put it on the active tasklist for the 1.0 release. Citing the track http://dovecot.org/pipermail/dovecot/2003-October/002493.html I was wandering, wether any further attempt has been made, to use the given functionality for real work. To be more precise, wether anybody has done - delivery of mailboxes to a shared maildir - offering these maildirs through a given namespace Before bothering here without any local experience, I'v set up a dov-server (1.0alpha3) on a debian sid. As an MTA postfix is doing the job. Within postfix I did set up a virtual domain and the needed maps (mailbox, alias). I'm able to deliver successful with the standard postfix functionality to the given filesystem structure (fs=ext3). If it is on any help, I can post the relevant config files. As good practice, all mail is delivered to given mailbox-owner with 0600 permission for the new subdir. Hence, can't be seen by any shared-maildir user (unless owner uid matches:) >From here on I'v tried to switch from debians default postfix delivery-strategy (mailbox_command = procmail -a "$EXTENSION") to given dovcot deliver process (mailbox_command = /usr/lib/dovecot/deliver). The primary aim is to define a strategy to deliver with 0660 rights which will enable group read-write access to the given Mailstore. I have adopted the dovecot.conf enableing a listening socket ... default_mail_env = maildir:/home/%u/Maildir: \ INDEX=/home/%u/MaildirIndex namespace private { separator = / prefix = inbox = yes } namespace public { # the prefix needs to be postponed with the separator prefix = Public/ # the location path given as [<mailbox-type>:]<path>/mailbox location = maildir:/home/SharedMaildirs separator = / inbox = no hidden = no } auth default { ... # using deliver through a socket socket listen { master { path = /var/run/dovecot/auth-master mode = 0666 } } } and configured the subsequent dovecot-deliver.conf ... auth_socket_path = /var/run/dovecot/auth-master mail = maildir:%h/Maildir/ umask = 0007 auth_verbose = yes use_syslog = yes just to see, whether a manual call /usr/lib/dovecot/dovecot-deliver -d <user> <testmail would do the trick. Well, I got the delivered mail, but files are not installed with the etimated previledges. Can someone can point me to the clou? Greetings Ralf PS: I also read about posix-acl's support. But my test's didn't allow a successful read ....

2 1

[Dovecot] Alpha4 pre-release, please upgrade
by Timo Sirainen 27 Oct '05

27 Oct '05

Please try if http://dovecot.org/nightly/dovecot-latest.tar.gz (or the CVS directly) works with you. I made a lot of changes to dovecot-auth, so I wouldn't want to make alpha4 release without some more testing in different environments. I'll release alpha4 in a few days, but it'll be basically same as this unless more bugs get fixed. Some of the changes include: - IMAP: We might have sent extra EXPUNGE messages when output buffer got full. This could have caused various sorts of very bad behavior. This is the main reason why everyone should upgrade as soon as possible. - POP3: We sent duplicate replies for LIST command when output buffer got full. Probably caused Thunderbird's duplicate deletion bugs? (Although I thought someone checked that Dovecot's reply was correct when the bug occurred?) - pop3_uidl_format setting is now required to be explicitly set in configuration file for pop3 to work at all. I want to get rid of the old default setting which breaks Outlooks, and simply changing the default would break existing setups. - Multiple passdbs and userdbs of same type can now be added with different parameters. Some people asked about this earlier. - Authentication cache works now with other than SQL and LDAP passdbs. Some passdbs such as PAM require some additional settings to work. See example config file. - Some other fixes to authentication cache related to failure handling and non-plaintext authentication. - deny passdb wasn't working for non-plaintext authentication.

8 21

[Dovecot] auth
by Riccardo Bini 27 Oct '05

27 Oct '05

It's possible to have an auth order so if the first is true skip the other ones? Bye Rick

2 1

[Dovecot] pop3 behaviour
by Krzysztof Janiszewski - IT Partner 27 Oct '05

27 Oct '05

Hi! I'v installed dovecot over um-pop3 today. Dovecot has only pop3 enabled. imap will be enabled later. But there is one issue - on some accounts, after receiving mail to Outlook Express, mail is not deleted from /var/mail/username mbox file, and on most it is deleted. Why it works in that way? Best regards Krzysztof

2 1

[Dovecot] how to configure dovecot, Error
by Roland Schmid 27 Oct '05

27 Oct '05

Hi, we are using Squirrelmail, imapd is dovecot. OS is Debian Sarge. When I want to login with Squirrelmail the connection to the imap-server is aborted. /var/log/mail.log gives the these log-entries: Oct 25 14:39:36 webserver dovecot: imap(rs.messegrafik-schreiber.de): mbox: Can't create root IMAP folder /home/rs.messegrafik-schreiber.de/mail: Permission denied Oct 25 14:39:36 webserver dovecot: imap(rs.messegrafik-schreiber.de): MAIL environment missing and autodetection failed (home /home/rs.messegrafik-schreiber.de) Oct 25 14:39:36 webserver dovecot: imap-login: Login: user=<rs.messegrafik-schreiber.de>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured Oct 25 14:39:36 webserver dovecot: child 31339 (imap) returned error 89 Need help, thanks. Roland

2 1

[Dovecot] Pop3 Pipeing
by Mark Smith 27 Oct '05

27 Oct '05

How would I go about and setup pop3 pipeing with dovecot I have instaled Perldesk and there instructions is for only Exim or Sendmail. Regards, _________________________________________________________________ MSN Messenger 7.5 is now out. Download it for FREE here. http://messenger.msn.co.uk

2 1

[Dovecot] 1.0alpha4: mbox-lock asserts and cores
by Jeff A. Earickson 27 Oct '05

27 Oct '05

Timo, I upgraded from alpha3 to alpha4 yesterday, and I am seeing a few of the following asserts: imap(user): file mbox-lock.c: line 379 (mbox_lock_fcntl): assertion failed: (lock_type == F_UNLCK) Gdb info on a couple of the cores is attached. It looks like the arg lock_type for mbox_lock_fcntl() is not getting passed in correctly, like the enum "enum mbox_lock_type type" in mbox_lock_list() is not getting set or used correctly so that lock_data[type].func is wrong. Hmmm. My setup: Solaris 9, mbox, dovecot built with gcc 4.0.2. The filesystem for INBOXes is NFS mounted from another Solaris 9 system, but the index files reside on local filesystems. My setting for "lock_method = fcntl", per your release notes. I did not change the default setting of "mmap_disable = no" because my index files are local. Jeff Earickson Colby College

2 1

[Dovecot] USER environment missing
by Ed 27 Oct '05

27 Oct '05

I am new to dovecot, and while I have the pop server running fine, I am having trouble with the imap server. It starts, but when I try to connect, I get an error: telnet localhost imap Trying 127.0.0.1... Connected to localhost.localdomain. Escape character is '^]'. imap(??): Fatal: USER environment missing Connection closed by foreign host. Not sure where to start on this one. (or what to show you). I am running under Ubuntu Linux, usiang postfix, fetchmail, etc.. (not sure that matters). -- No virus found in this outgoing message. Checked by AVG Anti-Virus. Version: 7.0.344 / Virus Database: 267.12.4/143 - Release Date: 10/19/2005

2 1

[Dovecot] alpha4 and zlib-plugin?
by Jeff A. Earickson 27 Oct '05

27 Oct '05

Hi, I saw the zlib-plugin reference in the alpha4 ChangeLog notes are searched the list for info about it. The only reference I found was from Timo back in March 2005. Questions: 1) Is this going to become a standard part of version 1.0? 2) Any plans or ability to make it read/write to a gzipped mailbox, or is this possible? Or will it always be read-only? 3) How does a mailbox get gzipped? From within dovecot somehow, or only by external action? Jeff Earickson Colby College

3 2

Re: [Dovecot] pop3 behaviour
by Krzysztof Janiszewski - IT Partner 26 Oct '05

26 Oct '05

Hello! > Do you have reason to believe that the clients are issuing a delete > command and that the mail is incorrectly being left on the server OR do > they have a 'keep mail on server' option checked? I'm sure thet they have 'keep mail on server' unchecked. When uw-ipop3d was used, mail was correctly deleted. Best regards Krzysztof

1 0

[Dovecot] Two "pre-migration" questions
by Alan Mead 26 Oct '05

26 Oct '05

I have read the migration docs. They seem to relate to migrating from one imap product to dovecot on the same server. I'm interested in migrating my Maildir-formatted email from one server to another. 1. Can I tar my ~/mail directory on serverX.com, untar it on a different physical serverY.com (initially with a different domain name), and still see my mail when I access imap.serverY.com <http://imap.serverY.com> (dovecot's running on serverY.com .. but let me know if there are any tricks that I need to make this work). 2. If I maintain large mailboxes and check my mail frequently, how does the dovecot server load compare to something like apache or Samba? I ask because I have a vanity domain that I mostly use for email and I want to ensure that I can migrate my precious emails to a new service provider. And the provider that I'm considering offers low-cost virtual dedicated servers but meters usage (including RAM and CPU). One of the reasons I have question #1 is that the server name seems to be part of the email file names... amead:/home/amead> ls mail/cur | head -2 2022292282.22297_0.vulcan.rootr.net:2,S 2022312282.3225_0.vulcan.rootr.net:2,S (rootr.net <http://rootr.net> is my current provider, not my vanity domain; vulcan is the name of their mailserver) I don't know what effect this will have, if any? Thanks! -Alan

3 3

[Dovecot] [Fwd: Dovecot disconnecting users at login for inactivity]
by Chris Liljenstolpe 25 Oct '05

25 Oct '05

3 3

[Dovecot] choosing syslog facility?
by Dominik Werder 25 Oct '05

25 Oct '05

Hello! How can I log dovecots messages into a separate file? Is it possible to set a custom syslog facility name somehow? I can't set the log file in dovecot because dovecot does not automatically rotate the logs like syslog does.. thank you! Dominik

4 4

[Dovecot] alpha4 - Unknown passdb driver 'pam'
by Willem Riede 25 Oct '05

25 Oct '05

Does anybody see this? Oct 24 19:41:44 athena dovecot: Dovecot v1.0.alpha4 starting up Oct 24 19:41:45 athena dovecot: Auth process died too early - shutting down Oct 24 19:41:45 athena dovecot: auth(default): Unknown passdb driver 'pam' Oct 24 19:41:45 athena dovecot: child 3374 (auth) returned error 89 This is on Fedora FC5-devel x86_64 (opteron), which is certainly pam based. FWIW, if I switch to passwd dovecot alph4 runs fine (so far). Regards, Willem Riede.

2 1

[Dovecot] Pop3 Pipeing
by Mark Smith 24 Oct '05

24 Oct '05

Does anyone know how to pipe with dovecot-pop3d? Please help Thanks _________________________________________________________________ Be the first to hear what's new at MSN - sign up to our free newsletters! http://www.msn.co.uk/newsletters

1 0

[Dovecot] debian dovecot upgrade
by Brent Clark 24 Oct '05

24 Oct '05

Hi all I find this highly upsetting, I just upgrade my debian dovecot, and I specified that I dont want to upgrade the conf file. and on restarting, I get this in my syslog. Oct 24 17:33:33 mail dovecot: Dovecot v1.0.alpha3 starting up Oct 24 17:33:34 mail dovecot: Login process died too early - shutting down Oct 24 17:33:34 mail dovecot: imap-login: Can't load certificate file /etc/ssl/certs/dovecot.pem: error:25066067:DSO support routines:DLFCN_LOAD:could not load the shared library Oct 24 17:33:34 mail dovecot: imap-login: Can't load certificate file /etc/ssl/certs/dovecot.pem: error:25066067:DSO support routines:DLFCN_LOAD:could not load the shared library Oct 24 17:33:34 mail dovecot: child 5983 (login) returned error 89 Oct 24 17:33:34 mail dovecot: child 5985 (login) returned error 89 mail:~# Wierd thing is, at no time am I asking for ssl, and in my conf file I have it hashed out. mail:~# cat /etc/dovecot/dovecot.conf | grep ssl # --with-ssldir=/etc/ssl #ssl_listen = #ssl_disable = no #ssl_cert_file = /etc/ssl/certs/dovecot.pem #ssl_key_file = /etc/ssl/private/dovecot.pem #ssl_ca_file = #ssl_verify_client_cert = no #ssl_parameters_file = /var/run/dovecot/ssl-parameters.dat #ssl_parameters_regenerate = 24 #ssl_cipher_list = all:!LOW #verbose_ssl = no #ssl_require_client_cert = no mail:~# I tried on the command line # dovecot -F -c dovecot.conf my version is: mail:~# dovecot --version 1.0.alpha3 mail:~# Would anyone perhaps know why I cant get the daemon started. Kind Regards Brent Clark

2 2

[Dovecot] dual auth with real users and virtual users
by Erick Perez 24 Oct '05

24 Oct '05

Hi, im using 0.99 stable in RPM form, Im using this for postfix+dovecot+real unix users, now i tried to enable virtual support with this: protocols = imap pop3 ssl_disable = yes log_path = /var/log/dovecot.log info_log_path = /var/log/dovecot.info login_user = dovecot mail_extra_groups = mail auth = default auth_mechanisms = plain auth_passdb = pam auth_userdb = passwd auth_userdb = passwd-file /etc/vhosts/userdb auth_passdb = passwd-file /etc/vhosts/passwd The above configuration works for local users but is not working for virtual users, it produces the error: dovecot-auth: Oct 21 00:19:14 Info: PAM: pam_authenticate(erickperez) failed: Authentication failure obviously the user erickperez exists in /etc/vhosts/userdb so PAM will fail. Im using 0.99 release. Thanks, -- ------------------------------------------- Erick Perez Linux User 376588 http://counter.li.org/ (Get counted!!!) Panama, Republic of Panama

2 2

[Dovecot] 1.0alpha4: drowning in asserts/cores
by Jeff A. Earickson 24 Oct '05

24 Oct '05

Timo, I have had to drop back to alpha3 because I found a pile of core files on my imap server this morning, from the weekend. They are all from the assert: imap(user): file mbox-lock.c: line 379 (mbox_lock_fcntl): assertion failed: (lock_type == F_UNLCK) I reported this issue to the list last Friday. Help... Jeff Earickson Colby College

1 0

[Dovecot] Case of %n (feauture request)
by Alexander Shikoff 24 Oct '05

24 Oct '05

Hello, I'm using dovecot not for a long time but I've newer seen most powerful and handy POP3/IMAP server. Thank Timo for dovecot; thank community for help! I would like to notice that %n is case-sensitive: it always stores user part of login without case conversions. As a result there are some inconveniences with virtual user organization, for example: password_query = SELECT `password` FROM `users` WHERE login = '%u' user_query = SELECT "mbox:/var/mail/virtual/%d/%n:INBOX=/var/mail/virtual/%d/%n:INDEX=MEMORY" AS `mail`, 101 AS `uid`, 101 AS `gid` FROM users WHERE login = '%u' In this example authentication works perfectly but user can not access it's mailbox because all mailbox names are lower-case. I think it would be more handy to make %d, %n and %u aliases lower-case and introduce three new aliases %D %N %U which store values without case conversions. But I'm not enough skilled in C to write a patch... and now I'm waiting for comments on this and answer from the developer. Thanks in advance, Alexander. -- Kind Regards, Alexander Shikoff minotaur(a)crete.org.ua

2 2

Re: [Dovecot] Same email recieved
by Bob Hope 24 Oct '05

24 Oct '05

Andrew Hutchings wrote: > On Fri, 2005-10-14 at 12:46 -0500, Bob Hope wrote: > >> They are using Outlook. I'm not seeing anything about UIDs of mails >> in dovecot.conf. I'm using dovecot 0.99.14 presently. >> >> Regards, >> >> Savage >> > > > Ah, afraid I can't really help then, I haven't used the .99 series of > Dovecot for over a year now and there seem to be quite a few issues with > it. > > Regards > Andrew > -- > Andrew Hutchings (A-Wing) - Linux Guru > Netserve Consultants - http://www.domaincity.co.uk/ > Linux CDs and DVDs - http://www.linuxiso.co.uk/ > Random quote 1: "Microsoft is not the answer. Microsoft is the question. > NO (or Linux) is the answer." - Unknown > > > > Well, I suppose I could upgrade to 1.0 then. I'll give that a try and drop a note here if it works. Thanks, Savage

1 1

[Dovecot] dovecot + postfix + freebsd help
by glemme 23 Oct '05

23 Oct '05

Hi. I'm currently setting up dovecot to work with my server. My inboxes from postfix are stored in /usr/var/spool/mail/ and then the username, so for me that would be / usr/var/spool/mail/viktor my homedirectory is /usr/home/glemme/homes/viktor/ so from what i can understand. My settings should be: default_mail_env = mbox:%h/Mail:INBOX:/usr/var/spool/mail/%u But guess what, I am probably wrong. my mailapp tells me my inbox is empty and my log claims this: dovecot: Oct 22 16:39:35 Info: imap(viktor: Effective uid=1015, gid=1004 dovecot: Oct 22 16:39:35 Info: imap(viktor: mbox: data=/usr/home/ glemme/homes/viktor/Mail:INBOX:/usr/var/spool/mail/viktor dovecot: Oct 22 16:39:35 Info: imap(viktor): mbox: INBOX defaulted to /usr/home/glemme/homes/viktor/Mail/inbox dovecot: Oct 22 16:39:35 Info: imap(viktor): mbox: root=/usr/home/ glemme/homes/viktor/Mail, index=/usr/home/glemme/homes/viktor/Mail, inbox=/usr/home/glemme/homes/viktor/Mail/inbox Why is it defaulting from the right INBOX to the wrong one? HELP! /glemme

2 1

[Dovecot] 1.0alpha2: how to reject specific users?
by Jeff A. Earickson 21 Oct '05

21 Oct '05

Hi, In Qualcomm's qpopper, you can specify a list of users to reject at authentication, even if they are otherwise valid, by putting them in a file (/etc/pop.nonauth). I use this to occasionally ban users who bang on the system needlessly until they Get a Clue. I looked thru the wiki.dovecot.org/Authentication pages and didn't see anything like this feature. Does it exist in 1.0? BTW, running 1.0alpha2 in production since Sunday night, working great. Zero core dumps, only minor chatter about "Corrupted index cache file" in the syslog, no problems. Jeff Earickson Colby College

3 7

[Dovecot] latest dovecot rpm for RedHat Enterprise 3
by Erick Perez 21 Oct '05

21 Oct '05

Does anyone have a repository with the latest dovecot for RHEL3 ? I have only found dovecot-1.0.0.4-200502 which is for february 2005. I dont know how to build rpms from .tar so i will not venture on that without some magic tool. Thanks,

1 0

[Dovecot] Performance issues in Alpha4 gone
by Daniel 21 Oct '05

21 Oct '05

Hi The performance issues I noticed on my system/setup with Alpha3 seem to be gone with Alpha4. As soon as I installed it I noticed imap seemed more responsive. Just thought I would let the list know. Regards Daniel

2 1

[Dovecot] imaps on alternate ports
by Andrew D. Clark 21 Oct '05

21 Oct '05

I'm trying to test out dovecot 1.0 alpha 3 prior to an upgrade from dovecot-0.99.14, but I cannot get imaps listening on anything other than 993. I've tried putting listen = *:2023 in the global section or in the imap { } section. No luck. What is the proper format for a config that only runs imaps and only listens on a particular port? -- Andrew Clark Campus Network Programmer University of California, Santa Barbara andrew.clark(a)ucsb.edu (805) 893-5311

2 1

[Dovecot] alpha4: flock change
by Jeff A. Earickson 20 Oct '05

20 Oct '05

Timo, The comments in dovecot-example.conf regarding lock_method for Solaris users needs to note your change. Your changelog says: - Default lock_method changed to flock instead of the old fcntl. Solaris users will need to set it back to fcntl. This makes sure that Dovecot's indexes aren't accidentally used with NFS. But there is no warning about this in the file for Solaris users. There should be; it will bite somebody later. Jeff Earickson Colby College

1 0

[Dovecot] [PATCH] Support for GSSAPI SASL Mechanism
by Jelmer Vernooij 20 Oct '05

20 Oct '05

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, Attached is a patch against current CVS that adds support for the GSSAPI SASL mechanism. It was written from scratch, after reading the patch from Colin Walters against a much older version of dovecot. Other then support for the 'GSSAPI' mechanism, it contains the following changes: - - Added 'auth_krb5_keytab' option for overriding default keytab location. The gssapi library already uses the environment variable KRB5_KTNAME to allow overriding of the keytab location, so I didn't have to make any changes on the login process side. - - Added 'need_passdb' member to mech_module and allow having no passdb's specified if no mechanisms need them (only useful for GSSAPI at the moment) Cheers, Jelmer - -- Jelmer Vernooij <jelmer(a)samba.org> -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) iD8DBQFDVgaEPa9Uoh7vUnYRAscGAJ9Fa4E5ze5IX3UeAfjwg7kzj5tgtQCcDva7 O5VTeOeJ7zpmHullxQN6q1Y= =60w7 -----END PGP SIGNATURE----- Index: configure.in =================================================================== RCS file: /home/cvs/dovecot/configure.in,v retrieving revision 1.214 diff -u -r1.214 configure.in --- configure.in 23 Sep 2005 13:28:40 -0000 1.214 +++ configure.in 19 Oct 2005 08:25:31 -0000 @@ -118,6 +118,15 @@ fi, want_bsdauth=yes) +AC_ARG_WITH(gssapi, +[ --with-gssapi Build with GSSAPI authentication support (default)], + if test x$withval = xno; then + want_gssapi=no + else + want_gssapi_yes + fi, + want_gssapi=yes) + AC_ARG_WITH(ldap, [ --with-ldap Build with LDAP support], if test x$withval = xno; then @@ -1192,6 +1201,17 @@ ]) fi +have_gssapi=no +if test $want_gssapi = yes; then + AC_CHECK_PROG(KRB5CONFIG, krb5-config, YES, NO) + if test $KRB5CONFIG = YES; then + AUTH_LIBS="$AUTH_LIBS `krb5-config --libs gssapi`" + AUTH_CFLAGS="$AUTH_CFLAGS `krb5-config --cflags gssapi`" + AC_DEFINE(MECH_GSSAPI,, Build with GSSAPI support) + have_gssapi=yes + fi +fi + if test $want_ldap = yes; then AC_CHECK_LIB(ldap, ldap_init, [ AC_CHECK_HEADER(ldap.h, [ @@ -1486,5 +1506,6 @@ echo "Building with IPv6 support .......... : $want_ipv6" echo "Building with pop3 server ........... : $want_pop3d" echo "Building with mail delivery agent .. : $want_deliver" +echo "Building with GSSAPI support ........ : $have_gssapi" echo "Building with user database modules . :$userdb" echo "Building with password lookup modules :$passdb" Index: dovecot-example.conf =================================================================== RCS file: /home/cvs/dovecot/dovecot-example.conf,v retrieving revision 1.155 diff -u -r1.155 dovecot-example.conf --- dovecot-example.conf 16 Oct 2005 14:59:12 -0000 1.155 +++ dovecot-example.conf 19 Oct 2005 08:25:31 -0000 @@ -568,9 +568,13 @@ # automatically created and destroyed as needed. #auth_worker_max_count = 30 +# Kerberos keytab to use for the GSSAPI mechanism. Will use the system +# default (usually /etc/krb5.keytab) if not specified. +#auth_krb5_keytab = + auth default { # Space separated list of wanted authentication mechanisms: - # plain digest-md5 cram-md5 apop anonymous + # plain digest-md5 cram-md5 apop anonymous gssapi mechanisms = plain # Index: src/auth/Makefile.am =================================================================== RCS file: /home/cvs/dovecot/src/auth/Makefile.am,v retrieving revision 1.47 diff -u -r1.47 Makefile.am --- src/auth/Makefile.am 7 Aug 2005 11:41:19 -0000 1.47 +++ src/auth/Makefile.am 19 Oct 2005 08:25:31 -0000 @@ -54,6 +54,7 @@ mech-cram-md5.c \ mech-digest-md5.c \ mech-ntlm.c \ + mech-gssapi.c \ mech-rpa.c \ mech-apop.c \ passdb.c \ Index: src/auth/auth.c =================================================================== RCS file: /home/cvs/dovecot/src/auth/auth.c,v retrieving revision 1.19 diff -u -r1.19 auth.c --- src/auth/auth.c 16 Oct 2005 14:06:59 -0000 1.19 +++ src/auth/auth.c 19 Oct 2005 08:25:31 -0000 @@ -56,8 +56,6 @@ } t_pop(); - if (auth->passdbs == NULL) - i_fatal("No password databases set"); if (auth->userdbs == NULL) i_fatal("No user databases set"); return auth; @@ -130,6 +128,9 @@ struct mech_module_list *list; for (list = auth->mech_modules; list != NULL; list = list->next) { + if (list->module.need_passdb && + !auth->passdbs) + break; if (list->module.passdb_need_plain && !auth_passdb_list_have_plain(auth)) break; Index: src/auth/mech-anonymous.c =================================================================== RCS file: /home/cvs/dovecot/src/auth/mech-anonymous.c,v retrieving revision 1.13 diff -u -r1.13 mech-anonymous.c --- src/auth/mech-anonymous.c 23 Apr 2005 09:11:49 -0000 1.13 +++ src/auth/mech-anonymous.c 19 Oct 2005 08:25:31 -0000 @@ -57,6 +57,7 @@ MEMBER(flags) MECH_SEC_ANONYMOUS, + MEMBER(need_passdb) TRUE, MEMBER(passdb_need_plain) FALSE, MEMBER(passdb_need_credentials) FALSE, Index: src/auth/mech-apop.c =================================================================== RCS file: /home/cvs/dovecot/src/auth/mech-apop.c,v retrieving revision 1.16 diff -u -r1.16 mech-apop.c --- src/auth/mech-apop.c 23 Apr 2005 09:11:49 -0000 1.16 +++ src/auth/mech-apop.c 19 Oct 2005 08:25:31 -0000 @@ -162,6 +162,7 @@ MEMBER(flags) MECH_SEC_PRIVATE | MECH_SEC_DICTIONARY | MECH_SEC_ACTIVE, + MEMBER(need_passdb) TRUE, MEMBER(passdb_need_plain) FALSE, MEMBER(passdb_need_credentials) TRUE, Index: src/auth/mech-cram-md5.c =================================================================== RCS file: /home/cvs/dovecot/src/auth/mech-cram-md5.c,v retrieving revision 1.20 diff -u -r1.20 mech-cram-md5.c --- src/auth/mech-cram-md5.c 8 Jan 2005 21:37:32 -0000 1.20 +++ src/auth/mech-cram-md5.c 19 Oct 2005 08:25:32 -0000 @@ -191,6 +191,7 @@ MEMBER(flags) MECH_SEC_DICTIONARY | MECH_SEC_ACTIVE, + MEMBER(need_passdb) TRUE, MEMBER(passdb_need_plain) FALSE, MEMBER(passdb_need_credentials) TRUE, Index: src/auth/mech-digest-md5.c =================================================================== RCS file: /home/cvs/dovecot/src/auth/mech-digest-md5.c,v retrieving revision 1.34 diff -u -r1.34 mech-digest-md5.c --- src/auth/mech-digest-md5.c 8 Jan 2005 21:37:32 -0000 1.34 +++ src/auth/mech-digest-md5.c 19 Oct 2005 08:25:32 -0000 @@ -619,6 +619,7 @@ MEMBER(flags) MECH_SEC_DICTIONARY | MECH_SEC_ACTIVE | MECH_SEC_MUTUAL_AUTH, + MEMBER(need_passdb) TRUE, MEMBER(passdb_need_plain) FALSE, MEMBER(passdb_need_credentials) TRUE, Index: src/auth/mech-login.c =================================================================== RCS file: /home/cvs/dovecot/src/auth/mech-login.c,v retrieving revision 1.12 diff -u -r1.12 mech-login.c --- src/auth/mech-login.c 23 Apr 2005 09:11:49 -0000 1.12 +++ src/auth/mech-login.c 19 Oct 2005 08:25:32 -0000 @@ -87,6 +87,7 @@ MEMBER(flags) MECH_SEC_PLAINTEXT, + MEMBER(need_passdb) TRUE, MEMBER(passdb_need_plain) TRUE, MEMBER(passdb_need_credentials) FALSE, Index: src/auth/mech-ntlm.c =================================================================== RCS file: /home/cvs/dovecot/src/auth/mech-ntlm.c,v retrieving revision 1.19 diff -u -r1.19 mech-ntlm.c --- src/auth/mech-ntlm.c 23 Apr 2005 09:11:49 -0000 1.19 +++ src/auth/mech-ntlm.c 19 Oct 2005 08:25:32 -0000 @@ -281,6 +281,7 @@ MEMBER(flags) MECH_SEC_DICTIONARY | MECH_SEC_ACTIVE, + MEMBER(need_passdb) TRUE, MEMBER(passdb_need_plain) FALSE, MEMBER(passdb_need_credentials) TRUE, Index: src/auth/mech-plain.c =================================================================== RCS file: /home/cvs/dovecot/src/auth/mech-plain.c,v retrieving revision 1.31 diff -u -r1.31 mech-plain.c --- src/auth/mech-plain.c 23 Apr 2005 09:11:49 -0000 1.31 +++ src/auth/mech-plain.c 19 Oct 2005 08:25:32 -0000 @@ -103,6 +103,7 @@ MEMBER(flags) MECH_SEC_PLAINTEXT, + MEMBER(need_passdb) TRUE, MEMBER(passdb_need_plain) TRUE, MEMBER(passdb_need_credentials) FALSE, Index: src/auth/mech-rpa.c =================================================================== RCS file: /home/cvs/dovecot/src/auth/mech-rpa.c,v retrieving revision 1.19 diff -u -r1.19 mech-rpa.c --- src/auth/mech-rpa.c 23 Apr 2005 09:11:49 -0000 1.19 +++ src/auth/mech-rpa.c 19 Oct 2005 08:25:32 -0000 @@ -614,6 +614,7 @@ MEMBER(flags) MECH_SEC_DICTIONARY | MECH_SEC_ACTIVE | MECH_SEC_MUTUAL_AUTH, + MEMBER(need_passdb) TRUE, MEMBER(passdb_need_plain) FALSE, MEMBER(passdb_need_credentials) TRUE, Index: src/auth/mech.c =================================================================== RCS file: /home/cvs/dovecot/src/auth/mech.c,v retrieving revision 1.54 diff -u -r1.54 mech.c --- src/auth/mech.c 7 Jan 2005 19:55:50 -0000 1.54 +++ src/auth/mech.c 19 Oct 2005 08:25:32 -0000 @@ -54,6 +54,9 @@ extern struct mech_module mech_ntlm; extern struct mech_module mech_rpa; extern struct mech_module mech_anonymous; +#ifdef MECH_GSSAPI +extern struct mech_module mech_gssapi; +#endif void mech_init(void) { @@ -65,6 +68,9 @@ mech_register_module(&mech_ntlm); mech_register_module(&mech_rpa); mech_register_module(&mech_anonymous); +#ifdef MECH_GSSAPI + mech_register_module(&mech_gssapi); +#endif } void mech_deinit(void) @@ -77,4 +83,7 @@ mech_unregister_module(&mech_ntlm); mech_unregister_module(&mech_rpa); mech_unregister_module(&mech_anonymous); +#ifdef MECH_GSSAPI + mech_unregister_module(&mech_gssapi); +#endif } Index: src/auth/mech.h =================================================================== RCS file: /home/cvs/dovecot/src/auth/mech.h,v retrieving revision 1.35 diff -u -r1.35 mech.h --- src/auth/mech.h 9 Jan 2005 16:54:48 -0000 1.35 +++ src/auth/mech.h 19 Oct 2005 08:25:32 -0000 @@ -24,6 +24,7 @@ const char *mech_name; enum mech_security_flags flags; + unsigned int need_passdb:1; unsigned int passdb_need_plain:1; unsigned int passdb_need_credentials:1; Index: src/master/auth-process.c =================================================================== RCS file: /home/cvs/dovecot/src/master/auth-process.c,v retrieving revision 1.82 diff -u -r1.82 auth-process.c --- src/master/auth-process.c 1 Oct 2005 10:52:16 -0000 1.82 +++ src/master/auth-process.c 19 Oct 2005 08:25:33 -0000 @@ -458,6 +458,8 @@ env_put("SSL_REQUIRE_CLIENT_CERT=1"); if (set->ssl_username_from_cert) env_put("SSL_USERNAME_FROM_CERT=1"); + if (set->krb5_keytab) + env_put(t_strconcat("KRB5_KTNAME=", set->krb5_keytab, NULL)); restrict_process_size(set->process_size, (unsigned int)-1); } Index: src/master/master-settings.c =================================================================== RCS file: /home/cvs/dovecot/src/master/master-settings.c,v retrieving revision 1.92 diff -u -r1.92 master-settings.c --- src/master/master-settings.c 16 Oct 2005 14:59:17 -0000 1.92 +++ src/master/master-settings.c 19 Oct 2005 08:25:33 -0000 @@ -155,6 +155,7 @@ DEF(SET_STR, username_chars), DEF(SET_STR, username_translation), DEF(SET_STR, anonymous_username), + DEF(SET_STR, krb5_keytab), DEF(SET_BOOL, verbose), DEF(SET_BOOL, debug), @@ -353,6 +354,7 @@ MEMBER(username_chars) "abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@", MEMBER(username_translation) "", MEMBER(anonymous_username) "anonymous", + MEMBER(krb5_keytab) NULL, MEMBER(verbose) FALSE, MEMBER(debug) FALSE, Index: src/master/master-settings.h =================================================================== RCS file: /home/cvs/dovecot/src/master/master-settings.h,v retrieving revision 1.60 diff -u -r1.60 master-settings.h --- src/master/master-settings.h 1 Oct 2005 10:52:16 -0000 1.60 +++ src/master/master-settings.h 19 Oct 2005 08:25:33 -0000 @@ -162,6 +162,7 @@ const char *username_chars; const char *username_translation; const char *anonymous_username; + const char *krb5_keytab; int verbose, debug; int ssl_require_client_cert; --- /dev/null 2005-10-17 12:49:06.896857000 +0200 +++ src/auth/mech-gssapi.c 2005-10-19 10:17:45.000000000 +0200 @@ -0,0 +1,321 @@ +/* + * GSSAPI Module + * + * Copyright (c) 2005 Jelmer Vernooij <jelmer(a)samba.org> + * + * Related standards: + * - draft-ietf-sasl-gssapi-03 + * - RFC2222 + * + * Some parts inspired by an older patch from Colin Walters + * + * This program is free software; you can redistribute it and/or modify + * it under the terms of the GNU Lesser General Public License as published + * by the Free Software Foundation; either version 2 of the License, or + * (at your option) any later version. + */ + +#include "common.h" +#include "mech.h" +#include "passdb.h" +#include "str.h" +#include "buffer.h" +#include "hex-binary.h" +#include "safe-memset.h" +#include "hostpid.h" + +#ifdef MECH_GSSAPI + +#include <gssapi/gssapi.h> + +struct gssapi_auth_request { + struct auth_request auth_request; + gss_ctx_id_t gss_ctx; + gss_cred_id_t service_cred; + + enum { + GSS_STATE_SEC_CONTEXT, + GSS_STATE_WRAP, + GSS_STATE_UNWRAP + } sasl_gssapi_state; + + gss_name_t src_name; + + pool_t pool; +}; + +static void auth_request_log_gss_error(struct auth_request *request, OM_uint32 status_value, int status_type, const char *description) +{ + OM_uint32 message_context = 0; + OM_uint32 major_status, minor_status; + gss_buffer_desc status_string; + + do { + major_status = gss_display_status(&minor_status, status_value, + status_type, GSS_C_NO_OID, &message_context, + &status_string); + + auth_request_log_error(request, "gssapi", "While %s: %s", + description, (char *)status_string.value); + + major_status = gss_release_buffer(&minor_status, &status_string); + } while (message_context != 0); +} + +static struct auth_request *mech_gssapi_auth_new(void) +{ + struct gssapi_auth_request *request; + pool_t pool; + + pool = pool_alloconly_create("gssapi_auth_request", 512); + request = p_new(pool, struct gssapi_auth_request, 1); + request->pool = pool; + + request->gss_ctx = GSS_C_NO_CONTEXT; + + request->auth_request.pool = pool; + return &request->auth_request; +} + +static OM_uint32 obtain_service_credentials(struct auth_request *request, gss_cred_id_t *ret) +{ + OM_uint32 major_status, minor_status; + string_t *principal_name; + gss_buffer_desc inbuf; + gss_name_t gss_principal; + + principal_name = t_str_new(40); + str_append(principal_name, t_str_lcase(request->service)); + str_append(principal_name, "@"); + str_append(principal_name, my_hostname); + + auth_request_log_info(request, "gssapi", + "Obtaining credentials for %s", str_c(principal_name)); + + inbuf.length = str_len(principal_name); + inbuf.value = (void*) str_c(principal_name); + + major_status = gss_import_name(&minor_status, &inbuf, + GSS_C_NT_HOSTBASED_SERVICE, &gss_principal); + + str_free(principal_name); + + if (GSS_ERROR(major_status)) { + auth_request_log_gss_error(request, major_status, GSS_C_GSS_CODE, + "importing principal name"); + return major_status; + } + + major_status = gss_acquire_cred(&minor_status, gss_principal, 0, + GSS_C_NULL_OID_SET, GSS_C_ACCEPT, ret, NULL, NULL); + + if (GSS_ERROR(major_status)) { + auth_request_log_gss_error(request, major_status, GSS_C_GSS_CODE, + "acquiring service credentials"); + auth_request_log_gss_error(request, minor_status, GSS_C_MECH_CODE, + "acquiring service credentials"); + return major_status; + } + + gss_release_name(&minor_status, gss_principal); + + return major_status; +} + +static void gssapi_sec_context(struct gssapi_auth_request *request, + gss_buffer_desc inbuf) +{ + OM_uint32 major_status, minor_status; + gss_buffer_desc outbuf; + + major_status = gss_accept_sec_context ( + &minor_status, + &request->gss_ctx, + request->service_cred, + &inbuf, + GSS_C_NO_CHANNEL_BINDINGS, + &request->src_name, + NULL, /* mech_type */ + &outbuf, + NULL, /* ret_flags */ + NULL, /* time_rec */ + NULL /* delegated_cred_handle */ + ); + + if (GSS_ERROR(major_status)) { + auth_request_log_gss_error(&request->auth_request, major_status, GSS_C_GSS_CODE, + "processing incoming data"); + auth_request_log_gss_error(&request->auth_request, minor_status, GSS_C_MECH_CODE, + "processing incoming data"); + + auth_request_fail(&request->auth_request); + return; + } + + if (major_status == GSS_S_COMPLETE) { + request->sasl_gssapi_state = GSS_STATE_WRAP; + auth_request_log_info(&request->auth_request, "gssapi", + "security context state completed."); + } else { + auth_request_log_info(&request->auth_request, "gssapi", + "Processed incoming packet correctly, waiting for another."); + } + + request->auth_request.callback(&request->auth_request, + AUTH_CLIENT_RESULT_CONTINUE, + outbuf.value, outbuf.length); + + major_status = gss_release_buffer(&minor_status, &outbuf); +} + +static void gssapi_wrap(struct gssapi_auth_request *request, + gss_buffer_desc inbuf) +{ + OM_uint32 major_status, minor_status; + gss_buffer_desc outbuf; + char ret[4]; + + /* The clients return data should be empty here */ + + ret[0] = 0x01; /* Only authentication, no integrity or confidentiality protection (yet?) */ + ret[1] = 0xFF; + ret[2] = 0xFF; + ret[3] = 0xFF; + + inbuf.length = 4; + inbuf.value = ret; + + major_status = gss_wrap(&minor_status, request->gss_ctx, 0, + GSS_C_QOP_DEFAULT, + &inbuf, NULL, &outbuf); + + if (GSS_ERROR(major_status)) { + auth_request_log_gss_error(&request->auth_request, major_status, GSS_C_GSS_CODE, + "sending security layer negotiation"); + auth_request_log_gss_error(&request->auth_request, minor_status, GSS_C_MECH_CODE, + "sending security layer negotiation"); + auth_request_fail(&request->auth_request); + return; + } + + auth_request_log_info(&request->auth_request, "gssapi", + "Negotiated security layer"); + + request->auth_request.callback(&request->auth_request, + AUTH_CLIENT_RESULT_CONTINUE, + outbuf.value, outbuf.length); + + major_status = gss_release_buffer(&minor_status, &outbuf); + + request->sasl_gssapi_state = GSS_STATE_UNWRAP; +} + +static void gssapi_unwrap(struct gssapi_auth_request *request, + gss_buffer_desc inbuf) +{ + OM_uint32 major_status, minor_status; + gss_buffer_desc outbuf; + + major_status = gss_unwrap(&minor_status, request->gss_ctx, + &inbuf, &outbuf, NULL, NULL); + + if (GSS_ERROR(major_status)) { + auth_request_log_gss_error(&request->auth_request, major_status, GSS_C_GSS_CODE, + "final negotiation: gss_unwrap"); + auth_request_fail(&request->auth_request); + return; + } + + if (outbuf.length <= 4) { + auth_request_log_error(&request->auth_request, "gssapi", + "Invalid response length"); + auth_request_fail(&request->auth_request); + return; + } + + request->auth_request.user = p_strndup(request->auth_request.pool, + ((unsigned char*) outbuf.value)+4, + outbuf.length-4); + + auth_request_success(&request->auth_request, NULL, 0); +} + +static void +mech_gssapi_auth_continue(struct auth_request *request, + const unsigned char *data, size_t data_size) +{ + struct gssapi_auth_request *gssapi_request = + (struct gssapi_auth_request *)request; + gss_buffer_desc inbuf; + + inbuf.value = (char*) data; + inbuf.length = data_size; + + switch (gssapi_request->sasl_gssapi_state) { + case GSS_STATE_SEC_CONTEXT: gssapi_sec_context(gssapi_request, inbuf); break; + case GSS_STATE_WRAP: gssapi_wrap(gssapi_request, inbuf); break; + case GSS_STATE_UNWRAP: gssapi_unwrap(gssapi_request, inbuf); break; + } +} + +static void +mech_gssapi_auth_initial(struct auth_request *request, + const unsigned char *data, size_t data_size) +{ + OM_uint32 major_status; + struct gssapi_auth_request *gssapi_request = + (struct gssapi_auth_request *)request; + + major_status = obtain_service_credentials(request, &gssapi_request->service_cred); + + if (GSS_ERROR(major_status)) { + auth_request_internal_failure(request); + return; + } + gssapi_request->src_name = GSS_C_NO_NAME; + + gssapi_request->sasl_gssapi_state = GSS_STATE_SEC_CONTEXT; + + if (data_size == 0) { + /* The client should go first */ + request->callback(request, + AUTH_CLIENT_RESULT_CONTINUE, + NULL, 0); + } else { + mech_gssapi_auth_continue(request, data, data_size); + } +} + + +static void +mech_gssapi_auth_free(struct auth_request *request) +{ + OM_uint32 major_status, minor_status; + struct gssapi_auth_request *gssapi_request = + (struct gssapi_auth_request *)request; + + major_status = gss_delete_sec_context(&minor_status, + &gssapi_request->gss_ctx, + GSS_C_NO_BUFFER); + + major_status = gss_release_cred(&minor_status, &gssapi_request->service_cred); + + pool_unref(request->pool); +} + +const struct mech_module mech_gssapi = { + "GSSAPI", + + MEMBER(flags) 0, + + MEMBER(need_passdb) FALSE, + MEMBER(passdb_need_plain) FALSE, + MEMBER(passdb_need_credentials) FALSE, + + mech_gssapi_auth_new, + mech_gssapi_auth_initial, + mech_gssapi_auth_continue, + mech_gssapi_auth_free +}; + +#endif Index: AUTHORS =================================================================== RCS file: /home/cvs/dovecot/AUTHORS,v retrieving revision 1.11 diff -u -r1.11 AUTHORS --- AUTHORS 19 Aug 2004 03:56:01 -0000 1.11 +++ AUTHORS 19 Oct 2005 08:38:49 -0000 @@ -12,6 +12,8 @@ Joshua Goodall <joshua(a)roughtrade.net> (src/auth/password-scheme-cram-md5.c, src/util/dovecotpw.c) +Jelmer Vernooij <jelmer(a)samba.org> (src/auth/mech-gssapi.c) + This product includes software developed by Computing Services at Carnegie Mellon University (http://www.cmu.edu/computing/) (src/lib/base64.c, src/lib/mkgmtime.c)

3 10

[Dovecot] "passdb" userdb
by Thomas Hummel 20 Oct '05

20 Oct '05

Hello Timo, How exactly would translate the "passdb" userdb example which is in the Wiki for SQL auth with LDAP auth, both in dovecot.conf and dovecot-ldap.conf ? -- Thomas Hummel | Institut Pasteur <hummel(a)pasteur.fr> | Pôle informatique - systèmes et réseau

2 3

[Dovecot] Large IMAP operations tend to timeout and cause problems?
by Alen Salamun 20 Oct '05

20 Oct '05

Hello all! I have moved from Courier-IMAP to Dovecot some month ago. It is quite stable on everyday use (1.0alpha4) but it has constant problems with large IMAP/SSL operations. We use Maildir format. For example if I select 400 messages, mark them deleted and use "purge command" in Thunderbird (to actually delete them) TB starts to do something and runs and runs and runs....Then I get script timed out errror and I have to restart TB. That never happened with Courier-Imap. Same thing happens for example moving 1000msgs to another folder or something like that. Another thing is still that from time to time dovecot indexes get corrupted and users can't access some folders. Then I have to delete dovecot* in that Maildir folder and it works again. Any thoughts on that please? BR, Alen

4 4

[Dovecot] Alpha1..2.. and 3 with Tru64
by Alfonso Sparano 20 Oct '05

20 Oct '05

Hi all, I've found a little problem to compile dovecot on a tru64 os v5.1. The problem is the lack of the "inttypes.h" into the included header in the project. Without this include the make process will fail because it can't find the uint32 type. So is sufficient to add the line '#include <inttypes.h>' in the src/lib/lib.h of the tgz distribution package. Alfonso Sparano

3 2

[Dovecot] passwd and virtual users
by Erick Perez 20 Oct '05

20 Oct '05

Hi, im runnign dovecot 0.99.14 with standard pop3 auth and a default .conf file. Everything works fine. But now I need to enable virtual users for several domains in the same server while keeping the local auth. my postfix is already working for the virtual domains. What do i need to modify to enable /etc/passwd auth (already done) and virtual domains auth? in the virtual part, i have no idea. Thanks, -- ------------------------------------------- Erick Perez

1 0

[Dovecot] Failed authentication to a mysql database (bug or PEBKAC?)
by jigen 19 Oct '05

19 Oct '05

Hi, dovecot has a little crazy behaviour connecting to a mysql db: if you specify "127.0.0.1" as host instead of "localhost" it seems to work, also with a password. BUT, if you assign host=localhost without a password, it works too (as Ger Visschers says).... One more question: how I can specify more different mysql-db conteining different users? I try in the following way: passdb sql { args = /etc/dovecot/dovecot-mysql_django.conf args = /etc/dovecot/dovecot-mysql_debord.conf } and also: passdb sql { args = /etc/dovecot/dovecot-mysql_debord.conf } passdb sql { args = /etc/dovecot/dovecot-mysql_django.conf } but it always seems to remember only the last args value and it tries to connect only one db... bye jigen -- jigen <jigen(a)metalabs.org> MeTA~LAbS

3 2

[Dovecot] Message not found errors
by Andrew Hutchings 19 Oct '05

19 Oct '05

Hi, I'm getting a very small amount of users getting message not found errors while downloading mail via POP. By the time they inform me and I switch on rawloging for them it works again. Any ideas where this is going wrong? Or at least a way I can diagnose it? It seems to have been happening since Alpha 1. Currently using pre-release of Alpha4. Regards Andrew -- Andrew Hutchings (A-Wing) - Linux Guru Netserve Consultants - http://www.domaincity.co.uk/ Linux CDs and DVDs - http://www.linuxiso.co.uk/ Random quote 192: Geeks like learning new things, and when they pop out at the end of the process they're entirely brainwashed. - The way that MicroSoft's trainers view technical staff.

1 1

[Dovecot] 1 user has random pam auth issues
by Obantec Support 19 Oct '05

19 Oct '05

Hi Dovecot 1.0 stable on FC3 i see this in my logs from 1 user Oct 19 07:20:36 proteus2a dovecot(pam_unix)[2937]: authentication failure; logname= uid=0 euid=0 tty= ruser= rhost=1.2.3.4 user=testuser IP & user changed by me. at other times he has no issues. no other users are reporting this. could it be his ADSL is flaky or is there another scenario. Mark

1 0

[Dovecot] Pocket Outlook weirdness
by Vadim Zaliva 19 Oct '05

19 Oct '05

Hi! I am trying to access my IMAP server running dovecot from my Pocket PC running PocketOutlook. I observe very strange behavior: it starts to fetch messages from INBOX and shows list them on the screen as it fetches, then all messages disappear from the screen and it says "fetching folders". After the end of update operation it shows me empty list of messages. Have anybody have seen such problem? In general, are there reports of successful pocket outlook + dovecot users? Any suggestions are appreciated! I really want to make this thing work. Sincerely, Vadim

1 0

[Dovecot] v. minor bug alpha4pre
by Andrew Hutchings 19 Oct '05

19 Oct '05

Hi, When upgrading to Alpha4pre I also changed UIDL format from %08Xv%08Xu to %08Xu%08Xv to be in line with future dovecot default. This caused the following error to happen on about 1% of mailboxes: file ostream-file.c: line 370 (stream_send_io): assertion failed: (fstream->io != NULL) Deleting dovecot-uidlist and indexes fixes this so its more of an FYI really. I always delete indexes on an upgrade anyway so I'm pretty sure interpretation of the uidlist file if the problem. Regards Andrew -- Andrew Hutchings (A-Wing) - Linux Guru Netserve Consultants - http://www.domaincity.co.uk/ Linux CDs and DVDs - http://www.linuxiso.co.uk/ Random quote 3: "We are MicroSoft. You will be assimilated. Resistance is futile." - Unknown

2 2

[Dovecot] Moving old files
by Jon 19 Oct '05

19 Oct '05

Hi, I wish to automatically remove mail files not accessed for some time. I have done this in the file system and it works fine although it is a bit slow when the mail client access the mailbox after changes. Are there any way of having dovecot moving the files so that index and subscriptions are kept more same? Can one use Dovecot from the command line? Best Regards - Jon

2 1

[Dovecot] POP Question
by Marc Perkel 18 Oct '05

18 Oct '05

After upgrading to Alpha 4 I have two people complaining about a POP problem. Aparently they are getting their email sent to them over and over. They have it set to "leave messages on server" but apparently whatever keeps track of that is broken. So - how is it determined with POP what is new and what is read?

4 4

[Dovecot] qpoppers XUIDL
by Dominik Werder 18 Oct '05

18 Oct '05

Hello, does anybody know how to make XUIDLs compatible to qpopper? I'm migrating from qpopper and one of my test-migration-accounts leaves the mail on the server. As soon as I switch to dovecot it downloads the mails again and again.. bye! Dominik

2 2

[Dovecot] Numpty question about EXISTS...
by Steve [Dovecot] 18 Oct '05

18 Oct '05

I'm fiddling with Ruby and its IMAP class. I'm trying to write something which (at this stage) can be thought of as a variant on xbiff which doesn't need poll the server to establish the presence of new mail... I'd like to establish a notification when the contents of a folder changes... which is likely to be when a different IMAP client moves a message into a new folder. I've been lead to believe that I can use the "EXISTS" response to trigger the 'new message present in IMAP folder" event in my program... but I don't seem to receive them when I would expect to when connected to my Dovecot server. I get one "EXISTS" message when I call "select" - but that's it - it doesn't seem to notice when another client moves messages in/out of the folder. Are my assumptions about IMAP incorrect - i.e. must I still poll? Can Dovecot be configured to send EXIST responses (or any other form of notification) when messages are moved into a folder? Any hints appreciated. Steve

3 3

[Dovecot] Debian - upgrade done, plain text auth fails
by Diederik de Vries 18 Oct '05

18 Oct '05

Hi there, I have a problem concerning authentication of dovecot. Yesterday I did a apt-get update on my Debian Testing machine, which had a new version of Dovecot (common/imap/pop3). It now runs 1.0alpha3 Local authentication works fine (Squirrelmail (IMAP), and local 110 connections work). However: pop3 from outside 127.0.0.1 plain barfs when entering the `u` for `user`. What the ....?: === +OK Dovecot ready. u-ERR invalid POP3 command De verbinding met de host is verbroken. (Connection with host is lost) == However, on localhost: === diedx:/etc/dovecot# telnet localhost 110 Trying 127.0.0.1... Connected to diederik.nl. Escape character is '^]'. +OK Dovecot ready. user died +OK pass nothere +OK Logged in. list +OK 208 messages: 1 1679750 2 22179 3 2116 === Works like a charm. I had this problem earlier, so then I switched the disable_plaintext_auth = no. This does not seem to work at this moment. Anyone? Config attached. Thanks! Diederik de Vries Rotterdam, The Netherlands ## Dovecot 1.0 configuration file # '#' character and everything after it is treated as comments. Extra spaces # and tabs are ignored. If you want to use either of these explicitly, put the # value inside quotes, eg.: key = "# char and trailing whitespace " # Default values are shown after each value, it's not required to uncomment # any of the lines. Exception to this are paths, they're just examples # with real defaults being based on configure options. The paths listed here # are for configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var # --with-ssldir=/etc/ssl # Base directory where to store runtime data. #base_dir = /var/run/dovecot/ # Protocols we want to be serving: # imap imaps pop3 pop3s #protocols = imap imaps protocols = imap imaps pop3 pop3s # IP or host address where to listen in for connections. It's not currently # possible to specify multiple addresses. "*" listens in all IPv4 interfaces. # "[::]" listens in all IPv6 interfaces, but may also listen in all IPv4 # interfaces depending on the operating system. If you want to specify ports # for each service, you will need to configure these settings inside the # protocol imap/pop3 { ... } section, so you can specify different ports # for IMAP/POP3. listen = * # IP or host address where to listen in for SSL connections. Defaults # to above if not specified. #ssl_listen = # Disable SSL/TLS support. #ssl_disable = no # PEM encoded X.509 SSL/TLS certificate and private key. They're opened before # dropping root privileges, so keep the key file unreadable by anyone but # root. #ssl_cert_file = /etc/ssl/certs/dovecot.pem #ssl_key_file = /etc/ssl/private/dovecot.pem # File containing trusted SSL certificate authorities. Usually not needed. #ssl_ca_file = # Request client to send a certificate. #ssl_verify_client_cert = no # SSL parameter file. Master process generates this file for login processes. # It contains Diffie Hellman and RSA parameters. #ssl_parameters_file = /var/run/dovecot/ssl-parameters.dat # How often to regenerate the SSL parameters file. Generation is quite CPU # intensive operation. The value is in hours, 0 disables regeneration # entirely. #ssl_parameters_regenerate = 24 # SSL ciphers to use #ssl_cipher_list = all:!LOW # Disable LOGIN command and all other plaintext authentications unless # SSL/TLS is used (LOGINDISABLED capability). Note that 127.*.*.* and # IPv6 ::1 addresses are considered secure, this setting has no effect if # you connect from those addresses. disable_plaintext_auth = no # Use this logfile instead of syslog(). /dev/stderr can be used if you want to # use stderr for logging (ONLY /dev/stderr - otherwise it is closed). #log_path = # For informational messages, use this logfile instead of the default #info_log_path = # Prefix for each line written to log file. % codes are in strftime(3) # format. #log_timestamp = "%b %d %H:%M:%S " ## ## Login processes ## # Directory where authentication process places authentication UNIX sockets # which login needs to be able to connect to. The sockets are created when # running as root, so you don't have to worry about permissions. Note that # everything in this directory is deleted when Dovecot is started. #login_dir = /var/run/dovecot/login # chroot login process to the login_dir. Only reason not to do this is if you # wish to run the whole Dovecot without roots. # http://wiki.dovecot.org/Rootless #login_chroot = yes # User to use for the login process. Create a completely new user for this, # and don't use it anywhere else. The user must also belong to a group where # only it has access, it's used to control access for authentication process. # Note that this user is NOT used to access mails. # http://wiki.dovecot.org/UserIds #login_user = dovecot # Set max. process size in megabytes. If you don't use # login_process_per_connection you might need to grow this. #login_process_size = 32 # Should each login be processed in it's own process (yes), or should one # login process be allowed to process multiple connections (no)? Yes is more # secure, espcially with SSL/TLS enabled. No is faster since there's no need # to create processes all the time. #login_process_per_connection = yes # Number of login processes to create. If login_process_per_connection is # yes, this is the number of extra processes waiting for users to log in. #login_processes_count = 3 # Maximum number of extra login processes to create. The extra process count # usually stays at login_processes_count, but when multiple users start logging # in at the same time more extra processes are created. To prevent fork-bombing # we check only once in a second if new processes should be created - if all # of them are used at the time, we double their amount until limit set by this # setting is reached. This setting is used only if login_process_per_use is yes. #login_max_processes_count = 128 # Maximum number of connections allowed in login state. When this limit is # reached, the oldest connections are dropped. If login_process_per_connection # is no, this is a per-process value, so the absolute maximum number of users # logging in actually login_processes_count * max_logging_users. #login_max_logging_users = 256 # Greeting message for clients. #login_greeting = Dovecot ready. # Space-separated list of elements we want to log. The elements which have # a non-empty variable value are joined together to form a comma-separated # string. #login_log_format_elements = user=<%u> method=%m rip=%r lip=%l %c # Login log format. %$ contains login_log_format_elements string, %s contains # the data we want to log. #login_log_format = %$: %s ## ## Mail processes ## # Maximum number of running mail processes. When this limit is reached, # new users aren't allowed to log in. #max_mail_processes = 1024 # Show more verbose process titles (in ps). Currently shows user name and # IP address. Useful for seeing who are actually using the IMAP processes # (eg. shared mailboxes or if same uid is used for multiple accounts). #verbose_proctitle = no # Show protocol level SSL errors. #verbose_ssl = no # Valid UID range for users, defaults to 500 and above. This is mostly # to make sure that users can't log in as daemons or other system users. # Note that denying root logins is hardcoded to dovecot binary and can't # be done even if first_valid_uid is set to 0. #first_valid_uid = 500 #last_valid_uid = 0 # Valid GID range for users, defaults to non-root/wheel. Users having # non-valid GID as primary group ID aren't allowed to log in. If user # belongs to supplementary groups with non-valid GIDs, those groups are # not set. #first_valid_gid = 1 #last_valid_gid = 0 # Grant access to these extra groups for mail processes. Typical use would be # to give "mail" group write access to /var/mail to be able to create dotlocks. #mail_extra_groups = # ':' separated list of directories under which chrooting is allowed for mail # processes (ie. /var/mail will allow chrooting to /var/mail/foo/bar too). # This setting doesn't affect login_chroot or auth_chroot variables. # WARNING: Never add directories here which local users can modify, that # may lead to root exploit. Usually this should be done only if you don't # allow shell access for users. See # /usr/share/doc/dovecot-common/configuration.txt for more information. #valid_chroot_dirs = # Default chroot directory for mail processes. This can be overridden for # specific users in user database by giving /./ in user's home directory # (eg. /home/./user chroots into /home). Note that usually there is no real # need to do chrooting, Dovecot doesn't allow users to access files outside # their mail directory anyway. #mail_chroot = # Enable mail process debugging. This can help you figure out why Dovecot # isn't finding your mails. #mail_debug = no # Default MAIL environment to use when it's not set. By leaving this empty # dovecot tries to do some automatic detection as described in # /usr/share/doc/dovecot-common/mail-storages.txt. # There's a few special variables you can use, eg.: # # %u - username # %n - user part in user@domain, same as %u if there's no domain # %d - domain part in user@domain, empty if there's no domain # %h - home directory # # See /usr/share/doc/dovecot-common/variables.txt for full list. Some examples: # # default_mail_env = maildir:/var/mail/%1u/%u/Maildir # default_mail_env = mbox:~/mail/:INBOX=/var/mail/%u # default_mail_env = mbox:/var/mail/%d/%n/:INDEX=/var/indexes/%d/%n # #default_mail_env = # If you need to set multiple mailbox locations or want to change default # namespace settings, you can do it by defining namespace sections: # # You can have private, shared and public namespaces. The only difference # between them is how Dovecot announces them to client via NAMESPACE # extension. Shared namespaces are meant for user-owned mailboxes which are # shared to other users, while public namespaces are for more globally # accessible mailboxes. # # REMEMBER: If you add any namespaces, the default namespace must be added # explicitly, ie. default_mail_env does nothing unless you have a namespace # without a location setting. Default namespace is simply done by having a # namespace with empty prefix. #namespace private { # Hierarchy separator to use. You should use the same separator for all # namespaces or some clients get confused. '/' is usually a good one. #separator = / # Prefix required to access this namespace. This needs to be different for # all namespaces. For example "Public/". #prefix = # Physical location of the mailbox. This is in same format as # default_mail_env, which is also the default for it. #location = # There can be only one INBOX, and this setting defines which namespace # has it. #inbox = yes # If namespace is hidden, it's not advertised to clients via NAMESPACE # extension or shown in LIST replies. This is mostly useful when converting # from another server with different namespaces which you want to depricate # but still keep working. For example you can create hidden namespaces with # prefixes "~/mail/", "~%u/mail/" and "mail/". #hidden = yes #} # Space-separated list of fields to initially save into cache file. Currently # these fields are allowed: # # flags, date.sent, date.received, size.virtual, size.physical # mime.parts, imap.body, imap.bodystructure # # Different IMAP clients work in different ways, so they benefit from # different cached fields. Some do not benefit from them at all. Caching more # than necessary generates useless disk I/O, so you don't want to do that # either. # # Dovecot attempts to automatically figure out what client wants and it keeps # only that. However the first few times a mailbox is opened, Dovecot hasn't # yet figured out what client needs, so it may not perform optimally. If you # know what fields the majority of your clients need, it may be useful to set # these fields by hand. If client doesn't actually use them, Dovecot will # eventually drop them. # # Usually you should just leave this field alone. The potential benefits are # typically unnoticeable. #mail_cache_fields = # Space-separated list of fields that Dovecot should never save to cache file. # Useful if you want to save disk space at the cost of more I/O when the fields # needed. #mail_never_cache_fields = # Like mailbox_check_interval, but used for IDLE command. #mailbox_idle_check_interval = 30 # Allow full filesystem access to clients. There's no access checks other than # what the operating system does for the active UID/GID. It works with both # maildir and mboxes, allowing you to prefix mailboxes names with eg. /path/ # or ~user/. #mail_full_filesystem_access = no # Maximum allowed length for mail keyword name. It's only forced when trying # to create new keywords. #mail_max_keyword_length = 50 # Save mails with CR+LF instead of plain LF. This makes sending those mails # take less CPU, especially with sendfile() syscall with Linux and FreeBSD. # But it also creates a bit more disk I/O which may just make it slower. #mail_save_crlf = no # Use mmap() instead of read() to read mail files. read() seems to be a bit # faster with my Linux/x86 and it's better with NFS, so that's the default. # Note that OpenBSD 3.3 and older don't work right with mail_read_mmaped = yes. #mail_read_mmaped = no # Don't use mmap() at all. This is required if you store indexes in remote # filesystems (NFS or clustered filesystem). #mmap_disable = no # Don't write() to mmaped files. This is required for some operating systems # which use separate caches for them, such as OpenBSD. #mmap_no_write = no # Locking method for index files. Alternatives are fcntl, flock and dotlock. # Dotlocking uses some tricks which may create more disk I/O than other locking # methods. #lock_method = fcntl # By default LIST command returns all entries in maildir beginning with dot. # Enabling this option makes Dovecot return only entries which are directories. # This is done by stat()ing each entry, so it causes more disk I/O. # (For systems setting struct dirent->d_type, this check is free and it's # done always regardless of this setting) #maildir_stat_dirs = no # Copy mail to another folders using hard links. This is much faster than # actually copying the file. This is problematic only if something modifies # the mail in one folder but doesn't want it modified in the others. I don't # know any MUA which would modify mail files directly. IMAP protocol also # requires that the mails don't change, so it would be problematic in any case. # If you care about performance, enable it. #maildir_copy_with_hardlinks = no # Which locking methods to use for locking mbox. There's four available: # dotlock: Create <mailbox>.lock file. This is the oldest and most NFS-safe # solution. If you want to use /var/mail/ like directory, the users # will need write access to that directory. # fcntl : Use this if possible. Works with NFS too if lockd is used. # flock : May not exist in all systems. Doesn't work with NFS. # lockf : May not exist in all systems. Doesn't work with NFS. # # You can use multiple locking methods; if you do the order they're declared # in is important to avoid deadlocks if other MTAs/MUAs are using multiple # locking methods as well. Some operating systems don't allow using some of # them simultaneously. #mbox_read_locks = fcntl #mbox_write_locks = dotlock fcntl # Maximum time in seconds to wait for lock (all of them) before aborting. #mbox_lock_timeout = 300 # If dotlock exists but the mailbox isn't modified in any way, override the # lock file after this many seconds. #mbox_dotlock_change_timeout = 30 # When mbox changes unexpectedly we have to fully read it to find out what # changed. If the mbox is large this can take a long time. Since the change # is usually just a newly appended mail, it'd be faster to simply read the # new mails. If this setting is enabled, Dovecot does this but still safely # fallbacks to re-reading the whole mbox file whenever something in mbox isn't # how it's expected to be. The only real downside to this setting is that if # some other MUA changes message flags, Dovecot doesn't notice it immediately. # Note that a full sync is done with SELECT, EXAMINE, EXPUNGE and CHECK # commands. #mbox_dirty_syncs = yes # Like mbox_dirty_syncs, but don't do full syncs even with SELECT, EXAMINE, # EXPUNGE or CHECK commands. If this is set, mbox_dirty_syncs is ignored. #mbox_very_dirty_syncs = no # Delay writing mbox headers until doing a full write sync (EXPUNGE and CHECK # commands and when closing the mailbox). This is especially useful for POP3 # where clients often delete all mails. The downside is that our changes # aren't immediately visible to other MUAs. #mbox_lazy_writes = yes # umask to use for mail files and directories #umask = 0077 # Drop all privileges before exec()ing the mail process. This is mostly # meant for debugging, otherwise you don't get core dumps. It could be a small # security risk if you use single UID for multiple users, as the users could # ptrace() each others processes then. #mail_drop_priv_before_exec = no # Set max. process size in megabytes. Most of the memory goes to mmap()ing # files, so it shouldn't harm much even if this limit is set pretty high. #mail_process_size = 256 # Log prefix for mail processes. # See /usr/share/doc/dovecot-common/variables.txt for list of possible # variables you can use. #mail_log_prefix = "%Us(%u): " ## ## IMAP specific settings ## protocol imap { # Login executable location. #login_executable = /usr/lib/dovecot/imap-login # IMAP executable location #mail_executable = /usr/lib/dovecot/imap # This would write rawlogs into ~/dovecot.rawlog/ directory: #mail_executable = /usr/lib/dovecot/rawlog /usr/lib/dovecot/imap # Maximum IMAP command line length in bytes. Some clients generate very long # command lines with huge mailboxes, so you may need to raise this if you get # "Too long argument" or "IMAP command line too large" errors often. #imap_max_line_length = 65536 # Support for dynamically loadable modules. #mail_use_modules = no #mail_modules = /usr/lib/dovecot/imap # Send IMAP capabilities in greeting message. This makes it unnecessary for # clients to request it with CAPABILITY command, so it saves one round-trip. # Many clients however don't understand it and ask the CAPABILITY anyway. #login_greeting_capability = no # Workarounds for various client bugs: # delay-newmail: # Send EXISTS/RECENT new mail notifications only when replying to NOOP # and CHECK commands. Some clients ignore them otherwise, for example # OSX Mail. Outlook Express breaks more badly though, without this it # may show user "Message no longer in server" errors. Note that OE6 still # breaks even with this workaround if synchronization is set to # "Headers Only". # outlook-idle: # Outlook and Outlook Express never abort IDLE command, so if no mail # arrives in half a hour, Dovecot closes the connection. This is still # fine, except Outlook doesn't connect back so you don't see if new mail # arrives. # netscape-eoh: # Netscape 4.x breaks if message headers don't end with the empty "end of # headers" line. Normally all messages have this, but setting this # workaround makes sure that Netscape never breaks by adding the line if # it doesn't exist. This is done only for FETCH BODY[HEADER.FIELDS..] # commands. Note that RFC says this shouldn't be done. # tb-extra-mailbox-sep: # With mbox storage a mailbox can contain either mails or submailboxes, # but not both. Thunderbird separates these two by forcing server to # accept '/' suffix in mailbox names in subscriptions list. #imap_client_workarounds = outlook-idle } ## ## POP3 specific settings ## protocol pop3 { # Login executable location. #login_executable = /usr/lib/dovecot/pop3-login # POP3 executable location #mail_executable = /usr/lib/dovecot/pop3 # Don't try to set mails non-recent or seen with POP3 sessions. This is # mostly intended to reduce disk I/O. With maildir it doesn't move files # from new/ to cur/, with mbox it doesn't write Status-header. #pop3_no_flag_updates = no # Support LAST command which exists in old POP3 specs, but has been removed # from new ones. Some clients still wish to use this though. Enabling this # makes RSET command clear all \Seen flags from messages. #pop3_enable_last = no # POP3 UIDL format to use. You can use following variables: # # %v - Mailbox UIDVALIDITY # %u - Mail UID # %m - MD5 sum of the mailbox headers in hex (mbox only) # %f - filename (maildir only) # # If you want UIDL compatibility with other POP3 servers, use: # UW's ipop3d : %08Xv%08Xu # Courier version 0 : %f # Courier version 1 : %u # Courier version 2 : %v-%u # Cyrus (<= 2.1.3) : %u # Cyrus (>= 2.1.4) : %v.%u # # Note that Outlook 2003 seems to have problems with %v.%u format which is # Dovecot's default, so if you're building a new server it would be a good # idea to change this. %08Xu%08Xv should be pretty fail-safe. #pop3_uidl_format = %v.%u # POP3 logout format string: # %t - number of TOP commands # %T - number of bytes sent to client as a result of TOP command # %r - number of RETR commands # %R - number of bytes sent to client as a result of RETR command # %d - number of deleted messages # %m - number of messages (before deletion) # %s - mailbox size in bytes (before deletion) #pop3_logout_format = top=%t/%T, retr=%r/%R, del=%d/%m, size=%s # Support for dynamically loadable modules. #mail_use_modules = no #mail_modules = /usr/lib/dovecot/pop3 # Workarounds for various client bugs: # outlook-no-nuls: # Outlook and Outlook Express hang if mails contain NUL characters. # This setting replaces them with 0x80 character. # oe-ns-eoh: # Outlook Express and Netscape Mail breaks if end of headers-line is # missing. This option simply sends it if it's missing. #pop3_client_workarounds = } ## ## Authentication processes ## # Executable location #auth_executable = /usr/lib/dovecot/dovecot-auth # Set max. process size in megabytes. #auth_process_size = 256 # Authentication cache size in kilobytes. #auth_cache_size = 0 # Time to live in seconds for cached data. After this many seconds a cached # record is forced out of cache. #auth_cache_ttl = 3600 # Space separated list of realms for SASL authentication mechanisms that need # them. You can leave it empty if you don't want to support multiple realms. # Many clients simply use the first one listed here, so keep the default realm # first. #auth_realms = # Default realm/domain to use if none was specified. This is used for both # SASL realms and appending @domain to username in plaintext logins. #auth_default_realm = # List of allowed characters in username. If the user-given username contains # a character not listed in here, the login automatically fails. This is just # an extra check to make sure user can't exploit any potential quote escaping # vulnerabilities with SQL/LDAP databases. If you want to allow all characters, # set this value to empty. #auth_username_chars = abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@ # Username character translations before it's looked up from databases. The # value contains series of from -> to characters. For example "#@/@" means # that '#' and '/' characters are translated to '@'. #auth_username_translation = # Username to use for users logging in with ANONYMOUS SASL mechanism #auth_anonymous_username = anonymous # More verbose logging. Useful for figuring out why authentication isn't # working. auth_verbose = yes # Even more verbose logging for debugging purposes. Shows for example SQL # queries. auth_debug = yes # Maximum number of dovecot-auth worker processes. They're used to execute # blocking passdb and userdb queries (eg. MySQL and PAM). They're # automatically created and destroyed as needed. #auth_worker_max_count = 30 auth default { # Space separated list of wanted authentication mechanisms: # plain digest-md5 cram-md5 apop anonymous mechanisms = plain # # Password database is used to verify user's password (and nothing more). # You can have multiple passdbs and userdbs. This is useful if you want to # allow both system users (/etc/passwd) and virtual users to login without # duplicating the system users into virtual database. # # http://wiki.dovecot.org/Authentication # # PAM authentication. Preferred nowadays by most systems. # Note that PAM can only be used to verify if user's password is correct, # so it can't be used as userdb. If you don't want to use a separate user # database (passwd usually), you can use static userdb. passdb pam { # [-session] [<service name>] # # -session makes Dovecot open and immediately close PAM session. Some # PAM plugins need this to work. # # If service name is "*", it means the authenticating service name # is used, eg. pop3 or imap. #args = dovecot } # /etc/passwd or similar, using getpwnam() # In many systems nowadays this uses Name Service Switch, which is # configured in /etc/nsswitch.conf. #passdb passwd { #} # /etc/shadow or similiar, using getspnam(). Deprecated by PAM nowadays. #passdb shadow { #} # passwd-like file with specified location #passdb passwd-file { # Path for passwd-file #args = #} # checkpassword executable authentication # NOTE: You will probably want to use "userdb passdb" with this. #passdb checkpassword { # Path for checkpassword binary #args = #} # SQL database #passdb sql { # Path for SQL configuration file, see /etc/dovecot/dovecot-sql.conf for example #args = #} # LDAP database #passdb ldap { # Path for LDAP configuration file, see /etc/dovecot/dovecot-ldap.conf for example #args = #} # vpopmail authentication #passdb vpopmail { #} # # User database specifies where mails are located and what user/group IDs # own them. For single-UID configuration use "static". # # http://wiki.dovecot.org/Authentication # http://wiki.dovecot.org/VirtualUsers # # /etc/passwd or similar, using getpwnam() # In many systems nowadays this uses Name Service Switch, which is # configured in /etc/nsswitch.conf. userdb passwd { } # passwd-like file with specified location #userdb passwd-file { # Path for passwd-file #args = #} # static settings generated from template #userdb static { # Template for settings. Can return anything a userdb could normally # return, eg.: uid, gid, home, mail, nice # # A few examples: # # args = uid=500 gid=500 home=/var/mail/%u # args = uid=500 gid=500 home=/home/%u mail=mbox:/home/%u/mail nice=10 # #args = #} # SQL database #userdb sql { # Path for SQL configuration file, see /etc/dovecot/dovecot-sql.conf for example #args = #} # LDAP database #userdb ldap { # Path for LDAP configuration file, see /etc/dovecot/dovecot-ldap.conf for example #args = #} # vpopmail #userdb vpopmail { #} # "passdb" user database means that the passdb already provided the # needed information and there's no need to do a separate userdb lookup. # This can be made to work with SQL and LDAP databases. # http://wiki.dovecot.org/AuthSpecials userdb passdb { } # User to use for the process. This user needs access to only user and # password databases, nothing else. Only shadow and pam authentication # requires roots, so use something else if possible. Note that passwd # authentication with BSDs internally accesses shadow files, which also # requires roots. Note that this user is NOT used to access mails. # That user is specified by userdb above. user = root # Directory where to chroot the process. Most authentication backends don't # work if this is set, and there's no point chrooting if auth_user is root. # Note that valid_chroot_dirs isn't needed to use this setting. #chroot = # Number of authentication processes to create #count = 1 # Require a valid SSL client certificate or the authentication fails. #ssl_require_client_cert = no } # It's possible to export the authentication interface to other programs, # for example SMTP server which supports talking to Dovecot. Client socket # handles the actual authentication - you give it a username and password # and it returns OK or failure. So it's pretty safe to allow anyone access to # it. Master socket is used to a) query if given client was successfully # authenticated, b) userdb lookups. # listener sockets will be created by Dovecot's master process using the # settings given inside the auth section #auth default_with_listener { # mechanisms = plain # passdb passwd { # } # userdb pam { # } # socket listen { # master { # path = /var/run/dovecot-auth-master # # WARNING: Giving untrusted users access to master socket may be a # # security risk, don't give too wide permissions to it! # #mode = 0600 # # Default user/group is the one who started dovecot-auth (root) # #user = # #group = # } # client { # path = /var/run/dovecot-auth-client # mode = 0660 # } # } #} # connect sockets are assumed to be already running, Dovecot's master # process only tries to connect to them. They don't need any other settings # than path for the master socket, as the configuration is done elsewhere. # Note that the client sockets must exist in login_dir. #auth external { # socket connect { # master { # path = /var/run/dovecot-auth-master # } # } #}

2 4

[Dovecot] A Couple Assertion Failures
by Todd Burroughs 18 Oct '05

18 Oct '05

Here's a couple of assertion failures from CVS version as of Oct. 6. There's also a segfault but the core file was empty so I don't know if the log entries are much help. BTW, the searching speed using pine has dramatically improved, nice work! Todd ----------------------------------------- dovecot: Oct 12 12:04:28 Error: 20278 imap(username): file mail-index-sync-ext.c: line 155 (get_ext_header): assertion failed: (memcmp((char *)(ext_hdr + 1), ext->name, strlen(ext->name)) == 0) dovecot: Oct 12 12:04:28 Error: child 20278 (imap) killed with signal 6 (gdb) bt full #0 0xffffe410 in ?? () No symbol table info available. #1 0xbffff158 in ?? () No symbol table info available. #2 0x00000006 in ?? () No symbol table info available. #3 0x00004f36 in ?? () No symbol table info available. #4 0xb7ef1d41 in raise () from /lib/tls/libc.so.6 No symbol table info available. #5 0xb7ef3529 in abort () from /lib/tls/libc.so.6 No symbol table info available. #6 0x0809b23a in i_internal_panic_handler ( fmt=0x6 <Address 0x6 out of bounds>, args=0x4f36 <Address 0x4f36 out of bounds>) at failures.c:374 No locals. #7 0x0809b654 in i_panic ( format=0x80a886c "file %s: line %d (%s): assertion failed: (%s)") at failures.c:173 No locals. #8 0x0808d787 in get_ext_header (map=Variable "map" is not available. ) at mail-index-sync-ext.c:157 ext_hdr = Variable "ext_hdr" is not available. (gdb) bt #0 0xffffe410 in ?? () #1 0xbffff158 in ?? () #2 0x00000006 in ?? () #3 0x00004f36 in ?? () #4 0xb7ef1d41 in raise () from /lib/tls/libc.so.6 #5 0xb7ef3529 in abort () from /lib/tls/libc.so.6 #6 0x0809b23a in i_internal_panic_handler ( fmt=0x6 <Address 0x6 out of bounds>, args=0x4f36 <Address 0x4f36 out of bounds>) at failures.c:374 #7 0x0809b654 in i_panic ( format=0x80a886c "file %s: line %d (%s): assertion failed: (%s)") at failures.c:173 #8 0x0808d787 in get_ext_header (map=Variable "map" is not available. ) at mail-index-sync-ext.c:157 #9 0x0808db69 in sync_ext_reorder (map=0x80cd520, ext_id=1, old_size=2) at mail-index-sync-ext.c:273 #10 0x0808e32e in mail_index_sync_ext_intro (ctx=0xbffff590, u=0x80b6688) at mail-index-sync-ext.c:340 #11 0x0808eb60 in mail_index_sync_keywords (ctx=0xbffff590, hdr=0x0, rec=0x80c7a74) at mail-index-sync-keywords.c:107 #12 0x0808678b in mail_index_sync_record (ctx=0xbffff590, hdr=0x80c8764, data=0x80c7a74) at mail-index-sync-update.c:520 #13 0x08086cb6 in mail_index_sync_update_index (sync_ctx=0x80c7618, sync_only_external=0) at mail-index-sync-update.c:674 #14 0x08084cf3 in mail_index_sync_commit (ctx=0x80c7618) at mail-index-sync.c:629 #15 0x080708a9 in mbox_sync (mbox=0x80c5c00, flags=Variable "flags" is not available. ) at mbox-sync.c:1707 #16 0x08071589 in mbox_storage_sync_init (box=0x80c5c00, flags=MAILBOX_SYNC_FLAG_FULL_READ) at mbox-sync.c:1770 #17 0x0808f751 in mailbox_sync_init (box=0x0, flags=MAILBOX_SYNC_FLAG_FULL_READ) at mail-storage.c:336 #18 0x0805ee18 in imap_sync_nonselected (box=0x80c5c00, flags=MAILBOX_SYNC_FLAG_FULL_READ) at imap-sync.c:171 #19 0x08058236 in _cmd_select_full (cmd=0x80bfbf8, readonly=0) at cmd-select.c:39 #20 0x080583c1 in cmd_select (cmd=0x80bfbf8) at cmd-select.c:92 #21 0x08059a5b in _client_input (context=0x80bfbb8) at client.c:338 #22 0x080a0a7a in io_loop_handler_run (ioloop=0x80be9b0) at ioloop-poll.c:190 #23 0x0809fff9 in io_loop_run (ioloop=0x80be9b0) at ioloop.c:230 #24 0x08060996 in main (argc=1, argv=0xbffffa54, envp=0xbffffa5c) at main.c:232 (gdb) p (char *)(ext_hdr + 1) Variable "ext_hdr" is not available. (gdb) p *ext Variable "ext" is not available. ----------------------------------------------------- dovecot: Oct 09 20:43:20 Error: 18254 imap(username): file mail-index.c: line 856 (mail_index_sync_from_transactions): assertion failed: (hdr.log_file_int_offset == (*map)->hdr.log_file_int_offset) dovecot: Oct 09 20:43:21 Error: child 18254 (imap) killed with signal 6 (gdb) bt full #0 0xffffe410 in ?? () No symbol table info available. #1 0xbffff2a8 in ?? () No symbol table info available. #2 0x00000006 in ?? () No symbol table info available. #3 0x0000474e in ?? () No symbol table info available. #4 0xb7ef1d41 in raise () from /lib/tls/libc.so.6 No symbol table info available. #5 0xb7ef3529 in abort () from /lib/tls/libc.so.6 No symbol table info available. #6 0x0809b23a in i_internal_panic_handler ( fmt=0x6 <Address 0x6 out of bounds>, args=0x474e <Address 0x474e out of bounds>) at failures.c:374 No locals. #7 0x0809b654 in i_panic ( format=0x80a886c "file %s: line %d (%s): assertion failed: (%s)") at failures.c:173 No locals. #8 0x0807fd5d in mail_index_map (index=0x80c6000, force=135040256) at mail-index.c:837 map = (struct mail_index_map *) 0x80c7230 ret = Variable "ret" is not available. (gdb) bt #0 0xffffe410 in ?? () #1 0xbffff2a8 in ?? () #2 0x00000006 in ?? () #3 0x0000474e in ?? () #4 0xb7ef1d41 in raise () from /lib/tls/libc.so.6 #5 0xb7ef3529 in abort () from /lib/tls/libc.so.6 #6 0x0809b23a in i_internal_panic_handler ( fmt=0x6 <Address 0x6 out of bounds>, args=0x474e <Address 0x474e out of bounds>) at failures.c:374 #7 0x0809b654 in i_panic ( format=0x80a886c "file %s: line %d (%s): assertion failed: (%s)") at failures.c:173 #8 0x0807fd5d in mail_index_map (index=0x80c6000, force=135040256) at mail-index.c:837 #9 0x08085186 in mail_index_sync_begin (index=0x80c6000, ctx_r=0x0, view_r=0x0, log_file_seq=0, log_file_offset=Unhandled dwarf expression opcode 0x93 ) at mail-index-sync.c:336 #10 0x08070423 in mbox_sync (mbox=0x80c6c08, flags=Variable "flags" is not available. ) at mbox-sync.c:1599 #11 0x0806a101 in mbox_transaction_commit (_t=0x80c87f8, flags=Variable "flags" is not available. ) at mbox-transaction.c:56 #12 0x0808f913 in mailbox_transaction_commit (t=0x0, flags=0) at mail-storage.c:421 #13 0x0805f090 in imap_sync_deinit (ctx=0x80c79b0) at imap-sync.c:70 #14 0x0805f14c in cmd_sync_continue (cmd=0x80bfbf8) at imap-sync.c:184 #15 0x080567d0 in cmd_fetch_finish (ctx=Variable "ctx" is not available. ) at cmd-fetch.c:106 #16 0x08056a1b in cmd_fetch (cmd=0x80bfbf8) at cmd-fetch.c:176 #17 0x08059a5b in _client_input (context=0x80bfbb8) at client.c:338 #18 0x080a0a7a in io_loop_handler_run (ioloop=0x80be9b0) at ioloop-poll.c:190 #19 0x0809fff9 in io_loop_run (ioloop=0x80be9b0) at ioloop.c:230 #20 0x08060996 in main (argc=1, argv=0xbffffa54, envp=0xbffffa5c) at main.c:232 ------------------------------------- dovecot: Oct 17 14:16:00 Error: 29119 imap(username): Corrupted index file /mailhome/new/k/t/username/.imap/INBOX/dovecot.index: File too small dovecot: Oct 17 14:16:03 Error: 29119 imap(username): Corrupted index file /mailhome/new/k/t/username/mail/.imap/sent-mail/dovecot.index: File too small dovecot: Oct 17 14:16:03 Error: 29119 imap(username): Corrupted transaction log file /mailhome/new/k/t/username/mail/.imap/sent-mail/dovecot.index.log: hdr.size too large (2104) dovecot: Oct 17 14:16:05 Error: child 29119 (imap) killed with signal 11

1 0

[Dovecot] Permission denied but works anyway
by Bob Hall 17 Oct '05

17 Oct '05

I've just updated from 99.14 to 1.0.a3 on a FreeBSD box. Everything went fine, except for a bit of flakyness from Thunderbird. When first checking a mail box in Thunderbird (running on Win2k), I get a message saying that the command can't be carried out and the server answered "Permission denied". I click OK and everything works fine. As long as Thunderbird stays open, the message doesn't pop up again. It only happens when I first check the Inbox for a given account. No problems with Eudora on Win2k or mutt on FBSD. I've googled with various keywords but I can't find anything on this. I have an extremely vague recollection of seeing a post on this, but I can't find anything.

2 2

[Dovecot] verbose pop3 logging
by Ilo Lorusso 17 Oct '05

17 Oct '05

Hi Im new to dovecot and am looking for some options in the /etc/dovecot.conf to make dovecot a bit more verbose in terms pop3 usage, What ip a user is coming from? How many mails the user downloaded? Timing? Errors occurred while downloading mail?? Is this all possible with dovecot?

3 2

[Dovecot] Dovecot v1.0a3 on OpenBSD 3.7
by Jeff Simmons 17 Oct '05

17 Oct '05

I've been trying to get Dovecot 1.0a3 running on OpenBSD 3.7, with little luck. I'm getting the following: Oct 16 17:00:50 mailtest dovecot: pop3(testuser):open(/var/mail/.temp.mail.mailtest.com.7078.43c0f93e9fecb54a) failed: Permission denied Oct 16 17:00:50 mailtest dovecot: pop3(testuser): file_lock_dotlock() failed with mbox file /var/mail/testuser: Permission denied Oct 16 17:00:50 mailtest dovecot: pop3-login: Login: user=<testuser>, method=PLAIN , rip=63.201.8.122, lip=64.4.143.26, TLS Oct 16 17:00:50 mailtest dovecot: pop3(testuser): Mailbox init failed top=0/0, retr=0/ del=0/0, size=0 I've read in the archives that this can be fixed by setting mail_extra_groups = mail in dovecot.conf, but OpenBSD has /var/mail owned by root:wheel mod 755, and /var/mail files owned by fileowner:users mod 600, and no mail group. Anyone know how I can fix this? Jeff Simmons jsimmons(a)goblin.punk.net Simmons Consulting - Network Engineering, Administration, Security "It was on fire when I got here."

3 3

Re: [Dovecot] Backup Maildir
by Odhiambo Washington 17 Oct '05

17 Oct '05

* On 06/10/05 13:10 -0400, Geo Carncross wrote: > On Thu, 2005-10-06 at 19:10 +0300, Odhiambo Washington wrote: > > * On 06/10/05 16:06 +0100, Gabe Granger wrote: > > > Hi All, > > > > > > I'm currently doing nightly full backups of /home. I'm not sure if a > > > full back up is the best way to do backups. I know with my > > > fileserver i do weekly full backup and daily incremental which would > > > file on those type of files. I guess my question to the group is, > > > how do you guys backup Maildir? whats the best way of doing it? > > > > > > This is an interesting question, especially because it relates to mail! > > I am a systems admin, but this is one area that I seriously flop in. > > > > How do you backup e-mails for users when during the backup, they are > > deleting the e-mails from the Maildir (POPping) and at the same, and > > the SMTP server is also writing to it. This is very real on a busy > > mail server. > > > > So, how do people make backups of client's e-mails (Maildir)??? > > The ostrich approach works very well for Maildir. Deleting entries or > new entries either show up or they didn't. Please describe this ostrich approach, or show me how. We only know of Ostriches for meat these sides :-) Best regards, Odhiambo Washington Systems Admin, Wananchi Online Ltd. Are you hosting your domain name with the leaders??: See http://webhosting.info/webhosts/tophosts/Country/KE DISCLAIMER : http://ns2.wananchi.com/~wash/Email/disclaimer.txt ----------------------------------+----------------------------------------- Odhiambo WASHINGTON . WANANCHI ONLINE LTD (Nairobi, KE) http://www.wananchi.com/email/ . 1ere Etage, Loita Hse, Loita St., Mobile: (+254) 722 743 223 . # 10286, 00100 NAIROBI ----------------------------------+----------------------------------------- Q: What is the difference between open-source and commercial software? A: If you have a problem with commercial software you can call a phone number and they will tell you it might be solved in a future version. For open-source software there isn't a phone number to call, but you get the solution within a day.

3 3

[Dovecot] E-mail marked as unread
by Andy Cravens 17 Oct '05

17 Oct '05

I have a problem where an e-mail will be marked as unread even though it has been read. When I click on the message the status changes to "read" however, when I go to check for new mail the status changes back to "unread." If I move the message to the trash folder and then move it back to my inbox, the problems stops. Unfortunately, a different e-mail is affected by this problem a few minutes later. I'm using alpha 3 on Solaris 9 and my client is Mozilla 1.7.7 on Solaris 9. No messages in the log to indicate a problem. Anybody else seen this?

2 1

[Dovecot] Invalid Headers
by Brant Fitzsimmons 16 Oct '05

16 Oct '05

Hello all, I have been trying to compare Dovecot to Cyrus and in trying to to migrate some mail from Dovecot to Cyrus I am unable to do so because of an invalid header. The From header is incorrectly written as From> as opposed to the correct From: . Any idea what may be causing this and how to fix it? My setup is Fetchmail->Postfix->amavis-new->clamav->dovecot for dovecot and Fetchmail->Postfix->amavis-new->clamav->cyrus for cyrus. When receiving mail in the cyrus setup I don't have the problem. Any thoughts? -- Brant Fitzsimmons brant(a)bfcomputerconsulting.com ------------------------------------------------------------------- "Strange times are these in which we live when the old and the young are taught falsehoods in the schools of learning. And the one man that dares to tell the truth is called at once a lunatic and a fool." -Plato

2 2

[Dovecot] A Couple Of Issues (APOP Causes Auth SIGSEGV, Umask Setting Ineffective)
by Sabahattin Gucukoglu 16 Oct '05

16 Oct '05

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I'm very happy with Dovecot and wish the best for its continued development. It's a true testament to brilliant componentised design and Unix philosophy. Configuration made easy because of the way the file is parsed and a single point of startup make it ridiculously straightforward (and lovely) to administer. But of course, we all already know this ... I'm sorry that I can't provide traces at the moment, I'm working from an optimised set of binaries. (-O3 -march=i586 -fomit-frame-pointer) GCC 3.4.4, Gentoo X86 2005.0, Linux 2.6.13, Glibc 2.6.5. Pegasus Mail 4.30B1 is the client on Win32. Dovecot is still Alpha2 (I will upgrade when Gentoo has updated their ebuild). Of course if you advise I'll look at rebuilding newer versions or patched versions with(out) debug symbols. 1. When I attempt APOP login of any variety on the POP3 server auth dies with signal 11. passwd-file is of course listed as a password database, alongside shadow. I get back "-ERR Internal authentication failure - please try again later." or something like this and all subsequent authentication in that session won't work (of course, auth is dead). The password entry is in /etc/dovecot.secrets (perms=0700,uid=0,gid=0) and looks like: username:{PLAIN}cleartextpassword 2. Umask setting gone strange. I set it, per example comment, to "7077" rather than default of 0077 (just to be precise...). When directories are subsequently created, user owning it doesn't even get read/write permissions (just x) and group gets rw but not x! It has not even to do with my system umask (022) set by login. I've set it to 0000 for now in dovecot (/etc/skel has .mail put in people's homedirs with 0700, so there's no worry, but of course I'd like to see that one fixed). If you need more info please let me know. Hope this is enough. Cheers, Sabahattin - -- If an email tells you to forward it to all your friends, please temporarily forget that I am your friend. Sabahattin Gucukoglu Phone: +44 20 88008915 Mobile: +44 7986 053399 Email/MSN: <mail(a)Sabahattin-Gucukoglu.com> Skype: SabahattinGucukoglu (requires authorisation, add me to your list first) SpeakFreely: Chalcedony.Sabahattin-Gucukoglu.com (Please use CELP compression if your processor allows) -----BEGIN PGP SIGNATURE----- Version: PGP 8.0 -- QDPGP 2.70 iQA/AwUBQzqINyNEOmEWtR2TEQLs1gCdGhobU2SQAuwA5fMIVFkEXG9dqfMAn3+7 9ebHqEFut7NapNhf7gERxhQ6 =b7zN -----END PGP SIGNATURE-----

3 5

[Dovecot] Dovecot doesn' compile with gnutls
by Elimar Riesebieter 16 Oct '05

16 Oct '05

Hi all, tried to build dovecot-1.0.alpha3 with gnutls. The build stops something like: ssl-proxy-gnutls.c:420: warning: 'gnutls_dh_params_set' is \ deprecated (declared at /usr/include/gnutls/compat8.h:82) ssl-proxy-gnutls.c: In function 'read_rsa_parameters': \ ssl-proxy-gnutls.c:446: warning: 'gnutls_rsa_params_set' is \ deprecated (declared at /usr/include/gnutls/compat8.h:77) make[4]: *** [ssl-proxy-gnutls.o] Error 1 Building with openssl 0.9.8 there are connection errors: dovecot: Oct 15 22:46:48 Error: imap-login: Can't load certificate \ file /etc/ssl/certs/dovecot.pem: error:25066067:DSO support \ routines:DLFCN_LOAD:could not load the shared library Any hints? Please notice I prefer gnutls ;-) Thanks Elimar -- On the keyboard of life you have always to keep a finger at the escape key;-)

3 4