- dovecot - dovecot.org

[Dovecot] Maildir, imap and newness of messages
by Anand Buddhdev 10 Feb '06

10 Feb '06

I'm using the standard Dovecot 0.99.14 on Fedora Core 4, with a Maildir++ mailbox. I've noticed what I think is an oddity in the way dovecot handles messages: According to the Maildir specification, a message in Maildir/new is a truly new message, which has not yet been touched by any reader. From an IMAP viewpoint, such a message should have the flag RECENT. However, if a message exists in Maildir/cur, then it means that the message is no longer new (because some other reader has opened the Maildir, and moved the message from new to cur). From an IMAP viewpoint, such a message should NOT have the RECENT flag. However, dovecot seems to get this wrong. For example, if I have a message in Maildir/new, and I use mutt (a console-based maildir-aware mail client) to open the Maildir, then mutt moves the messages from Maildir/new to Maildir/cur (note here that I haven't actually read the message yet, just opened the Maildir with mutt). I expect that when I now open this Maildir with dovecot imap, and do a "select inbox", it should report "1 EXISTS" and "0 RECENT". However, dovecot reports this as "1 EXISTS" and "1 RECENT". In my opinion, this is a bug in Dovecot. Would any of the developers like to comment? Anand

3 3

[Dovecot] Dovecot stops logging of imap logins after logrotation
by Gerhard Hofmann 10 Feb '06

10 Feb '06

Hi list, on my Debian box there is a logrotation cron job that will gzip existing /var/log/mail.log file and create a new mail.log. It seems that after running logrotation dovecot stops logging successful POP or IMAP logins to /var/log/mail.log (nevertheless, it still works to login with POP or SMTP). This is bad because pop-before-smtp mechanisms also stop working. I have deactivated logrotation cron job and will monitor mail.log file. Maybe I should just run /etc/init.d/dovecot restart after logrotation script. What do you think? TIA Gerhard

5 4

[Dovecot] Programming Help
by Neal Katz 10 Feb '06

10 Feb '06

Hi, I was hoping you could provide me with some pointers on how to get started adding some features to dovecot. What I am trying to do is add an optional publish mechanism, that would publish a list of events as they occur, so that an external program could read these events and do "something". These events would be "Add", "Delete", "Move" - these would be posted every time a new message is added, deleted or moved. "CreateDir", "DeleteDir" would be published when a user creates a subf-folder or removes one. A simple example would be to configure the system to publish 'Add Message' events, and then an external program would read these, and send a notification event to web based users who are currently logged in. The publish feature would be controlled by the config file, and would be disabled by default The config setting would allow an administrator to specify what events to publish, the mechanism to use, and optional arguments for the mechanism For mechanisms I plan on developing a file based system, one file per event, written into a directory, the subscriber/reader would delete the file Other mechanisms could include TCP/IP based (connect to port XX, and send some data); or even connect to a commercial Message Queue product. Ex. Publish=ADD+DELETE+MOVE:file:/var/spool/imapevents Or Publish=ADD+DELETE+MOVE:tcpip:localhost:9999 It would help me a lot if you could just provide me with a few pointers as to the best place to add my features into the dovecot code, I took a quick look at the code and decided to contact you first before going ahead and putting things in the WRONG place. I did see the code for supporting inotify and similar mechanisms, but I don't see the big picture ? How does dovecot use inotify ?, what features are enabled that you don't get without inotify. If you have a code-roadmap, or architectural diagrams (or doodles) that would be helpful too. In terms of inotify, I don't think this will work for me, since I would like to have the user, Message-Id and Imap UIDL sent in the event message I hope this makes sense, if not just send me an email asking for clarification. All of the changes I make I will submit back to you, and hopefully they will be made part of the base product. Thanks, Neal Katz p.s. I chose Dovecot because I was very impressed with the ease of installation and migration (from courier), my early tests have shown it to be twice as fast when traverse all messages in a large mailbox ( 100K message ).

3 2

[Dovecot] Mixed IMAP/POP3 environment, a success
by Denis Sbragion 10 Feb '06

10 Feb '06

Hello everybody, I just want to inform the Dovecot developers and users that I completely migrated the first mailbox (my own one) from Eudora/UW to SquirrelMail/Dovecot. I'm using it since a couple of days and after a bit of tuning (mostly SquirrelMail related) it works like a charm. I even performed some heavy operations, like moving thousands of messages between different mailboxes or searching within a 1 Gb folder, and performances are indeed great. My sincere greatest compliments to the Dovecot developers and my biggest thanks to the people who helped me. No wonder that Fedora/RedHat has decided to adopt Dovecot as the default IMAP server for future releases. It looks like the perfect balance between security, performances, flexibility, standards conformance and ease of use. Bye, -- Denis Sbragion InfoTecna Tel: +39 0362 805396, Fax: +39 0362 805404 URL: http://www.infotecna.it

1 0

[Dovecot] Dovecot 1.0b2 now in pkgsrc packaging system
by Todd Vierling 10 Feb '06

10 Feb '06

After months of testing in the "work in progress" pkgsrc-wip playground, dovecot-1.0b2 is now in the main pkgsrc mainline and will be tracked up through the 1.0 release and beyond. This means it's now much easier to get Dovecot 1.0 up and running on NetBSD and any other platform supported by pkgsrc (see www.pkgsrc.org) prior to this, 0.99.x was the newest available. Binary packages for NetBSD and some other systems should start appearing within a week or two of this message. As before, dovecot-nightly is still available in the pkgsrc-wip package tree, for those who like to live on the edge. -- -- Todd Vierling <tv(a)duh.org> <tv(a)pobox.com> <todd(a)vierling.name>

2 1

RE: [Dovecot] alternate ports?
by Villalovos, John L 10 Feb '06

10 Feb '06

dovecot-bounces(a)dovecot.org <> wrote: > On Thu, Feb 09, 2006 at 02:40:45PM -0800, Gregory K. Ruiz-Ade wrote: > >> I'm trying to set up 1.0 beta 2 on one of our systems, and would >> like to run it on alternate ports from the standard IMAP and >> IMAP/SSL ports so that we can test it out a couple users at a time. >> How does one tell dovecot to listen on alternate ports? I can't >> find anything in the example config file... > > imap_listen = host:port > pop3_listen = host:port I don't think that works in the 1.0b beta 2 (Note: 1.0 beta 3 just came out): Try something like this: # Listen on localhost for IMAP. Listen on all interfaces for IMAP/SSL protocol imap { listen = 127.0.0.1 ssl_listen = * }

1 0

[Dovecot] alternate ports?
by Gregory K. Ruiz-Ade 10 Feb '06

10 Feb '06

I'm trying to set up 1.0 beta 2 on one of our systems, and would like to run it on alternate ports from the standard IMAP and IMAP/SSL ports so that we can test it out a couple users at a time. How does one tell dovecot to listen on alternate ports? I can't find anything in the example config file... Thanks, Gregory -- Gregory K. Ruiz-Ade Sr. Systems Administrator Computer Science and Engineering University of California, San Diego Office: EBU3b 1216 Phone: (858) 822-2625 E-mail: gkra(a)ucsd.edu

3 2

[Dovecot] Openwebmail with Dovecot
by ftnx＠ksbase.com 10 Feb '06

10 Feb '06

So far I've managed to get Dovecot to work fine for regular POP users and Squirrelmail. Even though it seems dead slow and obsolete, a few users would like to use Openwebmail. All users are virtual, and there are/will be no system accounts. Anyone have a working example for Dovecot/Openwebmail for virtual user setup? Kari Suomela KARICO Business Services Toronto, ON Canada http://www.karico.ca

4 5

[Dovecot] epoll error when running as proxy
by Bill Boebel 09 Feb '06

09 Feb '06

I am running dovecot 1.0 beta3 as a front-end proxy, and getting the following error when using epoll. The error goes away if I switch to poll. On the backend IMAP server I see that the login was successful. The error occurs when I try to retrieve an email or get a folder listing via IMAP after logging in successfully... Feb 9 15:35:57 director4 dovecot: imap-login: proxy(bboebel(a)webmail.us): started: user=<bboebel(a)webmail.us>, method=plain, rip=204.119.252.7, lip=192.168.1.68 Feb 9 15:09:50 director4 dovecot: imap-login: io_loop_handle_add: epoll_ctl(op=3, fd=10, ret=-1, errno=2): No such file or directory Feb 9 14:58:23 director4 dovecot: child 9688 (login) returned error 89 I can't find anything in the mailing list archives about this error, so here are some details. I hope somebody can point me in the right direction to fix this. - I am running this on Red Hat ES4 (32-bit x86), compiling with the following options: ./configure \ --prefix=/usr \ --sysconfdir=/etc \ --localstatedir=/var \ --with-ssldir=/usr/share/ssl \ --disable-ipv6 \ --with-file-offset-size=32 \ --with-mem-align=4 \ --with-ioloop=epoll \ --without-passwd \ --without-passwd-file \ --without-shadow \ --without-pam \ --without-checkpassword \ --without-bsdauth \ --without-gssapi \ --with-ldap \ --without-vpopmail \ --with-static-userdb \ --with-prefetch-userdb \ --without-pgsql \ --with-mysql \ --without-sqlite \ --without-ssl \ --with-storages=maildir - I have also complied with these options and got the same error: ./configure \ --prefix=/usr \ --sysconfdir=/etc \ --localstatedir=/var \ --with-ioloop=epoll \ --with-mysql - I have also tried the latest CSV snapshot (dovecot-20060209.tar.gz) and 1.0 beta2, and I get the same error. - If I switch to poll instead of epoll, everything works fine. Any ideas? Bill

1 0

[Dovecot] trouble compiling today's CVS in Solaris 9
by Glenn Leavell 09 Feb '06

09 Feb '06

I've recently been able to compile the CVS code in Solaris 9, but I'm now getting a few errors. First, I receive this error during the autogen process: src/plugins/Makefile.am:5: required directory src/plugins/convert does not exist configure.in:1717: required file `src/plugins/convert/Makefile.in' not found I can workaround that by removing the reference to src/plugins/convert in configure.in. I then get this error: src/plugins/Makefile.am:5: required directory src/plugins/convert does not exist I can workaround that by removing the reference to the convert plugin from src/plugins/Makefile.am. After that, the autogen process completes and I get the previously discussed shell error when running make: if [ "" != "" ]; then \ for i in ; do \ echo "extern struct sql_db driver_${i}_db;" >>sql-drivers-register.c ; \ done \ fi /bin/bash: -c: line 1: syntax error near unexpected token `;' /bin/bash: -c: line 1: `if [ "" != "" ]; then for i in ; do echo "extern struct sql_db driver_${i}_db;" >>sql-drivers-register.c ; done fi' I can workaround that by simply running make from /bin/sh. I then get this error: Making all in auth make[3]: Entering directory `/home/glenn/dovecot/src/auth' /bin/bash ../../libtool --mode=link --tag=CC gcc -std=gnu99 -g -O2 -Wall ... <snip> userdb-prefetch.o userdb-static.o userdb-vpopmail.o userdb-sql.o -L/usr/local/ssl/lib libpassword.a ../lib-settings/libsettings.a ../lib-ntlm/libntlm.a ../lib-sql/libsql.a ../lib/liblib.a -lcrypt -lpam -lldap -ldl -lsocket -lnsl -lrt -lsendfile Undefined first referenced symbol in file sql_drivers_register_all main.o ld: fatal: Symbol referencing errors. No output written to dovecot-auth collect2: ld returned 1 exit status make[3]: *** [dovecot-auth] Error 1 make[3]: Leaving directory `/home/glenn/dovecot/src/auth' I'm not sure why sql_drivers_register_all is getting referenced. I tried explicitly turning off all sql-related options on the configure command line, and that didn't help. Any help would be appreciated. Thanks! Glenn

2 1