Vacation Application

[Gottschalk, David]

No murder here.

Oldschool Cyrus setup. I want to upgrade it actually, but there are 30K + accounts on these 3 servers.

The only problem I see with having it try each server, but failing how do you know if it really isn't that server, or there is just a network issue.

David Gottschalk
UTS Email team
david.gottschalk at emory.edu


-----Original Message-----
From: Nic Bernstein [mailto:nic at onlight.com]
Sent: Tuesday, March 10, 2009 2:00 PM
To: Gottschalk, David
Cc: info-cyrus at lists.andrew.cmu.edu
Subject: Re: Vacation Application

On 03/10/2009 12:42 PM, Gottschalk, David wrote:
> Hi All,
>   I have a question regarding a vacation application for Cyrus servers. I want to know what others are using to meet this need. Currently, we have a home grown application that allows users to enable/disable vacation messages for their Cyrus accounts. This application is old and outdated, and needs to be replaced. I found the Horde vacation application which looks like it will meet my needs, but I have one issue. We currently have three Cyrus servers with all the accounts spread out across those three servers. The problem I am running into with any vacation application, is how to identify to the vacation application which server a user is on without the user needing to know this information. Is anyone else in a similar situation?
>
Um, use a murder?  Otherwise you may want to adapt something like the
cyrus user validation script which was recently posted here.  Your
application could then perform lookups in the output of that script.
Lastly, you could just let you application attempt authenticating
against each server, in turn, stopping once it succeeds.

Cheers,
    -nic

--
Nic Bernstein                             nic at onlight.com
Onlight llc.                              www.onlight.com
2266 North Prospect Avenue #610           v. 414.272.4477
Milwaukee, Wisconsin  53202-6306          f. 414.290.0335


This e-mail message (including any attachments) is for the sole use of
the intended recipient(s) and may contain confidential and privileged
information.  If the reader of this message is not the intended
recipient, you are hereby notified that any dissemination, distribution
or copying of this message (including any attachments) is strictly
prohibited.

If you have received this message in error, please contact
the sender by reply e-mail message and destroy all copies of the
original message (including attachments).