I disagree. Think about a setup where more than one frontend connect to
a single backend.
Storage of configs in the database was how things were done pre-1.0. Bad
idea. I want to be able to tune front-end specifics on the front end:
listen at different addresses, run at different debug levels, run more
or less processes, etc.
Doug Stanley wrote:
I agree!
Doug
Matthew T. O'Connor wrote:
Personally, I think all dbmail configuration information should be
stored in
the database, the only exception being, bootstrap info required to
connect
to the database.
----- Original Message ----- From: "Jesse Norell" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Friday, October 10, 2003 2:55 PM
Subject: [Dbmail] feature solicitation
Hello,
Would anyone be interested in customizable error messages for
dbmail bounces, etc.? Eg. have a directory /etc/dbmail/ with
some message templates that are used to build the actual errors
(mailbox full, no such user, etc.). Or maybe would be nicer to
have them in a table in the database (for sites that use multiple
dbmail boxes for the same message store). I'll log a feature
request as a reminder if it seems like a good idea.
jn
--
Jesse Norell
jesse (at) kci.net
_______________________________________________
Dbmail mailing list
[email protected]
https://mailman.fastxs.nl/mailman/listinfo/dbmail
_______________________________________________
Dbmail mailing list
[email protected]
https://mailman.fastxs.nl/mailman/listinfo/dbmail
_______________________________________________
Dbmail mailing list
[email protected]
https://mailman.fastxs.nl/mailman/listinfo/dbmail
--
________________________________________________________________
Paul Stevens mailto:[EMAIL PROTECTED]
NET FACILITIES GROUP PGP: finger [EMAIL PROTECTED]
The Netherlands________________________________http://www.nfg.nl
