[Mailman-Developers] [ mailman-Feature Requests-595921 ] VirtualHost select interface

[noreply]

Feature Requests item #595921, was opened at 2002-08-16 11:27
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=350103aid=595921group_id=103

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Darius Tribandis (sirijus)
Assigned to: Nobody/Anonymous (nobody)
Summary: VirtualHost select interface

Initial Comment:
Hi,

becouse mailman supports virtualhosts it by pleasure to 
see and edit to which virtualhost belongs list, and 
chance to make it available to few virtual hosts.

Sirijus

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=350103aid=595921group_id=103

___
Mailman-Developers mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman-21/listinfo/mailman-developers

[Mailman-Developers] [ mailman-Bugs-593454 ] NewsRunner error

[noreply]

Bugs item #593454, was opened at 2002-08-10 17:52
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=100103aid=593454group_id=103

Category: nntp/news
Group: 2.1 beta
Status: Open
Resolution: None
Priority: 5
Submitted By: Simone Piunno (pioppo)
Assigned to: Nobody/Anonymous (nobody)
Summary: NewsRunner error

Initial Comment:
Just updated to Mailman 2.1b3:

Aug 10 17:18:57 2002 (10526) Uncaught runner exception: len() of unsized object
Aug 10 17:18:57 2002 (10526) Traceback (most recent call last):
  File /home/mailman21/Mailman/Queue/Runner.py, line 105, in _oneloop
self._onefile(msg, msgdata)
  File /home/mailman21/Mailman/Queue/Runner.py, line 154, in _onefile
keepqueued = self._dispose(mlist, msg, msgdata)
  File /home/mailman21/Mailman/Queue/NewsRunner.py, line 56, in _dispose
prepare_message(mlist, msg, msgdata)
  File /home/mailman21/Mailman/Queue/NewsRunner.py, line 132, in prepare_message
count = len(email.Iterators.body_line_iterator(msg))
TypeError: len() of unsized object



--

Comment By: Simone Piunno (pioppo)
Date: 2002-08-16 15:33

Message:
Logged In: YES 
user_id=227443

I have installed both 1.5.2 and 2.2.1.
Mailman has been configured --with-python=/usr/bin/python2 
but a couple files are still referring to the old python, at least
Mailman/Archiver/pipermail.py and Mailman/Post.py


--

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-08-16 00:37

Message:
Logged In: YES 
user_id=12800

Two questions, what version of Python are you running, and
can you upload the .pck file that's left in qfiles/shunt?

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=100103aid=593454group_id=103

___
Mailman-Developers mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman-21/listinfo/mailman-developers

[Mailman-Developers] [ mailman-Bugs-596055 ] wrong charset in bounce notice

[noreply]

Bugs item #596055, was opened at 2002-08-16 16:20
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=100103aid=596055group_id=103

Category: bounce detection
Group: 2.1 beta
Status: Open
Resolution: None
Priority: 5
Submitted By: Simone Piunno (pioppo)
Assigned to: Nobody/Anonymous (nobody)
Summary: wrong charset in bounce notice

Initial Comment:
When a member is disabled because of too many bounces
detected, if bounce_notify_owner_on_disable is set the list
owner is notified with a message generated in Boucer.py
using a template file (bounce.txt).

The problem is that the generated message is MIME 
encoded and bounce.txt is attached with hardcoded 
charset=us-ascii, even if a translated template was used.

Attached you can find a one-liner patch


--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=100103aid=596055group_id=103

___
Mailman-Developers mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman-21/listinfo/mailman-developers

[Mailman-Developers] [ mailman-Bugs-596055 ] wrong charset in bounce notice

[noreply]

Bugs item #596055, was opened at 2002-08-16 10:20
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=100103aid=596055group_id=103

Category: bounce detection
Group: 2.1 beta
Status: Closed
Resolution: Accepted
Priority: 5
Submitted By: Simone Piunno (pioppo)
Assigned to: Nobody/Anonymous (nobody)
Summary: wrong charset in bounce notice

Initial Comment:
When a member is disabled because of too many bounces
detected, if bounce_notify_owner_on_disable is set the list
owner is notified with a message generated in Boucer.py
using a template file (bounce.txt).

The problem is that the generated message is MIME 
encoded and bounce.txt is attached with hardcoded 
charset=us-ascii, even if a translated template was used.

Attached you can find a one-liner patch


--

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-08-16 10:41

Message:
Logged In: YES 
user_id=12800

Applied, thanks!

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=100103aid=596055group_id=103

___
Mailman-Developers mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman-21/listinfo/mailman-developers

[Mailman-Developers] [ mailman-Feature Requests-595333 ] REQ: admindb list of default responses

[noreply]

Feature Requests item #595333, was opened at 2002-08-14 20:57
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=350103aid=595333group_id=103

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Dylan Jay (dylan_jay)
Assigned to: Nobody/Anonymous (nobody)
Summary: REQ: admindb list of default responses

Initial Comment:
When moderating most rejected posts fit into certain 
catagories. It would be a big time saver to have a drop 
down list of default responces. Each would have a name 
and settings and text for the responce. A text box and 
a add as new default responce checkbox is all that is 
needed to add a new response (or edit one)

--

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-08-16 11:43

Message:
Logged In: YES 
user_id=12800

I agree that this would be nice. It's a feature that will
have to wait until after MM2.1, so I'm moving this to the
features request category.

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=350103aid=595333group_id=103

___
Mailman-Developers mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman-21/listinfo/mailman-developers

Re: [Mailman-Developers] Re: External subscriber lists in 2.1

[Dale Newfield]

On Sun, 23 Dec 2001, Barry A. Warsaw wrote:
 Note that if it was too expensive for getRegularMemberKeys() to return
 an in-memory list, it could (if you use Python 2.2) return an iterator
 object that implemented things in a more efficient manner, e.g. by
 paging through blocks.  I believe that any place where we expect a
 Python sequence (list) we could probably accept an iterator.

Do you know if this is in fact the case?  Is this how I should implement
it?

(While I've hacked in python fairly regularly, I've not done serious
Python development since ~1996, so some of these questions will be fairly
basic How's it work in Python2.2? ones.  Of course, this brings up the
question of whether or not it's reasonable to require that--don't we
currently only require 2.1.3?)

Below are different ways the results of get{Regular,Digest}MemberKeys
and getMembers are used in various places in the codebase.  Will each of
them still work if those methods return an iterator instead of a list?
(For example, does len(iterator) work?)

I'm guessing that a good answer might be that we want to add more
general-purpose accessor methods in class MemberAdaptor (and have the rest
of the codebase use those where appropriate) so that if there's a more
efficient way for a specific backend to provide specific data, it is able
to do so.  I'll include the two methods I propose at the end of this
message.

in Handlers/CalcRecips.py:
# Calculate the regular recipients of the message
recips = [mlist.getMemberCPAddress(m)
  for m in mlist.getRegularMemberKeys()
  if mlist.getDeliveryStatus(m) == ENABLED]
and:
recips = mlist.getMemberCPAddresses(mlist.getRegularMemberKeys() +
mlist.getDigestMemberKeys())

in Cgi/admin.py:
if not mlist.nondigestable and mlist.getRegularMemberKeys():
and:
if addr in mlist.getRegularMemberKeys():
and:
# If there are more members than allowed by chunksize, then we split the
# membership up alphabetically.  Otherwise just display them all.
chunksz = mlist.admin_member_chunksize
all = mlist.getMembers()
all.sort(lambda x, y: cmp(x.lower(), y.lower()))
then:
# BAW: There's got to be a more efficient way of doing this!
names = [mlist.getMemberName(s) or '' for s in all]
all = [a for n, a in zip(names, all)
   if cre.search(n) or cre.search(a)]

in HTMLFormatter.py:
members = self.getRegularMemberKeys()
for m in members:
if not self.getMemberOption(m, conceal_sub):
people.append(m)
num_concealed = len(members) - len(people)
and:
member_len = len(self.getRegularMemberKeys())





