[Mailman-Users] approval password linked to sender rather than list?
Background: Currently majordomo, but rapid switch to Mailman being considered. About 20,000 users. Over 2,000 lists, the majority being announcement with very limited numbers of permitted senders. Have been majordomo-based for many years. Recent spoof email jumped the priority of a potential majordomo-Mailman transition to very high. Installed Mailman 2.1.5 (that version simply for local proof-of-concept convenience). Would anticiapate running latest stable version. Very new to running a Mailman service (be gentle!). Executive summary of query: The existing Approved: mechanism needs a password shared in common across multiple people (which feels poor and doesn't scale well) and across multiple lists (again, scaling problems). Is there a facility, or plans for such, for each permitted sender to have (optionally) their own password, useable across many lists? (Note the numbers, and high proportion of limited access annnouncement lists in the above.) Details of query: I've read the FAQ. The nearest items to my query seem to be 3.11, 3.34, 3.46 etc. Our recent problem was a spoof email through Majordomo, via a small number of large lists to the entire institution, spoofing the From: of a valid Majordomo posters email address. The Mailman Approved: mechanism looks as if it should address much of this (but not as much as might be possible: see below). With Mailman, I've done an Approved: proof-of-concept demo: two lists, same list password; moderation switched on for everybody. Proved the working of: Approved: list password (1) being able to bypass the moderation function (good); (2) its absence or error being diverted to moderator (good). So our genuine posters can use Approved: and the email would go straight through, whereas the spoofer wouldn't be able to do this and the request would be diverted (very good!) to the various list moderators. BUT... ... in the environment described above we can see major benefits of a somewhat different authorisation slant. Problem: A spoof to many lists would go to many moderators within a list and across lists, requiring coordination of moderators within a list, and consistent action of one or more moderators per list across the lists. Very poor scaling at a large site (with many clusters of many lists). Suggestion: An approval process to allow a sender-based password. So something like: From: [EMAIL PROTECTED] # may or may not be spoofed To: [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED], ... Approved: pw belonging to permitted.poster.1 and also that pw being potentially shareable across multiple lists. This doesn't seem possible at present (v 2.1.5). But it seems related to FAQ 3.46, in particular section A password scheme could potentially be implemented Is it yet possible? (Assuming not, then ...) List subscribers can already have passwords attached to their membership of a particular list, but this is (I understand) only for subscription maintenance, not for posting authorisation. So the concept of password linked to email address is already present in Mailman. It would seem reasonable to extend Mailman to have a variant of the Approved: scheme (albeit with its inherent weak authentication) in which the password is associated with each permitted.poster.1 sender name to discriminate a real sender from the spoofer. Does that seem reasonable? What are the drawbacks (those that would have significantly worse problems/weaknesses than existing mechanisms)? Comments? If it is possible now (i.e. I have overlooked the relevant documentation), please point me in the correct direction, to documentation etc. If not yet possible, but acceptable in theory (perhaps with amendments), then we would hope to consider volunteering some effort into coding it. -- : David LeeI.T. Service : : Senior Systems ProgrammerComputer Centre : : Durham University : : http://www.dur.ac.uk/t.d.lee/South Road: : Durham DH1 3LE: : Phone: +44 191 334 2752 U.K. : -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Charset problem. cmd_confirm assumes ascii code.
Hello
We have problem with confirm mail when mail body contains
characters out of ascii code (range(128)). Mailman version
is 2.1.5 . I think Mailman could leave the body unread
when Subject contains the confirm code or at least it should
stop to end line. If Mailman wants to check through the body
it would be fair not to bug with the non-ascii codes.
People have auto-signatures with different character codes and
they may have automatic copy of the original mail as citation
(quotation). Mailmans request for confirmation contains non-ascii
code if the language code of the list is such.
Excerpt of the error log:
Apr 26 12:53:40 2006 (11216) Uncaught runner exception: 'ascii' codec can't
decode byte 0xe4 in position 3: ordinal not in range(128)
Apr 26 12:53:40 2006 (11216) Traceback (most recent call last):
File /usr/lib/mailman/Mailman/Queue/Runner.py, line 111, in _oneloop
self._onefile(msg, msgdata)
File /usr/lib/mailman/Mailman/Queue/Runner.py, line 167, in _onefile
keepqueued = self._dispose(mlist, msg, msgdata)
File /usr/lib/mailman/Mailman/Queue/CommandRunner.py, line 237, in
_dispose
res.process()
File /usr/lib/mailman/Mailman/Queue/CommandRunner.py, line 110, in process
stop = self.do_command(cmd, args)
File /usr/lib/mailman/Mailman/Queue/CommandRunner.py, line 135, in
do_command
return self.do_command(cmd, args)
File /usr/lib/mailman/Mailman/Queue/CommandRunner.py, line 137, in
do_command
return handler.process(self, args)
File /usr/lib/mailman/Mailman/Commands/cmd_confirm.py, line 86, in process
if line.lstrip() == match:
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe4 in position 3:
ordinal not in range(128)
Apr 26 12:53:40 2006 (11216) SHUNTING:
1146045219.7761891+6b2f2afceea57f26e6a9302e6a615bbd8266d493
Copy of the shunted file:
/usr/lib~mailman/bin/dumpdb -p
/var/spool/mailman/shunt/1146045219.7761891+6b2f2afceea57f26e6a9302e6a615bbd8266d493.pck
[- start pickle file -]
- start object 1 -
From [EMAIL PROTECTED] Wed Apr 26 12:53:39 2006
Received: from posti1.jyu.fi (posti1.jyu.fi [130.234.4.32])
by lists.jyu.fi (8.13.1/8.13.1) with ESMTP id k3Q9rdOt029242
for [EMAIL PROTECTED]; Wed, 26 Apr 2006 12:53:39 +0300
Received: from localhost (localhost.localdomain [127.0.0.1])
by posti1.jyu.fi (8.13.6/8.13.4) with ESMTP id k3Q9rdAc030411
for [EMAIL PROTECTED]; Wed, 26 Apr 2006 12:53:39 +0300
Received: from jylk.jyu.fi (jylk.jyu.fi [130.234.4.141])
by posti1.jyu.fi (8.13.6/8.13.6) with ESMTP id k3Q9rcUj030404
for [EMAIL PROTECTED]; Wed, 26 Apr 2006 12:53:38 +0300
Received: from jylk.jyu.fi by jylk.jyu.fi (PMDF V4.3-7 #2482)
id [EMAIL PROTECTED]; Wed, 26 Apr 2006 12:54:35 EET
Date: Wed, 26 Apr 2006 12:54:11 +0200 (EET)
From: Osmo Kujala [EMAIL PROTECTED]
Subject: Re: confirm 8e7af57ba7a721f68c96b0111f988ad36c8804f7
In-reply-to: Your message dated Wed, 26 Apr 2006 12:52:38 +0300
[EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Message-id: [EMAIL PROTECTED]
X-Envelope-to: [EMAIL PROTECTED]
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=ISO-8859-1
Content-transfer-encoding: 8BIT
X-Virus-Scanned: amavisd-new at cc.jyu.fi
X-Spam-Status: No, hits=-5.794 required=5 tests=[ALL_TRUSTED=-3.3, AWL=0.105,
BAYES_00=-2.599]
X-Spam-Level:
end
123ä
23456ö ÖÄ
- start object 2 -
{ '_parsemsg': False,
'lang': 'en',
'listname': 'ok-testi',
'received_time': 1146045219.7761891,
'torequest': 1,
'version': 3,
'whichq': '/var/spool/mailman/commands'}
[- end pickle file -]
What's especially nasty is that the waiting time for confirmation
stops with this error and the entry disappears from the list.
So it's hard to find out what happened.
I tried to find help from mailman-users archives. Found some
identical cases from years 2003 and 2004 by searching keywords
ascii ordinal confirm but no solution to the problem.
best regars
Osmo Kujala (Sorry about the typo's and I hope the scandinavian
characters won't stop you reading this)
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/kujala%40jylk.jyu.fi
Security Policy:
http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
Re: [Mailman-Users] Charset problem. cmd_confirm assumes ascii code.
Hi, Sorry about previous mail. I tried replying by using
a very stupid editor. I tried canceling the
the message but there wasn't that option. Lets try again.
I'm continuing my monolog(ue):
Hello
We have problem with confirm mail when mail body contains
characters out of ascii code (range(128)). Mailman version
is 2.1.5 . I think Mailman could leave the body unread
when Subject contains the confirm code or at least it should
stop to end line.
In the chart of IncomingRunner.py I can see why this is
not the case. I thought confirm is one of the jobs of
command processor like join, leave and request, when even
unicode processing would succeed better...
If Mailman wants to check through the body
it would be fair not to bug with the non-ascii codes.
People have auto-signatures with different character codes and
they may have automatic copy of the original mail as citation
(quotation). Mailmans request for confirmation contains non-ascii
code if the language code of the list is such.
Excerpt of the error log:
Apr 26 12:53:40 2006 (11216) Uncaught runner exception: 'ascii' codec can't
decode byte 0xe4 in position 3: ordinal not in range(128)
Apr 26 12:53:40 2006 (11216) Traceback (most recent call last):
File /usr/lib/mailman/Mailman/Queue/Runner.py, line 111, in _oneloop
self._onefile(msg, msgdata)
File /usr/lib/mailman/Mailman/Queue/Runner.py, line 167, in _onefile
keepqueued = self._dispose(mlist, msg, msgdata)
File /usr/lib/mailman/Mailman/Queue/CommandRunner.py, line 237, in
_dispose
res.process()
File /usr/lib/mailman/Mailman/Queue/CommandRunner.py, line 110, in process
stop = self.do_command(cmd, args)
File /usr/lib/mailman/Mailman/Queue/CommandRunner.py, line 135, in
do_command
return self.do_command(cmd, args)
File /usr/lib/mailman/Mailman/Queue/CommandRunner.py, line 137, in
do_command
return handler.process(self, args)
File /usr/lib/mailman/Mailman/Commands/cmd_confirm.py, line 86, in process
if line.lstrip() == match:
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe4 in position 3:
ordinal not in range(128)
Apr 26 12:53:40 2006 (11216) SHUNTING:
1146045219.7761891+6b2f2afceea57f26e6a9302e6a615bbd8266d493
Copy of the shunted file:
/usr/lib~mailman/bin/dumpdb -p
/var/spool/mailman/shunt/1146045219.7761891+6b2f2afceea57f26e6a9302e6a615bbd8266d493.pck
[- start pickle file -]
- start object 1 -
From [EMAIL PROTECTED] Wed Apr 26 12:53:39 2006
Received: from posti1.jyu.fi (posti1.jyu.fi [130.234.4.32])
by lists.jyu.fi (8.13.1/8.13.1) with ESMTP id k3Q9rdOt029242
for [EMAIL PROTECTED]; Wed, 26 Apr 2006 12:53:39 +0300
Received: from localhost (localhost.localdomain [127.0.0.1])
by posti1.jyu.fi (8.13.6/8.13.4) with ESMTP id k3Q9rdAc030411
for [EMAIL PROTECTED]; Wed, 26 Apr 2006 12:53:39 +0300
Received: from jylk.jyu.fi (jylk.jyu.fi [130.234.4.141])
by posti1.jyu.fi (8.13.6/8.13.6) with ESMTP id k3Q9rcUj030404
for [EMAIL PROTECTED]; Wed, 26 Apr 2006 12:53:38 +0300
Received: from jylk.jyu.fi by jylk.jyu.fi (PMDF V4.3-7 #2482)
id [EMAIL PROTECTED]; Wed, 26 Apr 2006 12:54:35 EET
Date: Wed, 26 Apr 2006 12:54:11 +0200 (EET)
From: Osmo Kujala [EMAIL PROTECTED]
Subject: Re: confirm 8e7af57ba7a721f68c96b0111f988ad36c8804f7
In-reply-to: Your message dated Wed, 26 Apr 2006 12:52:38 +0300
[EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Message-id: [EMAIL PROTECTED]
X-Envelope-to: [EMAIL PROTECTED]
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET=ISO-8859-1
Content-transfer-encoding: 8BIT
X-Virus-Scanned: amavisd-new at cc.jyu.fi
X-Spam-Status: No, hits=-5.794 required=5 tests=[ALL_TRUSTED=-3.3, AWL=0.105,
BAYES_00=-2.599]
X-Spam-Level:
end
123ä
23456ö ÖÄ
- start object 2 -
{ '_parsemsg': False,
'lang': 'en',
'listname': 'ok-testi',
'received_time': 1146045219.7761891,
'torequest': 1,
'version': 3,
'whichq': '/var/spool/mailman/commands'}
[- end pickle file -]
What's especially nasty is that the waiting time for confirmation
stops with this error and the entry disappears from the list.
So it's hard to find out what happened.
I tried to find help from mailman-users archives. Found some
identical cases from years 2003 and 2004 by searching keywords
ascii ordinal confirm but no solution to the problem.
http://www.mail-archive.com/mailman-users@python.org/msg20140.html
http://www.mail-archive.com/mailman-users@python.org/msg22621.html
...
From Mailman-developers:
http://www.mail-archive.com/mailman-developers@python.org/msg07411.html
Osmo
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
[Mailman-Users] Versions? Roadmap?
(New to Mailman, impressed so far.) Is there a Roadmap for future mailman releases? The current version seems to be 2.1.8 . However I've seen talk in archives about a 2.2.x and a Mailman 3. I've found the Mailman-3-dev archives but that seems to have been dormant for nearly a year (since July 2005). Although we are new (two weeks) to Mailman, we have a few queries about things we cannot find in 2.1.x. A Roadmap would show us (and other potential site-admins) what features might already be under consideration. For the record, our list (so far!) is: o approval: password: option for per-sender rather than per-list (see email earlier today); o true virtual hosting: same listname @ many domains; o corporate branding of Mailman pages. We could dabble in the possibility of contributing code to some of these. But any such work would need to be on something reasonably active with a realistic release schedule (we once, many years back, began doing things in Majordomo-2 only for that to stall and stall...). -- : David LeeI.T. Service : : Senior Systems ProgrammerComputer Centre : : Durham University : : http://www.dur.ac.uk/t.d.lee/South Road: : Durham DH1 3LE: : Phone: +44 191 334 2752 U.K. : -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] approval password linked to sender rather than list?
On 5/15/06, David Lee [EMAIL PROTECTED] wrote: List subscribers can already have passwords attached to their membership of a particular list, but this is (I understand) only for subscription maintenance, not for posting authorisation. So the concept of password linked to email address is already present in Mailman. It would seem reasonable to extend Mailman to have a variant of the Approved: scheme (albeit with its inherent weak authentication) in which the password is associated with each permitted.poster.1 sender name to discriminate a real sender from the spoofer. On the surface, this seems pretty reasonable. It ought to be easy to amend the bits that checked Approved: against the moderator/admin password to also check against the user password. For your purposes (*all* users must include a pssword), I think, this is trivial: in Mailman/Handlers/Approve.py, on or about line 108, change: if passwd is not missing and mlist.Authenticate((mm_cfg.AuthListModerator, mm_cfg.AuthListAdmin), passwd): to: --BEGIN-- if passwd is not missing and mlist.Authenticate((mm_cfg.AuthListModerator, mm_cfg.AuthListAdmin, mm_cfg.AuthUser), passwd, msg.get_sender()): --END-- (without, of course --BEGIN-- and --END--). That said, I don't really know Python, nor am I intimately familiar with the Mailman codebase, so you might want to wait for someone more knowledgable to vette this 'solution.' And, of course, when/if you upgrade, you'll need to re-do this, since Approve.py will get overwritten. -- - Patrick Bogen -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] approval password linked to sender rather than list?
At 10:01 AM +0100 2006-05-15, David Lee wrote: Is there a facility, or plans for such, for each permitted sender to have (optionally) their own password, useable across many lists? This is a very good question. I'm glad you brought it to this list. I'm pretty sure that there is no facility in Mailman today to achieve what you're looking for. I see no problem with the concept, but I will let others answer the technical issues of how it might be done, etc If you haven't done so already, I would encourage you to file this as a Request For Enhancement on the Mailman SourceForge page at http://sourceforge.net/tracker/?group_id=103atid=350103. Problem: A spoof to many lists would go to many moderators within a list and across lists, requiring coordination of moderators within a list, and consistent action of one or more moderators per list across the lists. Very poor scaling at a large site (with many clusters of many lists). Yup. Getting the list moderators/admins to act in a consistent manner is an issue regardless of the size of the list or the number of lists. We have similar issues with just the mailman-users and mailman-developers lists on python.org, and they are much less numerous than what you're talking about, and the lists are also much smaller. Sometimes I'll approve a post for the mailman-developers list that I think is marginal as to whether or not it belongs on that list and sometimes I'll let it sit for a few days and see if one of the other moderators/admins will take a decision. I try to follow the guidelines that we've agreed for moderating and administering the lists, but I don't always remember what they are, and I don't always make the decision in a way that the other moderators/admins would have agreed with. I'm not convinced that having per-user approval passwords would help the moderators act in a more consistent manner, but it certainly wouldn't hurt. This doesn't seem possible at present (v 2.1.5). But it seems related to FAQ 3.46, in particular section A password scheme could potentially be implemented Is it yet possible? Not so far as I know, and I'm not aware of it being on the official plan of things to be fixed in the upcoming versions (either 2.2 or Mailman3), but certainly something that could potentially be done. Does that seem reasonable? I think so. It would reduce the probability of someone being able to guess the list approval password, which can sometimes leak out via unexpected channels. What are the drawbacks (those that would have significantly worse problems/weaknesses than existing mechanisms)? About the only thing I can think of that might be an issue would be that there would now be more data to manage, and of course the problem of feeping creaturism. If not yet possible, but acceptable in theory (perhaps with amendments), then we would hope to consider volunteering some effort into coding it. If you code such a feature (or have it done for you), and then upload that to the Mailman patch page on SourceForge at http://sourceforge.net/tracker/?group_id=103atid=300103, you would be much more likely to get this feature incorporated into a future version of Mailman. This isn't to say that you would be guaranteed to get this feature incorporated, as there are many patches which have been uploaded that have not found their way into the main code base. But uploading your patch would greatly increase your chances. -- Brad Knowles, [EMAIL PROTECTED] Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. -- Benjamin Franklin (1706-1790), reply of the Pennsylvania Assembly to the Governor, November 11, 1755 LOPSA member since December 2005. See http://www.lopsa.org/. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Versions? Roadmap?
David Lee wrote: Is there a Roadmap for future mailman releases? snip We could dabble in the possibility of contributing code to some of these. But any such work would need to be on something reasonably active with a realistic release schedule (we once, many years back, began doing things in Majordomo-2 only for that to stall and stall...). We would be glad to have your input and involvement. Please visit our new wiki at http://wiki.list.org/ which we hope will answer some of your questions. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Versions? Roadmap?
At 3:34 PM +0100 2006-05-15, David Lee wrote: Is there a Roadmap for future mailman releases? There is some information at http://www.list.org/devs.html, http://www.list.org/todo.html and http://www.zope.org/Members/bwarsaw/MailmanDesignNotes/FrontPage, but I think most of the recent activity has been over at http://wiki.list.org/homepage.action. The current version seems to be 2.1.8. Correct. And I imagine there might be a 2.1.9 sometime in the not-to-distant future. However I've seen talk in archives about a 2.2.x and a Mailman 3. Barry, Tokio, Mark and others have been talking about various things for various versions for a long time. Barry is primarily focused on Mailman3, but I believe that Tokio and Mark may have some stuff that they're looking at putting into a potential 2.2.x version that would be released sooner. I've found the Mailman-3-dev archives but that seems to have been dormant for nearly a year (since July 2005). Activity has been going on off-list (especially at sprints that are held at Python conferences), but the list itself has not been very active lately. I'm pretty sure that Barry has been swamped with his real job, and hasn't had a whole lot of time to document some of the work he's been doing. Although we are new (two weeks) to Mailman, we have a few queries about things we cannot find in 2.1.x. A Roadmap would show us (and other potential site-admins) what features might already be under consideration. Regretfully, when it comes to a clear roadmap for future versions, there's not much in the way of consolidated documentation that I know of. Basically, you bug Barry, Tokio, and/or Mark, and then one or the other gets around to updating some documentation somewhere as to what they currently have in mind, or maybe they just post something to the list and one of the non-developers (like me) gets to take that and try to turn that into some useful documentation somewhere. o true virtual hosting: same listname @ many domains; That is being worked on. There are people who have virtual hosting implementations that they have developed for themselves, and there's even a virtual host patch that has been uploaded to the SourceForge Mailman patch page. The patch is pretty old and not really a complete solution to the problem, but this is an area of active development by the community. My hope is that the next generation of this work will be completed soon and appropriate patches uploaded to the SourceForge pages, as well as being incorporated into an upcoming version of Mailman (either 2.1.9 or 2.2.x, depending on how massive the changes may be). o corporate branding of Mailman pages. There's a certain amount of this that can already be done by editing the page templates. I'd encourage you to search the FAQ Wizard and the archives of the list. There is a limit to how much you can do easily, however. The more extensive the changes you want, the more likely you are to need to make actual source code modifications to achieve the look you desire. We could dabble in the possibility of contributing code to some of these. If you want to talk about coding opportunities for Mailman, then the mailman-developers list may be a better place to do that. Operational questions are appropriate for mailman-users, but if you're talking about actual code that you've developed, that's the domain of mailman-developers. But any such work would need to be on something reasonably active with a realistic release schedule (we once, many years back, began doing things in Majordomo-2 only for that to stall and stall...). Mailman has not been as active as it could be, but with additional core developers being brought online, allowing Tokio and Mark to focus on the 2.x tree while Barry works on Mailman3, I think we've been doing a lot better. -- Brad Knowles, [EMAIL PROTECTED] Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. -- Benjamin Franklin (1706-1790), reply of the Pennsylvania Assembly to the Governor, November 11, 1755 LOPSA member since December 2005. See http://www.lopsa.org/. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] approval password linked to sender rather than list?
On Mon, 15 May 2006, Brad Knowles wrote: At 10:01 AM +0100 2006-05-15, David Lee wrote: Is there a facility, or plans for such, for each permitted sender to have (optionally) their own password, useable across many lists? This is a very good question. I'm glad you brought it to this list. I'm pretty sure that there is no facility in Mailman today to achieve what you're looking for. I see no problem with the concept, but I will let others answer the technical issues of how it might be done, etc Glad it seems reasonable. Thanks. If you haven't done so already, I would encourage you to file this as a Request For Enhancement on the Mailman SourceForge page at http://sourceforge.net/tracker/?group_id=103atid=350103. Thanks. Done. I'm not convinced that having per-user approval passwords would help the moderators act in a more consistent manner, but it certainly wouldn't hurt. Hm? The idea is that the genuine sender should be able to avoid moderation in the first place. As an aside, is there a way to do Approved: as a header (rather than as first line of message-body) if the client is Outlook? OWA? What are the drawbacks (those that would have significantly worse problems/weaknesses than existing mechanisms)? About the only thing I can think of that might be an issue would be that there would now be more data to manage, and of course the problem of feeping creaturism. Thanks. Being new to Mailman (although with (too) many years' worth of Majordomo behind me) I wanted to do a basic sanity-check of the idea itself. If not yet possible, but acceptable in theory (perhaps with amendments), then we would hope to consider volunteering some effort into coding it. If you code such a feature (or have it done for you), and then upload that to the Mailman patch page on SourceForge at http://sourceforge.net/tracker/?group_id=103atid=300103, you would be much more likely to get this feature incorporated into a future version of Mailman. Thanks. The big question is: which version should we base it on? We would be looking to put into into local production (assuming we did it) fairly soon, but also be looking to get it incorporated into future versions. So Mm 2.1.x? 2.2.x? How different are those two versions? (I'm assuming not 3.x because that seems to be some way off yet.) Thanks again. -- : David LeeI.T. Service : : Senior Systems ProgrammerComputer Centre : : Durham University : : http://www.dur.ac.uk/t.d.lee/South Road: : Durham DH1 3LE: : Phone: +44 191 334 2752 U.K. : -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] posts from members are not reaching to any of the subscribers on the list
Hi, I am facing huge problem with all my mailing lists. When any memeber posts a message to the list, neither they are reaching to any member nor the are bouncing back to the sender. They are simply getting lost somewhere. On the other hand if I set members moderation required flag ON then their posts are getting displays in the moderation list. And when I accept the post they reaching to the receipients. Any Ideas? Timely help in this would be greatly appreciated. Please help. __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] posts from members are not reaching to any of the subscribers on the list
On 5/15/06, hp [EMAIL PROTECTED] wrote: On the other hand if I set members moderation required flag ON then their posts are getting displays in the moderation list. And when I accept the post they reaching to the receipients. This means that the mails are at least reaching your mailman install. Check your vette logs, as well as error, and smtp-failure for any indications as to why the mails aren't being delievered. -- - Patrick Bogen -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Custom footer based on sender's email
Ok, I got this piece kind of working, but there is a problem with this.
This is my search and replace string, and the search at this point doesn't
matter.
pl = re.sub('lksjdfsdf', 'new text', pl)
Here is the last part of the body, it is all contained in one line:
You received this e-mail because you are currently subscribed to this
message board alert. To unsubscribe from this alert, or to change your
settings to receive a digest version instead, please visit My Alerts.
After this message goes through mailman, this is how it comes out on the
other side:
jZ;]yay%hh?hjfzjCj?k-yM:4r^=JjgV'qbs OyDKijljw, g Z,j
}z? Ox^=by?m+ m?y?+.n+a?Oy?zS? ~jWZ zb
-z+i?zozx?v^j??3 %zl
If I add, or remove a letter to the orginal footer, anywhere, or change any
one of the punctuation marks to a letter, it will come through clean, and
not garbled.
I am stumped!
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf
Of Mark Sapiro
Sent: Thursday, May 11, 2006 3:53 PM
To: mailman-users@python.org
Subject: Re: [Mailman-Users] Custom footer based on sender's email
Mark Sapiro wrote:
Rob Jackson wrote:
snip
+pl = msg.get_payload(decode=True)
+re.sub('AZ', 'new text', pl)
+msg.set_payload(pl)
snip
It looks OK to me.
Actually, it's not OK. I overlooked the fact that Python strings are
immutable and re.sub doesn't (can't) change them in place. Thus,
re.sub('AZ', 'new text', pl)
needs to be
pl = re.sub('AZ', 'new text', pl)
--
Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/robertj%40linux4free.co
m
Security Policy:
http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Security Policy:
http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] approval password linked to sender rather than list?
At 5:59 PM +0100 2006-05-15, David Lee wrote: I'm not convinced that having per-user approval passwords would help the moderators act in a more consistent manner, but it certainly wouldn't hurt. Hm? The idea is that the genuine sender should be able to avoid moderation in the first place. That's not what I was referring to. I was referring to the things that would wind up in the moderator queue (potentially due to lack of appropriate password), and how those might be handled in an inconsistent manner. Whether it's a per-sender approval password or a per-list approval password, once you're past the automated system and your post is approved, then the moderators aren't going to see or touch it. However, while I see some advantages to allowing this route as an optional alternative, I think the bigger problem is the inconsistency in the way the moderators will tend to handle the stuff that gets dumped into their queue. Unfortunately, I'm not sure there's much you can do to try to solve that part of the problem. ;) As an aside, is there a way to do Approved: as a header (rather than as first line of message-body) if the client is Outlook? OWA? I'm not familiar with those clients. Others on the list might be more familiar with them, but you might also want to see if there are other mailing lists, forums, FAQs, etc... that would be oriented towards the specific clients you're interested in. The big question is: which version should we base it on? Start with the latest current version -- 2.1.8. If the feature is going to be incorporated into a future version then Tokio, Mark, or Barry can do any necessary work that might be required to bring it into whatever version they're working on. But I would strongly encourage you to make sure you follow the same style and programming methods, so that the amount of work needed to integrate your suggested feature would be minimized. We would be looking to put into into local production (assuming we did it) fairly soon, but also be looking to get it incorporated into future versions. Understood. So Mm 2.1.x? 2.2.x? How different are those two versions? (I'm assuming not 3.x because that seems to be some way off yet.) I think 2.2.x is still in fairly formative stages right now, and anything that would be required to bring the code up from the 2.1.8 baseline to 2.2.x should be something that Tokio, Mark, or Barry can do as needed. -- Brad Knowles, [EMAIL PROTECTED] Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. -- Benjamin Franklin (1706-1790), reply of the Pennsylvania Assembly to the Governor, November 11, 1755 LOPSA member since December 2005. See http://www.lopsa.org/. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Custom footer based on sender's email
I found a fix the the problem. Charset is set to UTF-8, and I changed it to
us-ascii, and it works great now.
-Rob
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf
Of Rob Jackson
Sent: Monday, May 15, 2006 12:26 PM
To: 'Mark Sapiro'; mailman-users@python.org
Subject: Re: [Mailman-Users] Custom footer based on sender's email
Ok, I got this piece kind of working, but there is a problem with this.
This is my search and replace string, and the search at this point doesn't
matter.
pl = re.sub('lksjdfsdf', 'new text', pl)
Here is the last part of the body, it is all contained in one line:
You received this e-mail because you are currently subscribed to this
message board alert. To unsubscribe from this alert, or to change your
settings to receive a digest version instead, please visit My Alerts.
After this message goes through mailman, this is how it comes out on the
other side:
jZ;]yay%hh?hjfzjCj?k-yM:4r^=JjgV'qbs OyDKijljw, g Z,j
}z? Ox^=by?m+ m?y?+.n+a?Oy?zS? ~jWZ zb
-z+i?zozx?v^j??3 %zl
If I add, or remove a letter to the orginal footer, anywhere, or change any
one of the punctuation marks to a letter, it will come through clean, and
not garbled.
I am stumped!
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf
Of Mark Sapiro
Sent: Thursday, May 11, 2006 3:53 PM
To: mailman-users@python.org
Subject: Re: [Mailman-Users] Custom footer based on sender's email
Mark Sapiro wrote:
Rob Jackson wrote:
snip
+pl = msg.get_payload(decode=True)
+re.sub('AZ', 'new text', pl)
+msg.set_payload(pl)
snip
It looks OK to me.
Actually, it's not OK. I overlooked the fact that Python strings are
immutable and re.sub doesn't (can't) change them in place. Thus,
re.sub('AZ', 'new text', pl)
needs to be
pl = re.sub('AZ', 'new text', pl)
--
Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/robertj%40linux4free.co
m
Security Policy:
http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/robertj%40linux4free.co
m
Security Policy:
http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Security Policy:
http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] Can I change the to address?
I notice that when I send an email to my maillist, it list [EMAIL PROTECTED] as the to user in the email header. Can mailman list the to section in the email header to the person it's actually delivering to? IE: [EMAIL PROTECTED] - Steve -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Can I change the to address?
Steve Quezadas wrote: I notice that when I send an email to my maillist, it list [EMAIL PROTECTED] as the to user in the email header. Can mailman list the to section in the email header to the person it's actually delivering to? IE: [EMAIL PROTECTED] If you see the 'personalize' options on the admin Non-digest options page, you do this by setting 'Full Personalization'. If you don't see the option, it has to be enabled by the site by putting OWNERS_CAN_ENABLE_PERSONALIZATION = Yes in mm_cfg.py. I.e., if it is your Mailman installation, you can do this. If it is a hosted Mailman, it is up to the host whether or not to allow this because there are performance considerations. -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Versions? Roadmap?
On 5/15/06, David Lee [EMAIL PROTECTED] wrote: o corporate branding of Mailman pages. I have posted a patch,# 1415956, on Sourceforge (http://sourceforge.net/tracker/index.php?func=detailaid=1415956group_id=103atid=300103 ) that allows you to use a site-wide header and footer to customise the web interface. I haven't upload the patch for V 2.1.8, but you can see what it looks like in practice on 2.1.7 at http://databaseadvisors.com/mailman/listinfo -- Bryan Carbonnell - [EMAIL PROTECTED] Life's journey is not to arrive at the grave safely in a well preserved body, but rather to skid in sideways, totally worn out, shouting What a great ride! -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] postfix virtual aliases and mailman problem
Dear all experts I made new mail server based on postfix with mysql backend for users,aliases, domain. also courier imap for mda. using webmail as well. Everything works fine. nad i planned to use mailman as well as list manager. steps that i have done are: -install mailman 2.17 (rpm) - modify conf in main.cf - modify conf in httpd.conf -modify conf in mm_cfg.py - create new list call test - access the mailman website and modify test list ia web - add members in the list - send sample email to the list The last step, send sample email to the list, faild with following error: The Postfix program |/usr/lib/mailman/mail/mailman post test2@mail.tarra.com (expanded from [EMAIL PROTECTED]): unknown user: |/usr/lib/mailman/mail/mailman post test2 it seems postfix cannot understand the pipe. what can i do? please any advise Thank you Regards Marendra i include the configurations of postfix and mailman: postfix: == myhostname = mail.something mynetworks_style = host mynetworks = something relay_domains = something owner_request_special = no recipient_delimiter = + unknown_local_recipient_reject_code = 550 virtual_alias_maps = mysql:/etc/postfix/mysql_virtual_alias_maps.cf,hash:/etc/mailman/aliases,hash:/var/lib/mailman/data/virtual-mailman virtual_gid_maps = static:12345 virtual_mailbox_base = /usr/local/virtual virtual_mailbox_domains = proxy:mysql:/etc/postfix/mysql_virtual_domains_maps.cf virtual_mailbox_limit = 0 virtual_mailbox_maps = proxy:mysql:/etc/postfix/mysql_virtual_mailbox_maps.cf virtual_minimum_uid = 12345 virtual_transport = virtual virtual_uid_maps = static:12345 virtual_create_maildirsize = yes virtual_mailbox_extended = yes virtual_mailbox_limit_maps = proxy:mysql:/etc/postfix/mysql_virtual_mailbox_limit_maps.cf virtual_mailbox_limit_override = yes virtual_maildir_limit_message = Sorry, the user's maildir has overdrawn his diskspace quota, please try again later. virtual_overquota_bounce = yes relay_domains = proxy:mysql:/etc/postfix/mysql_relay_domains_maps.cf proxy_read_maps = $local_recipient_maps $mydestination $virtual_alias_maps $virtual_alias_domains $virtual_mailbox_maps $virtual_mailbox_domains $relay_recipient_maps $relay_domains $canonical_maps $sender_canonical_maps $recipient_canonical_maps $relocated_maps $transport_maps $mynetworks $virtual_mailbox_limit_maps smtpd_recipient_restrictions = permit_mynetworks,reject_unknown_sender_domain, reject_unauth_destination,reject_unlisted_recipient, reject_invalid_hostname mmcfgpy from socket import * try: fqdn = getfqdn() except: fqdn = 'mm_cfg_has_unknown_host_domains' DEFAULT_URL_HOST = fqdn DEFAULT_EMAIL_HOST = fqdn # Because we've overriden the virtual hosts above add_virtualhost # MUST be called after they have been defined. add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) POSTFIX_STYLE_VIRTUAL_DOMAINS = ['mail.something'] Send instant messages to your online friends http://uk.messenger.yahoo.com -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
