similar to: Sieve question

Since switching to lmtp in dovecot, mail to user+mailboix at example.com does not get saved in ?.mailbox? as it did with LDA, instead it gets saved into the INBOX. If it matters, these are users who do NOT have a ~/.active_sieve file. I could understand (though it would bene a bit annoying) if the save overrode this mechanism. I did add lmtp_save_to_detail_mailbox = yes in the protocol lmtp

I am trying to create some sieve scripts to filter my mailing lists and am wondering if sieve logs anywhere, and it so where? I don?t see anything in mail.log beyond lines like: dovecot: lda(kremels at kreme.com)<39790><hNchChSkAV1umwAAIdGjjQ>: sieve: msgid=<267D5D71-D99C-4790-8706-C1A92BCC9F97 at kreme.com>: stored mail into mailbox ?INBOX' Which doesn?t really tell me

I have the following in my default.sieve file: require "fileinto"; if header :contains "X-spam-flag" "YES" { require ["vnd.dovecot.pipe", "copy", "imapsieve", "environment", "variables", "imap4flags"]; setflag "\\Seen"; fileinto "Junk"; } This is largely unchanged, except that I

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

Error: program `/usr/lib/dovecot/sieve/sa-learn-spam.sh' terminated abnormally, signal 11 Error: sieve: pipe action: failed to pipe message to program `sa-learn-spam.sh': refer to server log for more information. [2019-05-29 17:59:12] What server log? This is all that get logged. # pwd /usr/lib/dovecot/sieve # ls -lsa > total 96 > 8 drwxrwxrwx 3 root wheel 512 Jun 18 2018

Now i tried an additional rule in my "normal" working sieve-filter: if address :domain :matches "from" "company.example" ? { setflag "\\seen"; fileinto :create "INBOX/foo/test"; stop; } and sent an email from my company-account. The folder INBOX/foo/test gets created, but the message inside is not marked as seen. So i think, this is a bug in

Hello, I use FreeBSD 8.2-RELEASE-p7 i386 dovecot-2.1.6 dovecot-pigeonhole-0.3.0_1 I have the following problem: When I use the following script - the flag is set in \Seen : require ["imap4flags"]; # rule:[test] if anyof (header :contains "Subject" "test") { setflag "\\Seen"; stop; } . SELECT INBOX * OK [CLOSED] Previous mailbox

Hi all, ok, I just instealled the dovecot 2.0.0 release, and the latest mercurial pigeonhole source. All is well, except for a particular sieve rule that may not be working right. It is a simple rule that looks like this : require ["fileinto","imap4flags"]; # rule:[Past Due Notices] if allof (header :contains "Subject" "Account Past Due Notice") {

Which version of dovecot are you using? jakob Am 04.12.18 um 15:44 schrieb Larry Rosenman: > I have the following, and it works: > require ["include","fileinto","imap4flags","variables"]; > global "MyFlags"; > if header :contains ["X-LERCTR-Spam-Flag","X-TNTSCAN-Spam-Flag"] "YES" > { > redirect

Dear all, I have found a way to automatically copy sent emails in the "Sent" folder, but I am not sure it is the simplest and more reliable way on the long term. I am open to suggestions if I miss a feature in Dovecot - or Postfix, that allows me to do this. I vaguely remember an SMTP extension that do that, but my memory could be wrong. First, I use "~" as a recipient

I am now trying portmaster -f dovecot-2.3.6 which is reinstalling 78 ports. ?? On Wed, May 15, 2019 at 7:26 PM Cerebus the Aardvark <kreme at kreme.com> wrote: > > I've rebuilt dovecot, but no change in behavior. > > I also enabled debug, but nothing else is logged to /var/log/dovecot > as to why IMAP is crashing. > > On Wed, May 15, 2019 at 5:46 PM @lbutlr via

I tried it like you... doesn't work. The message gets all the other flags, but not the \Seen-Flag. My repo is https://repo.dovecot.org/ce-2.3-latest/debian/stretch stretch dpkg -l|grep dove ii? dovecot-core????????????????????? 2:2.3.4-2~stretch????????????? amd64??????? secure POP3/IMAP server - core files ii? dovecot-imapd???????????????????? 2:2.3.4-2~stretch????????????? amd64???????

How would I setup dovecot so that when messages are moved to the Archive mailbox, they are marked as read? Would it be similar to the imap-sieve for spam tagging? imapsieve_mailbox1_name = Junk imapsieve_mailbox1_causes = COPY imapsieve_mailbox1_before = file:/usr/lib/dovecot/sieve/report-spam.sieve Or is there a simpler method? If it matters: mailbox Archive { auto = subscribe

Did you notice the fileinto :flags usage? It comes from imap4sieve extension. https://tools.ietf.org/html/rfc5232#page-7 Aki > On 04 December 2018 at 17:13 Larry Rosenman <larryrtx at gmail.com> wrote: > > > I've been using that recipe for YEARS, and it DOES work for me on FreeBSD > (I'm also the port maintainer for dovecot and pigeonhole). > > Not sure

Running dovecot 1.2.12 on ubuntu 10.10. Here is the problem: I have mysql backend for expire. I am using the dovecot-postfix package which creates /etc/dovecot/conf.d/01-mail-stack-delivery.conf which looks like this: # Some general options protocols = imap imaps managesieve disable_plaintext_auth = no ssl = yes ssl_cert_file = /etc/ssl/certs/ssl-mail.pem ssl_key_file =

On 18 Jul 2020, at 11:23, Stephan Bosch <stephan at rename-it.nl> wrote: > On 12/07/2020 22:47, @lbutlr wrote: >> On 12 Jul 2020, at 10:17, Benny Pedersen <me at junc.eu> wrote: >>> @lbutlr skrev den 2020-07-12 16:43: >>>> I an trying to write a sieve action that will take mail that is >>>> addressed to a user only it is filed in a mailbox

Hello mailinglist-subscribers, i have an issue with the managesieve / sieve plugin in dovecot. We use roundcube as webmailer and if i define a new filter to move incoming mails directly into a subfolder i get the following sieve-code: require ["fileinto","imap4flags"]; # rule:[mail into folder] if allof (header :contains "from" "sender at domain.org") {

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",

On 13 Jun2019, at 02:18, Matt Anton via dovecot <dovecot at dovecot.org> wrote: > > Sieve logs are in users?s homes and can be configured with ? sieve_user_log ?: > > ? sieve_user_log = > The path to the file where the user log file is written. If not configured, a default location is used. If the main user's personal Sieve (as configured with sieve=) is a file, the

spi skrev den 2023-03-11 13:34: > if address :domain "From" "whatever.com"{ > fileinto :flags ["\\todo"] "working/whatever"; > } require ["fileinto","imap4flags"]; # rule:[set todo] if allof (header :contains "subject" "set imap flags in user sieve scripts", header :contains "from" "user at