Re: Sieve EditHeaders and Logging

On 05/06/2020 05:29, ellie timoney wrote: > Hi David, > >> Is it possible to enable the "editheaders" sieve extension? if so, how? > > Not in 3.0, but it's available in 3.2 I plan to update to 3.2 once I have 3.0 working in my environment (I'm migrating an existing legacy 2.5.3 server). > >

Re: Sieve EditHeaders and Logging

Hi David, > Is it possible to enable the "editheaders" sieve extension? if so, how? Not in 3.0, but it's available in 3.2 > Are sieve actions logged anywhere, e.g. to aid with debugging? Generally? I don't know. Maybe if you increase your syslog log level to "debug" and add "debug: yes" to yo

Re: Sieve admin account doesn't work anymore

Hello, > You're trying to use "proxy authentication". That only works with some > SASL mechanisms, not all of them. Yes, I know, we use "PLAIN" which does support that. > Perhaps try the same with imtest and > observe what mechanism is used? imtest is much more verbose than sieveshell. > Tha

Re: Sieve admin account doesn't work anymore

Am 17.02.20 um 09:16 Uhr schrieb Rainer Ruprechtsberger: > I hope I got the list to post this question to right, please excuse me > if I didn't.. > > I resently upgraded a cyrus-imap from version 2.4 to 3.0 and since then > my sieve admin account is not an admin anymore: > > sieveshell -u admin

Re: Sieve runtime error claiming mailbox doesn't exist

On 12/13/19 5:48 PM, Michael Menge wrote which cyrus version did you use with CentOS7? I can't be certain since the jump to CentOS 8 killed off my CentOS 7 install, but the latest packages listed for CentoOS 7 is cyrus-imapd-2.4.17-15.el7.x86_64.rpm Can you post the sieve script. I don't kn

Re: Sieve runtime error claiming mailbox doesn't exist

Hi Patrick Quoting Patrick Boutilier : At first glance it looks like you need to change your sieve rules to use . as the mailbox separator. Something like: user.jim.System Messages I don't think the hierarchy separator is the problem. Some log outputs use the internal format e.g. "delive

Re: Sieve runtime error claiming mailbox doesn't exist

At first glance it looks like you need to change your sieve rules to use . as the mailbox separator. Something like: user.jim.System Messages On December 13, 2019 11:08:54 AM AST, Jim Sculley wrote: >Hello.  I'm a new member of this list but a long time user of >cyrus-imapd with postfix on my

Re: sieve filter based on utf-8 encoded text part of address

Hi Pete, I guess the 'address' test command matches only the actual address, not the description. In your example it would match "my@address". I suggest you check https://www.cyrusimap.org/imap/reference/admin/sieve.html and https://thsmi.github.io/sieve-reference/en/index.html. Regards, Anatoli

Re: sieve filters being ignored

Quoting hwilmer : Never mind, I forgot to activate the filter, sorry. BTW, is there a way to have the destination folders automatically created with 'fileinto'? there was a patch older versions that was included into the official build in version 2.5.0. https://github.com/cyrusimap/cyr

Re: sieve filters being ignored

Never mind, I forgot to activate the filter, sorry. BTW, is there a way to have the destination folders automatically created with 'fileinto'? On 3/8/19 1:46 PM, hwilmer wrote: Hi, with cyrus installed on Centos 7, my sieve filter is being ignored in that no incoming mail is being filter

Re: Sieve not working

On Friday 15 February 2019, J Pilfold-Bagwell wrote: >    sieve        cmd="timsieved" listen="0.0.0.0:2000" prefork=0 >    sievecmd="timsieved" listen="0.0.0.0:4190" prefork=0 I think what you should to change it to sieve1cmd="timsieved" listen="0.0.0.0:2000" prefork=0 s

Re: Sieve script not working

On 3/1/19 3:18 PM, Willem Offermans wrote: Dear Andrea and Cyrus friends, That is exactly the point: it was not ``stupid`` in any way. It was ignorance, which we can only avoid by improving the documentation. I blame myself for this; I'll be glad if the documentation was improved, obviously.

Re: Sieve script not working

Dear Andrea and Cyrus friends, That is exactly the point: it was not ``stupid`` in any way. It was ignorance, which we can only avoid by improving the documentation. By the way, the debug/logging question is still not answered. Debugging/logging might also enlighten the user/administrator. Wi

