[Mailman-Users] Errors with new version

Hi, we seem to have new entries in the error log. I believe they have only started to appear with the recent updates, but I cannot swear to that: admin(7095): [- Mailman Version: 2.1.33 -] admin(7095): [- Traceback --] admin(7095): Traceback (most recent call last): admin(7095):

Re: [Mailman-Users] Errors while sending mail: centos + mailman + postfix

On 08/09/2017 10:17 AM, Dr. Alberto Barengols wrote: > > I had create a list ( c...@listas.pccorreo.com.ar ), and everything > went right. > > But when I send a message to this list it appears some errors: > > == > : Comman

[Mailman-Users] Errors while sending mail: centos + mailman + postfix

Hello everybody! I just installed Mailman version: 2.1.15 in a Centos server running Postfix 2,11,3 I had create a list ( c...@listas.pccorreo.com.ar ), and everything went right. But when I send a message to this list it appears some errors:

Re: [Mailman-Users] errors

christian stalberg wrote: >Ok I created the locks directory but now I am getting this error: > >Feb 17 17:16:01 2012 post(19147): Traceback (most recent call last): >post(19147): File "/usr/lib/mailman/scripts/post", line 69, in >post(19147): main() >post(19147): File "/usr/lib/mailman/s

Re: [Mailman-Users] errors

'/var/spool/mailman/in/1329516961.022899+e4ad547ef709f92bc2c43e86b88543fd2b8 7d705.pck.tmp' -Original Message- From: Mark Sapiro [mailto:m...@msapiro.net] Sent: Friday, February 17, 2012 4:47 PM To: christian stalberg; mailman-users@python.org Subject: Re: [Mailman-Users] errors christian stalberg wrote:

Re: [Mailman-Users] errors

christian stalberg wrote: >Moved list to another server. What is the problem here? > ># bin/withlist -l -r fix_url listname -v -u domainname.com >Importing fix_url... >Running fix_url.fix_url()... >Loading list stoptortureflights (locked) >Traceback (most recent call last): > File "bin/withlist",

[Mailman-Users] errors

Moved list to another server. What is the problem here? # bin/withlist -l -r fix_url listname -v -u domainname.com Importing fix_url... Running fix_url.fix_url()... Loading list stoptortureflights (locked) Traceback (most recent call last): File "bin/withlist", line 302, in main() File "b

Re: [Mailman-Users] Errors on mailman startup

* Malveeka Tewari : > I installed mailman on localhost using the following instructions on > http://systers.org/systers-soc/doku.php/step_by_step_system_installation_-_production > > But on starting mailman I get an error: > Site-list is missing: mailman-admin > > Can anyone help me here? Creat

Re: [Mailman-Users] Errors on mailman startup

Hi I installed mailman on localhost using the following instructions on http://systers.org/systers-soc/doku.php/step_by_step_system_installation_-_production But on starting mailman I get an error: Site-list is missing: mailman-admin Can anyone help me here? Thanks Malveeka On Fri, May 29, 200

Re: [Mailman-Users] Errors on mailman startup

Dave Filchak wrote: >> >OK .. ran both tests as mailman. First one was fine. Second one, while >it shown no errors initially, I only received the email that was sent as >a rcpt (secondary email address). The To: email address did not get >delivered. The smtp-failure logs do not show a specifi

Re: [Mailman-Users] Errors on mailman startup

Mark Sapiro wrote: Dave Filchak wrote: Mark Sapiro wrote: Did you actually do the test described in the post at (linked from the FAQ) as the Mailman user? Yes. This test was fine. Did you actually tr

Re: [Mailman-Users] Errors on mailman startup

Dave Filchak wrote: >Mark Sapiro wrote: >> >> Did you actually do the test described in the post at >> >> (linked from the FAQ) as the Mailman user? >> >Yes. This test was fine. >> Did you actually try to send mail as describ

