- dovecot - dovecot.org

[Dovecot] Dovecot Deliver Problem
by Marc Perkel 15 Sep '05

15 Sep '05

Trying to use the deliver utility and getting this error: error: net_connect(/var/run/dovecot/auth-master) failed: No such file or directory -- Marc Perkel - marc(a)perkel.com Spam Filter: http://www.junkemailfilter.com My Blog: http://marc.perkel.com

4 9

[Dovecot] Re: mailbox corruption
by Yannick Majoros 14 Sep '05

14 Sep '05

Kelly Sauke wrote: >Wietse Venema wrote: > > > >>Yannick Majoros: >> >> >> >> >>>>What else is accessing the mailbox files? Any scripts running around >>>>that access mail without proper file locking, like scripts that >>>>replicate mail to another box? >>>> >>>>Whay file system is being used? >>>> >>>>If you can't figure out which is broken, then you'll have to use >>>>maildir files. >>>> >>>> >>>> >>>> >>>> >>>No scripts. If amavisd-new is safe, then nothing else should access >>>mailboxes. Only via dovecot POP3/IMAP. Do you think it is worth to go >>> >>> >>> >>> >>amavisd-new accesses mailboxe files, and what file locking >>mechanism would that be using? >> >> Wietse >> >> >> >> >> >For what its worth, I'm seeing the exact same corruption as Yannick is >talking about and the only two pieces of software installed on my >machine are postfix and dovecot. One of those two is the culprit, not >sure which one. > > > Yep, I would think the same. This is not an evidence, but a strong doubt: the same problem is still present after replacing MailScanner by amavisd-new. It could be that it happens less often, although, but I need some time to make real stats... -- ---------------------------------------------------------------------- Yannick Majoros http://www.inma.ucl.ac.be/~majoros Informaticien AUTO-INMA/FSA/UCL CSAM 4, avenue G. Lemaître B-1348 Louvain-la-Neuve Belgium Tel: +32-10-47.80.10 Fax: +32-10-47.21.80 #JAPH : http://www.inma.ucl.ac.be/~majoros/japh.txt Si vous avez des problèmes pour afficher ce message (accents qui ne passent pas, signature électronique, ...) votre système de mail n'est pas conforme aux standards, voir http://www.inma.ucl.ac.be/~majoros/email.html ----------------------------------------------------------------------

3 2

[Dovecot] web-based mail
by str tux 14 Sep '05

14 Sep '05

Hello List, I just installed dovecot and i love the simplicity of the default config; it simply works. Now I want to setup and web-based in addition to the default pop3 and imap client access - what u guys can recommend? Thanks. str

8 11

[Dovecot] Dovecot-LDA problems (CVS version) Signal 11 and empty 'mail' dir
by Steffen Kaiser 14 Sep '05

14 Sep '05

Hello, I'm trying dovecot-lda (deliver.c has CVS version 1.18). When I try to deliver a mail, an empty directory is created name $HOME/mail. This is neither the configured (via LDAP) nor the default "mail" setting in the /usr/local/etc/dovecot-deliver.conf. When the $HOME directory does not exist, but the user itself: Sep 1 11:47:12 localhost deliver: mbox: Can't create root IMAP folder /home/skaise2a/mail: Permission denied Sep 1 11:47:13 localhost sm-mta[4684]: j819lCgd004682: SYSERR(root): mailer local died with signal 11 Default mail: mail = maildir:%h/.mailboxes:INDEX=/usr/local/var/spool/dovecot/indexes/%Lu Configured via LDAP for user skaise2a: maildir:/mailcache/skaise2a:INDEX=/var/cache/dovecot/indexes/skaise2a:CONTROL=/var/cache/dovecot/control/skaise2a I have only found the error message in dovecot's src/lib-storage/index/mbox/mbox-storage.c function create_root_dir(). The Dovecot logs indicate that dovecot-lda is requesting the information from it and the message is - once the empty directory could be created - delivered into the configured IMAP root. Bye, -- Steffen Kaiser

2 2

[Dovecot] mailbox corruption
by Yannick Majoros 14 Sep '05

14 Sep '05

