sieve script executed only when my client (thunderbird) is open and connected

[siktec-lab]

So, Everything is working fine, and I have a mailbox with a sieve script activated (which executes an external program).
When my local client (Thunderbird) is connected to the server and polling for incoming emails, the sieve script triggers. But when my client is closed, and an email is sent, the script fails with a timeout: "... Forcibly terminated with signal 15" in the logs.
What am I missing? Is there a way to process emails immediately?

[polarathene]

You should probably share more details, the easier it is to reproduce the better someone could chime in to assist.

My experience with sieve is that it works without needing any mail client connected. Probably something wrong with your configuration, or you're trying to do something a bit differently.

[polarathene]

I would just replace it with a basic script then, something that doesn't really do anything. Then see if that works without Thunderbird open, if it does, you'll know that it's something your script is doing.

[siktec-lab]

@polarathene, you are right. It seems that something else is happening, and the relation to the client being open or not is coincidental.
It's hard to debug, though. At this point, it's pretty random. My best guess right now is that it's related to querying the Google Sheets API.
It could be as simple as an execution time limit.
Do you know how we can increase those limits (if there are any)?
I saw some related stuff on Dovecot docs, but I'm unsure.

Finally, while trying to debug the Python script, I realized I couldn't interact with the file system at all. To my best understanding, this is because the "account user" is limited to its own folder.
Is there a way around that?

Thank you for your time and help :)

[polarathene]

I don't use sieve myself, you'll need someone else interested in such functionality to chime in and discuss.

I realized I couldn't interact with the file system at all. To my best understanding, this is because the "account user" is limited to its own folder.
Is there a way around that?

I think with ACCOUNT_PROVISIONER=FILE all users share the same 5000:5000 UID/GID, while with LDAP it's potentially different for each user.

Dovecot switches to the account UID/GID for security reasons, you shouldn't have write access to root owned parts of the filesystem.

Probably a few ways to approach whatever it is you're doing, but it's out of scope for support in DMS 😅

[siktec-lab]

I finally got it working reliably, and it's all buried in the Dovecot and plugin-specific configurations.

💡 It's a timeout problem, so whenever a Sieve script complains with a Forcibly terminated with signal 15,, it's probably a long-running script.

I appreciate your help, @polarathene. You are fantastic.