On Monday, January 6, 2003, at 07:05 PM, Barry A. Warsaw wrote:
I've only ever seen this with lists on python.org that we upgraded
from MM2.0 according to the instructions in the UPGRADING file (see
UPGRADING INDIVIDUAL LISTS). I've never seen this for brand new MM2.1
lists. I've suspect it's
Hi there!
This question was sent some weeks ago and Barry kindly replied
that would be present in 2.1 release... so... :)
Which variable I have to use to generate this one:
This message was sent to: [EMAIL PROTECTED]
In my own lists footer?
Thanks! :)
Marco
--
Bazzmann Labs(c) -
BF == Bryan Fullerton [EMAIL PROTECTED] writes:
BF Yup, I have no doubt that it's because I'm mixing 2.0 and
BF 2.1. And yup, I've been upgrading individual lists as per the
BF UPGRADING instructions. Here's the rewrite rule I used for the
BF 2.1 list:
|
Has a tutorial or any books been written on this program as there have been for
Python?
thanks
chas
...
--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ:
On Mon, 2003-01-06 at 14:49, Richard Barrett wrote:
In the light of the attached I'm starting to wonder if sourceforge is
really up to the task. The support response would probably be more familiar
to users of the commercial operating systems so many of us love to hate.
Of course, if any
Check the FAQ (URL at the bottom of message). FAQ 3.4 might be of interest.
Next thing is downgrading isn't recommended. Moving from 2.0.13 to 2.0.11 isn't
recommended.
* Jonathan Hughes ([EMAIL PROTECTED]) wrote:
Hey Guys,
I have a Mandrake 8.2 box with Mailman version 2.0.13 and I
* Robert Garrigos ([EMAIL PROTECTED]) wrote:
Does anyone know of a mailman module for phpnuke?
There isn't one, at least there hasn't been mention of one here that I'm aware of.
--
| Matthew Davis /\ http://dogpound.vnet.net/ |
* 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
Just a stab in the dark... Is it communicating with the smtp server? It looks like
its getting a connection refused to sendmailmaybe?
* David Gibbs ([EMAIL PROTECTED]) wrote:
Any thoughts on this?
Jan 06 11:11:44 2003 (13289) Uncaught runner exception: [Errno 4]
Interrupted system
BF == Bryan Fullerton [EMAIL PROTECTED] writes:
BF Is there any limit to the length of the list-name variables or
BF the comparisons?
None except limits on directory names in your OS's file system. I
doubt you're even close. :)
BF Is there any other way a cookie request for
I've got a currently-running 2.0.8 installation. I've
installed a 2.1 instance as completely separate, but am
finding that, somehow, while
http://www.inorganic.org/mailman2/admin works, the links it
forms are of the form:
http://www.inorganic.org/mailman/admin/list
rather than
BG == Ben Gertzfield [EMAIL PROTECTED] writes:
BG I haven't tested this at all, but this patch to
BG Mailman/Handlers/Decorate.py to add Content-Disposition:
BG inline to any MIME'd headers and footers may make MS Outlook
BG show the footer in the message. Can you test it and
* Barry A. Warsaw [EMAIL PROTECTED] schrieb am 07.01.2003:
BG I haven't tested this at all, but this patch to
BG Mailman/Handlers/Decorate.py to add Content-Disposition:
BG inline to any MIME'd headers and footers may make MS Outlook
BG show the footer in the message. Can
From the 'verify.txt' it looks like %(email) will work.
* Marco Trevisan | Bazzmann.Com ([EMAIL PROTECTED]) wrote:
Hi there!
This question was sent some weeks ago and Barry kindly replied
that would be present in 2.1 release... so... :)
Which variable I have to use to generate this one:
Did you run the fix_url.py script?
* Roy S. Rapoport ([EMAIL PROTECTED]) wrote:
I've got a currently-running 2.0.8 installation. I've
installed a 2.1 instance as completely separate, but am
finding that, somehow, while
http://www.inorganic.org/mailman2/admin works, the links it
forms are
Hi there!
I have this message in log files
Mailman mail-wrapper: Illegal command: mailowner
qmail: 1041983596.486292 delivery 171: deferral:
Illegal_command:_mailowner/
I am working with MM2.1rc3 and qmail in a linux
debian
What is the mean of this message???
Whe i'm trying to access Archives using web, it display this error :
error msg
--
Not Found
The requested URL /pipermail/aposc-mailinglist/ was not found on this server.
Apache/1.3.20 Server at nel-rel234.nat.mimos.my Port 80
Any clue what is going wrong?
rgds,
mr_zali
Jan 07 19:25:22 2003 qrunner(1270): Traceback (most recent call last):
Jan 07 19:25:22 2003 qrunner(1270): File /usr/local/mailman/bin/qrunner,
line 270, in ?
Jan 07 19:25:22 2003 qrunner(1270): main()
Jan 07 19:25:22 2003 qrunner(1270): File /usr/local/mailman/bin/qrunner,
line 230, in
After I installed Mailman on my FreeBSD server, I created a test list and
sent a subscription to it, the server returned the folowing error message.
What causes this problem? Any help will be appreciated. Jeffrey
--
The original message was received at Tue, 7
Hi Folks,
I've been reading -users with digest option. So, forgive me for
cutting the thread. Since the patch manager of SF is not allowing
to upload a new patch now, I send this to the list. (sorry, if
it's folded)
With this patch, Decorate.py will try to make the footer
* syed ([EMAIL PROTECTED]) wrote:
Whe i'm trying to access Archives using web, it display this error :
error msg
--
Not Found
The requested URL /pipermail/aposc-mailinglist/ was not found on this server.
Apache/1.3.20 Server at nel-rel234.nat.mimos.my Port 80
Any
Make sure you setup the alias file for your mail server, you skipped that step. Its
different for each mail server.
* Feng Jeffrey ([EMAIL PROTECTED]) wrote:
After I installed Mailman on my FreeBSD server, I created a test list and
sent a subscription to it, the server returned the folowing
Matthew Davis wrote:
* syed ([EMAIL PROTECTED]) wrote:
Whe i'm trying to access Archives using web, it display this error :
error msg
--
Not Found
The requested URL /pipermail/aposc-mailinglist/ was not found on this server.
Apache/1.3.20 Server at
* syed ([EMAIL PROTECTED]) wrote:
error msg
--
Not Found
The requested URL /pipermail/aposc-mailinglist/ was not found on this server.
Apache/1.3.20 Server at nel-rel234.nat.mimos.my Port 80
Any clue what is going wrong?
Did you setup the apache Alias
* syed ([EMAIL PROTECTED]) wrote:
What version of mailman? If 2.0 is your crontab installed?
Back to the httpd problem. Did you restart apache?
If there hasn't been any posts to the list, there won't be a dir there, and you'll
get that error.
I'm using mailman-2.0.13
MTA
Anyone know what this message means in the error log: Jan 07 20:22:06 2003
(9953) lost data files for filebase:
1041992497.529189+0825c00113b2b04e16abe6f914d3b764396f75da
david
--
Mailman-Users mailing list
[EMAIL PROTECTED]
On Tue, 7 Jan 2003, Matthew Davis wrote:
Did you run the fix_url.py script?
Nope. Didn't see that mentioned in the directions.
Finally got it working through the simple expedient of
reinstalling Mailman.
-roy
--
Mailman-Users mailing list
Is the request pending for an administrator? Or is it not getting delivered by
mailman?
Check logs/qrunner and logs/error
--
| Matthew Davis /\ http://dogpound.vnet.net/ |
||
| Tuesday, January 07,
On Tuesday, January 7, 2003, at 12:15 AM, Barry A. Warsaw wrote:
BTW, for the hacker inclined, an possibly useful way to debug this is
to edit SecurityManager.py, the __checkone() method. Stick something
like this before the first try: line (untested):
syslog('debug', 'key: %s, c[key]:
PAR == Paul Allen Rice [EMAIL PROTECTED] writes:
PAR I've noticed that when I log out of the admin page for one
PAR list, go to another and login there, then come back to the
PAR first list, all without shutting down my browser, Mailman
PAR allows me back into the first list
RSR == Roy S Rapoport [EMAIL PROTECTED] writes:
Did you run the fix_url.py script?
RSR Nope. Didn't see that mentioned in the directions.
It's buried in the UPGRADING INDIVIDUAL LISTS section of the UPGRADING
file.
-Barry
--
On Tuesday, January 7, 2003, at 07:12 AM, Stephan Berndts wrote:
I realized the problem that trawler-world-list-help matches not only
the rewriterule for trawler-world-list-help but also that for
trawler-world-list. (Is there one in your case? I cannot remember.)
Nope, here there's only a
BF == Bryan Fullerton [EMAIL PROTECTED] writes:
BF If python's Cookie code (or at least SimpleCookie) doesn't
BF like cookies with :'s in them that'd explain it.
Great sleuthing, Bryan!
I don't have time tonight to work out a fix, but this is an excellent
clue, and I'm hopeful there's
First I just want to say:
MAILMAN ROCKS! :)
I managed to get 2.1 and htdig all running together and working
peachykeen... :) it's a beautiful thing! My monthly mailers all work now,
creating lists from the webinterface works, etc!
However--a suggestion? In Defaults.py, once all the patches
Qmail people:
This is a documentation patch for the README.QMAIL file. There's not much
testing here, but Barry would you consider applying it? I'm cc'ing -users
so they will be brought up to speed on the new 2.1.
-Ed
--- README.QMAIL.old2002-04-05 13:24:10.0 -0800
+++
BG == Ben Gertzfield [EMAIL PROTECTED] writes:
BG It's theoretically possible to search through the whole
BG header/footer of each list to see if it is completely
BG us-ascii, but this seems like a hack to me. Unless we do
BG that, we have to assume that the footer is in the
On Monday, January 6, 2003, at 07:42 PM, Barry A. Warsaw wrote:
Very interesting. I wonder if this could be some Apache bug or other?
We're running 1.3.27 on python.org so I don't have direct experience
with this bug on Apache 2.0
Sorry, any references to 2.0 are Mailman - I'm using Apache
37 matches
Mail list logo