Re: [Mailman-Users] Errors on mailman startup

Mark Sapiro wrote: Dave Filchak wrote: Well .. I have ran through most of the FAQs and the debugging techniques listed in them and all SEEMS like it is functioning correctly. I have also upgraded Mailman to 2.1.8 from 2.1.6 and I still have the exact same problem. After upgrading, I didn't

Re: [Mailman-Users] Errors on mailman startup

Dave Filchak wrote: >Well .. I have ran through most of the FAQs and the debugging techniques >listed in them and all SEEMS like it is functioning correctly. I have >also upgraded Mailman to 2.1.8 from 2.1.6 and I still have the exact >same problem. After upgrading, I didn't run the debugging s

Re: [Mailman-Users] Errors on mailman startup

Well .. I have ran through most of the FAQs and the debugging techniques listed in them and all SEEMS like it is functioning correctly. I have also upgraded Mailman to 2.1.8 from 2.1.6 and I still have the exact same problem. After upgrading, I didn't run the debugging stuff again so I will try

Re: [Mailman-Users] Errors on mailman startup

Dave Filchak wrote: > >I have found the following in the smtp-failure logs: > >failed with code -1: (-2, 'Name or service not known') > >I have tons of these. I Googled this and one of the issues appears to be >not having search my.domain in my resolv.conf file. I have added this >but I still c

Re: [Mailman-Users] Errors on mailman startup

Mark Sapiro wrote: Dave Filchak wrote: My ISP had a major power outage a while back and I realized that mailman was no longer running. When trying to start it again, I am getting the following errors: /usr/local/mailman/bin/mailmanctl start Starting Mailman's master qrunner. [r...@ebony ~

Re: [Mailman-Users] Errors on mailman startup

Mark Sapiro wrote: Dave Filchak wrote: My ISP had a major power outage a while back and I realized that mailman was no longer running. When trying to start it again, I am getting the following errors: /usr/local/mailman/bin/mailmanctl start Starting Mailman's master qrunner. [r...@ebony ~

Re: [Mailman-Users] Errors on mailman startup

Dave Filchak wrote: >My ISP had a major power outage a while back and I realized that mailman >was no longer running. When trying to start it again, I am getting the >following errors: > >/usr/local/mailman/bin/mailmanctl start >Starting Mailman's master qrunner. >[r...@ebony ~]# Traceback (most

[Mailman-Users] Errors on mailman startup

My ISP had a major power outage a while back and I realized that mailman was no longer running. When trying to start it again, I am getting the following errors: /usr/local/mailman/bin/mailmanctl start Starting Mailman's master qrunner. [r...@ebony ~]# Traceback (most recent call last): File "

Re: [Mailman-Users] errors after hd crash

Zbigniew Szalbot wrote: > >We have had a HD crash and I had to bring the data back from a backup. I >fixed permissions, etc and it should work well now but on the website I get >Bug in Mailman version 2.1.10 > >We're sorry, we hit a bug! > >Please inform the webmaster for this site of this problem

[Mailman-Users] errors after hd crash

Hello, We have had a HD crash and I had to bring the data back from a backup. I fixed permissions, etc and it should work well now but on the website I get 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 tracebac

Re: [Mailman-Users] Errors after upgrade via up2date to 2.1.5

Hmm, well, after going through the FAQ, I think its working again, for some reason restarting it with mailmanctl instead of service mailman restart seems to have done the trick. At least I think thats what fixed it, I could be wrong about that. Thanks for your help Mark! Scott On 6/17/06, M

Re: [Mailman-Users] Errors after upgrade via up2date to 2.1.5

Mark Sapiro wrote: > >Also, as I look more closely at the original traceback, it is unusual >in that entries usually only have the pid and yours say 'mailowner >(pid)', and I don't know what 'mailowner' is. > >What do your sendmail aliases for Mailman look like? Normally, they all >pipe to /var/mai

