On 3/22/2012 5:48 PM, Stephen J. Turnbull wrote:
On Fri, Mar 23, 2012 at 1:09 AM, Barry Warsaw ba...@list.org wrote:
If we add something like $archive_url to the decoration interpolation
dictionary, what happens when we have multiple archivers that support
permalink() enabled? Do we chose
/reading :),
Chris
On 11/23/2011 5:16 AM, Ian Eiloart wrote:
On 16 Nov 2011, at 16:10, C Nulk wrote:
I can't help but consider the rash of useless Mediator headers.
Consider the following example:
Person 1 sends a message to a list which is then sent to Person 2.
Person 1's site has separate
Hello,
I thought I would ask a quick question on the development of Mailman 3.
Over in the Mailman-Users list, Mark Sapiro mentions that he adds a
regex into the ban_list of all of his lists.
Is there any consideration being given to having a global ban_list which
applied across all lists for a
On 11/15/2011 6:52 PM, Barry Warsaw wrote:
On Oct 29, 2011, at 06:39 AM, Patrick Ben Koetter wrote:
I suggest we use the term 'Mediator' as introduced by D. Crocker in RFC 5598
http://www.rfc-editor.org/in-notes/rfc5598.txt instead:
A Mediator attempts to preserve the original Author's
On 11/10/2011 12:33 PM, Patrick Ben Koetter wrote:
* Barry Warsaw ba...@list.org:
X-Mailman-Version
The version of Mailman that sent the message. It can lose the X-
prefix.
Modify to: List-Agent, Mediator
Next Step: Discuss
I like List-Agent much more than User-Agent,
On 11/2/2011 8:06 AM, Barry Warsaw wrote:
Thanks for coordinating this Patrick.
On Oct 30, 2011, at 08:04 PM, Patrick Ben Koetter wrote:
X-List-Received-Date
This only gets added when the message is sent to the archive.
Modify to: List-Archive-Sent
Next Step: Discuss
On 10/26/2011 5:43 AM, Ian Eiloart wrote:
On 25 Oct 2011, at 02:04, Barry Warsaw wrote:
On Oct 13, 2011, at 11:41 PM, Murray S. Kucherawy wrote:
There's movement afoot to deprecate use of X- in header field names. Just
call it Mailman-Topic. And if it's worthwhile, consider registering it
sent within (or BETWEEN) the scheduled digests time period /
freq. for whatever reason - size, number of msgs - would increment the
digest number only. If there are no digests/msgs to send, then the
volume number does not increment.
Thanks Mark,
Chris
On 5/24/2011 3:50 PM, Mark Sapiro wrote:
C
On 5/24/2011 5:23 AM, Barry Warsaw wrote:
On May 24, 2011, at 01:39 PM, Benedict Stein wrote:
5. showing stats within the archives view instead of the config
Yep. We need to do a much better job of collecting and exposing stats.
I don't know if this is the place to mention it but along with
Hello all,
I am using Mailman v2.1.9 with some minor local mods on CentOS 5.5. In
looking through the vette log, I noticed some of the log entries for
refused postings and discarded postings do not indicate what message
(via the message id) was acted upon. I would like to the message id to
Ian Eiloart wrote:
--On 9 July 2010 12:11:50 +0200 Anna Granudd anna.gran...@gmail.com
wrote:
Hi,
when subscribing a user or creating a list in Mailman 3.0 we need to
implement the use of a password for security reasons. Later the same
password will be used for logging in to the settings
Hello Mark,
I am posting the matches_p function below. I believe the problem is an
off-shoot of the lce/cpe problem with the LDAPMembership adapter you
helped me with earlier. I did get it to work by changing the condition
in matches_p from
if mother.members.has_key(sender):
to
if
I am pretty sure allowing the raw email addresses to be available is
going to go over like a lead balloon here. Anything (however minor) to
help protect the users/clients email addresses is helpful despite what
others think. It is fine if someone considers the obfuscation that
Mailman uses is
Barry Warsaw wrote:
On Aug 31, 2009, at 1:15 PM, C Nulk wrote:
I am pretty sure allowing the raw email addresses to be available is
going to go over like a lead balloon here. Anything (however minor) to
help protect the users/clients email addresses is helpful despite what
others think
Mark Sapiro wrote:
Barry Warsaw wrote:
On Aug 31, 2009, at 1:15 PM, C Nulk wrote:
As for using robots.txt, hmm, it is not the legitimate search
engines I
care about, it is the search engines/crawlers that do not respect my
robots.txt file that I care about. If I had
Barry Warsaw wrote:
I also looked to see if there was
an URL type interface for LDAP. There is however it would be primary be
an anonymous bind to a LDAP service. Most if not all places will not
allow anonymous binds which can update/change their LDAP information. I
just don't know enough
Mark Sapiro wrote:
C Nulk wrote:
While I waited, I did do some reading/researching on __init__ which lead
me to reading about __getattr__ and getattr. If I understand correctly,
the LDAPMemberships uses them to get the isMember() and getMembers()
methods among others.
Not exactly
Mark Sapiro wrote:
Consider the following instead.
Create a list named say posters with it's own extend.py with settings
like
ldap = LDAPMemberships(list)
ldap.ldapsearch = (role=list-poster) # as an example
ldap.ldapserver = ldap3.example.net
list._memberadaptor =
Mark Sapiro wrote:
C Nulk wrote:
Will this @list method also work for the other parameters/options that
have a list of email addresses (like owner, moderator, ban_list, ...) or
just the *_these_nonmembers options?
It only works for *_these_nonmembers. It could be implemented for
owner
Thank you for replying Mark.
Mark Sapiro wrote:
C Nulk wrote:
I have recently implemented the LDAPMembership adapter. It provides
some good functionality in creating the list membership. However, the
concept is there to provide access to one or more lists of email
addresses (list
Hello,
I have recently implemented the LDAPMembership adapter. It provides
some good functionality in creating the list membership. However, the
concept is there to provide access to one or more lists of email
addresses (list membership is essentially a list of email addresses). I
would like
21 matches
Mail list logo
