This is the error message I get when I try to update a picture
URL with its current URL, in the file
https://mailman.gramstad.no/mailman/edithtml/enag-mausoleum/listinfo.html
:
Bug in Mailman version 2.1.29
We're sorry, we hit a bug!
Please inform the webmaster for this site of this
On 1/6/20 10:13 AM, Erwin Schmitz wrote:
>
> Mailman Administrator Authentication page
> (.../cgi-bin/mailman/admin/mailman)
>
> After entering password and clicking on "Let me in" this message appears :
>
> Bug in Mailman version 2.1.23
>
> We're sorry, we
LS,
I'm using mailman mailinglists, only private lists are configured.
Mailman Administrator Authentication page
(.../cgi-bin/mailman/admin/mailman)
After entering password and clicking on "Let me in" this message appears :
Bug in Mailman version 2.1.23
On 10/27/19 9:24 PM, Stephen J. Turnbull wrote:
>
> It appears this process is running as www-data. Does
> /var/lib/mailman/locks exist? Is it a directory? Is it readable and
> writable as a directory by www-data or www-data's group? Is it on a
> local disk, or some kind of network file
Dave Stevens writes:
> I was trying to log in to the mailman pending admin tasks page to
> delete an attempted post by a non-member.
>
> in /var/log/mailman/error is:
> admin(22004): File "/var/lib/mailman/Mailman/LockFile.py", line 422,
> in __write admin(22004): fp =
Bug in Mailman version 2.1.26
We're sorry, we hit a bug!
Please inform the webmaster for this site of this problem. Printing of
traceback and other system information has been explicitly inhibited,
but the webmaster can find this information in the Mailman error logs.
I was trying to log in to
: mailman-users@python.org
> Subject: Re: [Mailman-Users] Bug in Mailman version 2.1.25
>
> On 04/14/2018 06:12 AM, Odhiambo Washington wrote:
> >
> > Here is what I would do:
> ...
>
> The suggestions here are way too complicated.
>
> Do the following:
>
On 04/14/2018 06:12 AM, Odhiambo Washington wrote:
>
> Here is what I would do:
...
The suggestions here are way too complicated.
Do the following:
Either run Mailman's
bin/rmlist myproblemlist
or just
rm -r /usr/local/mailman/lists/myproblemlist/
These will do the same thing which is
ailman-users@python.org
> > Subject: Re: [Mailman-Users] Bug in Mailman version 2.1.25
> >
> > Hopefully, you have a recent backup from before the outage with a good
> /usr/local/mailman/lists/myproblemlist/config.pck file that you can
> restore.
>
>
> Unfortunately,
> -Original Message-
> From: Mailman-Users
[mailto:mailman-users-bounces+mpn=icabs.co...@python.org] On Behalf Of Mark
Sapiro
> Sent: Friday, 13 April 2018 4:46 PM
> To: mailman-users@python.org
> Subject: Re: [Mailman-Users] Bug in Mailman version 2.1.25
>
> Hopeful
On 04/13/2018 04:25 AM, MPN Kazishe wrote:
>
> Apr 13 13:04:49 2018 (58769) couldn't load config file
> /usr/local/mailman/lists/myproblemlist/config.db.last
>
> [Errno 2] No such file or directory:
> '/usr/local/mailman/lists/myproblemlist/config.db.last'
>
> Apr 13 13:04:49 2018 (58769) All
Dear All,
I am running mailman version 2.1.25 on FreeBSD 11.1-RELEASE. I am getting
this error after a power outage on one of the lists. The web page give this
error here:
Bug in Mailman version 2.1.25
We're sorry, we hit a bug!
Please inform the webmaster for this site of this problem.
On 09/11/2017 04:15 AM, Menachem Bazian wrote:
>
> I inherited an install of Mailman and I know very little about it. I have
> been able to do most tasks (it's pretty intuitive) but I can't get in to
> the admindb portion of the program. I can login but when I do I get this:
>
> Bug in Mailman
Hi,
I inherited an install of Mailman and I know very little about it. I have
been able to do most tasks (it's pretty intuitive) but I can't get in to
the admindb portion of the program. I can login but when I do I get this:
Bug in Mailman version 2.1.23 We're sorry, we hit a bug!
Please inform
Hi
I know that this has been going around the internet lately. I've done
the usual web search. Not really found anything that might work for
me. I've installed a CentOS 7 web server. I'm building a site around
it. Mailman is my list management software. I've used it for more
than ten
Hi
Further to the last one. I did reinstall from the CentOS RPM. Some
things started to work but the list admin page stills gives me the
same error. I have tried to build from source but that fails
miserably. This is the first time that I've installed Mailman and so
I'm not sure what I've
On 08/16/2014 04:18 AM, Richard Ibbotson wrote:
I'm not sure what I've missed. /var/log/mailman/error shows...
Aug 16 07:12:25 2014 admin(17943):
admin(17943): [- Mailman Version: 2.1.15 -]
admin(17943): [- Traceback --]
On Saturday 16 August 2014 09:16:44 Mark Sapiro wrote:
This may be a file or a symlink to something like
/var/lib/mailman/data/adm.pw. In any case, the target needs to be
group mailman and mode 0640.
Running
sudo bin/check_perms -f
should fix this.
Ah... That was the one. I thought
--On 18. Dezember 2013 07:04:14 -0800 Mark Sapiro m...@msapiro.net wrote:
On 12/18/2013 01:27 AM, Sebastian Hagedorn wrote:
I installed Mailman 2.1.17 last night (upgrade from 2.1.15) and decided
to give the SUBSCRIBE_FORM_SECRET feature a try, since we don't use
static subscribe forms. All
Hi,
I installed Mailman 2.1.17 last night (upgrade from 2.1.15) and decided to
give the SUBSCRIBE_FORM_SECRET feature a try, since we don't use static
subscribe forms. All seemed well, but this morning I noticed that the
listinfo page for some of the lists didn't work anymore. Here's an
On 12/18/2013 01:27 AM, Sebastian Hagedorn wrote:
I installed Mailman 2.1.17 last night (upgrade from 2.1.15) and decided
to give the SUBSCRIBE_FORM_SECRET feature a try, since we don't use
static subscribe forms. All seemed well, but this morning I noticed that
the listinfo page for some of
On 08/08/2013 10:55 AM, Ralf Hildebrandt wrote:
- IncomingRunner now logs rejected messages to the vette log.
(LP: #1068837)
So I had a look today and found:
Aug 06 12:12:59 2013 (11069) doctors: Refused posting:
...
Aug 06 14:02:38 2013 (1639) doctorsportal: Discarded posting:
Aug 06
- IncomingRunner now logs rejected messages to the vette log.
(LP: #1068837)
So I had a look today and found:
Aug 06 12:12:59 2013 (11069) doctors: Refused posting:
...
Aug 06 14:02:38 2013 (1639) doctorsportal: Discarded posting:
Aug 06 14:02:38 2013 (1639) doctorsportal: Discarded posting:
I had been using mailman properly since the last few days but suddenly i am
getting this error while going to my admin page :
Bug in Mailman version 2.1.10 We're sorry, we hit a bug!
Please inform the webmaster for this site of this problem. Printing of
traceback and other system information has
Not without error details. You must find the error. Perhaps you are looking
at the wrong file.
On 11 April 2013 22:44, Sneha Bhattacharya sneha.2...@gmail.com wrote:
I had been using mailman properly since the last few days but suddenly i am
getting this error while going to my admin page :
Sneha Bhattacharya wrote:
I had been using mailman properly since the last few days but suddenly i am
getting this error while going to my admin page :
Bug in Mailman version 2.1.10 We're sorry, we hit a bug!
Please inform the webmaster for this site of this problem. Printing of
traceback and
We receive this error:
Bug in Mailman version 2.1.9
We're sorry, we hit a bug!
Please inform the webmaster for this site of this problem. Printing of traceback
and other system information has been explicitly inhibited, but the webmaster
can find this information in the Mailman error logs.
On 5/24/2012 5:41 PM, Fletcher Cocquyt wrote:
When attempting to login to the admin interface and the logs say:
May 24 17:32:05 2012 admin(20758):
admin(20758): [- Mailman Version: 2.1.9 -]
admin(20758): [- Traceback --]
Fletcher Cocquyt fcocquyt at stanford.edu writes:
We receive this error:
Bug in Mailman version 2.1.9
We're sorry, we hit a bug!
I added a debug line to Archiver.py:
syslog('error', 'Archive file access failure:\n\t%s %s', old, new)
and it revealed the issue was a missing symlink in
On Thu, 31 Mar 2011, Mark Sapiro wrote:
This error is due to one of several known incompatibilities between
Mailman versions older than 2.1.12 and Python 2.6 or later. See the
FAQ at http://wiki.list.org/x/pYA9.
I read the FAQ, which was however last updated in 2009.
This MIGHT not be a
Lucio Chiappetti wrote:
On Thu, 31 Mar 2011, Mark Sapiro wrote:
This error is due to one of several known incompatibilities between
Mailman versions older than 2.1.12 and Python 2.6 or later. See the
FAQ at http://wiki.list.org/x/pYA9.
I read the FAQ, which was however last updated in 2009.
On Wed, 30 Mar 2011, Mark Sapiro wrote:
Lucio Chiappetti wrote:
- when subscribing an user (myself) to [any] list via the web
interface I get the message on the screen
Bug in Mailman version 2.1.11
We're sorry, we hit a bug!
Please inform the webmaster for this site of this problem.
Lucio Chiappetti wrote:
I confirm that despite the fact this message is shown on the web page, I
receive the regular confirmation message, and if I click on the provided
URL I am regularly subscribed.
This error is due to one of several known incompatibilities between
Mailman versions older
On Wed, 30 Mar 2011, Lucio Chiappetti wrote in thread starting at
http://mail.python.org/pipermail/mailman-users/2011-March/071332.html
and ran bin/withlist -l -a -r fix_url
I still have some problems when subscribing a new user, and concerning
message archiving. I will post a separate
Lucio Chiappetti wrote:
On Wed, 30 Mar 2011, Lucio Chiappetti wrote in thread starting at
http://mail.python.org/pipermail/mailman-users/2011-March/071332.html
and ran bin/withlist -l -a -r fix_url
I still have some problems when subscribing a new user, and concerning
message archiving. I
Hi,
Figured this would be the best place to report this.
I just tried again to subscribe to the developers list and discovered that
you couldn't confirm your subscription just by replying.
The message text implies that the confirmation key should be in the
subject, but the confirmation key
Geoff Shang wrote:
I just tried again to subscribe to the developers list and discovered that
you couldn't confirm your subscription just by replying.
The message text implies that the confirmation key should be in the
subject, but the confirmation key was in the From address of the
On Mon, 1 Feb 2010, Mark Sapiro wrote:
There are two ways this works in general. If the site's
VERP_CONFIRMATIONS setting is No (the default) the confirmation is
From: listname-requ...@... with Subject: confirm token, and the
reply is to the listname-requ...@... address with the confirm command
Geoff Shang wrote:
On Mon, 1 Feb 2010, Mark Sapiro wrote:
If the site's VERP_CONFIRMATIONS setting is Yes as it is at python.org,
the confirmation is From: listname-confirm+token@... with Subject:
Your confirmation is required to join the listname mailing list, and
the reply is to
Mark,
The modification to MailList.py is something that you suggested awhile
back and I had carried it through as Mailman was upgraded. Here is the
thread from 2005.
http://mail.python.org/pipermail/mailman-users/2005-January/042116.html
This time, it didn't seem to work and broke it.The
Christopher Adams wrote:
The modification to MailList.py is something that you suggested awhile
back and I had carried it through as Mailman was upgraded. Here is the
thread from 2005.
http://mail.python.org/pipermail/mailman-users/2005-January/042116.html
This time, it didn't seem to work and
Mark,
Yes, you are correct. I realized that I was referring to the wrong fix
after sending my message. I certainly didn't want to insinuate that
you gave me bad information.
That aside, the question still stands. Why are these fixes needed to
force the templates to display as it seems they
Christopher Adams wrote:
That aside, the question still stands. Why are these fixes needed to
force the templates to display as it seems they should be default?
What about a list adminstrator who doesn't have full run of the system
to make these fixes? An administrator who does have full run
Since upgrading to version 2.1.12, I have experienced a number of
errors that have resulted in a You've Hit a Bug. So far, I have been
able to patch things up. The latest occurs when a user attempts to
subscribe from the web. Here is the error log information:
admin(9559): [- Mailman Version:
Christopher Adams wrote:
Since upgrading to version 2.1.12, I have experienced a number of
errors that have resulted in a You've Hit a Bug. So far, I have been
able to patch things up. The latest occurs when a user attempts to
subscribe from the web. Here is the error log information:
Hi,
I have suddenly begun getting an error on the ListInfo page for all of
my Mailman mailing lists. This is fairly recent. The lists function
normally (as in, emails sent to the list address are sent to the
subscribers) but nobody can subscribe through the listinfo page.
Yes, I know
J.R. Constance wrote:
I have suddenly begun getting an error on the ListInfo page for all of
my Mailman mailing lists. This is fairly recent. The lists function
normally (as in, emails sent to the list address are sent to the
subscribers) but nobody can subscribe through the listinfo page.
Thanks Mark, that fixed the problem.
The pending.pck file had a date of Sep 2007 with a file size of zero.
And yes, I did change that list address. Always feel kind of queasy
about giving out that much info for one of my lists to a public
mailing list.
By the way, visiting the listinfo
Bug in Mailman version 2.1.9 We're sorry, we hit a bug!
Help me...
--
'Feel the fear in my enemy's eyes'
==
Guilherme Funchal da Silva .`.
LPI Level 2 Certification
--
Mailman-Users mailing list
Guilherme Funchal wrote:
Bug in Mailman version 2.1.9 We're sorry, we hit a bug!
Help me...
If you have access to Mailman's logs, post the complete error message
and traceback from Mailman's error log.
If you don't have access to Mailman's logs, ask for help from the
people that administer the
Hi All
Can anyone shed any light on this error I get when creating a new list
from the webpage. (I can create lists okay from the newlist command)
*** Displayed on the webpage ***
-
Bug in Mailman version 2.1.9
We're sorry, we hit a bug!
Please inform the
Mark Dale wrote:
Can anyone shed any light on this error I get when creating a new list
from the webpage. (I can create lists okay from the newlist command)
*** extract from the error log ***
--
Jul 01 05:27:46 2008 (14663) command failed: /usr/sbin/postmap
- Pesan Asli
Dari: Mark Sapiro [EMAIL PROTECTED]
Kepada: [EMAIL PROTECTED]; Mailman-Users@python.org
Terkirim: Selasa, 1 Juli, 2008 20:59:40
Topik: Re: [Mailman-Users] Bug reported when creating a new list from webpage
Mark Dale wrote:
Can anyone shed any light on this error I get
That's great Mark, many thanks.
Just recapping for anyone else's interest.
--
After installing Mailman, when first attemping to create a new list
using the webpage - it returned a You don't have permission.
(Creating a new list
I tried starting up my mailman installation this morning (mailmanctl start),
and I got the following message:
Traceback (most recent call
Ki Song wrote:
One major error I see is that there is no more disk space on the server.
How can I remedy this situation?
Buy a bigger disk. :-(
Seriously, this is an OS question, not a Mailman question.
--
Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers,
San Francisco Bay
One major error I see is that there is no more disk space on the server.
How can I remedy this situation?
Buy a bigger disk. :-(
Seriously, this is an OS question, not a Mailman question.
--
Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers,
San Francisco Bay Area,
One major error I see is that there is no more disk space on the server.
How can I remedy this situation?
Buy a bigger disk. :-(
Seriously, this is an OS question, not a Mailman question.
--
Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers,
San Francisco Bay Area,
Ki Song wrote:
The weird thing is that until this Friday, there was approximately 70-80%
free space on the 75GB partition.
I know this is not a mailman question, but how should I go about looking for
files that may have suddenly taken up all that disk space.
Tools like du and find with the
Ki Song wrote:
OK. What if I installed a second hard drive.
How easy is it to tell mailman and other programs to use the second hard
drive?
You'd have to copy the current partition to the new drive and then
umount the old partition and mount the new one.
Or, would it be easier/better to
The esteemed Ki Song has said:
One major error I see is that there is no more disk space on the server.
How can I remedy this situation?
Buy a bigger disk. :-(
Seriously, this is an OS question, not a Mailman question.
--
Mark Sapiro [EMAIL PROTECTED]The highway is
Hi Mark, I stoped the services and restored backup. I checked permssions and
started the services. After that the mailman doesn't restart, see logs:
Traceback (most recent call last): File '/usr/local/mailman/bin/mailmanctl',
line 548, in ?main() File '/usr/local/mailman/bin/mailmanctl',
Fabricio Oliveira wrote:
I stoped the services and restored backup. I checked permssions and
started the services. After that the mailman doesn't restart, see logs:
Traceback (most recent call last):
File '/usr/local/mailman/bin/mailmanctl', line 548, in ?
main()
File
: Re:
RE: [Mailman-Users] Bug in Mailman version 2.1.9 Fabricio Oliveira wrote:
Hi Mark,See attachment file with the log. Thank you for reposting
the logs as an attachment. That is much better. Here is your log data with
my comments interspersed. Log - /usr/local/mailman/logs/error
Fabricio Oliveira wrote:
Hi Mark,
I see your considerations about permissions, but I don't know are SELinux.
What is this?
SELinux is a security policy manager that can prevent file access based
on security policies even though the access would be allowed by file
permissions.
I stoped
Hi Mark, See attachment file with the log. Thanks. Regards,FabrÃcio Date: Sat,
8 Mar 2008 09:05:25 -0800 From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] CC:
mailman-users@python.org Subject: Re: [Mailman-Users] Bug in Mailman version
2.1.9 Fabricio Oliveira wrote: Hi,When I try access
Fabricio Oliveira wrote:
Hi Mark,
See attachment file with the log.
Thank you for reposting the logs as an attachment. That is much better.
Here is your log data with my comments interspersed.
Log - /usr/local/mailman/logs/error
Mar 08 10:48:37 2008 qrunner(1656): Traceback (most
Hi,
When I try access the page of Mailman appear the error bellow:
Bug in Mailman version 2.1.9
We're sorry, we hit a bug!Please inform the webmaster for this site of this
problem. Printing of traceback and other system information has been explicitly
inhibited, but the webmaster can find
Fabricio Oliveira wrote:
Hi,
When I try access the page of Mailman appear the error bellow:
Bug in Mailman version 2.1.9
We're sorry, we hit a bug!Please inform the webmaster for this site of this
problem. Printing of traceback and other system information has been
explicitly
Moving to -developers, reply-to set. Please keep Henrik in the loop.
Seems to be the same as
http://sourceforge.net/tracker/index.php?func=detailaid=1186819group_id=103atid=100103
Henrik Rasmussen writes:
Stephen J. Turnbull wrote:
Henrik Rasmussen writes:
Of course it's possible that
Myron Kowalski wrote:
I have no bin/delete. I'm guessing you meant bin/discard.
Yes. My Bad. I meant bin/discard.
--
Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
Myron Kowalski wrote:
I got rid of all the heldmsg w/o any problems, until I got to the one
in question.
Discarding that heldmsg returned this error.
mailman:~/data% ../bin/discard heldmsg-net-avengers-3.pck
Traceback (most recent call last):
File ../bin/discard, line 120, in ?
main()
One of my users sent me this message that he got when he tried to
approve a message to
his list. As far as I can tell, all my other lists, including his, are
working well. Any help on
what I should be looking for?
Bug in Mailman version 2.1.4
We're sorry, we hit a bug!
If you would like
Myron Kowalski wrote:
One of my users sent me this message that he got when he tried to
approve a message to
his list. As far as I can tell, all my other lists, including his, are
working well. Any help on
what I should be looking for?
Bug in Mailman version 2.1.4
We're sorry, we hit a
On Feb 13, 2008, at 12:03 PM, Mark Sapiro wrote:
Myron Kowalski wrote:
One of my users sent me this message that he got when he tried to
approve a message to
his list. As far as I can tell, all my other lists, including his,
are
working well. Any help on
what I should be looking for?
On Feb 13, 2008, at 1:06 PM, Myron Kowalski wrote:
On Feb 13, 2008, at 12:45 PM, Myron Kowalski wrote:
On Feb 13, 2008, at 12:03 PM, Mark Sapiro wrote:
Myron Kowalski wrote:
One of my users sent me this message that he got when he tried to
approve a message to
his list. As far as I can
On Feb 13, 2008, at 12:45 PM, Myron Kowalski wrote:
On Feb 13, 2008, at 12:03 PM, Mark Sapiro wrote:
Myron Kowalski wrote:
One of my users sent me this message that he got when he tried to
approve a message to
his list. As far as I can tell, all my other lists, including his,
are
working
hi,
when users try to subscribe via the list-info-page
http://listen.esel.at/mailman/listinfo/liste
they get:
Bug in Mailman version 2.1.9. We're sorry, we hit a bug! (...)
The error only occurs when the subscribe policy is set to confirm.
as a workaround i have now changed it to confirm and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Maulwurf wrote:
when users try to subscribe via the list-info-page
http://listen.esel.at/mailman/listinfo/liste
they get:
Bug in Mailman version 2.1.9. We're sorry, we hit a bug! (...)
The error only occurs when the subscribe policy is set
Help...
When I try http://ml.inters.ru/mailman/admin (and others)
I see the text:
--
Bug in Mailman version 2.1.9
We're sorry, we hit a bug! etc.
the traceback is below..
help!
Geo wrote:
When I try http://ml.inters.ru/mailman/admin (and others)
I see the text:
--
Bug in Mailman version 2.1.9
We're sorry, we hit a bug! etc.
the traceback is below..
Wrong traceback! The traceback below is from
iMug wrote:
I have created four Mailman mailing lists associated with my organization's
domain name through our web-hosting provider's cPanel (ie I do not have root
access to the server to try to fix problems).
See
http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq06.011.htp.
One of
I have created four Mailman mailing lists associated with my organization's
domain name through our web-hosting provider's cPanel (ie I do not have root
access to the server to try to fix problems). One of these lists returns a
Bug in Mailman version 2.1.9.cp1 error message page anytime a
Hi guys, sorry for my bad english, i'm french.
I haven't found any website or mailing-list that can help me for this problem.
It was any days ago, i want to install postfix, and it runs really, i want to
put a mailing-list system, it's ok, but i want to add virtual users to postfix,
and it's ok
xaf wrote:
My main.cf :
-
snip
alias_maps = hash:/var/lib/mailman/data/aliases, hash:/etc/aliases
This is correct, but what is in /var/lib/mailman/data/aliases and has
postalias run and created the corresponding
/var/lib/mailman/data/aliases.db file?
But now, i have another
Mark Sapiro schrieb:
Stefan Grote wrote:
okay, but my Mailman error log is empty and my apache logs are empty too.
This can happen for a few reasons, but the most likely is a syntax
error in mm_cfg.py.
i don't touch the config. its ah fresh install from a Debian packet...
any
Stefan Grote wrote:
Mark Sapiro schrieb:
Stefan Grote wrote:
okay, but my Mailman error log is empty and my apache logs are empty too.
This can happen for a few reasons, but the most likely is a syntax
error in mm_cfg.py.
i don't touch the config. its
Stefan Grote wrote:
i don't touch the config. its ah fresh install from a Debian packet...
any ideas anyway?
Try changing
STEALTH_MODE = 1
to
STEALTH_MODE = 0
in scripts/driver and see if that gets you a more informative message.
Also check the web server error log.
If you're still stuck,
Stefan Grote wrote:
okay, but my Mailman error log is empty and my apache logs are empty too.
This can happen for a few reasons, but the most likely is a syntax
error in mm_cfg.py.
--
Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers,
San Francisco Bay Area, Californiabetter
Hi All, apologies in advanced for the length of this post I have hit
a bug when clicking on the sender filter privacy option... Would
anyone be able to decipher the traceback and suggest what might be the
problem and/or where I may be able to resolve it.. (mailman v 2.1.5)
Thanks :)
Spyro
Tiffany Miller wrote:
So, I can't 'see' the mailman error logs or the file system. I can only view
the file manager through my FTP program or cpanel. I checked the error logs
for the site, but nothing shows from today.
And not sure if it helps, but when I try to edit *any* of the public html
Mailman version: 2.1.7.cp2
Operating System: Linux
Apache version 1.3.36 (unix)
I was trying to edit the welcome message subscribers receive upon confirming
subscription to a newsletter mailing list for my client.
I accessed the admin interface through cpanel and clicked on the link to edit
Tiffany Miller wrote:
Mailman version: 2.1.7.cp2
Operating System: Linux
Apache version 1.3.36 (unix)
See
http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq06.011.htp
I was trying to edit the welcome message subscribers receive upon confirming
subscription to a newsletter mailing list
-
From: Mark Sapiro
To: Tiffany Miller ; mailman-users@python.org
Sent: Wednesday, July 19, 2006 5:22 PM
Subject: Re: [Mailman-Users] Bug in Mailman version 2.1.7.cp2
Tiffany Miller wrote:
Mailman version: 2.1.7.cp2
Operating System: Linux
Apache version 1.3.36 (unix)
See
http
Hello all,
We have mailman installed in our machine and that has been working
fine. Recently there was a post in our list regarding a certain topic
and what seemed interesting to me is that the mail was dated 16th July
18:34:39 hrs, on the daily digest while on the archives it appeared on
the 17th
Prasanta Baruah wrote:
We have mailman installed in our machine and that has been working
fine. Recently there was a post in our list regarding a certain topic
and what seemed interesting to me is that the mail was dated 16th July
18:34:39 hrs, on the daily digest while on the archives it
On 6/13/06, Bob Bergey [EMAIL PROTECTED] wrote:
At 11:57 AM -0500 on 6/13/06, Patrick Bogen wrote:
http://rentzsch.com/macosx/mailmanWorkaround
Wow -- that's exactly my problem! Thanks for the tip -- I'll try it
later today.
Let us know how it goes.
I'm a little scared to upgrade -- still
I have more than a dozen lists running in Mailman 2.1.4 on my Xserve,
all running fine, except that now on just one list I'm unable to
access the admin pages. The list is still sending messages okay,
individual subscribers can access their subscription options,
archives are fine, etc. -- but I
Bob Bergey wrote:
I have more than a dozen lists running in Mailman 2.1.4 on my Xserve,
all running fine, except that now on just one list I'm unable to
access the admin pages. The list is still sending messages okay,
individual subscribers can access their subscription options,
archives are
On Wed, 11 Jan 2006, Tokio Kikuchi wrote:
Sorry for the inconvenience but I've put a new bug in the code while tighten
up the security of the script. Work around is to put a line
import re
in the top part of the Mailman/Cgi/edithtml.py.
The bug was reported in
1 - 100 of 259 matches
Mail list logo