Hello, Here is the description of a problem we habe been having for some time. Originally posted on the postfix-users mailing list, but no solution found to date. >>>> We have been having problems with our mail system for a couple of >>>> months. Every now and then, some mailboxes get corrupted: a >>>> half-truncated message, usually without headers, is at the beginning >>>> of the mailbox, causing it to become unaccessible. >>>> >>>> For information, we use: >>>> >>>> - fedora core 4 >>>> - postfix-2.2.2-2 rpm >>>> - dovecot-0.99.14-4.fc4 rpm >>>> - mailscanner-4.36.4-1 rpm >>>> >>>> >>> >>> This ^^^^^^^^^^ is probably your problem. >>> >>> >> > > I wouldn't be so quick to blame mailscanner. I have fc4, postfix rpm > and dovecot. Nothing else and I get the same corruption he is talking > about. > > > Ok, I removed MailScanner and I still have the very same problem. Locking _does_ work for postfix and dovecot (discussed with Wietse, partly by mail). Any idea? As an alternative, is there a way of handling the problem better? Dovecot just locks on these corrupt mailboxes :-/ I didn't try Dovecot 1.0, as it is alpha and I don't have any package for that anyway (production system :-/ ). Thank you, -- ---------------------------------------------------------------------- Yannick Majoros http://www.inma.ucl.ac.be/~majoros Informaticien AUTO-INMA/FSA/UCL CSAM 4, avenue G. Lemaître B-1348 Louvain-la-Neuve Belgium Tel: +32-10-47.80.10 Fax: +32-10-47.21.80 #JAPH : http://www.inma.ucl.ac.be/~majoros/japh.txt Si vous avez des problèmes pour afficher ce message (accents qui ne passent pas, signature électronique, ...) votre système de mail n'est pas conforme aux standards, voir http://www.inma.ucl.ac.be/~majoros/email.html ----------------------------------------------------------------------

3 3

[Dovecot] Solaris build failed
by GARY GENDEL 14 Sep '05

14 Sep '05

dovecot-v1.0-alpha build failed for Solaris 11 (OpenSolaris Nevada). The problematic line is in socket.c line 228. The fix should be to change SOL_TCP to IPPROTO_TCP found in netinet/in.h. This change should work universally on all platforms. Gary

2 1

[Dovecot] what does this mean: Warning: Error in custom flags file / Corrupted Indexes
by rick tait 13 Sep '05

13 Sep '05

Hi everyone: I am seeing a whole LOT of these messages in my dovecot logfile: imap(rickt): Sep 12 17:14:03 Warning: Error in custom flags file / home/rickt/mail/.imap/TRASH/.customflags: Duplicated ID 0 imap(rickt): Sep 12 17:14:03 Warning: Error in custom flags file / home/rickt/mail/.imap/TRASH/.customflags: Duplicated ID 1 and also these: imap(mbwnews): Sep 12 17:10:16 Error: Corrupted index file /home/ mbwnews/mail/.imap/INBOX/.imap.index: used_file_size larger than real file size (2016 vs 1608) imap(mbwnews): Sep 12 17:10:18 Error: Corrupted index file /home/ mbwnews/mail/.imap/INBOX/.imap.index: used_file_size larger than real file size (2016 vs 1608) And not just referring to my inbox, other users as well. I hava bog standard install of 0.99.10.8, on an openbsd 3.6 box. every now and then i get an error from my or my users' IMAP email client saying that it couldn't access a particular inbox. a few clicks of "OK" or "Cancel" etc and the problem seems to go away. all kinds of errors (similar to above) in the imapd logfile though, seem to correspond with the timing of the abovementioned IMAP mail client errors. one thing: my users DO use procmail, so there is a chance that their IMAP client might have a mailbox open that procmail may be trying to append to. i wonder if this is a locking issue? i guess what i'm asking is - 2 thing: 1) how can i get these pesky imap client errors to go away so my users mailboxes can be successfully selected? 2) what do the indexing errors mean? are the 2 things related? Thanks so very much in advance everyone! Best, Rick. rick tait | e: rickt(a)rickt.org | t: 323.829.5703

1 0

[Dovecot] Changing location of dovecot.conf file
by Andy Cravens 12 Sep '05

