We often *have* the answers in the FAQ, people aren't always finding
them there, often because it hasn't occurred to them to look.
I was mentioned this to the last person who I helped with a Mailman
problem, and he offered this brilliant suggestion: Why don't we print
the FAQ (or at least the wiki link) with error messages generated by
mailman?
Just a quick "For more information on this error, consult the
documentation at http://wiki.list.org/x/Bw" or something along those lines.
I know, it's another line of work for the translators, and it won't
solve the problems that aren't heralded by error messages, but hopefully
it'll result in more people actually finding the information they need
on their own!
Terri
Hello
Is anyone working on the subject ?
can anyone suggest approaches, I'm pretty new to mailman's code
I know the its considered impossible, and that html messages are
considered bad, but there is no other way to format, for example
, bidi languages in non-html emails,
and listserv, for example, can embed link (e.g : unsubscribe) in the
footer of an html message (AFAIK)
I'd like to implement this, I think it shouldn't be that hard, and would
work in most cases.
--
Asaf Ohaion
Lingnu Open Source Consulting Ltd.
http://www.lingnu.com
Barry,
I am collecting information for my work on the MM3 Webinterface while we meet
at PyCon 2009 sprint.
So far I have found the "Summer of Code summary"
<http://wiki.list.org/display/DEV/2006/08/20/Summer+of+Code+summary>.
Any other information/writing I should collect and read before we meet?
I also believe I had seen a page where you (?) had noted a link for a design
you favoured, but I can't find it. Can you post the link or come up with a
list of sites you like? (Not that we weren't able to develop design. I just
want to get an idea.).
Thanks,
p@rick
--
state of mind
Agentur für Kommunikation, Design und Softwareentwicklung
Patrick Koetter Tel: 089 45227227
Echinger Strasse 3 Fax: 089 45227226
85386 Eching Web: http://www.state-of-mind.de
Amtsgericht München Partnerschaftsregister PR 563
Would any Mailman experts like to help me out with a bit better
Mailman/SpamBayes integration at the PyCon sprints? I plan to be there just
a couple days. I was able to integrate SpamBayes into gate_news, but there
is no user interface for training and no direct integration into other parts
of SpamBayes. (SpamBayes is invoked on mail.python.org long before mail
messages get to Mailman.)
So, would anyone be interested in at least being a subject matter expert on
the Mailman site of things?
--
Skip Montanaro - skip(a)pobox.com - http://www.smontanaro.net/
Is there any reason why there need to be two login screens?
One for regular users and another one for moderatores/admin?
p@rick
--
state of mind
Agentur für Kommunikation, Design und Softwareentwicklung
http://www.state-of-mind.de
Franziskanerstraße 15 Telefon +49 89 3090 4664
81669 München Telefax +49 89 3090 4666
Amtsgericht München Partnerschaftsregister PR 563
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
There is an internal inconsistency in the 3.0.2 email package that
shipped with Python 2.4.4 through 2.4.6. This has to do with the
Charset.Charset() constructor setting input_charset to a unicode which
then causes TypeError: decoding Unicode is not supported exceptions in
other parts of the email package. This problem does not seem to occur
with email 3.0.1 and Python 2.4.[123].
This (along with other stuff) is discussed in the bug report at
<https://bugs.launchpad.net/mailman/+bug/328353> and there is a patch
for email/Charset.py at
<http://launchpadlibrarian.net/23670138/Charset.py.patch>
At this point, the best advice seems to be use Python 2.5 or 2.6 with
Mailman 2.1.12.
- --
Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (MingW32)
iD8DBQFJvpFfVVuXXpU7hpMRAt1PAKDJ6BY84Fx271paX1m4BrtUikMFvQCePbyg
8xyRMCTeV2GB5v0ZZhjCf7E=
=ji8z
-----END PGP SIGNATURE-----
Mailman Developers,
I've recently sent the one or the other mail to this mailing list concerning
Mailman and Postfix as well as development of a new web interface for MM3.
You might have wondered who I am and why I started posting to the MM developer
list without any introduction. Please let me make up for this now.
My name is Patrick Ben Koetter. People who use Postfix may now my name from my
involvement in the Postfix community. At LISA'07 I was asked by Brad Knowles
to join the Python postmaster team, which I did a few months ago.
This involved introducing myself to Barry and we started talking about MM3
development, the webinterface, the plan for a REST client/server architecture
etc.
To cut things short we - my business partner Andreas and Florian, who's been
working with us for years - will attend the Mailman sprint at Pycon 2009. The
plan is to introduce us to MM3 code and architecture and start to develop a
new web interface based on a REST client/server architecture.
Andreas and Florian will focus on programming and I will work on the web
interface, documentation etc.
I hope this gives an idea what our motivation is about and why you (hopefully)
are going to see more posts from us to this list in the next time.
To start let me ask you for your input on MM3 web interface plans. Barry told
me several plans/feature/wish lists have been written and that he would like
them to be the base for further development.
So far I have found the following links:
<http://wiki.list.org/display/DEV/Web+Interface>
<http://wiki.list.org/display/DEV/REST+Interface>
Do you know of more?
Thanks,
p@rick
P.S.
We hope to meet all of you at Pycon 2009!
--
state of mind
Agentur für Kommunikation, Design und Softwareentwicklung
http://www.state-of-mind.de
Franziskanerstraße 15 Telefon +49 89 45227227
81669 München Telefax +49 89 45227226
Amtsgericht München Partnerschaftsregister PR 563
Hi,
Thanks to the NLnet foundation, the Secure List Server project (
http://non-gnu.uvt.nl/mailman-pgp-smime/ ) , which is including OpenPGP and
S/MIME support in Mailman has released a much improved mailman-pgp-smime patch:
http://non-gnu.uvt.nl/pub/mailman/mailman-2.1.11-pgp-smime_2009-01-02.patch…
. See http://non-gnu.uvt.nl/mailman-pgp-smime/NEWS.PGP-SMIME for the details.
There'll be talks about this patch:
On monday january 12 I'll talk at the Chaos Seminar</a> in Ulm, Germany,
see http://ulm.ccc.de/ChaosSeminar/2009/01_Mailman_PGP_SMIME .
On sunday february 8th, 10h20 (probably), I'll give a lightning talk at the
FOSDEM conference, ULB Campus Solbosch, Brussels, Belgium. See
http://fosdem.org/2009/node/164.
The talk will start with a very short overview of the history of Mailman and
the mailman-pgp-smime project. Some remarks will be made on how to install and
configure the software, so that one can try it. Currently supported features
will be mentioned, as well as an overview of development plans. One will learn
how to contribute to the project; an overview of the revision control system
used will be given. Some remarks on the future of the patch will be made: will
it be shipped with Mailman itself?
If you have used Mailman, both as a subscriber and as a list admin, and if
you know what PGP and S/MIME are, you should definitely attend this talk.
Hope to meet you there!
Bye,
Joost
--
irc:joostvb@{OFTC,freenode} ∙ http://mdcc.cx/ ∙ http://ad1810.com/
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
As you know, Mailman 2 can filter the content of a message before it's
forwarded on to the list membership. It can reorganize the MIME
structure of a message, based on settings for MIME type and file
extension.
The rules are fairly complex though:
* If the outer MIME type or file extension matches a filter pattern,
the entire message is disposed of.
* If there are pass filters and the outer MIME type or file extension
does not match a pass filter, the message is disposed of.
* If a subpart's MIME type or file extension matches a filter pattern,
that part is disposed of.
* If there are pass filters and a subpart's MIME type or file
extension does not match a pass filter, the subpart is disposed of.
* After all that, multipart/alternatives can be collapsed.
* After all that, text/html parts can be converted to text/plain
* After all that, if the outer message's body is empty and it has
exactly one subpart, the subpart "becomes" the outer part.
Disposal of messages can be one of:
* Reject the message to the original author
* Forward the message to the list owner and discard
* Preserve the message in the 'bad' queue and discard
The Zen of Python says:
"Complex is better than complicated."
"If the implementation is hard to explain, it's a bad idea."
and I think the implementation is both complicated and hard to
explain, and the u/i is no model of comprehension. I'm not entirely
sure how people use this feature though.
Some of the python.org lists have pass-types allowing multipart/mixed,
multipart/alternative and text/plain, while filtering out various file
extensions.
So I'd like to solicit your input on how you use the feature, and if
you have any ideas for an approach that would be easier to understand,
more useful, or both.
Barry
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Darwin)
iEYEARECAAYFAkmsFQ4ACgkQ2YZpQepbvXEIAACffKwhPLRK4hIbJ7Hs2Cfsitjk
xr8An1RqTVblud9OipgfanywU3Wr8kWV
=E7Nw
-----END PGP SIGNATURE-----