Re: [Mailman-Users] Errors after upgrade via up2date to 2.1.5

Scott Thomson wrote: > >This is the bounce message we're getting by the way: > >The following recipient(s) could not be reached: > > [EMAIL PROTECTED] on 6/16/2006 5:28 PM >The e-mail system was unable to deliver the message, but did not >report a specific reason. Check the addres

Re: [Mailman-Users] Errors after upgrade via up2date to 2.1.5

On 6/17/06, Mark Sapiro <[EMAIL PROTECTED]> wrote: > > Scott Thomson wrote: > > > >Thanks for the ideas, now I feel like I'm getting closer to the issue. > > > >check_perms came up clean, all the files in the in dir match these > >permissions. > > > >2302ff99d3a89dc936c9e66497cb08201f0.pck > >-rw-r

Re: [Mailman-Users] Errors after upgrade via up2date to 2.1.5

Scott Thomson wrote: > >Thanks for the ideas, now I feel like I'm getting closer to the issue. > >check_perms came up clean, all the files in the in dir match these >permissions. > >2302ff99d3a89dc936c9e66497cb08201f0.pck >-rw-rw1 mail mailman 10043 Jun 17 14:08 >1150567685.345078+9

Re: [Mailman-Users] Errors after upgrade via up2date to 2.1.5

Scott Thomson wrote: >So I upgraded mailman and sendmail yesterday, I'm running RHEL3 on a machine >out at serverbeach. The latest mailman is 2.1.5 via Red Hat Network. > >Now that I've upgraded to the latest versions of both available via up2date, >I'm getting errors when sending to a list. > >T

[Mailman-Users] Errors after upgrade via up2date to 2.1.5

So I upgraded mailman and sendmail yesterday, I'm running RHEL3 on a machine out at serverbeach. The latest mailman is 2.1.5 via Red Hat Network. Now that I've upgraded to the latest versions of both available via up2date, I'm getting errors when sending to a list. This is what is in my /error l

Re: [Mailman-Users] errors after applying virtualhost patches to 2.1.7

Bretton Vine wrote: >After applying the following two patches to the mailman source, >compiling and installing on Debian unstable I get the attached errors in >my logfiles. Can anyone explain specifically what's going wrong? >(The lists do still work though) But do messages get archived? >Fil

Re: [Mailman-Users] errors after applying virtualhost patches to 2.1.7

Bretton Vine said the following on 2006/03/20 07:19 PM: > After applying the following two patches to the mailman source, > compiling and installing on Debian unstable I get the attached errors in > my logfiles. Apologies, forgot to add which patches I applied: [1] http://nix.lauft.net/mailman/m

[Mailman-Users] errors after applying virtualhost patches to 2.1.7

After applying the following two patches to the mailman source, compiling and installing on Debian unstable I get the attached errors in my logfiles. Can anyone explain specifically what's going wrong? (The lists do still work though) ---

Re: [Mailman-Users] Errors with fcron jobs

Hugo Villeneuve <[EMAIL PROTECTED]> wrote: > Thanks Mark, > Adding SHELL = /bin/sh to my mailman crontab solved my problem. I think > it would be a good idea to add a note to the Mailman installation manual for > people using fcron instead of cron. I have attached my complete crontab as a

Re: [Mailman-Users] Errors with fcron jobs

Mark Sapiro <[EMAIL PROTECTED]> wrote: > Well, I don't use fcron so I don't know for sure, but looking at the > various manpages leads me to think that the shell= setting in the > fcron config file is only a default if the shell is not otherwise > specified. > > man 5 fcrontab > > says > > Whe

Re: [Mailman-Users] Errors with fcron jobs

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hugo Villeneuve wrote: > On Sun, 18 Dec 2005 14:15:46 -0800 > Mark Sapiro <[EMAIL PROTECTED]> wrote: >> fcron by default runs commands using the user's login shell from >> /etc/passwd. Thus you have to either specify a valid shell in >> /etc/passwd or

