- dovecot - dovecot.org

[Dovecot] appenduid?
by Johannes Berg 06 Jul '04

06 Jul '04

Hi, Does dovecot support APPENDUID? If not, would it be possible to add? johannes

2 1

Re: [Dovecot] [PATCH, RFC] add APOP authentication mechanism
by Timo Sirainen 06 Jul '04

06 Jul '04

On 1.7.2004, at 16:26, Andrey Panin wrote: >> + if (strcmp(auth_request->protocol, "POP3")) { >> + if (verbose) >> + i_info("apop(%s): wrong protocol %s", >> get_log_prefix(auth_request), >> + auth_request->protocol); >> + mech_auth_finish(auth_request, NULL, 0, FALSE); >> + return TRUE; >> + } >> >> I don't think there's really any point in checking this? Maybe someone >> really wants to use APOP with another protocol :) > > This will be RFC violation isn't it ? (I'll send a public reply, the last question could need input from others) Well, it's not compatible with any RFC of course, but I don't think it would violate anything? I'd just rather like to avoid unnecessary code bloat. Well, except now that I thought about the logic instead of just the code, there are problems. APOP prevents replay attacks by sending different timestamp in greeting, but you're sending the greeting to dovecot-auth as user input to APOP authentication mechanism. So, a user could simply say "AUTH APOP" and send wanted timestamp as input. One way to fix this would be to disallow APOP mechanism to be used with AUTH command in pop3-login and require that the request was done with POP3 protocol. But I think that's pretty ugly kludge. It also requires that processes connecting to dovecot-auth are trusted, which is something I've tried to avoid as much as possible. So dovecot-auth doesn't really know if it's pop3-login which connects to it.. Better fix would be to get part of the timestamp from dovecot-auth itself. It could send a growing ID number as handshake which would be used as part of the timestamp, and APOP mechanism processing would check that timestamp really contains the ID. So timestamp would be <authid.unixtime@hostname>. That also makes the PID go away, which was another thing I would have suggested. POP3 RFC also says: It is conjectured that use of the APOP command provides origin identification and replay protection for a POP3 session. Accordingly, a POP3 server which implements both the PASS and APOP commands should not allow both methods of access for a given user; that is, for a given mailbox name, either the USER/PASS command sequence or the APOP command is allowed, but not both. But I don't know if there's any nice way to do it, except perhaps by defining APOP password scheme which would actually be plaintext but wouldn't work with anything but APOP authentication. Do any other servers prevent it either?

2 5

[Dovecot] Debian dovecot news
by Jaldhar H. Vyas 04 Jul '04

04 Jul '04

I uploaded 0.99.10.6 to sid. Owing to the importance of the dot lock fix, I've tried to have this pushed to sarge quickly. Let's see how that goes. I've prepared a backport of 0.99.10.6 to woody which should be showing up on www.backports.org soon hopefully. In the meantime, if you desperately need it and don't mind working out dependencies yourself, you can find it at http://www.braincells.com/backports/ I uploaded 1.0test18 to http://src.braincells.com/dovecot-test/ (I'll do test20 tomorrow) I told Timo I'd port dovecot's gnutls support from gnutls7 to gnutls10 but I have absolutely no time for it so if someone would volunteer, contact me, I'd really appreciate it. -- Jaldhar H. Vyas <jaldhar(a)debian.org> La Salle Debain - http://www.braincells.com/debian/

4 7

[Dovecot] index file regeneration?
by Paul Reilly 02 Jul '04

02 Jul '04

Quick question: How does dovecot keep the message headers index file updated? Eg: if my MDA delivers an extra 10 messages while I'm logged in. How does the message index get updated? At what points is it regenerated? Thanks, Paul

2 7

[Dovecot] 1.0-test24 and some mbox benchmarking
by Timo Sirainen 02 Jul '04

02 Jul '04

