- dovecot - dovecot.org

[Dovecot] disabling indexes?
by Marten Lehmann 02 May '05

02 May '05

Hello, I recently had the problem, that an index was corrupt. Thus, messages haven't been listed (talking about POP3), but still remained in the filesystem. As there is no SEARCH-command in POP3, dovecot didn't notice that the index is corrupt and didn't rebuild it. The problem is, that a user can't delete messages through POP3 which aren't listed by dovecot. If the maildir size increases, the arrival of new messages will be blocked because the mailbox is full. And the user has no chance to delete it. Regards Marten

1 0

[Dovecot] Blank lines in mailboxes
by Jakob Curdes 30 Apr '05

30 Apr '05

Hello, we use dovecot on a regular basis. Sometimes I end up with a user telling me he does not get mail. When I look after the problem, I always find leading blank lines in the mbox file. We are using postfix with dovecot and amavisd as spam scanner. Amavisd never accesses the mbox files directly so this can be ruled out. I suspected procmail but now it happened also with accounts where no procmail is active. I found only a list thread where this happened always, i.e. it was a configuration error. (Meaning the mailbox was correct but dovecot would not read it). Here ist is only occasionally and therefore hard to track . Does anybody have the same problem or has hints to a solution ? We are running postfix 2.1.4 and dc 0.99.10.6 ; just now I am upgrading to pf 2.2.2. and dc 0.99.14. Yours, Jakob Curdes

5 21

[Dovecot] Fresh Dovecot Install
by GPL 29 Apr '05

29 Apr '05

Working on an RH9 box. Did not use yum. Downloaded the "dovecot-stable-latest.tar.gz". Uncompressed it, downloaded and installed gcc. Ran the following: ./configure make sudo make install Seemed to have done its thing. I'll admit I am not well versed in using "make" or compiling anything. When I install I usually use yum on fedora machines. This one being an RH9 machine I have plugged yum into the fedora legacy project and it did not let me install dovecot via yum. So I opted for this route. Regardless, if I run 'which dovecot' I see "/usr/local/sbin/dovecot" However now I do not seem to be able to see it run. I get nothing when I: rpm -qa | grep dovecot ps aux | grep dovecot service dovecot status SO AM HAVE MISSED SOMETHING! Is there another script I need to run? Suggestions welcome. Thanks, George

5 8

[Dovecot] error: received another "not listening" notification
by Andreas Goertz 29 Apr '05

29 Apr '05

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, i got a problem with dovecot 0.99.14 - after a while of checking pop3 periodically, the dovecot-auth process gets killed. Some clients, e.g. outlook (express), then requests for reentering the password. When this happens, i see something like this in th elogs: Apr 28 14:53:45 marge dovecot: child 25819 (auth) killed with signal 4 Apr 28 14:55:09 marge dovecot: login: received another "not listening" notification (if you can't login at all, see src/lib/fdpass.c) Any idea, how to solve this? Thanks in advance, Andreas Goertz. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFCcOjTpAOZWzj6viQRAtz+AKCjfTe3ib3tsBUeqZjTuLY/hcJ2mACgqePc /T4TGvBNzmY0snTpOMHuUdE= =t5Ev -----END PGP SIGNATURE-----

1 1

[Dovecot] dovecot 0.99.xx to 1.0-stable how-to?
by Rich West 28 Apr '05

28 Apr '05

I realize that there have been some big changes in features and configuration file settings between 0.99.xx and 1.0-stable, so when I went to perform an upgrade on our testing server, I carefully combed through the configuration files and matched up everything I could. I fired up dovecot-1.0-stable and was pleased to see that it was happily running. I attempted to connect to it, and discovered that it wasn't listening to any ports.. then I realized that the app had crashed due to a typo in the config file (oops). Fixed that, started it up, and it was happily running and listening. However, it wouldn't authenticate any users.. Backing down to the 0.99.14 version that we had installed allowed for authentication (against ldap) to work just fine.. Is there anything that I should be looking for within the dovecot-1.0-stable that is dramatically different in regards to user authentication? -Rich

3 5

[Dovecot] Root uid
by Chris L. Franklin 28 Apr '05

28 Apr '05

Whats the easy'est way to mod the source to allow the statis uid and or gid or of the users be root ? PS. I do wish this was an admin set-able option in the dovecot.conf -- Chris L. Franklin --

3 2

Re: [Dovecot] Root uid
by Curtis Maloney 28 Apr '05

28 Apr '05

Chris L. Franklin wrote: >> Honestly, why do you want it to be root? It's NOT a good idea, even >> though Dovecot has so far shown to be very secure. > > > I disagree, strongly To which statement? That using root is not a good idea, or that Dovecot has shown to be secure? >> I thought the only thing stopping this (apart from good sense) is the >> minimum UID setting in the config file? > > Nope it's in the source to disallow it Oh, ok. Well, I'm not surprised. It's generally considered a bad practice. > PS. On the good sense part, It's way I use SELinux. I could just hand > out root's login on my box and not worry. > From what I understand, SELinux is a special case. What I've been told of it, it's an interesting idea, with much merit. I don't know enough to say either way. Maybe I'll take a closer look after I've finished delving into Sun's RBAC. As for the code changes, from memory the UID checking stuff is all in the one place ( in 0.99.14 it seems to be src/lib/restrict-access.c ). I'm not sure about 1.0... we'll move to that when we can have custom flags :) -- Curtis

