On 25/08/2022 15:20, dove...@ptld.com wrote:
On 08-25-2022 9:10 am, João Silva wrote:
User home != mail home?
mail not in the user home? is that the situation?
Do you mean `/home/user` when you say user home?
Made the question before knowing about the virtual users.
But dovecot allow to
On 08-26-2022 9:22 am, João Silva wrote:
Made the question before knowing about the virtual users.
But dovecot allow to set a "home" for virtual users (as far as I undestood)
https://wiki2.dovecot.org/VirtualUsers/Home?highlight=%28home%29|%28mail%29
If already had read that and didn't help let
As far as I understood the sieve location is relative to the home.
In my server I kept the default
sieve = file:~/sieve;active=~/.dovecot.sieve
the sieve is defined with relation to the home ~
In your definition there are ../ in the mix
so
home
inside the home a Maildir or whetever you want
On 08-26-2022 11:34 am, João Silva wrote:
As far as I understood the sieve location is relative to the home.
True.
In my server I kept the default
sieve = file:~/sieve;active=~/.dovecot.sieve
In your definition there are ../ in the mix
Yes, mine is "active=~/../_sieve/.active_sieve" which h
On 26/08/2022 16:43, dove...@ptld.com wrote:
On 08-26-2022 11:34 am, João Silva wrote:
As far as I understood the sieve location is relative to the home.
True.
In my server I kept the default
sieve = file:~/sieve;active=~/.dovecot.sieve
In your definition there are ../ in the mix
Yes, mi
ls /home/../tmp
is valid, it's relative or absolute?
While valid, do you actually do that in your absolute paths?
And i still fail to see what any of it has to do with relative vs absolute
symlink creation as you acknowledge starting with ~ makes it relative to the
home directory.
I feel lik
