Displaying 20 results from an estimated 80000 matches similar to: "sieve issue"
2012 Apr 29
3
Sieve doesn't find user scripts
Hi,
I want to use Sieve filtering with my Dovecot 1.2 installation on Debian
squeeze. I have a virtual domain setup using Portgresql.
ManageSieve works fine so far, I can edit and activate/deactive scripts (using
Thunderbird + Plugin) and they show up in the filesystem where I expect them to
be, see below.
The problem is that LDA doesn't find the script. From
/var/log/dovecot-deliver.log:
2011 Jul 27
3
sieve on debian squeeze
Hi. I have a quite problem with dovecot and sieve on Debian Squeeze.
I'm trying to enable sieve plugin into dovecot, but something is
deeply wrong. I hope that this is the right place to give some help.
There are no errors or warning messages, simply sieve don't works.
For the big picture about my mail server you can follow this link
2009 Oct 16
1
Dovecot can't find users' sieve files
Hello.
I asked for help on #dovecot but one suggestion I got was setting sieve
variable explicitly but unfortunatelly that didn't help.
I'm trying to set up sieve to be able to use vacation module.
So in the lda section I put:
mail_plugins = sieve
And in plugins section:
sieve = ~/.dovecot.sieve
Then I put .dovecot.sieve file in the user's directory.
This is what I get in
2008 Sep 08
2
Sieve, and logging.
Hi All,
Relatively new to Dovecot - converting from courier-imap. So far, I've
got it working with virtual users (postfixadmin tables), and it seems to
be working. I'm trying to get sieve working. It's not, so I tried
turning up the logging, and putting it into a separate log file to get
it out of the syslog for now. I can get the main dovecot to log, but
I cannot get any log
2017 Nov 09
2
Sieve global path?
Hello,
I am building a new server on CentOS 7 and the global sieve filter can
not be loaded. The debug shows:
Nov? 9 15:23:09 mail dovecot: lmtp(11182, gao at mydomain.com): Debug:
sieve: Pigeonhole version 0.4.2 initializing
Nov? 9 15:23:09 mail dovecot: lmtp(11182, gao at mydomain.com): Debug:
sieve: include: sieve_global_dir is not set; it is currently not
possible to include `:global'
2008 Apr 26
1
sieve doesn't sift yet
Hi all,
I am having difficulty getting sieve working. I created a simple set of
rules which I've validated on the sieve-php page at SF. I placed this file,
.dovecot.sieve, in the root of my maildir, which I understand is the
default location. I also created a logfile in /var/log, but nothing has
gotten written to it yet. Here is my configuration:
$ sudo dovecot -n
# 1.0.13:
2011 May 08
3
sieve filters not being invoked
Hi all,
Similar to someone who posted here yesterday, I am having trouble getting
sieve filters working.
I have installed pigeonhole. I can create, edit, and save scripts from both
the Thunderbird sieve extension as well as the Roundcube sieve plugin via
managesieve running on port 4190. The .sieve file is properly saved in
~/sieve with a symlink from ~/.dovecot.sieve.
But the filters are not
2016 Oct 19
2
sieve sending vacation message from vmail@ns1.domain.tld
Also, please provide an example scenario; i.e., for one problematic
delivery provide:
- The values of the variables substituted in the dovecot-lda command
line; i.e., provide that command line.
- The incoming e-mail message.
Regards,
Stephan.
Op 19-10-2016 om 12:43 schreef Matthew Broadhead:
> dovecot is configured by sentora control panel to a certain extent. if
> you want those
2016 Oct 19
3
sieve sending vacation message from vmail@ns1.domain.tld
Op 19-10-2016 om 13:47 schreef Matthew Broadhead:
> i am not 100% sure how to give you the information you require.
>
> my current setup in /etc/postfix/master.cf is
> flags=DRhu user=vmail:mail argv=/usr/libexec/dovecot/deliver -d
> ${recipient}
> so recipient would presumably be user at domain.tld? or do you want the
> real email address of one of our users? is there
2014 Sep 26
1
Dovecot Sieve and Postfix header_checks Issue
Hello List,
I tried to subscribe but it's taking forever for the confirmation email to arrive so I thought I would ask away by emailing directly. My apologies in advance should this question appear twice.
It may seem real simple to experts but I cannot really figure it out. I'll try to be concise:
Dovecot version is 2.1.7. Its dovecot ?n is real short one and follows right after my
2016 Oct 20
2
sieve sending vacation message from vmail@ns1.domain.tld
do i need to provide more information?
On 19/10/2016 14:49, Matthew Broadhead wrote:
> /var/log/maillog showed this
> Oct 19 13:25:41 ns1 postfix/smtpd[1298]: 7599A2C19C6:
> client=unknown[127.0.0.1]
> Oct 19 13:25:41 ns1 postfix/cleanup[1085]: 7599A2C19C6:
> message-id=<edc55a9b-eb49-3945-dc60-0e1d51a78e97 at nbmlaw.co.uk>
> Oct 19 13:25:41 ns1 postfix/qmgr[1059]:
2011 May 18
3
Dovecot deliver
Hi all,
I have a problem with my dovecot/postfix configuration:
here is my dovecot -n
# 1.2.16: /etc/dovecot.conf
Warning: fd limit 128 is lower than what Dovecot can use under full
load (more than 768). Either grow the limit or change
login_max_processes_count and max_mail_processes settings
# OS: OpenBSD 4.9 i386 nfs
base_dir: /var/dovecot/
log_path: /var/log/dovecot
protocols: imaps pop3s
2016 Nov 02
2
sieve sending vacation message from vmail@ns1.domain.tld
is there something more i need to be doing my end?
On 25/10/2016 09:11, Matthew Broadhead wrote:
> are there any instructions or tests i can make to check the sieve
> configuration? or does the magic all happen internally and there are
> no settings to change?
>
> On 21/10/2016 10:22, Matthew Broadhead wrote:
>> the server is using CentOS 7 and that is the package that
2015 Feb 12
2
Dovecot dsync not replicating ".dovecot.sieve -> .sieve/managesieve.sieve" / setactive
Hello,
I've ran into problem with Dovecot and dsync replication. Everything
works perfectly, including replication of sieve scripts, except fact
that if user activates the 'managesieve' ruleset (I'm using currently
Roundcubemail) on "mail1" host, it wouldn't be activated on "mail2"
host, by creating symlink ".dovecot.sieve ->
2018 Mar 02
3
Sieve filter fileinto doesn't preserve flags
Using `fileinto` to move a mail into another mailbox removes flags
that have been set with a previous sieve filter with `addflag`.
# 2.2.33.2 (d6601f4ec): /etc/dovecot/dovecot.conf
# Pigeonhole version 0.4.21 (92477967)
# OS: Linux 4.9.0-6-amd64 x86_64 Debian 9.1 ext4
lda_mailbox_autocreate = yes
lda_mailbox_autosubscribe = yes
mail_debug = yes
mail_location = maildir:/var/vmail/%d/%n
2016 Oct 21
3
sieve sending vacation message from vmail@ns1.domain.tld
the server is using CentOS 7 and that is the package that comes through
yum. everything is up to date. i am hesitant to install a new package
manually as that could cause other compatibility issues? is there
another way to test the configuration on the server?
On 21/10/2016 01:07, Stephan Bosch wrote:
> Op 10/20/2016 om 7:38 PM schreef Matthew Broadhead:
>> do i need to provide
2011 Mar 29
3
global sieve not working
My global sieve rule is not working and do not compile. But per-user sieve
is working.
Here is my dovecot -n:
log_path: /var/log/dovecot.log
protocols: imap pop3
ssl: no
login_dir: /var/run/dovecot/login
login_executable(default): /usr/libexec/dovecot/imap-login
login_executable(imap): /usr/libexec/dovecot/imap-login
login_executable(pop3): /usr/libexec/dovecot/pop3-login
mail_uid: 501
mail_gid:
2018 Mar 02
4
Sieve filter imapflags with "flagvar" not working
Following the rfc5232, Sieve Email Filtering: Imap4flags Extension
the following filter doesn't work when the `"flagvar"` part is added
require "imap4flags";
if header :contains "X-Spam" "Yes" {
? setflag "flagvar" "spam";
}
removing the `"flagvar"` part works as expected
# 2.2.33.2 (d6601f4ec):
2015 Apr 27
3
Fatal: Error in configuration file /etc/dovecot/dovecot.conf: protocols: Unknown protocol: sieve
Here is the output from dovecot -n
# 2.2.9: /etc/dovecot/dovecot.conf
# OS: Linux 3.13.0-32-generic x86_64 Ubuntu 14.04.2 LTS ext4
auth_mechanisms = plain login
auth_verbose = yes
log_path = /var/log/dovecot.log
mail_debug = yes
mail_location = maildir:/var/mail/vhosts/%d/%n
namespace inbox {
inbox = yes
location =
mailbox Drafts {
special_use = \Drafts
}
mailbox Junk {
special_use = \Junk
}
2009 Apr 17
3
Setup Question
I really want to try and get this plus addressing working correctly with
Dovecot and Postfix. After doing some reading I think I am going to
change my Postfix setup from mailbox_command to mailbox_transport. I
have a few questions to make sure I am thinking correctly. All of my
users are system users. Their mail is delivered directly to their
"/home/<user>/Maildir"