Hi,
Is it really worth the effort to develop the aliasing in dbmail, with all
error handling etc.
Isn't it other issues that could use our attention better?
Howabout using your MTA.
What's going on here? Nobody is talking about new developments. There is
a bug in the *existing* dbmail functionality. There are several
possibilities to fix it. It's all about the simple decision which of
these fixes would be best for dbmail.
Aliases have their problems and maybe it would be best to do away with
them in dbmail-3. But now, this is existing functionality and people may
depend on it. It should simply be fixed the right way. "How about using
your MTA" is in no way a solution to the problem at hand.
Imho, since aliases are features in both dbmail-1 and dbmail-2,
everything that is possible in dbmail-1 should still be configurable in
dbmail-2.
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]
This is exactly what I was talking about: this would *not* be working if
we chose to always deliver to a matching user. Imho, this would be a
regression to dbmail-1.
Best regards,
Michael