Re: Sieve script not working

On 3/1/19 12:31 PM, Michael Menge wrote: is the script activated? Uh, no! a user can have multiple scripts stored on the server but only one can be activated at the same time. On the filesystem there should be a "defaultbc"  which is a soft link to the active bc file. There was no such

Re: Sieve script not working

Hi Quoting Willem Offermans : Dear Michael and Cyrus friends, Where is this documented? I cannot find anything about this in https://www.cyrusimap.org/imap/reference/admin/sieve.html The example shown in section "Testing the

Re: Sieve script not working

Dear Michael and Cyrus friends, Where is this documented? I cannot find anything about this in https://www.cyrusimap.org/imap/reference/admin/sieve.html How should a user/administrator know? Pay attention to https://www.cyrusimap.or

Re: Sieve script not working

Hi Quoting Andrea Venturoli : On 3/1/19 12:04 PM, Willem Offermans wrote: (big snip on the rest) $ man timsieved TIMSIEVED(8)  TIMSIEVED(8) Just to make sure I've clarified this: the script *is* there. ls /var/imap/sieve/u/user1 user1

Re: Sieve script not working

On 3/1/19 12:04 PM, Willem Offermans wrote: > (big snip on the rest) $ man timsieved TIMSIEVED(8)  TIMSIEVED(8) Just to make sure I've clarified this: the script *is* there. ls /var/imap/sieve/u/user1 user1.sieve.bc user1.sieve.script

Re: Sieve script not working

Dear Andrea and Cyrus friends, I remember from a long time ago, that documentation with respect to sieve was sparse. It took me quite some time to set things up and to handle sieve back then. But even now I wouldn’t know how to debug the sieve process. Most of the things in the background of th

Re: Sieve script not working

On 3/1/19 11:01 AM, Merlin Hartley wrote: Is this a shared mailbox? No. Have you actually compiled the script or just put the plain text there? Did you install the file by hand or use something like timsieved? I install the scripts via sieveshell. You haven’t really given us much to

Re: Sieve script not working

Is this a shared mailbox? Have you actually compiled the script or just put the plain text there? Did you install the file by hand or use something like timsieved? You haven’t really given us much to go on… Merlin -- Merlin Hartley Computer Officer MRC Mitochondrial Biology Unit University of

Re: Sieve script not working

On 2/6/19 6:43 PM, Bron Gondwana wrote: Yeah, it's just called test.c in the sieve directory. Here's our buildscript code: ... I'm giving up on this: I cannot get to build this test binary; besides, I'm *sure* the script is correct, since it works for other 2 mailboxes. Thanks for your hel

Re: Sieve not working

Dear jpilfold-bagwell and Cyrus friends, Now you are sure that sieve is actually listening on the mentioned ports. How about the main question? Are the scripts applied to the incoming mail? Wiel Offermans wil...@offermans.rompen.nl > O

Re: Sieve not working

Hi Willem, Once I found that you can run sieve on ports 200 and 4190 at the same time, I set it up just in case Cyrus was talking to only one of the ports. If I telnet in, I get this response. [root@mail rules]# telnet localhost 2000 Trying ::1... telnet: connect to address ::1: Connection re

Re: Sieve not working

Dear Egoitz and Cyrus friends, Check if sieve is actually listening at port 2000 as well. Wiel Offermans wil...@offermans.rompen.nl > On 18 Feb 2019, at 09:34, ego...@sarenet.es wrote: > > Hi! > > > > Could you try enabling local6.debug channel in syslog, so that you could see > additio

Re: Sieve not working

Hi! Could you try enabling local6.debug channel in syslog, so that you could see additional Sieve debugging information?. Can you then post that log? Cheers! El 2019-02-15 12:32, J Pilfold-Bagwell escribió: > Hi All, > > I have a Centos 7 box running with the latest default cyrus install fro

Re: Sieve script not working

On Tue, Feb 5, 2019, at 06:20, Andrea Venturoli wrote: > On 2/2/19 8:25 PM, Bron Gondwana wrote: > > What is being written to syslog by your lmtpd? > > Absolutely nothing (apart from transient errors on the rare occasions > when I reboot the server and sendmail comes up before imapd). > > Is thi

Re: Sieve script not working

