Re: [Mailman-Users] digests/Python/2.1.12 upgrade

[Christopher Adams]

Mark,

Running crontab -u mailman -i just reads out crontab.in.

The edit to charset.py worked and the digests have been generated.
Thank you for your commitment to help. It really makes a big
difference to us adminstrators. I wonder why this particular
installation presented a unique problem.

Thanks again,

Christopher Adams

On Mon, Jul 20, 2009 at 6:08 PM, Mark Sapiro wrote:
> Christopher Adams wrote:
>>
>>>From crontab.in :
>
>
> What about from
>
> crontab -u mailman -l
>
> although it's popbably the same.
>
>
>>#
>># Noon, mail digests for lists that do periodic as well as threshhold 
>>delivery.
>>0 12 * * * /usr/local/bin/python -S /usr/local/mailman/cron/senddigests
>>#
>>
>>This invokes version 2.5.
>>
>>>From senddigests:
>>
>>#! /usr/local/bin/python
>>
>>This invokes version 2.5
>
>
> Take a look at /usr/local/lib/python2.5/email/charset.py. At around
> line 196, you should see
>
>    def __init__(self, input_charset=DEFAULT_CHARSET):
>
> followed by 4 comment lines and
>
>        try:
>            if isinstance(input_charset, unicode):
>                input_charset.encode('ascii')
>            else:
>                input_charset = unicode(input_charset, 'ascii')
>        except UnicodeError:
>            raise errors.CharsetError(input_charset)
>        input_charset = input_charset.lower()
>
> This may be a problem, although others who've had this problem with a
> different email package have switched to this one and it solved the
> problem. Try changing
>
>            else:
>                input_charset = unicode(input_charset, 'ascii')
>
> to
>
>            else:
>                unicode(input_charset, 'ascii')
>
> and then restart Mailman.
>
> If that fixes the problem for you, I don't know why others don't have
> this problem with email 4.0.1, but at least you will be OK.
>
>
> --
> Mark Sapiro         The highway is for gamblers,
> San Francisco Bay Area, California    better use your sense - B. Dylan
>
>



-- 
Christopher Adams
adam...@gmail.com
--
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] Password reminder on private archive login page

[Mark Sapiro]

liste yoneticisi wrote:
>
>I heard that 2.1.12 doesn't work properly on 2.4.4 but I am informed that
>the newer version of Python  doesn't exist on Debian Package.
>It seems difficult to upgrade under these circumstances.


There is a simple patch to the Python 2.4.4 lib/email/Charset.py at
 that will
fix it for Mailman.

Also see the comment thread at
.

-- 
Mark Sapiro The 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/archive%40jab.org

Security Policy: http://wiki.list.org/x/QIA9

Re: [Mailman-Users] Password reminder on private archive login page

[Mark Sapiro]

