We're currently using Qmail to host approximately 50 mailboxes for a
single domain. The accounts have been created as system accounts on a
Red Hat 6.0 machine. We're currently trying to find solutions to a
couple problems:
1) Something that will allow an administrator to quickly create a
forward file for a specific user. For the most part, the email accounts
are assigned to customer service personnel. If they're sick for a day,
we need a way to painlessly and transparently forward their mail to
another representative. While we currently do this by connecting to the
machine and hand-creating an appropriate line in ~/.qmail, it's not an
optimal solution as the other administrator is not familiar with Unix.
We'd also like to be able to delegate the responsibility for creating
these forwards to the department head to relieve the IS department of a
bit of work.
2) A utility that will silently migrate user passwords from /etc/shadow
to another (more easily dealt with) storage scheme. We currently
utilize MD5 hashing in the file. Right now, we're using checkpassword
to authenticate POP3 retrievals and chpasswd.cgi to allow web-based
password changes. Apart from boldly breaking email retrieval in moving
to other methods, I'm not sure how to approach this. Ideally, I'd like
to be able to move to something that allows easy mail management via web
interfaces (much easier for my coworker to deal with). That would
include addition and removal of users, the above mentioned forwarding
and other items.
I've looked at qmailadmin, but it seems to require the use of virtual
domains and user setup outside of system files. I'd love to move to
POP3 service that doesn't require system accounts, but I think I've
backed myself into a corner using system accounts (and not making note
of passwords). Any hints in making changes that are invisble to users
would be greatly appreciated.
Any ideas from other readers?
--
Steve Philp
Network Administrator
Advance Packaging Corporation
[EMAIL PROTECTED]