On 2/2/19 8:25 PM, Bron Gondwana wrote: What is being written to syslog by your lmtpd? Absolutely nothing (apart from transient errors on the rare occasions when I reboot the server and sendmail comes up before imapd). Is this log to be enabled somehow? There's also a sieve-test binary t

Re: Sieve script not working

What is being written to syslog by your lmtpd? Sieve failures should be logged to syslog. There's also a sieve-test binary that you can build in the Cyrus source code. I don't think it's built by default on most platforms though, we build it specially at FM. It takes a script and a raw email an

Re: Sieve script not working

On 1/20/19 3:21 PM, Andrea Venturoli wrote: On 1/20/19 12:13 AM, Nic Bernstein wrote: Andrea, It would help to know which version of Cyrus you're having difficulty with, and what setting you're using for 'unixhierarchysep'? Sorry, I obviously should have said it from the start: I'm using vers

Re: Sieve script not working

On 1/20/19 12:13 AM, Nic Bernstein wrote: Andrea, It would help to know which version of Cyrus you're having difficulty with, and what setting you're using for 'unixhierarchysep'? Sorry, I obviously should have said it from the start: I'm using version 2.5.12 on FreeBSD 11.2/amd64. I'm not u

Re: Sieve script not working

Andrea, It would help to know which version of Cyrus you're having difficulty with, and what setting you're using for 'unixhierarchysep'?  If you've recently upgraded to 3.X, for example, have you followed the instructions and converted your sieve scripts? Cheers,     -nic On 1/19/19 5:14 AM

Re: sieve runtime error

> Thanks, this got me looking into sendmail a little closer. I've never used > the program and didn't realize a dummy sendmail binary was installed on my > system. Actually installed sendmail and it works now, messages are being > filtered. You don't have to install sendmail, also postfix has a co

Re: sieve runtime error

Thanks, this got me looking into sendmail a little closer. I've never used the program and didn't realize a dummy sendmail binary was installed on my system. Actually installed sendmail and it works now, messages are being filtered. On Tue, Dec 18, 2018 at 4:32 AM Simon Matter wrote: > > I'm try

Re: sieve runtime error

> I'm trying to setup sieve and getting the following error in my logs: > > Dec 17 10:36:07 bllmail01 cyrus/lmtp[14530]: sieve runtime error for > jschaef...@harmonywave.net id > : > Reject: Sendmail process terminated normally, exit status 255 > > > I'm following the documentation here: > https://

Re: Sieve scripts execution for connected folders

Yes, my version is 2.5.11-10.11.el7.kolab_16, and seems there is this bug, so shared folder sieves not working there https://github.com/cyrusimap/cyrus-imapd/issues/1453 - kvaps On Tue, Oct 9, 2018 at 9:13 PM kvaps wrote: > > Sorry for confuse. I was little confused myself :) > > Yes, my user an

Re: Sieve scripts execution for connected folders

Sorry for confuse. I was little confused myself :) Yes, my user and few other users subscribed to this shared folder. Each user have own seen status for this folder - this is ok. But folder is big and have new mails quite often. Each user should react different mails in this mailbox. For now I re

Re: Sieve scripts execution for connected folders

Your use of the phrase "connected to all users" and, earlier, "connected and subscribed", is confusing.  Am I correct to assume you mean the folder is "subscribed" by all users?  There is no such thing asa mailbox/folder being "connected" as a state.  It may be subscribed or not, it may be conn

Re: Sieve scripts execution for connected folders

Hi, thanks for quick answer, Yes, I know about shared folder sieves, but I have aniother case: Eg I have some users: user/us...@example.org user/us...@example.org user/us...@example.org and shared folder shared/t...@example.org This folder connected to all users and have no shared see

Re: Sieve scripts execution for connected folders

Kvaps, It is unclear from your message just where this "shared folder" is rooted and where your sieve scripts are.  Do you mean a folder which is outside of the "user" name space?  If so, you cannot manage message delivery to this folder via user sieve scripts, but must use global sieve script

Re: Sieve stopped working after updating cyrus-imapd to 3.0.5

Hello, just for information, the update to version 3.0.6 did not fix the problem for me, I'm still having the same issue. I had to apply my workaround (create symbolic links) to make it work again. Regards, Ralf Am 02.03.2018 um 20:11 schrieb rfk: Hi Ken, my distribution is Gentoo and my

