similar to: Connection closed by foreign host.

Hello, Dovecot keeps crashing at login time. Things were fine on 2.2.2 Fatal: master: service(imap): child 5014 killed with signal 11 Here is the trace: Core was generated by `imap'. Program terminated with signal 11, Segmentation fault. #0 0x00000000105cdfdf in mailbox_list_get_storage (list=0x7fffffffe310, vname=0x10a04ab0 "INBOX/spam", storage_r=0x7fffffffe308) at

We're currently running 2.1.16. I've been wanting to update to a 2.2.X version, but have been running into problems, even with the latest (2.2.12). I'm not sure at what version this issue appeared, but I believe I've tried 2.2.10, 2.2.11, and now 2.2.12. We have a shared maildir setup. With that configuration in place and with a user in the dovecot-acl file, I can do the

when .dovecot.sieve is a symlink (which it is in my case) a warning is written to the error log file, but it still works. Dec 12 10:02:33 managesieve(tester at domain.com): Warning: sieve-storage: Active sieve script symlink /srv/vmail/sieve/domain.com/tester/.dovecot.sieve is broken: invalid/unknown path to storage (points to ingo.sieve). root at

Hi Volker! This is what I wanted to avoid with my question. I reported my script with only three word just to make an example but my list is quite longer than this. Let's suppose a list of 30 or 40 words... 30 or 40 rules? Possible but very unconfortable to manage. A more compact version of the script could be this: -- the script begins ------------ require ["fileinto",

Hi everybody! I manage a mail server running Dovecot 2.2.21 with Pigeonhole 0.4.10. I successfully configured sieve and use it also to filter some spam messages. Here is one of the script I use to filter messages on the basis of prohibited words in message body. As you can see, the last command writes to the log the action of this script. -- the script begins ------------ require

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

Trying to make vnd.dovecot.filter to exchange an email with my script. (I have a vnd.dovecot.pipe script working, so I'm pretty sure it's not the configuration...) I'm passing the email using stdin/stdout and _not_ using sockets. My script receives the email and processes it, but the filter process fails: lda(<username>): Error:

Am Samstag, 30. Juni 2018, 11:28:43 CEST schrieb Lukas: > Hi everybody! > > I manage a mail server running Dovecot 2.2.21 with Pigeonhole 0.4.10. I successfully configured sieve and use it also to filter some spam messages. Here is one of the script I use to filter messages on the basis of prohibited words in message body. > > As you can see, the last command writes to the log the

Sorry @lbutlr, this is a very silly answer to my question...! My script is not the definite spam solution on my mail server, obviously. In addition to Spamassassin, blacklist implementation, SPF, DKIM and more, I need to filter some specific messages with particular words and log the script action. In my first mail I made an example with three really obvious words but my need is not about sex or

>>>> 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 30 Jun 2018, at 03:28, Lukas <lukas at email.it> wrote: > body :text :contains "crypto", > body :text :contains "sex", > body :text :contains "viagra" This is a very silly way to try to deal with spam. In fact, your own message to the list will be flagged by your rule. Actual spam message will illy not even hit this rule as

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 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 because vnd.dovecot.environment already provides the >> username? (which does work for me) >> >> If

What is your configuration (output from `dovecot -n`)? Op 16/08/2018 om 14:01 schreef Leandro Lucarella: > 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

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! Is there a way to initialize global variables with default values in sieve_before scripts that can be used in the sieve_default script or in user scripts? I've tried the following code but this doesn't work.. before.d/10-set-defaults.sieve: -------------------- 8< -------------------- require ["variables", "include"]; require "vnd.dovecot.debug"; set

Hi, I have noticed a strange behaviour when using size matches with GB in sieve. If I use filter that matches mails smaller then 4, or 8GB it does not match in any case. same filter matches with 3,5,6,7 GB example filter: require "vnd.dovecot.debug"; if allof (size :under 4G) { debug_log "MATCH"; } else { debug_log "NO MATCH"; } # sieve-filter

Hi, I am pushing some updates and fixes that addresses much of the issues that we talked about since last couple of days. 1. Use configuration option :debug_log: false to disable backgroundrb_debug.log. 2. As shown below, use lazy_load option to disable aggressive loading of models ( and somewhat stupid too). 3. MiddleMan.delete_worker(:worker => :foo_worker) will now ABORT the worker, it

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

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