- 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