No, I just tried it with "sieveshell -u cyrus localhost" and it failed, which I expected. Then I ran with "-a cyrus" and it worked. I hadn't even thought of the default behaviour of assuming "-u <login user>". Joost's point is that he's unable to run the current version with -u <adminuser> and so cannot administer global sieve scripts. I was just trying to think around that.
-nic
On 4/15/24 14:13, Simon Matter wrote:
Joost, Doh! My apologies. I should have thought that through a bit more before commenting. -nicCould it be that the user should be cyrus (or another admin user)? I mean, Nic, did you run sieveshell as user cyrus? Regards, SimonOn 4/15/24 13:58, J. Roeleveld via Info wrote:On Monday, 15 April 2024 14:08:25 CEST Nic Bernstein wrote:[Going back to the original message due to subsequent trimming] I haven't got v3.8.1 installed, but I've just checked on my older v3 release I use this command to see Global sieve scripts: $*sieveshell -a cyrus localhost* connecting to localhost Please enter your password: > ls default <- active script In other words, no "-u <user>" since this isn't a "user" in the proper sense. Have you tried this approach? -nicIf I don't specify a "-u <user>", it uses whichever username I am logged in as on the server. I have no access to the global sieve-scripts this way. And the command I am using is the one that is even still documented for the current DEV version. I think there should be still a way to access and change the global sieve- scripts. Physically there are stored at: <sievedir>/global/.... With <sievedir> being configured as " sievedir: <sievedir> " in imapd.conf. I also see the users sieve-scripts stored in that tree as: <sievedir>/j/user/joost/.... (<--- this is the sieve-script(s) for my user are stored) -- JoostOn 4/12/24 12:38, Joost Roeleveld via Info wrote:Hi all, I "recently" upgraded to cyrus-imap version 3.8.1. This has been running correctly, but now that I want to update a global sievescript (for a shared mailbox), I find that I can not login using the user I got specified as "admins". This user/password still works when connecting using "cyradm", but when using it with "sieveshell", it fails: # sieveshell -a <adminuser> -u <adminuser> localhost connecting to localhost Please enter your password: Please enter your password: Please enter your password: unable to connect to server at /usr/bin/sieveshell line 202, <STDIN> line 3. In the logs, I see: Apr 12 11:24:52 mailstore1 cyrus/sieve[22174]: Falling back to using legacy location for cyrus.dav Apr 12 11:24:52 mailstore1 cyrus/sieve[22174]: IOERROR: failed to create user.<adminuser>.#sieve (Permission denied) Apr 12 11:24:52 mailstore1 cyrus/sieve[22174]: error in actions_setuser() Apr 12 11:24:52 mailstore1 cyrus/sieve[22174]: Lost connection to client -- exiting Obviously, the mentioned folder doesn't exist, there isn't even a " user.<adminuser> " folder, which there shouldn't as there should never be email sent to this account. Can someone let me know what I need to change in my commands or am I hitting a bug? Many thanks, Joost------------------------------------------ Cyrus: Info Permalink:https://cyrus.topicbox.com/groups/info/Tac9e88ede3418262-M7092c392246e65800f69513d Delivery options:https://cyrus.topicbox.com/groups/info/subscription-- Nic Bernsteinnic@xxxxxxxxxxxxxxxx https://www.nicbernstein.com------------------------------------------ Cyrus: Info Permalink: https://cyrus.topicbox.com/groups/info/Tac9e88ede3418262-M9c8e4b5c920fdb49d984924d Delivery options: https://cyrus.topicbox.com/groups/info/subscription
-- Nic Bernstein nic@xxxxxxxxxxxxxxxx https://www.nicbernstein.com