Re: [Mailman-Users] Errors with fcron jobs

Hugo Villeneuve wrote: > >In the fcron configuration file, I have already this line for the shell: > shell = /bin/sh Well, I don't use fcron so I don't know for sure, but looking at the various manpages leads me to think that the shell= setting in the fcron config file is only a default if th

Re: [Mailman-Users] Errors with fcron jobs

On Sun, 18 Dec 2005 14:15:46 -0800 Mark Sapiro <[EMAIL PROTECTED]> wrote: > Hugo Villeneuve wrote: > > > > I'm using fcron to schedule the mailman jobs. I configured fcron to run > > the mailman jobs as the mailman user (fcrontab -u mailman...). I also > > created the mailman user with no lo

Re: [Mailman-Users] Errors with fcron jobs

Hugo Villeneuve wrote: > > I'm using fcron to schedule the mailman jobs. I configured fcron to run > the mailman jobs as the mailman user (fcrontab -u mailman...). I also created > the mailman user with no login shell (/bin/false), similar to what is > suggested in the mailman installation

[Mailman-Users] Errors with fcron jobs

Hi, I'm using fcron to schedule the mailman jobs. I configured fcron to run the mailman jobs as the mailman user (fcrontab -u mailman...). I also created the mailman user with no login shell (/bin/false), similar to what is suggested in the mailman installation manual. When the

Re: [Mailman-Users] Errors in Mailman

Terry Allen <[EMAIL PROTECTED]> wrote: 1 - If I make a change to mm_cfg.py, to refresh the config, is it sufficient to from the command line simply run bin/mailmanctl reload bin/mailmanctl restart (not reload) 2 - In my Postfix logs, this appeared - fatal: open /usr/local/mailman/data/aliases.db:

Re: [Mailman-Users] Errors in Mailman

Terry Allen <[EMAIL PROTECTED]> wrote: > >1 - If I make a change to mm_cfg.py, to refresh the config, is it >sufficient to from the command line simply run bin/mailmanctl reload bin/mailmanctl restart (not reload) >2 - In my Postfix logs, this appeared - fatal: open >/usr/local/mailman/data/

[Mailman-Users] Errors in Mailman

Hi again, I have Mailman best part running, but there are a few odd errors & I have a few short questions relating to those if someone wouldn't mind replying to them. 1 - If I make a change to mm_cfg.py, to refresh the config, is it sufficient to from the command line simply run bin/mailmanctl

Re: [Mailman-Users] Errors During Make-Install

Richard, Thank you for responding and the tip. I had suspected python. Here's what I get: isl{root}250: python Python 2.3.3 (#1, Sep 10 2004, 10:20:22) [GCC 3.2.3] on sunos5 Type "help", "copyright", "credits" or "license" for more information. >>> import socket Traceb

Re: [Mailman-Users] Errors During Make-Install

You probably have a problem with your Python installation. _socket is part of the standard Python library providing support for the UNIX/BSD socket interface. Unless and until you can run python from the command line and enter the command "import socket" without getting an exception raised then

[Mailman-Users] Errors During Make-Install

Hello, I am trying to install and run Mailman on Solaris 2.7 or SunOS 5.7 and I'm getting the following fatal when running 'make install': Traceback (most recent call last): File "bin/update", line 50, in ? from Mailman import Utils File "/usr/local/mailman/Mailman/Util

[Mailman-Users] Errors after upgrade 2.1.2 -> 2.1.5

I did an upgrade from 2.1.2 to 2.1.5 and started seeing the errors like the one quoted below. It's always in "dequeue" but sometimes from various queues under qfiles. The installation used T. Kikuchi's patch to CookHeaders but was not in any other way unusual. The only other special circumstance

Re: [Mailman-Users] Errors running check_db