Re: SIEVE not workin in 3.0.5

Am Donnerstag, 22. März 2018, 13:19:37 CET schrieb Ken Murchison: > This was fixed with > https://github.com/cyrusimap/cyrus-imapd/commit/73af8e19546f235f6286cc9147a > 3ea74bde19ebb#diff-020bdafc26d65dd6a68af1d78b11a456 > > This fix will be in 3.0.6. Thanks! So i will bump the repo maintainer the

Re: SIEVE not workin in 3.0.5

Am Donnerstag, 22. März 2018, 12:54:00 CET schrieben Sie: > The same issue was discussed in this thread: > > > Seems very similiar, even if he comes from a upgrades cyrus system while i did a new / fresh one. > There was

Re: SIEVE not workin in 3.0.5

This was fixed with https://github.com/cyrusimap/cyrus-imapd/commit/73af8e19546f235f6286cc9147a3ea74bde19ebb#diff-020bdafc26d65dd6a68af1d78b11a456 This fix will be in 3.0.6. On 03/22/2018 07:47 AM, Niels Dettenbach via Info-cyrus wrote: Dear all, on a fresh installed cyrus 3.0.5 under Linux

Re: SIEVE not workin in 3.0.5

The same issue was discussed in this thread: There was no resolution, AFAICT. I'd suggest opening an issue on GitHub: --On 22. März 2018 um 12:47:48 +0100 Niels Dettenba

Re: Sieve stopped working after updating cyrus-imapd to 3.0.5

Hi Ken, my distribution is Gentoo and my previous cyrus version was 2.5.10. Then I upgraded to 3.0.4 but this ebuild (though marked stable by the Gentoo devs) was terminating "abnormally" all the time. Finally I upgraded to 3.0.5 which is running fine until now - well, except for sieve. Rega

Re: Sieve stopped working after updating cyrus-imapd to 3.0.5

Hi Sebastian, in my second post you can see my cyrus.conf: https://lists.andrew.cmu.edu/pipermail/info-cyrus/2018-February/039985.html No "-C" flags in use though. Regards, Ralf Am 02.03.2018 um 09:21 schrieb Sebastian Hagedorn: Hi Ralf, thanks a lot for your feedback, seems like we're com

Re: Sieve stopped working after updating cyrus-imapd to 3.0.5

I've done some investigating this morning and it appears that you are correct in that lmtpd and timsieved differ in how they handle the hierarchy separator.  But I'm not sure just yet when this split happened. Did you upgrade from 3.0.4 or from 2.x? On 03/01/2018 03:36 PM, rfk wrote: Hey Seb

Re: Sieve stopped working after updating cyrus-imapd to 3.0.5

Hi Ralf, thanks a lot for your feedback, seems like we're coming closer. Although I'm not sure what port 24 is supposed to be in your swaks command I just sent myself an e-mail while strace was attached to cyrusmaster. The log revealed the following: readlink("/var/imap/sieve/u/user^domain^de/d

Re: Sieve stopped working after updating cyrus-imapd to 3.0.5

Hey Sebastian, thanks a lot for your feedback, seems like we're coming closer. Although I'm not sure what port 24 is supposed to be in your swaks command I just sent myself an e-mail while strace was attached to cyrusmaster. The log revealed the following: readlink("/var/imap/sieve/u/user^dom

Re: Sieve stopped working after updating cyrus-imapd to 3.0.5

Not really. My best suggestion would be to strace the lmtp process to see if the sieve scripts are even found and opened. On a test system I did it like this: strace -f -ff -o /tmp/lmtptrace -p It might be better to prefork an lmtpd and to specifically strace that pid, but in my case it didn

Re: Sieve stopped working after updating cyrus-imapd to 3.0.5

Hello, still no other ideas? Ralf Am 15.02.2018 um 19:37 schrieb rfk: Hi, I'm so sorry, don't know how this could happen, but the last line of my configuration was lost during copy and paste: altnamespace: 0 So it is already disabled. Ralf Am 15.02.2018 um 19:32 schrieb Michael Menge

Re: sieve and utf-8 MIME/base64 content

On Mon, Feb 19, 2018, at 14:33, Eugene M. Zheganin wrote: > But my users kind of demand more and more :), now they want not only the > header/body search, but also sorting out the letters to the folders that > contain the localized symbols. So, it's working fine when a folder is > named 'Junk e-

Re: sieve and utf-8 MIME/base64 content

Hi, On 16.02.2018 15:37, Robert Stepanek wrote: Thanks for making this more clear to me :) On Fri, Feb 16, 2018, at 11:07, Vladislav Kurz wrote: The problem is that headers with non-ascii chars are encoded in form like this: Subject: =?UTF-8?B?UmU6I.gVG9v?= And also the body is sometimes c

