Just received word about those three:
https://github.com/0NYX-MY7H/CVE-2025-43921
-- wasn't able to reproduce on 2.1.39
https://github.com/0NYX-MY7H/CVE-2025-43920
-- wasn't able to reproduce on 2.1.39, due to not using an *_EXTERNAL_ARCHIVER
https://github.com/0NYX-MY7H/CVE-2025-43919
-- wasn't
I am pleased to announce the release of Mailman 2.1.36.
This is a security release. It fixes
https://bugs.launchpad.net/mailman/+bug/1949401 CVE-2021-43331 and
https://bugs.launchpad.net/mailman/+bug/1949403 CVE-2021-43332. The
former of these could allow an XSS attack against the user options
Two new security issues have been reported in Mailman 2.1. These have
been given the IDs CVE-2021-43331 and CVE-2021-43332.
I plan to release 2.1.36 with full details this Friday, November 12. At
that time the vulnerabilities will be made public and patches will also
be made available.
--
Ma
A couple of vulnerabilities have recently been reported. Thanks to Andre
Protas, Richard Cloke and Andy Nuttall of Apple for reporting these and
helping with the development of a fix.
CVE-2021-42096 could allow a list member to discover the list admin
password.
CVE-2021-42097 could allow a l
I recently rebuilt my server (Ubuntu 20.04) and rebuilt mailman 2 -
upgrading to the latest version 2.1.34. The mail server is postfix
I run three mailing lists, including "TESTmail". The same issue below
affects all three lists which are set up in the same way.
On the General Page, I have fille
On 07/26/2018 04:48 AM, Richard Damon wrote:
> The issue is probably that the links still point to the http version,
> which is redirecting to the https and losing the form data. You need to
> change the config variable that gives the base page for the admin pages
> to point to the https version.
On 7/26/18 7:26 AM, Jayson Smith wrote:
> Hi,
>
>
> I'm currently using 2.1.26. Recently I had LetsEncrypt add lines to my
> Apache configuration to redirect browsers from HTTP to HTTPS URLs.
> This morning I found that this doesn't seem to work well with Mailman
> database admin pages, I couldn't
Hi,
I'm currently using 2.1.26. Recently I had LetsEncrypt add lines to my
Apache configuration to redirect browsers from HTTP to HTTPS URLs. This
morning I found that this doesn't seem to work well with Mailman
database admin pages, I couldn't get Mailman to reject a held message
until I co
On 11/01/2017 06:48 PM, Robert Heller wrote:
> Thanks, that fixed things.
>
> Wouldn't make better sense to just use "relative" URLs?
We do use relative URLs in many, but not all cases. The list method
which gets these URLs has a flag to require an absolute URL and some
calls set it and some don
Thanks, that fixed things.
Wouldn't make better sense to just use "relative" URLs?
At Wed, 1 Nov 2017 17:41:56 -0700 Mark Sapiro wrote:
>
> On 11/01/2017 05:01 PM, Robert Heller wrote:
> > I can't find the admistrator docs for Mailman 2.1.x (I am running 2.1.16).
> > I
> > recently (today)
On 11/01/2017 05:01 PM, Robert Heller wrote:
> I can't find the admistrator docs for Mailman 2.1.x (I am running 2.1.16). I
> recently (today) got a Let's Encrypt SSL cert for my mailman site, but
> some things are not working right. The forms are being populated with
> http://
> actions and
I can't find the admistrator docs for Mailman 2.1.x (I am running 2.1.16). I
recently (today) got a Let's Encrypt SSL cert for my mailman site, but
some things are not working right. The forms are being populated with http://
actions and not https:// actions. What do I need to fix to correct
Hi, found this message back from 2005/11/28:
> "make install" dies with
> (cd ./$p ; umask 02 ; PYTHONPATH=/home/mailman/2.1.5/pythonlib
> /usr/local/bin/python setup.py --quiet install --install-lib
> /home/mailman/2.1.5/pythonlib --install-purelib
> /home/mailman/2.1.5/pythonlib --install-
Christophe Kalt wrote:
> Hi all,
>
> "make install" dies with
> (cd ./$p ; umask 02 ; PYTHONPATH=/home/mailman/2.1.5/pythonlib
> /usr/local/bin/python setup.py --quiet install --install-lib
> /home/mailman/2.1.5/pythonlib --install-purelib
> /home/mailman/2.1.5/pythonlib --install-data /h
Hi all,
"make install" dies with
(cd ./$p ; umask 02 ; PYTHONPATH=/home/mailman/2.1.5/pythonlib
/usr/local/bin/python setup.py --quiet install --install-lib
/home/mailman/2.1.5/pythonlib --install-purelib /home/mailman/2.1.5/pythonlib
--install-data /home/mailman/2.1.5/pythonlib); \
done
On Thu, 2003-12-04 at 05:41, M. Lewis wrote:
> I'm running Mailman -2.1.1-4 and Postfix-2.0.16-4.
>
> Monday morning at 5:00am my logs started filling with messages. As close as I
> can pin down what initiated the problem was the sending out of users
> passwords as that cron job starts at 5:00am
I'm running Mailman -2.1.1-4 and Postfix-2.0.16-4.
Monday morning at 5:00am my logs started filling with messages. As close as I
can pin down what initiated the problem was the sending out of users
passwords as that cron job starts at 5:00am on the first of the month.
Since that time, mailman
I use a VPS at Verio.
Has anyone with a similar configuration installed 2.1 yet successfully or
know if 2.1 is compatible with a virtual install?
AB
--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailm
I have searched the archives and docs... But I am really stuck on chuck.
Is there a pretty concise how to for installing Mailman on a Redhat 7.2
box using named based virtual hosts in a chroot environment with
safemode on?
What I want to do is install mailman (rpm or ./configure) on the server
(I
is light. There are no indications
> that the processes hung, died or puked. It simply just stops
> handling e-mail. Sendmail seems to work well.
>
> Mike
>
>
> -Original Message-
> From: Thomas Hillson [mailto:[EMAIL PROTECTED]
> Sent: Monday, March 31, 2003 8:
d. It simply just stops
handling e-mail. Sendmail seems to work well.
Mike
-Original Message-
From: Thomas Hillson [mailto:[EMAIL PROTECTED]
Sent: Monday, March 31, 2003 8:47 AM
To: mcobb; [EMAIL PROTECTED] Org
Subject: Re: [Mailman-Users] Mailman 2.1 setup problem
Mike.
Did you finish
Mike.
Did you finish going through the INSTALL document to copy the mailman
script to /etc/init.d and then run it. That starts the mailmanctl
application that passes email back to Postfix. You do not need the
wrapper as that is a sendmail app under the older Mailman.
Make sure mailmanctl is ru
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
mcobb wrote:
> I'm at whits end. I have spent all (probably because I'm an idiot)
> installing Mailman 2.1 on a RedHat 8.0 server. I'm running Postfix 1.11
> and have done all the config's via the Howto, Howdon'ts, pain and
> suffering guide etc.
>
> I
Folks,
I'm at whits end. I have spent all (probably because I'm an idiot)
installing Mailman 2.1 on
a RedHat 8.0 server. I'm running Postfix 1.11 and have done all the config's
via the Howto,
Howdon'ts, pain and suffering guide etc.
I created a list called test, and send e-mail to it. I get nothi
Fellow listers:
First, please forgive me for my general state of "newbieness", but that's
about where I am with Mailman and Python.
In any event, I've installed Mailman v.2.1 on a machine configured thusly:
Power Mac G4 400MHz (AGP)
1GB RAM
Mac OS X Server v.10.2.4 (Darwin)
December 2002 develop
Hello!
I've installed mailman 2.1, and I have a problem. I've posted it into
the FAQ:
3.19. How do I prevent Mailman to attach signs when the mail body is not
ASCII?
When I send a letter to a Mailman 2.1 mailserver, and the body of the
mail contains non-ASCII characters, the sign I set for t
> "jam" == John A Martin <[EMAIL PROTECTED]> writes:
jam> ,[ Google ] | Your search - "Warsaw's 4th Law" - did not
jam> match any documents. `
jam> :-)
Try "Warsaw's Fourth Law" :)
-Barry
--
Mailman-Users mailing lis
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
>>>>> "BAW" == Barry A Warsaw
>>>>> "Re: [Mailman-Users] Mailman 2.1 mailpasswds error"
>>>>> Tue, 4 Feb 2003 00:39:57 -0500
BAW> see Warsaw's 4th Law. :)
Pointer
CVR> it boiled down to problems with some of the language codecs,
CVR> the multi-byte languages. So evidently that isn't really
CVR> fixed on OS X, but I'll deal with that later.
I bet you're still having problems building Python extension modules
(i.e. C modules) on OSX.
I'm sure I
> "CVR" == Chuq Von Rospach <[EMAIL PROTECTED]> writes:
CVR> it boiled down to problems with some of the language codecs,
CVR> the multi-byte languages. So evidently that isn't really
CVR> fixed on OS X, but I'll deal with that later.
I bet you're still having problems building P
> "IVL" == Ivan Van Laningham <[EMAIL PROTECTED]> writes:
IVL> Thanks! That would have saved me an hour or so of poking
IVL> around on Feb 1;-)
I can definitely relate -- see Warsaw's 4th Law. :)
-Barry
--
Mailman-Users mailing l
Hi All--
"Barry A. Warsaw" wrote:
>
> > "MB" == Matt Brown <[EMAIL PROTECTED]> writes:
>
> MB> With 2.1 you need to create a "site-wide" mailing list called
> MB> "mailman".
>
> Note BTW, that I've just modified mailmanctl to refuse to start if the
> site list doesn't exist.
>
Tha
> "MB" == Matt Brown <[EMAIL PROTECTED]> writes:
MB> With 2.1 you need to create a "site-wide" mailing list called
MB> "mailman".
Note BTW, that I've just modified mailmanctl to refuse to start if the
site list doesn't exist.
-Barry
-
first of the month, and my password sending errored out again. I've
been spending some time debugging.
it boiled down to problems with some of the language codecs, the
multi-byte languages. So evidently that isn't really fixed on OS X, but
I'll deal with that later.
debugging this is tough, si
Hello
As a lot of qmail+vpopmail+mailman users, I get the famous
"Sorry,_no_mailbox_here_by_that_name._(#5.1.1)" error message.
I have gathered here the 3 alias creation methods i found reading the archives, in the
hope one of a goodwill soul to help.
Here is my setup:
FreeBSD 4.7_Stable - sour
Hello
As a lot of qmail+vpopmail+mailman users, I get the famous
"Sorry,_no_mailbox_here_by_that_name._(#5.1.1)" error message.
I have gathered here the 3 alias creation methods i found reading the archives,
in the hope one of a goodwill soul to help.
Here is my setup:
FreeBSD 4.7_Stable - so
At 03:58 AM 2/1/2003, Matt Brown wrote:
On Saturday 01 February 2003 04:18 pm, Larry Hansford wrote:
> However, the end-of-month cron job mailpasswds did not run.
>
> The subject of the message is:
>
> Cron /usr/local/bin/python -S /home/mailman/cron/mailpasswds
>
> And, the body of the message i
On Saturday 01 February 2003 04:18 pm, Larry Hansford wrote:
> However, the end-of-month cron job mailpasswds did not run.
>
> The subject of the message is:
>
> Cron /usr/local/bin/python -S /home/mailman/cron/mailpasswds
>
> And, the body of the message is:
>
> Site list is missing: mailman
Wit
Several weeks ago, I upgraded Mailman from v2.0.11 to v2.1, and have not
had any problems with it since. Both the users and me, as administrator,
love all the new features that became available.
However, the end-of-month cron job mailpasswds did not run.
The subject of the message is:
Cron /
On Wed, 29 Jan 2003 13:46:24 +0100, Marc Haber
<[EMAIL PROTECTED]> wrote:
>Is there a possibility to allow Mailman 2.1 to immedately forward a
>message from a moderator to the list if and only if the correct
>moderator password is given in the message? If the message doesn't
>have an "Approved: " h
30-Jan-03 at 10:46, Jon Carnes ([EMAIL PROTECTED]) wrote :
> An alternative way to eliminate the handling of aliases is to move to
> Postfix and use the Mailman/Postfix integration. Now that is a win-win
> situation.
>
> You can actually mimic this integration with Sendmail if you use a cron
> sc
An alternative way to eliminate the handling of aliases is to move to
Postfix and use the Mailman/Postfix integration. Now that is a win-win
situation.
You can actually mimic this integration with Sendmail if you use a cron
script (or modify the new-list app to include the script commands), to
ru
At 21:51 29/01/2003, Jon Carnes wrote:
If you can get shell access to the server you can use the
~mailman/bin/genaliases command to generate the aliases for your created
lists. You could simply redirect the output of that command into a
local aliases file and then include that aliases file in you
29-Jan-03 at 16:51, Jon Carnes ([EMAIL PROTECTED]) wrote :
> If you can get shell access to the server you can use the
> ~mailman/bin/genaliases command to generate the aliases for your created
> lists. You could simply redirect the output of that command into a
> local aliases file and then inclu
>What you don't know (because you've never done it before) is that
>installing via the Source is actually easier with Mailman than
>installing via the RPM.
>
>Installing via the RPM is buggy and only works if no default has been
>touched - plus you still need to do all the work that is associated w
nuary 28, 2003 9:07 PM
> To: '[EMAIL PROTECTED]'
> Subject: Re: [Mailman-Users] mailman-2.1-1.i386.rpm
>
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Parker, David K wrote:
> > I'm almost at a point where I've either got to scrap ma
If you can get shell access to the server you can use the
~mailman/bin/genaliases command to generate the aliases for your created
lists. You could simply redirect the output of that command into a
local aliases file and then include that aliases file in your MTA's list
of aliases that it checks.
: [Mailman-Users] mailman-2.1-1.i386.rpm
I have the latest package from RedHat (2.1-7) running on RedHat 7.3 over
Postfix 1.7. I had to change the spec file slightly (use postfix and
python2 instead of sendmail and python), and can give anyone who wants
it a diff. The [beta] packages are available here
The RPM from RawHide isn't supported on RedHat 7.3 (or technically
anywhere, since RawHide is the beta distro). RedHat 7.3 has
/usr/bin/python (a 1.x binary from the 'python') and /usr/bin/python2 (a
2.x binary from the 'python2'). I had to configure the spec file to
depend on the python2 packa
> Simon White wrote:
> >29-Jan-03 at 10:30, Justin Georgeson ([EMAIL PROTECTED]) wrote :
> >
> >>I have the latest package from RedHat (2.1-7) running on RedHat 7.3 over
> >>Postfix 1.7. I had to change the spec file slightly (use postfix and
> >>python2 instead of sendmail and python), and can g
See my previous post. :)
Simon White wrote:
29-Jan-03 at 10:30, Justin Georgeson ([EMAIL PROTECTED]) wrote :
I have the latest package from RedHat (2.1-7) running on RedHat 7.3 over
Postfix 1.7. I had to change the spec file slightly (use postfix and
python2 instead of sendmail and python), a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Simon White wrote:
> Funny that they should miss the key dependency: Mailman requires
> python2...
They don't, the requires line from the rawhide rpm is:
Requires: webserver, python >= 2.2.1, mktemp
Apparently rawhide uses python-2 by default in
They didn't miss it, the RPM is aimed at RedHat 8, which has python 2.
RedHat 7.3 has two packages, python and python2, so you have to build it
using /usr/bin/python2 instead of /usr/bin/python (--with-python option
to configure)
Simon White wrote:
29-Jan-03 at 10:30, Justin Georgeson ([EMAIL P
From: Marc Haber <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: [Mailman-Users] [Mailman 2.1] Is it possible to pre-approve a
message?
Message-ID: <[EMAIL PROTECTED]>
Content-Type: text/plain; charset=us-ascii
MIME-Version: 1.0
Precedence: list
Message: 11
Hi,
we have a mai
29-Jan-03 at 10:30, Justin Georgeson ([EMAIL PROTECTED]) wrote :
> I have the latest package from RedHat (2.1-7) running on RedHat 7.3 over
> Postfix 1.7. I had to change the spec file slightly (use postfix and
> python2 instead of sendmail and python), and can give anyone who wants
> it a diff.
iginal Message-
From: Todd [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, January 28, 2003 9:07 PM
To: '[EMAIL PROTECTED]'
Subject: Re: [Mailman-Users] mailman-2.1-1.i386.rpm
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Parker, David K wrote:
I'm almost at a point where I've either
29-Jan-03 at 09:27, Parker, David K ([EMAIL PROTECTED]) wrote :
> Apparently the RPM was set expect Postfix MTA to run as mail. I'm guessing
> the RedHat standard is to run MTA as nobody. I do appreciate the efforts of
> the person who put the rpm out. I've got the list back up on another RedHat
>
TED]]
Sent: Tuesday, January 28, 2003 9:07 PM
To: '[EMAIL PROTECTED]'
Subject: Re: [Mailman-Users] mailman-2.1-1.i386.rpm
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Parker, David K wrote:
> I'm almost at a point where I've either got to scrap mailman
> completely and
Hi,
we have a mailing list of customers that we use to send out
announcements about service problems, bad lines and general
information. Nobody should be able to send e-mail to that list except
the people allowed to do so. Since e-mail senders are easily forged,
we have currently set all list memb
Hi,
I'm using mailman 2.1 on a Cobalt RAQ3 and trying to use the web
interface to create a list.
It creates the list, but doesn't add any entries to either the aliases
file or the virtusertable. It also doesn't provide a list of what
entries need to be added.
It doesn't seem that I have ev
Install clean from source, be sure to point the ./configure script to
your Pyton2.2.1 executable.
Good Luck - Jon Carnes
On Tue, 2003-01-28 at 23:01, Parker, David K wrote:
> I've been fighting problems after upgrading Mailman 2.0x to 2.1-1 using
> mailman-2.1-1.i386.rpm. I'm making headway but n
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Parker, David K wrote:
> I'm almost at a point where I've either got to scrap mailman completely
> and revert to an earlier rpm or install clean from source. Any suggestions
> would be appreciated.
If you're banging your head against the wall, uninsta
>I've been fighting problems after upgrading Mailman 2.0x to 2.1-1 using
>mailman-2.1-1.i386.rpm. I'm making headway but now mailmanctl terminates
>with the following error:
>
># /etc/rc.d/init.d/mailmanctl start
>Traceback (most recent call last):
> File "/etc/rc.d/init.d/mailmanctl", line 104, i
I've been fighting problems after upgrading Mailman 2.0x to 2.1-1 using
mailman-2.1-1.i386.rpm. I'm making headway but now mailmanctl terminates
with the following error:
# /etc/rc.d/init.d/mailmanctl start
Traceback (most recent call last):
File "/etc/rc.d/init.d/mailmanctl", line 104, in ?
(like the
StringIO module).
Good Luck - Jon Carnes
- Original Message -
From: <[EMAIL PROTECTED]>
To: "Jon Carnes" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Saturday, January 25, 2003 5:21 PM
Subject: Re: [Mailman-Users] Mailman 2.1: ImportError: No module n
, January 25, 2003 2:52 PM
> Subject: [Mailman-Users] Mailman 2.1: ImportError: No module named
> pythonlib.StringIO
>
>
> > updated installation from 2.0.13
> >
> > Had to install new python, python-2.2.2-7 compiled from source RPM
> > after updating the requir
2 PM
Subject: [Mailman-Users] Mailman 2.1: ImportError: No module named
pythonlib.StringIO
> updated installation from 2.0.13
>
> Had to install new python, python-2.2.2-7 compiled from source RPM
> after updating the required packages (i.e. db4).
>
> Any ideas on where the sou
updated installation from 2.0.13
Had to install new python, python-2.2.2-7 compiled from source RPM
after updating the required packages (i.e. db4).
Any ideas on where the source of this problem lies? It's running
on YDL 2.3 (redhat 7.2 like ppc system)
Bob
Many commands in Mailman installed from RPM give the following error? It
seems to be giving up on the second ">". Any thoughts?
File "./list_members", line 88
print >> fd, _(__doc__)
David Parker
Systems/Network Administrator
Information Technology Services
City of Bryan, Texas
---
Check your list admin settings and see if your set to get immediate
notifications.
On Fri, 2003-01-24 at 11:36, Marc Perkel wrote:
> I just upgraded to mailman 2.1 and it seems to work except I'm not receiving
> messages that would normally be sent to the moderator. When a non-member or
> modera
I just upgraded to mailman 2.1 and it seems to work except I'm not receiving
messages that would normally be sent to the moderator. When a non-member or
moderated member posts to the list it does hold the message for the moderator -
but it doesn't notify the moderator that a message is being hel
Hi,
I tried using the web interface to create a mailing
list. It claimed to have create it, but it didn't add the entries to the
aliases file?
Do I have a permissions issue?
--Will
--
Mailman-Users mailing list
[EMAIL PROTECTED]
http:/
The web site warns away from using it, but I see responses on the mailing
list that suggest people should use it in production if they want certain
features.
When is it going to come out of beta?
Sarah Stapleton-Gray
Web Site Coordinator
National Or
> The web site warns away from using it, but I see responses on
> the mailing
> list that suggest people should use it in production if they
> want certain
> features.
what do they warn of? web server? place a reverse proxy in front of it. we
run it with squid 2.4 stable 3 with host header
On Thursday 10 Oct 2002 9:53 pm, NOW Website Coordinator wrote:
> The web site warns away from using it, but I see responses on the mailing
> list that suggest people should use it in production if they want certain
> features.
>
> When is it going to come out of beta?
Dunno...
>
> Is anyo
On Thu, 2002-10-10 at 15:53, NOW Website Coordinator wrote:
> The web site warns away from using it, but I see responses on the mailing
> list that suggest people should use it in production if they want certain
> features.
>
> When is it going to come out of beta?
That's Barry's call.
>
> Is
I use it's built in
archiver, we don't really use it anyways...
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of NOW Website
Coordinator
Sent: Thursday, October 10, 2002 14:53
To: [EMAIL PROTECTED]
Subject: [Mailman-Users] Mailman 2.1 -- is anyone usi
The web site warns away from using it, but I see responses on the mailing
list that suggest people should use it in production if they want certain
features.
When is it going to come out of beta?
Is anyone currently using it?
Are you using it with Qmail in production?
Would you recommend it?
Hi
Sorry if this is the wrong list to post this but I have been testing Mailman
2.1 B2 for a while and was wondering when 2.1 was going to be released as
stable.
Thanks
Sean
---
Sean Preston [EMAIL PROTECTED]
System Administrator & Developer
Health Systems Trust (www.hst.org.za)
--
Hi,
I am using Mailman 2.0.1 and would like to know
if Mailman 2.1 will enable end users (who do not have access to the config
files) to edit the complete Welcome message, and maybe even the help message. I
am aware of several other improvements that will take effect with 2.1 but this
is t
> "KC" == Kevin Crawford <[EMAIL PROTECTED]> writes:
KC> Hello All, I am using 2.1b - I added a fake test user and sent
KC> some messages to the list - seemed that logs/bounce was
KC> logging the bounces. I then removed that user. A couple of
KC> days later, today, I added hi
Hello All,
I am using 2.1b - I added a fake test user and sent some messages to the
list - seemed that logs/bounce was logging the bounces. I then removed that
user. A couple of days later, today, I added him back, as well as another
fake user. When I send messages to the list now - nothing is log
Any recent timeframe on betas or final, are we still looking at the end
of Q1 2002 for a final 2.1 release? I patiently await the new features,
especially finally getting rid of subscriber passwords for unsubscribes.
Thanks,
Ben
--
Mailman-Use
On Tue, 8 Jan 2002 20:47:58 -0800 (PST)
Michael Ghens <[EMAIL PROTECTED]> wrote:
> On the mailman page, it states taht mailman 2.1 is still alpha. I
> would like to move to it. Is it worth my time or should I wait?
That rather depends on your needs, your level of general SysAdm
expertise and ab
> On the mailman page, it states taht mailman 2.1 is still alpha. I would
> like to move to it. Is it worth my time or should I wait?
Well, I'm using it happily. It adds a lot.
Try it out at least on a test list.
--
Mailman-Users maillist
On the mailman page, it states taht mailman 2.1 is still alpha. I would
like to move to it. Is it worth my time or should I wait?
--
Mailman-Users maillist - [EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
What is the status of 2.1?
safe to install/upgrade/use yet?
--
Jay S. Curtis
Camelid Listowner
Alpacas Listowner
member info / subscribe / unsubscribe / user options at:
http://lrllamas.com/mailman/listinfo/camelid
http://lrllamas.com/mailman/listinfo/alpacas
87 matches
Mail list logo