http://dovecot.org/test/ Again only mbox fixes. I found some more bugs which could have also caused some of the mbox problems that people reported. They were found when I today thought I'd again do a bit of testing with my favourite 1.4GB mbox. Then I thought I might as well see how it compares against UW-IMAP. First a bit of explanations how they work internally: Dovecot 1.0-test24 ------------------ Dovecot works by trying to do everything in one "sync" function. It reads new mails, inserts missing headers, writes header modifications and expunges messages. Dovecot leaves 100 bytes of padding in every mail's headers, which it can use to avoid moving the rest of the file forward when it needs to insert space. However, if there's not enough space (and with new mails there isn't), it needs to do the moving. Moving is done by first reading messages and counting how many bytes we're short. Once we've seen enough padding we'll rewrite those messages. If we read until end of file, we'll grow the file and rewrite the messages. Rewriting is made backwards, so we don't have to do much buffering, and in case the rewriting gets interrupted (crash, power loss, etc.) the data loss is very small, a few kilobytes maximum. UW-IMAP 2004 ------------ UW-IMAP first only reads the mbox with SELECT, rewrite is only triggered by LOGOUT, EXPUNGE and CHECK commands. UW-IMAP also inserts padding, but less than Dovecot. It tries to get added headers to fit into 50 bytes, and what's not used is left as padding. Normally this seems to get it around 15-20 bytes of padding. Perhaps I should shrink it from Dovecot too. Rewriting works by reading the file forward into buffer and writing the changes as needed. This is quite fast, but it means the buffer can grow large, and if the rewrite gets interrupted everything in the buffer gets lost. In my test mbox this would have been 23MB of lost data, but normally much less. Benchmarks ---------- I simply rewrote a 1.4GB mbox containing 361052 mails, Linux kernel mailing list archives from years 96-02. Computer is Athlon XP 2700+ with 1GB of memory. reads/writes were counted using Linux's iostat command. Nothing else was being used in that partition, so the numbers should be accurate. Except UW-IMAP's read count is a few blocks too much because I got tired of waiting it and started looking into the mbox to see how far it had gotten. Read counts could also be somewhat wrong if some of the mbox was already in buffer cache. I tried to trash it anyway by catting 2x4GB of data into /dev/null. Kernel used around 900MB of memory for caching. Total CPU times may also be a bit off, as the computer was being used at the same time. Dovecot 1.0-test24 ------------------ reads : 4007432 blocks = 1956 MB writes: 2947381 blocks = 1439 MB original mbox : 1420611590 B = 2774632 blocks = 1354 MB rewritten mbox: 1472684487 B = 2876336 blocks = 1404 MB indexes : 14452732 B = 28227 blocks = 14 MB 7221164 dovecot.index 10436 dovecot.index.cache 7221132 dovecot.index.log (this will be truncated after a while) - 16064 VSZ, 8012 RSS after SELECT completed - 14MB is mmaped index files - 216kB heap left of which 70kB actually in use - heap usage was 25MB VSZ/RSS constantly while syncing, but allocations were so large that libc used anonymous mmap()s so they got dropped after sync - VSZ peaked at 32MB, most likely because index file(s) were temporarily being mmap()ed more than once - 63.37s user - 16.56s system - 24% cpu - 5:22.75 total UW-IMAP 2004 ------------ Reading: - memory: 70044 VSZ, 67724 RSS - CPU: 7s user, 53s total Totally: reads : 5549640 blocks = 2709 MB writes: 2875581 blocks = 1404 MB original mbox : 1420611590 B = 2774632 blocks = 1354 MB rewritten mbox: 1444411190 B = 2821115 blocks = 1377 MB - 93416 VSZ, 91120 RSS - 2295.81s user - 23.99s system - 96% cpu - 39:57.90 total Notes ----- Not counting Dovecot's indexes UW-IMAP wrote 21MB less. But Dovecot wrote 27MB more padding, so just by shrinking it Dovecot would have written 6MB less data. Also because Dovecot writes the file backwards, it needs to do some extra jumping around and overlapping writes, but I guess OS nicely merged them. I'm not exactly sure why UW-IMAP uses so much CPU for rewriting, but it does and so Dovecot is over 7x faster in total (with 36x less CPU). Dovecot should also support delaying the rewrite. This is mostly useful for POP3 clients which deletes all the mail at logout, so they won't need the rewriting at all. Dovecot also writes all flag changes to disk immediately while UW-IMAP leaves it later to do more at once. That results in less total I/O as well.

1 0

[Dovecot] 1.0-test22 - maildir fixed?
by Timo Sirainen 02 Jul '04

02 Jul '04

http://dovecot.org/test/ Well, remember when I said: > 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. Just before I found the expunge bug in index, I was trying to fix the new-dir-only syncing because the code looked wrong. Then I figured out the indexing problem and thought maybe this one wasn't broken after all, and then forgot about it. Finally after lots of debugging, I came to same conclusion again. The code was wrong, and cause of the remaining "Maildir sync: UID < next_uid (312 < 3)" errors. So, please try and see if you still can break this release. Other changes include some crashfixes for cache file and fix for mbox which kept constantly rewriting headers for \recent messages if we had selected the mailbox as read-only (EXAMINE, STATUS).

11 30

[Dovecot] building dovecot 1.0 test19 over fc1
by Luis Miguel Cruz 02 Jul '04

02 Jul '04

[root@fc1-devel tmp]# rpmbuild -ta dovecot-1.0-test19.tar.gz error: line 7: Illegal char '-' in version: Version: 1.0-test19 Seems to be an error into the .spec file I am not sure. I will check it. Did anyone get this problem in the past? Thanks.

2 1

[Dovecot] 1.0-test23 and caching decisions
by Timo Sirainen 30 Jun '04

30 Jun '04

