> If you want something done, and there isn't anyone who has the time,
> skills or inclination to do it for you, then you either knuckle down and
And how could I know that there isn't anyone, huh?
> do it yourself, or forget about it. You don't keep hounding someone else
> to do it.
You are rude. Look what you've just written. You seem to have contempt
for users of the program, and that's a very bad thing. Is the mailman for
the users or the users for the mailman? There are developers, and users,
users can make their wishlist, and developers could see what they can do.
If someone can do a patch himself, that's good, but if someone cannot,
then telling him to shut up, because he cannot do it himself is just rude
and silly.
ak
[sourceforge seems to be down, so I post this here]
Hi there,
We developped a reliable solution for running lists with the same name
on different domains on the same Mailman installation.
I implemented that on top of the Mailman 2.1.1-5.1 Debian stable
package. All that is needed is to patch 2 files (bin/newlist,
Mailman/MailList.py) in the mailman install, and here is the patch:
http://bugs.koumbit.net/file_download.php?file_id=3&type=bug
There's only one caveat right now: Mailman/Cgi/create.py might need to
get patched too, but I haven't got around looking at it yet, and it
"just works", for now.
I don't know what's the current status of virtual hosting support on
Mailman, but this patch is a simple hack that should bring joy in the
homes of all Mailman admins around the world. :)
I got my inspiration and part of the code from:
http://mithrandr.moria.org/blog/139.html
All it does is to add the domain to the internal_name() of a list. The
real_name is kept as is, and the getListAddress() does the Right Thing.
This makes Mailman generate aliases like:
list-example.com: "|/var/lib/mailman/mail/mailman post list-example.com"
Care will have to be taken on the MTA side to map those list-example.com
to list(a)example.com. We are using alternc.org to manage our server, so
we are using LDAP, so everything went pretty smoothly. :) But I guess it
will require some magic on the Postfix side or something...
Cheers,
A.
PS: for those wanting to see more, you can come to our Wiki:
http://koumbit.net/wiki/VirtualMailman
You'll probably have a little trouble finding your way if you don't
read french though. :) Babelfish might help, haven't tried.
----- End forwarded message -----
Hi,
I have a few subscribers who use the "not metoo" setting in mailman...
but apparently since a few upgrades (i'm now running 2.1.4), it doesn't
work anymore: they *do* get their own posts. I tried it myself and I can
confirm that if I set my subscription to "not metoo", I get my own post
anyway (yes my email adddress is exactly the same as the one i'm
subscribed with).
Anybody here who experiences the same problem with 2.1.4?
or do I need to start digging in the code? :)
TIA,
Ricardo.
Hello,
I have an "interesting" on some mailinglist. All mails to this list get shunted with the
error message: LookupError: unknown encoding: X-UNKNOWN
This only happens when digestable is set to true. The funny thing about this, that
I cannot figure out when this error occurs. It is only reproduceable on some lists.
- Not all lists with the digestable=1 have this phenomen, in fact only a few have it
- The problem is indepented from the mailer I use. Other lists work fine with all tested mailers
- The listowner told me that he didn't change the digestable option when mails stopped
arriving at the list (he just changed the archive from public to private).
- The list worked fine for some month before it "stopped working" at the beginning of april
- Updating mailman to 2.1.4 and several restarts didn't help
- There were no lockfiles that could have caused this problem
- Skimming the code in Scrubber.py und Message.py didn't help me.
- My current "hotfix" is to disable the digest option on the affected lists. But this cannot
be the solution forever....
My setup is a gentoo-linux box with mailman-2.1.4 and python-2.3.3
I have absolutely no clue how this problem was introduced to my system an why it
is just limited to some list.
There is a (quite old) bugreport about this problem from another guy:
http://sourceforge.net/tracker/index.php?func=detail&aid=803729&group_id=10…
but there's now hint there were the problem lies.
I hope you give a hint were to look for the source of this problem. Mainly I just want to
understand what's going on here.
Here's the excerpt from my error log:
Apr 26 18:27:05 2004 (17449) Uncaught runner exception: unknown encoding: X-UNKNOWN
Apr 26 18:27:05 2004 (17449) Traceback (most recent call last):
File "/usr/local/mailman/Mailman/Queue/Runner.py", line 110, in _oneloop
self._onefile(msg, msgdata)
File "/usr/local/mailman/Mailman/Queue/Runner.py", line 160, in _onefile
keepqueued = self._dispose(mlist, msg, msgdata)
File "/usr/local/mailman/Mailman/Queue/IncomingRunner.py", line 130, in _dispose
more = self._dopipeline(mlist, msg, msgdata, pipeline)
File "/usr/local/mailman/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline
sys.modules[modname].process(mlist, msg, msgdata)
File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 91, in process
send_digests(mlist, mboxfp)
File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 132, in send_digests
send_i18n_digests(mlist, mboxfp)
File "/usr/local/mailman/Mailman/Handlers/ToDigest.py", line 306, in send_i18n_digests
msg = scrubber(mlist, msg)
File "/usr/local/mailman/Mailman/Handlers/Scrubber.py", line 265, in process
url = save_attachment(mlist, part, dir)
File "/usr/local/mailman/Mailman/Handlers/Scrubber.py", line 361, in save_attachment
fnext = os.path.splitext(msg.get_filename(''))[1]
File "/usr/local/mailman/pythonlib/email/Message.py", line 714, in get_filename
return unicode(newvalue[2], newvalue[0] or 'us-ascii')
LookupError: unknown encoding: X-UNKNOWN
Apr 26 18:27:05 2004 (17449) SHUNTING: 1082996756.746207+e85fdb8b141ccd2a8f0757824f62fbff58
da2ce4
--
Gregor Maier
Fachschaft Mathe/Phys/Info
Computerreferat
I've just uploaded Mailman 2.1.5 release candidate 2 (no, you never saw
rc1 :). Since there are some fairly significant changes with this
version, I felt it was necessary to put out a release candidate to
hopefully prompt some additional testing.
If you're able to test the new version, that would be great, but please
note that:
* The file format for on-disk messages in the qrunners has
changed. Until now, each queued message was represented by two
files, a .msg and a .pck file. With this version, all
information is kept in the .pck file. This improves stability
and performance. The upgrade script will attempt to convert all
your existing .msg/.pck files to the single .pck file, but there
may still be lurking problems with this conversion.
* The pending database has been changed from a global pickle file
living in $prefix/data, to a unique pickle file per mailing
list. The upgrade script attempts to determine which list each
pending request belongs to, but it isn't always possible to
know, so while it does the best it can, there may still be
lurking problems with this conversion.
If you upgrade you should do so only on a quiet system. I recommend
shutting down Mailman, your MTA, and your web server before doing the
upgrade. Please note any problems you have with the conversion scripts
(you may want to make backups first ;).
My thanks for not letting the above discourage you from testing the new
version. :) I think the improvements in 2.1.5 are worth it, and based
on experiences running python.org, the new version should be quite
stable once installed.
I plan to release 2.1.5 final sometime next weekend.
-Barry
Howdy. I did my best to find this in all of the FAQs, online docs, INSTALL
and UPGRADE readmes (which are somewhat out of date) and had no luck.
I just upgraded to 2.14 of Mailman which of course stomped on my nice archive
templates which linked to my swish-e searching amongst other things. I've
tried editing things in /usr/local/mailman/templates/ but so far these have
not taken effect so I am missing something or pipermail is not looking where
I think it is looking.
Last time I had to mess with the templates was a long way back so I have
forgotten what was required exactly. Since the docs don't help and changing
stuff like "archidxhead.html" seems to have no effect, I am asking here.
=)
An expletive or two in my direction followed by directions to where this is
documented would be appreciated.
Cheers
Companies are now starting to block Mailman lists (among others)
because of the way the headers are sent out stating the hand-off to
the server:
Received: from localhost.localdomain ([127.0.0.1]
helo=mail.python.org)
by mail.python.org with esmtp (Exim 4.22)
id 1BH7Kx-0001vz-7S; Fri, 23 Apr 2004 16:31:51
-0400
Anything with that format - they are marking as "probable SPAM"
Any thoughts on how to zap?
Also, as I mine is an announce only list - it would be nice to be able
to zap the other received from headers and show the message as
coming directly from the server. One webmail program does it - but
it cannot send HTML.
Received: from localhost.localdomain ([127.0.0.1]
helo=mail.python.org)
by mail.python.org with esmtp (Exim 4.22)
id 1BH7Kx-0001vz-7S; Fri, 23 Apr 2004 16:31:51
-0400
Received: from mydomain.com ([111.111.11.111])
by mail.python.org with esmtp (Exim 4.22) id
1BH7Ko-0001tP-Ph
for mailman-users(a)python.org; Fri, 23 Apr 2004
16:31:42 -0400
BTW - usim exim as MTA.
Thanks.
Lloyd F. Tennison
lloyd_tennison(a)whoever.com
No trees were harmed in the transmission of this
message.
However, a rather large number of electrons were
temporarily
inconvenienced.
What client
----- Original Message ---------------
>Return-Path: <mailman-coders-bounces(a)python.org>
>Received: from spf6.us4.outblaze.com (205.158.62.33) by mta4.wss.scd.yahoo.com (7.0.016)
> id 408811160004A6AD for lloyd(a)danandben.com; Thu, 22 Apr 2004 21:47:55 -0700
>Received: from mail.python.org (mail.python.org [12.155.117.29])
> by spf6.us4.outblaze.com (Postfix) with ESMTP id 4C491539A7
> for <lloyd_tennison(a)whoever.com>; Fri, 23 Apr 2004 04:43:34 +0000 (GMT)
>Received: from localhost.localdomain ([127.0.0.1] helo=mail.python.org)
> by mail.python.org with esmtp (Exim 4.22)
> id 1BGsbS-0004aP-VI; Fri, 23 Apr 2004 00:47:54 -0400
>Received: from sc8-sf-sshgate.sourceforge.net ([66.35.250.220])
> by mail.python.org with esmtp (Exim 4.22) id 1BGsbQ-0004VZ-Ac
> for mailman-coders(a)python.org; Fri, 23 Apr 2004 00:47:52 -0400
>Received: from sc8-sf-web4-b.sourceforge.net ([10.3.1.24]
> helo=sc8-sf-web4.sourceforge.net)
> by sc8-sf-sshgate.sourceforge.net with esmtp (Exim 3.36 #1 (Debian))
> id 1BGsbP-000831-00; Thu, 22 Apr 2004 21:47:51 -0700
>Received: from nobody by sc8-sf-web4.sourceforge.net with local (Exim 3.36 #1
> (Debian)) id 1BGsbP-0003Eh-00; Thu, 22 Apr 2004 21:47:51 -0700
>To: noreply(a)sourceforge.net
>From: "SourceForge.net" <noreply(a)sourceforge.net>
>Mime-Version: 1.0
>Content-Type: text/plain; charset="ISO-8859-1"
>Message-Id: <E1BGsbP-0003Eh-00(a)sc8-sf-web4.sourceforge.net>
>Date: Thu, 22 Apr 2004 21:47:51 -0700
>X-Spam-Status: OK (lists-mailman 0.000)
>Cc:
>Subject: [ mailman-Bugs-940497 ] substitute poster's address but keep name
>X-BeenThere: mailman-coders(a)python.org
>X-Mailman-Version: 2.1.5b1
>Precedence: list
>Reply-To: mailman-developers(a)python.org
>List-Id: Mailman list for bug and patch messages <mailman-coders.python.org>
>List-Unsubscribe: <http://mail.python.org/mailman/listinfo/mailman-coders>,
> <mailto:mailman-coders-request@python.org?subject=unsubscribe>
>List-Archive: <http://mail.python.org/pipermail/mailman-coders>
>List-Post: <mailto:mailman-coders@python.org>
>List-Help: <mailto:mailman-coders-request@python.org?subject=help>
>List-Subscribe: <http://mail.python.org/mailman/listinfo/mailman-coders>,
> <mailto:mailman-coders-request@python.org?subject=subscribe>
>Sender: mailman-coders-bounces(a)python.org
>Errors-To: mailman-coders-bounces(a)python.org
>
>Bugs item #940497, was opened at 2004-04-23 04:47
>Message generated for change (Tracker Item Submitted) made by Item Submitter
>You can respond by visiting:
>https://sourceforge.net/tracker/?func=detail&atid=100103&aid=940497&group_i…
>
>Category: security/privacy
>Group: 2.1 (stable)
>Status: Open
>Resolution: None
>Priority: 5
>Submitted By: Pierre Abbat (phma)
>Assigned to: Nobody/Anonymous (nobody)
>Summary: substitute poster's address but keep name
>
>Initial Comment:
>I was on a list that uses the feature in which the poster's
>From: header is replaced with the list address to prevent
>spammers from harvesting addresses. Unfortunately, this
>makes it impossible, in the second pane of my mail client, to
>see who said what. I suggest substituting only the address,
>leaving the name intact. For example:
>From: Ellie Vator <l.e.vator(a)otis.com>
>To: foo(a)bar.baz
>should become
>From: Ellie Vator <foo(a)bar.baz>
>To: foo(a)bar.baz
>and
>From: l.e.vator(a)otis.com (Ellie Vator)
>should become
>From: foo(a)bar.baz (Ellie Vator)
>..
>
>----------------------------------------------------------------------
>
>You can respond by visiting:
>https://sourceforge.net/tracker/?func=detail&atid=100103&aid=940497&group_i…
>
>_______________________________________________
>Mailman-coders mailing list
>Mailman-coders(a)python.org
>http://mail.python.org/mailman/listinfo/mailman-coders
Hello,
since the site configuration file mm_cfg.py - typically located in
/usr/lib/mailman/Mailman/mm_cfg.py or /usr/local/mailman/Mailman/mm_cfg.py - is
a configuration file, I would like to move it to a configuration or state
directory like /etc or /var to be LSB conform.
Is there some easy support for this in Mailman ?
--
Heiko Rommel rommel(a)suse.de
SUSE Linux AG, Maxfeldstr. 5, D-90409 Nuernberg
T: +49 (0) 911 74053 0 F: +49 (0) 911 741 77 55
Hello all,
I'm installing Mailman 2.1.2 from the RedHat 9 source RPM and can't seem to
access any of the web scripts. I've included various results below; does
anyone have any suggestions as to how I might resolve this issue? Thanks,
Ned
---
[ned@sven bin]$ ls -l /var/log/mailman
total 15
-rw-rw-r-- 1 mailman mailman 322 Apr 22 18:43 error
-rw-rw-r-- 1 mailman mailman 1260 Apr 21 13:29 post
-rw-rw-r-- 1 mailman mailman 7065 Apr 22 18:55 qrunner
-rw-rw-r-- 1 mailman mailman 2063 Apr 22 18:55 smtp
-rw-rw-r-- 1 mailman mailman 728 Apr 21 13:29 smtp-failure
-rw-rw-r-- 1 root mailman 193 Apr 21 11:42 subscribe
[ned@sven bin]$ pwd
/var/mailman/bin
[ned@sven bin]$ sudo ./check_perms
No problems found
[ned@sven bin]$
---
Bug in Mailman version 2.1.2
We're sorry, we hit a bug!
If you would like to help us identify the problem, please email a copy of
this page to the webmaster for this site with a description of what
happened. Thanks!
Traceback:
Traceback (most recent call last):
File "/var/mailman/scripts/driver", line 68, in run_main
immediate=1)
File "/var/mailman/Mailman/Logging/StampedLogger.py", line 52, in __init__
Logger.__init__(self, category, nofail, immediate)
File "/var/mailman/Mailman/Logging/Logger.py", line 49, in __init__
self.__get_f()
File "/var/mailman/Mailman/Logging/Logger.py", line 67, in __get_f
1)
File "/usr/lib/python2.2/codecs.py", line 496, in open
file = __builtin__.open(filename, mode, buffering)
IOError: [Errno 13] Permission denied: '/var/log/mailman/error'
Python information:
VariableValue
sys.version 2.2.3 (#1, Aug 8 2003, 08:44:02) [GCC 3.2.3 20030502 (Red Hat
Linux 3.2.3-13)]
sys.executable /usr/bin/python
sys.prefix /usr
sys.exec_prefix /usr
sys.path /usr
sys.platform linux2
Environment variables:
VariableValue
HTTP_COOKIE PHPSESSID=3466d0405189bbc9ac394ef34b4bea73
SCRIPT_FILENAME /var/mailman/cgi-bin/listinfo
PYTHONPATH /var/mailman
SERVER_SOFTWARE Apache/2
SERVER_ADMIN webmaster(a)spflrc.org
SCRIPT_NAME /mailman/listinfo
SERVER_SIGNATURE
REQUEST_METHOD GET
HTTP_HOST www.spflrc.org
SERVER_PROTOCOL HTTP/1.1
QUERY_STRING
REQUEST_URI /mailman/listinfo
HTTP_ACCEPT */*
HTTP_USER_AGENT Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en)
AppleWebKit/137 (KHTML, like Gecko) Safari/137
HTTP_CONNECTION keep-alive
SERVER_NAME www.spflrc.org
REMOTE_ADDR 17.213.14.246
REMOTE_PORT 54326
HTTP_ACCEPT_LANGUAGE en, ja;q=0.92, ja-jp;q=0.96, fr;q=0.88, de-de;q=0.85,
de;q=0.81, es;q=0.77, it-it;q=0.73, it;q=0.69, nl-nl;q=0.65, nl;q=0.62,
sv-se;q=0.58, sv;q=0.54, no-no;q=0.50, no;q=0.46, da-dk;q=0.42, da;q=0.38,
fi-fi;q=0.35, fi;q=0.31
SERVER_PORT 80
GATEWAY_INTERFACE CGI/1.1
HTTP_ACCEPT_ENCODING gzip, deflate;q=1.0, identity;q=0.5, *;q=0
SERVER_ADDR 66.220.29.254
DOCUMENT_ROOT /var/www/html