In the immortal words of Troy Settle ([EMAIL PROTECTED]):
>
> Would you also advocate the use of a jackhammer over a nut cracker for
> gaining access to almonds?
I guess I see this as more of a case of not bothering to scrape my
knuckles using a cresent wrench when I've got a perfectly fitted bolt
driver available to me. YMMV.
> The terminology used in qmailadmin is very strange compared to the other
> MTAs that I've experienced. Anyone remember sendmail? You know... that
> bloated MTA that held the internet together for so many years? An alias is
> like this:
>
> sales: april,may,june
>
> Say I want my customers to be able to email us at [EMAIL PROTECTED] Under
> the other 3 MTAs I've worked with (sendmail, exim, postfix), I would create
> an ALIAS that points to the local staff accounts that should recieve mail
> sent to the support address (without actually creating a 'support' mailbox).
Okay, remember for a moment here that qmailadmin is not qmail, and
qmail is not vpopmail. If you want to do that, qmail will happily let
you:
cat <<EOF >/var/qmail/alias/.qmail-sales
april
may
june
EOF
cat <<EOF >/var/qmail/alias/.qmail-support
sysadmin1
sysadmin2
sysadmin3
EOF
Or you can just install fastforward (http://cr.yp.to/fastforward.html)
and edit "/etc/aliases" like you would in the Bad Old Days.
But given that qmailadmin makes creating and maintaining a mailing
list _really_ _really_ easy, I just can't see why you'd want to. Even
for a "tiny" distribution list (two to ten people, say), you get a
number of advantages (bounce and loop protection, archiving if you
like) and no disadvantages that I am aware of. Whereas I have on a
number of occasions had to clean up a monstrous (>1000 lines)
/etc/aliases file that tends to be the logical result of "Oh, I'll
just add another alias" after it's been let run for a couple of years.
It's not fun, believe me.
> If a user or employee leaves me, I cry. But, after I'm done crying, I'm
> nice enough to set up a forwarding for them ($HOME/.forward), which gets
> deleted when I delete the account. I need to rethink this as well. Not
> quite sure how to handle this gracefully under qmailadmin (so that when I do
> a vdeluser, the .qmail-blah file goes away too, or perhaps set an expiration
> time, after which the .qmail-bleh file goes away automatically).
You can do this using qmailadmin's forward feature, and it will work
regardless of whether the vpopmail virtual account is still there.
(Forwards take precedence over local accounts.)
> Oh, anyways, topic. If I want to host a mailing list for open subscription,
> then I use a list manager (procmail, now exmlm).
Having qmailadmin able to set a list as open or closed would be nice,
I grant. This should be a trivial addition.
-n
------------------------------------------------------<[EMAIL PROTECTED]>
Like an exterminator running low on dust, I'm /
bug-powder itchin' and I can't be trusted. (--Bomb The Bass)
<http://www.blank.org/memory/>------------------------------------------