liste yoneticisi wrote:
>
>I have two main questions.
>
>First; We once asked about adding password reminder to private archive
>login page. We tried some modifications but couldn't succeed. I copied the
>previous correspondence below.
>
>"""
>>Can I put the password reminder on private archive login page? So that,
>>list members who want to see the archive, but do not remember their
>>passwords, can quickly learn their passwords. Otherwise, password
>>reminder is too hard to find using the links on general list info page..
>
>
>This is a good idea. I think I'll implement it for Mailman 2.2.
>
>What needs to be done is the reminder button has to be added to the
>private.html archive login template and code needs to be added to
>Mailman/Cgi/private.py to recognize the button and send the reminder.
>
>You can look at Mailman/Cgi/options.py for how it's done there.
>"""
>
>
>I have added the following lines to
>PATH/mailman/Mailman/Cgi/private.py
>
>"
>print Utils.maketext(
>'private.html',
>{'action'  : Utils.websafe(action),
> 'realname': mlist.real_name,
> 'message' : message,
> }, mlist=mlist)
>return
>
>### My Lines 7/4/2009 Eklenti baslangic
>
>if cgidata.has_key('emailpw'):
>mlist.MailUserPassword(user)
>options_page(
>mlist, doc, user, cpuser, userlang,
>_('A reminder of your password has been emailed to you.'))
>print doc.Format()
>return
>### My Lines 7/4/2009 Eklenti bitis
>
>
>lang = mlist.getMemberLanguage(username)
>i18n.set_language(lang)
>doc.set_language(lang)
>
># Authorization confirmed... output the desired file
>try:
>ctype, enc = guess_type(path, strict=0)
>
>"
>
>But nothing changed.:-(


There are several things wrong with the above.

You have copied the wrong code from options.py. That code processes the
reminder button from the logged-in options page (I'm not sure why
there is a reminder there, but the list admin could use it to send a
reminder to the user). You want the code that follows the comment

# Are we processing a password reminder from the login screen?

but if you copy it verbatim as you did with the other, you'll have the
problem that it calls the function loginpage() just as the above calls
options_page() and those functions are local to the options.py module
and undefined in private.py. You don't want to call either of those.

The final problem is you've inserted your code in the wrong place. You
put it where it is only reached if the user is already authenticated
or provided a valid authentication.


>What else can we do about it?


Find someone who knows some Python to do this for you.


You can try the insert in the attached reminder.txt file, but note that
this is untested and may cause problems.


>Mailman version is 2.1.9
>
>
>
>The second question is about vesion upgrade.
>
>Mailman, in our system, is running on Debian.
>Python version is 2.4.4
>
>I heard that 2.1.12 doesn't work properly on 2.4.4 but I am informed that
>the newer version of Python  doesn't exist on Debian Package.
>It seems difficult to upgrade under these circumstances.
>
>What are the major differences between the Mailman versions 2.1.9 and
>2.1.12 with regard to security, usability?


See


-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

if not mlist.WebAuthenticate((mm_cfg.AuthUser,
  mm_cfg.AuthListModerator,
  mm_cfg.AuthListAdmin,
  mm_cfg.AuthSiteAdmin),
 password, username):
if cgidata.has_key('submit'):
# This is a re-authorization attempt
message = Bold(FontSize('+1', _('Authorization failed.'))).Format()

# Are we processing a password reminder from the login screen?
if cgidata.has_key('login-remind'):
if mlist.isMember(user):
mlist.MailUserPassword(user)
message = Bold(FontSize('+1', _("""If you are a list member,
your password has been emailed to 
you."""))).Format()
else:
# Not a member
if mlist.private_roster == 0:
# Public rosters
safeuser = Utils.websafe(user)
message = Bold(FontSize('+1',
   _('No such member: %(safeuser)s.'))).Format()
else:
syslog('mischief',
   'Reminder attempt of non-member w/ private rosters: 
%s',
   user)

# Output the password form
---

Re: [Mailman-Users] digests/Python/2.1.12 upgrade

[Mark Sapiro]

Christopher Adams wrote:
>
>>From crontab.in :


What about from

crontab -u mailman -l

although it's popbably the same.


>#
># Noon, mail digests for lists that do periodic as well as threshhold delivery.
>0 12 * * * /usr/local/bin/python -S /usr/local/mailman/cron/senddigests
>#
>
>This invokes version 2.5.
>
>>From senddigests:
>
>#! /usr/local/bin/python
>
>This invokes version 2.5


Take a look at /usr/local/lib/python2.5/email/charset.py. At around
line 196, you should see

def __init__(self, input_charset=DEFAULT_CHARSET):

followed by 4 comment lines and

try:
if isinstance(input_charset, unicode):
input_charset.encode('ascii')
else:
input_charset = unicode(input_charset, 'ascii')
except UnicodeError:
raise errors.CharsetError(input_charset)
input_charset = input_charset.lower()

This may be a problem, although others who've had this problem with a
different email package have switched to this one and it solved the
problem. Try changing

else:
input_charset = unicode(input_charset, 'ascii')

to

else:
unicode(input_charset, 'ascii')

and then restart Mailman.

If that fixes the problem for you, I don't know why others don't have
this problem with email 4.0.1, but at least you will be OK.


-- 
Mark Sapiro The 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/archive%40jab.org

Security Policy: http://wiki.list.org/x/QIA9

Re: [Mailman-Users] mailman-loop question

[Mark Sapiro]

Christopher Adams wrote:

>Since upgrading to Mailman 2.1.12, the system has been generating
>dozens of messages similar to the one below. Prior to the upgrade, I
>did not see these sent from mailman-loop. I checked the mailman
>aliases and see the entry for it:
>
># The ultimate loop stopper address
>mailman-loop: /usr/local/mailman/data/owner-bounces.mbox
>
>
>An example of the messages:
>
>From: mailman-l...@mydomain.com; on behalf of; Mail Delivery System
>[mailer-dae...@mydomain.com]
>
>  Subject: Staying healthy is easy
>  Sent:7/20/2009 10:08 AM
>
>The following recipient(s) could not be reached:
>
> joe.b...@wherever.com on 7/20/2009 10:08 AM
>Failed (host mail.system.com[xxx.xxx.xxx.xx] said: 550
>5.1.1 ... User unknown (in reply to RCPT TO
>command))
>
>
>What specifically is  mailman-loop supposed to do and is this just a
>coincidence that I am getting them after the upgrade? I commented out
>the alias and restarted mailman, yet the message continue to be
>delivered.


The mailman-loop alias has nothing to do with this message and you
shouldn't remove it. It is there to prevent bounce loops should THIS
message bounce.

The messages are bounces of password reminders. This changed in 2.1.11.
See

for more detail.

-- 
Mark Sapiro The 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/archive%40jab.org

Security Policy: http://wiki.list.org/x/QIA9

[Mailman-Users] mailman-loop question

[Christopher Adams]

Since upgrading to Mailman 2.1.12, the system has been generating
dozens of messages similar to the one below. Prior to the upgrade, I
did not see these sent from mailman-loop. I checked the mailman
aliases and see the entry for it:

# The ultimate loop stopper address
mailman-loop: /usr/local/mailman/data/owner-bounces.mbox


An example of the messages:

From: mailman-l...@mydomain.com; on behalf of; Mail Delivery System
[mailer-dae...@mydomain.com]

  Subject:  Staying healthy is easy
  Sent: 7/20/2009 10:08 AM

The following recipient(s) could not be reached:

 joe.b...@wherever.com on 7/20/2009 10:08 AM
Failed (host mail.system.com[xxx.xxx.xxx.xx] said: 550
5.1.1 ... User unknown (in reply to RCPT TO
command))


What specifically is  mailman-loop supposed to do and is this just a
coincidence that I am getting them after the upgrade? I commented out
the alias and restarted mailman, yet the message continue to be
delivered.


-- 
Christopher Adams
adam...@gmail.com
--
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] digests/Python/2.1.12 upgrade

