On May 3, 2005, at 04:21, Tony Bibbs wrote:
I had my mailman site defaced. The
/path/to/mailman/archives/public/listname/index.html
pages have all been replaced by crap.
How do I recover those pages?
You can regenerate them using the 'arch' tool supplied with Mailman:
bin/arch --wipe
On May 3, 2005, at 06:07, Chris Serenil wrote:
I have just installed Mailman 2.1.15 with the htdig
patch 444884 and 444879. The search fails when I have
a list name with a dot in it. (Example
fa.dl-testlist). I will get these errors when doing a
search. If there is no dot it works fine.
On May 7, 2005, at 03:36, Anshuman Prusty wrote:
In the test server at gospelcom.net, I am testing the subscriptions
for the newsletter and receiving the following error messages
--
--
Warning: fsockopen(): unable
On May 3, 2005, at 00:07, Jeff Peterson wrote:
In the Topic Name field, I have tried adding extra spaces, but the
extra
spaces are not displayed.
The leading spaces are preserved in the list object, but since they
are being displayed in a table cell, they don't appear in the GUI.
I have
On May 4, 2005, at 03:36, James Beeghley wrote:
I am setting up Mainman to be used as a communication mechanism for
my school district. I was wondering if it is possible to modify the
confirming emails which are sent to potential subscribers.
You can modify the template 'verify.txt',
Hi,
thank you for your answer.
Pickle de l'état des archives
vers /usr/local/mailman/archives/private/testliste/pipermail.pck
I think that should be the last thing it writes
In fact, it's the only thing it writes...
, as it saves the
state of the archives in the pickle. (Does it
At 11:49 PM -0400 2005-05-06, Larry Hansford wrote:
I got it working. I upgraded from Python 2.2.3 to Python 2.3.5
and reinstalled Mailman, and it began working.
Mailman 2.1.5 required Python 2.3, but in theory this was
supposed to be fixed in Mailman 2.1.6, easing the restriction
At 07:45 AM 5/7/2005, Brad Knowles wrote:
At 11:49 PM -0400 2005-05-06, Larry Hansford wrote:
I got it working. I upgraded from Python 2.2.3 to Python 2.3.5
and reinstalled Mailman, and it began working.
Mailman 2.1.5 required Python 2.3, but in theory this was
supposed to be fixed in
I get the error:
UnicodeEncodeError: 'ascii' codec can't encode character u'\xd6' in
position 5: ordinal not in range(128)
in mailmans logs/errors, but how do I find out which list / which mail
causes it?
Apr 14 09:21:52 2005 (7409) Traceback (most recent call last):
File
I can access Mailman webpages just fine; however, after I fill in the
new list info and hit submit I get an error message (Bug in Mailman
version 2.1.5 We're sorry, we hit a bug!.) Also, it seems that no
emails can be sent or received trough the list.
I've tried to add in mm_cfg.py the following
On 5/7/05 4:45 AM, Brad Knowles [EMAIL PROTECTED] wrote:
Mailman 2.1.5 required Python 2.3, but in theory this was
supposed to be fixed in Mailman 2.1.6, easing the restriction back
down to Python 2.1.
Which would imply that Barry's new email module is good back at least to
Python 2.1. (If
Thanks to Dan' suggestions I've fixed the perm error.
I have a different MTA problem now. When I try to subscribe to the
list, or send an email to the list I get...nothing. No email makes it
trough the list, and I also get no subscription conformation from the
list.
Python 2.3.5, Mailman 2.1.5,
I can't understand these two logs. No mail makes it trough and this is
the only relelvant thing that I can see in the MTA logs. The second
log is a cron error. I've search the FAQ, read it, and I still don't
know how to troubleshoot this.
May 7 16:30:02 mail postfix/pickup[531]: 620D21002E8A:
Did you copy the /home/mailman/scripts/mailman to /etc/rc.d/init.d/, and
then do chkconfig --add mailman?
Did you do a /etc/rc.d/init.d/mailman start? Did you get any errors when
you did the start?
At 07:41 PM 5/7/2005, James wrote:
Hrrm... what do I do now?
ps aux | grep qrunner
root
I've cp /usr/lib/mailman/scripts/mailman /etc/init.d/. No errors.
I do have one problem with cron that I can't figure out. When I try to
ls -la the path in the error message below I don't see the
gate_news.lock
ls -la /var/lib/mailman/locks/
total 8
drwxrwxr-x+ 2 list list 57 May 7 17:01 .
On May 8, 2005, at 06:16, Daya Baran wrote:
If you edit confirm.py - you get this message Bug In Mailman
You must have made a mistake editing the script so that it was no
longer a valid Python program.
I had to reinstall mailman
If you had just been making changes to the one file, you
Is there a way to create default settings (privacy options, bounce
processing etc) that would be copied to all newly added mailing lists?
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
On May 8, 2005, at 10:43, James wrote:
Is there a way to create default settings (privacy options, bounce
processing etc) that would be copied to all newly added mailing lists?
Copy the settings you wish to customize from Mailman/Defaults.py to
your Mailman/mm_cfg.py file and make the
18 matches
Mail list logo
