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
: 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
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
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
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
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
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
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
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
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 postfix
Hi,
Im new to mailman.I've configured mailman-2.1.6 and getting the list
mailed to my email id . while trying to access the list through my
apache sever ,im getting the following error..
Bug in Mailman version 2.1.6
We're sorry, we hit a bug!
Please inform the webmaster for this site of this
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!\
Dave
Bug in Mailman version 2.1.5
Bug in Mailman version 2.1.5
We're sorry, we hit a bug!
If you would like to help us identify the problem,
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
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
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 bug
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? There
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
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
We recently received a report from one of users regarding a bug
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
the mailman software to 2.1.6 in hopes the bug will be fixed.
Can someone tell me what I can look for?
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
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 last):
File
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.
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 last):
File
Dear Sirs,
Hi!
There are more or less about seven months we make use of your Mailman service,
without any type of interruption.
But, since eight days, without explication, the Members Management page have
binded, with the system following written report:
Bug in Mailman version 2.1.5p1We're
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 hit a bug!
If
Hello,
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 hit a bug!
If you would like to
--On February 16, 2005 6:32:57 PM -0500 John Dennis [EMAIL PROTECTED]
wrote:
leading white space in python is significant
To which I reply:
As a completely off-topic question:
What the heck were they thinking when the designers of Python chose amount
of leading white space to indicate block
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
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 last):
File
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]
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
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:
File
Has anyone seen this problem?
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 last):
Christopher Adams wrote:
Has anyone seen this problem?
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
Christopher Adams wrote:
Traceback (most recent call last):
File /lists/scripts/driver, line 80, in run_main
pkg = __import__('Mailman.Cgi', globals(), locals(), [scriptname])
File /lists/Mailman/Cgi/private.py, line 43
parts = path.split(SLASH)
^
SyntaxError: invalid
Both answers mentioned a poor patch job. You are correct. Since I was
unaware that the patch job had been done, I didn't know what to look
for. I guess some text was simply pasted into the private.py file and it
resulted in spaces rather than tabs. The intention was to manually do
exactly what
Mark Sapiro wrote:
Christopher Adams wrote:
Traceback (most recent call last):
File /lists/scripts/driver, line 80, in run_main
pkg = __import__('Mailman.Cgi', globals(), locals(), [scriptname])
File /lists/Mailman/Cgi/private.py, line 43
parts = path.split(SLASH)
^
SyntaxError:
Are you running SuSE Linux? I had this problem two days ago when I
upgraded mailman using YOU from 2.1.3 to 2.1.4 on my Suse 9.1 Pro on a
AMD64 system.
To fix my problem all I had to do was install a python module via
YAST. I can't remember the name of it right now, but it's documented
in my
Carsten Henkel schrieb:
but i have no idea why that is. have you any idea ?
A solution to your problem was posted about 12 hours ago to this list.
[EMAIL PROTECTED]
-thh
--
Mailman-Users mailing list
Mailman-Users@python.org
i become this error page on the webinterface:
Bug in Mailman version 2.1.4
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:
Content-type:
Text
Bug in Mailman version 2.1.4
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 last):
On Jan 24, 2005, at 06:30, leonardo wrote:
File /var/lib/mailman/Mailman/Gui/Privacy.py, line 510, in
handleForm
GUIBase.handleForm(self, mlist, category, subcat, cgidata, doc)
File /var/lib/mailman/Mailman/Gui/GUIBase.py, line 154, in
handleForm
doc.addError(
File
Bug in Mailman version 2.1.2
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 last):
File
On 04/03/04 01:36 Ing.CIP Alejandro Celi Mariategui wrote:
Bug in Mailman version 2.1.1
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
Bug in Mailman version 2.1.1
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 last):
File
Hi, Mailman GURUS !!!
I need some help over here ... hehehe ...
Well, we have a server, with the following softwares:
- Fedora Linux - Core 1 (Operational System)
- Kernel = 2.4.22-1.2140.nptlsmp
- Mailman 2.1.4 (source compiled)
- Postfix 2.0.16 (source compiled)
- Apache 1.3.29 (source
Hi, Mailman GURUS !!!
I need some help over here ... hehehe ...
Well, we have a server, with the following softwares:
- Fedora Linux - Core 1 (Operational System)
- Kernel = 2.4.22-1.2140.nptlsmp
- Mailman 2.1.4 (source compiled)
- Postfix 2.0.16 (source compiled)
- Apache 1.3.29 (source
At 3:09 PM -0200 2004/02/06, Alessandro Luiz Petrocino wrote:
Hi, Mailman GURUS !!!
I need some help over here ... hehehe ...
Is there a particular reason that you feel you need to send this
message to the entire mailing list at least three times?
--
Brad Knowles, [EMAIL PROTECTED]
They
Sorry, my resoanable friend ...
I was an error in my mail program, and it sended the same message 2 (I
repeat: 2) TIMES !!!
So, can you, Mr. PERFECT GUY, forgive me ?!? It was an error ...
So, can anyone help me with THE MAILMAN PROBLEM, and not with the number
of messages sended ?!?
Thank's a
Alessandro Luiz Petrocino said:
I need some help over here ... hehehe ...
You don't say... Try not being so hysterical about your problem next time,
and obeying simple list etiquette - like ensuring you only send one
message to the list.
1.) When I try to create a new list, over the web
Hi;
I have received this page of error messages. Other notable item is
/usr/local is full. I don't know what I can safely delete or dev/null.
Please advise.
TIA
Michael
Michael P. Kolotila
Programmer/System Analyst
ACIS
Northern Essex Community College
Haverhill, MA 01830
e-mail [EMAIL
hi, our mailing lists [EMAIL PROTECTED] and
[EMAIL PROTECTED] are on your mailman, and they havebeen up and down
for the last week. today we got this message when we accessed the admin
page--hope you can help us.
josey foo
please reply to [EMAIL PROTECTED]
_
Bug in Mailman
hello,
are you hosted on Sitelutions as I am?
I had the exact same trouble; they have also been
working on their servers over the past few days.
They tell me it is all fixed now.
lee
--- Josephine Foo [EMAIL PROTECTED] wrote:
hi, our mailing lists [EMAIL PROTECTED]
and
[EMAIL
When trying to create a new list, I get the following error.
HEEEPPP
Thanks
Hannes
Bug in Mailman version 2.1.1
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
Hannes Calitz [EMAIL PROTECTED] writes:
When trying to create a new list, I get the following error.
...
RuntimeError: command failed: /usr/sbin/postalias
/var/lib/mailman/data/aliases (status: 1, Operation not permitted)
Oh, i know this.
Read
1 - 100 of 124 matches
Mail list logo
