similar to: Managesieve: first steps

Hi, I've been trying some benchmarks to compare 1.0 vs 1.1 -this is the easiest way to explain the move to my boss-, so I've compiled dovecot 1.1 and imaptest-20080627 in my secondary machine running RHEL4, with homes in NFS, indeces in local files and control files also in NFS. Then I've created 100 new users imaptest001-imaptest100, and set the password paquitoelchocolatero to

Hi, Before some major changes in our infrastructure, I was interested in the performance impact of moving indexes to our NAS (Emc Celerra v5.5). So I downloaded both dovecot-1.1.19 and dovecot-1.2.6, compiled them and wrote 2 confs for each of them, one with local indexes and another with indexes in the NAS. Then I created 19 pam users, and tested system performance this way: - uninstall

Hello, I use the debian packages from http://xi.rename-it.nl/debian/ version 1.1.7-0~auto+17 If I put a sieve script into /home/vmail/sieve-scripts/test.de/test.sieve it is used, so cmusieve works. But if I activate managesieve I get in the log: dovecot: 2008-12-14 21:24:49 Fatal: managesieve-login: USER environment missing dovecot: 2008-12-14 21:24:49 Error: managesieve-login: BYE

Hello dovecot users, I have updated the MANAGESIEVE patch to fix the currently known small problems with the protocol implementation. It is designed for rc28, but also compiles cleanly with the current cvs branch_1_0. Change Log V4 ------------- - Added managesieve_implementation_string setting to the managesieve configuration. This can be used to customize the default

Hello, I've been trying to get managesieve to work for our LAN, but when I try to login from a remote host i always get the following line in the log file: dovecot: child 26014 (login) killed with signal 11 When i enable debuging, it just gives me that line, nothing more. I can only login from the localhost through telnet but not from a remote host. My conf: # 1.1.6:

Looks like libguestfs build is broken, or not documented properly. I tried (based on http://libguestfs.org/guestfs-building.1.html): git clean -dxf ./autogen.sh autoreconf failes with: autoreconf: running: automake --add-missing --copy --no-force configure.ac:38: installing 'build-aux/missing' configure.ac:221: error: required file 'common/mlcustomize/Makefile.in' not found

Hi! Two days ago I upgraded to 1.2.15, and again I the warning "Warning: fd limit 1024 is lower than what Dovecot can use under full load" reappeared. It's a bit weird, because my actual limits are higher. From /etc/security/limits.conf * soft nofile 4096 * hard nofile 8192 root soft nofile 4096 root

Hi, I'm doing the final tests before I migrate my 10000 users from RHEL 4 + dovecot 1.1.20 to RHEL5 + dovecot 1.2.11, and I'm having some serious problems with outlook 2007 clients disconnecting very often. In dovecot's log I see lot of connects and disconnects from these clients (as oposed to my kmail, that just connects once when I come in and disconnects when I shut it off).

Hello list, I'm using Dovecot 1.0.0 on FreeBSD 6.2-RELEASE and applied the latest MANAGESIEVE patch v3 [1] which seems to have worked smoothly, i.e. all hunks succeeded and no compilation problems. Now this may be stupid question with an obvious answer, but I am at a loss at how to start the daemon? What's the binary called that starts the sieve server? Is there a special way to

Hello! I'm trying for a lot of time to make managesieve working with dovecot 1.1.17 and virtual users on openSuSE 11.1. I think I'm doing some misconfiguration, but I can't figure it out. Perhaps it's something with the paths to the sieve scripts? In dovecot.conf I find in the comments: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ protocol

Hello dovecot users, I have updated the MANAGESIEVE patch to apply and compile against dovecot 1.0.rc28. Not much has changed with respect to the functionality of the previous version however: ChangeLog vs v2 - Updated source to compile with dovecot 1.0.rc28, tested with rc27 (debian package) - Daemon now uses the same location for .dovecot.sieve as dovecot-lda This is typically

Help! I just noticed this error this morning, we have been getting a lot of these in rc28 and rc29, not in rc27 or before: Apr 6 07:22:52 karst dovecot: [ID 107833 mail.error] IMAP(jaearick): mbox file /var/mail/j/jaearick was modified while we were syncing, check your locking settings Pine coughed up an internal error, no core dump, and dovecot basically doubled the size of my mailbox by

Hi, Seem i switch my dovecot authentification to cram-md5 mecanism, i'am unable to authenticate to managesieve login. log: Dec 16 23:50:16 managesieve-login: Info: Disconnected (disconnected while authenticating): method=CRAM-MD5, rip=192.168.0.100, lip=192.168.0.50 dovecot -n : # 1.2.8: /etc/mailapp/dovecot/dovecot.conf # OS: Linux 2.6.22.8 x86_64 log_path: /var/log/dovecot.log

I'm not sure if it's even intended to work in this particular case, but there's a problem when chroot is explicitely defined and rawlogging is used. Rawlog respects chroot point, without being actually chrooted. Consider configurtion as below, with two cases (dovecot.rawlog dir is of course created earlier, with appropriate uid/gid). 1) dovecot.userdb:

Hi all, I've installed rc23 in a new testing machine, and i've had some permission problems related to dovecot-master.conf. As I have my master passwords in that file, I don't want it to be world readable. dovecot -n shows that auth_user is nobody, so setting the permissions to nobody.whatever 640 solves the problem. Anyway, I've tried to change the auth_user setting with no

Hi all, I'm in my final steps with my testing server using rc23 in a x86 RHEL4 machine. Everything is working quite well, but still are some LDAP related issues I'd like to clarify: - I'm using auth_bind and auth_bind_userdn. So pass_filter isn't used, and pass_attrs are never searched. Is this true or am I missing something? - Is there a choice for the userdb bind/queries

hi list I upgraded to 1.1.3, and have my logs turned off for some time, but turned it back on when someone complained about moving emails. I saw this in the logs. Seems strange. Using gentoo on AMD 64 bit. All is working fine, but is this a cause for alarm. dovecot: Jun 05 17:10:32 Fatal: imap-login: Dovecot version mismatch: Master is v1.1.rc6, login is v1.1.rc8 (if you don't care, set

Hi All, I have a client running Dovecot-Postfix on Debian Squeeze. I'm using Dovecot from the Squeeze repository. # dovecot --version 1.2.15 I've implemented a central mail_location and am using one vmail user, as I thought this would be be the best approach for when it came time to implement Shared and Public Mailboxes. # dovecot -n # 1.2.15: /etc/dovecot/dovecot.conf # OS: Linux

Is there a way to configure dovecot to register in syslog the debug messages enabled by mail_debug=yes as a debug not as information? I need this because I want to send this kind of information only to a remote server. I've configured rsyslog to do this, but dovecot is registering those debug messages as information not as debug (as I expected). This is my rsyslog config: mail.info;\

Hello again, managesieve is working. Now I tried a vacation script with the result that the vacation response is sent but I got he following error: deliver(test1 at xxxxxx.de): 2008-12-15 14:34:28 Error: file_dotlock_create(/home/vmail/%d/%n/Maildir/.dovecot.lda-dupes) failed: No such file or directory /home/vmail/xxxxxx.de/test1/Maildir/ is the correct dir, there are the other files like