def getNumMembers(self, type, status, options, regexp=None):
Get the number of members of this mailing list matching type and
status, and optionally matching the regular expression passed in.

type is one of the module constants REGULAR, DIGEST, or EITHER.
The tally should include just the appropriate type of members.

status is a list containing some subset of the values ENABLED,
UNKNOWN, BYUSER, BYADMIN, BYBOUNCE.  The tally should include only
members whose status is in that list.

options is a dictionary containing some number of {flag:boolean}
pairs.  Only members with values matching that specified for each
flag in the dictionary should be included in the tally.

regexp is a string containing a regular expression to use as a filter.
If this is not None, only members whose CPE or NAME match the regexp
should be included in the tally.  (I don't have in mind a more
efficient way to implement this in the SQL MemberAdaptor, unless the
only non-token element in the regexp is .*, as that could be matched
using sql's wild-card %.  Just because it doesn't result in a more
efficient implementation in this case doesn't mean it shouldn't be
part of the interface, though.)

raise NotImplemented

def getMemberIterator(self, type, status, options, style, order, regexp=None):
Get an iterator of members of this mailing list matching type and
status, and optionally matching the regular expression passed in.

type, status, options, and regexp are as used in getNumMembers().

style is what content the iterator should contain: KEY, LCE, CPE, or
NAME   (If NAME, and some users have no RealName set, those
iterator entries will be None.)

order specifies in which order those items should be returned by the
iterator: KEY, LCE, CPE, or NAME  (This part hasn't been thought
through as thoroughly--are there other interesting orderings?)

raise NotImplemented




The rest of this message is for context since I'm responding to something
8 months old.

On Sun, 23 Dec 2001, Barry A. Warsaw wrote:
  JCL == J C Lawrence [EMAIL PROTECTED] writes:
 JCL In 2.1 when used with external 

[Mailman-Developers] [ mailman-Bugs-595132 ] No mail going out

[noreply]

Bugs item #595132, was opened at 2002-08-14 13:02
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=100103aid=595132group_id=103

Category: mail delivery
Group: 2.0.x
Status: Closed
Resolution: Invalid
Priority: 5
Submitted By: Terkel Olsen (terkel)
Assigned to: Nobody/Anonymous (nobody)
Summary: No mail going out

Initial Comment:
Hi there,
i have Installed Mailman manually on a NetBSD
for some reason its not in pkgsrc anymore. It installs
allmost fine, just had to fix a few GID's and point it to 
python, and then it appeared to install.

I created a list fine and it sent the e-mail to the admin
adress, but if i try to send anything to the list nothing 
gets send back. Its not even held for approval. The error 
log shows nothing and the maillog only shows this:

Aug 14 11:06:19 www sendmail[29601]: g7E96J229601: 
from=terkel, size=54, class=0, nrcpts=1, 
msgid=[EMAIL PROTECTED]
nierforlagene.dk, relay=terkel@localhost

Aug 14 11:06:19 www sendmail[29603]: g7E96J229601: 
to=|/usr/home/mailman/mailman/mail/wrapper post 
jokes, [EMAIL PROTECTED]
rforlagene.dk (1/0), delay=00:00:00, xdelay=00:00:00, 
mailer=prog, pri=30054, dsn=2.0.0, stat=Sent

But nothing further, so i guess it goes to the wrapper 
program but then no further...

Anyone experienced this before ? 

Terkel

--

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-08-16 11:45

Message:
Logged In: YES 
user_id=12800

Sounds to me like you didn't install the cronjob to get
qrunner going (assuming you're using MM2.0 -- you don't say
in your bug report).

I don't think this is a bug.  Contact
[EMAIL PROTECTED] for more help.

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=100103aid=595132group_id=103

___
Mailman-Developers mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman-21/listinfo/mailman-developers

[Mailman-Developers] [ mailman-Bugs-594913 ] rfc822.parseaddress() in Util.py Invalid

[noreply]

Bugs item #594913, was opened at 2002-08-14 02:19
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=100103aid=594913group_id=103

Category: command line scripts
Group: 2.0.x
Status: Closed
Resolution: Invalid
Priority: 5
Submitted By: Federico Sevilla III (jijo)
Assigned to: Nobody/Anonymous (nobody)
Summary: rfc822.parseaddress() in Util.py Invalid

Initial Comment:
The reference to rfc822.parseaddress() on line 160 of
Util.py in Mailman 2.0.12 is invalid. As of at least
Python 2.1 and Python 2.2, the rfc822 module does not
contain this function. This makes it impossible to use
add_members from the command line, although web-based
subscription still seems to work.

The pertinent traceback:

Traceback (most recent call last):
  File /usr/sbin/add_members, line 221, in ?
main()
  File /usr/sbin/add_members, line 195, in main
nres = ml.ApprovedAddMembers(nmembers, None, 0,
send_welcome_msg)
  File /usr/lib/mailman/Mailman/MailList.py, line
1097, in
ApprovedAddMembers
Utils.ValidateEmail(name)
  File /usr/lib/mailman/Mailman/Utils.py, line 160,
in ValidateEmail
realname,str = rfc822.parseaddress(str)
AttributeError: 'rfc822' module has no attribute
'parseaddress'

The fix is pretty simple. Simply replace

realname,str = rfc822.parseaddress(str)

on line 160 of Utils.py with

realname,str = rfc822.parseaddr(str)

--

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-08-16 11:51

Message:
Logged In: YES 
user_id=12800

Where did you get Mailman 2.0.12 from?  There is no
parseaddress() call in Utils.py in the official Mailman
2.0.13 release, and there was no change to this since
MM2.0.12.  Are you using some non-standard patch or local hack?

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=100103aid=594913group_id=103

___
Mailman-Developers mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman-21/listinfo/mailman-developers

[Mailman-Developers] [ mailman-Bugs-595132 ] No mail going out

[noreply]

Bugs item #595132, was opened at 2002-08-14 10:02
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=100103aid=595132group_id=103

Category: mail delivery
Group: 2.0.x
Status: Closed
Resolution: Invalid
Priority: 5
Submitted By: Terkel Olsen (terkel)
Assigned to: Nobody/Anonymous (nobody)
Summary: No mail going out

Initial Comment:
Hi there,
i have Installed Mailman manually on a NetBSD
for some reason its not in pkgsrc anymore. It installs
allmost fine, just had to fix a few GID's and point it to 
python, and then it appeared to install.

I created a list fine and it sent the e-mail to the admin
adress, but if i try to send anything to the list nothing 
gets send back. Its not even held for approval. The error 
log shows nothing and the maillog only shows this:

Aug 14 11:06:19 www sendmail[29601]: g7E96J229601: 
from=terkel, size=54, class=0, nrcpts=1, 
msgid=[EMAIL PROTECTED]
nierforlagene.dk, relay=terkel@localhost

Aug 14 11:06:19 www sendmail[29603]: g7E96J229601: 
to=|/usr/home/mailman/mailman/mail/wrapper post 
jokes, [EMAIL PROTECTED]
rforlagene.dk (1/0), delay=00:00:00, xdelay=00:00:00, 
mailer=prog, pri=30054, dsn=2.0.0, stat=Sent

But nothing further, so i guess it goes to the wrapper 
program but then no further...

Anyone experienced this before ? 

Terkel

--

Comment By: Nobody/Anonymous (nobody)
Date: 2002-08-16 08:58

Message:
Logged In: NO 

You are quite right about the cronjob, i have completely 
missed that section in the install file. Very sorry for creating a 
bug for this.

Thanks again

  Terkel

--

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-08-16 08:45

Message:
Logged In: YES 
user_id=12800

Sounds to me like you didn't install the cronjob to get
qrunner going (assuming you're using MM2.0 -- you don't say
in your bug report).