At 1:48 AM -0400 2004/05/30, Bruce Embrey wrote: When running check_db -av I get an error on some lists "[Errno 2] No such file or directory: '/var/mailman/lists/listname/config.db.last'. Some of my lists have a number of files in their directories and some have only two (config.pck and config.

[Mailman-Users] Errors running check_db

Mailman Users: When running check_db -av I get an error on some lists "[Errno 2] No such file or directory: '/var/mailman/lists/listname/config.db.last'. Some of my lists have a number of files in their directories and some have only two (config.pck and config.pck.last). Is this a problem and w

Re: [Mailman-Users] Errors

On 26 May 2004, at 22:57, Mark Smith wrote: Hi, I don't understand this message. - The following addresses had permanent fatal errors - "|/home/mailman/mail/wrapper post mug" (expanded from: <[EMAIL PROTECTED]>) - Transcript of session follows - Mailman error: post got bad listname

Re: [Mailman-Users] Errors

al Message - From: "Mark Smith" <[EMAIL PROTECTED]> To: "Andreas Sheriff" <[EMAIL PROTECTED]> Sent: Wednesday, May 26, 2004 3:03 PM Subject: Re: [Mailman-Users] Errors > Andreas, > > > How would I fix this? mug was the name of a lists I created. &

Re: [Mailman-Users] Errors

