Re: [Mailman-Users] Bug in Mailman version 2.1.23

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 h

Re: [Mailman-Users] bug

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 system

Re: [Mailman-Users] Bug in Mailman version 2.1.25

: 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: > > E

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: Either run Mailman's bin/rmlist myproblemlist or just rm -r /usr/local/mailman/lists/myproblemlist/ These will do the same thing which is remov

Re: [Mailman-Users] Bug in Mailman version 2.1.25

On 14 April 2018 at 15:33, MPN Kazishe wrote: > > -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.or

Re: [Mailman-Users] Bug in Mailman version 2.1.25

> -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

Re: [Mailman-Users] Bug in Mailman version 2.1.25

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 my

Re: [Mailman-Users] Bug in Mailman version 2.1.23

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 ve

Re: [Mailman-Users] Bug in Mailman version 2.1.15

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 t

Re: [Mailman-Users] Bug in Mailman version 2.1.15

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 --] admin(17943

Re: [Mailman-Users] Bug in Mailman version 2.1.15

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 m

Re: [Mailman-Users] Bug in SUBSCRIBE_FORM_SECRET feature?

--On 18. Dezember 2013 07:04:14 -0800 Mark Sapiro 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 seemed well, but t

Re: [Mailman-Users] Bug in SUBSCRIBE_FORM_SECRET feature?

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 som

Re: [Mailman-Users] Bug in 2.1.16rc2 regarding new logging to vette?

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:

Re: [Mailman-Users] Bug in mailman2.1.0

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

Re: [Mailman-Users] Bug in mailman2.1.0

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 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 v

Re: [Mailman-Users] Bug in Mailman version 2.1.9

Fletcher Cocquyt 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 /var/

Re: [Mailman-Users] Bug in Mailman version 2.1.9

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 --

Re: [Mailman-Users] bug adding user, and archiving gets "shunted"

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 . > >I read the FAQ, which was however last update

Re: [Mailman-Users] bug adding user, and archiving gets "shunted"

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 . I read the FAQ, which was however last updated in 2009. This MIGHT not be a pro

Re: [Mailman-Users] bug adding user, and archiving gets "shunted"

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 olde

Re: [Mailman-Users] bug adding user, and archiving gets "shunted"

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. P

Re: [Mailman-Users] bug adding user, and archiving gets "shunted"

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 archi

Re: [Mailman-Users] Bug: couldn't subscribe to dev list bysimplyreplying

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+@... with Subject: >> Your confirmation is required to join the listname mailing list, and >> the reply is to listna

Re: [Mailman-Users] Bug: couldn't subscribe to dev list by simplyreplying

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 , and the reply is to the listname-requ...@... address with the confirm command possi

Re: [Mailman-Users] Bug: couldn't subscribe to dev list by simplyreplying

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 >con

Re: [Mailman-Users] bug error when subscribing through web after Mailman 2.1.12 upgrade

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

Re: [Mailman-Users] bug error when subscribing through webafterMailman 2.1.12 upgrade

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 should

Re: [Mailman-Users] bug error when subscribing through webafterMailman 2.1.12 upgrade

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 wo

Re: [Mailman-Users] bug error when subscribing through web afterMailman 2.1.12 upgrade

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 problem

Re: [Mailman-Users] bug error when subscribing through web afterMailman 2.1.12 upgrade

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: > >adm

Re: [Mailman-Users] Bug in Mailman error on 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 pag

Re: [Mailman-Users] Bug in Mailman error on ListInfo Page

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 pa

Re: [Mailman-Users] bug

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 th

Re: [Mailman-Users] Bug reported when creating a new list from webpage

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 f

Re: [Mailman-Users] Bug reported when creating a new list from webpage

- 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

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 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

Re: [Mailman-Users] Bug in Mailman version 2.1.8

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]>

Re: [Mailman-Users] Bug in Mailman version 2.1.8

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

Re: [Mailman-Users] Bug in Mailman version 2.1.8

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

Re: [Mailman-Users] Bug in Mailman version 2.1.8

>>> 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, >>

Re: [Mailman-Users] Bug in Mailman version 2.1.8

>> >> 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 Fra

