used by
Debian.
So if you want to leverage existing open source archiving or at least
look at an example of what would be necessary to allow easy easy
external archiving integration with Mailman you might want to look at
Lurker.
--
John Dennis <[EMAIL PROTECTED]>
___
bin/newlist to see how it's done.
Yes, that's what I meant, it's a good example of how to use the mailman
API directly.
--
John Dennis <[EMAIL PROTECTED]>
___
Mailman-Developers mailing list
Mailman-Developers@python.org
http://mail.
create a
> new list from the Python modules directly?
>
> Any pointers to the right docs here would be appreciated.
Your best bet might be to look at the command line interfaces under
the /bin directory in the source tarball. For the case cited you'll want
to look at bin/newlist.
--
#x27;t want to do that myself! Is there a Mercurial
> equivalent to SF for cvs and svn, or Launchpad for bzr?
The Fedora Project has started project hosting as well. At the moment it
is Trac based with Mercurial as one of the SCM options.
--
John
. By restricting the options to
the SCM's which currently have the most mindshare the pain threshold for
developers would be mitigated and the project would have stronger
assurances of on-going future support for the SCM.
--
John Dennis <[EMAIL PROTECTED]>
___
popular Python project). I've used Mercurial now for about 5
months and it has worked well. FWIW we have other projects also using
Mercurial.
I'll confess I'm not familiar with Bazaar and what it has to offer, it
may be the optimal choice, but I'm wondering, have you given Me
an do so
yourself, either directly via the mailman source distribution or by
installing an RPM from another release, but this would be a site
customization unsupported by Red Hat.
--
John Dennis <[EMAIL PROTECTED]>
Learn. Network. Experience open source.
Red Hat Summit San Diego | May 9-
On Thu, 2006-07-06 at 18:07 -0400, emf wrote:
> John Dennis wrote:
>
> > Speaking of stylesheets and customized UI, are you planning on having
> > the core mailman code generate xml, which then is transformed with xslt?
>
> This would be nice. My immediate target
On Thu, 2006-07-06 at 14:17 -0400, John Dennis wrote:
> ... don't forget for those folks who dislike
> pipermail one can with minimal effort use an external archiver.
Oh, and I should have added that one of the beefs with using an external
archiver is the disjoint UI between mail
ties?, else
Is the attribute defined for the list?, else
Is the attribute defined in the site's global properties?, else
attribute is undefined
--
John Dennis <[EMAIL PROTECTED]>
Red Hat Inc.
___
Mailman-Developers mailing list
Mailm
this during your
summer of code? You've got great ideas, but be realistic about what you
can actually accomplish and don't forget for those folks who dislike
pipermail one can with minimal effort use an external archiver.
--
John Dennis <[EMAIL
think I would
prefer both well known names and unknown extended names have identical
document structure rather than special casing the extended names in an
independent way. Special casing during a document traversal based on
context introduces unnecessary pain.
--
John Dennis <[EMAIL PROTECTED
On Thu, 2006-07-06 at 17:24 +0100, Ian Eiloart wrote:
>
> --On 6 July 2006 11:30:08 -0400 John Dennis <[EMAIL PROTECTED]> wrote:
>
> > I'm not sure I understand what the purpose is in treating the extended
> > fields differently, it seems like it would overly c
t;
> In order to provide a feed interface/ decent moderation interface, I
> have to have something analogous to this; while I don't intend to write
> each mail out as xml, there should be an url you can tickle to get out
> an xml representation.
--
John Dennis <[EMAIL PR
y the MLM, but rather than bringing any of
this functionality into Mailman lets define the interfaces which are
needed such that Mailman can operate cooperatively with any archiver
which supports a well defined API.
--
John Dennis <[EMAIL PROTECTED]>
Red Hat Inc.
__
XT data type are virtually
unlimited (as is the BLOB, or Binary Large Object, don't you love the
name?) But since the bounce data is converted to text the TEXT data type
makes more sense than BLOB.
--
John Dennis <[EMAIL PROTECTED]>
___
o take
an entirely different direction and we no longer have need for these
pieces of code. I would like to contribute what I've done as a patch on
the SF site. The only problem is its a 95% solution, the list
creation/deletion hooks are the missing 5% and I doubt I'll finish that
work. I
user properties are per list) then there seems to be little
value in intermingling site user data and mailman list data.
Also, it was not clear how an adapter might implement just a subset of
the methods via inheritance, I suppose it would copy the function
pointers from the mlist._member
ot;
README.EXIM"
README.LINUX"
README.MACOSX"
README.POSTFIX"
README.QMAIL"
README.SENDMAIL"
--
John Dennis <[EMAIL PROTECTED]>
___
Mailman-Developers mailing list
Mailman-Developers@python.org
http://mail.python.org/ma
become
"if I am me", which is trivally true because of the setgid property,
then the validty check always succeeds no matter who invoked mailman and
all security is defeated.
Note: I have only responded to this list, I have not updated the
original bug posting.
--
John Dennis <[E
voked? Is it only
for optional third party cgi scripts?
--
John Dennis <[EMAIL PROTECTED]>
___
Mailman-Developers mailing list
Mailman-Developers@python.org
http://mail.python.org/mailman/listinfo/mailman-developers
Mailman FAQ: http://www.pyth
y operates unless the
> PATH_INFO environment variable value being set up for the CGI script by
> Apache is a result of version-dependent processing done by Apache on
> the request URI.
Please, lets not discuss the recipe for the attack on an open mailing
list.
--
ntication mechanisms (e.g. pam, ldap, kerberos, etc.) should be
implemented. In my mind, this is too radical for a 2.1.x release. 3.0 is
the right time debut a more configurable and robust security framework.
--
John Dennis <[EMAIL PROTECTED]>
___
he MM 3.0 feature list. BTW, is there an independent MM 3.0
list? I thought I had heard such a beast existed, but my recollection is
hazy.
--
John Dennis <[EMAIL PROTECTED]>
--- Begin Message ---
Hi,
do you have a trusted contact to the Mailman developers? Their home
page doesn'
nue to ship mailman's
private copy of the codecs, add a check to "configure" to test for 2.4,
if its available use the python version, if not fallback to the previous
private method. Sound like a plan?
--
John Dennis <[EMAIL PROTECTED]>
On Tue, 2004-10-19 at 11:34, Dale Newfield wrote:
> On Tue, 19 Oct 2004, John Dennis wrote:
> > > "mailmanctl stop;config.status;make install;mailmanctl start"
>
> Just remembered that I missed "check_perms -f" in there. Which of course
> brings up th
ent to answer this
question and there were permission issues to overcome), this allows a
non-root, non-mailman user to do "/sbin/service mailman status"
--
John Dennis <[EMAIL PROTECTED]>
___
Mailman-Developers mailing list
[EMAIL PROTE
r to configure):
CONFIG_DIR: default=$VAR_PREFIX/dataFHS=/etc/mailman
PID_DIR default=$VAR_PREFIX/dataFHS=/var/run/mailman
Existing directories that can now be specified as parameter to configure:
LOCK_DIR: default=$VAR_PREFIX/locks FHS=/v
to a more constrained set of packages and much
more security driven. This patch which has been in our RPM for a while
is on the table for removal because of these security concerns.
--
John Dennis <[EMAIL PROTECTED]>
Mailman security is in part enforced by requiring it execute
SGID. When
e.in removes the "other" read permission on
$prefix/archives/private, but it leaves group read/write. This suggests
to me that $prefix/cgi-bin/private with setgid and arbitrary owner (e.g.
without running the "finish") is fine and thus leads me to the
conclusion the finish
nd the Red
Hat portion of the FAQ should be amended.
Thanks!
--
John Dennis <[EMAIL PROTECTED]>
___
Mailman-Developers mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-developers
Unsubscribe:
http://mail.python.
ase.
Out of curiosity could you elaborate on UID/GID constraints which
prevent you from using a postfix/mailman combination?
--
John Dennis <[EMAIL PROTECTED]>
___
Mailman-Developers mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/
ck in
> to RHEL 4.0. I would like to hope so, as I find 2.1.5 far superior to
> 2.0.13.
Mailman 2.1.5 is in RHEL 4
--
John Dennis <[EMAIL PROTECTED]>
___
Mailman-Developers mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo
On Tue, 2004-08-31 at 14:06, Brad Knowles wrote:
> At 10:45 AM -0400 2004-08-31, John Dennis wrote:
>
> > To the best of my knowledge the problems were addressed and there are
> > many satisfied users. We did ship a package with an install problem, but
> > then ag
#x27;m not sure it's
fair for you to maintain a mailman FAQ entry denigrating Red Hat or
reiterate that view in the mailing list for a past mistake, may we apply
for forgiveness?
--
John Dennis <[EMAIL PROTECTED]>
___
Mailman-Developers
to build Python from source if 2.3
> becomes a requirement...
FC2 which was just released has 2.3.3 as will RHEL4. Red Hat users if
they use Red Hat rpms will never have to build Python from source.
--
John Dennis <[EMAIL PROTECTED]>
__
the exploit? Is there a CVE or CAN open
against it? I assume given the public announcement this is not an
embargoed security exploit, or is it?
--
John Dennis <[EMAIL PROTECTED]>
___
Mailman-Developers mailing list
[EMAIL PROTECTED]
http://mail.
On Tue, 2004-01-27 at 13:26, Les Niles wrote:
> On Tue, 27 Jan 2004 04:39:24 -0800 "Somuchfun" <[EMAIL PROTECTED]> wrote:
> >I have a question in regards to mailman's recovery abilities.
> >Let's say mailman is running and sending out messages to a large list and
> >the machine crashes or is reboot
New Yahoo! Shopping - with improved product search
> http://shopping.yahoo.com
>
> _______
> Mailman-Developers mailing list
> [EMAIL PROTECTED]
> http://mail.python.org/mailman/listinfo/mailman-developers
--
John Dennis <[EMAIL PROTECTED]>
___
Mailman-Developers mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-developers
The mailman script which is used to start/stop/restart the mailman
daemon invokes mailmanctl with the -s argument when starting the
service. This argument purportedly is for stale lock clean up. One
consequence of passing this arg during a service start is that
mailmanctl bypasses the lockfile chec
40 matches
Mail list logo