http://dovecot.org/test/ mbox fixes mostly. Began some other things, but none of them actually work yet: - Use X-UIDL header in mboxes for POP3 UIDL list - Cache file compression - Some cleverness for cache file for figuring out what to cache Well, I might as well explain the last one now. Users can be divided to three groups: 1. Most users will use only a single IMAP client which caches everything locally. For these users it's quite pointless to do any kind of caching as it only wastes disk space. That might also mean more disk I/O. 2. Some users use multiple IMAP clients which cache everything locally. These could benefit from caching until all clients have fetched the data. After that it's useless. 3. Some clients don't do permanent local caching at all. For example Pine and webmails. These clients would benefit from caching everything. Some locally caching clients might also access some data from server again, such as when searching messages. They could benefit from caching only these fields. After thinking about these a while, I figured out that people who care about performance most will be using the upcoming Dovecot LDA anyway which updates the indexes/cache immediately. In that case even the first user group would benefit from caching the same way as second group. LDA reads the mail anyway, so it might as well extract some information about it and store them into cache. So, group 1. and 2. could be optimally implemented by keeping things cached only for a while. I thought a week would be good. When cache file is compressed, everything older than week will be dropped. But how to figure out if user is in group 3? One quite easy rule would be to see if client is accessing messages older than a week. But with only that rule we might have already dropped useful cached data. It's not very nice if we have to read and cache it twice. Most locally caching clients always fetch new messages (all but body) when they see them. They fetch them in ascending order. Noncaching clients might fetch messages in pretty much any order, as they usually don't fetch everything they can, only what's visible in screen. Some will use server side sorting/threading which also makes messages to be fetched in random order. Second rule would then be that if a session doesn't fetch messages in ascending order, the fetched field type will be permanently cached. So, we have three caching decisions: 1. Don't cache: Clients have never wanted the field 2. Cache temporarily: Clients want this only once 3. Cache permanently: Clients want this more than once Different mailboxes have different decisions. Different fields have different decisions. There are some problems, such as if a client accesses message older than a week, we can't know if user just started using a new client which is just filling it's local cache for the first time. Or it might be a client user hasn't just used for over a week. In these cases we shouldn't have marked the field to be permanently cached. User might also switch clients from non-caching to caching. So we should re-evaluate our caching decisions from time to time. This is done by checking the above rules constantly and marking when was the last time the decision was right. If decision hasn't matched for two months, it's changed. I picked two months because people go to at least one month vacations where they might still be reading mails, but with different clients.

1 0

[Dovecot] Locked index file
by Kevin Cramer 30 Jun '04

30 Jun '04

I have docevot 0.99.10.6 installed on OpenBSD 3.5 and I'm using it with Squirrelmail. I tried to empty my Trash folder and it timed out. It looks like the process or thread died but the lock wasn't removed: Jun 25 09:16:30 plato imap(kevin): Timeout while waiting for release of shared fcntl() lock for index file /home/kevin/Maildir/.Trash/.imap.index How can I free this lock? I have tried stopping and re-starting dovecot already but that didn't help. Also, is there something I should do to prevent this in the future? The OpenBSD package sets the default locking to fcntl for mbox. I'm not sure if that is the setting that also controls the locking mechanism on the index files. Thanks, Kevin

2 3

[Dovecot] ldap auth problems
by Karl Latiss 30 Jun '04

30 Jun '04

I have previously configured dovecot with ldap auth on a fedora setup with no problems. Now, using RHEL 3 with the same config I get: dovecot: Jun 30 17:46:07 Error: Auth process died too early - shutting down dovecot: Jun 30 17:46:07 Error: child 16780 (auth) killed with signal 11 pop3-login: Jun 30 17:46:07 Fatal: fd_send(-1) failed: Broken pipe imap-login: Jun 30 17:46:07 Fatal: fd_send(-1) failed: Broken pipe This doesn't happen when using other kinds of authentication, eg pam The ldap directory is working fine for other apps so I'm pretty sure that's not it. I'm using the rpm from dag's repository and even re-compiled to ensure ldap support is there. Any clues? -- Karl Latiss <karl(a)designit.com.au> designIT

2 1

[Dovecot] 1.0 Maildir/mbox
by Paul Adams 29 Jun '04

29 Jun '04

Just to confirm, and sorry if I've missed this info somewhere in the flurry of messages: dovecot 1.0 will be able to support maildir and mbox users simultaneously? Paul

2 1

Re: [Dovecot] phpGroupWare
by Avery 29 Jun '04

29 Jun '04

I am currently using SQ mail also. Was wondering though about phpGroupWare. Brook Humphrey said: > On Friday 25 June 2004 08:46 pm, Avery wrote: >> Anyone here using phpGroupWare with dovecot? Does anyone know if it is >> possible? >> >> Thanks > I use squirllmail and it works great. > > -- > -~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~- > Brook Humphrey > Mobile PC Medic, 420 1st, Cheney, WA 99004, 509-235-9107 > http://www.webmedic.net, bah(a)webmedic.net, bah(a)linux-mandrake.com > Holiness unto the Lord > -~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~-~`'~- > > -- Avery

1 0

[Dovecot] Dovecot on Redhat GFS
by Tomi Hakala 28 Jun '04

28 Jun '04

Now that Redhat released GFS to GLP has anyone gotten around to test Dovecot on top of that? -- Tomi Hakala

1 0

[Dovecot] 0.99.10.6 -imap flag update problem still present
by Hauke Fath 28 Jun '04

28 Jun '04

