Hello,
I haven't been reading the list much lately, so I'm not sure if these
items have been discussed before.
Some functionality that has been asked for by users on our network, that
does not seem to exist in any of the versions of QmailAdmin that are
available, are the FUNCTIONs below. The SOLUTIONs are what changes I've
made to the QmailAdmin source that we maintain to address them, but
these may not and probably are not optimal.
FUNCTION: The ability to create and manage default aliases, in the form
of:
.qmail-test-default
There is code in the alias.c file to ignore any files that end in
-default. This seems to be in place to prevent mailing list
configuration files from coming up. The result is that a user can add
default aliases, but they will not show up in the interface.
SOLUTION: Instead of blocking .qmail files that end in -default, just
blocked .qmail-default, and then for any any other -default files, use
the 'is_mailing_list()' function to check if it is associated with a
mailing list, and skip the file if it does belong to a mailing list.
FUNCTION: The ability to blackhole an email address, so that any email
sent in to that address will be deleted. Useful when you don't want to
bounce the message, but just want it to disappear.
SOLUTION: First, changed the dropdown box of email users when adding a
new alias to include a DELETE option. Selecting this option would
create a dotqmail file with the following:
| /usr/local/vpopmail/bin/vdelivermail '' delete
Not sure if this is the best way to blackhole email, or if routing it to
/dev/null is.
Next, to have the program parse files correctly and display them as a
DELETE destination, I added code to check the file for the above
string. If it matched, then the "Email Account" field was filled in
with "DELETE", and the modify button was set to disabled.png, as there
is no point to modifying it really.
------------------------------
If others on this list think these features would be useful, could we
get this functionality rolled into a future release of QmailAdmin?
Any feedback on my methodology for the solutions is welcome as well, as
there are probably a number of cases that I'm not taking into
consideration where problems may arise.
I could provide a patch, but I think it would be best to see if the
functionality can be implemented cleanly by the code maintainers rather
than my hack.
--
Justin Hopper <[EMAIL PROTECTED]>