Re: [Mailman-Users] Bug in Mailman version 2.1.8

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 Ba

Re: [Mailman-Users] Bug in Mailman version 2.1.9

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: [Mailman-Users] Bug in Mailman version 2.1.9

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',

Re: [Mailman-Users] Bug in Mailman version 2.1.9

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 st

Re: [Mailman-Users] Bug in Mailman version 2.1.9

-users@python.org> Subject: 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

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 > > Mar 08 10:48:37 2008 qrunner(1656): Traceback (mo

Re: [Mailman-Users] Bug in Mailman version 2.1.9

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:

Re: [Mailman-Users] Bug in Mailman version 2.1.9

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

Re: [Mailman-Users] bug in Mailman 2.1.4

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 ? >

Re: [Mailman-Users] bug in Mailman 2.1.4

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 ---

Re: [Mailman-Users] bug in Mailman 2.1.4

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

Re: [Mailman-Users] bug in Mailman 2.1.4

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,

Re: [Mailman-Users] bug in Mailman 2.1.4

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 lo

Re: [Mailman-Users] bug in Mailman 2.1.4

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, w

Re: [Mailman-Users] bug when subscribing via web

-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 poli

Re: [Mailman-Users] bug in mailman2.1.9

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

Re: [Mailman-Users] Bug in the public HTML pages

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 . >One

Re: [Mailman-Users] Bug with Postfix + MySQL + Mailman

Hello ! I have found the problem, my mailserver was really configured correctly, but, and it isn't in any manual, I must add "local_recipient_maps" value ... Now it's ok ! Thank you for your answer Have a nice day ;) XaF [http://www.sbird.info/] --

Re: [Mailman-Users] Bug with Postfix + MySQL + Mailman

xaf wrote: > >My main.cf : >- >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 e

Re: [Mailman-Users] Bug in Mailman version 2.1.5

Stefan Grote wrote: >another question..what is about the mailinglist mail adress? my mailman >sends me a message. but the mail adress of my ml doesn't exits. >must i add the adress per hand? You must inform your MTA how to deliver to Mailman lists. How to do this depends on the MTA. It may be d

Re: [Mailman-Users] Bug in Mailman version 2.1.5

Hi Mark, Mark Sapiro schrieb: >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 > > thanks a lot! it works. The rights of the log file was wrong. I don

Re: [Mailman-Users] Bug in Mailman version 2.1.5

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,

Re: [Mailman-Users] Bug in Mailman version 2.1.5

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. >> >> >> >>

Re: [Mailman-Users] Bug in Mailman version 2.1.5

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 pa

Re: [Mailman-Users] Bug in Mailman version 2.1.5

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, Californiabet

Re: [Mailman-Users] Bug in Mailman version 2.1.7.cp2

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 ht

Re: [Mailman-Users] Bug in Mailman version 2.1.7.cp2

agle-designs.com - Original Message - 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: L

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 >I was trying to edit the welcome message subscribers receive upon confirming >subscription to a newsletter maili

Re: [Mailman-Users] Bug or

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 appe

Re: [Mailman-Users] Bug in Mailman 2.1.4

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 -

Re: [Mailman-Users] Bug in Mailman 2.1.4

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

Re: [Mailman-Users] Bug in 2.1.7, can't edit Public HTML pages & text files

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 > http://sourcefo

Re: [Mailman-Users] Bug in 2.1.7, can't edit Public HTML pages & text files

Christopher X. Candreva wrote: > Mailman is telling me there is a bug whenever I try to submit a page from > the "Edit the public HTML pages and text files" menu. The page returned > says: > > Bug in Mailman version 2.1.7 > > We're sorry, we hit a bug! > > Please inform the webmaster for this

Re: [Mailman-Users] Bug when editing Mailman html pages

PeteBell wrote: >I have just tried to edit the user-editable html pages (subscribe, >option results, list-info, and the 'welcome to new subscriber' text >message), but I get the following message... > > >Bug in Mailman version 2.1.6 >We're sorry, we hit a bug! >Please inform the webmaster for

Re: [Mailman-Users] Bug in Mailman

plaza c schrieb: > 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. You should look for that information. > Is this error of post

Re: [Mailman-Users] Bug report: hanging message (shunting)

At 10:51 PM +0200 2005-08-10, Loek Jehee wrote: > I consider this a bug in MailMan which I would like to inform you of. You need to file a report on the SourceForge Mailman Bugs page at , if you want it to get into the system an

Re: [Mailman-Users] Bug in Mailman???

David Andrews wrote: >When I, or any of my users go to: > >http://www.mydomain.org/mailman/listinfo > >the following page comes up? Any thoughts or suggestions? Thanks!\ > > >Bug in Mailman version 2.1.5 > >We're sorry, we hit a bug! > >If you would like to help us identify the problem, please

Re: [Mailman-Users] Bug in Mailman 2.1.6b4

BTW, I found the changes to ListAdmin.py from: http://www.mail-archive.com/mailman-coders@python.org/msg00255.html Darren On Mon, 2005-07-11 at 13:22, Darren G Pifer wrote: > Hello, > > Today, after doing some checking on the user's list, I > found the errors associated with "There is a b

Re: [Mailman-Users] Bug in Mailman 2.1.6b4

I hate answering my question but I found this info from a google search. Has anyone else modified ListAdmin.py with these changes?: http://list.iskon.hr/~jelly/mailman-2.1.5-_UpdateRequests.diff Does this look reasonable? Darren Pifer Old Dominion University On Mon, 2005-07-11 at 13:22, Darren

Re: [Mailman-Users] Bug in Mailman 2.1.6b4

Hello, Today, after doing some checking on the user's list, I found the errors associated with "There is a bug in 2.1.6b4". in mailman's error log which I reported to this list a week ago. I don't know why I did not see it earlier. Here is a portion of the trace in the error log: Jul 07 09

Re: [Mailman-Users] Bug in Mailman 2.1.6b4

On Fri, 2005-07-08 at 12:08 -0400, Darren G Pifer wrote: > Thanks for the information. You are correct, I have not seen > anything in the Apache logs, however, I have not seen anything > logged to mailman's logs either. > > Is there a way to disable stealth mode? I know this could cause > security

Re: [Mailman-Users] Bug in Mailman 2.1.6b4

Thanks for the information. You are correct, I have not seen anything in the Apache logs, however, I have not seen anything logged to mailman's logs either. Is there a way to disable stealth mode? I know this could cause security implications but may need to do this temporarily to find and fix the

Re: [Mailman-Users] Bug in Mailman 2.1.6b4

On Fri, 2005-07-08 at 11:54 +0900, Jim Tittsler wrote: > On Jul 8, 2005, at 04:59, Darren G Pifer wrote: > > [...] from a version of Mailman we upgraded to recently. I tried to > > look > > in the logs but could not find anything. We will be upgrading > > Did you look in your Apache error logs?

Re: [Mailman-Users] Bug in Mailman 2.1.6b4

On Jul 8, 2005, at 04:59, Darren G Pifer wrote: > [...] from a version of Mailman we upgraded to recently. I tried to > look > in the logs but could not find anything. We will be upgrading Did you look in your Apache error logs? There may be a Python traceback there that would narrow down the

Re: [Mailman-Users] Bug on Version 2.1.5

SER.RI-TIC - Jordi Tomàs Boqué wrote: > >today we found this Bug. Version of Mailman is 2.1.5. Maybe new version >solve problem ? > >thanks. > >- >Jun 14 11:38:54 2005 admin(1293): > >admin(1293): [- Mailman Version: 2.1.5 -] >admin(1293): [--

Re: [Mailman-Users] Bug report

PeteBell wrote: > >I have just gone live with my email list, and this is the first time >anyone has reported a problem to me, so here it is for your comments. >(First let me remind you that I do *not* have access to the Mailman >installation, and I do *NOT* speak Python - apart from the "Mont

Re: [Mailman-Users] bug in mailman 2.1.5, please help

Alias Mohd FKE wrote: > >Bug in Mailman version 2.1.5 > >We're sorry, we hit a bug! > >If you would like to help us identify the problem, please email a copy of this >page to the webmaster for this site with a description of what happened. >Thanks! > >Traceback: > > >Traceback (most recent call l

Re: [Mailman-Users] bug in mailman 2.1.5, please help

Sometime on Tue, May 17, 2005 at 05:37:33PM +0800, Alias Mohd FKE said: > > Bug in Mailman version 2.1.5 > > We're sorry, we hit a bug! > > If you would like to help us identify the problem, please email a copy of > this page to the webmaster for this site with a description of what happened.

RE: [Mailman-Users] Bug Help

On Wed, 2005-04-27 at 11:38 -0400, Loomis, Todd, CTR, DMSO wrote: > No actually I get the following: > > Traceback (innermost last): > File "", line 1, in ? > KeyError: getpwnam(): name not found Since the command "id" can lookup up the mailman password info we know it's defined in the system a

RE: [Mailman-Users] Bug Help

Todd, CTR, DMSO Cc: mailman-users@python.org Subject: RE: [Mailman-Users] Bug Help On Wed, 2005-04-27 at 11:06 -0400, Loomis, Todd, CTR, DMSO wrote: > Yes I get > uid=41(mailman) gid=41(mailman) groups=41(mailman) Then this command: python -c "import pwd; print pwd.getpwnam('mail

RE: [Mailman-Users] Bug Help

On Wed, 2005-04-27 at 11:06 -0400, Loomis, Todd, CTR, DMSO wrote: > Yes I get > uid=41(mailman) gid=41(mailman) groups=41(mailman) Then this command: python -c "import pwd; print pwd.getpwnam('mailman')[2]" should print 41, if it doesn't then I'm at a loss other than you might have python proble

RE: [Mailman-Users] Bug Help

Yes I get uid=41(mailman) gid=41(mailman) groups=41(mailman) -Original Message- From: John Dennis [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 27, 2005 10:53 AM To: Loomis, Todd, CTR, DMSO Cc: mailman-users@python.org Subject: Re: [Mailman-Users] Bug Help On Wed, 2005-04-27 at 08

Re: [Mailman-Users] Bug Help

On Wed, 2005-04-27 at 08:19 -0400, Loomis, Todd, CTR, DMSO wrote: > I getting this error can anyone help? Mailman version 2.0.13 > File "../Mailman/mm_cfg.py", line 50, in ? > MAILMAN_UID = pwd.getpwnam('mailman')[2] > KeyError: getpwnam(): name not found Did you create the user account "mailman"

Re: [Mailman-Users] Bug in Mailman version 2.1.4

Camila Canto wrote: > >This bug appear when I try to use the tool listinfo in Mailman. >What can I do? >Thanks > >Camila Canto > ><> > >*Bug in Mailman version 2.1.4*<> > > > We're sorry, we

Re: [Mailman-Users] bug in mailman

i had runned bin/check_perms -f , but nothing changed. now i have removed whole mailman, and i will try to install it with sources. thanks for your helps. On Thu, 17 Feb 2005 22:56:55 +0100, Brad Knowles <[EMAIL PROTECTED]> wrote: > At 11:01 PM +0200 2005-02-15, H. Kerem Cevahir wrote: > > >

Re: [Mailman-Users] bug in mailman

At 11:01 PM +0200 2005-02-15, H. Kerem Cevahir wrote: File "/usr/lib/mailman/Mailman/Archiver/Archiver.py", line 95, in InitVars os.mkdir(self.archive_dir()+'.mbox', 02775) OSError: [Errno 13] Permission denied: '/var/lib/mailman/archives/private/deneme.mbox' You've got a permissions pro

Re: [Mailman-Users] bug in mailman

You've probably hit a bug in the SELinux policy, it was fixed in selinux-policy-targeted-1.17.30-2.80. Therefore you can either update your selinux-policy-targeted rpm to the latest version or disable SELinux with system-config-security level. -- John Dennis <[EMAIL PROTECTED]> -

Re: [Mailman-Users] bug in Mailman when accessing Private Archives

On Feb 17, 2005, at 9:03 AM, Steve Burling wrote: What the heck were they thinking when the designers of Python chose "amount of leading white space" to indicate block structure? It seems absolutely guaranteed to cause problems such as this. it's one of those things about python that you either

  1   2   >