[Dovecot] dovecot-1.2-sieve sending vacation replies regardless of recipient (patch)
I want a way to send VAR messages without having to specify up front all of the addresses for which such VARs should be sent.
I realize this goes against rfc 3834, but it seemed reasonable to add a tag to the vacation command to skip the [to, cc, bcc, ...] recipients check. The patch I made is attached. The new usage with this patch is:
vacation [":days" number] [":subject" string]
[":x_any_address"]
[":from" string] [":addresses" string-list]
[":mime"] [":handle" string]
What do you think of this patch? Is there a better way to accomplish the same thing without writing a patch? Is there a better way to write this patch to make it a cleaner feature or easier to maintain? Could this ever be part of the mainline?
Mark Washenberger Rackspace Hosting Software Developer, Email & Apps mark.washenberger@rackspace.com
On Thu, 2010-04-01 at 10:52 -0400, Mark Washenberger wrote:
I want a way to send VAR messages without having to specify up front all of the addresses for which such VARs should be sent.
Do you want vacation replies really for ALL To: addresses, or would (a list of) *@domain.org be enough? Or in other words: Do you want vacation replies only for user's own domains, or also for messages that are forwarded there (from gmail/whatever)?
"Timo Sirainen" tss@iki.fi said:
On Thu, 2010-04-01 at 10:52 -0400, Mark Washenberger wrote:
I want a way to send VAR messages without having to specify up front all of the addresses for which such VARs should be sent.
Do you want vacation replies really for ALL To: addresses, or would (a list of) *@domain.org be enough? Or in other words: Do you want vacation replies only for user's own domains, or also for messages that are forwarded there (from gmail/whatever)?
In my case, my users are accustomed to their VAR responding for arbitrary aliases. So I do want all, not just *@domain.com.
From my glance at the code, however, if it were modified to accept "*@domain.com" in the :addresses string-list, it appears that it would be a very simple step to modify it to accept "*".
participants (2)
-
Mark Washenberger
-
Timo Sirainen