Re: Sieve with links?

2020-04-03 Thread @lbutlr
On 02 Apr 2020, at 05:02, @lbutlr  wrote:
> # doveadm sieve list -u user@domain
> doveadm(user@domain): Warning: sieve: file storage: Active sieve script 
> symlink /usr/local/virtual/user@domain/.active_sieve is no symlink.
> spamassassin ACTIVE

BTW, if I remove the link and place a normal file in that location (and stoped 
dovecot), I still get this warning. I checked about a dozen users and all 
returned this warning, regardless of it the .active_sieve file was a link or a 
regular file.

Other sieve scripts are working for other users.

===>>> dovecot-2.3.10_2
===>>> dovecot-pigeonhole-0.5.10


-- 
The omnipotent eyesight of various supernatural entities is often
remarked upon. It is said that they can see the fall of every
sparrow. And this may be true. But there is only one who is
always there when it hits the ground. —Hogfather




Re: Sieve with links?

2020-04-02 Thread @lbutlr
On 02 Apr 2020, at 06:27, Sami Ketola  wrote:
> if you do cat /usr/local/virtual/user@domain/.active_sieve does it follow the 
> symlink correctly?

Yes.

On 02 Apr 2020, at 05:03, Aki Tuomi  wrote:
> And what is the "default sieve file"?

The system-code one that runs for all users.

# cat /usr/lib/dovecot/sieve/default.sieve
require "fileinto";
if header :contains "X-spam-flag" "YES" {
 fileinto "Junk”;
}



-- 
"Are you pondering what I'm pondering?"
"I think so, Brain, but I find scratching just makes it worse.”




Re: Sieve with links?

2020-04-02 Thread Sami Ketola



> On 2 Apr 2020, at 14.02, @lbutlr  wrote:
> 
> On 02 Apr 2020, at 03:48, Aki Tuomi  wrote:
>> On 2.4.2020 11.07, @lbutlr wrote:
>>> Is there any reason that a .active_sieve file would not load because it is 
>>> a symbolic link? The target of the link is readable by the mail user, but 
>>> instead of getting the trace for the .active_sieve file, I only get the 
>>> trace for the default sieve file.
>> 
>> Does `doveadm sieve list` show it as active script?
> 
> Users are all virtual, so not sure who much that matters.
> 
> # doveadm sieve list  
> doveadm(root): Error: Couldn't drop privileges: User is missing UID (see 
> mail_uid setting)
> 
> # sudo -u vmail doveadm sieve list
> spamassassin ACTIVE
> 
> # doveadm sieve list -u user@domain
> doveadm(user@domain): Warning: sieve: file storage: Active sieve script 
> symlink /usr/local/virtual/user@domain/.active_sieve is no symlink.
> spamassassin ACTIVE
> 
> # ls -ls /usr/local/virtual/user@domain/.active_sieve
> 0 lrwxr-xr-x  1 root  vmail  50 Apr  2 04:58 .active_sieve -> 
> /usr/local/virtual/otheruser@domain/.sieve/listid
> 
> # ls -lsH  /usr/local/virtual/user@domain/.active_sieve
> 8 -rw-r--r--  2 vmail  vmail  1863 Apr  2 01:58 .active_sieve
> 

if you do cat /usr/local/virtual/user@domain/.active_sieve does it follow the 
symlink correctly?

Sami



Re: Sieve with links?

2020-04-02 Thread Aki Tuomi


On 2.4.2020 14.02, @lbutlr wrote:
> On 02 Apr 2020, at 03:48, Aki Tuomi  wrote:
>> On 2.4.2020 11.07, @lbutlr wrote:
>>> Is there any reason that a .active_sieve file would not load because it is 
>>> a symbolic link? The target of the link is readable by the mail user, but 
>>> instead of getting the trace for the .active_sieve file, I only get the 
>>> trace for the default sieve file.
>> Does `doveadm sieve list` show it as active script?
> Users are all virtual, so not sure who much that matters.
>
> # doveadm sieve list  
> doveadm(root): Error: Couldn't drop privileges: User is missing UID (see 
> mail_uid setting)
>
> # sudo -u vmail doveadm sieve list
> spamassassin ACTIVE
>
> # doveadm sieve list -u user@domain
> doveadm(user@domain): Warning: sieve: file storage: Active sieve script 
> symlink /usr/local/virtual/user@domain/.active_sieve is no symlink.
> spamassassin ACTIVE
>
> # ls -ls /usr/local/virtual/user@domain/.active_sieve
> 0 lrwxr-xr-x  1 root  vmail  50 Apr  2 04:58 .active_sieve -> 
> /usr/local/virtual/otheruser@domain/.sieve/listid
>
> # ls -lsH  /usr/local/virtual/user@domain/.active_sieve
> 8 -rw-r--r--  2 vmail  vmail  1863 Apr  2 01:58 .active_sieve
>
>
>
And what is the "default sieve file"?

Aki



Re: Sieve with links?

2020-04-02 Thread @lbutlr
On 02 Apr 2020, at 03:48, Aki Tuomi  wrote:
> On 2.4.2020 11.07, @lbutlr wrote:
>> Is there any reason that a .active_sieve file would not load because it is a 
>> symbolic link? The target of the link is readable by the mail user, but 
>> instead of getting the trace for the .active_sieve file, I only get the 
>> trace for the default sieve file.
> 
> Does `doveadm sieve list` show it as active script?

Users are all virtual, so not sure who much that matters.

# doveadm sieve list  
doveadm(root): Error: Couldn't drop privileges: User is missing UID (see 
mail_uid setting)

# sudo -u vmail doveadm sieve list
spamassassin ACTIVE

# doveadm sieve list -u user@domain
doveadm(user@domain): Warning: sieve: file storage: Active sieve script symlink 
/usr/local/virtual/user@domain/.active_sieve is no symlink.
spamassassin ACTIVE

# ls -ls /usr/local/virtual/user@domain/.active_sieve
0 lrwxr-xr-x  1 root  vmail  50 Apr  2 04:58 .active_sieve -> 
/usr/local/virtual/otheruser@domain/.sieve/listid

# ls -lsH  /usr/local/virtual/user@domain/.active_sieve
8 -rw-r--r--  2 vmail  vmail  1863 Apr  2 01:58 .active_sieve



-- 
Rule 1: To every rule there is an exception.




Re: Sieve with links?

2020-04-02 Thread Aki Tuomi


On 2.4.2020 11.07, @lbutlr wrote:
> Is there any reason that a .active_sieve file would not load because it is a 
> symbolic link? The target of the link is readable by the mail user, but 
> instead of getting the trace for the .active_sieve file, I only get the trace 
> for the default sieve file.
>
>

Does `doveadm sieve list` show it as active script?

Aki



Sieve with links?

2020-04-02 Thread @lbutlr
Is there any reason that a .active_sieve file would not load because it is a 
symbolic link? The target of the link is readable by the mail user, but instead 
of getting the trace for the .active_sieve file, I only get the trace for the 
default sieve file.


-- 
'Winners never talk about glorious victories. That's because they're
the ones who see what the battlefield looks like afterwards. It's
only the losers who have glorious victories.' --Small Gods