Re: sieve and utf-8 MIME/base64 content

Thanks for making this more clear to me :) On Fri, Feb 16, 2018, at 11:07, Vladislav Kurz wrote: > The problem is that headers with non-ascii chars are encoded in form > like this: > Subject: =?UTF-8?B?UmU6I.gVG9v?= > And also the body is sometimes completely in base64, even though it is > jus

Re: sieve and utf-8 MIME/base64 content

On 02/16/18 10:25, Robert Stepanek wrote: > On Fri, Feb 16, 2018, at 10:17, Eugene M. Zheganin wrote: > >> I'm using sieve with cyrus to sort incoming mail, and it works perfectly >> with latin symbols. But what if I need to sort out the mail that has all >> sorts utf-8 sumbols in it ? Like MIME

Re: sieve and utf-8 MIME/base64 content

On Fri, Feb 16, 2018, at 10:17, Eugene M. Zheganin wrote: > I'm using sieve with cyrus to sort incoming mail, and it works perfectly > with latin symbols. But what if I need to sort out the mail that has all > sorts utf-8 sumbols in it ? Like MIME-encoded headers and base64 > -encoded body ? T

Re: Sieve stopped working after updating cyrus-imapd to 3.0.5

Hi, I'm so sorry, don't know how this could happen, but the last line of my configuration was lost during copy and paste: altnamespace: 0 So it is already disabled. Ralf Am 15.02.2018 um 19:32 schrieb Michael Menge: Hi, Quoting rfk : Hi, thanks for your feedback. Unfortunately sieve

Re: Sieve stopped working after updating cyrus-imapd to 3.0.5

Hi, Quoting rfk : Hi, thanks for your feedback. Unfortunately sievec reports nothing: # grep -v ^# roundcube.script require ["imapflags","fileinto"]; if anyof (header :contains "Subject" "test") { setflag "\\Seen"; fileinto "INBOX/Trash"; stop; } # sievec roundcube.

Re: Sieve stopped working after updating cyrus-imapd to 3.0.5

Hi, thanks for your feedback. Unfortunately sievec reports nothing: # grep -v ^# roundcube.script require ["imapflags","fileinto"]; if anyof (header :contains "Subject" "test") { setflag "\\Seen"; fileinto "INBOX/Trash"; stop; } # sievec roundcube.script test # Here's

Re: Sieve stopped working after updating cyrus-imapd to 3.0.5

Hi, Does the "sievec" compiler report any errors if you try to compile your sieve scripts by hand? Its manpage is here: https://www.cyrusimap.org/imap/reference/manpages/systemcommands/sievec.html Cheers, ellie On Thu, Feb 15, 2018, at 5:28 AM, rfk wrote: > Hello, > > recently I updated my

Re: sieve ports: 2000 and 4190

On Friday 01 September 2017, Anton Shilov wrote: > sieve2000 cmd="timsieved" listen="2000" proto=tcp4 prefork=0 > sieve4190 cmd="timsieved" listen="4190" proto=tcp4 prefork=0 Thanks, it works. -- Regards, Sergey Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.a

Re: sieve ports: 2000 and 4190

Hi Sergey, I think - yes. You can use something like this: cyrus.conf  SERVICES { ... sieve2000 cmd="timsieved" listen="2000" proto=tcp4 prefork=0 sieve4190 cmd="timsieved" listen="4190" proto=tcp4 prefork=0 ... } === or use tcp-balanser soft which listening to cli

Re: Sieve impersonate

On 07/28/17 11:27 +0200, Gabriele Bulfon wrote: Hi, is there any valid way to impersonate using authorization on timsieved? I tried with: AUTHENTICATE "PLAIN" "x" creating the auth string with a perl script as: encode_base64($authid."\x00".$username."\x00".$password."") being : authid

Re: Sieve RFC5490 checks user quota usage