Hi, the email status problem that I reported for Dovecot 0.99.10.5 on June 3rd does still show up in 0.99.10.6. Quoting myself: (1) When new mail is delivered to the inbox, the last read mail(s) change(s) to "unread". Clients: Eudora 6 (Mac), Mozilla 1.6 (NetBSD, Linux, Win XP), MS Outlook. (2) When you attempt to move mails from the inbox to another folder with Mozilla (1.6 on win32, Linux, NetBSD), they are not removed from the inbox, effectively performing a copy instead of a move. And, while I am at it, (3) I see a regular log entry from a MS Outlook 2000 SP 3 Jun 3 10:26:23 bounce imap-login: SSL_read() syscall failed: EOF [130.83.XXX.XXX] The setup here: OS NetBSD 2.0beta, MTA sendmail 8.12.11, LDA maildrop 1.3.9, dovecot 0.99.10.6, OpenSSL 0.9.7d Any ideas? My users are starting to nag... hauke -- Institut für Nachrichtentechnik /~\ The ASCII Ribbon Campaign FG Signalverarbeitung \ / No HTML/RTF in email TU Darmstadt X No Word docs in email Ruf +49-6151-16-3281, Fax -3778 / \ Respect for open standards

2 7

[Dovecot] Mailbox archiving
by Leslie Viljoen 28 Jun '04

28 Jun '04

Hi all! I have a strange problem with Dovecot - deleted messages never seem to get deleted on the server! Deleted messages just seem to get a 'T' at the end of them on the server and remain there, so user mail boxes continue to grow to incredible sizes. Is this a setting I must change somewhere? Must I delete these files manually? Leslie

3 2

[Dovecot] Is Dovecot able to use PostgreSQL to store mailboxes?
by Bill Moran 28 Jun '04

28 Jun '04

Subject says it all. (I'm almost positive this is a FAQ, or that the information is online _somewhere_, but I just spent 20 minutes without finding it ... sorry if I didn't search hard enough) -- Bill Moran Potential Technologies http://www.potentialtech.com

6 8

[Dovecot] passwd + shadow auth problem
by T'aZ 28 Jun '04

28 Jun '04

Hi! here is the problem , i have local users some have shadow password, some not, so i must create two auth one to login via shadow , and one via passwd so here is my config file (stripped comments): protocols = imap imaps pop3 pop3s imap_listen = 192.168.0.2 pop3_listen = 192.168.0.2 imaps_listen = 192.168.0.2 pop3s_listen = 192.168.0.2 login = imap login = pop3 auth = default auth_mechanisms = plain auth_userdb = passwd auth_passdb = shadow auth_user = root auth_count = 1 auth_verbose = yes auth = truc auth_mechanisms = plain auth_userdb = passwd auth_passdb = passwd auth_verbose = yes if i try a user with shadow, it works, but if i try a user without shadow, it fails in the log with dovecot-auth: shadow(taz): unknown user what's wrong, why doesnt it use the second auth option ? where is my error ? i'm using 0.99.10.6 thanks in advance -- T'aZ |Jabber:taz-007@jabber.org|GPG keyID:E051925D|http://taz.prout.be *They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.* Benjamin Franklin 1759 *Beaucoup,vite,loin,mal.* http://www.cl.cam.ac.uk/~rja14/tcpa-faq.html

2 1

[Dovecot] invalid mask
by Adrian Roye 28 Jun '04

28 Jun '04

Hi ! I still get the message: "The current command did not succeed. The mail server responded: invalid mask" I am using the Netscapes mail client. Adrian

2 1

[Dovecot] phpGroupWare
by Avery 26 Jun '04

26 Jun '04

Anyone here using phpGroupWare with dovecot? Does anyone know if it is possible? Thanks -- Avery

1 0

[Dovecot] Locked index file
by Kevin Cramer 25 Jun '04

25 Jun '04

I have docevot 0.99.10.6 installed on OpenBSD 3.5 and I'm using it with Squirrelmail. I tried to empty my Trash folder and it timed out. It looks like the process or thread died but the lock wasn't removed: Jun 25 09:16:30 plato imap(kevin): Timeout while waiting for release of shared fcntl() lock for index file /home/kevin/Maildir/.Trash/.imap.index How can I free this lock? I have tried stopping and re-starting dovecot already but that didn't help. Also, is there something I should do to prevent this in the future? The OpenBSD package sets the default locking to fcntl for mbox. I'm not sure if that is the setting that also controls the locking mechanism on the index files. Thanks, Kevin

1 0

[Dovecot] Locked index file
by Kevin Cramer 25 Jun '04

25 Jun '04

I have docevot 0.99.10.6 installed on OpenBSD 3.5 and I'm using it with Squirrelmail. I tried to empty my Trash folder and it timed out. It looks like the process or thread died but the lock wasn't removed: Jun 25 09:16:30 plato imap(kevin): Timeout while waiting for release of shared fcntl() lock for index file /home/kevin/Maildir/.Trash/.imap.index How can I free this lock? I have tried stopping and re-starting dovecot already but that didn't help. Also, is there something I should do to prevent this in the future? The OpenBSD package sets the default locking to fcntl for mbox. I'm not sure if that is the setting that also controls the locking mechanism on the index files. Thanks, Kevin

