It was related to some memory allocation in go. When I increased the memory in lmtp. This problem was solved. Others started to notice this after some specific version update of go.
Op 19-9-2024 om 22:46 schreef Marc via dovecot:
I am trying to modify the body of message with a global sieve script. It looks like that sieve-test does not generate this error, however I am not really able to verify the output. There does not seem to be an option to catch the output (new message)
In sieve-test, any action that sends a message is just printing it to the screen. So, you could just issue "redirect" in execute mode.
trace log 00000008: 3: finishing match with result: matched 00000029: 3: jump if result is false 00000029: 3: not jumping 0000002e: 5: filter action 0000002e: 5: execute program `sieve-command' 0000002e: 5: filter action: program indicated false result 0000005f: ## Finished executing script 'commands'
require ["vnd.dovecot.execute","vnd.dovecot.filter","vnd.dovecot.debug"]; #if true if header :contains "Subject" "xxxx" { filter "sieve-command" ["-task","xxxx"]; }
dovecot log (1166226): Terminated with non-zero exit code 2
dovecot mailing list --dovecot@dovecot.org To unsubscribe send an email todovecot-leave@dovecot.org
dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-leave@dovecot.org