similar to: docecot managesieve global filter, service name

You can also write to mailing list without subscribing. Anyway, I haven't written managesieve-login code, Ccing Stephan. On Thu, 2009-01-15 at 17:00 +0100, Wolfgang.Friebel at desy.de wrote: > Hi, > > sorry that do not write to the list, I am not subscribed yet. I have read > the november 2008 thread where managesieve-login does a segfault. As it > happened to me as well and

Hi folks, I'm setting up a dovecot server with managesieve support. I'd like to offer spamfiltering through a Sieve script to my users by default, but still allow them to modify the filtering rules through Managesieve. I found the sieve_global_path configuration option, which seems perfect for what I want. I can configure a default script there, which will work for all users until they

Is there some simple textual frontend to the ManageSieve protocol somewhat easier to use than gnutls-cli? I.e. something to use like managesieve -u ef putscript myscript < /tmp/myscript Password: managesieve -u ef setactive myscript Password: simply doing the TLS authentication and length computation for me.

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, well, I'm sort of sure that this was raised in the past, but I do not find the patch / answer of it: I'm running dovecot v1.0.15 from hg (5567:568687e4df02) with managesieve patch v9.2 (there is one change between this and v9.3 except in regards of AUTH so this should not matter.) and dovecot-sieve v1.0.3. When an user issues just

Hi, I have a problem with dovecot's sieve and SOGo ( http://www.sogo.nu/ ) I have installed last version of sogo ( 1.3.6) in one virtual machine with ubuntu, lucid. In another virtualmachine with ubuntu jaunty is running dovecot ( 1:1.1.11-0ubuntu4.1 ) When try to activate vacation function, after the "PUTSCRIPT "sogo" command, the manage-sieve answer: NO "Script name

tonight dovecot 1.2beta4 crashed for the first time with an assertion failed. See attached log file. Around that time nobody was logged in into dovecot and there were no other mail deliveries going on. The mail in question should have been delivered to three recipients, one got the mail, the two others not. There is unfortunately no core dump file. I have attached the dovecot -n output as

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

With all the mess that my email has become, it makes sense for me to try to make use of Sieve, but I'm having quite the time finding out how to make it work. I'm running 1.0.13 on a Debian machine. Sieve appears to be compiled with it. I can access managesieve, and I have set up dovecot.conf with lda. I do not get a NO response when I PUTSCRIPI, but LISTSCRIPTS produces no result, so I

I am building dovecot-2.0-pigeonhole-0.2.1 (dovecot-2.0.5, but that does not matter) with dovecot-config in place (in /usr/lib64/dovecot) on a 64bit Linux (RHEL5): ./configure --with-dovecot=/usr/lib64/dovecot The libs needed for several executables in libexec such as /usr/libexec/dovecot/managesieve-login are not installed in /usr/lib64 but in /usr/lib64/dovecot. Therefore the executable

Hello, I'm testing dovecot replication alongside pigeonhole and liking it. Dovecot v2.2.13 Pigeonhole v0.4.3 If I create or edit a sieve script on one server (via managesieve, using the thunderbird plugin as it happens) then it does get replicated to the other - great! However, if I set a script to be active (SETACTIVE) on one side then this is not being replicated across to the other

Using dovecot 1.2beta (but earlier versions should behave similarly) we have a problem in conjunction with empty To: headers and the RT request tracker. RT sends mail out using Bcc: and no To: header at all. To make some mailers happy one can configure to send a dummy To: header, which we do. Our To header looks like: To: "AdminCc of rt Ticket #123456":; The message_address_parse

Hi Timo, we are currently running dovecot 2.1.10 using mdbox storage. Sometimes we get requests from users to restore accidentally deleted mails. If the mails got deleted before a backup was made, such mails could of course not be restored from backup. One option to help users in this respect would be to use the lazy expunge plugin. On the other hand I have seen, that the deleted mails stay

In order to let users construct a sieve filter using a GUI I have taken websieve.pl from Alain Turbide (for use with Cyrus) and modified it to work with dovecot. In order to get it working quickly I have removed all the code I did not need (e.g. ldap support, password authentication) and coded Kerberos5 auth (via GSSAPI or SASL) in. I understand that this makes the work mostly useless to

Hello we are doing regular backups of the mdbox mail folders using dsync -u username backup mdbox:/somedir/BACKUPS/username (still with version 2.1.10, but 2.2.5 is in testing phase) We do observe that the directory size in the BACKUPS directory is growing with respect to the original mail folders. I believe this is due to deleted mails not being purged in the backup. We are doing regular

Hello Dovecot users, Because there was a crash bug in the ManageSieve v0.10.4 login daemon, I made a new release of the ManageSieve service for Dovecot v1.1. This release includes two other small fixes as well. Changelog v0.10.5: - Fixed a segfault bug in the authentication time-out. Bug report and trace provided by Wolfgang Friebel. - Fixed maximum permissions for uploaded

Hello Dovecot users, Because there was a crash bug in the ManageSieve v0.10.4 login daemon, I made a new release of the ManageSieve service for Dovecot v1.1. This release includes two other small fixes as well. Changelog v0.10.5: - Fixed a segfault bug in the authentication time-out. Bug report and trace provided by Wolfgang Friebel. - Fixed maximum permissions for uploaded

Is dovecot still considered unreliable when combined with NFS? Is this true for mbox only, or Maildir as well? If dovecot Is still considered unreliable with NFS, how about having a dovecot mode that would chain into procmail for delivery, so that dovecot doesn't (necessarily) have to reinvent that wheel? Thanks!

Greetings all, I'll skip the details of the setup, except to say that it has a non-standard (and non-templateable) home directory path for virtual users. Ran into the following problem when a debian (possibly from backports) packaged dovecot-1.1.2 was upgraded to a dovecot-1.1.13-2~bpo50+1 (definately from backports): sieve-storage: root directory specified by mail data does not exist:

Hi i have a problem compiling as mantioned on object of this mail: i'm changing dovecot on my debian 6 from version 2.2.32 to 2.2.36 and pigeonhole from 0.4.20 to 0.4.24 this is output of dovecot -n for listing versions installed dovecot -n # 2.2.32 (dfbe293d4): /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.4.20 (7cd71ba) # OS: Linux 2.6.32-5-amd64 x86_64 Debian 6.0.10 i have

Hi everyone, New to the list, and fairly confident that this issue is purely down to my own idiocy, so please go easy on me! I've been running Dovecot 1.0.13 on Debian (via Aptitude package) for some time, and have been delighted with it. For a while I've toyed with the idea of using ManageSieve as there's a nice plugin for Roundcube, so I'm trying to follow the how-to at