How can I always send a vacation response with sieve?
I don't want dovecot to wait X days before sending out another vacation response. However, setting the :days to "0" doesn't work.
RFC https://www.rfc-editor.org/rfc/rfc5230.html#section-4.1 says:
4.1. Days Parameter
The ":days" argument is used to specify the period in which addresses
are kept and are not responded to, and is always specified in days.
The minimum value used for this parameter is normally 1. Sites MAY
define a different minimum value as long as the minimum is greater
than 0. Sites MAY also define a maximum days value, which MUST be
greater than 7, and SHOULD be greater than 30.
If ":days" is omitted, the default value is either 7 or the minimum
value (as defined above), whichever is greater.
If the parameter given to ":days" is less than the minimum value,
then the minimum value is used instead.
If ":days" exceeds the site-defined maximum, the site-defined maximum
is used instead.Sorry if this is more of a sieve question and is slightly off topic.
You do not want to do that because that can create loops.
-----Original Message----- I don't want dovecot to wait X days before sending out another vacation response. However, setting the :days to "0" doesn't work.
RFC https://www.rfc-editor.org/rfc/rfc5230.html#section-4.1 says:
4.1. Days Parameter
The ":days" argument is used to specify the period in whichaddresses are kept and are not responded to, and is always specified in days. The minimum value used for this parameter is normally 1. Sites MAY define a different minimum value as long as the minimum is greater than 0. Sites MAY also define a maximum days value, which MUST be greater than 7, and SHOULD be greater than 30.
If ":days" is omitted, the default value is either 7 or the minimum value (as defined above), whichever is greater. If the parameter given to ":days" is less than the minimum value, then the minimum value is used instead. If ":days" exceeds the site-defined maximum, the site-definedmaximum is used instead.
Sorry if this is more of a sieve question and is slightly off topic.
On 2021-09-04 05:50 PM, Marc wrote:
You do not want to do that because that can create loops.
Yeah, right after I posted this I did some more googling and someone else was saying the same thing.
I found another way around the problem I was trying to solve, though. So I'm good. Thanks for your response.
"Steve" == Steve Dondley s@dondley.com writes:
Steve> On 2021-09-04 05:50 PM, Marc wrote:
You do not want to do that because that can create loops.
Steve> Yeah, right after I posted this I did some more googling and someone Steve> else was saying the same thing.
Steve> I found another way around the problem I was trying to solve, Steve> though. So I'm good. Thanks for your response.
So share your solution! Just because you found a solution, doesn't mean others won't run into the same problem... *hint* *hint*
So share your solution! Just because you found a solution, doesn't mean others won't run into the same problem... *hint* *hint*
My solution had nothing to do with dovecot. The solution involved hacking the php code of an ancient cms so that your could reply directly to the person who filled out an email form.
"Steve" == Steve Dondley s@dondley.com writes:
So share your solution! Just because you found a solution, doesn't mean others won't run into the same problem... *hint* *hint*
Steve> My solution had nothing to do with dovecot. The solution Steve> involved hacking the php code of an ancient cms so that your Steve> could reply directly to the person who filled out an email Steve> form.
Thanks for that info, since it clarified that the solution you found wasn't dovecot related, even though you posted on the mailing list.
https://imgs.xkcd.com/comics/wisdom_of_the_ancients.png
*grin*
Hey what do you use to to put the first name in the quoted portions of the emails? And what is that called so I can google it?
On Sep 7, 2021, at 5:27 PM, John Stoffel john@stoffel.org wrote:
"Steve" == Steve Dondley s@dondley.com writes:
So share your solution! Just because you found a solution, doesn't mean others won't run into the same problem... *hint* *hint*
Steve> My solution had nothing to do with dovecot. The solution Steve> involved hacking the php code of an ancient cms so that your Steve> could reply directly to the person who filled out an email Steve> form.
Thanks for that info, since it clarified that the solution you found wasn't dovecot related, even though you posted on the mailing list.
https://imgs.xkcd.com/comics/wisdom_of_the_ancients.png
*grin*
On 09-04-2021 4:28 pm, Steve Dondley wrote: I don't want dovecot to wait X days before sending out another vacation response. However, setting the :days to "0" doesn't work.
RFC https://www.rfc-editor.org/rfc/rfc5230.html#section-4.1 says:
4.1. Days Parameter
The ":days" argument is used to specify the period in which addresses are kept and are not responded to, and is always specified in days. The minimum value used for this parameter is normally 1. Sites MAY define a different minimum value as long as the minimum is greater than 0. Sites MAY also define a maximum days value, which MUST be greater than 7, and SHOULD be greater than 30.
If ":days" is omitted, the default value is either 7 or the minimum value (as defined above), whichever is greater.
If the parameter given to ":days" is less than the minimum value, then the minimum value is used instead.
If ":days" exceeds the site-defined maximum, the site-defined maximum is used instead.
Sorry if this is more of a sieve question and is slightly off topic.
If you are using pigeonhole then you can set it to "0" which will send a reply every email. What you are reading are the RFC's for what software developers "should" follow. But nothing makes them follow everything to the T. Pigeonhole allows using "0".
https://doc.dovecot.org/settings/pigeonhole-ext/vacation/
sieve_vacation_min_period:
"A minimum of 0 indicates that users are allowed to make the Sieve interpreter send a vacation response message for every incoming message"
participants (5)
-
dovecot＠ptld.com
-
John Stoffel
-
Marc
-
s＠dondley.com
-
Steve Dondley