1 0

[Dovecot] Assertion Failures in Current CVS version
by Todd Burroughs 28 Apr '05

28 Apr '05

I've attached a few assertion errors in imap. Any fixes or advice on where to look are appreciated. This is with the CVS version, current as of April 27. Todd Burroughs

1 0

[Dovecot] cutting everything after @
by Juraj Bednar 27 Apr '05

27 Apr '05

Hello, I am migrating one server to dovecot. The only problem is, that users have logins with @domain as part of their user name. I want to use pam auth (for other reasons, if only for dovecot, I would use mysql, but I need the same password db to be used for other services, like samba). Is there a way to allow this type of login? Just cut everything beginning with @. I can change the source code, but then I don't get nice automatic upgrades. Or can this be done easily with PAM? Thanks, Juraj.

7 7

[Dovecot] Shared mailboxes and accessing MailDir not through IMAP
by Steffen Kaiser 27 Apr '05

27 Apr '05

Hello, I'm testing Dovecot that is part of Debian/sarge (v0.99.14-1). So far so good. I have migrated some mailboxes for testing with success and seems that everything works fine. One thing I do not figure out is, what to do about shared mailboxes, which are the very reason of searching for an alternative IMAP server, The Wiki states that there is some sort of shared mailboxes, based upon symlinks. Well, but since which version actually?? The Changelog stops at 2003-11-08 21:12 ? What I need is a mailbox (maildir) for a contact address (not a real shared mailbox, but several users shall be able to read a mail and delete it after processing). For this, one needs write permission to the mails therein only, the MDA takes care of to make the mails readable for the group. It would be good to see, if somebody had answered a mail already, but that's not required. What I tried is this: I setup all Unix-permissions of the folders (. cur new tmp: u=rwx,g=srwx) and their parents (u=rwx,g=x). Then I placed a symlink into the maildir of all users. Each user caches the INDEXes into an individual /var/ directory, not in the maildirs themselves. (BTW: I wonder why I need to give the group write permission to the base directory '.'). The mailbox shows up and is read-write. Now I wonder, what impact I'm to expect here? Esp. "The only problem is that currently everyone's message flags would be shared as well." (quote from a message of a thread taken from the Wiki) Then there is http://dovecot.org/pipermail/dovecot/2003-March/001113.html the third item will apply to my situation, I guess. MailDir is (sort of) expected to be read by mutt directly, for instance. Because the mailboxes are located within the users home directories, some of them do this. Do this item mean that Dovecot is NOT expecting that mails are deleted in any other way than through itself? Otherwise Dovecot would find a change in the mailbox and rebuilt the index file regardless whether the change had been originated by another IMAP client or by directly manipulating the maildir. Bye, -- Steffen Kaiser

4 3