cot@dovecot.org> wrote:
>
> On 3/10/19 12:35 PM, Monis Monther via dovecot wrote:
> > [...]
> >
> > This is actually what I have done now, but I want it to be more
> > robust, if this user quits, then I must have someone else in the group
> > with the rule.
&g
Yassine Chaouche via dovecot <
> dovecot@dovecot.org> wrote:
>
>>
>> On 3/10/19 9:07 AM, Yassine Chaouche via dovecot wrote:
>>
>> On 3/9/19 12:41 PM, Monis Monther via dovecot wrote:
>>
>> Hi,
>>
>> We have an alias group named x...@examp
er or
plugin that can achieve this? How do ticketing systems handle this?
Thanks
Monis
On Sun, Mar 10, 2019 at 11:13 AM Yassine Chaouche via dovecot <
dovecot@dovecot.org> wrote:
>
> On 3/10/19 9:07 AM, Yassine Chaouche via dovecot wrote:
>
> On 3/9/19 12:41 PM, Monis Monther vi
email.
This is similar to any ticketing system, It there a way to achieve this?
Thanks
Monis
On Sat, Mar 9, 2019 at 9:29 PM @lbutlr via dovecot
wrote:
> On 9 Mar 2019, at 06:43, Monis Monther via dovecot
> wrote:
> > Because its not actually a vacation, we are using it as an auto r
9, 2019 at 4:36 PM Odhiambo Washington
wrote:
>
>
> On Sat, 9 Mar 2019 at 14:41, Monis Monther via dovecot <
> dovecot@dovecot.org> wrote:
>
>> Hi,
>>
>> We have an alias group named x...@example.com, this alias group has 3
>> actual users a...@examp
Hi,
We have an alias group named x...@example.com, this alias group has 3 actual
users a...@example.com, b...@example.com and c...@example.com
We set vacation rule on the generic sieve rule, the problem is that 3
responses are sent to the original sender. (obviously because the rule is
being exec