- dovecot - dovecot.org

[Dovecot] 0.99.10.6-rc1 released
by Timo Sirainen 18 Jun '04

18 Jun '04

http://dovecot.org/rc/ Fixes the crashes people had been getting more often with 0.99.10.5. Also included all the patches in dovecot.org/patches/old: - SHA1 passwords - mail_extra_groups setting (Debian people can finally fix #185335 :) - autocreate missing maildirs (and don't crash) - maildir_stat_dirs setting If no problems are found within few days this will simply be renamed to 0.99.10.6.

3 5

[Dovecot] 0.99.10.6-rc2
by Timo Sirainen 18 Jun '04

18 Jun '04

http://dovecot.org/rc/ Since rc1: - Changed a few comments in dovecot-example.conf - Changed a few error messages. Most importantly: "Internal error occured. Error report written to server log." .. maybe that would get more people to look for the real error in the log file :) - Added NAMESPACE command - Fixed SHA1 compiling issue - Fixed FreeBSD compiling issue

1 0

[Dovecot] dovecot startup failure - dovecot-auth unable to open passwd-file
by Stephen Hillier 18 Jun '04

18 Jun '04

Hi all, I'm stuck on getting dovecot to work for 2 days. Here's the logfile entries from the startup process(es) dovecot: Jun 18 14:48:43 Info: Dovecot starting up dovecot-auth: Jun 18 14:48:44 Fatal: Can't open passwd-file /var/run/dclogin/mail-passwd: No such file or directory dovecot: Jun 18 14:48:44 Error: Auth process died too early - shutting down dovecot: Jun 18 14:48:44 Error: child 7313 (auth) returned error 89 imap-login: Jun 18 14:48:44 Fatal: fd_send(-1) failed: Broken pipe pop3-login: Jun 18 14:48:44 Fatal: fd_send(-1) failed: Broken pipe The strange thing is, the file I've specified does exist -- i created it manually -- and the 1 entry in that file is this: steve:s13fj3NHakds.:10001:5000::/var/run/dovecot/home/steve:/sbin/nologin::~/Mail/:INBOX=/var/spool/mail/steve What's even stranger -> every time I try to startup dovecot, the passwd-file that is seen to be "missing" gets deleted!!!! why??? Here's a copy of my current (broken) conf: base_dir = /var/run/dovecot/ protocols = imap imaps pop3 pop3s ssl_disable = yes log_path = /var/log/maillog login_dir = /var/run/dclogin login_chroot = no login = imap login_executable = /usr/libexec/dovecot/imap-login login_user = doveauth login_process_per_connection = yes login_processes_count = 5 login = pop3 login_executable = /usr/libexec/dovecot/pop3-login first_valid_uid = 10000 last_valid_uid = 20000 first_valid_gid = 5000 last_valid_gid = 5100 default_mail_env = mbox:~/Mail/:INBOX=/var/spool/mail/%u mbox_locks = fcntl imap_executable = /usr/libexec/dovecot/imap pop3_executable = /usr/libexec/dovecot/pop3 auth = default auth_mechanisms = plain digest-md5 auth_userdb = passwd-file /var/run/dclogin/mail-passwd auth_passdb = passwd-file /var/run/dclogin/mail-passwd auth_executable = /usr/libexec/dovecot/dovecot-auth auth_verbose = yes I'm sure I did something silly in my conf that's causing the problem but I'm not sure what that might be. Thanks in advance for any and all help. Steve. ______________________________________________________________________ Post your free ad now! http://personals.yahoo.ca

2 1

[Dovecot] Info: Internal login failure:
by Nico De Beer - MWEB 18 Jun '04

18 Jun '04

