Re: sieve filter move wrong email to Junk folder

Also, I wouldn't use the second rule:     if header :contains "subject" ["SPAM?"] {       fileinto "Junk";       stop;     } If someone sends you an email with the subject "Can you help me with this spam?" it will get filed into Junk. Bill

Re: sieve filter move wrong email to Junk folder

This is what I use.  Notice the comma: require "fileinto"; if header :contains "X-Spam-Status" "Yes," {   fileinto "SystemFolders.SuspectedSpam";   stop; } Bill On 12/14/2017 1:02 PM, Richard wrote: Date: Thursday, December 14, 2017 09:47:44 -0800 From: Gao I use a sieve

Re: Mail-crypt plugin clarification

Aki Tuomi writes: Dovecot does support making it difficult to prevent access to the stored mail. Those who have had problems understanding the documentation might find this unintended double-negative ironically funny. You can, with suitable workflows, ensure that the user's emails are not

Re: sieve filter move wrong email to Junk folder

This is what I use with Exim, spam.sieve is included in from a master.sieve: thebighonker.lerctr.org /home/ler $ more sieve/spam.sieve require ["fileinto","imap4flags"]; if header :contains ["X-LERCTR-Spam-Flag","X-TNTSCAN-Spam-Flag"] "YES" { redirect "spamt...@spambouncer.org"; fileinto

Re: sieve filter move wrong email to Junk folder

Well I changed the line to   if header :contains "X-Spam-Status: YES" { Then I got: # sievec spam_to_junk.sieve spam_to_junk: line 3: error: the header test requires 2 positional argument(s), but 1 is/are specified. spam_to_junk: error: validation failed. sievec(root): Fatal: failed to

Re: sieve filter move wrong email to Junk folder

thank you for the advice. I'll change it. Gao On 2017-12-14 10:02 AM, Richard wrote: Date: Thursday, December 14, 2017 09:47:44 -0800 From: Gao I use a sieve filter to move spam email to user's Junk folder: # cat spam_to_junk.sieve require "fileinto";   if exists

Re: sieve filter move wrong email to Junk folder

> Date: Thursday, December 14, 2017 09:47:44 -0800 > From: Gao > > I use a sieve filter to move spam email to user's Junk folder: ># cat spam_to_junk.sieve > require "fileinto"; >   if exists "X-Spam-Status" { >   if header :contains "X-Spam-Status" "YES" { >  

sieve filter move wrong email to Junk folder

I use a sieve filter to move spam email to user's Junk folder: # cat spam_to_junk.sieve require "fileinto";   if exists "X-Spam-Status" {   if header :contains "X-Spam-Status" "YES" {   fileinto "Junk";   stop;   } else {   }   }   if header :contains "subject"

Re: New Dovecot service: SMTP Submission (RFC6409)

One other point. Adding support for something like this that also requires Clients to add support for it is just begging for a feature that never gets used. Stephan, are you sure there is no (fairly simple) way to make this an SMTP service that any email client that supports SMTP can use? On

Re: New Dovecot service: SMTP Submission (RFC6409)

On 12/14/2017, 3:03:41 AM, Aki Tuomi wrote: > On 13.12.2017 21:41, Tanstaafl wrote: >> On 12/12/2017, 1:39:08 PM, Stephan Bosch wrote: >> I thought this was simply going to be an SMTP like service that any SMTP >> client could utilize, keeping the

Re: doveadm log reopen not works with 2.2.33

On 12/14/2017 03:18 PM, Alessio Cecchi wrote: > Is this a know bug? https://www.dovecot.org/pipermail/dovecot/2017-November/109971.html

doveadm log reopen not works with 2.2.33

Hi, after the upgrade from dovecot 2.2.32 to 2.2.33 we notice that the /var/log/director/director.log was empty and the log are write in the logrotate file es. /var/log/director/director.log-20171201. Log path is dovecot is: log_path = /var/log/director/director.log Logrotate configuration

Panic: file imap-client.c: line 1204 (client_handle_input): assertion failed: (o_stream_is_corked(client->output))

Running Dovecot from the daily builds: 2:2.3.0~alpha0-1~auto+1287 in an proxy setup: auth_mechanisms = plain login default_vsz_limit = 1 G imapc_host = .charite.de imapc_port = 993 imapc_ssl = imaps imapc_ssl_verify = no listen = *,:: mail_gid = imapproxy mail_home = /home/imapproxy/%u

Re: dovecot (+sendmail) fails to get email into thunderbird

> # %u is replaced with the username that logs in > mail_location = mbox:~/mail:INBOX=/var/mail/%u > if i change the mail location into: mbox:~/mail:INBOX=/var/mail/%u mail.log says: Dec 14 14:24:26 pie dovecot: imap(update.site1): Error: user update.site1: Initialization failed: Namespace '':

dovecot crashing

i have a system with panics/crashes and seem to be able to trigger the problem. dovecot version: 2.2.33.2 (from ius rpm-package-repository) maillog: Dec 14 10:55:00 vimap01 dovecot: imap(XXX): Panic: file index-mail-binary.c: line 358 (blocks_count_lines): assertion failed: (block_count == 0

Re: New Dovecot service: SMTP Submission (RFC6409)

Op 14-12-2017 om 8:26 schreef María Arrea:     Stephan, thank you very much for your hard work. I want to ask your opinion about jmap ( http://jmap.io/ ) , do you think is a viable alternative to current IMAP + MSA ? Difficult to tell at this point, as It is not finished yet. It all

Re: auth_policy in a non-authenticating proxy chain

On 2017-12-14 10:31, Sami Ketola wrote: > >> On 14 Dec 2017, at 8.30, Peter Mogensen wrote: >> However... since the proxy use "nopassword", ALL passdb lookups result >> in "success", so the proxy will never report an authentication failure >> to the authpolicy server. > > > Why

Re: auth_policy in a non-authenticating proxy chain

> On 14 Dec 2017, at 8.30, Peter Mogensen wrote: > However... since the proxy use "nopassword", ALL passdb lookups result > in "success", so the proxy will never report an authentication failure > to the authpolicy server. Why not authenticate the sessions at the proxy level

Re: Recommended tool for migrating IMAP servers

> On 13 Dec 2017, at 18.27, Davide Marchi wrote: > > Sami Ketola wrote:> We run all our migrations using Dovecot internal dsync. > Usually using imapc connector to connect to legacy >> platform. >> Wqmi > > Many thanks Wqmi! > Well, I've read the dsync documentation, but this

Re: Mail-crypt plugin clarification

On 14.12.2017 01:07, Joseph Tam wrote: > rje writes: > >> I'm looking into ways to encrypt the stored email on my server. The >> idea is >> to make it impossible for my hosting provider (who has access to my >> VPS) to >> read the mail from the disk. > > Just to be clear, if at any point your

Re: New Dovecot service: SMTP Submission (RFC6409)

On 13.12.2017 21:41, Tanstaafl wrote: > On 12/12/2017, 1:39:08 PM, Stephan Bosch wrote: >> However, keep in mind that for this particular feature we're just >> providing the "chicken" as it were. The "egg", i.e. client support, is >> still to come. Apart from Trojita