Displaying 20 results from an estimated 50000 matches similar to: "Sieve counterpart of IMAP SPECIAL-USE"
2014 Dec 29
2
SPECIAL-USE again
On 2014-12-29 20:45, Stephan Bosch wrote:
> For creating a special use mailbox there is the CREATE-SPECIAL-USE
> capability (https://tools.ietf.org/html/rfc6154, Section 3). As you
> suggested, the special use attributes can also be changed using the
> METADATA capability (https://tools.ietf.org/html/rfc6154, Section 4).
> Unfortunately, both of these features are not yet supported
2014 Dec 29
0
SPECIAL-USE again
On 12/29/2014 9:24 PM, Peter Mogensen wrote:
> On 2014-12-29 20:45, Stephan Bosch wrote:
>> For creating a special use mailbox there is the CREATE-SPECIAL-USE
>> capability (https://tools.ietf.org/html/rfc6154, Section 3). As you
>> suggested, the special use attributes can also be changed using the
>> METADATA capability (https://tools.ietf.org/html/rfc6154, Section 4).
2014 Dec 29
2
SPECIAL-USE again
Hi,
Great to see Thunderbird support SPECIAL-USE now.
I would like to hear the list about the intended use of SPECIAL-USE.
I get the impression from several earlier mails here that the intention
is for the server to globally decide what the folder-name of a specific
SPECIAL-USE folder is for all users.
That's the way the documentation exemplifies it and what I get from
posts like this:
2015 Apr 08
0
Sieve, multiple addresses, and variables
On 4/7/2015 10:48 PM, Andrew Sullivan wrote:
> Hi,
>
> I have another sieve question, this time about setting variables.
>
> I join a lot of mailing lists at ietf.org. I thought it'd be handy to
> filter these all into a common folder and then into individual
> folders, without having to configure each mailing list independently.
>
> So wrote this (this is just a
2020 Apr 16
1
Bug maybe already resolved? Sieve rule does not accept special use folder names
Hmmm, confusing, clients should then display the mailbox name redirected
by the server.
If a user in a front end just sees the 'Junk E-mail', that is the name
he is going to be using in his mailbox rules. If he does not know that
this is actually the Junk folder on the server, he will make an
incorrect message rule.
So I guess you have to correct this server side, before storing
2008 Jul 28
2
Sieve Notify Error
Hello,
I'm using dovecot 1.1.1 and dovecot-sieve-1.1.5 .
I'm very interested in the notify plugin, I've tried many code which have generated some errors (coding errors that have been arrived in the .dovecot.sieve.err) but these errors are fixed.
But Notify is still not working, I've the following in mail.log :deliver(webmaster at xxx.net): SIEVE ERROR: Unknown [unimplemented]
2015 Apr 07
2
Sieve, multiple addresses, and variables
Hi,
I have another sieve question, this time about setting variables.
I join a lot of mailing lists at ietf.org. I thought it'd be handy to
filter these all into a common folder and then into individual
folders, without having to configure each mailing list independently.
So wrote this (this is just a part, obviously):
require ["envelope", "variables",
2020 Apr 16
2
Bug maybe already resolved? Sieve rule does not accept special use folder names
I do not have the log file anymore from the home dir. It just complains
that the folder Spam does not exist.
dovecot: lmtp(xxxx): oG8YI6enmF7FIAAAI7dPvA: sieve: Execution of script
/xxxx/.dovecot.sieve failed, but implicit keep was successful (user
logfile /xxx/.dovecot.sieve.log may reveal additional details)
-----Original Message-----
From: Stephan Bosch [mailto:stephan at rename-it.nl]
2018 Mar 24
0
recipient delimiter and sieve filters
Op 3/24/2018 om 9:16 AM schreef Andr? Rodier:
> Dear all,
>
> I have found a way to automatically copy sent emails in the "Sent"
> folder, but I am not sure it is the simplest and more reliable way on
> the long term.
>
> I am open to suggestions if I miss a feature in Dovecot - or Postfix,
> that allows me to do this. I vaguely remember an SMTP extension that do
2020 Apr 16
0
Bug maybe already resolved? Sieve rule does not accept special use folder names
On 16/04/2020 23:19, Marc Roos wrote:
> I do not have the log file anymore from the home dir. It just complains
> that the folder Spam does not exist.
>
> dovecot: lmtp(xxxx): oG8YI6enmF7FIAAAI7dPvA: sieve: Execution of script
> /xxxx/.dovecot.sieve failed, but implicit keep was successful (user
> logfile /xxx/.dovecot.sieve.log may reveal additional details)
So, does that
2020 Apr 16
0
Bug maybe already resolved? Sieve rule does not accept special use folder names
On 16/04/2020 23:38, Marc Roos wrote:
> It is a 'special use' folder, so it only appears to exist in mail
> clients.
>
> # spam folders merging
> mailbox Junk {
> special_use = \Junk
> auto = create
> }
> mailbox Spam {
> special_use = \Junk
> auto = no
> }
> mailbox "Junk E-mail" {
> special_use
2015 Feb 15
0
dovecot 2.2.15 script_after not executed
On 2/12/2015 2:12 AM, Florin Portase wrote:
>
> On 2015-02-12 01:01, Stephan Bosch wrote:
>
>> On 2/11/2015 10:37 PM, Portase Florin wrote:
>>> On 2/11/2015 8:41 PM, Stephan Bosch wrote:
>>>> On 2/11/2015 7:34 PM, Florin Portase wrote:
>>>>> Hello guys,
>>>>>
>>>>> I'm having troubles making
2007 Sep 26
2
Subaddress Extension in sieve plugin
Hello!
With many MTAs it is possible to use a special form of adressing: subaddresses or "plussed
addresses". For sendmail you can read some information on
http://www.sendmail.org/m4/misc_features.html
http://www.unix.org.ua/orelly/networking/sendmail/ch24_04.htm#SML2-CH-24-SECT-4-3
In a sieve filter you can analyse these special detail values, the syntax is described in
RFC3598
2020 Apr 16
2
Bug maybe already resolved? Sieve rule does not accept special use folder names
It is a 'special use' folder, so it only appears to exist in mail
clients.
# spam folders merging
mailbox Junk {
special_use = \Junk
auto = create
}
mailbox Spam {
special_use = \Junk
auto = no
}
mailbox "Junk E-mail" {
special_use = \Junk
auto = no
}
On 16/04/2020 23:19, Marc Roos wrote:
> I do not have the log file anymore from the
2020 Apr 16
2
Bug maybe already resolved? Sieve rule does not accept special use folder names
Sieve rule fileinto Spam fails, while fileinto Junk succeeds
mailbox Spam {
special_use = \Junk
auto = no
}
dovecot-pigeonhole-2.2.36-3.el7_7.1.x86_64
dovecot-2.2.36-3.el7_7.1.x86_64
CentOS Linux release 7.7.1908 (Core
2015 Feb 12
2
dovecot 2.2.15 script_after not executed
On 2015-02-12 01:01, Stephan Bosch wrote:
> On 2/11/2015 10:37 PM, Portase Florin wrote: On 2/11/2015 8:41 PM, Stephan Bosch wrote: On 2/11/2015 7:34 PM, Florin Portase wrote: Hello guys,
>
> I'm having troubles making "script_after" to exec sieve scripts::
>
> Keep in mind that the sieve_after script is only executed when the
> "keep" action [1 [1]]
2007 Mar 09
1
Dovecot's Sieve Support
Hi Folks,
I'm looking for details of Dovecot's Sieve support. Specifically,
Support for Sieve scripts (RFC 3028) and the protocol for remotely
managing Sieve scripts, including:
-- draft-martin-managesieve-06.txt
-- draft-ietf-sieve-imapflags-05.txt
And the following Sieve actions:
-- fileinto
-- redirect
-- imapflags
Thanks,
Robb Beal
-- www.laszlosystems.com --
2015 Feb 12
0
dovecot 2.2.15 script_after not executed
On 2/11/2015 10:37 PM, Portase Florin wrote:
> On 2/11/2015 8:41 PM, Stephan Bosch wrote:
>> On 2/11/2015 7:34 PM, Florin Portase wrote:
>>> Hello guys,
>>>
>>> I'm having troubles making "script_after" to exec sieve scripts::
>>>
>> Keep in mind that the sieve_after script is only executed when the
>> "keep" action
2019 Feb 28
0
Pigeonhome Sieve: check existence of a folder?
What about extension "mailbox"?
https://wiki.dovecot.org/Pigeonhole/Sieve
https://tools.ietf.org/html/rfc5490#section-3
A simple example (not tested, but should work):
note:?
+ I use '/' instead of '.' as hierarchical separator
+ stop; stops the whole script, but you could use elsif instead.
require ["fileinto", "mailbox"];
if header :contains
2015 Feb 11
2
dovecot 2.2.15 script_after not executed
On 2/11/2015 8:41 PM, Stephan Bosch wrote:
> On 2/11/2015 7:34 PM, Florin Portase wrote:
>> Hello guys,
>>
>> I'm having troubles making "script_after" to exec sieve scripts::
>>
> Keep in mind that the sieve_after script is only executed when the
> "keep" action [1] is executed or when the implicit "keep" [2] is still
>