similar to: (auth) killed with signal 11

I'd like a separate feature for setting umask for index and cache files differently from email files. The reason is that I'm putting indexes in a separate location and I need group create rights in directories. Otherwise what happens is that the first user creates the directories, but the second user for the domain that has a different UID gets an error. default_mail_env =

Getting an error on POP only - "Authentication Server Isn't Connected" IMAP works fine. This used to work. not sure what changed.

OK - here's whay I need to make it work for my Linuxconf compatible authentication system. First - a question: Will this work? I can find docs on "virtualfile. auth virtualfile { mechanisms = plain digest-md5 userdb = passwd-file /etc/vmail/passwd.%d passdb = passwd-file /etc/vmail/shadow.%d user = root } Then - since the dmain name selects the passwd file, if there were a

This would make my life a lot easier in migrating to Dovecot. And it should be really easy to implement. Here's how linuxconf does it: Password files are placed in the /etc/vmail directory as follows: /etc/vmail/passwd.domain1 /etc/vmail/shadow.domain1 /etc/vmail/passwd.domain2 /etc/vmail/shadow.domain2 The password and shadow files are exactly the same format as the /etc/password and

http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc6.tar.gz http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc6.tar.gz.sig This is it. The first v1.1 release that actually deserves the "release candidate" name. It contains everything I require from v1.1.0 release. There are two bugs left that I'd like to get fixed, but they won't block v1.1.0 release: *

http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc6.tar.gz http://dovecot.org/releases/1.1/rc/dovecot-1.1.rc6.tar.gz.sig This is it. The first v1.1 release that actually deserves the "release candidate" name. It contains everything I require from v1.1.0 release. There are two bugs left that I'd like to get fixed, but they won't block v1.1.0 release: *

I guess Dovecot has an LDA called deliver. What is it and how do I use it? Or is it ready to be used. can't find any docs on it. -- Marc Perkel - marc at perkel.com Spam Filter: http://www.junkemailfilter.com My Blog: http://marc.perkel.com

Feb 27 14:17:46 wurfel dovecot: imap-login: Login: user=<USER>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured Feb 27 14:17:46 wurfel dovecot: IMAP(USER): file mbox-sync-update.c: line 387 (mbox_sync_update_header): assertion failed: (ctx->mail.uid != 0 || ctx->pseudo) This is happening for dozens of users. Anyone have a suggestion of what to adjust? It was happening somewhat

OK - I thought this was going to be easy. Maybe it is. I'm just not that good at reading directions. Trying to use dsync. Getting this error: Mail locations must use the same virtual mailbox hierarchy separator (specify separator for the default namespace) Currently using maildir. The setup is as follows: mail_uid = mail mail_gid = mail mail_location =

The default_mail_env is very powerful, but .... If you have multiple databases wouldn't it make sense to have a separate mail environment for each database? For example: userdb passwd { default_mail_env = mbox:~/mail/:INBOX=/var/mail/%u } # Linuxconf passwd-like file with specified location userdb passwd-file { args = /etc/vmail/passwd.%d default_mail_env =

http://dovecot.org/nightly/dovecot-latest.tar.gz Would be nice to get some testing before the actual release. I've now finally gone through all the "TODO" mails in this list and my INBOX and fixed pretty much every problem I know of. There are still some mbox bugs, but I can't really get them fixed unless someone figures out how to reproduce them

OK - my last main bug was fixed a few releases ago. I know that there's no end to getting things right but there comes a point when you need to call it done. No one trusts a 1.0 to be perfect but Dovecot is already better that most 2.0 versions of other software. I vote (as if my vote counted) to call it done, declare victory, and move on to 1.01, 1.02 etc. No one is going to trus it till

Can't figure out why the login is slow. I telnet to port 143 on localhost. I type: 0 login user password Takes about 10 seconds and it lets me in. I'm using MYSQL and it's a small indexed database on a fast server so it's not the mysql query that's slowing it down. At least I don't think it is. But - kind of stumped. Just wondering if there's something obvious

I had our production systems running on rc23, however we ran into problems when the server was under heavy load. Eventually, the server would begin to freeze all imap connection after authentication (according to the logs). A user would connect, authentication would succeed, and then the connection would sit until timing out. No error logs were produced. Upgrading to rc24 did not

Timo, I see where at least one other person reported this, but here goes. I went from rc24 to rc25 this morning, and I got an assert and core from my own mailbox withing five minutes: Mar 2 06:52:26 karst dovecot: [ID 107833 mail.error] IMAP(jaearick): file mbox-sync-rewrite.c: line 408: assertion failed: (need_space == (uoff_t)-mails[idx].space) Mar 2 06:52:26 karst dovecot: [ID 107833

His Friends, I've been using dovecot-1.0.alpha5 for a long time, now i would like to update to v.1.0.rc24 on my Red Hat ES 4 machine, so i need an rpm version that i couldn't find on the web. Also now i can build the rpm package via SPECS, which i don't have. Plis, anybody would help? Thanks in advanced, Alfredo -------------- next part -------------- An HTML attachment was

Hi, sometimes there is a timeout, while logging in. Dovecot-rc24 Dovecot uses PAM, PAM uses a LDAP server. Solaris 10 The log, if everything is ok: auth(default): client in: AUTH 1 PLAIN service=POP3 secured lip=x.x.x.x rip=x.x.x.x resp= auth(default): client out: CONT 1 auth(default): client in: CONT<hidden> auth(default): client out: OK 1

Trying to get the master password to work. What am I doing wrong? Trying this test: /etc/dovecot.masterusers master:{plain}test auth_master_user_separator=* auth default_with_listener { mechanisms = plain passdb passwd-file { # Master users that can log in as anyone args = /etc/dovecot.masterusers master = yes #pass =yes } passdb passwd-file { # Path for

Hi, almost everything is in the subject. Server : Solaris 9 /SPARC, Dovecot 1.0.rc22 Client : Mac OS X 10.4.8 (8L2127) Kernel-Version: Darwin 8.8.1 Thunderbird is: german Version 1.5.0.9 (20061207) With OS X Mail.app, message deletion works. With Thunderbird, a warning popup appear on the desktop. English translation is about "command failed, internal error occurred".

Hi, We are currently moving from linuxconf/dovecot to a dovecot setup with sql support, the problem we currently facing is having a message sent to a aliase delivered to the user email inbox with dovecot-lda, i have created cedrict at mail.vdl and a alias test at mail.vdl, when i send to cedrict at mail.vdl the message is included in the user inbox file, but when i send to test at mail.vdl