Please reply to [EMAIL PROTECTED] for further discussion of this feature. Once the feature requirements are set, we will move the discussion over to qmailadmin-devel to go over implementation details. If you're only subscribed to qmailadmin-devel, send replies to me. I'd like to keep the discussion on a single list at a time...

On Monday, September 22, 2003, at 09:55 AM, Paul L. Allen wrote:
I remain unconvinced that this is the cleanest solution, although it may
be the only solution that works with everything (so far) known to use
.qmail files for special purposes. It certainly appears to fall short
of what is required.

How about this idea. Each domain has a template file (something like domains/domain.com/dotqmail-template?), or a default template (~vpopmail/etc/dotqmail-template?) that explains to qmailadmin how to build a .qmail file for a user. This would be used when adding a new user, or modifying an existing user. We could also add support to vpopmail's adduser command as well.


We'd have to define macros of some sort for a few useful options:

Username
Domain name
full email address
path to Maildir
insert vacation program delivery here
insert forwarding addresses here
insert spam check here
etc.

There might also have to be lines like "if V_USER1 is set, do this" or "if V_USER2 is not set, do this" to allow for sys admins to customize QmailAdmin using the USER flags (which is currently possible -- you have to update the text in the language file to indicate what the flag is for). This would allow end-users the option to turn on and off certain features of a .qmail file (as controlled by the sys admin).

After reviewing the moduser page in QmailAdmin, we might need to spend more time on this subject, and reorg the moduser page as well. If a user chooses to forward their email to another address and NOT save a copy, then QmailAdmin will need a way to build .qmail from the dotqmail-template file and NOT have mail saved in the Maildir...

I'd really like to find a resolution to the problem that's clean, simple and flexible. Since I personally won't be using this feature, I'll need help from everyone that does. I'd like to come up with a feature specification that will support the majority of your needs and then start coding it.

Question 1: Would such a system fit your needs?
Question 2: What macros would you use in a template (e.g., from the list above)?


--
Tom Collins
[EMAIL PROTECTED]
QmailAdmin: http://qmailadmin.sf.net/  Vpopmail: http://vpopmail.sf.net/
Info on the Sniffter hand-held Network Tester: http://sniffter.com/




Reply via email to