I don't think this is a bug.  Contact
[EMAIL PROTECTED] for more help.

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=100103aid=595132group_id=103

___
Mailman-Developers mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman-21/listinfo/mailman-developers

[Mailman-Developers] [ mailman-Bugs-596055 ] wrong charset in bounce notice

[noreply]

Bugs item #596055, was opened at 2002-08-16 14:20
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=100103aid=596055group_id=103

Category: bounce detection
Group: 2.1 beta
Status: Closed
Resolution: Accepted
Priority: 5
Submitted By: Simone Piunno (pioppo)
Assigned to: Nobody/Anonymous (nobody)
Summary: wrong charset in bounce notice

Initial Comment:
When a member is disabled because of too many bounces
detected, if bounce_notify_owner_on_disable is set the list
owner is notified with a message generated in Boucer.py
using a template file (bounce.txt).

The problem is that the generated message is MIME 
encoded and bounce.txt is attached with hardcoded 
charset=us-ascii, even if a translated template was used.

Attached you can find a one-liner patch


--

Comment By: Ousmane Wilane (wilane)
Date: 2002-08-16 15:59

Message:
Logged In: YES 
user_id=47556

Current cvs:
make install leads to this (Python 2.2):

Traceback (most recent call last):
  File bin/update, line 47, in ?
from Mailman import MailList
  File /usr/local/mailman/Mailman/MailList.py, line 51, in ?
from Mailman.Bouncer import Bouncer
  File string, line 193
if isinstance(msg, StringType):
 ^
SyntaxError: invalid syntax
make: *** [update] Error 1


--

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-08-16 14:41

Message:
Logged In: YES 
user_id=12800

Applied, thanks!

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=100103aid=596055group_id=103

___
Mailman-Developers mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman-21/listinfo/mailman-developers

[Mailman-Developers] [ mailman-Bugs-594913 ] rfc822.parseaddress() in Util.py Invalid

[noreply]

Bugs item #594913, was opened at 2002-08-14 14:19
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=100103aid=594913group_id=103

Category: command line scripts
Group: 2.0.x
Status: Closed
Resolution: Invalid
Priority: 5
Submitted By: Federico Sevilla III (jijo)
Assigned to: Nobody/Anonymous (nobody)
Summary: rfc822.parseaddress() in Util.py Invalid

Initial Comment:
The reference to rfc822.parseaddress() on line 160 of
Util.py in Mailman 2.0.12 is invalid. As of at least
Python 2.1 and Python 2.2, the rfc822 module does not
contain this function. This makes it impossible to use
add_members from the command line, although web-based
subscription still seems to work.

The pertinent traceback:

Traceback (most recent call last):
  File /usr/sbin/add_members, line 221, in ?
main()
  File /usr/sbin/add_members, line 195, in main
nres = ml.ApprovedAddMembers(nmembers, None, 0,
send_welcome_msg)
  File /usr/lib/mailman/Mailman/MailList.py, line
1097, in
ApprovedAddMembers
Utils.ValidateEmail(name)
  File /usr/lib/mailman/Mailman/Utils.py, line 160,
in ValidateEmail
realname,str = rfc822.parseaddress(str)
AttributeError: 'rfc822' module has no attribute
'parseaddress'

The fix is pretty simple. Simply replace

realname,str = rfc822.parseaddress(str)

on line 160 of Utils.py with

realname,str = rfc822.parseaddr(str)

--

Comment By: Federico Sevilla III (jijo)
Date: 2002-08-17 00:05

Message:
Logged In: YES 
user_id=9096

This is from the Debian package. I just downloaded the
package sources for the 2.0.12-3 package, and there is
nothing that changes the Utils.py file, and the Utils.py
file as claimed indeed comes with rfc822.parseaddr(str) and
not rfc822.parseaddress(str). Unfortunately because I
already modified my installed Utils.py to fix the problem I
was having, I cannot trace to see when the file was last
updated (this wasn't a fresh install but was an upgrade from
a previous version) to find out why it got changes.

My apologies for the hassles. Thank you for pointing out
that the distributed tarball comes with a Utils.py that was
not broken to begin with.

Cheers.

--

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-08-16 23:51

Message:
Logged In: YES 
user_id=12800

Where did you get Mailman 2.0.12 from?  There is no
parseaddress() call in Utils.py in the official Mailman
2.0.13 release, and there was no change to this since
MM2.0.12.  Are you using some non-standard patch or local hack?

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=100103aid=594913group_id=103

___
Mailman-Developers mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman-21/listinfo/mailman-developers

[Mailman-Developers] [ mailman-Bugs-594913 ] rfc822.parseaddress() in Util.py Invalid

[noreply]

Bugs item #594913, was opened at 2002-08-14 14:19
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=100103aid=594913group_id=103

Category: command line scripts
Group: 2.0.x
Status: Closed
Resolution: Invalid
Priority: 5
Submitted By: Federico Sevilla III (jijo)
Assigned to: Nobody/Anonymous (nobody)
Summary: rfc822.parseaddress() in Util.py Invalid

Initial Comment:
The reference to rfc822.parseaddress() on line 160 of
Util.py in Mailman 2.0.12 is invalid. As of at least
Python 2.1 and Python 2.2, the rfc822 module does not
contain this function. This makes it impossible to use
add_members from the command line, although web-based
subscription still seems to work.

The pertinent traceback:

Traceback (most recent call last):
  File /usr/sbin/add_members, line 221, in ?
main()
  File /usr/sbin/add_members, line 195, in main
nres = ml.ApprovedAddMembers(nmembers, None, 0,
send_welcome_msg)
  File /usr/lib/mailman/Mailman/MailList.py, line
1097, in
ApprovedAddMembers
Utils.ValidateEmail(name)
  File /usr/lib/mailman/Mailman/Utils.py, line 160,
in ValidateEmail
realname,str = rfc822.parseaddress(str)
AttributeError: 'rfc822' module has no attribute
'parseaddress'

The fix is pretty simple. Simply replace

realname,str = rfc822.parseaddress(str)

on line 160 of Utils.py with

realname,str = rfc822.parseaddr(str)

--

Comment By: Federico Sevilla III (jijo)
Date: 2002-08-17 00:06

Message:
Logged In: YES 
user_id=9096

This is from the Debian package. I just downloaded the
package sources for the 2.0.12-3 package, and there is
nothing that changes the Utils.py file, and the Utils.py
file as claimed indeed comes with rfc822.parseaddr(str) and
not rfc822.parseaddress(str). Unfortunately because I
already modified my installed Utils.py to fix the problem I
was having, I cannot trace to see when the file was last
updated (this wasn't a fresh install but was an upgrade from
a previous version) to find out why it got changes.

My apologies for the hassles. Thank you for pointing out
that the distributed tarball comes with a Utils.py that was
not broken to begin with.

Cheers.

--

Comment By: Federico Sevilla III (jijo)
Date: 2002-08-17 00:05

Message:
Logged In: YES 
user_id=9096

This is from the Debian package. I just downloaded the
package sources for the 2.0.12-3 package, and there is
nothing that changes the Utils.py file, and the Utils.py
file as claimed indeed comes with rfc822.parseaddr(str) and
not rfc822.parseaddress(str). Unfortunately because I
already modified my installed Utils.py to fix the problem I
was having, I cannot trace to see when the file was last
updated (this wasn't a fresh install but was an upgrade from
a previous version) to find out why it got changes.

My apologies for the hassles. Thank you for pointing out
that the distributed tarball comes with a Utils.py that was
not broken to begin with.

Cheers.

--

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-08-16 23:51

Message:
Logged In: YES 
user_id=12800

Where did you get Mailman 2.0.12 from?  There is no
parseaddress() call in Utils.py in the official Mailman
2.0.13 release, and there was no change to this since
MM2.0.12.  Are you using some non-standard patch or local hack?

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=100103aid=594913group_id=103