[Christopher Adams]

Mark,

>From crontab.in :

#
# Noon, mail digests for lists that do periodic as well as threshhold delivery.
0 12 * * * /usr/local/bin/python -S /usr/local/mailman/cron/senddigests
#

This invokes version 2.5.

>From senddigests:

#! /usr/local/bin/python

This invokes version 2.5

As for /usr/local/mailman/pythonlib/lib/python2.5, that does seem to
be irrelevant to this. It points to some Japanese site-packages or
something. I thought is was something else.

On Sat, Jul 18, 2009 at 10:05 PM, Mark Sapiro wrote:
> Christopher Adams wrote:
>>
>>It says __version__ = '4.0.1'
>>
>>I guess my only alernative is to upgrade to 2.5.2, though I am not
>>sure if the OS will support it.
>
>
> I don't know if that will help as it has the same version 4.0.1 email
> package.
>
> What are the python comands in Mailman's crontab and in the initial
> line of cron/senddigests, and what python do they invoke?
>
> You mentioned earlier
>
>>I also have this in the mailman directory:
>
>>/usr/local/mailman/pythonlib/lib/python2.5
>
> That in itself is probably irrelevant, but what is that? Is it a
> symlink or the entire Python library or ?
>
> --
> Mark Sapiro         The highway is for gamblers,
> San Francisco Bay Area, California    better use your sense - B. Dylan
>
>



