Re: Minimum days between sieve vacation responses

2011-11-05 Thread Ramprasad
On Fri, 2011-11-04 at 08:24 -0500, k...@rice.edu wrote:
 On Fri, Nov 04, 2011 at 07:59:07AM +0100, Bron Gondwana wrote:
  On Fri, Nov 04, 2011 at 12:22:54PM +0530, Ram wrote:
   Can I configure sieve to send vacation responses for every message .. 
   rather than waiting for n days before responding again to the same 
   sender
  
  Ouch - why?  There's a danger of mail loops, amongst other things.
  
  Bron.
 
 Double ouch, ouch! That is a really, really, REALLY bad idea. We actually
 made a work-around within the mail system to make this happen and sooner
 or later, in EVERY case, we had a massive mail loop or other type of self-
 inflicted DoS against our mail infrastructure. In most of them, the users
 themselves received so much mail that their mail clients were unable to
 handle the volume and mail administrators were needed to clean things
 enough for them to get back to work.
 


I understand that this may lead to mail loops

But our client requires that every mail to sa...@domain.comshould
immediately get a response ( Business requirements .. not technical ) 


Assuming that I have methods to avoid looping at the SMTP level .. how
can I do this in cyrus, sieve




Thanks
Ram






Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/


Re: Minimum days between sieve vacation responses

2011-11-05 Thread Bron Gondwana
On Sat, Nov 05, 2011 at 01:37:02PM +0530, Ramprasad wrote:
 But our client requires that every mail to sa...@domain.comshould
 immediately get a response ( Business requirements .. not technical ) 

Sieve is probably the wrong tool for the job.

 Assuming that I have methods to avoid looping at the SMTP level .. how
 can I do this in cyrus, sieve

I would recommend an email autoresponder designed for the job, see:

http://en.wikipedia.org/wiki/Autoresponder

In particular Today's autoresponders need to be careful to not
generate e-mail backscatter, which can result in the autoresponses
being considered E-mail spam.

I would probably hang something like request-tracker on the sales
address, causing every contact to not only get an immediate response,
but be trackable from there.

Bron.

Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/


Minimum days between sieve vacation responses

2011-11-04 Thread Ram
Can I configure sieve to send vacation responses for every message .. 
rather than waiting for n days before responding again to the same sender


Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/


Re: Minimum days between sieve vacation responses

2011-11-04 Thread Bron Gondwana
On Fri, Nov 04, 2011 at 12:22:54PM +0530, Ram wrote:
 Can I configure sieve to send vacation responses for every message .. 
 rather than waiting for n days before responding again to the same sender

Ouch - why?  There's a danger of mail loops, amongst other things.

Bron.

Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/


Re: Minimum days between sieve vacation responses

2011-11-04 Thread k...@rice.edu
On Fri, Nov 04, 2011 at 07:59:07AM +0100, Bron Gondwana wrote:
 On Fri, Nov 04, 2011 at 12:22:54PM +0530, Ram wrote:
  Can I configure sieve to send vacation responses for every message .. 
  rather than waiting for n days before responding again to the same sender
 
 Ouch - why?  There's a danger of mail loops, amongst other things.
 
 Bron.

Double ouch, ouch! That is a really, really, REALLY bad idea. We actually
made a work-around within the mail system to make this happen and sooner
or later, in EVERY case, we had a massive mail loop or other type of self-
inflicted DoS against our mail infrastructure. In most of them, the users
themselves received so much mail that their mail clients were unable to
handle the volume and mail administrators were needed to clean things
enough for them to get back to work.

The moral is, if you need this, the implementation is far from trivial
and you will need to implement internal controls and feedback loops to
prevent these types of problems. Unless you are legally required to
do this, figure out another way.

Cheers,
Ken

Cyrus Home Page: http://www.cyrusimap.org/
List Archives/Info: http://lists.andrew.cmu.edu/pipermail/info-cyrus/