search for: be3h7irf

...errors for a while and then complained > only about one of the scripts, now both scripts seems to say > something but I'm not sure what. Maybe I'll try to recreate the > files for fun. The relevant mail_debug lines seem to be these: dovecot: lmtp(testuser at example.com): Debug: Be3h7iRf/1TnUw2PM/SpMA: sieve: Opening script 1 of 2 from `/usr/local/var/dovecot/sieve/script1.sieve' dovecot: lmtp(testuser at example.com): Debug: Be3h7iRf/1TnUw2PM/SpMA: sieve: Loading script /usr/local/var/dovecot/sieve/script1.sieve dovecot: lmtp(testuser at example.com): Debug: Be3h7iRf/1TnUw2PM/...

On 3/10/2015 8:11 PM, E.B. wrote: >> Last time I had a few stupid problems in the releases, so >> I'll follow >> Timo's example and I release an RC first. >> >> The highlights include the implementation of the index and >> metadata >> extensions. Quite a few bugs are fixed as well. > When I compiled and installed this, Sieve scripts were being

...ot override settings such as that (and log_path) from > a userdb lookup? Hmm, I WAS able to override mail_debug from userdb, > but not log_path? > > Sieve-related mail_debug, then? > > This looks like the relevant log info: > > dovecot: lmtp(testuser at example.com): Debug: Be3h7iRf/1TnUw2PM/SpMA: sieve: file storage: Storage path `/vmail/example.com/testuser/sieve' not found > dovecot: lmtp(testuser at example.com): Debug: Be3h7iRf/1TnUw2PM/SpMA: sieve: No default script configured for user > dovecot: lmtp(testuser at example.com): Debug: Be3h7iRf/1TnUw2PM/SpMA: sie...

...log_path) from > > a userdb lookup? Hmm, I WAS able to override mail_debug from userdb, > > but not log_path? > > > > Sieve-related mail_debug, then? > > > > This looks like the relevant log info: > > > > dovecot: lmtp(testuser at example.com): Debug: Be3h7iRf/1TnUw2PM/SpMA: sieve: file storage: Storage path `/vmail/example.com/testuser/sieve' not found > > dovecot: lmtp(testuser at example.com): Debug: Be3h7iRf/1TnUw2PM/SpMA: sieve: No default script configured for user > > dovecot: lmtp(testuser at example.com): Debug: Be3h7iRf/1TnUw2PM...

...> only about one of the scripts, now both scripts seems to say > > something but I'm not sure what. Maybe I'll try to recreate the > > files for fun. > > The relevant mail_debug lines seem to be these: > > dovecot: lmtp(testuser <at> example.com): Debug: Be3h7iRf/1TnUw2PM/SpMA: sieve: Opening script 1 of 2 > from `/usr/local/var/dovecot/sieve/script1.sieve' > dovecot: lmtp(testuser <at> example.com): Debug: Be3h7iRf/1TnUw2PM/SpMA: sieve: Loading script /usr/local/var/dovecot/sieve/script1.sieve > dovecot: lmtp(testuser <at> example....

...didn't get any replies - can I not override settings such as that (and log_path) from a userdb lookup? Hmm, I WAS able to override mail_debug from userdb, but not log_path? Sieve-related mail_debug, then? This looks like the relevant log info: dovecot: lmtp(testuser at example.com): Debug: Be3h7iRf/1TnUw2PM/SpMA: sieve: file storage: Storage path `/vmail/example.com/testuser/sieve' not found dovecot: lmtp(testuser at example.com): Debug: Be3h7iRf/1TnUw2PM/SpMA: sieve: No default script configured for user dovecot: lmtp(testuser at example.com): Debug: Be3h7iRf/1TnUw2PM/SpMA: sieve: User h...

> > I have some global scripts that were running nicely. > > > > Then I opened one in an editor and (probably, but not 100% sure) > > mindlessly saved the file, even though I hadn't made any changes. > > > > Shortly after, Sieve errors started showing in the log: > > > > Error: 4k5JA74R/1TlIwABG/SpMA: sieve: binary save: failed to create