Il 21 marzo 2017 alle 19.19 Nic Bernstein ha scritto:Paolo,Attached is the script we've been using for ages for this purpose. Ouruses LDAP as a source of user ID information, but it could be easilyadapted for other AAA databases.Thank you Nic. That's a good alternative.My request about doing it wi

Re: Sieve RFC5490 checks user quota usage

Paolo, Attached is the script we've been using for ages for this purpose. Our uses LDAP as a source of user ID information, but it could be easily adapted for other AAA databases. Cheers, -nic On 03/21/2017 10:59 AM, Paolo Cravero wrote: And for Nic, yes, I mean the "IMAP STORAGE quota"

Re: Sieve RFC5490 checks user quota usage

Hi, Quoting Paolo Cravero : And for Nic, yes, I mean the "IMAP STORAGE quota". I would like to warn the user that his quota is about to fill up through an email, triggered on new mail arrival or login. Why? Because not all clients support reading the quota over IMAP or handling an alert (think

Re: Sieve RFC5490 checks user quota usage

There is no mailbox annotation that exposes quota that could be used with the mboxmetadata extension (RFC5490) and there is no current Sieve extension for checking quota.Thank you Ken. Given the double negative answer I guess that developing such a feature would require a lot of work, or it is not

Re: Sieve RFC5490 checks user quota usage

You could do it with your MTA instead - you could write a filter/router/acl in exim for example - these can use arbitrary command output to decide on what to do with a message. M -- Merlin Hartley Computer Officer MRC Mitochondrial Biology Unit Cambridge, CB2 0XY United Kingdom > On 21 Mar 20

Re: Sieve RFC5490 checks user quota usage

There is no mailbox annotation that exposes quota that could be used with the mboxmetadata extension (RFC5490) and there is no current Sieve extension for checking quota. On 03/17/2017 11:01 AM, Paolo Cravero wrote: Hello. I am trying to figure out if sieve, with RFC5490 support, is able to

Re: Sieve RFC5490 checks user quota usage

Paolo, Please clarify; when you say "disk quota," do you mean a filesystem level quota, or do you really mean IMAP STORAGE quota, as administered through Cyrus? -nic On 03/17/2017 10:01 AM, Paolo Cravero wrote: Hello. I am trying to figure out if sieve, with RFC5490 support, is able to r

Re: Sieve login issue. Please help.

On 22.09.2016 11:38, Michael Menge via Info-cyrus wrote: Hi, Quoting Müfit Eribol via Info-cyrus : Hello, I am a happy user of cyrus-imapd for years without any major problem for small user base. Currently, I am having login problem for sieve. I have been trying to find the problem fo

Re: Sieve login issue. Please help.

Hi, Quoting Müfit Eribol via Info-cyrus : Hello, I am a happy user of cyrus-imapd for years without any major problem for small user base. Currently, I am having login problem for sieve. I have been trying to find the problem for days. Please find below information about my configura

Re: sieve runtime error Fileinto: Permission denied

On 24/05/16 12:59, Edda via Info-cyrus wrote: Interesting ;-) Looks like fileinto wants to deliver to an existent (existent for the user) but different folder as you expect, not the ones you listed below. What's your sieve script? And what sees the user in the IMAP LIST command? I can repro

Re: sieve runtime error Fileinto: Permission denied

Interesting ;-) Looks like fileinto wants to deliver to an existent (existent for the user) but different folder as you expect, not the ones you listed below. What's your sieve script? And what sees the user in the IMAP LIST command? I can reproduce this issue with a test user (mailtest) and a

Re: sieve runtime error Fileinto: Permission denied

I wonder if this is an 'altnamespace' issue - are you specifying INBOX/folder? -- Merlin Hartley > On 23 May 2016, at 12:52, Sunny via Info-cyrus > wrote: > > Hi, > > I'm seeing the following error logs with some users sieve filtering > May 23 11:41:31 imap02 lmtpunix[26005]: sieve runtime e

Re: sieve runtime error Fileinto: Permission denied

On Tue, May 24, 2016, at 20:16, Patrick Boutilier via Info-cyrus wrote: > On 05/24/2016 01:56 AM, OBATA Akio via Info-cyrus wrote: > > On Tue, 24 May 2016 12:32:07 +0900, Bron Gondwana via Info-cyrus > > wrote: > > > >> On Tue, May 24, 2016, at 10:44, OBATA Akio via Info-cyrus wrote: > >>> On Tue,

