- dovecot - dovecot.org

[Dovecot] debian testing and dovecot
by vmstech 12 Feb '06

12 Feb '06

Hi all - Does anyone know how far off beta2 is from getting into debian testing? thx Glenn

2 1

[Dovecot] Compiling Dovecot with gssapi
by Luca Bertoncello 12 Feb '06

12 Feb '06

Hi, all! I'm new to Dovecot and I try to compile it to allow GSSAPI authentication. Unfortunately, configure says me always: Install prefix ...................... : /usr/local File offsets ........................ : 64bit I/O loop method ..................... : poll File change notification method ..... : dnotify Building with SSL support ........... : yes (OpenSSL) Building with IPv6 support .......... : yes Building with pop3 server ........... : yes Building with GSSAPI support ........ : no Building with user database modules . : static prefetch passwd passwd-file checkpassword mysql (modules) Building with password lookup modules : passwd passwd-file shadow pam checkpassword mysql (modules) And, of course, I can't use this authentication method... I searched in google and Dovecot docs, but I didn't found anything... Can someone help me? The system is a Linux RedHat 9 Thanks a lot! -- _______________________________ Luca Bertoncello -Programmierung / Mailserver- IMS Internet-Media-Service GmbH Bärensteiner Straße 7 01277 Dresden Fon: +49 351 2112034 Fax: +49 351 2112020 email: bertoncello(a)internet24.de

3 2

[Dovecot] Dovecot pop3s problem : can't see email
by Rory Campbell-Lange 11 Feb '06

11 Feb '06

Hi. I am trying to setup dovecot running a pop3 service for external clients (and intend in future to setup an imap interface on localhost only for squirrelmail.) Exim is delivering ok to local mailboxes, but I can't seem to get dovecot to serve them. Configuration details: ---------------------- All users run as the tst user, and authentication is done through postgresql. ...excerpt... mail_extra_groups = tst default_mail_env = mbox:INDEX=~/home/tst/Mail/:/home/tst/Mail/%u protocol pop3 { pop3_uidl_format = %08Xu%08Xv pop3_client_workarounds = outlook-no-nuls oe-ns-eoh } ...excerpt... Log details: ------------ The log shows that docecot is looking at /home/tst/Mail/test Feb 11 13:54:55 tst dovecot: auth(default): client in: AUTH^I1^IPLAIN^Iservice=POP3^Isecured^Ilip=217.147.82.200^Irip=83.146.33.145^Iresp=AHRlc3QAcXVhdWpv Feb 11 13:54:55 tst dovecot: auth(default): sql(test,83.146.33.145): query: SELECT passwd as password FROM users WHERE userid = 'test' AND active = 'Y' Feb 11 13:54:55 tst dovecot: auth(default): client out: OK^I1^Iuser=test Feb 11 13:54:55 tst dovecot: auth(default): master in: REQUEST^I1^I14586^I1 Feb 11 13:54:55 tst dovecot: auth(default): sql(test,83.146.33.145): SELECT '/home/tst/Mail/' || home AS home, uid, gid FROM users WHERE userid = 'test' AND active = 'Y' Feb 11 13:54:55 tst dovecot: auth(default): master out: USER^I1^Itest^Ihome=/home/tst/Mail/test^Iuid=1001^Igid=1001 Feb 11 13:54:55 tst dovecot: pop3-login: Login: user=<test>, method=PLAIN, rip=83.146.33.145, lip=217.147.82.200, TLS Feb 11 13:54:58 tst dovecot: pop3(test): Logout. top=0/0, retr=0/ del=0/0, size=0 tst:/home/tst/Mail# ls -lt | grep test -rw------- 1 tst tst 1017 Feb 11 13:41 test -- Rory Campbell-Lange <rory(a)campbell-lange.net> <www.campbell-lange.net>

1 0

[Dovecot] Bug in gssapi support
by Mark Davies 10 Feb '06

10 Feb '06

Hi, Was trying to use the gssapi support and the authentication would consistently die for me. The following patch fixes: --- src/auth/mech-gssapi.c.orig 2006-01-10 15:46:10.000000000 +1300 +++ src/auth/mech-gssapi.c @@ -138,7 +138,7 @@ static OM_uint32 obtain_service_credenti return major_status; } - gss_release_name(&minor_status, gss_principal); + gss_release_name(&minor_status, &gss_principal); return major_status; } as gss_release_name takes a pointer to a gss_name_t as second arg. cheers mark

1 0

[Dovecot] Outlook anonymous IMAP login
by Vincent Jaussaud 10 Feb '06

10 Feb '06

Hello guys, I'm trying to setup anonymous IMAP login on a bunch of Outlook clients, but it doesn't seems to work. I'm using dovecot-0.99.14-r1, on a Gentoo Linux OS. Using command line anonymous login, it's working just fine: youri / # telnet localhost 143 Trying 127.0.0.1... Connected to localhost. Escape character is '^]'. * OK dovecot ready. . CAPABILITY * CAPABILITY IMAP4rev1 SORT THREAD=REFERENCES MULTIAPPEND UNSELECT LITERAL+ IDLE CHILDREN LISTEXT LIST-SUBSCRIBED NAMESPACE STARTTLS AUTH=PLAIN AUTH=ANONYMOUS . OK Capability completed. . AUTHENTICATE ANONYMOUS + . OK Logged in. But with Outlook it's not working at all. I tried using no password, or just some random stream, it makes no difference. The error I got in dovecot's logs are: Feb 07 12:31:16 Info: PAM: pam_authenticate(anonymous) failed: Authentication failure Feb 07 12:31:19 Info: PAM: pam_authenticate(anonymous) failed: Authentication failure Feb 07 12:31:28 Info: PAM: pam_authenticate(anonymous) failed: Authentication failure My assumption is that Outlook doesn't provide anonymous IMAP support. Could someone confirm this ? Do you know if any workaround/anonymous plugin exist ? Thanks ! --- Everything takes longer, costs more, and is less useful. -- Erwin Tomash

3 4

[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