The first time when the sieve files and folders get created, the active symlink is created as a full absolute path
.active_sieve -> /mnt/email/domain/user/_sieve/filters.sieveAfter that, if you disable and enable the rule set the symlink gets recreated as relative
.active_sieve -> filters.sieveHow can i have the symlink always created as a relative path even on first time creation? Having a full absolute path over a mounted NSF is fragile.
Dovecot 2.3.16 Pigeonhole 2.3.16
mail_home = /mnt/email/%d/%n/_dovecot mail_location = maildir:/mnt/email/%d/%n/_folders:INDEX=/mnt/email/%d/%n/_dovecot:CONTROL=/mnt/email/%d/%n/_dovecot plugin { sieve = file:~/../_sieve;active=~/../_sieve/.active_sieve sieve_max_script_size = 1M sieve_max_actions = 32 sieve_max_redirects = 4 sieve_quota_max_scripts = 20 sieve_quota_max_storage = 5M sieve_vacation_min_period = 1d sieve_vacation_use_original_recipient = no sieve_vacation_dont_check_recipient = no sieve_vacation_send_from_recipient = no sieve_redirect_envelope_from = sender sieve_user_email = %u }
User home != mail home?
mail not in the user home? is that the situation?
On 25/08/2022 13:32, dovecot@ptld.com wrote:
The first time when the sieve files and folders get created, the active symlink is created as a full absolute path
.active_sieve -> /mnt/email/domain/user/_sieve/filters.sieve
After that, if you disable and enable the rule set the symlink gets recreated as relative
.active_sieve -> filters.sieve
How can i have the symlink always created as a relative path even on first time creation? Having a full absolute path over a mounted NSF is fragile.
Dovecot 2.3.16 Pigeonhole 2.3.16
mail_home = /mnt/email/%d/%n/_dovecot mail_location = maildir:/mnt/email/%d/%n/_folders:INDEX=/mnt/email/%d/%n/_dovecot:CONTROL=/mnt/email/%d/%n/_dovecot plugin { sieve = file:~/../_sieve;active=~/../_sieve/.active_sieve sieve_max_script_size = 1M sieve_max_actions = 32 sieve_max_redirects = 4 sieve_quota_max_scripts = 20 sieve_quota_max_storage = 5M sieve_vacation_min_period = 1d sieve_vacation_use_original_recipient = no sieve_vacation_dont_check_recipient = no sieve_vacation_send_from_recipient = no sieve_redirect_envelope_from = sender sieve_user_email = %u }
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?
No, mail is not stored in /home/ because these are virtual users.
I would not want to create 1,000+ linux users with home directories just to provide email accounts to people who will never login to linux.
On 25/08/2022 15:20, dovecot@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/userwhen you say user home?
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 me know.
No, mail is not stored in
/home/because these are virtual users. I would not want to create 1,000+ linux users with home directories just to provide email accounts to people who will never login to linux.
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 me know.
If you review my first email you can see that home is being set in the config. Although i not sure how setting home has anything to do with sieve active symlinks.
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 and, since the home is defined keep the default value for the sieve
On 26/08/2022 14:57, dovecot@ptld.com wrote:
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 me know.
If you review my first email you can see that home is being set in the config. Although i not sure how setting home has anything to do with sieve active symlinks.
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 has ~ same as yours. And /../ is a relative path feature, you don't see /../ in full absolute paths.
So how is using ~ and a relative path creating an absolute symlink? How do you prevent it so dovecot only creates a relative symlink?
On 26/08/2022 16:43, dovecot@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, mine is "active=~/../_sieve/.active_sieve" which has ~ same as yours. And /../ is a relative path feature, you don't see /../ in full absolute paths.
But somehow can be interfering. In my case I would try. It is possible?
ls /home/../tmp
is valid, it's relative or absolute?
So how is using ~ and a relative path creating an absolute symlink? How do you prevent it so dovecot only creates a relative symlink?
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 like this has completely gone off the rails.
participants (2)
-
dovecot＠ptld.com
-
João Silva