mug is not the name of a list. Andreas If this is the first email to me, please place NOSPAM somewhere in the subject. - Original Message - From: "Mark Smith" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, May 26, 2004 2:57 PM Subject: [Mailma

[Mailman-Users] Errors

Hi, I don't understand this message. - The following addresses had permanent fatal errors - "|/home/mailman/mail/wrapper post mug" (expanded from: <[EMAIL PROTECTED]>) - Transcript of session follows - Mailman error: post got bad listname: mug 554 "|/home/mailman/mail/wrapper po

Re: [Mailman-Users] errors using DELIVERY_MODULE = 'Postfix'

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Brian York wrote: > Whe i set DELIVERY_MODULE = 'Postfix' i get the following error repeated > several times on the console. > --- > Traceback (most recent call last):

[Mailman-Users] errors using DELIVERY_MODULE = 'Postfix'

Whe i set DELIVERY_MODULE = 'Postfix' i get the following error repeated several times on the console. --- Traceback (most recent call last): File "/var/mailman/bin/qrunner", line 270, in ? main() File "/va

[Mailman-Users] errors on make install

when i install 2.1.4 i get this following error on make install command: Compiling /usr/local/mailman/Mailman/i18n.py ... Compiling /usr/local/mailman/Mailman/versions.py ... Traceback (most recent call last): File "bin/update", line 48, in ? from Mailman import MailList File "/usr/local/

[Mailman-Users] Errors with htdig

Hi all I upgraded to mailman 2.1.4 and I added the indexing and htdig patches to have searchable archives. Everything seems to be working, but I keep getting this error from the nightly_htdig cron job. What am I doing wrong? DB2 problem...: /var/lib/htdig/db.metaphone.db: Permission denied DB

Re: [Mailman-Users] errors using -request address

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Duncan Baker - Lydbury English Centre wrote: > I've just started using Mailman and I get nothing at all if I send > to the -request address. It just comes through as a straight email > to my default domain address and doesn't seem to trigger Mailman at

Re: [Mailman-Users] errors using -request address

I've just started using Mailman and I get nothing at all if I send to the -request address. It just comes through as a straight email to my default domain address and doesn't seem to trigger Mailman at all. Grateful for any thoughts on that. Running on an NT server if that makes any diffference.

[Mailman-Users] errors using -request address

When I send commands to the -request address I get an email back that says: There were problems with the email commands you sent to Mailman via the administrative address <[EMAIL PROTECTED]>. To obtain instructions on valid Mailman email commands, send email to <[EMAIL PROTECTED]> with the

[Mailman-Users] errors reported when trying to create test list

Hello, Traceback (innermost last): File "./bin/newlist", line 220, in ? main() File "./bin/newlist", line 169, in main mlist.Create(listname, owner_mail, pw) File "/home/mailman/Mailman/MailList.py", line 787, in Create self.InitVars(name, admin, crypted_password) File "/hom

[Mailman-Users] errors reported when trying to create test list

Hello, Traceback (innermost last): File "./bin/newlist", line 220, in ? main() File "./bin/newlist", line 169, in main mlist.Create(listname, owner_mail, pw) File "/home/mailman/Mailman/MailList.py", line 787, in Create self.InitVars(name, admin, crypted_password) File "/hom

Re: [Mailman-Users] Errors when creating a new list in v.2.1

It looks like this command failed: /usr/sbin/postalias /usr/local/mailman/data/aliases It's probably a permissions issue. Is the web server user able to write to that directory? Dallas On Tuesday, March 18, 2003, at 07:28 pm, Ted Dively wrote: I just tried to create a list via the http inte

Re: [Mailman-Users] Errors when creating a new list in v.2.1

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ted Dively wrote: > I just tried to create a list via the http interface, and Mailman > returned this error message. Any ideas, fellow listers? As always, > thanks for your patience, understanding, and guidance. [...] > Traceback (most recent call la

[Mailman-Users] Errors when creating a new list in v.2.1

I just tried to create a list via the http interface, and Mailman returned this error message. Any ideas, fellow listers? As always, thanks for your patience, understanding, and guidance. Ted Dively *** Bug in Mailman version 2.1 We're sorry, we hit a bug! If you wo

Re: [Mailman-Users] Errors when starting Mailman v.2.1

>From the Archives: === I've had this exact same problem installing mailman on solaris. The problem is in getting python configured properly. Make sure LD_LIBRARY_PATH points to all the right places, including wherever the SSL libraries live, and you may have to hack the Modules/Setup file in the p

[Mailman-Users] Errors when starting Mailman v.2.1

Can anyone tell me what these errors mean, and how I can avoid them when running bin/mailmanctl start? Errors when starting mailman 2.1 on OSXS v.10.2.4: Mar 12 12:44:46 2003 qrunner(6534): Cannot import runner module Mailman.Queue.NewsRunner Mar 12 12:44:46 2003 qrunner(6534): No module named _

Re: [Mailman-Users] Errors in nightly gzip

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Lucas, Lucas Albers wrote: > [EMAIL PROTECTED] root]# ls -ld /usr/local/mailman /usr/local/mailman/archives > /usr/local/mailman/archives/private/ > drwxrwsr-x 21 mailman mailman 4096 Feb 12 20:17 /usr/local/mailman > drwxrwsr-x4 mailma

RE: [Mailman-Users] Errors in nightly gzip

PROTECTED] On Behalf Of Todd Sent: Monday, February 24, 2003 3:06 PM To: [EMAIL PROTECTED] Subject: Re: [Mailman-Users] Errors in nightly gzip -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Luke, Lucas Albers wrote: >> Just out of curiosity, what are the perms on the directory where >>

Re: [Mailman-Users] Errors in nightly gzip

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Luke, Lucas Albers wrote: >> Just out of curiosity, what are the perms on the directory where mailman >> is trying to create the file (/usr/local/mailman/archives/private/cs223)? > > ls -l /usr/local/mailman/archives/private/cs223 > total 20 > drwx

RE: [Mailman-Users] Errors in nightly gzip

> --Luke > --Computer Science Sysadmin, MSU Bozeman > --admin(AT)cs.montana.edu 994-3931 > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf > Of Todd > Sent: Monday, February 24, 2003 12:28 PM > To: [EMAIL PROTECTED] &g

Re: [Mailman-Users] Errors in nightly gzip

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Lucas Albers wrote: > I am getting errors in my nightly gzip job. > Any ideas what is causing it? > Check-perms does not find any errors. [...] > Message Excerpt: > Traceback (most recent call last): > File "/usr/local/mailman/cron/nightly_gzip", lin