12 Sep '05

I've been looking through the configure options and can't seem to find a place to specify where dovecot.conf lives. I want the default location to be in /etc and not under the dovecot install directory tree. -- Andy

2 1

[Dovecot] An alternate "dovecot-auth" daemon using cyrus-sasl
by buc 12 Sep '05

12 Sep '05

We use dovecot in a heterogeneous environment (Windows/Linux desktops and Linux servers). For unified authentication we use a sheaf "Samba/Openldap" (i.e., Samba NT domain with openldap backend and pam/nss_ldap for Linux). Windows users are authenticated well everywhere, but there is one old issue. As "SPA" (NTLM) against NT domain is not supported by dovecot, it is necessary to use default "plain" method. In addition to security problems, it does also a problem of password unification. Each time a user changes the password, he should do it one more time for the mail program. I know that dovecot supports NTLM, however against local database only (not for NT domain controller). In early versions support of cyrus-sasl (which supports NTLM now) had been incorporated, however it like not work and now is removed. Fortunately, there is a possibility to substitute dovecot-auth executable. Therefore I have tried to make an alternate variant of dovecot-auth, which supports all that we need. For us, it seems to be more useful to create an auth daemon using cyrus-sasl, rather than to add domain support to existing ntlm code. First of all, it is easier for implementation. Besides it enables use of all mechanisms supported by cyrus-sasl (present and future), including GSSAPI. Anyway, it will be the useful additive to dovecot. I have made appropriate patches for both dovecot-1.0-stable and dovecot-1.0.alpha1. The idea is to copy "src/auth" to "src/auth-cyrus", strip all unneeded from newly created directory and add cyrus-sasl support. The resulting code probably looks not so elegantly as if it has been written separately, however this way allows to not make a lot of things from the scratch. The patch against 1.0.alpha1 is here: http://dmitry.butskoy.name/dovecot/dovecot-1.0.alpha1-cyrus.tar.gz . To be more readable, it is not a flat patch (due to a lot of whole files add/remove). It is a tarball with 3 files: a list of files to initial copy from auth/ to auth-cyrus/, a patch for resulting tree, and a script which automates this steps (:-)). (The script should be run in the root of the main source, i.e. a dir with src/ and doc/ subdirs). I already have successfully tested this patch with PLAIN method. However before testing of other methods, it would be desirable that somebody have looked at it. Whether someone could check up my patch (just fluently having read), at least for obvious bugs and typos? Dmitry Butskoy <Dmitry(a)Butskoy.name> Saint-Petersburg, Russia Red Hat Certified Engineer 809003662809495

4 3

[Dovecot] Dovecot feature request: move /var/mail/uid to INBOX
by Steffen Kaiser 12 Sep '05

12 Sep '05

Hello, UW-Imap has a (questional, but for me useful) feature to slurp all mails pending in /var/mail/uid into the user's INBOX whenever the user successfully logs on and the INBOX is not configured as /var/mail/uid. The usefulness for me is that users have a relatively small quota, so the noisy "over quota" messages pop up for everyone now and then, regardless how frequent one reads the mail. When I now set a large quota for the "pending INBOX", where the user (aka dovecot) can only delete mails from, I circumvent those messages, prevent that users use the (large) INBOX as yet another place to pile up data (the user does not know about the pending INBOX at all) and let the users have "full" control over their folders. The disadvantage is that it works for "real" users only. Another disadvantage is that one would expect "LDA"-features in the server portion of Dovecot, e.g. Sieve :-), or the server would need to spawn the Dovecot-LDA somehow. (Next thing is that, currently, the mails are delivered into the home directory of the users, what leads to several annoyances when someone is away for some time and finds his home directory locked, because the mass of mails locked the directory. Mostover, those IMAP servers I ran so far didn't allowed the user to delete a mail via IMAP often, because some temp or arbitary file couldn't created in the IMAP root. Because the user is already logged on onto Dovecot, there should be less problems deleting mails when the quota exceeds while slurping them in. At least I had extremly good experiences with this mechanism, when I used UW-Imap and the INBOX was located as mbx in the user's homedirectory.) Bye, -- Steffen Kaiser

1 0