Submitted yesterday as Bug 961587.
Mailman 2.1.5, upgraded from 2.1.4.
Three different lists on the same server exhibit similar behaviour.
One list gets admin notices daily that there are -1 messages in the
moderator queue, when there are none displayed on the admindb page.
Two other list gets admin notices daily that there are 1 messages in
the moderator queue, when there are none displayed. For one list, I
have rmlist'd it and re-created it, to no avail.
Please advise.
Thanks,
Matt
--
Matt Domsch
Sr. Software Engineer, Lead Engineer
Dell Linux Solutions linux.dell.com & www.dell.com/linux
Linux on Dell mailing lists @ http://lists.us.dell.com
The MIME policies on here are ridiculous. I'm not going to jump through
50 hoops just to post a stupid small patch. And I'm not going to stop
signing my email either.
*sigh*,
--
The best we can hope for concerning the people at large is that they
be properly armed. -- Alexander Hamilton
-- Eric Hopper (hopper(a)omnifarious.org http://www.omnifarious.org/~hopper) --
It's really annoyed me that I can't create a list alias domain, like
lists.omnifarious.org and still be able to refuse mail to
list-name(a)omnifarious.org
So, I created a small patch to Mailman.MTA.Postfix that allows you to
specify a prefix to be applied to all virtually hosted lists that show
up in the omnifarious.org domain.
For example, I have set this prefix to 'mmlist_'. This is what my
virtual-mailman file now looks like:
# STANZA START: list-name
# CREATED: Thu May 27 08:00:48 2004
list-name(a)lists.omnifarious.org mmlist_list-name
list-name-admin(a)lists.omnifarious.org mmlist_list-name-admin
list-name-bounces(a)lists.omnifarious.org mmlist_list-name-bounces
list-name-confirm(a)lists.omnifarious.org mmlist_list-name-confirm
list-name-join(a)lists.omnifarious.org mmlist_list-name-join
list-name-leave(a)lists.omnifarious.org mmlist_list-name-leave
list-name-owner(a)lists.omnifarious.org mmlist_list-name-owner
list-name-request(a)lists.omnifarious.org mmlist_list-name-request
list-name-subscribe(a)lists.omnifarious.org mmlist_list-name-subscribe
list-name-unsubscribe(a)lists.omnifarious.org mmlist_list-name-unsubscribe
# STANZA END: list-name
And, here is what my aliases file looks like:
# STANZA START: list-name
# CREATED: Thu May 27 08:00:48 2004
mmlist_list-name: "|/var/list-name/mail/list-name post list-name"
mmlist_list-name-admin: "|/var/list-name/mail/list-name admin list-name"
mmlist_list-name-bounces: "|/var/list-name/mail/list-name bounces list-name"
mmlist_list-name-confirm: "|/var/list-name/mail/list-name confirm list-name"
mmlist_list-name-join: "|/var/list-name/mail/list-name join list-name"
mmlist_list-name-leave: "|/var/list-name/mail/list-name leave list-name"
mmlist_list-name-owner: "|/var/list-name/mail/list-name owner list-name"
mmlist_list-name-request: "|/var/list-name/mail/list-name request list-name"
mmlist_list-name-subscribe: "|/var/list-name/mail/list-name subscribe list-name"
mmlist_list-name-unsubscribe: "|/var/list-name/mail/list-name unsubscribe list-name"
# STANZA END: list-name
Yes, people can still send to mmlist_list-name(a)omnifarious.org, but I
consider that an acceptable tradeoff since I'm now allowed a lot more
detailed control over my omnifarious.org namespace.
The parameter's name is POSTFIX_VIRTUAL_PREFIX, and it's expected to be
set in the mm_cfg file. If there is no POSTFIX_VIRTUAL_PREFIX set, it
defaults to being blank, which gives you the original behavior for the
Postfix MTA.
Have fun (if at all possible),
--
The best we can hope for concerning the people at large is that they
be properly armed. -- Alexander Hamilton
-- Eric Hopper (hopper(a)omnifarious.org http://www.omnifarious.org/~hopper) --
Hello Developers.
I have a client that would like to customize the subject line of the
subscription acknowledgement message that mailman sends out when someone
successfully subscribes.
We have successfully customized the lists/<listname>/en/subscribeack.txt
message and it works great! However there does not appear to be any way
to change the subject line of that message.
I have searched the documentation, list archives, and finally the source
code. I could not find anything in the documentation or the archives but
the relevant lines of source code appear to be here:
Deliverer.py line 75
msg = Message.UserNotification(
self.GetMemberAdminEmail(name), self.GetRequestEmail(),
_('Welcome to the "%(realname)s" mailing list%(digmode)s'),
text, pluser)
This appears to be a hard-coded subject line. :(
Would there be any work-around that wouldn't effect the subject line of
every list on the system?
Ultimately I believe there should be two new options added to the
General list information page right under "Send welcome message to newly
subscribed members?"
----
Subject line of Welcome message: Welcome to the "%(realname)s" mailing
list%(digmode)s
Body of Welcome message: <default body text>
----
Is there any chance this is something that might make it into Mailman
anytime soon?
Any suggestions, hints, rants etc. are welcome.
Thank you.
--
John Lange
BigHostBox.com
(204) 885 0872
I just got this on a new list I created...
"...mailing list has -1 request(s) waiting for your consideration at:"
That's kinda funny... now how am I supposed to approve -1 messages?
Ricardo.
> def ScriptURL(target, web_page_url=None, absolute=False):
> """target - scriptname only, nothing extra
> web_page_url - the list's configvar of the same name
> absolute - a flag which if set, generates an absolute url
> """
> if web_page_url is None:
> web_page_url = mm_cfg.DEFAULT_URL_PATTERN % get_domain()
> if web_page_url[-1] <> '/':
> web_page_url = web_page_url + '/'
> fullpath = os.environ.get('REQUEST_URI')
> if fullpath is None:
> fullpath = os.environ.get('SCRIPT_NAME', '') + \
> os.environ.get('PATH_INFO', '')
> baseurl = urlparse.urlparse(web_page_url)[2]
> if not absolute and fullpath.endswith(baseurl):
^^^^^^^^^^^^^^^^^
> # Use relative addressing
> fullpath = fullpath[len(baseurl):]
> i = fullpath.find('?')
> if i > 0:
> count = fullpath.count('/', 0, i)
> else:
> count = fullpath.count('/')
> path = ('../' * count) + target
> else:
> path = web_page_url + target
> return path + mm_cfg.CGIEXT
>
I'm curious about the "if not absolute ..." test in the code above.
Is it possible that the author really wanted
if not absolute and fullpath.startswith(baseurl):
?
This would seem to make more sense to me, since the test is presumably
there to check whether a relative URL can be constructed. This would
seemingly need the LEADING (not the TRAILING) part of "fullpath" to be
"baseurl".
Also given the code in the "then" clause, which apparently (and
understandably) wants to strip the "baseurl" part out of "fullpath",
I'd expect the startswith method to be used in the if.
Finally, the entire reason I'm looking at this is that a local user
complained about the link individual lists on the mailing list
overview page being absolute URIs. Changing "endswith" to "startswith"
does the trick...
On the other hand, I'm not familiar with the mailman code, nor am I a
python programmer, so perhaps I'm missing something...?
TIA!,
- Richard Geiger
rmg(a)datadomain.com
Today I am releasing Mailman 2.1.5, a bug fix release that also contains
new support for the Turkish language, and a few minor new features.
Mailman 2.1.5 is a significant upgrade which should improve disk i/o
performance, administrative overhead for discarding held spams, and the
behavior of bouncing member disables. This version also contains a fix
for an exploit that could allow 3rd parties to retrieve member
passwords. It is thus highly recommended that all existing sites
upgrade to the latest version.
The full source tarball, as well as a patch against Mailman 2.1.4 have
been made available. See
http://sourceforge.net/project/showfiles.php?group_id=103
for links to downloads.
NOTE: You will want to read the UPGRADING file for important information
regarding upgrading from earlier version to Mailman 2.1.5. A number of
internal file formats have changed so you must shut down web and mail
access to Mailman before you upgrade. You will also want to re-run
configure (i.e. config.status) before you run "make install".
See also:
http://www.list.orghttp://mailman.sf.nethttp://www.gnu.org/software/mailman
Finally, a personal note. I have left Zope Corporation to join Secure
Software, a company started by John Viega -- Mailman's original author.
Although I won't be working on Mailman in any official capacity, it is
exciting to be working with him and the rest of the folks there. I
leave Zope Corp on a positive note and wish nothing but success for them
too.
You can find Secure Software on the web at
http://www.securesoftware.com. Please continue to use my
barry(a)python.org email address for all Mailman correspondences. I don't
expect much to change for the Mailman project at all.
Enjoy,
-Barry
2.1.5 (15-May-2004)
- The admindb page has a checkbox that allows you to discard all held
messages that are marked Defer. On heavy lists with lots of spam holds,
this makes clearing them much faster.
- The qrunner system has changed to use only one file per message.
However the configuration variable METADATA_FORMAT has been removed, and
support for SAVE_MSGS_AS_PICKLES has been changed. The latter no longer
writes messages as plain text. Instead, they are stored as pickles of
plain strings, using the text pickle format. This still makes them
non-binary files readable and editable by humans.
bin/dumpdb also works differently. It will print out the entire pickle
file (with more verbosity) and if used with 'python -i', it binds msg to
a list of all objects found in the pickle file.
Removed from Defaults.py: PENDINGDB_LOCK_TIMEOUT,
PENDINGDB_LOCK_ATTEMPTS, METAFMT_MARSHAL, METAFMT_BSDDB_NATIVE,
METAFMT_ASCII, METADATA_FORMAT
- The bounce processor has been redesigned so that now when an address's
bounce score reaches the threshold, that address will be sent a probe
message. Only if the probe bounces will the address be disabled. The
score is reset to zero when the probe is sent. Also, bounce events are
now kept in an event file instead of in memory. This should help
contain the bloat of the BounceRunner.
New supporting variables in Defaults.py: VERP_PROBE_FORMAT,
VERP_PROBE_REGEXP
REGISTER_BOUNCES_EVERY is promoted to a Defaults.py variable.
- The pending database has been changed from a global pickle file, to a
unique pickle file per mailing list.
- The 'request' database file has changed from a marshal, to the more
secure pickle format.
- Disallow multiple password retrievals.
- The email package is updated to version 2.5.5.
- New language: Turkish.
- Bugs and patches: 869644, 869647 (NotAMemberError for old cookie data),
878087 (bug in Slovenian catalog), 899263 (ignore duplicate pending
ids), 810675 (discard all defers button)
Can one of the mailman pros on the list enlighten me about how the bounce
management works in the background?
Let's say the list is set to suspend a member after 3 bounces and then
delete him after 3 more attempts, each 7 days apart. So lets say one member
has had 3 bounces and is suspended. Now suddenly I change the list settings
so it requires 5 bounces before a member is suspended. Will the list notice
this during the next time it sends out emails? How does the list check the
current settings of the list versus the individual status? Is there a
cleanup process for members who are dormant because of changes in the list
settings?
Thanks for all the input on this!
I'm currently using Mailman 2.1.4 with Postfix on a Red Hat Enterprise
Verison 3 workstation.
I would like to use the scrubber.patch to put attachments has a viewable
link in the archives, "which is working", but I also want the attachment
completely stripped from the email message. Here's my problem, if I
enable content filtering to strip the attachments, scrubber never puts
the attachment as a link in the archives. I thought it might be a
Global Pipeline issue, so
I changed the sequence of the global pipeline "as shown below", and put
Scrubber as the first Handler to be processed and of course put this in
"mm_cfg.py" and restarted Mailman. Still, the content filtering strips
the attachments like I want, but scrubber never puts the attachment as
a link in the archives.
Does the sequence of the Pipeline affect this process, is there a way to
do what I want? Also is there documentation that shows a step by step
process that a message goes through before delivery? I would love to
see this, it would help me understand the process that Mailman does to
prepare a message for delivery.
I manage 200 lists at Idaho State Univeristy, and Mailman is a very
critical application for us, which makes this task very important and in
a rush to get accomplished.
I would appreciate your help.
GLOBAL_PIPELINE = [
# These are the modules that do tasks common to all delivery paths.
'Scrubber',
'SpamDetect',
'Approve',
'Replybot',
'Moderate',
'Hold',
'MimeDel',
'Emergency',
'Tagger',
'CalcRecips',
'AvoidDuplicates',
'Cleanse',
'CookHeaders',
# And now we send the message to the digest mbox file, and to the arch and
# news queues. Runners will provide further processing of the message,
# specific to those delivery paths.
'ToDigest',
'ToArchive',
'ToUsenet',
# Now we'll do a few extra things specific to the member delivery
# (outgoing) path, finally leaving the message in the outgoing queue.
'AfterDelivery',
'Acknowledge',
'ToOutgoing',
]
--
Kory Wheatley
Academic Computing Analyst Sr.
Phone 282-3874
#########################################
Everything must point to him.
Hi guys,
When viewing the user page in danish (with 30% or less translated - I'll
have a look a that at some point when I get the time) - it fails with this
message (it works fine when using english):
Bug in Mailman version 2.1.5
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 "/usr/local/mailman/scripts/driver", line 87, in run_main
main()
File "/usr/local/mailman/Mailman/Cgi/options.py", line 239, in main
loginpage(mlist, doc, user, language)
File "/usr/local/mailman/Mailman/Cgi/options.py", line 813, in loginpage
table.AddRow([_("""In order to change your membership option, you must
File "/usr/local/mailman/Mailman/i18n.py", line 89, in _
return tns % dict
ValueError: unsupported format character 'p' (0x70) at index 105
Python information:
Variable Value
sys.version 2.2.3 (#1, Jul 28 2003, 11:43:19) [GCC 3.2.2 20030322 (Gentoo
Linux 1.4 3.2.2-r2)]
sys.executable /usr/bin/python
sys.prefix /usr
sys.exec_prefix /usr
sys.path /usr
sys.platform linux2
Environment variables:
Variable Value
PATH_INFO /lp-nyhedsbrev
CONTENT_LENGTH 100
CONTENT_TYPE application/x-www-form-urlencoded
HTTP_COOKIE POSTNUKESID=5241e6345df9c0303def0d4b0749ea3a
SCRIPT_FILENAME /usr/local/mailman/cgi-bin/options
PYTHONPATH /usr/local/mailman
SERVER_SOFTWARE Apache
SERVER_ADMIN admin(a)EnableIT.dk
SCRIPT_NAME /mailman/options
SCRIPT_URI http://www.mysite.dk/mailman/options/lp-nyhedsbrev
SERVER_SIGNATURE
REQUEST_METHOD POST
HTTP_HOST www.mysite.dk
SCRIPT_URL /mailman/options/lp-nyhedsbrev
SERVER_PROTOCOL HTTP/1.1
QUERY_STRING
REQUEST_URI /mailman/options/lp-nyhedsbrev
HTTP_ACCEPT
text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,video/x-mng,image/png,image/jpeg,image/gif;q=0.2,*/*;q=0.1
HTTP_ACCEPT_CHARSET ISO-8859-1,utf-8;q=0.7,*;q=0.7
HTTP_USER_AGENT Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6)
Gecko/20040418 Firefox/0.8
HTTP_CONNECTION keep-alive
HTTP_REFERER http://www.mysite.dk/mailman/listinfo/lp-nyhedsbrev
SERVER_NAME my site
REMOTE_ADDR <client-ip-removed>
HTTP_KEEP_ALIVE 300
REMOTE_PORT 34514
HTTP_ACCEPT_LANGUAGE en-us,en;q=0.5
PATH_TRANSLATED /www/websites/mysite/html/lp-nyhedsbrev
SERVER_PORT 80
GATEWAY_INTERFACE CGI/1.1
HTTP_ACCEPT_ENCODING gzip,deflate
SERVER_ADDR 192.168.1.2
DOCUMENT_ROOT /www/websites
--
Regards,
Klavs Klavsen, GSEC - kl(a)vsen.dk - http://www.vsen.dk
PGP: 7E063C62/2873 188C 968E 600D D8F8 B8DA 3D3A 0B79 7E06 3C62
"Those who do not understand Unix are condemned to reinvent it, poorly."
--Henry Spencer