[Mailman-Users] Errors in nightly gzip

I am getting errors in my nightly gzip job. Any ideas what is causing it? Check-perms does not find any errors. Message Headers Received: from web1.cs.montana.edu (localhost.localdomain [127.0.0.1]) by web1.cs.montana.edu (8.12.5/8.12.5) with ESMTP id h1LAR0d0006676 for <[EMAIL PRO

Re: [Mailman-Users] Errors with Mailman 2.1 final

29-Jan-03 at 11:58, Simon White ([EMAIL PROTECTED]) wrote : > I saw an error on the HTTPS site too, a Traceback with different params, > but I can't reproduce it so I won't bother y'all with it now Here it is: Traceback (most recent call last): File "/home/mailman/scripts/driver", line 87, in r

[Mailman-Users] Errors with Mailman 2.1 final

Hello I was running Mailman 2.1b6, I just upgraded because I was having some problems. I always get the latest before coming to a list (I'm new here, just point me to some FAQ or other). First of all the UPGRADING file doesn't cover from 2.1bN to 2.1final, but that's minor. I fly by the seat of m

Re: [Mailman-Users] Errors running CGI script

You will also see this if Apache is not configured correctly... You may need an Alias in httpd.conf: Alias /pipermail/ //archives/public/ Quoting Matthew Davis <[EMAIL PROTECTED]>: > * Feng Jeffrey ([EMAIL PROTECTED]) wrote: > > I've been trying to install Mailman onto a FreeBSD based compute

Re: [Mailman-Users] Errors running CGI script

* Feng Jeffrey ([EMAIL PROTECTED]) wrote: > I've been trying to install Mailman onto a FreeBSD based computer. After I > created a test mailing list, I ran into an error like this when accessing > the mailing list archive from the Apache server: > > Forbidden > You don't have permission to access

[Mailman-Users] Errors running CGI script

I've been trying to install Mailman onto a FreeBSD based computer. After I created a test mailing list, I ran into an error like this when accessing the mailing list archive from the Apache server: Forbidden You don't have permission to access /pipermail/test/ on this server. Additionally, a 403 F

[Mailman-Users] Errors installing mailman-2.0.13 / Python-2.2.1 / Solaris 8

Title: Errors installing mailman-2.0.13 / Python-2.2.1 / Solaris 8  ./configure returns errors installing mailman-2.0.13 with Python-2.2.1 under the Solaris 8 operating environment, Ultra 5. The initial errors I encounter were with the UID and group ID checking. I fixed these by following th

Re: [Mailman-Users] errors

At 09:42 30/08/2002 +0200, Roelf Schreurs wrote: >Hi > >I'm quite worried about these errors in mailman. >Can somebody please explain what this means. > >Thanks > >Aug 30 09:37:42 2002 (21563) Uncaught runner exception: unpack list of >wrong size >Aug 30 09:37:42 2002 (21563) Traceback (most rece

[Mailman-Users] errors

Hi   I'm quite worried about these errors in mailman. Can somebody please explain what this means.   Thanks   Aug 30 09:37:42 2002 (21563) Uncaught runner exception: unpack list of wrong sizeAug 30 09:37:42 2002 (21563) Traceback (most recent call last):  File "/opt/mailman/Mailman/Queue/Run

[Mailman-Users] errors log

Hi   I get the following error in my error log.     Aug 27 10:10:10 2002 (26463) Uncaught runner exception: unpack list of wrong sizeAug 27 10:10:10 2002 (26463) Traceback (most recent call last):  File "/opt/mailman/Mailman/Queue/Runner.py", line 105, in _oneloop    self._onefile(msg, msgd

[Mailman-Users] Errors

This weekend, my error logs started filling up with this error: Jul 20 16:12:01 2002 (80580) Delivery exception: EOF read where object expected Jul 20 16:12:01 2002 (80580) Traceback (most recent call last): File "/home/mailman/Mailman/Handlers/HandlerAPI.py", line 82, in do_pipeline func(m

RE: [Mailman-Users] errors in subscription process

04, 2002 11:31 AM > To: [EMAIL PROTECTED] > Subject: [Mailman-Users] errors in subscription process > > > I'm getting errors in the subscription process. > > Background: I'm not sure whether this is a problem > with the way my ISP has mailman set up or if it i

[Mailman-Users] errors in subscription process

I'm getting errors in the subscription process. Background: I'm not sure whether this is a problem with the way my ISP has mailman set up or if it is something I can fix. The MTA in use there is Exim 3.35 #1, and it is configured such that all mail to my domain that isn't directed to a particular

Re: [Mailman-Users] Errors getting web pages, using 2.0.8

> "KM" == Kevin McCann <[EMAIL PROTECTED]> writes: KM> Messages are sent just fine, archive files are created, but KM> when I try to retrieve web pages (archives, listinfo, etc.), I KM> get messages in /home/mailman/logs/errors that contain this: KM> admin(3434): [- Mail

[Mailman-Users] Errors with Mailman 2.1 - Sendmail Problem

Hi, I get following error in the error log of mailman: May 05 09:51:49 2002 (27895) Uncaught runner exception: global name 'recips' is not defined         May 05 09:51:49 2002 (27895) Traceback (most recent call last):  

[Mailman-Users] Errors from qrunner

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi I get the following error messages, I don't have any idea where from: Found in log/error Jan 14 17:50:02 2002 qrunner(22552): Traceback (most recent call last): Jan 14 17:50:02 2002 qrunner(22552): File "/usr/lib/mailman/cron/qrunner", line 28

[Mailman-Users] errors and questions mailman

hi, i setup a mailinglist for blind folks. i have differently questions: 1. a non-subscriber send a message to my list. mailman give i reply. i Approve the message, go on the submit-button. the message will only saved in the archiv. is this option disabled, mailman send the message to the subscrib

[Mailman-Users] errors with admindb and hold-postings

I'm using Mailman version 2.0.6 on Red Hat 7.1. It was working fine before I went on vacation, but now I'm getting many errors. No one has changed anything, or so I'm told, so I don't know where to start looking. Because there's a cron job to retry failed deliveries once per minute, I continual

[Mailman-Users] Errors: OSError: [Errno 2] No such file or directory

Hi All, I've been using mailman since the 1.x versions and am now using 2.0.3 but ever since upgrading from 2.0 to 2.0.2 (the problem didnt exist with 2.0) I have been getting the following email every time somebody posts: Date: Wed, 14 Mar 2001 22:54:01 +1100 From: root (Cron Daemon) To: mai

Re: [Mailman-Users] errors after installing postfix

Hi Charles. If I read your post right, you're building with the wrong GID. Try configuring with --with-mail-gid=99. Dave Klingler > > I can't get rid of this: > > Jan 5 09:40:24 mail postfix/local[29125]: 75172FBD: > to= com>, relay=local, delay=0, status=bounced (Command died with status 2:

[Mailman-Users] errors after installing postfix

I can't get rid of this: Jan 5 09:40:24 mail postfix/local[29125]: 75172FBD: to=, relay=local, delay=0, status=bounced (Command died with status 2: " /home/ma ilman/mail/wrapper post test". Command output: Failure to exec script. WANTED gid 501, GOT gid 99. (Reconfigure to take 99?) ) I have d

[Mailman-Users] Errors after installing Postfix

I can't get rid of this:   Jan  5 09:40:24 mail postfix/local[29125]: 75172FBD: to=, relay=local, delay=0, status=bounced (Command died with status 2: " /home/mailman/mail/wrapper post test". Command output: Failure to exec script. WANTED gid501, GOT gid 99.  (