Re: sieve runtime error Fileinto: Permission denied

On 05/24/2016 01:56 AM, OBATA Akio via Info-cyrus wrote: On Tue, 24 May 2016 12:32:07 +0900, Bron Gondwana via Info-cyrus wrote: On Tue, May 24, 2016, at 10:44, OBATA Akio via Info-cyrus wrote: On Tue, 24 May 2016 07:25:42 +0900, Bron Gondwana via Info-cyrus wrote: > On Mon, May 23, 2016, a

Re: sieve runtime error Fileinto: Permission denied

On Tue, 24 May 2016 12:32:07 +0900, Bron Gondwana via Info-cyrus wrote: On Tue, May 24, 2016, at 10:44, OBATA Akio via Info-cyrus wrote: On Tue, 24 May 2016 07:25:42 +0900, Bron Gondwana via Info-cyrus wrote: > On Mon, May 23, 2016, at 22:47, Sundeep Singh Nanuwa via Info-cyrus wrote: >> O

Re: sieve runtime error Fileinto: Permission denied

On Tue, May 24, 2016, at 10:44, OBATA Akio via Info-cyrus wrote: > On Tue, 24 May 2016 07:25:42 +0900, Bron Gondwana via Info-cyrus > wrote: > > > On Mon, May 23, 2016, at 22:47, Sundeep Singh Nanuwa via Info-cyrus wrote: > >> On 23/05/16 13:35, Bron Gondwana via Info-cyrus wrote: > >> > You nee

Re: sieve runtime error Fileinto: Permission denied

On Tue, 24 May 2016 07:25:42 +0900, Bron Gondwana via Info-cyrus wrote: On Mon, May 23, 2016, at 22:47, Sundeep Singh Nanuwa via Info-cyrus wrote: On 23/05/16 13:35, Bron Gondwana via Info-cyrus wrote: > You need to have "anyone p" acl to fileinto anything other than inbox. That didn't work u

Re: sieve runtime error Fileinto: Permission denied

On Mon, May 23, 2016, at 22:47, Sundeep Singh Nanuwa via Info-cyrus wrote: > On 23/05/16 13:35, Bron Gondwana via Info-cyrus wrote: > > You need to have "anyone p" acl to fileinto anything other than inbox. > That didn't work unfortunately. Deliver into INBOX works, fileinto doesn't. It's ACLs fo

Re: sieve runtime error Fileinto: Permission denied

On 23/05/16 14:09, Jack Snodgrass via Info-cyrus wrote: file permissions like right.. acl permissions look right... are you running with selinux set to something other than disabled? Just a guess... but everything else looks ok. It's disabled SELINUX=disabled Thanks Cyrus Home Page: ht

Re: sieve runtime error Fileinto: Permission denied

file permissions like right.. acl permissions look right... are you running with selinux set to something other than disabled? Just a guess... but everything else looks ok. jack On 05/23/2016 07:47 AM, Sundeep Singh Nanuwa via Info-cyrus wrote: On 23/05/16 13:35, Bron Gondwana via Info-cy

Re: sieve runtime error Fileinto: Permission denied

On 23/05/16 13:35, Bron Gondwana via Info-cyrus wrote: You need to have "anyone p" acl to fileinto anything other than inbox. That didn't work unfortunately. Thanks Cyrus Home Page: http://www.cyrusimap.org/ List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/ To Unsub

Re: sieve runtime error Fileinto: Permission denied

You need to have "anyone p" acl to fileinto anything other than inbox. Bron. On Mon, May 23, 2016, at 21:52, Sunny via Info-cyrus wrote: > Hi, > > I'm seeing the following error logs with some users sieve filtering > May 23 11:41:31 imap02 lmtpunix[26005]: sieve runtime error for test2 id

Re: Sieve for shared mailboxes

Thanks Nic that looks useful Unfortunately ‘info' doesn’t seem to function on our installation: localhost> lm shared/mbujobs shared/mbujobs (\HasChildren) localhost> lam shared/mbujobs jt lrswipkxtecda merlin lrs anonymous p ij lrswipkxtecda localhost> info shared/mbujobs localhost> localhost>

Re: Sieve for shared mailboxes