I get the following error on auth with mysql on pop3 what am i missing or doing wrong mysql config file db_host = localhost #db_port = 3306 db_unix_socket = /var/lib/mysql/mysql.sock db = ADMIN db_user = mailmaster db_passwd = ******** db_client_flags = 0 default_pass_scheme = PLAIN password_query = SELECT MAILBOX_PASSWORD AS password FROM MAIL WHERE MAILBOX_USERNAME = '%n' AND MAILBOX_DOMAIN = '%d' #user_query = SELECT MAILBOX_ROOT AS home,uid,gid FROM MAIL WHERE MAILBOX_USERNAME = '%n' and MAILBOX_DOMAIN='%d' dovecot config file base_dir = /var/run/dovecot/ protocols = imap pop3 imap_listen = * pop3_listen = * ssl_disable = yes log_path = /var/log/dovecot_log info_log_path = /var/log/dovecot_info_log log_timestamp = "%b %d %H:%M:%S " login_dir = /var/run/dovecot/login login = imap login_executable = /usr/local/libexec/dovecot/imap-login login_user = dovecot login_process_size = 16 login_process_per_connection = yes login_processes_count = 3 login_max_processes_count = 128 login_max_logging_users = 256 login = pop3 max_mail_processes = 1024 verbose_proctitle = no first_valid_uid = 500 #last_valid_uid = 0 default_mail_env = maildir:/home/mail/%d/%n/Maildir mail_cache_fields = MessagePart client_workarounds = oe6-fetch-no-newmail:outlook-idle: mailbox_check_interval = 300 mailbox_idle_check_interval = 30 mail_save_crlf = yes mail_read_mmaped = no maildir_copy_with_hardlinks = yes mbox_locks = dotlock fcntl mbox_read_dotlock = yes mbox_lock_timeout = 120 mbox_dotlock_change_timeout = 30 umask = 0077 mail_drop_priv_before_exec = no imap_executable = /usr/local/libexec/dovecot/imap imap_process_size = 256 pop3_executable = /usr/local/libexec/dovecot/pop3 pop3_process_size = 256 auth = default auth_mechanisms = plain auth_passdb = mysql /usr/local/etc/dovecot-mysql.conf auth_user = mailmaster auth_username_chars = abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@ Are you ready for Telkom's 10-digit dialling? To find out how this will affect your Internet connection in the not too distant future, go to www.mweb.co.za/ten

2 1

[Dovecot] Maildir + Evolution
by mkortela＠cc.hut.fi 18 Jun '04

18 Jun '04

I don't know if this is an Evolution bug or not, but when I use the maildir format with Dovecot 0.99.10p2 (from OpenBSD packages collection) and connect to it from Evolution 1.4 using IMAP, Evolution displays subfolders incorrectly. It actually does not show any subfolders, only root folders with names like "Folder.Subfolder" and "Folder.Subfolder.Subsubfolder". There's no such problem when using traditional mailboxes. Is this an Evolution bug or one of Dovecot's? I had thought the IMAP protocol should act the same no matter which mail dir structure was used... -- Mikko Kortelainen mkortela(a)cc.hut.fi

3 2

[Dovecot] Add SSL to Dovecot & SquirrelMail
by Eric Kahklen 18 Jun '04

18 Jun '04

I am relatively new to setting up mail servers and wondered how difficult it would be to add SSL to my current Dovecot & SquirrelMail setup. Would I just add SSL to the squirrelmail directory under appache with my certificate? Does Dovecot need any changes to the configuration? I have it working fine without SSL. Thanks, Eric

1 0

[Dovecot] IMAP and webmail applications
by Tom Allison 18 Jun '04

18 Jun '04

I've been hunting around for a webmail application other than squirrelmail for reasons that really don't matter. But I'm seeing that a lot of these applications tend to sometimes access servers via IMAP, but they always seem to have a touch more information needed than might be for an IMAP session. An example is openwebmail. It authenticates very similar to how dovecot authenticates, with a userdb and passdb specifications. It reads directly off the disk for some of it's activities. As for squirrelmail, they seem to want a lot of information regarding the mail architecture (mbox, maildir, folder locations...) and I don't really see where this could come into play with an IMAP implimentation. So, not actually having read all 82 pages of RFC 2060 (but I did print them!), I'm trying to see what I might miss if I were to attempt a web mail application that was based entirely upon IMAPv4 with the only information known prior to connection is the server name. Kind of like my mail client. Will I get into trouble with mail directories/folders if I start accessing different IMAP servers other than dovecot? Can I discover this without any hints from the user? I'm not sure exactly what I'm asking for here, other than some thoughts on what I might have to watch out for or do without (when comparing to squirrelmail as an example). I know I'll have to do something different if someone wants an addressbook, but I'm not there yet.

