[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [cobalt-developers] Limiting Qpopper to a single message at a time
- Subject: Re: [cobalt-developers] Limiting Qpopper to a single message at a time
- From: "Steve Werby" <steve-lists@xxxxxxxxxxxx>
- Date: Thu May 2 08:01:59 2002
- List-id: Discussion Forum for developers on Sun Cobalt Networks products <cobalt-developers.list.cobalt.com>
"Jeff Lasman" <jblists@xxxxxxxxxxxxx> wrote:
> Steve Werby wrote:
>
> > I don't think this is possible. And I can't envision why you'd want a
> > user's email to be divided up across several machines. Can you share
why
> > you want to do this?
>
> For example to distribute incoming sales or support email, for example.
> I used to distribute an email server for Windows which could do this via
> a built in mailing-list function setting.
Thanks, Jeff. That makes perfect sense. E. B. is probably right that
qpopper can be hacked pretty easily to do this. I know the original poster
didn't ask for other alternatives, but I'd like to share one. For something
like sales or support it's probably ideal to have all requests in a central
location for tracking, auditing and building up a database of customer info.
and history. If the emails are distributed this is rather difficult to do,
at least without a lot of manual work. I think this is best handled by a
CRM tool or by piping the email to a script that stores it in a DB, with a
web-based tool that gives each user access to the queue and allows flags to
be set - open, closed, active, etc. and with timestamps and notes for each
activity and a record of the support person involved. My 2 cents.
--
Steve Werby
President, Befriend Internet Services LLC
http://www.befriend.com/