On 03/18/2016 05:48 AM, Merlin Hartley via Info-cyrus wrote: ... Of course, over-time more complexity is always required and I have recently implemented a few shared mailboxes (rather than just sharing user mailboxes). Inevitably, the users are now asking for an auto-reply to be configured for

Re: Sieve for shared mailboxes

We don't use shared mailboxes or non-user sieve at all at FastMail, so it gets less testing than most things. I'd love to have contributions of good test cases to Cassandane from someone who knows exactly how this should work so we can make sieve good for the shared case too. It's somewhat tricky

Re: Sieve for shared mailboxes

Sorry I wasn’t clear: we are using an alias with +plus addressing and lmtp to deliver into the shared mailbox I have the shared mailbox working just fine… it is only the sieve on shared mailboxes that is failing... aliases file: mbujobs: +shared/mbujobs exim router: imap_shared_accept: drive

Re: Sieve for shared mailboxes

I have had mixed luck with direct mailbox delivery(+ addressing) and when I say mixed I mean mostly bad. I wanted to try using it for direct delivery of copies of all sent messages. I found I needed special permissions on all the mailboxes and duplicate delivery detection would not work in that

Re: Sieve for shared mailboxes

Sieve is run as part of the mail delivery into the mailbox. That would either be deliver or the lmtp interface. If your users are dragging and dropping the messages into the shared mailboxes then I don't believe that you can have sieve run on the mbox to mbox transfer. On 03/18/2016 06:48 AM

Re: Sieve: vacation from: parameter with display-name

Am 08.03.16 um 14:19 schrieb Edda via Info-cyrus: [...] From: > To my understanding of RFC 5322 this is not a valid „mailbox“, because of the outer angle brackets around. sendmail rewrites it internally to the resulting valid but ugly form: From: " I looked at RFC 5322 a bit further. It st

Re: Sieve vacation script?

On Sat, 26 Dec 2015, Patrick Goetz via Info-cyrus wrote: I've been struggling with figuring out how to set up a sieve vacation reply script. The documentation on this is pretty sparse, and the stuff I do find doesn't work. For example, I have a script that kind of does that. We needed in ou

Re: Sieve vacation script?

> On Dec 26, 2015, at 1:14 PM, Sebastian Hagedorn via Info-cyrus > wrote: > > Hi, > >> I've been struggling with figuring out how to set up a sieve vacation >> reply script. The documentation on this is pretty sparse, and the stuff >> I do find doesn't work. For example, >> >> [cyrus@www ~]

Re: Sieve vacation script?

Hi, I've been struggling with figuring out how to set up a sieve vacation reply script. The documentation on this is pretty sparse, and the stuff I do find doesn't work. For example, [cyrus@www ~]$ sieveshell --user=resea...@episcopalarchives.org --authname=cyrus localhost connecting to local

Re: Sieve, a problem with if/elsif/else

On Monday 31 August 2015, Eric Luyten wrote: > > else { fileinto "INBOX/BounceError"; } > > } > > Why "else fileinto" doesn't work ? Discovered in 2.4.17, > > reproduced in 2.4.18. > Did you define "INBOX/BounceError" as a mailbox ? > This is not implied by the fact that it is a hierarchy. > Som

Re: Sieve, a problem with if/elsif/else

On Mon, August 31, 2015 9:22 am, Sergey wrote: > Hello. > > > I have a strange problem. I use a filter > > > if address :contains ["To"] ["bounceerror@"] { ifaddress :contains > ["From"] ["MAILER-DAEMON@srv1.domain"] { > fileinto "INBOX/BounceError/srv1"; } > elsif address :contains ["From"] ["

Re: sieve and global/default scripts

On Fri, 6 Feb 2015, Eugene M. Zheganin wrote: Hi. On 06.02.2015 17:05, Niels Dettenbach wrote: The sieve script is (depending from where or what it should do) in a global place (or domain) - logged in as cyrus admin - - like imap/sieve/global or by SIEVE shell - within the cyrus system and the

Re: sieve and global/default scripts

Hi. On 06.02.2015 18:05, Niels Dettenbach wrote: > But btw: Depending of what your filter should do, may be it makes more sense > in your target scenario to do the filter / rule task on all incoming mail in > your mailer/MDA/MTA before cyrus - i.e. by your mailers SIEVE implementation > or othe

  1   2   3   4   5   6   7   8   9   10   >