Hello, I am trying to set sieve up on a Centos 7 server. It's a configuration with postfix, Maildir, MySQL and virtual domains which works fine. I have created a simple .dovecot.sieve in the user's directory: # cat /home/mail/domain.com/user/.dovecot.sieve require "fileinto"; redirect "other_address at other_domain.com"; Here are the logs: dovecot: lda(user at domain.com): Debug: sieve: Pigeonhole version 0.4.2 initializing lda(user at domain.com): Debug: sieve: include: sieve_global_dir is not set; it is currently not possible to include `:global' scripts. dovecot: lda(user at domain.com): Debug: sieve: script file /home/mail/ domain.com/.dovecot.sieve not found dovecot: lda(user at domain.com): Debug: sieve: user's script ~/.dovecot.sieve doesn't exist (trying default script location instead) lda(user at domain.com): Debug: sieve: no default script configured for user lda(user at domain.com): Debug: sieve: user has no valid location for a personal script lda(user at domain.com): Debug: sieve: no scripts to execute: reverting to default delivery. dovecot: lda(user at domain.com): msgid=<005b01d269ca$f287ebf0$d797c3d0$@fr>: saved mail to INBOX It tells that user's script ~/.dovecot.sieve doesn't exis However, on the troubleshooting guide, I can see these logs: dovecot: lda(hendrik): Debug: sieve: using sieve path for user's script: /home/hendrik/.dovecot.sieve dovecot: lda(hendrik): Debug: sieve: opening script /home/hendrik/.dovecot.sieve As you can see, it refers to "lda(hendrik)" but not "lda(user at domain.com" I am wondering whether Sieve looks for the file elsewhere than /home/mail/ domain.com/user/.dovecot.sieve Do you have any idea?
Am 08.01.2017 um 17:31 schrieb Jibeji:> Hello, > I am trying to set sieve up on a Centos 7 server. > It's a configuration with postfix, Maildir, MySQL and virtual domains which > works fine. > > I have created a simple .dovecot.sieve in the user's directory: > > # cat /home/mail/domain.com/user/.dovecot.sieve > require "fileinto"; > redirect "other_address at other_domain.com"; > > > Here are the logs: > > dovecot: lda(user at domain.com): Debug: sieve: Pigeonhole version 0.4.2 > initializing > lda(user at domain.com): Debug: sieve: include: sieve_global_dir is not set; > it is currently not possible to include `:global' scripts. > dovecot: lda(user at domain.com): Debug: sieve: script file /home/mail/ > domain.com/.dovecot.sieve not found > dovecot: lda(user at domain.com): Debug: sieve: user's script ~/.dovecot.sieve > doesn't exist (trying default script location instead) > lda(user at domain.com): Debug: sieve: no default script configured for user > lda(user at domain.com): Debug: sieve: user has no valid location for a > personal script > lda(user at domain.com): Debug: sieve: no scripts to execute: reverting to > default delivery. > dovecot: lda(user at domain.com): msgid=<005b01d269ca$f287ebf0$d797c3d0$@fr>: > saved mail to INBOX > > It tells that user's script ~/.dovecot.sieve doesn't exis > > However, on the troubleshooting guide, I can see these logs: > > dovecot: lda(hendrik): Debug: sieve: using sieve path for user's script: > /home/hendrik/.dovecot.sieve > dovecot: lda(hendrik): Debug: sieve: opening script > /home/hendrik/.dovecot.sieve > > As you can see, it refers to "lda(hendrik)" but not "lda(user at domain.com" > > I am wondering whether Sieve looks for the file elsewhere than /home/mail/ > domain.com/user/.dovecot.sieve > > Do you have any idea?You hopefully see that you have mismatching path information: > dovecot: lda(user at domain.com): Debug: sieve: script file /home/mail/ > domain.com/.dovecot.sieve not found > dovecot: lda(hendrik): Debug: sieve: using sieve path for user's script: > /home/hendrik/.dovecot.sieve So please provide your "doveconf -n" output or at least validate yourself the sieve settings. And .dovecot.sieve is a symlink to the active sieve filter. Alexander
Hello,
Here it is:
# 2.2.10: /etc/dovecot/dovecot.conf
# OS: Linux 3.14.32-xxxx-grs-ipv6-64 x86_64
first_valid_gid = 5000
first_valid_uid = 5000
lda_mailbox_autocreate = yes
lda_mailbox_autosubscribe = yes
mail_access_groups = vmail
mail_location = /home/mail/%d/%n
mail_privileged_group = vmail
managesieve_notify_capability = mailto
managesieve_sieve_capability = fileinto reject envelope encoded-character
vacation subaddress comparator-i;ascii-numeric relational regex imap4flags
copy include variables body enotify environment mailbox date ihave
mbox_write_locks = fcntl
mmap_disable = yes
namespace inbox {
inbox = yes
location mailbox Drafts {
special_use = \Drafts
}
mailbox Junk {
special_use = \Junk
}
mailbox Sent {
special_use = \Sent
}
mailbox "Sent Messages" {
special_use = \Sent
}
mailbox Trash {
special_use = \Trash
}
prefix }
passdb {
args = /etc/dovecot/dovecot-sql.conf.ext
driver = sql
}
plugin {
sieve = ~/.dovecot.sieve
sieve_dir = ~/sieve
}
postmaster_address = postmaster at radioamateur.org
protocols = imap pop3 sieve
service auth {
unix_listener /var/spool/postfix/private/auth {
group = postfix
mode = 0600
user = postfix
}
unix_listener auth-userdb {
group = vmail
mode = 0600
user = vmail
}
}
ssl = required
ssl_cert = </etc/httpd/ssl/public.new.crt
ssl_key = </etc/httpd/ssl/private.new.key
ssl_protocols = !SSLv2 !SSLv3
userdb {
args = /etc/dovecot/dovecot-sql.conf.ext
driver = sql
}
protocol lda {
mail_plugins = sieve
}
On Sun, Jan 8, 2017 at 6:05 PM, Alexander Dalloz <ad+lists at uni-x.org>
wrote:
> Am 08.01.2017 um 17:31 schrieb Jibeji:
>
>> Hello,
>> I am trying to set sieve up on a Centos 7 server.
>> It's a configuration with postfix, Maildir, MySQL and virtual
domains
>> which
>> works fine.
>>
>> I have created a simple .dovecot.sieve in the user's directory:
>>
>> # cat /home/mail/domain.com/user/.dovecot.sieve
>> require "fileinto";
>> redirect "other_address at other_domain.com";
>>
>>
>> Here are the logs:
>>
>> dovecot: lda(user at domain.com): Debug: sieve: Pigeonhole version
0.4.2
>> initializing
>> lda(user at domain.com): Debug: sieve: include: sieve_global_dir is not
set;
>> it is currently not possible to include `:global' scripts.
>> dovecot: lda(user at domain.com): Debug: sieve: script file /home/mail/
>> domain.com/.dovecot.sieve not found
>> dovecot: lda(user at domain.com): Debug: sieve: user's script
>> ~/.dovecot.sieve
>> doesn't exist (trying default script location instead)
>> lda(user at domain.com): Debug: sieve: no default script configured for
user
>> lda(user at domain.com): Debug: sieve: user has no valid location for a
>> personal script
>> lda(user at domain.com): Debug: sieve: no scripts to execute: reverting
to
>> default delivery.
>> dovecot: lda(user at domain.com): msgid=<005b01d269ca$f287ebf0$d
>> 797c3d0$@fr>:
>> saved mail to INBOX
>>
>> It tells that user's script ~/.dovecot.sieve doesn't exis
>>
>> However, on the troubleshooting guide, I can see these logs:
>>
>> dovecot: lda(hendrik): Debug: sieve: using sieve path for user's
script:
>> /home/hendrik/.dovecot.sieve
>> dovecot: lda(hendrik): Debug: sieve: opening script
>> /home/hendrik/.dovecot.sieve
>>
>> As you can see, it refers to "lda(hendrik)" but not
"lda(user at domain.com"
>>
>> I am wondering whether Sieve looks for the file elsewhere than
/home/mail/
>> domain.com/user/.dovecot.sieve
>>
>> Do you have any idea?
>>
>
> You hopefully see that you have mismatching path information:
>
> > dovecot: lda(user at domain.com): Debug: sieve: script file
/home/mail/
> > domain.com/.dovecot.sieve not found
>
> > dovecot: lda(hendrik): Debug: sieve: using sieve path for user's
script:
> > /home/hendrik/.dovecot.sieve
>
> So please provide your "doveconf -n" output or at least validate
yourself
> the sieve settings.
>
> And .dovecot.sieve is a symlink to the active sieve filter.
>
> Alexander
>