hello to all
one question: is there a easy way, to mail to all of the
list-administrators or do I have to set up a list for them seperately?
thanx
Stefan
[Copy sent separately to both exim and mailman lists]
I updated and cleaned up my HOWTO information for using exim & mailman
together and put it up on the exim web site. The exim list is now
using *exactly* that configuration (copied and pasted from the howto)
for its list settings, so I am reasonably confident that I didn't break
something stupidly when copying :-)
Any comments, corrections or additions on this can be sent directly to
me.
The URL for the HOWTO is
http://www.exim.org/howto/mailman.html
For completeness, Mailman info is at
http://www.list.org/
and exim information is at
http://www.exim.org/
The mailing lists and archives for each are linked off their main pages.
Nigel.
--
[ Nigel Metheringham Nigel.Metheringham(a)VData.co.uk ]
[ Phone: +44 1423 850000 Fax +44 1423 858866 ]
Is it possible to hook up a way to search mailman archives for
keywords or strings in the messages?
If so what is the preferred approach on a Red Hat Linux box (5.1 or
later)?
Is anyone on this list willing to share a recipe for doing the above?
TIA
jam
How should one approach converting to mailman from listproc
characterized by about
120 lists
3K subscribers
about 70 lists archived from 1995 (/home/listproc/httpd/html)
df gives
Filesystem 1024-blocks Used Available Capacity Mounted on
/dev/sda2 1981000 1381172 497414 74% /
/dev/sda1 15522 1134 13587 8% /boot
/dev/sda7 497667 284071 187894 60% /home/listproc
/dev/sda8 497667 266621 205344 56% /home/listproc/httpd
/dev/sda9 4353573 97841 4030422 2% /var/spool/news
/dev/sda10 1026067 214503 758552 22% /extra
This is on a Red Hat Linux 5.1 box dedicated to listserv.
I dunno nut'n about listserv and just started experimenting with
mailman.
The directories in /extra are
/ectra/listproc/archive mbox files to Aug 7 99
/ectra/listproc/archive/lists
about 120 subdirectories for lists, some empty,
some containing apparently monthly
archive.yymmdd.gz files
The listproc seems to have been poorly maintained and typically poorly
operated by the list owners as well.
Help, suggestions, guidance, and what all will be greatly appreciated.
jam
>I need to disable the password confirmation on subscription. I've changed
>the Defaults.py file to permit open subscription, and (I think) generated a
>new .pyc file, but it has made no difference in the behavior of the
>subscription - it still wants confirmation of the password. I've also made
>a couple of other minor changes to other files in an attempt to accomplish
>the same thing, but I seem to be missing some critical step in making the
>changes "live". Can anyone give me a clue? I'm looking at documentation,
>but I'm really in a hurry on this one and was hoping someone might have a
>quick answer.
First of, right there in the file, and in the docs, it warns you in
large letters not to be doing those types of configurations in the
Defaults file. Put the value you want to change in the mm_cfg.py file;
that's what it's for. Every installation of mailman is going to
clobber that Defaults file; none of them will touch the mm_cfg file.
Second, there's two variable you need to change. Set
ALLOW_OPEN_SUBSCRIBE to 1 to enable to ability to turn off password
confirmation. Set DEFAULT_SUBSCRIBE_POLICY to 0 to make new lists by
default be non-password confirming (generally a bad move in this day of
practical jokers and hackers, but I'll assume you know what you're
doing)
Third, realize that paragraph two up there just sets defaults for
*future* lists. Nothing in Defaults.py or mm_cfg.py affects the
settings in *existing* lists. Once you have ALLOW_OPEN_SUBSCRIBE set
to 1, the privacy pages of your various lists should now list a 4th
option for subscriptions, "None" I believe is the keyword. You have
to go through each list you want to have no confirmation, and no
admin approval, and turn it on. (Or write the python code to
do it for you. I dunno what the variable is, but perusing the
code should locate it for you; unless you have a buttload of lists,
it'd likely be faster to do it by hand.)
This is actually a python question, but since it's the mailman sources I
need to change, I hope someone here can answer the question.
I need to disable the password confirmation on subscription. I've changed
the Defaults.py file to permit open subscription, and (I think) generated a
new .pyc file, but it has made no difference in the behavior of the
subscription - it still wants confirmation of the password. I've also made
a couple of other minor changes to other files in an attempt to accomplish
the same thing, but I seem to be missing some critical step in making the
changes "live". Can anyone give me a clue? I'm looking at documentation,
but I'm really in a hurry on this one and was hoping someone might have a
quick answer.
Thanks.
Michael
Hi
I am running MailMan 1.0 on Solaris 2.6 and have several mailing lists.
list1 with subscribers lista, listb, listc, listd
lista with subscribers a, aa, aaa, aaaa
listb with subscribers b, bb, bbb, bbbb
listd d, dd, ddd, dddd
When I sent message to list1 I got a message from mailman admin about
administrative request for lists a, b, c, d and the reason "Implicit
address".
Any ideas?
Thanks in advance.
--
Igor Dukhovich
Network Systems Services
Parametric Technology, Inc.
Waltham, MA
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Anyone know what the proper permissions are for everything in ~mailman? I had
my lists working just fine, but then accidentally nuked a list, and had to
restore some file. Now, I am having permissions problems after my cron jobs run.
I get this from check_perms:
Traceback (innermost last):
File "bin/check_perms", line 160, in ?
checkall()
File "bin/check_perms", line 76, in checkall
os.path.walk(mm_cfg.PREFIX, checkwalk, STATE)
File "/usr/lib/python1.5/posixpath.py", line 253, in walk
walk(name, func, arg)
File "/usr/lib/python1.5/posixpath.py", line 253, in walk
walk(name, func, arg)
File "/usr/lib/python1.5/posixpath.py", line 247, in walk
func(arg, top, names)
File "bin/check_perms", line 52, in checkwalk
except OSError, (code, msg):
NameError: OSError
- --
- -----------------------------------------------------------------------------
Brian Knotts <bknotts(a)europa.com>
29-Oct-99 - 05:46:57
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v0.9.8 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE4GZfhKV5kReY9sP8RAvlNAJ9ZJ8J3h/Cxu6O46D1Bxsl08rYoXACgqaFW
91pA34607YjwynVZ7zn28g0=
=YwrS
-----END PGP SIGNATURE-----
Due to a mail loop, I have several hundred post requests in one of my lists.
I'd like to blow them all away without clicking 300 times on some web form.
I've looked around in the mailman tree, but I just can't find where those
subscription messages are sitting.
Can someone give me a hint?
Thanks,
Marc
--
Microsoft is to software what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/ (friendly to non IE browsers)
Finger marc_f(a)merlins.org for PGP key and other contact information
I maintain a Mailman mailing list and have had problems with users
sending messages in HTML format. Is there any way to either filter
or bounce these messages before they appear on the list?
Any help would be appreciated.
Thanks,
Christopher Everett
ceverett(a)directlink.net