[Mailman-Users] python 3 and mailman 2.1.12
python 3.1 was just installed on a system where I am running mailman 2.1.12.
It seems to have broken the mailman web interface and sending of mail via
mailman lists.
An error from the mailer daemon when sending to one of the lists gives me a
traceback:
==
- Transcript of session follows -
Message delivered to mailing list t...@saturn.sri.com
Traceback (most recent call last):
File /usr/local/mailman/scripts/post, line 31, in module
import paths
File /usr/local/mailman/scripts/paths.py, line 40, in module
s = unicode('OK', 'iso-2022-jp')
NameError: name 'unicode' is not defined
554 5.3.0 unknown mailer error 1
==
I notice in other posts that some versions of python 2 and mailman are not
compatible. I am guessing the same is true for python 3. I see on the
python page that 3 is the shiny new thing.
python 2.3.3 is still on our system, but one of our users wants to
upgrade. For mailman 2.1.12 purposes, should I revert to say python 2.7?
Or is 2.1.14 compatible with python 3?
Thanks,
Hal Huntley
--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] /usr/lib/mailman/cron/senddigests error
I get this mailman message about digests a few times a week based on the
senddigests cron job. Since we don't do digests on any of our mailing
lists, I've ignored it and no one has complained about not receiving
messages on any of our lists.
But in the interest of learning something and reducing the amount of email I
may get, I'd like to figure out how to make it go away. I've deleted most
of the headers. The text of the traceback is in its entirety.
It's probably a pretty easy fix, I'd guess. I _could_ comment out the
cronjob entry for the senddigests, and I'm willing to do that, but it would
be more beneficial to learn a bit more of the depths of things.
It's mailman 2.1.5.
Hal Huntley
SRI International
-
[Maybe pertinent headers:]
X-Cron-Env: SHELL=/bin/sh
X-Cron-Env: HOME=/usr/lib/mailman
X-Cron-Env: PATH=/usr/bin:/bin
X-Cron-Env: LOGNAME=mailman
X-Cron-Env: USER=mailman
Subject: [Mailman] Cron mail...@host /usr/lib/mailman/cron/senddigests
X-Mailman-Version: 2.1.5
Precedence: list
[body of message:]
Traceback (most recent call last):
File /usr/lib/mailman/cron/senddigests, line 94, in ?
main()
File /usr/lib/mailman/cron/senddigests, line 86, in main
mlist.send_digest_now()
File /usr/lib/mailman/Mailman/Digester.py, line 60, in send_digest_now
ToDigest.send_digests(self, mboxfp)
File /usr/lib/mailman/Mailman/Handlers/ToDigest.py, line 132, in
send_digests
send_i18n_digests(mlist, mboxfp)
File /usr/lib/mailman/Mailman/Handlers/ToDigest.py, line 225, in
send_i18n_digests
addresses = getaddresses([oneline(msg.get('from', ''), lcset)])
File /usr/lib/mailman/Mailman/Handlers/ToDigest.py, line 389, in oneline
h = make_header(decode_header(s))
File /usr/lib/mailman/pythonlib/email/Header.py, line 113, in decode_header
raise HeaderParseError
email.Errors.HeaderParseError
___
Mailman mailing list
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
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://wiki.list.org/x/QIA9
[Mailman-Users] footers and members of the list
We have a request from a list administrator asking if he can have the all the members of the list listed in the footer of the message. This list is under Mailman 2.1.9. This isn't a personalization listing with just the name of the member subscribing. He wants all the messages going out to have all the list members in the footer. Is there a variable that can handle that? Or must the list maintainer just add the names by hand? He may be content with just names or email addresses. Regards, Hal Huntley SRI International -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
Re: [Mailman-Users] footers and members of the list
Hal Huntley wrote: We have a request from a list administrator asking if he can have the all the members of the list listed in the footer of the message. This list is under Mailman 2.1.9. This isn't a personalization listing with just the name of the member subscribing. He wants all the messages going out to have all the list members in the footer. Is there a variable that can handle that? Or must the list maintainer just add the names by hand? He may be content with just names or email addresses. No, there is no variable that can handle that, but one could easily put a link to the list's roster page in the footer which I think would be much better than putting everyone's address in which raises serious privacy concerns should such a message be forwarded off list. -- Mark Sapiro m...@msapiro.netThe 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://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/hal%40sofdev.sri.com Security Policy: http://wiki.list.org/x/QIA9 === Mark, Thank you for that information. I gave that URL idea a try and if I happened to be logged in as a list administrator for a list, I got a list of members. I also tried getting a roster by going to a .../mailman/roster/listname of a list I am a member of but was not logged in. I got an authentication failed. error message. Since one needs to be a member of the list to see the members, that makes sense. One could set the URL to point to the .../listinfo/listname page where the person could enter their email address and password to get the list members, but I think the list admininstrator wants something a bit easier to get the names. I will share your thoughts with the list administrator about not wanting to do that anyway due to privacy concerns. Excellent point. Hal -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 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://wiki.list.org/x/QIA9
[Mailman-Users] delivery problems and digests?
One mailman instance that I work with is running 2.1.2 on a linux
2.4.20-20.9 kernel.
Mail to a specific list is not getting delivered, but other lists on the
same instance are being delivered fine. The error message one person got
back when they tried to send a message to the list was:
start error message ===
Traceback (most recent call last):
File /usr/local/mailman/cron/senddigests, line 94, in ?
main()
File /usr/local/mailman/cron/senddigests, line 86, in main
mlist.send_digest_now()
File /usr/local/mailman/Mailman/Digester.py, line 60, in send_digest_now
ToDigest.send_digests(self, mboxfp)
File /usr/local/mailman/Mailman/Handlers/ToDigest.py, line 130, in
send_digests
send_i18n_digests(mlist, mboxfp)
File /usr/local/mailman/Mailman/Handlers/ToDigest.py, line 303, in
send_i18n_digests
msg = scrubber(mlist, msg)
File /usr/local/mailman/Mailman/Handlers/Scrubber.py, line 232, in process
url = save_attachment(mlist, part, dir)
File /usr/local/mailman/Mailman/Handlers/Scrubber.py, line 348, in
save_attachment
fnext = os.path.splitext(msg.get_filename(''))[1]
File /usr/local/mailman/pythonlib/email/Message.py, line 707, in
get_filename
return unicode(newvalue[2], newvalue[0])
TypeError: unicode() argument 2 must be string, not None
end error message ===
I read this message to the list that is dated January 2006:
==
Mailman sends messages in both regular and digest delivery. The digest
processing is inserted in the middle of regular delivery if the messages
accumulated to a preset amount. If there is a serious error in the
digest processing, the regular delivery fails. Since the messages are
accumulated already, arrival of following message triggers the digest
processing again and also fail in the subsequent regular delivery.
==
It went on to say:
==
Therefore, the site administrator should check the qfiles/shunt
directory and the logs/error file periodically.
==
The recommendation was to go to 2.1.7 of mailman. Well, I'd rather not do
that with all the lists going right now. I'll need to do that later.
I guess something bombed with the digestifying. We don't digest the
specific list, so I tried turning that off on the list, but that didn't
help any. I saw in the FAQ to try unshunt, but that doesn't seemed to
have unstick the log jam. There are quite a few files in the qfiles/shunt
directory.
Is there a command or a set of procedures that I can run to make the list
start delivering mail again normally?
Hal Huntley
SRI International
--
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] default action on administrative requests
Richard and Heath,
Thank you for pointing me in the right direction. You got me to the correct
file and looking at the right places. However, it wasn't at this location
in the admindb.py file, but further down. Working with this part of the
code:
radio = RadioButtonArray(id, (_('Defer'),
_('Approve'),
_('Reject'),
_('Discard')),
values=(mm_cfg.DEFER,
mm_cfg.SUBSCRIBE,
mm_cfg.REJECT,
mm_cfg.DISCARD),
checked=0).Format()
and setting checked=3, did not do what I wanted.
The relevant lines of code appear to be around line 392.
Here is where I modified things:
== start code segment ==
# The encompassing sender table
stable = Table(border=1)
stable.AddRow([Center(Bold(_('From:')).Format() + esender)])
stable.AddCellInfo(stable.GetCurrentRowIndex(), 0, colspan=2)
left = Table(border=0)
left.AddRow([_('Action to take on all these held messages:')])
left.AddCellInfo(left.GetCurrentRowIndex(), 0, colspan=2)
btns = hacky_radio_buttons(
'senderaction-' + qsender,
(_('Defer'), _('Accept'), _('Reject'), _('Discard')),
(mm_cfg.DEFER, mm_cfg.APPROVE, mm_cfg.REJECT, mm_cfg.DISCARD),
(0, 0, 0, 1))
### modifying line above to see if default action for discard is
### set here. Hal 7/30/2003
###(1, 0, 0, 0))
== end code segment ==
As you can see, I changed the line (1, 0, 0, 0)) to be (0, 0, 0, 1)) and
the discard radio button was selected as the default on the web page.
I realize this changes things for all my lists instead of just the one.
For now, that is ok since there are few lists to worry about.
I would like to request an enhancement by those who know how to develop that
this feature be made available on a per list basis.
Thanks again,
Hal Huntley
SRI International
==
On Wednesday, July 30, 2003, at 03:06 pm, Heath Raftery wrote:
Hi Hal,
On Wednesday, July 30, 2003, at 11:36 AM, Hal Huntley wrote:
I have a list that gets more spam than legit email. I would like to
have the
Action to take on all these held messages on the
admindb/listname page
to have a default of discard instead of defer. This way I can
quickly
scan the baddies and then submit all data once I see they are all
spam;
no clicking on the Discard radio button.
Not a definitive answer, but I've found the following in
Mailman/Mailman/Cgi/admindb.py:
radio = RadioButtonArray(id, (_('Defer'),
_('Approve'),
_('Reject'),
_('Discard')),
values=(mm_cfg.DEFER,
mm_cfg.SUBSCRIBE,
mm_cfg.REJECT,
mm_cfg.DISCARD),
checked=0).Format()
I reckon (but have not confirmed) that you could change the checked=0
bit to
checked=4 for Approve
checked=2 for Reject
checked=3 for Discard
Not quite. The value assigned to the checked parameter is the offset of
the radio button in the array which is initially checked when the form
is rendered; the value is the offset in the preceding list of button
names and their values. So:
checked=0 means the 'Defer' button would be checked
checked=1 means the 'Approve' button would be checked
checked=2 means the 'Reject' button would be checked
checked=3 means the 'Discard' button would be checked
(got these values from the HTML source generated in a typical
Administrative Requests page)
This seems to put a CHECKED flag in the INPUT tag, which I'm not
actually sure is valid HTML.
It is valid HTML. CHECKED (without any value associated) is a valid
attribute of an INPUT tag of TYPE=radio. It causes that radio button
to be in the on state when the form is initially displayed.
My reading seems to suggest that a value=Yes is required instead. If
that is not visible, then the standard is unclear. One version says
the user agent should select the first radio button in the group, so
you may want to try rearranging the order of the buttons in the
RadioButtonArray above instead.
Right now, I also wish this behavior for one list only, not as a
default for
all the lists that I have.
Hmm, dunno about that!
If you hack the code in the admindb.py file then the changes will
affect all lists equally.
Hope that helps, tell us how you go!
Heath
--
Mailman-Users mailing list
[EMAIL PROTECTED]
http
[Mailman-Users] default action on administrative requests
I sent this question a while back and had no reply. I didn't see my own message come back to me by way of the mailing list, so I presume it did not get out. I'm using Mailman 2.1.2 with Python 2.1.3 with Solaris 8. I've looked through the FAQ. I've seen a similar question on this list, but the answer was get Mailman 2.1. I now have 2.1.2, but this issue still eludes me. I have a list that gets more spam than legit email. I would like to have the Action to take on all these held messages on the admindb/listname page to have a default of discard instead of defer. This way I can quickly scan the baddies and then submit all data once I see they are all spam; no clicking on the Discard radio button. I don't want to use the Privacy Options - Sender Filters option of: Action to take for postings from non-members for which no explicit action is defined. to be discard. I know that the messages would come to me with the: Should messages from non-members, which are automatically discarded, be forwarded to the list moderator? but I really don't want the messages automatically coming to me; I want the member of my list to receive it if I click Accept. I've seen reference to a script that will just toss everything that is queued up for a list; I would rather not do this. Right now, I also wish this behavior for one list only, not as a default for all the lists that I have. What file do I need to change to make the default choice be discard on the administrative requests page? Pointers to documentation gratefully accepted. Thank you, Hal Huntley SRI International -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
[Mailman-Users] administrative requests default action
I'm using Mailman 2.1.2 with Python 2.1.3 with Solaris 8. I've seen a similar question on this list, but the answer was get Mailman 2.1. I have a list that gets more spam than legit email. I would like to have the Action to take on all these held messages on the admindb/listname page to have a default of discard instead of defer. This way I can quickly scan the baddies and then submit all data once I see they are all spam; no clicking on the Discard radio button. I don't want to use the Privacy Options - Sender Filters option of: Action to take for postings from non-members for which no explicit action is defined. to be discard. I know that the messages would come to me with the: Should messages from non-members, which are automatically discarded, be forwarded to the list moderator? but I really don't want the messages automatically coming to me; I want the member of my list to receive it if I click Accept. Right now, I also wish this behavior for one list only, not as a default for all the lists that I have. Thank you, Hal Huntley SRI International -- Mailman-Users mailing list [EMAIL PROTECTED] 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/ This message was sent to: [EMAIL PROTECTED] Unsubscribe or change your options at http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
