search for: imap_us

Displaying 3 results from an estimated 3 matches for "imap_us".

Did you mean: imap_s
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
2016 Dec 05
0
imapsieve environment variables missing?
...variable using the "imap.user" environment item will work once the "imapsieve" extension [4] is require'd. That is a bit cumbersome though, since you need 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] http...
2016 Dec 05
2
imapsieve environment variables missing?
...the "imap.user" environment item will work once the "imapsieve" > extension [4] is require'd. That is a bit cumbersome though, since you > need to put that in a variable with a statement like: if environment > :matches "imap.user" "*" { set "imap_user" "${1}"; }. I don't see that being too cumbersome, as it's the standard way the environment extension is used, and it's what I expect from reading the RFC. But I understand your point that it's more lengthy than just accessing the variable directly. So the only...