___
Mailman-Developers mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman-21/listinfo/mailman-developers

[Mailman-Developers] [ mailman-Bugs-594913 ] rfc822.parseaddress() in Util.py Invalid

[noreply]

Bugs item #594913, was opened at 2002-08-14 02:19
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=100103aid=594913group_id=103

Category: command line scripts
Group: 2.0.x
Status: Closed
Resolution: Invalid
Priority: 5
Submitted By: Federico Sevilla III (jijo)
Assigned to: Nobody/Anonymous (nobody)
Summary: rfc822.parseaddress() in Util.py Invalid

Initial Comment:
The reference to rfc822.parseaddress() on line 160 of
Util.py in Mailman 2.0.12 is invalid. As of at least
Python 2.1 and Python 2.2, the rfc822 module does not
contain this function. This makes it impossible to use
add_members from the command line, although web-based
subscription still seems to work.

The pertinent traceback:

Traceback (most recent call last):
  File /usr/sbin/add_members, line 221, in ?
main()
  File /usr/sbin/add_members, line 195, in main
nres = ml.ApprovedAddMembers(nmembers, None, 0,
send_welcome_msg)
  File /usr/lib/mailman/Mailman/MailList.py, line
1097, in
ApprovedAddMembers
Utils.ValidateEmail(name)
  File /usr/lib/mailman/Mailman/Utils.py, line 160,
in ValidateEmail
realname,str = rfc822.parseaddress(str)
AttributeError: 'rfc822' module has no attribute
'parseaddress'

The fix is pretty simple. Simply replace

realname,str = rfc822.parseaddress(str)

on line 160 of Utils.py with

realname,str = rfc822.parseaddr(str)

--

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-08-16 12:12

Message:
Logged In: YES 
user_id=12800

Ok, thanks for the update.

--

Comment By: Federico Sevilla III (jijo)
Date: 2002-08-16 12:06

Message:
Logged In: YES 
user_id=9096

This is from the Debian package. I just downloaded the
package sources for the 2.0.12-3 package, and there is
nothing that changes the Utils.py file, and the Utils.py
file as claimed indeed comes with rfc822.parseaddr(str) and
not rfc822.parseaddress(str). Unfortunately because I
already modified my installed Utils.py to fix the problem I
was having, I cannot trace to see when the file was last
updated (this wasn't a fresh install but was an upgrade from
a previous version) to find out why it got changes.

My apologies for the hassles. Thank you for pointing out
that the distributed tarball comes with a Utils.py that was
not broken to begin with.

Cheers.

--

Comment By: Federico Sevilla III (jijo)
Date: 2002-08-16 12:05

Message:
Logged In: YES 
user_id=9096

This is from the Debian package. I just downloaded the
package sources for the 2.0.12-3 package, and there is
nothing that changes the Utils.py file, and the Utils.py
file as claimed indeed comes with rfc822.parseaddr(str) and
not rfc822.parseaddress(str). Unfortunately because I
already modified my installed Utils.py to fix the problem I
was having, I cannot trace to see when the file was last
updated (this wasn't a fresh install but was an upgrade from
a previous version) to find out why it got changes.

My apologies for the hassles. Thank you for pointing out
that the distributed tarball comes with a Utils.py that was
not broken to begin with.

Cheers.

--

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-08-16 11:51

Message:
Logged In: YES 
user_id=12800

Where did you get Mailman 2.0.12 from?  There is no
parseaddress() call in Utils.py in the official Mailman
2.0.13 release, and there was no change to this since
MM2.0.12.  Are you using some non-standard patch or local hack?

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=100103aid=594913group_id=103

___
Mailman-Developers mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman-21/listinfo/mailman-developers

[Mailman-Developers] [ mailman-Bugs-594703 ] Bug canceling discardedmail

[noreply]

Bugs item #594703, was opened at 2002-08-13 14:06
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=100103aid=594703group_id=103

Category: None
Group: 2.1 beta
Status: Closed
Resolution: Fixed
Priority: 5
Submitted By: Garey Mills (gareytm)
Assigned to: Nobody/Anonymous (nobody)
Summary: Bug canceling discarded mail

Initial Comment:
When poster tries to cancel email, and moderator has 
already discarded it, Mailman reports a bug. Here is the 
trace:

Traceback:

Traceback (most recent call last):
  File /usr/local/mailman/scripts/driver, line 82, in 
run_main
main()
  File /usr/local/mailman/Mailman/Cgi/confirm.py, line 
141, in main
heldmsg_prompt(mlist, doc, cookie, *content[1:])
  File /usr/local/mailman/Mailman/Cgi/confirm.py, line 
612, in heldmsg_prompt
ign, sender, msgsubject, givenreason, ign, ign = 
mlist.GetRecord(id)
  File /usr/local/mailman/Mailman/ListAdmin.py, line 
163, in GetRecord
type, data = self.__db[id]
KeyError: 5





Python information:

 Variable
Value
 sys.version
 2.2.1 (#1, Jun 10 2002, 14:31:04) [GCC 2.95 
19990728 (release)] 
 sys.executable
 /usr/local/bin/python 
 sys.prefix
 /usr/local 
 sys.exec_prefix
 /usr/local 
 sys.path
 /usr/local 
 sys.platform
 osf1V4 




Environment variables:

Variable
  
 Value
 HTTP_COOKIE 
  
mailman+admin=280200693f28593d732800613
6616235613030333131303932383837653463343661
653733376234623536363661363939;
  
allusers+admin=280200696628593d732800353
73635316133633866323335346264373061613638646530
323436663963633066613131336131; asc+admin=;
  p-r-
demo+admin=28020069bb34593d73280034373
33562333563323038653463356264643637623566306462
6430333634313966333561353736 
 SERVER_SOFTWARE 
  Apache/1.3.26 (Unix) 
 PYTHONPATH 
  /usr/local/mailman 
 SCRIPT_FILENAME 
  /usr/local/mailman/cgi-bin/confirm 
 SERVER_ADMIN 
  [EMAIL PROTECTED] 
 SCRIPT_NAME 
  /mailman/confirm 
 SERVER_SIGNATURE 
 REQUEST_METHOD 
  GET 
 HTTP_HOST 
  www.lib.berkeley.edu 
 PATH_INFO 
  /p-r-
demo/690b69a8dccbfa63a5b1a8aa592f14597f517e87 
 SERVER_PROTOCOL 
  HTTP/1.0 
 QUERY_STRING 
 REQUEST_URI 
  /mailman/confirm/p-r-
demo/690b69a8dccbfa63a5b1a8aa592f14597f517e87 
 HTTP_ACCEPT 
  image/gif, image/x-xbitmap, image/jpeg, 
