similar to: Sieve authentication / directory issue after upgrade to 1.0.13.

Hi, I'm testing Dovecot to migrate from my old Courier IMAP/POP server. It work fine but I have some problems to start the sieve server "pysieved" from Neale Pickett in PAM auth, I got the message: Traceback (most recent call last): File "/usr/share/pysieved/pysieved.py", line 97, in <module> main() File "/usr/share/pysieved/pysieved.py", line

Hi List, I would like to log pop3/imap login events but I don't see them in the logfiles. What am I doing wrong? dovecot version: 1.1.11 dovecot -n: # 1.1.11: /etc/dovecot/dovecot.conf # OS: Linux 2.6.28-13-server i686 Ubuntu 9.04 nfs base_dir: /var/run/dovecot/ log_path: /var/log/mail.log log_timestamp: %Y-%m-%d %H:%M:%S protocols: imap pop3 imaps pop3s ssl_cert_file:

Hi, I am using dovecot 1.0.10 and pysieved, in a master/slave cluster with ldap (auth_bind=yes). For conceptuals reasons, i would like to keep on the same partition the mailstore + sieve scripts. I have try to set "sieve" and "home" variables under the "plugin" section with an absolute path, and i have tried to override home variable in user_attrs

I have written a managesieve server from scratch in Python. I did just enough work to get it working with avelsieve (the squirrelmail plugin), smartsieve, and KDE's sieve kioplugin. It supports the entire Internet draft. Since I didn't have a working sieve server to compare against, I'm not sure if it's 100% compatible with timsieved. Client applications seem to work okay

Hello, dovecot-users ... as you may read at http://lists.horde.org/archives/horde/Week-of-Mon-20090706/037786.html I am stuck getting dovecot-sieve working with the ingo-application of the horde-framework. To me it seems as if ingo doesn't even trigger any request/command to managesieve ... I set "mail_debug=yes" in the managesieve-section of dovecot.conf but don't see any

Hello there, I have been using pysieved and avelsieve and it has been working great. I decided to do test with the ManageSieve patch and got this problem: Nov 27 17:21:29 cambui dovecot: MANAGESIEVE(miguel): sieve-storage: using active sieve script path: ~/.dovecot.sieve Nov 27 17:21:29 cambui dovecot: MANAGESIEVE(miguel): sieve-storage: using sieve script storage directory: ~/.sieve Nov 27

Hello, Before asking help, i would like thank Timo for this awesome server, it's lite, fast, and has good features. I've read the Wiki, tutorials, and tried various configurations to get the result I expect. My company is running a dovecot 1.0.0 server set up with an LDAP directory, mails are delivered to /var/spool/imap and users do not have a real unix home directory on this

Hi, I'm wondering, whether it's possible, to define an ACL on the mailbox itself. We use Dovecot 1.2.15 (included in Debian 6) and maildir filesystem layout: /home/mail01/user1/Maildir/new \ /home/mail01/user1/Maildir/cur Inbox /home/mail01/user1/Maildir/tmp / /home/mail01/user1/Maildir/.folder1/new \ /home/mail01/user1/Maildir/.folder1/cur folder1

If moving from pysieved to Dovecot native ManageSieve implementation, should this just work or do I need to do anything with existing sieve filter rule files, etc? Any reasons not to do the switch? Regards, BTJ -- ----------------------------------------------------------------------------------------------- Bj?rn T Johansen btj at havleik.no

Hi, I had successfully set up dovecot-1.0-test62 + ldap pass/user db, but now I'm encoutering a SIGSEV problem with a similar set up of a brand new dovecot-1.0-test65 installation. The auth process is killed by a SIGSEV as reported in the error log file : dovecot: Mar 30 17:06:59 Error: child 28291 (auth) killed with signal 11 To be precise, the problem occurs in the

Hello dovecot users, I have updated the MANAGESIEVE patch to fix a recently reported problem. This is a patch against the latest stable release 1.0.3. It currently won't compile with 1.1 due to significant changes in the master code. Change Log V7 ------------- - Robin Breathe indicated that the regex capability was missing in the server's SIEVE listing. It turns out I forgot to

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, there were some posts into this lists regarding Webmail interfaces and Sieve. What are the experiences with them? I need a webmail frontend that is capable of IMAP, supporting dovecot's namespaces, verifying PGP and managing Sieve in conjunction with Dovecot. I found two mature products, I also saw posts about, so I'm going to ask.

Another crahs with backtrace: GNU gdb 6.8-debian Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was

GNU gdb 6.8-debian Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as

Seeing dovecot-auth segfault on amd64 dovecot is 1.2.4 pertinent details below: ldd /usr/local/libexec/dovecot/dovecot-auth linux-vdso.so.1 => (0x00007fffef1fe000) libcrypt.so.1 => /lib/libcrypt.so.1 (0x00007fe8e6bae000) libvpopmail.so => /usr/lib/libvpopmail.so (0x00007fe8e6986000) libdl.so.2 => /lib/libdl.so.2 (0x00007fe8e6782000) librt.so.1 => /lib/librt.so.1

Hello... I have dovecot 1.0.10 running with the sieve plugin and virtual users (LDAP). My webmail is squirrelmail. I want to allow the users to create sieve-scripts via a squirrelmail-plugin. The plugins seems to require that the IMAP-server is cyrus. What are the options for dovecot? Thanks, Tobias

Hi, all. I'd like to introduce this open source email server solution here, hope it can help people who need mail server solution. Project: http://code.google.com/p/iredmail/ iRedMail is: * Mail server solution for Red Hat(R) Enterprise Linux and CentOS 5.x, support both i386 and x86_64. * A shell script set, used to install and configure all mail server related software

Hi Timo, may I request once more to consider the attached patch for dovecot 1.1, it enables the sieve plugin (incl. sievec and sieved, needed for pysieved) to be built against an installed dovecot package, if --enable-header-install additionally installs the liblib.a library in the same directory as dovecot-config. I have included this patch in the pkgsrc dovecot 1.1 package a while ago. Geert

I need to use Dovecot auth socket from my perl script to validate user's passwords (for jabber server). Is there any information about how to communicate with dovecot auth socket?

Hi! I am currently testing a setup with dovecot's lda, the cmusieve plugin, pysieved and the avelsieve plugin for squirrelmail. The issue I am stumbling upon is that avelsieve is generating folder names including the namespace prefix when creating "fileinto" rules. E.g.: A rule: If the header "Precedence" contains "bulk", then file it into the folder