5 6

[Dovecot] 1.0-test16 - nearing usable state
by Timo Sirainen 18 Jun '04

18 Jun '04

http://dovecot.org/test/ Here you go, maildir syncing problems finally fixed (I hope). Well, except there's this "new-dir-only syncing" optimization which I'm not really sure if it works as it should. The bug really was in index code as I was beginning to suspect. The good thing is that while trying to figure it out over the last several weeks I thought of many other potential problems (race conditions) which got fixed. Those would have been much harder to find than this one :) Finally I thought I'd stop looking at the code and just begin dumping tons of debugging data to see where exactly it goes wrong. After few hours of debugging I figured out it was because message was being removed from index but not from maildir. 5 hours of sleep later I woke up, thought a while, figured out where it must be, got up, half an hour more debugging and found it. :) Code merging two UID range buffers into one was buggy, inserting one line of code fixed it. So .. Maybe I'll finally start using this myself now. The next important problems seem to be some random error messages about index locking timeouts and some asserts in some situations.

3 2

Re: [Dovecot] IMAP and webmail applications
by durango99 18 Jun '04

18 Jun '04

i thought squirrelmail would be way too much of an overkill for my needs also but i went for it. i'm using debian and i got the squirrelmail package installed and working within 15 minutes. what really makes life easy is that squirrelmail comes with a configuration utility (squirrelmail-configure). it was very easy to get things configured without worry about a lot of conf files :) i also like the many plugins that people have created for squirrelmail. it's also very simple to add these plugins into squirrelmail using squirrelmail-configure. i had originally been ssh and mutt to check my mail, but i decided it be nice to have a web front-end and squirrelmail /apache /dovecot /procmail /spamassassin /gotmail /getmail /fetchyahoo have been a good mix for me. the hardest part for me was figuring out procmail and not squirrelmail :) my 2 cents, dan > I've been hunting around for a webmail application other than > squirrelmail for reasons that really don't matter. > > But I'm seeing that a lot of these applications tend to sometimes access servers via IMAP, but they always seem to have a touch more information needed than might be for an IMAP session. > > An example is openwebmail. It authenticates very similar to how dovecot authenticates, with a userdb and passdb specifications. It reads directly off the disk for some of it's activities. > > As for squirrelmail, they seem to want a lot of information regarding the mail architecture (mbox, maildir, folder locations...) and I don't really see where this could come into play with an IMAP implimentation. > > So, not actually having read all 82 pages of RFC 2060 (but I did print them!), I'm trying to see what I might miss if I were to attempt a web mail application that was based entirely upon IMAPv4 with the only information known prior to connection is the server name. Kind of like my mail client. > > Will I get into trouble with mail directories/folders if I start accessing different IMAP servers other than dovecot? Can I discover this without any hints from the user? > > I'm not sure exactly what I'm asking for here, other than some thoughts on what I might have to watch out for or do without (when comparing to squirrelmail as an example). I know I'll have to do something different if someone wants an addressbook, but I'm not there yet. >

1 0

[Dovecot] shared authentication
by Kevin 16 Jun '04

16 Jun '04

whats the recommended way to share a user auth info between dovecot and postfix? sasldb seems like it could work but nobody really seems to like using the giant mass that is sasl. i also cant find any information on actually getting dovecot to use sasl past the configure options. i looked at timo's patch for postfix to use dovecot-auth but it doesnt apply correctly on the 2.1 branch. so what are people using to share passwords between the two without using the system passwd?

3 3