- dovecot - dovecot.org

[Dovecot] Simulating UW Snarf...
by Todd Piket 10 Feb '06

10 Feb '06

I already wrote to Timo, but I thought some others on this list may have had a similar situation. So here goes: The scenario at Michigan Technological University stems from long standing traditions and policies that probably won't change. That said, two of the policies are 1.)we don't bounce mail and 2.)we guarantee delivery when we accept a piece of mail. The UW IMAP "snarf" capability was nice because it allowed us to introduce file system, per user quotas w/o worrying about the "INBOX" in an over quota situation. This is because the user could still read mail. The delivered mail would get "snarfed" from /var/mail/user when the user went back under quota. In our test cases with switching to Maildir with Dovecot, we deliver directly to the user's INBOX instead of /var/mail/user so what do we do when the user is over quota because we can't bounce the mail? After many lengthy discussions our thought was this. Could we symbolically link the user's "Maildir/new" to a non-quota file system such that the move from "new" to "cur" would fail if the user is over quota? What will Dovecot do in that failure situation? Do you have other suggestions? I would be more than willing to develop a patch that makes this an option in the config file. Probably similar to allowing the indexes and control files be on a non-quota file system. Again, it would only allow "Maildir/new" to be on a separate file system, not the whole "INBOX". I hope this conveys the idea well enough. Any thoughts or ideas the list provides would be greatly appreciated. -- Regards, ------------------------------------------------------------ | Todd Piket | Email: todd(a)mtu.edu | | Programmer/Analyst | Phone: (906) 487-1720 | | Distributed Computing Services | | | Michigan Technological University | | ------------------------------------------------------------

8 18

[Dovecot] In-memory Index file bug
by Tony Kay 10 Feb '06

10 Feb '06

Hi, I am getting intermittent error messages in the log when my mail client tries to create/open a folder named ".imhoprefs". Some accounts seem to able to do it, but I have at least one that gives the log error: Feb 7 09:29:54 acad-cl1 dovecot: imap(tkay): close() failed with index file (in-memory index): Bad file descriptor I traced through the code, and it seems to be coming from mail_index_close() (line 1527 of mail-index.c), which seems to be attempting to close a file descriptor for an index. The funny thing is that since I am using in-memory indexes, I believe that there shouldn't be any file descriptor to close, which would explain why the close is failing... Environment information: - Dovecot 1.0b2 - mbox - Environment setting: default_mail_env = mbox:%h:INBOX=%h/.mail:INDEX=MEMORY - Attempting to create/use a folder called mail/.imhoprefs At first, I though the folder itself might be corrupted, so I removed it. No dice. I've checked file permissions. No problems. I honestly can't explain why some users are able to use this folder without error, and others are not. -- Anthony Kay University Computing Center (541) 346-1719 GPG Fingerprint: B0DB D46A 60AF FAE7 A94A 5075 0CB4 4D88 9F4F 7F09 Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning. Rich Cook

2 1

[Dovecot] RE: epoll error when running as proxy
by Bill Boebel 10 Feb '06

10 Feb '06

Also, for testing in the error message I patched src/lib/ioloop-epoll.c to show the "ret" and "errno" variables as well as the variable names, which is why there is a bit of extra data in this error message... imap-login: io_loop_handle_add: epoll_ctl(op=3, fd=10, ret=-1, errno=2): No such file or directory Bill On Thursday, February 9, 2006 16:32, Bill Boebel said: > 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 >

5 8

[Dovecot] If mbox does not exist dovecot creates directory
by Alexander Shikoff 10 Feb '06

10 Feb '06

Hi, I've searched the archive of mailing list but did not find anything about this issue. dovecot 1.0alpha5, using mbox format and MySQL DB of users When user is trying to login via POP3 and there is no corresponding mailbox for it dovecot creates a directory instead of mbox file. In this time log looks like Feb 10 10:39:36 orion dovecot: auth-worker(default): sql(ivan.sid(a)my.com.ua,192.168.3.9): query: SELECT `password` FROM `users` WHERE login = 'ivan.sid(a)my.com.ua' Feb 10 10:39:36 orion dovecot: auth(default): client in: AUTH 1 PLAIN service=POP3 lip=192.168.5.23 rip=192.168.3.9 resp=AGl2YW4uaXZhbm9mZkBmY2JhbmsuY29tLnVhADE= Feb 10 10:39:36 orion dovecot: auth(default): client out: OK 1 user=ivan.sid(a)my.com.ua Feb 10 10:39:36 orion dovecot: auth-worker(default): sql(ivan.sid(a)my.com.ua,192.168.3.9): SELECT "mbox:/var/mail/virtual/my.com.ua/ivan.sid:INBOX=/var/mail/virtual/my.com.ua/ivan.sid:INDEX=MEMORY" AS `mail`, 'mailnull' AS `uid`, 'mail' AS `gid` FROM users WHERE login = 'ivan.sid(a)my.com.ua' Feb 10 10:39:36 orion dovecot: auth(default): master in: REQUEST 101 98738 1 Feb 10 10:39:36 orion dovecot: auth(default): master out: USER 101 ivan.sid(a)my.com.ua mail=mbox:/var/mail/virtual/my.com.ua/ivan.sid:INBOX=/var/mail/virtual/my.com.ua/ivan.sid:INDEX=MEMORY uid=26 gid=6 Feb 10 10:39:36 orion dovecot: pop3(ivan.sid(a)my.com.ua): Effective uid=26, gid=6 Feb 10 10:39:37 orion dovecot: pop3(ivan.sid(a)my.com.ua): mbox: data=/var/mail/virtual/my.com.ua/ivan.sid:INBOX=/var/mail/virtual/my.com.ua/ivan.sid:INDEX=MEMORY Feb 10 10:39:37 orion dovecot: pop3(ivan.sid(a)my.com.ua): mbox: root=/var/mail/virtual/my.com.ua/ivan.sid, index=, inbox=/var/mail/virtual/my.com.ua/ivan.sid Feb 10 10:39:37 orion dovecot: pop3(ivan.sid(a)my.com.ua): open() failed with mbox file /var/mail/virtual/fcbank.com.ua/ivan.sid: Is a directory Feb 10 10:39:37 orion dovecot: pop3(ivan.sid(a)my.com.ua): Mailbox init failed top=0/0, retr=0/ del=0/0, size=0 Feb 10 10:39:37 orion dovecot: pop3-login: Login: user=<ivan.sid(a)my.com.ua>, method=PLAIN, rip=192.168.3.9, lip=192.168.5.23 Please help me with this issue! Thanks in advance, Alexander -- Kind Regards, Alexander Shikoff minotaur(a)crete.org.ua

2 2

[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