image/pjpeg, image/png, */* 
 HTTP_ACCEPT_CHARSET 
  iso-8859-1,*,utf-8 
 HTTP_USER_AGENT 
  Mozilla/4.79 [en] (Windows NT 5.0; U) 
 HTTP_CONNECTION 
  Keep-Alive 
 HTTP_REFERER 
  
http://us.f136.mail.yahoo.com/ym/ShowLetter?
MsgId=6112_8948012_210880_1238_476_0_10784YY=
54989inc=25order=downsort=datepos=0view=h
ead=box=Inbox
 SERVER_NAME 
  www.lib.berkeley.edu 
 REMOTE_ADDR 
  128.32.238.84 
 REMOTE_PORT 
  1342 
 HTTP_ACCEPT_LANGUAGE
  en 
 PATH_TRANSLATED 
  /data/_b/webdata/p-r-
demo/690b69a8dccbfa63a5b1a8aa592f14597f517e87 
 SERVER_PORT 
  80 
 GATEWAY_INTERFACE 
  CGI/1.1 
 HTTP_ACCEPT_ENCODING
  gzip 
 SERVER_ADDR 
  169.229.32.48 
 DOCUMENT_ROOT 
  /data/_b/webdata 

--

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-08-16 13:31

Message:
Logged In: YES 
user_id=12800

Fixed, thanks!

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=100103aid=594703group_id=103

___
Mailman-Developers mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman-21/listinfo/mailman-developers

[Mailman-Developers] [ mailman-Bugs-594703 ] Bug canceling discardedmail

[noreply]

Bugs item #594703, was opened at 2002-08-13 18:06
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=100103aid=594703group_id=103

Category: None
Group: 2.1 beta
Status: Closed
Resolution: Fixed
Priority: 5
Submitted By: Garey Mills (gareytm)
Assigned to: Nobody/Anonymous (nobody)
Summary: Bug canceling discarded mail

Initial Comment:
When poster tries to cancel email, and moderator has 
already discarded it, Mailman reports a bug. Here is the 
trace:

Traceback:

Traceback (most recent call last):
  File /usr/local/mailman/scripts/driver, line 82, in 
run_main
main()
  File /usr/local/mailman/Mailman/Cgi/confirm.py, line 
141, in main
heldmsg_prompt(mlist, doc, cookie, *content[1:])
  File /usr/local/mailman/Mailman/Cgi/confirm.py, line 
612, in heldmsg_prompt
ign, sender, msgsubject, givenreason, ign, ign = 
mlist.GetRecord(id)
  File /usr/local/mailman/Mailman/ListAdmin.py, line 
163, in GetRecord
type, data = self.__db[id]
KeyError: 5





Python information:

 Variable
Value
 sys.version
 2.2.1 (#1, Jun 10 2002, 14:31:04) [GCC 2.95 
19990728 (release)] 
 sys.executable
 /usr/local/bin/python 
 sys.prefix
 /usr/local 
 sys.exec_prefix
 /usr/local 
 sys.path
 /usr/local 
 sys.platform
 osf1V4 




Environment variables:

Variable
  
 Value
 HTTP_COOKIE 
  
mailman+admin=280200693f28593d732800613
6616235613030333131303932383837653463343661
653733376234623536363661363939;
  
allusers+admin=280200696628593d732800353
73635316133633866323335346264373061613638646530
323436663963633066613131336131; asc+admin=;
  p-r-
demo+admin=28020069bb34593d73280034373
33562333563323038653463356264643637623566306462
6430333634313966333561353736 
 SERVER_SOFTWARE 
  Apache/1.3.26 (Unix) 
 PYTHONPATH 
  /usr/local/mailman 
 SCRIPT_FILENAME 
  /usr/local/mailman/cgi-bin/confirm 
 SERVER_ADMIN 
  [EMAIL PROTECTED] 
 SCRIPT_NAME 
  /mailman/confirm 
 SERVER_SIGNATURE 
 REQUEST_METHOD 
  GET 
 HTTP_HOST 
  www.lib.berkeley.edu 
 PATH_INFO 
  /p-r-
demo/690b69a8dccbfa63a5b1a8aa592f14597f517e87 
 SERVER_PROTOCOL 
  HTTP/1.0 
 QUERY_STRING 
 REQUEST_URI 
  /mailman/confirm/p-r-
demo/690b69a8dccbfa63a5b1a8aa592f14597f517e87 
 HTTP_ACCEPT 
  image/gif, image/x-xbitmap, image/jpeg, 
image/pjpeg, image/png, */* 
 HTTP_ACCEPT_CHARSET 
  iso-8859-1,*,utf-8 
 HTTP_USER_AGENT 
  Mozilla/4.79 [en] (Windows NT 5.0; U) 
 HTTP_CONNECTION 
  Keep-Alive 
 HTTP_REFERER 
  
http://us.f136.mail.yahoo.com/ym/ShowLetter?
MsgId=6112_8948012_210880_1238_476_0_10784YY=
54989inc=25order=downsort=datepos=0view=h
ead=box=Inbox
 SERVER_NAME 
  www.lib.berkeley.edu 
 REMOTE_ADDR 
  128.32.238.84 
 REMOTE_PORT 
  1342 
 HTTP_ACCEPT_LANGUAGE
  en 
 PATH_TRANSLATED 
  /data/_b/webdata/p-r-
demo/690b69a8dccbfa63a5b1a8aa592f14597f517e87 
 SERVER_PORT 
  80 
 GATEWAY_INTERFACE 
  CGI/1.1 
 HTTP_ACCEPT_ENCODING
  gzip 
 SERVER_ADDR 
  169.229.32.48 
 DOCUMENT_ROOT 
  /data/_b/webdata 

--

Comment By: Garey Mills (gareytm)
Date: 2002-08-16 17:58

Message:
Logged In: YES 
user_id=555793

Barry -

Is there a patch you could send me?

Thanks;

Garey Mills [EMAIL PROTECTED]

--

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-08-16 17:31

Message:
Logged In: YES 
user_id=12800

Fixed, thanks!

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=100103aid=594703group_id=103

___
Mailman-Developers mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman-21/listinfo/mailman-developers

[Mailman-Developers] [ mailman-Bugs-596215 ] html bugs in 2.0.13

[noreply]

Bugs item #596215, was opened at 2002-08-16 11:57
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=100103aid=596215group_id=103

Category: Web/CGI
Group: 2.0.x
Status: Open
Resolution: None
Priority: 5
Submitted By: Chuq Von Rospach (chuqui)
Assigned to: Nobody/Anonymous (nobody)
Summary: html bugs in 2.0.13

Initial Comment:
Ran into some HTML bugs in 2.0.13. For instance, going to 
the listinfo/mailman-subscribers page and subscribing, it 
returns the confirmation is required warning.

It looks good, but view source it. An unterminated BODY 
tag, followed by a second body tag with a bgcolor, followed 
by a third body tag a couple of lines later.

There are also two /body tags, and the title is in the 
body, not in the head.

While it seems to format okay in browsers, it's seriously 
broken HTML, and it's driving mod_layout nuts, since it 
depends on the body tags to do header/footer insertions 
right. I think there's one other generated page with similar 
problems, too, but I'm not sure which it is yet.



--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=100103aid=596215group_id=103

___
Mailman-Developers mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman-21/listinfo/mailman-developers

Re: [Mailman-Developers] Anti-spam killer app?

[John W Baxter]

At 13:10 -0700 8/16/2002, Chuq Von Rospach wrote:
Take a look at this --

http://www.paulgraham.com/spam.html

It's a new technique for identifying spam. The more I look into the details,
the more I think we have the anti-spam killer app, becaues it tunes itself
to the individual (or site), adapts as the anti-spammers adapt, and the
technique used is fairly easy to implement and damn difficult for a spammer
to avoid

Damn, I wish I'd thought of this.

Me, too.  ;-)

I find it fascinating that the last URL reference at the bottom (yes, I
read that far) is to the page at Apple's site describing the filtering in
Apple's revised Mail.app in Mac OS X 10.2.

I think the idea has a lot of promise.

  --John

-- 
John Baxter   [EMAIL PROTECTED]  Port Ludlow, WA, USA

___
Mailman-Developers mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman-21/listinfo/mailman-developers

Re: [Mailman-Developers] Anti-spam killer app?

[Barry A. Warsaw]

 CVR == Chuq Von Rospach [EMAIL PROTECTED] writes:

CVR http://www.paulgraham.com/spam.html

CVR It's a new technique for identifying spam. The more I look
CVR into the details, the more I think we have the anti-spam
CVR killer app, becaues it tunes itself to the individual (or
CVR site), adapts as the anti-spammers adapt, and the technique
CVR used is fairly easy to implement and damn difficult for a
CVR spammer to avoid

CVR Damn, I wish I'd thought of this.

Indeed, and from the article...

 I don't know why I avoided trying the statistical approach for so
 long. I think it was because I got addicted to trying to identify
 spam features myself, as if I were playing some kind of competitive
 game with the spammers. (Nonhackers don't often realize this, but
 most hackers are very competitive.)

