similar to: Using filter in an imapsieve script?

Hi Stephan yes the imap_sieve plugin is added to the mail_plugins for imap. Thanks for the hint with mail_debug. After enabling it I can see that the program seems to be called, so filter should not be the problem. But the result is that the message appears unencrypted in my sent folder > Apr 6 08:20:26 mbox2 dovecot: imap(tobster at brain-force.ch): Debug: imapsieve: mailbox Sent: APPEND

Op 4/5/2017 om 11:48 AM schreef Tobi: > Hello list > > I currently have an issue with an imapsieve script on my dovecot server > > CentOS Linux release 7.3.1611 (Core) > Dovecot 2.2.26.0 (23d1de6) > Pigeonhole 2.2.26.0 > > The goal is to "fire" an imapsieve script upon mailclient saves message > to sent folder > I setup the following in 90-plugin.conf:

Dear dovecot developers, I have an issue with the Pigeonhole IMAPSieve Plugin and the order in which administrator scripts are executed. Although I cannot find anything about the order in which the scripts are executed, I would expect they are executed in the order they are defined: the one defined by imapsieve_mailbox1_* before the one defined by imapsieve_mailbox2_* in case both match. I

Op 4/5/2017 om 11:48 AM schreef Tobi: > Hello list OK, I know why this is happening now. > I currently have an issue with an imapsieve script on my dovecot server > > CentOS Linux release 7.3.1611 (Core) > Dovecot 2.2.26.0 (23d1de6) > Pigeonhole 2.2.26.0 > > The goal is to "fire" an imapsieve script upon mailclient saves message > to sent folder > I setup

Hi list I just realized that that I don not receive all mails in my mailbox (running dovecot-ee 2.2.23.1-1 on Debian 8). On my frontend servers (running postfix) the queue fills up with mails that cannot be delivered via lmtp to my backend servers. The error message on the frontend is "lost connection with backend while sending data" When I checked the logs on the backend server I found

On Friday 17 August 2018 01:41:39 CEST Stephan Bosch wrote: > dovecot -n Hi, here it is (I don't know why I get the SSLv2 warning because it is disabled in ssl_protocols, any ideas about that too?). BTW, even when storing the message in a different folder with fileinto, the original message is still saved in the original mailbox. I also tried using `discard;` and makes no difference, I

Hello, I'm trying to do a simple thing using imapsieve, I want messages to be marked as read when moved to certain folders (Trash, Archive, Spam). All the set up to run the imapsieve script works perfectly, but I'm having trouble to make changes effective. As the RFC says, IMAP messages are immutable, but it's not clear to me reading the specs if this applies to IMAP flags too, as one

On 2016-12-05 07:22, Stephan Bosch wrote: > Op 5-12-2016 om 16:10 schreef MRob: >> On 2016-12-05 06:13, Stephan Bosch wrote: >>> Op 5-12-2016 om 14:32 schreef MRob: >>> >>> Could you show me your full script? I am mainly interested in the >>> require statements involved. >> >> I don't know how I managed to compile only using direct

Hi, I'm running a dovecot 2.2.26 (self compiled) on a Centos 7. I have a sieve script which should run an external script (in filter mode) that encrypts the mail using the users pub key. I configured 90-plugin.conf as follows plugin { sieve_plugins = sieve_extprograms sieve_extensions = +vnd.dovecot.filter sieve_filter_bin_dir = /etc/dovecot/sieve-filters

On 2016-12-05 06:13, Stephan Bosch wrote: > Op 5-12-2016 om 14:32 schreef MRob: >> On 2016-12-05 04:38, Stephan Bosch wrote: >>> Op 5-12-2016 om 13:28 schreef MRob: >>>> RFC6785 says imap.user and imap.email environment variables should >>>> be made available but I can't access them no matter what I try. Are >>>> they not implemented

Hi, > Can you enable mail_log plugin, try again, and send updated logs? > Aki Sure, but logs contain same info. 1. When I move a message from Inbox to Spam it matches both rules and sieve executing both scripts in sequence: Debug: Spam: Mailbox opened because: SELECT Debug: imapsieve: mailbox Spam: APPEND event Debug: sieve: Pigeonhole version 0.4.21 (92477967) initializing Debug: sieve:

Hello all, Hopefully this is something fairly simple. I've been trying to set up the Sieve Antispam system as detailed at https://wiki2.dovecot.org/HowTo/AntispamWithSieve, but at the moment, whenever I change mailboxes I get the following message logged: Aug 22 09:30:45 remy dovecot: imap(darac at darac.org.uk): Error: imapsieve: mailbox INBOX: Failed to read /shared/imapsieve/script

Hi, Running dovecot 2.2.27 (c0f36b0) on Debian GNU/Linux stable (version 9.6), I'm trying to use the execute command in a sieve script, with direct execution (not service socket). The script is executed, and returns (the process exits), but the dovecot-lda process seems to not notice, and thinks the script did not terminate. After sieve_execute_exec_timeout has passed, it sends a TERM, a bit

>>>> I don't know how I managed to compile only using direct access of >>>> ${imap.user} before since now I get an unknown namespace error on my >>>> test script. >>>> >>>> But doing it this way compiles: >>>> >>>> require ["environment", "variables", "vnd.dovecot.debug"];

On Tue, Aug 22, 2017 at 01:55:45PM +0300, Aki Tuomi wrote: > > >On 22.08.2017 13:37, Darac Marjal wrote: >> Hello all, >> >> Hopefully this is something fairly simple. >> >> I've been trying to set up the Sieve Antispam system as detailed at >> https://wiki2.dovecot.org/HowTo/AntispamWithSieve, but at the moment, >> whenever I change mailboxes

Hello, The documentation says imapsieve_url "has no effect on the administrator-controlled Sieve scripts". However, when setting this item, I get lines such as: Error: imapsieve: mailbox INBOX: Failed to read /shared/imapsieve/script mailbox attribute: Mailbox attributes not enabled and that's it. imapsieve_mailboxXXX_* settings are completely ignored. Unsetting imapsieve_url

I?m trying to follow the instructions on the wiki to move from antispam to IMAPSieve, but it?s not working at all. A bit of a background: dovecot-core 2:2.3.8-4~buster dovecot-imapd 2:2.3.8-4~buster dovecot-lmtpd 2:2.3.8-4~buster dovecot-managesieved 2:2.3.8-4~buster dovecot-pgsql 2:2.3.8-4~buster dovecot-pop3d 2:2.3.8-4~buster

Hello, I'm experiencing some strange problem with imapsieve mailbox rules matching. I have Ubuntu Server 18.04.1 LTS with Postfix 3.3.0, Dovecot 2.2.33.2 and Rspamd 1.7.9. The problem occurs with Microsoft Outlook 2016 mail client. When moving with Outlook, APPEND event is logged instead of MOVE. However, when moving with another client, MOVE event is logged. So without APPEND event in

On 2016-12-05 15:26, Stephan Bosch wrote: > Op 12/6/2016 om 12:23 AM schreef MRob: >>>>>> I don't know how I managed to compile only using direct access of >>>>>> ${imap.user} before since now I get an unknown namespace error on >>>>>> my >>>>>> test script. >>>>>> >>>>>> But doing

Hi to all of you, as I am struggling around with this a week or so I'm afraid I have to ask for help here. The problem is sitting right in front of the computer, as most of the time. ;-) So let me explain: Dovecot is working properly for IMAP with LE certificates, so I thought it's time to continue with Christoph Haas tutorial primarily and other blogs and tutorials for setting up the