It's funny how you often manage to solve problems you've been haunted by
for days just after you've mailed the proper mailing list about it,
isn't it? Well, this time I managed to be one step ahead, but as I had
already written most of the message when I realised the solution, I
guess I might as well send it. Maybe it can help someone else..
The correct solution was of course to change ~/testlist/inlocal and
~/testlist/outlocal from user-testlist to saying just testlist.
Thanks for the attention I WOULD have gotten had I not solved the
problem myself. ;)
Below is the original message.
Henrik.
---
Ok, I've been trying to do this in several ways now, without complete
success.
Some (or rather, one) users on our mail server want their own mailing
lists, but would rather not have the user name preceeding the list name.
<first.last-list>@gammadata.se is quite long and quite inconsequent.
It's OK with me, provided that I don't have to have him running around
in /var/qmail/alias to do it.
I tried with placing the usual .qmail-<list> aliases in
/var/qmail/alias, but naturally that fails. A simple .qmail-<list> for
forwarding works for sending to the list, and is what I use now, but it
works badly for requests and bounces.
Just now I tried to work it out with putting aliases in
/var/qmail/users, which seems to be the proper way to do it (if there is
any at all.)
My /var/qmail/users/assign looks like this (and this is just for my own
testlist.)
---
=testlist:spiff:9999:999:/home/spiff:-:testlist:
+testlist-:spiff:9999:999:/home/spiff:-:testlist-:
.
---
I succeed in sending messages to testlist, but testlist-help,
testlist-subscribe and others do not work. (Yes, they work if I use
spiff-testlist-help and spiff-testlist-subscribe.) And here is the error
message..
---
Hi. This is the qmail-send program at mail.gammadata.se.
I'm afraid I wasn't able to deliver your message to the following
addresses.
This is a permanent error; I've given up. Sorry it didn't work out.
<[EMAIL PROTECTED]>:
ezmlm-manage: fatal: I do not accept messages at this address (#5.1.1)
---
Does anyone know a way to solve this? Are the requests being processed