1 0

[Dovecot] IMAP mailing archives back online
by Timo Sirainen 24 Jun '04

24 Jun '04

Read-only mboxes seem to be working nicely now, so I installed latest CVS Dovecot to dovecot.org again to serve them. Allows either ANONYMOUS SASL logins, or plaintext logins with "anonymous" user and empty password.

1 0

[Dovecot] Sym links to subfolders?
by Kevin Cramer 24 Jun '04

24 Jun '04

I just installed dovecot 0.99.10.6 and I'm trying to use symlinks for subfolders. I have my mail in ~/Maildir and I want to make symlinks such as from .Sent to ~/Mail/Sent. All of these folders are maildir and the permissions are correct. I've searched the list and I cannot find anything stating that it should not work. In fact I've seen posts that claim it should work. However, it does not work for me and looking at maildir-list.c around line 101, it appears that it is only checking for directories and not for links. I'm doing this because I have it setup so I can use mutt directly against the maildir folders and so IMAP will work against them. It's worked great for over a year but I want to move it to a different machine and I wanted to switch from courier-imap to dovecot. Can anyone confirm that it works or not? Any ideas on how to address this issue? Thanks, Kevin

2 1

[Dovecot] Re: [ismail] Re: using Dovecot
by Steven Stern 24 Jun '04

24 Jun '04

On Wed, 23 Jun 2004 18:26:01 +0000, "Kelley Reynolds" <kelley(a)insidesystems.net> wrote: > >I've never used dovecot, but I know that those directories aren't what IMAP servers generally expect when looking for a rootfolderpath. > >For example, courier is always 'INBOX', uw-imap is usually but not always 'mail', and sometimes it's just a blank string. My guess is that for you, it's one of those three. If your mail is in a 'mail' directory, I suggest just putting 'mail' and not '~/mail'. > >Kelley Reynolds >President >Inside Systems, Inc > >___________________________________________________________________ I'm going to cross post this to the dovecot list in case someone there has an idea. To bring those people up to speed: I'm evaluating ISMail (www.insidesystems.net) as a replacement for IMP. I'm having problems configuring the IMAP settings to work with Dovecot. === I've got some progress. I set rootmailfolder to "~/mail". When I login to ISMail, it creates the directory ~/inbox as follows: mail Sent Items then dies. If I set rootmailfolder to as "rootmailfolder=" with no argument, it creates .imap INBOX .customflags .imap.index.data .imap.index.tree .imap.index .imap.index.log then dies If I set rootmail folder to "INBOX" INBOX Sent Items .subscriptions .imap INBOX .customflags .imap.index.data .imap.index.tree .imap.index .imap.index.log -- Steve

2 1

[Dovecot] customflags considered a folder?
by Peter Schuller 24 Jun '04

24 Jun '04

Hello, i just switched from courier-imap to dovecot on a machine. The transition was painless except for one issue - when using the "Check mail" feature of kmail, one gets the message: "Unable to get information about folder customflags. The server replied: internal error..." So it looks like the server isn't properly hiding the .customflags file for some reason. I googled and only found one person who had seen something similar, but no solution. This is with dovecot 0.99.10.5. Similarly, 'customflags' does show up as a folder when using mutt. How would I go about preventing this problem? Thanks! -- / Peter Schuller, InfiDyne Technologies HB PGP userID: 0xE9758B7D or 'Peter Schuller <peter.schuller(a)infidyne.com>' Key retrieval: Send an E-Mail to getpgpkey(a)scode.org E-Mail: peter.schuller(a)infidyne.com Web: http://www.scode.org

2 5

[Dovecot] 1.0-test20
by Timo Sirainen 22 Jun '04

22 Jun '04

http://dovecot.org/test/ One more for today :) Again mostly mbox fixes and optimizations. Don't try it with maildir because it crashes with COPY and APPEND commands. This release supports now UIDPLUS extension. It was mostly a side effect of making saving mails store the X-UID header immediately to mbox and adding the mail to index. So, a Dovecot LDA would finally make sense now. Besides keeping indexes updated, it could also ask user's home dir, uid and gid from dovecot-auth. Now, that combined with postfix-dovecot-auth patch, Dovecot would be very simple to install with Postfix :)

2 2

[Dovecot] Compile error
by Greg T. Harber 22 Jun '04

22 Jun '04

