[Dovecot] Reset vacation lda-dupes database
Hello, I have dovecot 2.2.6 and pignenhole 0.4.2 running on freebsd9.1. We have a mix of unix users (/home/user) and postfixadmin users (/home/vmail/domain/user). I am using dovecot managesive with afterlogic webmail which has a managesieve plugin to set the out of office message. All works fine. I have sieve_vacation_default_period set to 1d.
The problem I'm trying to solve is that users set their vacation message and want to test it. So they have their colleagues send them multiple test messages and want to make sure it works. Of course only the first message gets an auto-reply. I tell them that the auto responder only sends one message per day per sender but they would like to test it with a new message etc. So I have to remove their .lda-dupes file manually so they can try again.
My previous autoresponder setup (squirrelmail) used a .forward technique and removed the vacation database when they turned the responder from off to on, and this worked well for the above issue.
Is there a solution for dovecot managesieve which will remove or reset the .lda-dupes file whenever a new sieve file is uploaded? Or another solution that will reset the "vacation timer" when the user turns vacation from off to on?
Thank you Mike
On 17.11.2013, at 0.21, Mike Selner @ Yahoo mselner@yahoo.com wrote:
Hello, I have dovecot 2.2.6 and pignenhole 0.4.2 running on freebsd9.1. We have a mix of unix users (/home/user) and postfixadmin users (/home/vmail/domain/user). I am using dovecot managesive with afterlogic webmail which has a managesieve plugin to set the out of office message. All works fine. I have sieve_vacation_default_period set to 1d.
The problem I'm trying to solve is that users set their vacation message and want to test it. So they have their colleagues send them multiple test messages and want to make sure it works. Of course only the first message gets an auto-reply. I tell them that the auto responder only sends one message per day per sender but they would like to test it with a new message etc. So I have to remove their .lda-dupes file manually so they can try again.
My previous autoresponder setup (squirrelmail) used a .forward technique and removed the vacation database when they turned the responder from off to on, and this worked well for the above issue.
Is there a solution for dovecot managesieve which will remove or reset the .lda-dupes file whenever a new sieve file is uploaded? Or another solution that will reset the "vacation timer" when the user turns vacation from off to on?
They can add a different :handle parameter to get a different response, but .. as I understand it, a different vacation reason message should also trigger a separate vacation notice, but looks like Pigeonhole doesn’t currently do that. Stephan?
On 11/19/2013 8:53 PM, Timo Sirainen wrote:
On 17.11.2013, at 0.21, Mike Selner @ Yahoo mselner@yahoo.com wrote:
They can add a different :handle parameter to get a different response, but .. as I understand it, a different vacation reason message should also trigger a separate vacation notice, but looks like Pigeonhole doesn’t currently do that. Stephan?
It should though. It implements the behavior recommended in the RFC (http://tools.ietf.org/html/rfc5230#section-4.2); i.e., generate a handle from the provided arguments (ignoring variables!) if none is provided explicitly. This is performed here:
http://hg.rename-it.nl/dovecot-2.2-pigeonhole/file/b7434a02fc51/src/lib-siev...
So did you test this unsuccessfully or did you have problems finding it in the sources? If it doesn't work it would obviously be a bug. The constructed handle value can be seen by dumping the Sieve script binary with sieve-dump.
Regards,
Stephan.
On 19.11.2013, at 22.36, Stephan Bosch stephan@rename-it.nl wrote:
On 11/19/2013 8:53 PM, Timo Sirainen wrote:
On 17.11.2013, at 0.21, Mike Selner @ Yahoo mselner@yahoo.com wrote:
They can add a different :handle parameter to get a different response, but .. as I understand it, a different vacation reason message should also trigger a separate vacation notice, but looks like Pigeonhole doesn’t currently do that. Stephan?
It should though. It implements the behavior recommended in the RFC (http://tools.ietf.org/html/rfc5230#section-4.2); i.e., generate a handle from the provided arguments (ignoring variables!) if none is provided explicitly. This is performed here:
http://hg.rename-it.nl/dovecot-2.2-pigeonhole/file/b7434a02fc51/src/lib-siev...
So did you test this unsuccessfully or did you have problems finding it in the sources? If it doesn't work it would obviously be a bug. The constructed handle value can be seen by dumping the Sieve script binary with sieve-dump.
Oh, I just didn’t look into the correct place in the code. I didn’t think that handle would be generated before ext_vacation_operation_execute(). So answer to Mike: Just have them change the reason string in some way.
On Tuesday, November 19, 2013 3:00 PM, Timo Sirainen tss@iki.fi wrote:
On 19.11.2013, at 22.36, Stephan Bosch stephan@rename-it.nl wrote:
On 11/19/2013 8:53 PM, Timo Sirainen wrote:
On 17.11.2013, at 0.21, Mike Selner @ Yahoo mselner@yahoo.com wrote:
They can add a different :handle parameter to get a different response, but .. as I understand it, a different vacation reason message should also trigger a separate vacation notice, but looks like Pigeonhole doesn’t currently do that. Stephan?
It should though. It implements the behavior recommended in the RFC (http://tools.ietf.org/html/rfc5230#section-4.2); i.e., generate a handle from the provided arguments (ignoring variables!) if none is provided explicitly. This is performed here:
http://hg.rename-it.nl/dovecot-2.2-pigeonhole/file/b7434a02fc51/src/lib-siev...
So did you test this unsuccessfully or did you have problems finding it in the sources? If it doesn't work it would obviously be a bug. The constructed handle value can be seen by dumping the Sieve script binary with sieve-dump.
Oh, I just didn’t look into the correct place in the code. I didn’t think that handle would be generated before ext_vacation_operation_execute(). So answer to Mike: Just have them change the reason string in some way.
Thank you! That did the trick. If they change the vacation message it will send an auto- response even if it had previously responded to the same person.
Mike
participants (3)
-
Mike Selner ＠ Yahoo
-
Stephan Bosch
-
Timo Sirainen