[Tickets #7342] Re: Vacation -> Plesk driver should set ans_freq = 1

[bugs at horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/7342
------------------------------------------------------------------------------
  Ticket             | 7342
  Updated By         | jsaxe at briworks.com
  Summary            | Vacation -> Plesk driver should set ans_freq = 1
  Queue              | Vacation
  Version            | 3.0.1
  Type               | Enhancement
  State              | New
  Priority           | 1. Low
  Milestone          |
  Patch              | 1
  Owners             |
------------------------------------------------------------------------------


jsaxe at briworks.com (2008-09-15 16:12) wrote:

Good afternoon. I just made a tiny enhancement to the  
vacation/lib/Driver/plesk.php file to set an additional XML parameter  
available in Plesk. If "ans_freq" is not set, then it defaults in  
Plesk to a value of 10, which means that the first 10 times an  
external user sends in an email to an account, the autoresponder will  
shoot out a response. This is fine, until two users in the same  
company are both on vacation, and one of them sends email to the  
other; then each side gets 10 "dueling vacation messages" that look  
like "Re: Re: Re: original subject". I thought it was pretty funny,  
but some of our users don't have a sense of humor.

So here is my improved version, as a patch:


[root at lin-10-ve1 Driver]# diff plesk.php.original plesk.php
158c158
<             . '</text></autoresponder></autoresponders></mailname></filter>'
---
>             .  
> '</text><ans_freq>1</ans_freq></autoresponder></autoresponders></mailname></filter>'


Note that this field of part of the Plesk 8.3 XML API specification,  
which I got as a PDF from Parallels' site. Also note that their parser  
seems to be sensitive to the sequence in which these parameters are  
given; I tried adding <ans_freq> right after the <name> and <enabled>  
flags of the autoresponder, and it gave some XML HTTP error, but if I  
put it here, after the <text> parameter, it accepts it fine. (I  
followed the order in that section of the PDF.)

Also note that I do not know whether this field is available in older  
versions of Plesk, or whether attempting to supply it to an older  
version would succeed but silently ignore this parameter, or would  
completely fail. Sorry, don't have time or resources to test it. I  
just wanted to submit this so other people might get the benefit of  
our research.

Cheers!

-- Jeff Saxe, Network Engineer
Blue Ridge InternetWorks
Charlottesville, VA, US
434-817-0707 ext. 2024