Sam Varshavchik schrieb:
On Sun, 13 Aug 2000, Georg Lutz wrote:
Sam Varshavchik schrieb:
On Sun, 13 Aug 2000, Georg Lutz wrote:
Perhaps there are other solutions for this issue.
(Making a public maildir / shared folder is not a solution in this case)
Why not? It's a perfect solution.
Of course, it would be the best technical solution.
But if all users have this public folder then no user feels realy
responsible for this (he thinks the others read the email) or the email
is processed more than one time(he thinks the others did not read the
mail).
In this case ,its better if a person gets the email directly in his
inbox.
Then set up a mailing list to deliver mail to all concerned parties.
Hm. mailinglist?
Sorry, I believe we are talking about two different things.
Distributing all incoming mail to inf...@domain.de to all users is not
what I want.
inf...@domain.de is an address for general contact. Nobody uses this
address for sending mail.
If someone writes an email to inf...@domain.de the mail should be routed
to to an user currently working (... to an user loggend-in in
courier-imap)
So one mail to inf...@domain.de should result in only one mail to one
user.
If I distribute this email to all users (via mailinglist, public dir,
forwarding etc.) all users have this email and there will be trouble
about who has to proccess this email.
At the moment users have to set this manually over a Web-Interface(which
sets a forward to their email-address in .qmail-infos)
But human are forgetful.
It would be better if there is an intelligent routing.
3 messages in net.sourceforge.lists.courier-usersRe: [courier-users] Non-personalized ...