On dovecot-1.0-test21: gcc -DHAVE_CONFIG_H -I. -I. -I../.. -I../../src/lib -I../../src/lib-auth -DPKG_RUNDIR=\""/usr/local/var/run/dovecot"\" -DSBINDIR=\""/usr/local/sbin"\" -I/usr/local/include -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -c ssl-proxy-gnutls.c ssl-proxy-gnutls.c:11:2: #error broken currently ssl-proxy-gnutls.c:310: error: conflicting types for `ssl_proxy_new' ssl-proxy.h:12: error: previous declaration of `ssl_proxy_new' ssl-proxy-gnutls.c: In function `ssl_proxy_new': ssl-proxy-gnutls.c:319: warning: passing arg 2 of `gnutls_transport_set_ptr' makes pointer from integer without a cast ssl-proxy-gnutls.c: In function `read_dh_parameters': ssl-proxy-gnutls.c:417: warning: `gnutls_dh_params_set' is deprecated (declared at /usr/local/include/gnutls/compat8.h:82) ssl-proxy-gnutls.c: In function `read_rsa_parameters': ssl-proxy-gnutls.c:443: warning: `gnutls_rsa_params_set' is deprecated (declared at /usr/local/include/gnutls/compat8.h:77) make[3]: *** [ssl-proxy-gnutls.o] Error 1 On dovecot-0.99.10.6: gcc -DHAVE_CONFIG_H -I. -I. -I../.. -I../../src/lib -DPKG_RUNDIR=\""/usr/local/var/run/dovecot"\" -DSBINDIR=\""/usr/local/sbin"\" -I/usr/local/include -g -O2 -Wall -W -Wmissing-prototypes -Wmissing-declarations -Wpointer-arith -Wchar-subscripts -Wformat=2 -Wbad-function-cast -c ssl-proxy-gnutls.c ssl-proxy-gnutls.c: In function `ssl_handshake': ssl-proxy-gnutls.c:280: warning: implicit declaration of function `gnutls_handshake_get_direction' ssl-proxy-gnutls.c: In function `initialize_state': ssl-proxy-gnutls.c:302: warning: implicit declaration of function `gnutls_cert_type_set_priority' ssl-proxy-gnutls.c: In function `ssl_proxy_new': ssl-proxy-gnutls.c:318: warning: passing arg 2 of `gnutls_transport_set_ptr' makes pointer from integer without a cast ssl-proxy-gnutls.c: In function `read_dh_parameters': ssl-proxy-gnutls.c:416: warning: `gnutls_dh_params_set' is deprecated (declared at /usr/local/include/gnutls/compat8.h:82) ssl-proxy-gnutls.c: In function `read_rsa_parameters': ssl-proxy-gnutls.c:442: warning: `gnutls_rsa_params_set' is deprecated (declared at /usr/local/include/gnutls/compat8.h:77) ssl-proxy-gnutls.c: In function `ssl_proxy_init': ssl-proxy-gnutls.c:508: warning: implicit declaration of function `gnutls_certificate_allocate_cred' ssl-proxy-gnutls.c:520: error: void value not ignored as it ought to be ssl-proxy-gnutls.c:523: error: void value not ignored as it ought to be ssl-proxy-gnutls.c: In function `ssl_proxy_deinit': ssl-proxy-gnutls.c:545: warning: implicit declaration of function `gnutls_certificate_free_cred' make[3]: *** [ssl-proxy-gnutls.o] Error 1 Environment: Solaris 8 (2.8) gnutls 1.0.13 gcc -v Reading specs from /usr/local/lib/gcc-lib/sparc-sun-solaris2.8/3.3/specs Configured with: ../configure --disable-nls --with-as=/usr/ccs/bin/as --with-ld=/usr/ccs/bin/ld Thread model: posix gcc version 3.3 Process: # ./configure # make

3 2

[Dovecot] Update: Compile error
by Greg T. Harber 22 Jun '04

22 Jun '04

Offending lines in src/login-common/ssl-proxy-gnutls.c 519 ret = gnutls_certificate_set_dh_params(x509_cred, dh_params); 520 if (ret < 0) 521 i_fatal("Can't set DH parameters: %s", gnutls_strerror(ret)); 522 ret = gnutls_certificate_set_rsa_params(x509_cred, rsa_params); 523 if (ret < 0) 524 i_fatal("Can't set RSA parameters: %s", gnutls_strerror(ret)); Problem: gnutls.h lists these two functions as returning void Solution: remove the ret and the check code Compilation continue but link fails: Undefined first referenced symbol in file gnutls_cert_type_set_priority ../login-common/liblogin-common.a(ssl-proxy-gnutls.o) gnutls_certificate_allocate_cred ../login-common/liblogin-common.a(ssl-proxy-gnutls.o) gnutls_certificate_free_cred ../login-common/liblogin-common.a(ssl-proxy-gnutls.o) gnutls_handshake_get_direction ../login-common/liblogin-common.a(ssl-proxy-gnutls.o) Solution: Add #include "/usr/local/include/gnutls/compat4.h" to ssl-proxy-gnutls.c Successful compile afterwards. -- Greg T. Harber gth(a)cs.sfasu.edu Director, McGee Computing Laboratory 936 468-2508 Department of Computer Science P.O. Box 13063 Stephen F. Austin State University Nacogdoches, TX 75962 USA

1 0

[Dovecot] 1.0-test21
by Timo Sirainen 22 Jun '04

22 Jun '04

