Howabout using your MTA.
And yes, I know, people keep wanting to use dbmail to solve *all* their email
management problems. And I also know that was one of Roel and Eelco's original
design goals.
In my opinion the authsql user-management is already severely overloaded and in
serious need of redesign.
Why do we want to store alias information in the database: delivery
Why do we want to store user information in the database: authentication
Both are at present totally intertwined, both in the code, and in the perception
of many users. However, if we can separate them, great things are suddenly
possible like pam-authentication (users in ldap,passwd,radius...) while leaving
the aliases in the database, or even storing them elsewhere.
Michael Häusler wrote:
Hi,
What about that one: I have a user [EMAIL PROTECTED], no aliases. Then I go to
holiday and add an alias [EMAIL PROTECTED]>[EMAIL PROTECTED]
I would expect that I only get a copy and every mail still is in my
[EMAIL PROTECTED] INBOX.
But what if you want a temporary forward and *no* delivery to your
primary mailbox ([EMAIL PROTECTED])? This would be impossible to configure,
when mail is always delivered to the user.
Since the aliases table is about delivery, I'd say remove the:
alias deliver_to
----------------------------
[EMAIL PROTECTED] 123
and add a:
[EMAIL PROTECTED] [EMAIL PROTECTED]
--
________________________________________________________________
Paul Stevens [EMAIL PROTECTED]
NET FACILITIES GROUP GPG/PGP: 1024D/11F8CD31
The Netherlands_______________________________________www.nfg.nl
