On Fri, 2003-03-21 at 12:30, Will Froning wrote:
I've noticed that Mailman is kind enough to apply some formatting
changes to my newlist.txt template when it sends the file out.
Is there a way to keep Mailman from joining these lines?
Start the lines with whitespace. Mailman won't wrap such
On Thu, 2003-03-20 at 21:16, Jeremy Butler wrote:
I encountered an interesting case of, I think, Mailman-provoked Postfix
churning this afternoon. For several hours, Postfix and Mailman kept going
in circles (see below). Fortunately, when I restarted Postfix, the
churning stopped.
This
On Mon, 2003-01-27 at 16:28, Jon Carnes wrote:
~mailman/bin/genaliases in mentioned in:
NEWS
UPGRADING
README.POSTFIX
Sorry, it looks like the genaliases script is designed specifically to
be used with Postfix... Hmmm. Seems like it could easily be made MTA
neutral, and still be
On Fri, 2003-03-21 at 17:58, Ted Dively wrote:
On Friday, Mar 21, 2003, at 13:08 US/Pacific, Andre Ricardo wrote:
Do what the message says, recompile with --with-mail-gid=nobody
As my original post says, I *did* this, but I get the exact same error,
only with nobody and mailman
On Thu, 2003-03-20 at 15:43, Todd wrote:
I think you have to restart mailmanctl after you do this, but I'm not sure.
Any time you make a change to mm_cfg.py you need to restart mailmanctl,
otherwise none of the qrunners will see the changes.
-Barry
On Thu, 2003-03-20 at 14:12, Bob Franklin wrote:
What I'm unsure about is what should be done with this list - should it be
configured in a certain way or whatever? I guess it's just required so
Mailman can have a valid sending address and can capture bounces, etc. in
the usual way.
Right,
On Thu, 2003-03-20 at 10:36, Jeremy Butler wrote:
I know that one is not supposed to manually edit virtual-mailman, but I've
run into a problem where aliases were not deleted when I removed a list and
then recreated it again with the same name.
Consequently, I've got duplicate entires (see
On Fri, 2003-03-21 at 17:20, John Swartzentruber wrote:
I'm not sure I can stretch my memory back to January, but I think the
issue was that the genaliases script doesn't create a file with the
aliases in them unless you are using Postfix (presumably with the MTA
variable set to Postfix). I'm
On Fri, 2003-03-21 at 17:04, Marilyn Davis wrote:
I'm still pulling out my hair on this one, and a hairless woman is not
a pretty thing.
Oh, I don't know about that...
http://go.sciflicks.com/artists/p/persis_khambatta_star_trek_the_motion_picture.jpg
:)
I figured out that the SMTPDirect
On Tue, 2003-03-18 at 11:27, Chris Barnett wrote:
Is there something else I can do or anywhere I can look for more clues?
The other traffic is minor, but sending duplicates to this number of
people is a big problem for me.
In addition to your sendmail logs, you can look in log/smtp to see if
On Mon, 2003-03-17 at 15:15, Chuq Von Rospach wrote:
This gave me an idea, since I had a list with a binary email address
(how? add_members of a directory instead of a file in the directory.
oops).
Here's a thought: since find_members takes a regular expression, you
could do something like
On Mon, 2003-03-17 at 15:15, Chuq Von Rospach wrote:
This gave me an idea, since I had a list with a binary email address
(how? add_members of a directory instead of a file in the directory.
oops).
Oh, I should point out one other thing. I fixed Mailman cvs so that it
would reject
On Sun, 2003-04-06 at 19:36, Todd Green wrote:
I do not believe this is the case. Postfix will execute commands via the
uid specified by postconf default_privs which is set to nobody if you
don't change it. However the mailman script is setgid, so it will run with
an effective group of
On Sat, 2003-05-17 at 00:12, Kory Wheatley wrote:
I've sent this email twice and no one has responded to this problem, I would really
appreciate a response.
I receive this below error when I go into the Administrative Interface and
check Preserve messsages for the site administrator and
On Mon, 2003-06-02 at 16:36, Kory Wheatley wrote:
Is there some kind of administrator login I can use to manage
subscriptions ... we have so many listservs that adding and removing
subscriptions by list is a big hassle - it would be easier if I could
manage subscriptions by user name rather
On Mon, 2003-05-26 at 19:34, Tentra List Support wrote:
I tryed change the default page and link colors by adding relevant fields in
Default.py to mm_cfg.py. Changing all of the directives worked except for
WEB_LINK_COLOR
which did not result in a change. I found the offending error in
This sounds like an interesting opportunity to get some more Mailman
exposure. I won't be able to attend, but if any of our UK or Euro
friends are planning to, would you be willing to volunteer a little time
at the booth? If so, please let me and Brian know (I don't know what
all is involved,
On Sun, 2003-08-10 at 18:10, [EMAIL PROTECTED] wrote:
Hi Barry,
We seem to have a problem here with your mailing list called *peach.kiosk.ws*. A ton
of us are getting these emails for removal from this list. Here is the URL:
On Thu, 2003-08-14 at 10:45, Chuming Chen wrote:
Before I send a digest out, I would like to edit it. Where in the
Unix world is it located? How can I have permission to read/write
it?
It lives in lists/yourlist/digest.mbox
I would like to be able to send out a digest when I want. From
I recently received a message about problems with Mailman and CPanel. I
don't know anything about CPanel, or why Mailman and CPanel might not be
working together, but that doesn't mean I wouldn't be interested in
helping to make sure this is still a viable solution. I know a lot of
people use
On Mon, 2003-09-22 at 18:49, Chuq Von Rospach wrote:
Does anybody know anything about this?
I've seen people asking about it on ListOwners. I've kept my head down
because I didn't know what you'd said/done, but it sort of sounds like
it's either the cPanel folks trying to blame Mailman
On Mon, 2003-09-22 at 19:02, Robert Anderson wrote:
I don't know the answer but is mailman really an out of the box solution
that is suitable for users without basic programming or linux sysadmin
skills? Because there are a lot of CPanel users in this category.
Installation and setup
On Mon, 2003-09-29 at 10:37, Ricardo Kleemann wrote:
Hi,
Is there a way for mailman's configure script to detect the
current settings (such as
--with-username, --with-mail-gid and so on)?
Or is there a quick way for me to manually check what they
should be?
I want to be able to
On Thu, 2003-10-02 at 15:53, Tom Limoncelli wrote:
Not to one-up you but...
I record the steps I take to build something in a script, so that the
next time I build something I can edit the script a little and run it.
Lately I've added a boilerplate at the top that sets the PATH,
Terri Oda has written a nice manual for Mailman list members, and I've
finally pushed it out to the web site (and mirrors). It's available
both on-line and in PDF format.
You can access the manual at:
http://www.list.org/users.html
http://mailman.sf.net/users.html
On Wed, 2003-10-15 at 05:56, Iain Bapty wrote:
I'm a 3rd year Computer Science student at UMIST in Manchester, UK just
starting my 3rd year project. My project is to create a new archiver
component for Mailman based on Zest. I'm posting this message to both
User and Developer lists as I
On Thu, 2003-10-30 at 05:11, Pasi Sjoholm wrote:
anyone didn't reply to me so I fixed this by myself, here is the patch:
Applied, with some modification, to CVS. It will be part of 2.1.4.
Thanks,
-Barry
--
Mailman-Users mailing list
[EMAIL
I've had a lot of requests recently for information about Mailman
hosting. As a general rule I don't like to recommend any particular
hosting company. But if you do provide Mailman hosting facilities,
please make sure you've added yourself to the PythonHosting wiki:
On Tue, 2003-11-25 at 17:08, pchamorro wrote:
Dear Mailman Users,
I finished the Spanish translation of 'GNU Mailman - List Member Manual'
written by Terri Oda. If somebody knows about spanish-fluent mailman users,
please forward this message to him/her. The translated manual is available
On Tue, 2003-12-09 at 01:50, City wrote:
version 2.1.2 have an option Only List administrator can post
messages in mailing list?
If yes where?
http://www.python.org/cgi-bin/faqw-mm.py?req=showfile=faq03.011.htp
-Barry
--
SourceForge recently instituted a donation system for projects and
users, whereby you can donate some money to a PayPal account to show
your appreciation for the free and open source projects you use.
Donations to projects require opt-in from all the project's admins.
Jeremy and I have both
On Fri, 2004-01-02 at 19:32, Tim Perdue wrote:
Hello, I am trying to get a mailman install to work on SUSE Pro 9 with
their weird apache 2.0.48 setup. Apache runs as wwwrun:www, or is
supposed to.
I properly compiled mailman with cgi-gid=8 (www) and the list WWW
interface works 90%
On Mon, 2004-01-12 at 17:53, Mark A. Mandel wrote:
On your web page
http://www.list.org/lists.html
the link labeled
{{Listowners}} is a mailing list with a non-technical focus,
specifically for discussions from the perspective of listowners and
moderators who do not have shell
On Thu, 2004-01-22 at 15:39, Richard Barrett wrote:
And I did not say it would. Nor is it necessary to so do. Outlook is
not wrong and nor is Mailman. Its just that some users are confused by
what they see and some mailing list admins are equally confused about
why their users are
On Thu, 2004-01-22 at 16:48, Brad Knowles wrote:
At 4:26 PM -0500 2004/01/22, Barry Warsaw wrote:
Who's the agent responsible for the actual transmission of the message?
Is Mailman acting as this agent? Arguably not.
I disagree. I believe that this is exactly the role
On Sun, 2004-02-01 at 08:40, Andrzej Kasperowicz wrote:
Hi!
In monthly reminders send by mailman in Polish, Polish fonts are
corrupted. Code page in the header of the message is correct i.e. iso-
8859-2, but instead of Polish fonts there are only some numbers displayed
as can be seen
On Mon, 2004-02-09 at 10:51, Brad Knowles wrote:
At 3:31 PM +0100 2004/02/09, Kai Schaetzl wrote:
Searchable Archives:
http://www.mail-archive.com/mailman-users%40python.org/
Unfortunately, the link to the maillists on www.lists.org doesn't point to
that archive. Wouldn't it be
I have some rather big changes ready for MM2.1.5 that I wanted to
describe and get feedback from you. While I have this stuff working and
ready to be checked in, we will definitely need some beta testing before
unleashing on the world. I hope you'll be able to help with that. I
think these
I have just released Mailman 2.0.14 as a patch-only release. This fixes
a DoS bug to be described in CAN-2003-0991. See here for details:
https://sourceforge.net/project/shownotes.php?release_id=97760
Please note that since I am no longer actively maintaining Mailman 2.0,
this release has had
I've created a list specifically for discussing Mailman 3 design and
development. Feel free to subscribe at:
http://mail.python.org/mailman/listinfo/mailman3-dev
I'd like to keep MM3 discussions off the main mailman-developers list as
much as possible. The list will be open and will be run
Hey folks, quick note. Mailman's the March 2004 SourceForge.net project
of the month.
http://sourceforge.net/potm/potm-2004-03.php
-Barry
--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
On Thu, 2004-03-18 at 11:23, Jon Carnes wrote:
The problem I've been having is that there doesn't seem to be a way
for the LIST ADMIN to change a subscriber's e-mail address without a
confirmation (unless one goes through a subscribe/unsubscribe which
risks changing user options and the user
I've just uploaded Mailman 2.1.5 release candidate 2 (no, you never saw
rc1 :). Since there are some fairly significant changes with this
version, I felt it was necessary to put out a release candidate to
hopefully prompt some additional testing.
If you're able to test the new version, that
On Sat, 2004-04-24 at 23:47, Barry Warsaw wrote:
I've just uploaded Mailman 2.1.5 release candidate 2 (no, you never saw
rc1 :).
There was something wrong with the tarball, so I just uploaded a new
version (along with a new signature and an updated md5sum in the release
notes).
If you grabbed
Today I am releasing Mailman 2.1.5, a bug fix release that also contains
new support for the Turkish language, and a few minor new features.
Mailman 2.1.5 is a significant upgrade which should improve disk i/o
performance, administrative overhead for discarding held spams, and the
behavior of
On Tue, 2004-06-01 at 17:31, Brad Knowles wrote:
At 6:45 PM +0100 2004/06/01, Ian A B Eiloart wrote:
Ah, I see, so I upgrade by reinstalling. But that isn't clear from the
documentation, because as easy as doesn't mean is achieved by. So
there's me thinking, OK, so its easy, but how do
) is written as Solvenian. please correct this.
However, this page has the same error. I believe that this will
need to be corrected by Barry Warsaw.
Fixed in cvs. This will be corrected on the web pages the next time I
push them out.
Thanks,
-Barry
signature.asc
Description
On Tue, 2004-06-22 at 10:20, Brad Knowles wrote:
It's been a little while since I've gotten anything from the
list, and it appears some messages have shown up in the archives that
I haven't seen. I'm checking my subscription now, but I'm wondering
if anyone else has seen any
On Fri, 2004-12-03 at 21:41, Tokio Kikuchi wrote:
time.strftime('%d-%b-%Y', day + (0,)*6)) should be something like:
time.strftime('%d-%b-%Y', day + (0,0,0,0,1,0))
Looks like we should care 2.4 compatibilty first before jumping in it.
Definitely. We should not release 2.1.6 until we're
I've finally regained access to all three websites, list.org,
mailman.sf.net, and the GNU mirror, so I've pushed out the latest
updates. There are the usual additions to the list of users, but much
more importantly there's Terri's new user documentation, and my recent
consolidation of the
There is a critical security flaw in Mailman 2.1.5 and earlier Mailman
2.1 versions which can allow remote attackers to gain access to member
passwords under certain conditions. The extent of the vulnerability
depends on what version of Apache you are running, and (possibly) how
you have
On Wed, 2005-02-09 at 17:00, Tokio Kikuchi wrote:
I've tested with my 1.3.29 installation and verified apache PATH_INFO
does convert '//' to '/'. Barry also wanted to clarify which apache
version/installation (combination with mailman) is valnerable. Return
code of 200 doesn't mean
On Mon, 2005-02-14 at 10:23, Brad Knowles wrote:
In response to this issue, FAQ 1.27 has been updated
Wow Brad, I was just about to change this to read
[EMAIL PROTECTED] but you beat me to it by seconds. :)
, and the
mailman-users and mailman-developers mailing lists have likewise
Release candidate 3 for Mailman 2.1.6 is now available. This fixes a
late-breaking problem with RFC 2231 encoded headers containing bogus or
non-existent charsets. Specifically, this release includes an updated
version of the email package (2.5.6).
Please try this version out as much as
On Fri, 2005-05-13 at 00:23, Mark Sapiro wrote:
All of a sudden, within the last hour or so, subject_prefix on both
mailman-users@python.org and mailman-developers@python.org is being
added to replies even though it's already present resulting in
doubling and tripling (so far not more) of the
On Fri, 2005-05-13 at 05:05, Brad Knowles wrote:
At 12:41 AM -0400 2005-05-13, Barry Warsaw wrote:
Thanks for the quick heads up. I think I just fixed it. At least I
/hope/ so, 'cause I'm going to bed. ;)
So far as I know, we had been running a plain-jane 2.1.6rc3
On Fri, 2005-05-13 at 08:14, Tokio Kikuchi wrote:
I believe I could finally fix the bug and commited in CVS. IMHO, python
re.escape() should escape special characters only -- I can't find '%' in
special character list in the manual.
Cool. Sounds like a bug to me. I'll probably spin rc4 in
A few more last minute fixes and some language updates. Please let me
know if you encounter any show stoppers. Barring any really critical
bugs, this is going to be 2.1.6 final.
-Barry
https://sourceforge.net/project/shownotes.php?release_id=327367
signature.asc
Description: This is a
On behalf of the development team, I'm pleased to announce the release
of GNU Mailman 2.1.6. This is a significant release, which includes
three important security patches, updated Chinese (zh_TW and zh_CN)
support, better compatibility with Python 2.4, a few new features, and
many bug fixes.
On Thu, 2005-07-28 at 11:52, Mark Sapiro wrote:
The real issue here seems to be that the import from mm_cfg done in the
driver script is inadequately protected. The driver script
print_traceback definition contains
try:
from Mailman.mm_cfg import VERSION
except
The Python.org administrators have moved the website to our spiffy new
server, however the Mailman FAQ wizard hasn't yet been moved. It should
be shortly.
Please try not to make any changes to the FAQ wizard for the next day or
so. Currently, until your DNS updates, you'll be hitting the wizard
On Wed, 2005-10-12 at 13:16, Barry Warsaw wrote:
The Python.org administrators have moved the website to our spiffy new
server, however the Mailman FAQ wizard hasn't yet been moved. It should
be shortly.
Please try not to make any changes to the FAQ wizard for the next day or
so
On Fri, 2005-12-23 at 09:22 +0900, Tokio Kikuchi wrote:
May be we should set this default in Defaults.py.in in the next release
of 2.1.7. Thoughts?
It's probably a good idea, but also as Stephen says, it might be a good
idea to shorten the filename (keeping the extension) even when this
value
On Jan 14, 2006, at 9:59 PM, Tokio Kikuchi wrote:
Mark Sapiro wrote:
File /usr/lib/python2.3/uu.py, line 139, in decode
sys.stderr.write(Warning: %s\n % str(v))
File /usr/lib/mailman/Mailman/Logging/MultiLogger.py, line 45,
in write
_logexc(logger, msg)
File
On Mon, 2006-01-16 at 09:25 +0900, Tokio Kikuchi wrote:
In usual mailman qrunner execs, stderr is logged into logs/errors. It
is the additional tee_to_real_stderr in LogStdErr() setting which wants
to print the error into real stderr.
Isn't it safe to put the tee_to_real_stderr value 0
For a while now, I've been trying to implement several project
management improvements for Mailman, so that future development can be
opened up to more people. As Tokio's and Mark's work has shown, there
are very talented programmers out there that can contribute great stuff
to Mailman if given a
On Sun, 2006-04-16 at 11:17 +0930, Clytie Siddall wrote:
Barry, thanks for such an encouraging look into the near future. :)
I'm trying to get re-energized! :)
OK, I've already submitted an i18n howto to the SF tracker, which I
don't think Tokoi has had time to implement. I would be happy
On Thu, 2006-04-27 at 16:04 +0100, Richard Barrett wrote:
And your point is?
Of course I be deluded and imagining the error response I got back
but then again 17 days is a long time in the life of a file's
permissions.
Indeed. After I sent my response, I noticed that your original
On Thu, 2006-04-27 at 22:46 -0500, Brad Knowles wrote:
If the previous value of the Sender: field is being lost, then
that should be corrected. At the very least, the value should be
saved in an Old-Sender: or Previous-Sender: or some other
suitable renamed sender field.
Probably
On Fri, 2006-04-28 at 12:37 -0500, Brad Knowles wrote:
The current FAQ Wizard has the advantage of simplicity and
tracking all previous changes (in case things need to be rolled
back). Wikis, by their nature, are considerably more complex and at
least some of them don't track
Now that I have a few minutes to breath ;) I'll try to summarize my
thoughts on this, and then perhaps go back later and follow up to
specific points later in the thread.
I'm sympathetic to ripping out the Sender: field munging. It was always
primarily a workaround for buggy MTAs. If the
On Fri, 2006-04-28 at 13:05 -0500, Neal Groothuis wrote:
As I noted in my previous response, I believe that the correct field (if
Mailman were to add a Sender: header) to add would be Resent-Sender.
Please see RFC 2822, section 3.6.6.
Whatever else we decide, I don't agree, or at least,
On Fri, 2006-04-28 at 14:08 -0400, Bob [EMAIL PROTECTED] wrote:
...Trouble similar to a current problem I am having with AOL: they are
bouncing all email with the
FROM: address of a specific AOL user, when mailman delivers the
messages to -any- aol or cs.com
address.
Have you tried
On Fri, 2006-04-28 at 19:12 -0500, Brad Knowles wrote:
I think we need to gather a lot more information about the likely
outcome from this change, and I think the best way to achieve this is
through giving admins (either site admins or list admins) the ability
to set an option and
On Sun, 2006-04-30 at 00:00 +0900, Stephen J. Turnbull wrote:
Sender doesn't instruct *conformant* MTAs at all, does it? AFAIK the
only thing that a RFC 2821-conforming MTA looks at is the Return-Path
header, and it's supposed to remove that.
So this is purely a matter of pragmatic
On Mon, 2006-05-01 at 18:16 -0700, Mark Sapiro wrote:
Neal Groothuis wrote:
Mailman is not the originator of the message, so it should
not be tampering with the From: or Sender: fields at all.
This is arguably not true. Mailman may add a list header and/or list
footer to the body of
On Mon, 2006-05-01 at 13:27 -0500, Neal Groothuis wrote:
I'd like to work up an unofficial diff to Mailman 2.1 for people like
Stephen who are willing to give it a try on a live site.
I'm not sure this is even necessary.
Ezmlm doesn't touch the Sender: header at all, Majordomo sets it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On behalf of the Mailman development team, I'm happy to announce the
release of Mailman 2.1.9 release candidate 1. This is primarily a
bug fix and security release, although it also contains two new
languages: Arabic and Vietnamese.
This
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On behalf of the GNU Mailman development team, I'm please to announce
GNU Mailman 2.1.9. This is primarily a security and bug fix release
and it is highly recommended that all sites upgrade to this version.
Mailman 2.1.9 also contains support
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Okay, first of all let's all take a deep breath. This can be worked
out.
Let me state up front that my general preference is always to allow
the widest possible access to the Mailman and Python lists, and in
general to all open source content.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sep 18, 2006, at 12:26 PM, JC Dill wrote:
If Barry wants to let the list be gatewayed to gmane and usenet
over our objections, he is certainly entitled to do that. It will
also mean that he will need new people to help manage the various
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sep 20, 2006, at 10:35 AM, Bill Landry wrote:
Thanks Patrick, that certainly gives me a listing of all of the member
e-mail address for every list, but does not associate them with the
particular list they apply to. I was looking for an output
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sep 26, 2006, at 2:12 PM, Brad Knowles wrote:
At 8:51 AM -0400 9/26/06, Elizabeth Schwartz wrote:
Another question: is there any parallelism of processing files
in the out
queue or are they done sequentially?
By default, it's
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm including mailman-developers on this message, because I want to
discuss the issue of which Python versions to support.
On Sep 27, 2006, at 11:04 AM, Stubbs Jeff wrote:
Got a question. I picked up another Mac, so I'm going to rebuild my
list
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sep 26, 2006, at 9:07 PM, Brad Knowles wrote:
But you're still using a single directory as an on-disk queue, and
that single directory has to be completely locked, operated on, and
then unlocked every single time you want to create a new
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sep 27, 2006, at 9:32 PM, [EMAIL PROTECTED] wrote:
Mailman 2.1.x supported on Python 2.3, 2.4, and 2.5. Drop support
for Python 2.1 and 2.2. We've done this accidentally in Mailman
2.1.9, so let's make it official.
Would it be possible to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sep 27, 2006, at 8:29 PM, Tokio Kikuchi wrote:
In summary my preferences would be:
Mailman 2.1.x supported on Python 2.3, 2.4, and 2.5. Drop support
for Python 2.1 and 2.2. We've done this accidentally in Mailman
2.1.9, so let's make it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sep 28, 2006, at 2:13 PM, Stubbs Jeff wrote:
Barry - thanks for the advice
I just wanted to report that Tiger (10.4.7 : ppc), Python 2.5 (from
the OS X installer), and Mailman 2.1.9 works perfectly. Install
went without a hitch.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sep 28, 2006, at 8:45 PM, Larry Stone wrote:
This all made me curious. I'm just a user of Mailman on Mac OS X - no
development of any sort by me - so I'm good with 2.1.9 and Python
2.3.5 on
10.4.7 - but this topic made me look at the Python
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sep 28, 2006, at 11:03 PM, Larry Stone wrote:
On 9/28/06 9:16 PM, Barry Warsaw at [EMAIL PROTECTED] wrote:
So, that leads to the question, is there any reason to install
python 2.5
while running 2.1.9 or are we fine with 2.3.5 if we aren't
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Oct 8, 2006, at 11:01 AM, Gadi Evron wrote:
Hi guys. I've been playing a lot with Google's new code search,
collecting
a lot of search strings relating to security.
I searched for TBD and then TBD security. The very first hit is from
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Oct 27, 2006, at 3:54 PM, Paul Gevers wrote:
I am working on a customized user management system created in
python/Zope. Currently I am using the bash script in mailman/bin to
communicate with Mailman, but I like to do a little bit more (which
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Oct 28, 2006, at 2:30 PM, Dragon wrote:
I'm in agreement with Mark here. I find this whole idea horrifying.
HTML is for web pages, not e-mail.
Friends don't let friends do HTML e-mail.
I'm by no means a fan of HTML email either, but /if/ we
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Nov 17, 2006, at 11:53 AM, Brad Knowles wrote:
PPS: Perhaps you could remove the direct link to this list from
http://www.gnu.org/software/mailman/lists.html (in the left row) -
because the list requires subscription.
The list does require
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Nov 18, 2006, at 7:48 AM, Georg Sauthoff wrote:
At the page http://www.gnu.org/software/mailman/docs.html the authors
invite users to just mail to mailman-users@ ('Email Us' - left side,
like every left side ) and only 'suggest' to subscribe
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Nov 19, 2006, at 4:00 AM, Brad Knowles wrote:
This might very well work. But speaking only for myself, I would
not be interested in being on the mailman-help list.
I don't blame you ;). If anybody else is interested in seeing a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Nov 19, 2006, at 12:41 PM, Mark Sapiro wrote:
If you haven't started rebuilding the archives yet, I suggest you
don't
do it. Not only will it invalidate all the links in the FAQ which can
be changed with some effort, it will also invalidate
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Nov 22, 2006, at 11:28 PM, John W. Baxter wrote:
In your situation, it may make more sense to use a mailing list
manager
written to be driven from email, such as Majordomo. Mailman--as a
reaction to the problems some people found with the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Nov 28, 2006, at 6:08 PM, Guy Waugh wrote:
I'm still wondering whether I should be NFS-sharing the qfiles
directory. I haven't delved into the Mailman source code to try to
figure this out, but...
You should be able to NFS share the qfiles
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Nov 28, 2006, at 6:32 PM, Brad Knowles wrote:
I believe that you are correct -- if the post is held on only one
server, and you happen to log into the other server to approve the
post, then the second machine would not see that post to approve
1 - 100 of 405 matches
Mail list logo