http://dovecot.org/test/ Should work again with maildir. - Some bugfixes to indexes (possibly fixing the still persisting maildir sync errrors?) - Enabled cache file again. If client asks about something that can be cached for future, it's done. There's currently no smart logic about when not to do it or when to cache more than was asked for future use. Currently nothing is ever deleted from cache. Currently it's disabled if mmap_disable = yes. - Removed UIDPLUS extension after all. It needs more thinking with maildir, because for performance reasons new messages are given UIDs once at the end transaction rather than separately for each one. So, the UID would have to be 0 temporarily until transaction is committed. But the current API make the new messages visible without syncing, and then the sequences don't match anymore and we can't get the UIDs. So, this one needs thinking, mostly from API designing point of view.

8 25

[Dovecot] LDAP Bind
by Hervé Commowick - NewSports 22 Jun '04

22 Jun '04

hi all 2 Questions : - how not using the authentication bind feature of ldap server ? i rewrite checkpassword-ldap recently to use in bincimap server, and it take 3 lines to do this, so i don't understand how you don't use it. it is more powerful and more secure than retrieve pasword from the base and use crypto api to compare it. - is the dovecot server support the IMAPdir feature like bincimap or not ? thx for this great software, who replace my imap and pop3 server when it support that :) Vr.

3 6

[Dovecot] Delete message
by Marius Stan 22 Jun '04

22 Jun '04

Hello, I'm seeing that our favourite pop3 server only deletes the messages upon logoff: dele 1 +OK Marked to be deleted. quit +OK Logging out, messages deleted. Connection closed by foreign host. This is causing me some trouble with a certain webmail app. Is there a way I can instruct Dovecot to immediatelly delete a message ? 10x, Marius

2 1

[Dovecot] proxy plugin
by Timo Sirainen 22 Jun '04

22 Jun '04

I've updated the proxy plugin at http://dovecot.org/patches/1.0/quota.c. It doesn't exactly work, even against latest CVS Dovecot as it crashes in save/copy, but it shows how it's basically going to work. Pretty ugly to do objects with C, but works.. If you're interested about writing support for some specific quota backend (maildir++, sql, ..), now would be a good time to begin :) Well, the reason it crashes is because it needs to find out the message's size, but Dovecot doesn't yet really like being asked about messages that haven't been committed to index. I guess that needs to change, hopefully won't require too large changes. I think I'm going to merge mail-index-view and mail-index-transaction into same thing..

1 1

[Dovecot] I/O Leak?
by Paul McMurphy 22 Jun '04

22 Jun '04

Is the I/O leak message normal? (from syslog) Jun 22 02:12:39 xbox pop3(paul): lstat(/var/mail/Maildir/paul/INBOX/cur) failed: Permission denied Jun 22 02:12:39 xbox pop3(paul): lstat(/var/mail/Maildir/paul/INBOX/cur) failed: Permission denied Jun 22 02:12:39 xbox pop3: I/O leak: 0x8050ce0 (0) Jun 22 02:12:39 xbox pop3: I/O leak: 0x8084b10 (1) Jun 22 02:13:22 xbox pop3-login: Login: paul [192.168.1.10] Jun 22 02:13:23 xbox pop3(paul): lstat(/var/mail/Maildir/paul/INBOX/cur) failed: Permission denied Jun 22 02:13:23 xbox pop3(paul): lstat(/var/mail/Maildir/paul/INBOX/cur) failed: Permission denied Jun 22 02:13:23 xbox pop3: I/O leak: 0x8050ce0 (0) Jun 22 02:13:23 xbox pop3: I/O leak: 0x8084b10 (1) Oh... and any hints on the permissions problem would be ok also. ;) Debian 1.0.1 / dovecot 0.99.10.6-1 Thanks!

2 1

[Dovecot] The Status: header is forced
by Olivier Tharan 21 Jun '04

21 Jun '04

