Displaying 8 results from an estimated 8 matches for "rfc5229".
Did you mean:
rfc5228
2008 Nov 20
1
Sieve RFC5229 support?
I'd like to take advantage of RFC5229 match variables (it would reduce
the number of rules I have by an order of magnitude); however, the
required extension isn't supported yet. Am I mistaken? If not, are
there plans to support it?
2009 Aug 13
1
sieve: variable extension?
Hello, Dovecot.
Does dovecot sieve supports variable extension (rfc5229)? It is very
useful for users with large amount of mailing lists, as it allows to
write only one rule for all lists (filtering by List-Id).
If it is not supported, is here any plans to support it? I can try
to implement it, but I don't want to duplicate work, if somebody has
this extension i...
2012 Aug 28
1
use sieve plugin with variable and folders
Hello ,
I'm trying to use the pigeonhole plugin but I'm experiencing configuration
problem... Hope you could help me!
Firstly :
my sieve filter test is the next one :
///////////////////
require ["fileinto" , "variables" , "mailbox"];
if address :matches "Delivered-To" "*@*.*" {
fileinto :create ".INBOX.iop" ; stop ;
}
2017 Feb 10
0
Safely piping to a shell script
Thanks for the previous answer on :execute. In thinking about
malicious input, I am worried about the possibility that mail will be
sent with a clever from line. (Section 7 of
http://www.ietf.org/rfc/rfc5229.txt is great, btw)
To address this, I'm considering the following, and would appreciate
feedback. I'm aware that this doesn't capture all emails, those with
non-alphanum are legit, and badly handled.
I think that this restricts the input of the grepfrom script to be
a single string,...
2014 Mar 17
1
Sieve escape user input
Hi,
i'm having problems with escaping user input in sieve scripts. I'm using 'variables' extension and i can't find out how to escape character '$' - i tried '\$' and '$$' but nothing helps. Any ideas? Thanks.
azur
2013 Nov 19
1
Quick question on sieve
I have a procmail recipe that does the majority of my heavy lifting for my mailing lists. It's pretty straightforward, but as I understand it, this isn't something sieve can do:
# [ ] contains a space and a tab
:0
* 9876543210^0 ^(List-Id:.*<|X-Mailing-List:[ ]*)\/[-A-z0-9_+]+
* 9876543210^0 ^(List-Post:[ ]*(<mailto:)?|List-Owner:[ ]*(<mailto:)?owner-)\/[-A-Z0-9_+]+
*
2016 Dec 05
0
imapsieve environment variables missing?
...d to put that in a variable with a statement like: if environment
:matches "imap.user" "*" { set "imap_user" "${1}"; }. The standard [1]
provides no alternative.
Relevant specifications:
[1] http://tools.ietf.org/html/rfc5183/
[2] http://tools.ietf.org/html/rfc5229/
[3]
https://raw.githubusercontent.com/dovecot/pigeonhole/master/doc/rfc/spec-bosch-sieve-dovecot-environment.txt
[4] https://tools.ietf.org/html/rfc6785
Regards,
Stephan.
2016 Dec 05
2
imapsieve environment variables missing?
On 2016-12-05 07:22, Stephan Bosch wrote:
> Op 5-12-2016 om 16:10 schreef MRob:
>> On 2016-12-05 06:13, Stephan Bosch wrote:
>>> Op 5-12-2016 om 14:32 schreef MRob:
>>>
>>> Could you show me your full script? I am mainly interested in the
>>> require statements involved.
>>
>> I don't know how I managed to compile only using direct