I figured it out myself (by looking in the listinfo code to see
what it did). Found the VIRTUAL_HOST_OVERVIEW setting. Changed
that to "0", and I get the behaviour I want now.
--jessica
Jessica Koeppel wrote:
>
>This might be more of an apache configuration thing, but
&
This might be more of an apache configuration thing, but
I'm not sure. It actually feels a bit more like a mailman thing.
I have mailman installed on machine "mail2.foo.com".
There's an alias for the machine, "lists.foo.com".
I have apache configured so that when you come in to
the server with
and don't forget that most mail servers' configurations
will require you to run something to get the mail server
to recognize the new aliases (ie; sendmail's "newaliases",
and postfix's newaliases or "postalias hash:/path/to/aliases-file"
or whatever's appropriate for your configuration).
-jess
>1) is there any way to recreate the .db files, or in any other manner,
>get these messages sent out?
I figured out that I could cat the stranded .msg file through
"mail/wrapper post ".
where listname was the appropriate list for the file in question. I
moved all these stranded .msg files t
I'm running mailman 2.0.8 on OpenBSD 2.9, with Python 2.0.
I noticed that my qrunner log file was getting big - it was
full of errors like this:
Feb 24 21:08:37 2002 (26363) Exception reading qfile:
/local/mailman/qfiles/bdc2a3863d4738f59ad367ba32b011997f9db914
[Errno 2] No such file or direct
Oh no. I've just discovered that Outlook replies to the "Sender:"
field, over the "From:" field in many situations. It uses "From:" when
you hit "Reply", but it uses "Sender:" to display the "From:" field in
certain places (only some places! it's crazy!), and worst of all, it
uses Sender: when yo
Oh no. I've just discovered that Outlook replies to the "Sender:"
field, over the "From:" field in many situations. It uses "From:" when
you hit "Reply", but it uses "Sender:" to display the "From:" field in
certain places (only some places! it's crazy!), and worst of all, it
uses Sender: when yo
I've got a bunch of lists which I want to have set so that anyone can
subscribe themselves very easily.
However - I want only people on my internal network to be able to do this.
The web interface is accessible only internally, so that's easy.
But [EMAIL PROTECTED] is still there - random outs
There is also a per-list option, which I believe controls this. (I haven't
actually experimented to make sure it works as I expect it to, though!).
On the list's General Options page, a little more than half way down,
you'll find "Send monthly password reminders or no?".
So you ought to be able
Markus Kachel wrote:
>
>I thing, that it is the best solution to change the name for the
>second list. Many list-robots use -admin as the adress for the
>Admin or Moderator of the list, for example Mailman and Majordomo. So
>it is nearly a standard, because it is often used.
Hi Markus,
I definite
I'm using mailman at home for some lists, and really like it.
I'm now setting it up for someone who has been hosting a whole bunch
of lists. Unfortunately, I've doscovered that in two cases, he has
bot and -admin lists. This doesn't work with mailman
because I need to put -admin into the aliase
11 matches
Mail list logo