Hi, I started testing dovecot for our next POP/IMAP server (nearing production state), and noticed that the Status: header is always added, with a value of 'O' or 'RO'. This happens in `lib-index/mbox/mbox-rewrite.c'. This does not seem to happen in the Maildir case. Is the Status: header really needed in every case? This breaks mutt which displays mails with a 'O' flag instead of 'N'. My dovecot is 0.99.10.4 (FreeBSD port), but the behavior is still the same in the CVS version. -- olive

3 6

[Dovecot] 1.0-test19
by Timo Sirainen 21 Jun '04

21 Jun '04

http://dovecot.org/test/ I'm finally using this release myself with mboxes. So far no crashes or corruption. :) - several mbox fixes and optimizations - maildir syncing fix - solaris fixes - create mbox root dir if it doesn't exist

2 3

[Dovecot] 0.99.10.6 released
by Timo Sirainen 20 Jun '04

20 Jun '04

Since no-one have complained about previous RCs, I guess it's release time. Since -rc2 I added the ioloop.c assert fix, and 64bit Solaris fix. Here's the full change summary again: v0.99.10.6 2004-06-20 Timo Sirainen <tss(a)iki.fi> + SHA1 password support using OpenSSL crypto library + mail_extra_groups setting + maildir_stat_dirs setting + Added NAMESPACE capability and command - Autocreate missing maildirs (instead of crashing) - Fixed occational crash in maildir synchronization - Fixed occational assertion crash in ioloop.c - Fixed FreeBSD compiling issue - Fixed issues with 64bit Solaris binary

2 1

[Dovecot] Re: [dovecot-cvs] dovecot/src/lib fdpass.c,1.28,1.29
by Charlie Allom 20 Jun '04

20 Jun '04

Will this perhaps fix these? imap-login: Jun 15 12:28:16 Panic: file ioloop.c: line 90: assertion failed: (i o->fd <= current_ioloop->highest_fd) dovecot: Jun 15 12:28:16 Error: child 17987 (login) killed with signal 6 imap-login: Jun 15 13:14:58 Panic: file ioloop.c: line 90: assertion failed: (i o->fd <= current_ioloop->highest_fd) dovecot: Jun 15 13:14:58 Error: child 13002 (login) killed with signal 6 On Tue, Jun 15, 2004 at 02:42:25AM +0300, cras(a)procontrol.fi wrote: > Update of /home/cvs/dovecot/src/lib > In directory talvi:/tmp/cvs-serv11171 > > Modified Files: > fdpass.c > Log Message: > Solaris fix by Tim Hurman > > > > Index: fdpass.c > =================================================================== > RCS file: /home/cvs/dovecot/src/lib/fdpass.c,v > retrieving revision 1.28 > retrieving revision 1.29 > diff -u -d -r1.28 -r1.29 > --- fdpass.c 1 Dec 2003 19:07:34 -0000 1.28 > +++ fdpass.c 14 Jun 2004 23:42:23 -0000 1.29 > @@ -31,12 +31,20 @@ > #include <sys/uio.h> > > #ifndef CMSG_SPACE > -# define CMSG_ALIGN(len) \ > +# if defined(_CMSG_DATA_ALIGN) && defined(_CMSG_HDR_ALIGN) /* for Solaris */ > +# define CMSG_ALIGN(len) _CMSG_DATA_ALIGN(len) > +# define CMSG_SPACE(len) \ > + (_CMSG_DATA_ALIGN(len) + _CMSG_HDR_ALIGN(sizeof(struct cmsghdr))) > +# define CMSG_LEN(len) \ > + (_CMSG_HDR_ALIGN(sizeof(struct cmsghdr)) + (len)) > +# else > +# define CMSG_ALIGN(len) \ > (((len) + sizeof(size_t) - 1) & ~(sizeof(size_t) - 1)) > -# define CMSG_SPACE(len) \ > +# define CMSG_SPACE(len) \ > (CMSG_ALIGN(len) + CMSG_ALIGN(sizeof(struct cmsghdr))) > -# define CMSG_LEN(len) \ > +# define CMSG_LEN(len) \ > (CMSG_ALIGN(sizeof(struct cmsghdr)) + (len)) > +# endif > #endif > > #ifdef SCM_RIGHTS > -- .signature 0x14AA7941

2 4

[Dovecot] 0.99.10.5 released
by Timo Sirainen 19 Jun '04

19 Jun '04

One more bugfix since rc2: - Maildir: synchronization might have sometimes set wrong flags to messages, or crash completely Quite rare because we were lucky before :) And list of all the changes one more time: v0.99.10.5 2003-12-27 Timo Sirainen <tss(a)iki.fi> + MySQL authentication, patch by Matthew Reimer + --with-moduledir configure option - mbox: APPEND reversed given \Draft and \Deleted flags - mbox: "LF not found" errors happened sometimes when X-IMAPbase header was updated. Possibly corrupted mbox sometimes. Thanks to Fabrice Bellet for finding this bug. - Custom flags couldn't be unset - Maildir: make sure ":2," is appended to filename when moving mails from new/ to cur/. - Maildir: synchronization might have sometimes set wrong flags to messages, or crash completely - Maildir: RENAME xx inbox.xx didn't result as uppercased ".INBOX.xx" directory which then couldn't be accessed - Don't crash with RAND_bytes() error messages anymore. This mostly happened with Fedora/RedHat.

6 13

[Dovecot] 1.0-test17
by Timo Sirainen 19 Jun '04

19 Jun '04

http://dovecot.org/test/ Just mbox fixes since 1.0-test16. The logic is simpler and more correct now. Can anyone break it anymore? I actually tested it a while with Evolution and several mailboxes and it didn't break at least immediately. :) Now maybe a few more days and I dare trying this thing myself with my real mboxes (yes, I'm still using them). Dovecot mailing list archives could soon be served with 1.0-tests too, as soon as I get support for read-only mboxes working again (storing and comparing MD5 summed headers).

5 17

[Dovecot] 1.0-test18
by Timo Sirainen 19 Jun '04

19 Jun '04

http://dovecot.org/test/ Again mostly just mbox fixes. The good thing is that the code is only getting cleaner and more understandable with every release. But I think it's clean enough now that this release should work :) It also has checkpassword passdb support. Supporting it as userdb isn't yet implemented. I think I'll make some generic caching thingy, so that if passdb is same as userdb, they both could be queried from database in one query. Probably by allowing pass_query/pass_filter to return them.

1 0

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

19 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