Let's look at this another way. Doing a single intake and manual
distribution is a major bottleneck. What if you instead gave read/write
permissions to your users to access #Users/info/INBOX via IMAP.

The helpdeskers would check the main shared mailbox for new messages and
reply to them from their own helpdesk accounts.

As for assigning messages, you could create a very simple addon to a
webmail program allowing the intake person to link a message UID to a
technician's name. A cron job runs to check that the message has been
flagged as \Replied within a specified deadline.

Everything stays in IMAP, and a small external database links up the
message UIDs to the job assignments.

Aaron

On Wed, 2006-09-20 at 09:26 +0530, Nataraj S Narayan wrote:
> Hi
> 
> I dont quite like this scheme, but thats what the boss wants.
> 
> My company wants to go for one single emailid for the outside world.
> Example  [EMAIL PROTECTED]
> 
> One person will download from the pop3 server and distribute after
> checking the content. I am using fetchmail as of now to download all the
> mails. Internally, we can have as many ids we want, but outgoing only
> with [EMAIL PROTECTED] That part I know postfix will take care.
> 
> So, Imap 'replied-flag' will help to find messages not replied. OK. But
> how does one mark a downloaded mail 'to-be-replied-by-internal-userid'?
> 
> I need to report only if that particular guy doesnt answer.
> 
> regards
> 
> Nataraj
> 
> Marc Dirix wrote:
> > You need some sort of ticket system?
> > I wouldn't use dbmail itself for this kind of sorting but some kind  of 
> > script.
> > 
> > What do you mean with downloading? from a pop-source? If you use  
> > fetchmail, the original
> > sender stays intact.
> > 
> > For checking if the message is replied within 2 days you can check  
> > everyday if the imap replied flag has been set, And compare it with  the 
> > message-date. You'd need to create a cron script for this.
> > 
> > /marc
> > 
> 
> 
> _______________________________________________
> Dbmail-dev mailing list
> [email protected]
> http://twister.fastxs.net/mailman/listinfo/dbmail-dev

Reply via email to