Michael Monnerie wrote:
On Freitag 26 Juni 2009 Paul J Stevens wrote:
I don't follow. It's been in dbmail forever. Take a look at
dbmail.schema.
OK, I never looked so far, as LDAP was never really thought about. I
looked once into it, but didn't find a nice tool to insert our data in
an
On Mittwoch 24 Juni 2009 Michael Monnerie wrote:
I've extended dbmail since before we started, in order to have an
extra domains and customers table. This has big advantages.
Nobody to comment on this? Too complicated, too harsh, or maybe just a
stupid idea of me?
mfg zmi
--
// Michael
On Mittwoch 24 Juni 2009 Michael Monnerie wrote:
I've extended dbmail since before we started, in order to have an
extra domains and customers table. This has big advantages.
Nobody to comment on this? Too complicated, too harsh, or maybe just a
stupid idea of me?
mfg zmi
--
// Michael
Michael Monnerie wrote:
On Mittwoch 24 Juni 2009 Michael Monnerie wrote:
I've extended dbmail since before we started, in order to have an
extra domains and customers table. This has big advantages.
Nobody to comment on this? Too complicated, too harsh, or maybe just a
stupid idea of me?
On Freitag 26 Juni 2009 Paul J Stevens wrote:
Even we do very much the same in our main installation, we use LDAP
to extend the user model, so the extra tables would be redundant for
us. Also, I fail to understand how the additional tables effect
dbmail internals. My business logic builds on
Michael Monnerie wrote:
On Freitag 26 Juni 2009 Paul J Stevens wrote:
Even we do very much the same in our main installation, we use LDAP
to extend the user model, so the extra tables would be redundant for
us. Also, I fail to understand how the additional tables effect
dbmail internals. My
I think I've said this around 2006 already, but maybe time has come to
suggest it again. As far as I read this mailing list, most people use
dbmail to run several (if not lots of) domains. We are in the same
situation, a small ISP running some hundred domains.
I've extended dbmail since before
