similar to: Restrictions on default.sieve

On 21 Oct 2020, at 11:51, PGNet Dev <pgnet.dev at gmail.com> wrote: > On 10/21/20 10:29 AM, @lbutlr wrote: >> Are there actions that default.sieve cannot take? >> I tried adding >> redirect :copy "backup+foo at local.example.com" > > do you have an explicit > > require ["copy"]; Nope. <thud>? All try again. For the record, the

On 10 Apr 2019, at 09:06, @lbutlr via dovecot <dovecot at dovecot.org> wrote: > Should I add > > service stats { > unix_listener stats-writer { > user = dovecot > } > unix_listener stats-reader { > user = dovecot > } > } > > to my dovecot.conf file? I did this and it appears to have fixed the issue. Also, the failed message strongly

So, I have the sieve working up to the point that it calls the script, and the script is called (I get different errors if the script is not there, for example). filter action execute program `darkmode.sh' [[EXECUTION ABORTED]] There's no other error logged (for example, when I had sieve_filter_bin_dir miss-set, I would get: sieve: action filter: failed to execute program

On 10/21/20 1:10 PM, @lbutlr wrote: > I have trace logs enabled for user scripts, but I think only error get logged for upper level, and only along the lines of "could not compile <name of sieve>". verify that you can compile the scripts manually, even as root then double-check your perms on your sieve/ dir, making sure that the write perms are correct for your dovecot

On Wed, 10 Apr 2019 at 17:50, @lbutlr via dovecot <dovecot at dovecot.org> wrote: > On 10 Apr 2019, at 08:36, @lbutlr via dovecot <dovecot at dovecot.org> wrote: > > net_connect_unix(/var/run/dovecot/stats-writer) failed: Permission den)) > > One other detail: > > /var/run/dovecot/stats-writer: > 0 srw-rw---- 1 root dovecot 0 Apr 10 08:47 stats-writer

On 08.03.2018 03:09, @lbutlr wrote: > On 2018-03-06 (14:41 MST), "@lbutlr" <kremels at kreme.com> wrote: >>> and using "doveadm search mailbox $VIRTUAL_MAILBOX? >> # doveadm search mailbox "@virtual.day" -u kremels >> # > Any clues on this? As far as I can tell from the documentation and the list this should work, but it is not. > You

> On 10 April 2019 20:48 @lbutlr via dovecot <dovecot at dovecot.org> wrote: > > > On 10 Apr 2019, at 10:43, @lbutlr via dovecot <dovecot at dovecot.org> wrote: > > lso, the failed message strongly implies that the email was not delivered, since it happens on the delivery log line and there is not indication in the log that delivery succeeded. However, the message

On 13 Jun2019, at 23:24, Aki Tuomi via dovecot <dovecot at dovecot.org <mailto:dovecot at dovecot.org>> wrote: > On 14 June 2019 04:25 @lbutlr via dovecot < dovecot at dovecot.org> wrote: >> >> >> Well, progress. At least now editheader loads. Sadly that brings up new errors. >> >> specified field name `Reply-To:' is invalid. >>

On 10/21/20 2:12 PM, @lbutlr wrote: > Do I HAVE to have a default.sieve, that's the only thing that I can think the has changed in that folder. RE: compile, fyi note @ https://wiki2.dovecot.org/Pigeonhole/Sieve/Usage#Manually_Compiling_Sieve_Scripts https://wiki2.dovecot.org/Pigeonhole/Sieve/Configuration#Executing_Multiple_Scripts_Sequentially the conditions under which you need to

One of my accounts was having login failures when trying to send mail, but was able to check mail. I tried everything I could think of to see what the issue might be, but eventually went in and reset the password in the sql database (I knew the password, so I reset it to the same password). {SHA256-CRYPT}$5$VuS? {SHA256-CRYPT}$5$VI7? So the password was updated properly. Clients can still

On 21 Oct 2020, at 14:10, @lbutlr <kremels at kreme.com> wrote: > I have trace logs enabled for user scripts, but I think only error get logged for upper level, and only along the lines of "could not compile <name of sieve>". Any ideas? Is there a way to force the default and sieve_before scripts to log to syslog? -- The real world was far too real to leave neat little

On 13 Feb 2018, at 00:11, Aki Tuomi <aki.tuomi at dovecot.fi> wrote: > doveadm -u "*mask*" makes no sense. The ?index? that was in the first line was dropped out of my further examples. But now where was there a ?*mask*?. > what command are you trying to run? # doveadm index -u ?*@sqldomain.tld" "*? Error: User listing returned failure doveadm: Error: Failed to

On Jun 4, 2019, at 1:43 PM, Stephan Bosch via dovecot <dovecot at dovecot.org> wrote: > Op 30-5-2019 om 9:46 schreef @lbutlr via dovecot: >> Error: program `/usr/lib/dovecot/sieve/sa-learn-spam.sh' terminated abnormally, signal 11 >> Error: sieve: pipe action: failed to pipe message to program `sa-learn-spam.sh': refer to server log for more information. [2019-05-29

How would I get the rule if header :contains "X-spam-flag" "YES" { fileinto "Junk"; } To apply to all users mail at delivery time?

# 2.2.33.2 (d6601f4ec): If I do doveadm index -u user "*" for a local user, it works fine, but if I do doveadm -u "*@sqldomain.tld" "*" or doveadm -u "*@localaliasdomain.tld" "*" or doveadm -u "*@localdomain.tld" "*" or doveadm -u "user at localdomain.tld" "*" it fails, ? -u "user

On Jun 6, 2019, at 1:03 PM, @lbutlr via dovecot <dovecot at dovecot.org> wrote: > On Jun 6, 2019, at 4:45 AM, @lbutlr via dovecot <dovecot at dovecot.org> wrote: >> imapsieve_mailbox2_before = file:/usr/lib/dovecot/sieve/report-ham.sieve >> imapsieve_mailbox2_causes = COPY >> imapsieve_mailbox2_from = Junk >> imapsieve_mailbox2_name = * > > One other

See comment in context below: On Fri, 2019-10-11 at 19:26 -0600, @lbutlr via dovecot wrote: > On Oct 11, 2019, at 2:00 PM, Joseph Tam <jtam.home at gmail.com> wrote: > > On Fri, 11 Oct 2019, @lbutlr wrote: > > > >>>> Oct 09 16:02:50 imap-login: Info: Aborted login (auth failed, 5 attempts in 33 secs): user=<myuser at covisp.net>, xx.xx.xx.xx, PLAIN, TLS

I was trying to process a bunch of folders to sync them to another drive and ran across an error I haven’t seen before. Normally I do this sync via a mounted file system, but this time I tried to do it over ssh: find . -type f -atime -1 -exec rsync -aP {} 10.0.0.11:/Volumes/Drive5/{} \; bash: -c: line 0: syntax error near unexpected token `(' bash: -c: line 0: `rsync --server -logDtpre.iLsfx

I do know that sub-addressing with a special character is nowadays a normal, better, way to do it. Unfortunately we have used this system for a very long time, starting around 2005... So there are a lot of existing email addresses. I am considering changing to a new hosting company, that's why I started looking for a solution.? The current company has very limited functionality for

I created some new users in my MySQL database using postfoxadmin. The passwords looked correct in the database and show the right prefix {SHA256-CRYPT} but logins were failing, so I manually created new passwords from the command line: doveadm pw -s SHA256-CRYPT -p ?a password" -u kremels at kreme.com {SHA256-CRYPT}$5$ZKsovTv0Ddc9k4? I then went into the postfix database and manually