-- 
Christopher Adams
adam...@gmail.com
--
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] Password reminder on private archive login page

[liste yoneticisi]

Hello;

I have two main questions.

First; We once asked about adding password reminder to private archive
login page. We tried some modifications but couldn't succeed. I copied the
previous correspondence below.

"""
>Can I put the password reminder on private archive login page? So that,
>list members who want to see the archive, but do not remember their
>passwords, can quickly learn their passwords. Otherwise, password
>reminder is too hard to find using the links on general list info page..


This is a good idea. I think I'll implement it for Mailman 2.2.

What needs to be done is the reminder button has to be added to the
private.html archive login template and code needs to be added to
Mailman/Cgi/private.py to recognize the button and send the reminder.

You can look at Mailman/Cgi/options.py for how it's done there.
"""


I have added the following lines to
PATH/mailman/Mailman/Cgi/private.py

"
print Utils.maketext(
'private.html',
{'action'  : Utils.websafe(action),
 'realname': mlist.real_name,
 'message' : message,
 }, mlist=mlist)
return

### My Lines 7/4/2009 Eklenti baslangic

if cgidata.has_key('emailpw'):
mlist.MailUserPassword(user)
options_page(
mlist, doc, user, cpuser, userlang,
_('A reminder of your password has been emailed to you.'))
print doc.Format()
return
### My Lines 7/4/2009 Eklenti bitis


lang = mlist.getMemberLanguage(username)
i18n.set_language(lang)
doc.set_language(lang)

# Authorization confirmed... output the desired file
try:
ctype, enc = guess_type(path, strict=0)

"

But nothing changed.:-(

What else can we do about it?
Mailman version is 2.1.9



The second question is about vesion upgrade.

Mailman, in our system, is running on Debian.
Python version is 2.4.4

I heard that 2.1.12 doesn't work properly on 2.4.4 but I am informed that
the newer version of Python  doesn't exist on Debian Package.
It seems difficult to upgrade under these circumstances.

What are the major differences between the Mailman versions 2.1.9 and
2.1.12 with regard to security, usability?

Thanks...
--
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] Message Delays

[Stefan Förster]

* stevenmark1...@aol.com wrote:
> Hi i run a mailman list and am having complaints from members because , for
>  example an email is sent to the list at 0800 hrs and they are not
> receiving it  until 2300hrs , the members all have different isp mailboxes 
> from a
> variety of  isp's , the message is hitting the server from the sender but is
> very erratic at  getting to peoples inboxes , any ideas as to why , as the
> company i buy the list  through say there are no issues with the list when
> quite clearly there are

Without the mailserver's logs, this is hard to debug. The next time a
message is delivered with a large delay, find out the message-id of
that post to the list, and try asking the company running your list
for you for the following details:

1. The time the message with the given message id and the recipient
who had a complaint entered the queue of that company's mail server.
2. The time of all delivery attempts to the receivers mail server. If
there is more than one attempt, they should provide you with the
errors which prevented a successful delivery.

Since not all of your list's subscribers have problems receiving the
mail in a timely manner I don't think this is a mailman problem at
all.


Cheers
Stefan
-- 
Stefan Förster http://www.incertum.net/ Public Key: 0xBBE2A9E9
Der Preis der Freiheit ist ewige Wachsamkeit!
--
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