Of course you have to realize that 83% of hackers have no idea what
a statistical approach means .532 wink.  :)

On a serious note, who's gonna hack up the Python code for an MM2.1
prototype handler module?

-Barry

___
Mailman-Developers mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman-21/listinfo/mailman-developers

[Mailman-Developers] [ mailman-Bugs-571004 ] member_posting_only does not work

[noreply]

Bugs item #571004, was opened at 2002-06-19 03:28
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=100103aid=571004group_id=103

Category: security/privacy
Group: 2.0.x
Status: Pending
Resolution: Works For Me
Priority: 5
Submitted By: Josef Grosch (jgrosch)
Assigned to: Nobody/Anonymous (nobody)
Summary: member_posting_only does not work

Initial Comment:
Version 2.0.11 on FreeBSD 4.6

Mailman allows people who are not on the list are
allowed to post. member_posting_only is set yes but non
members are still posting.



--

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-08-16 17:57

Message:
Logged In: YES 
user_id=12800

Changing status to Pending waiting on more information.

--

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-08-09 15:32

Message:
Logged In: YES 
user_id=12800

Several reasons why this could appear so:

- mail headers are being forged, so they are passing the
membership tests
- the addresses are on the members accepted for posting
list (e.g. the `posters' variable)
- the postings are being held but a moderator is approving them

I can't reproduce this, so I'll need more information.  

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=100103aid=571004group_id=103

___
Mailman-Developers mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman-21/listinfo/mailman-developers

[Mailman-Developers] [ mailman-Bugs-566301 ] umbrella list: unsubscribe key public

[noreply]

Bugs item #566301, was opened at 2002-06-08 17:44
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=100103aid=566301group_id=103

Category: security/privacy
Group: 2.1 beta
Status: Open
Resolution: None
Priority: 5
Submitted By: Stefan Divjak (stdivjak)
Assigned to: Nobody/Anonymous (nobody)
Summary: umbrella list: unsubscribe key public

Initial Comment:
Mailman offers a feature to set up an umbrella-list, 
which is used if a list just has other lists as members.

Assume we have an umbrella-list U, which has to 
members, X and Y - both are also lists.

Now, cleverly, the monthly password reminders are 
not sent to X and Y, but to X-owner and Y-owner 
instead, so this information should reach the owners of 
the subscribed lists (sending a password reminder to 
X would mean giving each member of the X list the 
power to unsubscribe X from U etc.).

But: If a member of X or Y opens the member options 
page (http://my.server.net/mailman/options/U/X) and 
clicks on the unsubscribe button, the necessary key 
is mailed to X (and not to X-owner). This is probably 
not what we want. If the list archive is not private, the 
password is even available to everyone out there.

--

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-08-16 17:59

Message:
Logged In: YES 
user_id=12800

Umbrella lists are a hack that will eventually go away. 
Still, if they're there now they should at least be safer. 
Any chance you'd like to generate a patch for this problem?
 If not, I'm lowering the priority because it involves a
soon-to-be deprecated feature.

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=100103aid=566301group_id=103

___
Mailman-Developers mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman-21/listinfo/mailman-developers

[Mailman-Developers] [ mailman-Bugs-565706 ] user wrongly detected

[noreply]

Bugs item #565706, was opened at 2002-06-07 04:21
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=100103aid=565706group_id=103

Category: mail delivery
Group: 2.0.x
Status: Pending
Resolution: None
Priority: 5
Submitted By: Enrico Cherubini (bestkevin)
Assigned to: Nobody/Anonymous (nobody)
Summary: user wrongly detected

Initial Comment:
Hi,
I'm using mailman 2.0.6 and a user, that is in the
mailing list, is not able to write in it after I closed
the list to members only. He is member as I can see in
the members list, here is what happen:

Jun 07 09:31:06 2002 (29505) post to lugvr from .,
size=1350, success

the poster is identified as '.'here are headers of
an email he sent:

From: .::Spark::. [EMAIL PROTECTED]

If you need any further information you are welcome

--

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-08-16 18:00

Message:
Logged In: YES 
user_id=12800

No more information has been provided, and the submitter is
using a fairly outdated version.  I'm changing the status to
Pending, awaiting an update or more information.

--

Comment By: Nobody/Anonymous (nobody)
Date: 2002-07-10 14:51

Message:
Logged In: NO 


Has the user turned off mail delivery?

--

Comment By: Simone Piunno (pioppo)
Date: 2002-06-07 04:43

Message:
Logged In: YES 
user_id=227443

Ciao Enrico!

did you remember me?  I was pioppo on #linux-it @ IrcNET :)

I think 1st of all you should upgrade to Mailman 2.0.11 
and/or to a more recent Python (I guess you are using 
1.5.2)



--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=100103aid=565706group_id=103

___
Mailman-Developers mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman-21/listinfo/mailman-developers

[Mailman-Developers] [ mailman-Bugs-565706 ] user wrongly detected

[noreply]

Bugs item #565706, was opened at 2002-06-07 01:21
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=100103aid=565706group_id=103

Category: mail delivery
Group: 2.0.x
Status: Pending
Resolution: None
Priority: 5
Submitted By: Enrico Cherubini (bestkevin)
Assigned to: Nobody/Anonymous (nobody)
Summary: user wrongly detected

Initial Comment:
Hi,
I'm using mailman 2.0.6 and a user, that is in the
mailing list, is not able to write in it after I closed
the list to members only. He is member as I can see in
the members list, here is what happen:

Jun 07 09:31:06 2002 (29505) post to lugvr from .,
size=1350, success

the poster is identified as '.'here are headers of
an email he sent:

From: .::Spark::. [EMAIL PROTECTED]

If you need any further information you are welcome

--

Comment By: Nobody/Anonymous (nobody)
Date: 2002-08-16 16:36

Message:
Logged In: NO 

Yes I did turn off delivery.  I read the mail via the web interface.  
we are using version 2.0.12.




--

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-08-16 15:00

Message:
Logged In: YES 
user_id=12800

No more information has been provided, and the submitter is
using a fairly outdated version.  I'm changing the status to
Pending, awaiting an update or more information.

--

Comment By: Nobody/Anonymous (nobody)
Date: 2002-07-10 11:51

Message:
Logged In: NO 


Has the user turned off mail delivery?

--

Comment By: Simone Piunno (pioppo)
Date: 2002-06-07 01:43

Message:
Logged In: YES 
user_id=227443

Ciao Enrico!

did you remember me?  I was pioppo on #linux-it @ IrcNET :)

I think 1st of all you should upgrade to Mailman 2.0.11 
and/or to a more recent Python (I guess you are using 
1.5.2)



--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=100103aid=565706group_id=103

___
Mailman-Developers mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman-21/listinfo/mailman-developers

[Mailman-Developers] [ mailman-Bugs-553385 ] Translation strings

[noreply]

Bugs item #553385, was opened at 2002-05-07 14:45
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=100103aid=553385group_id=103

Category: Web/CGI
Group: 2.1 beta
Status: Closed
Resolution: Fixed
Priority: 5
Submitted By: Daniel Buchmann (avalon)
Assigned to: Nobody/Anonymous (nobody)
Summary: Translation strings

Initial Comment:
#: Mailman/Gui/ContentFilter.py:38
Minor typo; the entry reads: Policies concerning
concerning the content [...]

#: Mailman/Commands/cmd_set.py:186
msgid %(status)s (%(how)s on %(date)s)
I'm not sure I fully understand what this is.
status = delivery status? (disabled/enabled?)
how = how it was disabled?
date = the date it happened?
How is the date written here? In english? According to
the user's language setting? According to the locale?
I believe this information is needed for many
languages, to be able to translate this entry in the
correct way...

#: Mailman/Commands/cmd_set.py
None of the commands should be translated, right?
Should the various set options be translated? (e.g.
'ack', 'delivery', 'digest', etc.)

If yes, then the output of the set help command would
give the users a translated explanation to english
commands. When they do set show, the various options
will also be translated, but english commands must be
sent to the listname-request address, right? It is
also currently not possible to translate the 'digest'
option (there is no catalog entry for it). And why does
the 'delivery' option have its own entries, when all
the others have entries like this: ack %(onoff)s ?

If no, then several cmd_set.py entries could probably
be removed from the catalog, or they must be left blank
so they default to their english value.


--

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-08-16 20:29

Message:
Logged In: YES 
user_id=12800

Fixed the typo in your patch, thanks.

As for your questions:

- we really have no architecture to do localization of dates
unfortunately.  The bit in cmd_set.py is trying to tell a
user how and when they got disabled, e.g. something like
disabled (due to bounces on somedate...).  We'll have
to live with US-centric formats here for now.

- correct, none of the commands should be translated. 
Eventually we may want to localize cmd_set.py and other
email commands, but that's not well supported now. 

- thanks for mentioning the bug in the marking of the digest
options.  I'll fix that too.

- digest has its own entries because there are three
choices.  does it make a difference for how you would add
translations?

- i'm not sure what catalog entries should be removed.  The
current mapping between commands and methods is pretty
static ('digest' command - set_digest()).

Thanks

--

Comment By: Simone Piunno (pioppo)
Date: 2002-05-10 15:54

Message:
Logged In: YES 
user_id=227443




--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=100103aid=553385group_id=103

___
Mailman-Developers mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman-21/listinfo/mailman-developers

[Mailman-Developers] Re: Anti-spam killer app?

[Harald Koch]

 Damn, I wish I'd thought of this.

A naive google search finds papers 4 years old discussing the problem,
which makes me wonder why nobody has implemented this before now...

-- 
Harald Koch [EMAIL PROTECTED]

It takes a child to raze a village.
-Michael T. Fry

___
Mailman-Developers mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman-21/listinfo/mailman-developers

[Mailman-Developers] [ mailman-Feature Requests-550462 ] New feature: Automoderatemicrosoft user

[noreply]

Feature Requests item #550462, was opened at 2002-04-29 21:53
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=350103aid=550462group_id=103

Category: None
Group: None
Status: Open
Resolution: Rejected
Priority: 5
Submitted By: Mark Whitis (whitis)
Assigned to: Nobody/Anonymous (nobody)
Summary: New feature: Automoderate microsoft user

Initial Comment:


I am not using mailman at the moment but I was looking at its feature list and planned 
upgrades and found this missing.  And it could be added

in a very general form that could support

many other uses.



Reason for suggesting: everytime I post a message

on a Linux list, I get a bunch of virus messages

from bozos who have subscribed to those lists

from a windows box.  And I am certainly not

alone in that respect.  Usually these messages

do not arrive via the list but are sent to anyone

who posts to the list (often by lurkers).  Users of

real operating systems who subscribe to lists related to those should not be 
inconvinienced

by those who use microsoft products, there of
all places.

I would like to suggest that future versions of

Mailman include a feature (selected by the moderator)

which automatically takes certain actions based

on the subscibers email client.  This feature

could be activated based on the message headers

in the replies to subscription confirmation messages.


Actions could include:

   - Placing the user in moderated status

 (prevents sending virus to the list
 directly but doesn't prevent the virus
 from getting addresses from the user).
   - Cancelling the subscription

   - Sending a warning message to the user

   - Requiring the user to send a control message
 agreeing that their virus software will
 be kept up to date.
   - hide or mung all email addresses in copies
 of messages delivered to this user so
 email worms/viruses cannot harvest them.
The email client status could be updated when the user sends a new control message.  



Optionally, it could also detect microsoft platforms via the browser ID when people 
sign on via the web site.



Detection could be controlled by a configuration file listing with four fields: 
action, mail/web, field,

and regex:

   ACCEPT MAIL X-Mailer .*Microsoft Sucks.*

   REJECT MAIL X-Mailer .*Microsoft Outlook.*

   REJECT MAIL X-Mimeole .*Microsoft Exchange.*

   REJECT WEB Browser-ID .*Internet Explorer.*

  (note: this would be triggered by opera

  in identify as Internet Explorer mode, but

  the user can switch to identify as opera).

   REJECT WEB Browser-ID .*Windows 95.*

   REJECT WEB Browser-ID .*Windows 98.*

   REJECT WEB Browser-ID .*Windows NT.*

   REJECT WEB Browser-ID .*Windows ME.*

   REJECT WEB Browser-ID .*Windows 2000.*

   REJECT WEB Browser-ID .*Win16.*

   REJECT WEB Browser-ID .*Win32.*

   REJECT WEB Browser-ID .*MSIE.*



If you place someone on moderated status based on their mail client or web browser, 
the reason

for moderation should be noted so that they can

be automatically un-moderated (if otherwise consistent with policy) when they use a 
real computer to access the list.



This feature could also be used to protect some

protection against other problems, as well.  Spam,

   REJECT MAIL From .*hotmail.com.*

   REJECT MAIL Subject: .*casino.*

   REJECT ATTACH Content-Type: application/octet-stream

   REJECT ATTACH Content-Type: audio/x-wav

   REJECT ATTACH Content-Type: audio/x-midi

   REJECT BODY insurance

   MODERATE-MSG BODY profaneword





The config file could be XMLized:

filter action=reject source=mail header=X-Mailer contents=.*microsoft.* /



Possible Extensions:

   action: make actions instead and allow a comma

   separated list (or even nested XML action   tags)

 moderate-msg

 moderate-user

 unmoderate-user

 strip-attachments

 strip-attachment

 bounce-message

 append-boilerplate

 

source: comma separated list

WEB_POST, WEB_CONTROL, MAIL_POST, MAIL_CONTROL, POST_BODY, 
POST_ATTACHMENT_HDR,

  POST_ATTACHMENT_BODY.



 blacklist: added field.

 .rss.mail-abuse.org

 .dul-mail-abuse.org

Note that for the Dial Up list, this should

   only be applied to the first Received line

   added by the mail server itself.



  user-status: the users existing status

  (normal, moderated, moderated-newbie,

   moderated-badsoftware, trusted,   

   moderator, list_owner, etc.)

   could be considered in applying filters.



XML structure could be much more complicated, as

well.



   filter userclass=... source=...

   pattern

   /pattern

   pattern

  exception

  pattern

  /pattern

  /exception

/pattern

blacklist

/blacklist

   /filter



One could also allow a user so detected to subscribe only 

[Mailman-Developers] [ mailman-Bugs-550314 ] Sending to multiple lists chooses one.

[noreply]

Bugs item #550314, was opened at 2002-04-29 14:48
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=100103aid=550314group_id=103

Category: mail delivery
Group: 2.0.x
Status: Closed
Resolution: Works For Me
Priority: 5
Submitted By: Jeff Posner (jposnersails)
Assigned to: Nobody/Anonymous (nobody)
Summary: Sending to multiple lists chooses one.

Initial Comment:
When I send a single message addressed as multiple 
lists on to 'TO:' line, each recipient receives 
exactly one copy.  If a single user is a memeber of 
more than one list, he receives the copy to 
a seemingly random list.

I am new to this version (just upgraded from 1.x) and 
have not seen this problem before.

Thanks.

--

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-08-16 20:34

Message:
Logged In: YES 
user_id=12800

I suspect nobody's analysis might be closer to the truth.
 Certainly we cross post all the time with MM 2.0.13 and
have never seen a problem.

--

Comment By: Nobody/Anonymous (nobody)
Date: 2002-05-02 01:52

Message:
Logged In: NO 

If your users run Cyrus, or some similar mail system, 
messages with duplicate message-IDs are only stored once. 
This may, or may not, be relevant.

--

Comment By: Dan Mick (dmick)
Date: 2002-05-01 17:54

Message:
Logged In: YES 
user_id=10725

Just tested with close-to-current 2.1CVS; it works for me.
Two test lists, one post with both lists on To: line,
I get two copies as expected.

What version are you running?

It might be worth checking the archives to see if the
message got to both places; maybe one list is broken.


--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=100103aid=550314group_id=103

___
Mailman-Developers mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman-21/listinfo/mailman-developers

[Mailman-Developers] [ mailman-Bugs-593454 ] NewsRunner error

[noreply]

Bugs item #593454, was opened at 2002-08-10 15:52
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=100103aid=593454group_id=103

Category: nntp/news
Group: 2.1 beta
Status: Closed
Resolution: Fixed
Priority: 5
Submitted By: Simone Piunno (pioppo)
Assigned to: Nobody/Anonymous (nobody)
Summary: NewsRunner error

Initial Comment:
Just updated to Mailman 2.1b3:

Aug 10 17:18:57 2002 (10526) Uncaught runner exception: len() of unsized object
Aug 10 17:18:57 2002 (10526) Traceback (most recent call last):
  File /home/mailman21/Mailman/Queue/Runner.py, line 105, in _oneloop
self._onefile(msg, msgdata)
  File /home/mailman21/Mailman/Queue/Runner.py, line 154, in _onefile
keepqueued = self._dispose(mlist, msg, msgdata)
  File /home/mailman21/Mailman/Queue/NewsRunner.py, line 56, in _dispose
prepare_message(mlist, msg, msgdata)
  File /home/mailman21/Mailman/Queue/NewsRunner.py, line 132, in prepare_message
count = len(email.Iterators.body_line_iterator(msg))
TypeError: len() of unsized object



--

Comment By: Ron Jarrell (jarrell)
Date: 2002-08-17 00:56

Message:
Logged In: YES 
user_id=34619

Hey, Barry, I'm getting the same thing with my 
installation, with straight python 2.2 everywhere (I don't 
*have* 1.5.2 installed anymore).


--

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-08-16 21:35

Message:
Logged In: YES 
user_id=12800

Fixed now, thanks!

--

Comment By: Simone Piunno (pioppo)
Date: 2002-08-16 13:33

Message:
Logged In: YES 
user_id=227443

I have installed both 1.5.2 and 2.2.1.
Mailman has been configured --with-python=/usr/bin/python2 
but a couple files are still referring to the old python, at least
Mailman/Archiver/pipermail.py and Mailman/Post.py


--

Comment By: Barry A. Warsaw (bwarsaw)
Date: 2002-08-15 22:37

Message:
Logged In: YES 
user_id=12800

Two questions, what version of Python are you running, and
can you upload the .pck file that's left in qfiles/shunt?

--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=100103aid=593454group_id=103

___
Mailman-Developers mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman-21/listinfo/mailman-developers

Re: [Mailman-Developers] Anti-spam killer app?

[Chuq Von Rospach]

On 8/16/02 5:40 PM, Barry A. Warsaw [EMAIL PROTECTED] wrote:
 I actually think we're getting really close, and I'm psyched about all
 the great feedback I'm getting on beta 3.  I'll probably release a
 beta 4 this weekend, and then I want to get serious wink about a
 release schedule.

Which is perfect timing, because I've installed jaguar on my new test
server, and I'm going to spend time this weekend building out the
environment, which means sometime in the next few days, I'm going to load up
Mailman and see what happens...


-- 
Chuq Von Rospach, Architech
[EMAIL PROTECTED] -- http://www.chuqui.com/

No! No! Dead girl, OFF the table! -- Shrek



___
Mailman-Developers mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman-21/listinfo/mailman-developers

Re: [Mailman-Developers] Anti-spam killer app?

[Barry A. Warsaw]

 CVR == Chuq Von Rospach [EMAIL PROTECTED] writes:

CVR Which is perfect timing, because I've installed jaguar on my
CVR new test server, and I'm going to spend time this weekend
CVR building out the environment, which means sometime in the
CVR next few days, I'm going to load up Mailman and see what
CVR happens...

Cool!  Depending on how adventurous you are, you may want to check out
Python 2.3's cvs.  Jack Jansen's been doing a lot of work on providing
Carbon support for Python, if I've been following his checkins
correctly.  Haven't played with it, but and of course Python 2.3's not
even in alpha yet, but we use it every day and it's pretty stable
(performance-wise, mostly if not feature-wise).

-Barry

___
Mailman-Developers mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman-21/listinfo/mailman-developers

Re: [Mailman-Developers] Comments on smart address matching?

[Barry A. Warsaw]

 CVR == Chuq Von Rospach [EMAIL PROTECTED] writes:

CVR I wouldn't fix. Instead, I'd focus on adding address
CVR aliasing, and let people add in those as aliases. It fixes a
CVR more general issue (I have all these addresses, and want one
CVR subscription) and they get fixed as a side effect of the
CVR more general fix.

Agreed.

CVR They would still have to add in their aliases. I see at as
CVR motivation to convince their admins to fix the real
CVR problem... (giggle)

Agreed!
-Barry

___
Mailman-Developers mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman-21/listinfo/mailman-developers

Re: [Mailman-Developers] Anti-spam killer app?

[Darrell Fuhriman]

Satya [EMAIL PROTECTED] writes:

 don't deactivate me!) thingy which'll be called from procmail, and
 another perl thingy which'll be called from crontab ... well, never
 mind the details.

Yah, I threw it together this afternoon, too.

Sorry, guys, I did it in perl, too.  I'm just trying to collect
enough spam to seed it.  I only had a couple hundred laying
around.  I can start doing some more serious testing.  So far, it
seems to do the right thing.

The code's rather un-polished, but you're welcome to what I've
got so far.

Darrell

___
Mailman-Developers mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman-21/listinfo/mailman-developers

Re: [Mailman-Developers] Anti-spam killer app?

[Satya]

On Aug 17, 2002 at 00:38, Barry A. Warsaw wrote:

That's okay, I'm going to shame Tim Peters into building an ultra
efficient Python version, which we'll just wrap in the MM handler API
and be done with it. :)

But... but... what will *I* use?

On Aug 16, 2002 at 21:55, Darrell Fuhriman wrote:

Yah, I threw it together this afternoon, too.

The code's rather un-polished, but you're welcome to what I've
got so far.

Awesome, can I have it?

-- 
Satya. URL:http://satya.virtualave.net/
Please feel free to blither now. -- THHGTTG


___
Mailman-Developers mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman-21/listinfo/mailman-developers

[Mailman-Developers] [ mailman-Bugs-596361 ] rejection-notice not translated

[noreply]

Bugs item #596361, was opened at 2002-08-17 06:21
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=100103aid=596361group_id=103

Category: Web/CGI
Group: 2.1 beta
Status: Open
Resolution: None
Priority: 5
Submitted By: Tokio Kikuchi (tkikuchi)
Assigned to: Nobody/Anonymous (nobody)
Summary: rejection-notice not translated

Initial Comment:
on the admindb screen, detailed description of the held
messages include 'rejection-notice' field to be sent to the
message sender but the default value in the text form is
in english and not translated into the list-preferred
language. 

Following short patch may work:
--- admindb.py.orig Fri Aug 16 11:39:53 2002
+++ admindb.py  Sat Aug 17 14:57:37 2002
@@ -595,8 +595,8 @@
 t.AddRow([
 Bold(_('If you reject this post,brplease
explain (optional):')),
 TextArea('comment-%d' % id, rows=4, cols=80,
- text =
Utils.wrap(msgdata.get('rejection-notice',
-   _('[No
explanation given]')),
+ text =
Utils.wrap(_(msgdata.get('rejection-notice',
+   _('[No
explanation given]'))),
column=80))
 ])
 row, col = t.GetCurrentRowIndex(),
t.GetCurrentCellIndex()





--

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detailatid=100103aid=596361group_id=103

___
Mailman-Developers mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman-21/listinfo/mailman-developers