[qmailadmin] .qmail-user location patch for qmailadmin?

2004-12-01 Thread john bender
I've inquired before about the location of the
.qmail-user or user/.qmail files that qmail works on
when, for example, a vacation message is enabled for a
specific account.

Is there a patch that would make qmailadmin only work
on

~vpopmail/domains/domain.com/.qmail-user

instead of

~vpopmail/domains/domain.com/user/.qmail ?

I have some knowledge of C, and could probably hack
it, but if there is a patch that was released by
Inter7, I'd prefer to use that.

Thanks.



__ 
Do you Yahoo!? 
All your favorites on one personal page – Try My Yahoo!
http://my.yahoo.com 


[qmailadmin] QmailAdmin 1.2.5 released (devel)

2004-12-01 Thread Tom Collins
http://qmailadmin.sf.net/
Release Notes:
This release is mainly code cleanup.  Function declarations were
moved into header files, and we now compile QmailAdmin with
all warnings on.
I made changes to the code to eliminate all compiler warnings
(fixing some problems in the process).  Due to the large number
of changes, this release will be classified as devel until it has had
more testing.
In addition to the main code cleanup, I rewrote the code that
parses a user's .qmail file and made a slight change in how .qmail
files with vacation responses are written.  This is the first step
toward fixing a number of known problems with .qmail files.
ChangeLog:
Tom Collins
- Remove unnecessary name attributes in SUBMIT buttons. [869292]
- When adding a mailing list, automatically subscribe the
  list owner and make them a moderator/remote admin. [892489]
- user.c: deliver mail to Maildir before sending vacation message
  in order to prevent autorespond from losing messages.
- Move .qmail parsing code from template.c to user.c.  Rewrite
  for more flexibility and to allow new format for vacation.
- configure.in: Compile with all warnings on.
- Add header files: alias.h auth.h autorespond.h cgi.h command.h
  dotqmail.h forward.h limits.h mailinglist.h show.h template.h
  user.h util.h.
- Modify .c files to use header files, fix function prototypes,
  definitions and calls for consistent parameter passing and
  return values.
- Modify code to eliminate all compiler warnings.