Since Barry suggested that conversation about improving the mailman GUI
should be moved here, I thought I'd take a minute to ask a couple
First, let me say, that I'm willing to do some of the work on this part
of the project. In the organization I work for (and run mailman for) the
biggest complaints I hear revolve around the interface, and the lack of
control over the design, so I'd love to see a proper template system in
That said, I'm not clear where this project stands. I've been reviewed
the summary from last summer's SoC work, and while that's given me some
idea of what was done, I don't have a good sense of how and where to get
started on helping. Can you all offer some suggestions about what I can
do to be helpful and contribute?
-----BEGIN PGP SIGNED MESSAGE-----
I just started a wiki page to collect thoughts about improving
logging in the next version of Mailman. Please feel free to comment
in the page if you have specific goals for improved logging.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
-----END PGP SIGNATURE-----
I am resending this email, as well as to the other mailing lists, since
I have received zero feedback since sending the original over two weeks ago.
Should I assume there is no interest in this translation, and just keep
it for my own sites?
ציטוט Dov Zamir:
> ציטוט Barry Warsaw:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>> It's probably best to open a patch issue on SourceForge and attach
>> your .po file to the patch. Then send a link to that issue here.
>> One of us will pull it into svn from there.
> I have just uploaded the Hebrew translation files to Sourceforge as
> issue number 1696053. Here is the attached description:
> Attached are the Hebrew files for Mailman 2.1.9
> I added a parameter to the LC_DESCRIPTION function, and these are the
> that are affected by the addition of 'direction' to the 'LC_DESCRIPTION'
> function. They have been changed, and diffs are attached...
> Likewise, all translation files are attached.
> There is still a problem displaying command line output in the correct
> direction. Still looking for a solution...
> Mailman-i18n mailing list
> Posts: Mailman-i18n(a)python.org
> Unsubscribe: http://mail.python.org/mailman/options/mailman-i18n/linux%40zamirfamily.com
I'm trying to write a script to determine what lists have users that
have moderation turned on. I found the following example in the list
archives using the withlist command
from Mailman import mm_cfg
for member in m.getMembers():
if m.getMemberOption(member, mm_cfg.Moderate):
However when I run the command:
withlist -q -r checkModerated.py jww_test
I get the following error:
Traceback (most recent call last):
File "/home/mailman/bin/withlist", line 297, in ?
File "/home/mailman/bin/withlist", line 269, in main
func = getattr(mod, callable)
AttributeError: 'module' object has no attribute 'py'
This seems pretty simple to me, but I don't have any python experience,
this is my first brush with python. I do know perl, java and assorted
other programming languages but you have to start somewhere when
learning something new. Any help would be appreciated. Or you can
forward this to your co-workers to make fun of the n00b.
Principal Systems Engineer - Messaging Infrastructure
DHL Worldwide Express - AMIS
8701 East Hartford Drive
Scottsdale, AZ 85255
This particular problem is caused by a bug in email 4.0.1 package which
was fixed in the most recent subversion repository.
Maybe it's time to think of next bug fix release of mailman 2.1.10 as
soon as the email 4.0.2(?) is out.
Justin Warren wrote:
> Hi folks,
> I hit the same sort of problem as a couple of other people apparently
> have, eg:
> I hit this when Mailman attempts to send digests.
> I thought I'd tracked the issue to the way Charset is used within
> Mailman/Scrubber.py, on line 193 (some modifications by me to print
> debug output):
> charset = None
> lcset = Utils.GetCharSet(mlist.preferred_language)
> print "getting charset for preferred language:", repr(lcset)
> lcset_out = Charset(lcset).output_charset or lcset
> print "lcset_out is:", repr(lcset_out)
> Which yields:
> getting charset for preferred language: 'us-ascii'
> lcset_out is: u'us-ascii'
> It appears that Charset returns a unicode string for
> its .output_charset, which python2.4 email.Message.set_charset() does
> not recognise as a string, and it isn't a Charset either, so a TypeError
> is raised.
> I don't know enough about why .output_charset is being used, or why it
> is unicode, but it seems that changing line 193 to read:
> lcset_out = Charset(lcset) or lcset
> would prevent this error.
> However, something else is also returning a unicode string, since after
> changing Scrubber, you end up with this error:
> Traceback (most recent call last):
> File "/usr/lib/mailman/cron/senddigests", line 94, in ?
> File "/usr/lib/mailman/cron/senddigests", line 86, in main
> File "/var/lib/mailman/Mailman/Digester.py", line 60, in send_digest_now
> ToDigest.send_digests(self, mboxfp)
> File "/var/lib/mailman/Mailman/Handlers/ToDigest.py", line 142, in send_digests
> send_i18n_digests(mlist, mboxfp)
> File "/var/lib/mailman/Mailman/Handlers/ToDigest.py", line 339, in send_i18n_digests
> mcset = msg.get_content_charset('')
> File "/usr/lib/python2.4/email/Message.py", line 805, in get_content_charset
> charset = unicode(charset, 'us-ascii').encode('us-ascii')
> TypeError: decoding Unicode is not supported
> I haven't worked out what this other thing is as yet.
> Alternately, patching email/Message.py (line 803) to ignore a charset
> that is a unicode string seems to work, but is probably fragile or
> broken in other ways:
> # charset character must be in us-ascii range
> if not isinstance(charset, unicode):
> charset = unicode(charset, 'us-ascii').encode('us-ascii')
> except UnicodeError:
> return failobj
> I hope this helps someone more knowledgable about Mailman to work out
> what the underlying problem is.
Tokio Kikuchi, tkikuchi(a)is.kochi-u.ac.jp
Dear Mailman Developers,
I am looking to put together a team for Kwotidian.com, a
startup which will create and distribute bilingual language
development email. Kwotidian will use Mailman and we need 1-3
persons to handle the technical side.
The idea for Kwotidian began with a company named Wordburger in
1999. Wordburger sent out bite-size, witty, bilingual language
lessons. Subscribers learned a few useful English words each
day. Wordburger grew rapidly to 140,000 subscribers who wanted
to learn or improve their English, 95% of whom were in non-English
speaking countries. Our most successful edition was the
Chinese, with 55,000 subscribers. We shut down in 2001 because
our primary revenue model at that time was advertising and the
reputation of internet advertising had gone down the drain. Now
we intend to try again. The goal is not to have hundreds of
thousands of subscribers - it is to have millions of subscribers.
Kwotidian.com needs a small team whose essential ingredient is
enthusiasm and energy. Mailman and html experience would be
good and experience with international character set encodings would
be desirable but not essential.
Kwotidian is not yet operational but the basic idea and a
sample Kwotidian daily message can be seen at kwotidian.com.
Please get in touch with me if you are interested. I will be
glad to provide more details.
Williamstown, Massachusetts USA
First of all, thanks for this great system !!
The templates pages and other generated one have integrated design
I propose to transform html pages with "div" formatting to separate code and
Example in joint- files
On the other hand, has anyone thought of transformation of the mails into XML
files storage (piped postfix posting as it actually is) ?
We could then transform them into XHTML with XSLT, to have a forum-like
archives browsing, [or to have a blog system (with comments posting)],
keeping the mailing-list feature.
I think you already thought of that.