Hello everybody. I'm a new list manager and I'm looking for some
documentation to make some changes that I haven't been able to make
through the /mailman/admin/listname web interface.
I went to www.list.org, but the documentation there explains how all this
(already known in my case) stuff /mailman/admin/listname. For example, I
want to change the Reply-To: header and the addresses which listname-admin
and listname-owner point to, but it isn't described there, nor in the faq.
Could you tell me please where can I find a more complete doc? Thanks.
Guillermo Pereyra Irujo
Mar del Plata, Argentina
Linux User #207706
Dear gurus :)
Hey, I've been trying to convince the ppl at work that mailman would
be an awesome solution... just came across an "simple"? issue. Is
there anyway to automatically reject mail coming from a specific
address (or domain?) without having to bother the list administrator
Thanks for any help...
>From the hands of -< dansan >-
Not everything that can be counted counts, and not everything that
counts can be counted.
-- Albert Einstein
I installed Mailman on a Sun Sparc server, Solaris 2.8.
The name of the server is:
So far it seems to work fine, EXCEPT...
I created a mailing list named test. When I subscribed myself
to the test mailing list, I received a confirmation message.
The return address from this message was not correct, it
It should have been:
I have the following variable set for DEFAULT_HOST_NAME:
Defaults.py:DEFAULT_HOST_NAME = 'aulist'
mm_cfg.py:DEFAULT_HOST_NAME = 'aulist.duc.auburn.edu'
How can I fix this?
Office of Information Technology
Auburn University, AL
on 3/29/01 12:42 PM, Aleksandra Witkowska at aleksw(a)ameritech.net wrote:
> Blackhole list?
When you use m4 to compile sendmail's config file, it has an option to check
the senders domain/ip against a list that is maintained against spammers -
who seem to have discovered the usefulness of this list.
I get the following error message bouncing back when I try to post or
subscribe to a mailing list I set up on a Cobalt server. It is compliled to
use a local version of Perl 6 and is also compiled with a prefix.
It seems that wrapper is looking for /home/mailman/post in
/usr/local/majordomo and is obviously having problems. Why would it be doing
this and how do I fix it?
wrapper: Trying to exec /usr/local/majordomo/post failed: No such file
Did you define PERL correctly in the Makefile?
HOME is HOME=/usr/local/majordomo,
PATH is PATH=/bin:/usr/bin,
SHELL is SHELL=/bin/sh,
MAJORDOMO_CF is MAJORDOMO_CF=/usr/local/majordomo/majordomo.cf
451 "|/home/mailman/mail/wrapper post uknews"... Operating system error
I had something weird happen today. I set up a new list for a client today.
They used it and the users are telling them that they are getting the same
message 35-50 times. Do you have any idea why this might have happened?
I am the administrator of a non-profit mailing list. First of all let me
thank you for letting us use a great product. Now let me explain the
I have a mailing list, with the following settings
1. Posting allowed only for the list members.
2. Temporarily we have put the list under moderation. In this setting, all
messages have to be approved by the list administrator.
a). Under the above settings, I was under the impression that all postings
by non-members would be automatically rejected, and only postings by
list-members would be displayed to the administrator for approval.
b). But recently we received a couple of unsolicited postings from
non-members. These postings by non-members were also LISTED FOR APPROVAL
along with the postings from members. This created some confusion.
c). I verified the mailing list's setting once again and I do not see any
d). Is the above behavior is a Bug ?
I would appreciate a reply.
I have a list that has to have its archives rebuilt. The problem is that
the first two years of archives do not exist in mbox format, as someone
trimmed the mbox file way back when. This portion of the archives only
exists in the regular text files, that the Mailman archiver created.
I tried appending those two years of files together and changing the initial
"From user(a)foo.bar" to "^N^NFrom user(a)foo.bar" to get Mailman to see
the files as mbox format files. My local unix mail program (mailx) sees
the file as having 2200 or so messages for these two years, but the
archiver does not. It only sees two messages in total from it.
When I concatenated the old file with the current mbox file (the old
archives first ;-) It sees the two messages from the first part of the
file and then correctly processes the current mbox part.
How can I either a) persuade the archiver to properly handle these
messages or b) modify the pipermail.pck file to have it see these
two years worth of archives and properly update the index file.
We are using Mailman 2.0b2. While I want to upgrade to 2.03, I'd
rather not screw up too much at once.
Any advice would be appreciated.