Hi Davide and people,
It seems that my struggle was fruitful, soon xmail will replace 2
sendmail and 2 exchange server faily loaded ( over 280 domains and
approx 16000 e-mail addrs).
Now everything is fine and dandy, xmail behaved excellent on different
tortures, from mail-bombs to simulated network problems. And I have to
mention again that the new filter framework proved to be extremely
robust and simple to use if not as feature full as sendmail's libmilter,
but it does what we need it to do.
Here is a short description of a real world situation: customer A wants
to host 4 domains: 1 domain gold with maximum 1000 accounts, 2 domains
silver with 400 accounts and one domain bronze with 50 accounts , each
domain with its own quota, same gose for customer B that has another set
of domains with different parameters.
Now from the existing features of xmail I'm able to do everything
except for these things:
-Limitation of maximum number of accounts ( and possibly aliases) per
domain, this feature is essential for a commercial success of xmail and
I belive it will make xmail the dear of small ISPs.
-A method to have an intermediate level between full server
administrator that can create/delete domains at will and postmaters that
are restricted inside of a domain, some kind of demi-gods that are
allowed create a limited and configurale number of domains with
predefined restrictions like domain quota and max number of accounts and
max number of aliases. This demigods will have to be defined in the same
TAB that now keep server admins or in a separate TAB.
- Priviledge separation between domain creators, like once a demigod
created a domain this becomes his only to meta-administrate ( override
postmaster tasks and delete domain) that domain. His priviledges must
not extend over some other people domains even if is capable to
delete/rename/create domains of its own within the constraints of his
definiton. Of corse server admin will keep full override rights over ALL
domains.
- The posibility to add new variables in domain TAB definitons ( and
even in the users ones ) in the form of name/value pairs to be able
store comments and stuff not directly related to server operatins, like
comments and accounting info.
I know that all those could be implemented in some middleware sitting
between xmail control channel and configuration/administration
application but I'd really like to see at least accounts nummber
restriction and generic variables in the main distribution.
If some of the thing I've listed above can be done in the already
existing xmail, excuse my blindness in reading the docs and help me see
the light :-) with some examples.
Davide if you are not interested about these features plese helpme at
last with some insightfull ideeas of where is the best way to name/place
those variables to be consistent with the existing naming/organization
conventions and I'll try to do the programming as much as possible.
Of course if you or anybody else have some patches related to that
features lingerin somewhere I'll be more than happy to test them and
help debug/finish them.
Thank you all for your time used to read this rather lenghty message
and keep up the good work.
Mircea C.
-
To unsubscribe from this list: send the line "unsubscribe xmail" in
the body of a message to [EMAIL PROTECTED]
For general help: send the line "help" in the body of a message to
[EMAIL PROTECTED]
