From juhani.ollikainen at dnainternet.net  Mon Jan  1 07:38:30 2007
From: juhani.ollikainen at dnainternet.net (Juhani Ollikainen)
Date: Mon, 1 Jan 2007 08:38:30 +0200
Subject: OK
Message-ID: <000c01c72d6f$74277070$4df295d4@antec>


Juhani Ollikainen
e-mail. juhani.ollikaineneen at dnainternet.net
           ad.jo at dnainternet.net 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.python.org/pipermail/mailman-coders/attachments/20070101/2944a06d/attachment.htm 

From noreply at sourceforge.net  Fri Jan  5 15:18:46 2007
From: noreply at sourceforge.net (SourceForge.net)
Date: Fri, 05 Jan 2007 06:18:46 -0800
Subject: [ mailman-Bugs-1628753 ] Outbound messages have domain fubar'd
Message-ID: <E1H2puA-00049f-I6@sc8-sf-web10.sourceforge.net>

Bugs item #1628753, was opened at 2007-01-05 09:18
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1628753&group_id=103

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: mail delivery
Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Michael Reynolds (wshs)
Assigned to: Nobody/Anonymous (nobody)
Summary: Outbound messages have domain fubar'd

Initial Comment:
This is using a port install of mailman in FreeBSD, with version 2.1.9_1. When sending messages to users, either triggered by the web interface, or a message from a user to a mailman controlled email address, while using qmail with the included qmail-to-mailman script, the following errors litter my logs:

2007-01-05 07:53:25.924843500 info msg 5348160: bytes 1233 from <sirv-bounces at lists.delinked.us> qp 98922 uid 89
2007-01-05 07:53:25.961231500 starting delivery 17: msg 5348160 to remote munged at gmail.comyes

Note the 'gmail.comyes'.
A 'yes' is appended to every outbound message's target domain, thus making delivery impossible.

I spent a few days thinking it was something I messed up, so I went through my entire system setup checking everything that could influence mail. I then discovered the problem is specific to mailman. Not sure what info I can provide to help, but I'd be willing to supply upon request. I am using FreeBSD 5.5, Python 2.5.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1628753&group_id=103

From noreply at sourceforge.net  Fri Jan  5 16:11:17 2007
From: noreply at sourceforge.net (SourceForge.net)
Date: Fri, 05 Jan 2007 07:11:17 -0800
Subject: [ mailman-Bugs-1628753 ] Outbound messages have domain fubar'd
Message-ID: <E1H2qiz-0000YU-Qf@sc8-sf-monitor2.sourceforge.net>

Bugs item #1628753, was opened at 2007-01-05 06:18
Message generated for change (Comment added) made by msapiro
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1628753&group_id=103

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: mail delivery
Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Michael Reynolds (wshs)
Assigned to: Nobody/Anonymous (nobody)
Summary: Outbound messages have domain fubar'd

Initial Comment:
This is using a port install of mailman in FreeBSD, with version 2.1.9_1. When sending messages to users, either triggered by the web interface, or a message from a user to a mailman controlled email address, while using qmail with the included qmail-to-mailman script, the following errors litter my logs:

2007-01-05 07:53:25.924843500 info msg 5348160: bytes 1233 from <sirv-bounces at lists.delinked.us> qp 98922 uid 89
2007-01-05 07:53:25.961231500 starting delivery 17: msg 5348160 to remote munged at gmail.comyes

Note the 'gmail.comyes'.
A 'yes' is appended to every outbound message's target domain, thus making delivery impossible.

I spent a few days thinking it was something I messed up, so I went through my entire system setup checking everything that could influence mail. I then discovered the problem is specific to mailman. Not sure what info I can provide to help, but I'd be willing to supply upon request. I am using FreeBSD 5.5, Python 2.5.

----------------------------------------------------------------------

>Comment By: Mark Sapiro (msapiro)
Date: 2007-01-05 07:11

Message:
Logged In: YES 
user_id=1123998
Originator: NO

There are many people using Mailman 2.1.9 and probably several using the
FreeBSD port. This is the first report of this issue. It may have
something to do with Python 2.5 or perhaps the combination of the FreeBSD
port and Python 2.5.

The following is an interactive Python snippet (Python responses other
than prompts omitted) that sends mail in exactly the same way as Mailman
does. If you have changed the assignments of SMTPHOST and/or SMTPPORT in
mm_cfg.py, change them here too. Try this and see if the problem exists
with it. If so, the problem is with Python, not Mailman.

>>> import smtplib
>>> msg = """Subject: Test Message
... Message-Id: <some-id at nowhere.example.com>
... From: poster at example.com
... To: you
...
... The body
... """
>>> rcpts = ['user1 at example.com', 'userb at example.com']
>>> env = 'list-bounces at example.com'
>>> SMTPHOST = 'localhost'
>>> SMTPPORT = 0
>>> x = smtplib.SMTP()
>>> x.set_debuglevel(1)
>>> x.connect(SMTPHOST, SMTPPORT)
>>> x.sendmail(env, rcpts, msg)
>>> x.quit()


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1628753&group_id=103

From noreply at sourceforge.net  Sat Jan  6 08:40:57 2007
From: noreply at sourceforge.net (SourceForge.net)
Date: Fri, 05 Jan 2007 23:40:57 -0800
Subject: [ mailman-Feature Requests-673265 ] Post confirmation + moderation
Message-ID: <E1H36Aj-0000XO-T8@sc8-sf-web1.sourceforge.net>

Feature Requests item #673265, was opened at 2003-01-23 19:39
Message generated for change (Comment added) made by tpetazzoni
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=673265&group_id=103

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Samuel Tardieu (samtardieu)
Assigned to: Nobody/Anonymous (nobody)
Summary: Post confirmation + moderation

Initial Comment:
The following scheme (implemented by me for Sympa as a
scenario some time ago) leads to a spam-free
mailing-list with almost no work from the
moderator.

When a mail arrive and should be held for any reason
(sender not in
subscriber list, list not in to: or cc:, too many
recipients), ask the
alleged sender to confirm its post then hold it for
moderation when
the sender confirms its intention to post.

This way, spam (whose confirmation request will almost
never be answered) is not presented to the moderators,
while mail sent by
humans will.

It would be great to have this feature in mailman.

----------------------------------------------------------------------

Comment By: Thomas Petazzoni (tpetazzoni)
Date: 2007-01-06 08:40

Message:
Logged In: YES 
user_id=1145572
Originator: NO

I also really would like to see this feature implemented in Mailman. I'm
the mailing list moderator of several lists managed by Mailman, and I'm
really bored by all the spam I have to delete from the administrative
interface. Of course, I could configure the lists to drop e-mails from
non-members, but as some of my lists target a public that doesn't really
understand the way mailing lists work, I prefer to keep the solution of
moderating valid e-mails by hand.

Having a mechanism where a e-mail would be send to the sender asking for
confirmation would be nice. Sympa has this feature for a long time, but I'd
really prefer sticking with Mailman, I like it better.

----------------------------------------------------------------------

Comment By: James Andrewartha (watha)
Date: 2006-11-13 03:48

Message:
Logged In: YES 
user_id=460267

http://viewmtn.angrygoats.net/revision/diff/dfedaca2816739f4f052d21247f6877f5ee39905/with/c6835f6646f467e9a012823b0817e17e152f9811
has an implementation for this, although there's a few other
features mixed into the diff as well.

----------------------------------------------------------------------

Comment By: Lucas Nussbaum (lnu)
Date: 2006-11-11 11:52

Message:
Logged In: YES 
user_id=527142

Also, this could be implemented in a greylist-like way: the
sender would have to confirm his first post, and then, its
mails would get auto-accepted for a few hours/days.

----------------------------------------------------------------------

Comment By: Lucas Nussbaum (lnu)
Date: 2006-11-11 11:34

Message:
Logged In: YES 
user_id=527142

Hi,

This feature would really be great to have in mailman.
Additionnally, a web-based confirmation interface could be
added, with an image-based confirmation, to prevent robots
from auto-confirming their posts. Is it planned ? I'm a bit
concerned by the fact that this feature request was posted
more than 3 years ago.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=673265&group_id=103

From noreply at sourceforge.net  Sat Jan  6 15:11:33 2007
From: noreply at sourceforge.net (SourceForge.net)
Date: Sat, 06 Jan 2007 06:11:33 -0800
Subject: [ mailman-Feature Requests-673265 ] Post confirmation + moderation
Message-ID: <E1H3CGj-0007Uc-Ec@sc8-sf-web6.sourceforge.net>

Feature Requests item #673265, was opened at 2003-01-23 13:39
Message generated for change (Comment added) made by bwarsaw
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=673265&group_id=103

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Samuel Tardieu (samtardieu)
Assigned to: Nobody/Anonymous (nobody)
Summary: Post confirmation + moderation

Initial Comment:
The following scheme (implemented by me for Sympa as a
scenario some time ago) leads to a spam-free
mailing-list with almost no work from the
moderator.

When a mail arrive and should be held for any reason
(sender not in
subscriber list, list not in to: or cc:, too many
recipients), ask the
alleged sender to confirm its post then hold it for
moderation when
the sender confirms its intention to post.

This way, spam (whose confirmation request will almost
never be answered) is not presented to the moderators,
while mail sent by
humans will.

It would be great to have this feature in mailman.

----------------------------------------------------------------------

>Comment By: Barry A. Warsaw (bwarsaw)
Date: 2007-01-06 09:11

Message:
Logged In: YES 
user_id=12800
Originator: NO

Mailman 2.2 will definitely have this feature in some form or another.

----------------------------------------------------------------------

Comment By: Thomas Petazzoni (tpetazzoni)
Date: 2007-01-06 02:40

Message:
Logged In: YES 
user_id=1145572
Originator: NO

I also really would like to see this feature implemented in Mailman. I'm
the mailing list moderator of several lists managed by Mailman, and I'm
really bored by all the spam I have to delete from the administrative
interface. Of course, I could configure the lists to drop e-mails from
non-members, but as some of my lists target a public that doesn't really
understand the way mailing lists work, I prefer to keep the solution of
moderating valid e-mails by hand.

Having a mechanism where a e-mail would be send to the sender asking for
confirmation would be nice. Sympa has this feature for a long time, but I'd
really prefer sticking with Mailman, I like it better.

----------------------------------------------------------------------

Comment By: James Andrewartha (watha)
Date: 2006-11-12 21:48

Message:
Logged In: YES 
user_id=460267

http://viewmtn.angrygoats.net/revision/diff/dfedaca2816739f4f052d21247f6877f5ee39905/with/c6835f6646f467e9a012823b0817e17e152f9811
has an implementation for this, although there's a few other
features mixed into the diff as well.

----------------------------------------------------------------------

Comment By: Lucas Nussbaum (lnu)
Date: 2006-11-11 05:52

Message:
Logged In: YES 
user_id=527142

Also, this could be implemented in a greylist-like way: the
sender would have to confirm his first post, and then, its
mails would get auto-accepted for a few hours/days.

----------------------------------------------------------------------

Comment By: Lucas Nussbaum (lnu)
Date: 2006-11-11 05:34

Message:
Logged In: YES 
user_id=527142

Hi,

This feature would really be great to have in mailman.
Additionnally, a web-based confirmation interface could be
added, with an image-based confirmation, to prevent robots
from auto-confirming their posts. Is it planned ? I'm a bit
concerned by the fact that this feature request was posted
more than 3 years ago.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=673265&group_id=103

From noreply at sourceforge.net  Sun Jan  7 17:45:36 2007
From: noreply at sourceforge.net (SourceForge.net)
Date: Sun, 07 Jan 2007 08:45:36 -0800
Subject: [ mailman-Bugs-1629971 ] Repeat Emails from Mailman 2.1.9
Message-ID: <E1H3b9M-0008P9-2u@sc8-sf-web2.sourceforge.net>

Bugs item #1629971, was opened at 2007-01-07 16:45
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1629971&group_id=103

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: mail delivery
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: mfr301 (mfr301)
Assigned to: Nobody/Anonymous (nobody)
Summary: Repeat Emails from Mailman 2.1.9

Initial Comment:
Hello,

 

I currently use your software as a reseller client with ResellerZoom.com.  3 days ago my clients and myself started receiving numerous repeat emails.  The emails were being sent by the mailing list section of Mailman 2.1.9.   The problem is that every time (Since it started and has been going on for 3 straight days), I receive emails, they are the SAME emails over and over.  Their not visible on the mailing list, their not in a que, and their not in pending messages.  

 

I have a client who kept deleting mailing lists (like test at .....) and it kept re-appearing.  I have been on line with the ResellerZoom tech support CONSTANTLY from my blackberry for 3 days since the problem started and they have not been able to rectify the problem.  Is there anything you can suggest?


Mike
mfr301 at aol.com

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1629971&group_id=103

From noreply at sourceforge.net  Sun Jan  7 19:21:04 2007
From: noreply at sourceforge.net (SourceForge.net)
Date: Sun, 07 Jan 2007 10:21:04 -0800
Subject: [ mailman-Bugs-1629971 ] Repeat Emails from Mailman 2.1.9
Message-ID: <E1H3cdk-0002wy-E8@sc8-sf-web11.sourceforge.net>

Bugs item #1629971, was opened at 2007-01-07 08:45
Message generated for change (Comment added) made by msapiro
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1629971&group_id=103

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: mail delivery
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: mfr301 (mfr301)
Assigned to: Nobody/Anonymous (nobody)
Summary: Repeat Emails from Mailman 2.1.9

Initial Comment:
Hello,

 

I currently use your software as a reseller client with ResellerZoom.com.  3 days ago my clients and myself started receiving numerous repeat emails.  The emails were being sent by the mailing list section of Mailman 2.1.9.   The problem is that every time (Since it started and has been going on for 3 straight days), I receive emails, they are the SAME emails over and over.  Their not visible on the mailing list, their not in a que, and their not in pending messages.  

 

I have a client who kept deleting mailing lists (like test at .....) and it kept re-appearing.  I have been on line with the ResellerZoom tech support CONSTANTLY from my blackberry for 3 days since the problem started and they have not been able to rectify the problem.  Is there anything you can suggest?


Mike
mfr301 at aol.com

----------------------------------------------------------------------

>Comment By: Mark Sapiro (msapiro)
Date: 2007-01-07 10:21

Message:
Logged In: YES 
user_id=1123998
Originator: NO

Until you determine that there actually is a bug in Mailman, it would be
better to discuss issues like this on the mailman-users at python.org list.
See <http://mail.python.org/mailman/listinfo/mailman-users>.

You say the mails you receive were sent by Mailman, but they are 'not
visible on the mailing list'. What do you mean by 'not visible on the
mailing list' and how do you know they are sent by Mailman?

Re: deleted lists reappearing, How are the lists being deleted?

It might be more productive for ResellerZoom to contact
mailman-users at python.org directly.

Also, if the Mailman is cPanel's, see
<http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq06.011.htp>.




----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1629971&group_id=103

From noreply at sourceforge.net  Thu Jan 11 13:17:43 2007
From: noreply at sourceforge.net (SourceForge.net)
Date: Thu, 11 Jan 2007 04:17:43 -0800
Subject: [ mailman-Patches-630339 ] create list with multiple owners
Message-ID: <E1H4ysJ-0007In-P8@sc8-sf-monitor2.sourceforge.net>

Patches item #630339, was opened at 2002-10-29 10:03
Message generated for change (Comment added) made by kink
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=630339&group_id=103

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: list administration
Group: Mailman 2.2 / 3.0
Status: Open
Resolution: None
Priority: 3
Private: No
Submitted By: IKEDA Soji (hatukanezumi)
Assigned to: Nobody/Anonymous (nobody)
Summary: create list with multiple owners

Initial Comment:
Create list with multiple list owners, by 'create' CGI
script and 'newlist' command line script.


----------------------------------------------------------------------

Comment By: Thijs Kinkhorst (kink)
Date: 2007-01-11 13:17

Message:
Logged In: YES 
user_id=285765
Originator: NO

I support that this patch be added. Thanks!

----------------------------------------------------------------------

Comment By: IKEDA Soji (hatukanezumi)
Date: 2005-05-10 13:30

Message:
Logged In: YES 
user_id=529503

Update for 2.1.6RC3.

----------------------------------------------------------------------

Comment By: IKEDA Soji (hatukanezumi)
Date: 2004-01-06 08:28

Message:
Logged In: YES 
user_id=529503

Update for 2.1.4.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=630339&group_id=103

From noreply at sourceforge.net  Fri Jan 12 14:33:23 2007
From: noreply at sourceforge.net (SourceForge.net)
Date: Fri, 12 Jan 2007 05:33:23 -0800
Subject: [ mailman-Bugs-1628753 ] Outbound messages have domain fubar'd
Message-ID: <E1H5MX5-0007s2-Et@sc8-sf-web5.sourceforge.net>

Bugs item #1628753, was opened at 2007-01-05 09:18
Message generated for change (Comment added) made by wshs
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1628753&group_id=103

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: mail delivery
Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Michael Reynolds (wshs)
Assigned to: Nobody/Anonymous (nobody)
Summary: Outbound messages have domain fubar'd

Initial Comment:
This is using a port install of mailman in FreeBSD, with version 2.1.9_1. When sending messages to users, either triggered by the web interface, or a message from a user to a mailman controlled email address, while using qmail with the included qmail-to-mailman script, the following errors litter my logs:

2007-01-05 07:53:25.924843500 info msg 5348160: bytes 1233 from <sirv-bounces at lists.delinked.us> qp 98922 uid 89
2007-01-05 07:53:25.961231500 starting delivery 17: msg 5348160 to remote munged at gmail.comyes

Note the 'gmail.comyes'.
A 'yes' is appended to every outbound message's target domain, thus making delivery impossible.

I spent a few days thinking it was something I messed up, so I went through my entire system setup checking everything that could influence mail. I then discovered the problem is specific to mailman. Not sure what info I can provide to help, but I'd be willing to supply upon request. I am using FreeBSD 5.5, Python 2.5.

----------------------------------------------------------------------

>Comment By: Michael Reynolds (wshs)
Date: 2007-01-12 08:33

Message:
Logged In: YES 
user_id=96949
Originator: YES

I've tracked the problem down to internal stupidity, and it is not related
at all to Mailman. However, it wasn't noticed until Mailman made me aware
of it (patch that adversely affected smtp relaying). I do apologize for
blaming mailman.

----------------------------------------------------------------------

Comment By: Mark Sapiro (msapiro)
Date: 2007-01-05 10:11

Message:
Logged In: YES 
user_id=1123998
Originator: NO

There are many people using Mailman 2.1.9 and probably several using the
FreeBSD port. This is the first report of this issue. It may have something
to do with Python 2.5 or perhaps the combination of the FreeBSD port and
Python 2.5.

The following is an interactive Python snippet (Python responses other
than prompts omitted) that sends mail in exactly the same way as Mailman
does. If you have changed the assignments of SMTPHOST and/or SMTPPORT in
mm_cfg.py, change them here too. Try this and see if the problem exists
with it. If so, the problem is with Python, not Mailman.

>>> import smtplib
>>> msg = """Subject: Test Message
... Message-Id: <some-id at nowhere.example.com>
... From: poster at example.com
... To: you
...
... The body
... """
>>> rcpts = ['user1 at example.com', 'userb at example.com']
>>> env = 'list-bounces at example.com'
>>> SMTPHOST = 'localhost'
>>> SMTPPORT = 0
>>> x = smtplib.SMTP()
>>> x.set_debuglevel(1)
>>> x.connect(SMTPHOST, SMTPPORT)
>>> x.sendmail(env, rcpts, msg)
>>> x.quit()


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1628753&group_id=103

From noreply at sourceforge.net  Fri Jan 12 16:44:16 2007
From: noreply at sourceforge.net (SourceForge.net)
Date: Fri, 12 Jan 2007 07:44:16 -0800
Subject: [ mailman-Bugs-1628753 ] Outbound messages have domain fubar'd
Message-ID: <E1H5OZk-000429-8w@sc8-sf-web11.sourceforge.net>

Bugs item #1628753, was opened at 2007-01-05 06:18
Message generated for change (Comment added) made by msapiro
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1628753&group_id=103

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: mail delivery
Group: 2.1 (stable)
>Status: Deleted
>Resolution: Invalid
Priority: 5
Private: No
Submitted By: Michael Reynolds (wshs)
Assigned to: Nobody/Anonymous (nobody)
Summary: Outbound messages have domain fubar'd

Initial Comment:
This is using a port install of mailman in FreeBSD, with version 2.1.9_1. When sending messages to users, either triggered by the web interface, or a message from a user to a mailman controlled email address, while using qmail with the included qmail-to-mailman script, the following errors litter my logs:

2007-01-05 07:53:25.924843500 info msg 5348160: bytes 1233 from <sirv-bounces at lists.delinked.us> qp 98922 uid 89
2007-01-05 07:53:25.961231500 starting delivery 17: msg 5348160 to remote munged at gmail.comyes

Note the 'gmail.comyes'.
A 'yes' is appended to every outbound message's target domain, thus making delivery impossible.

I spent a few days thinking it was something I messed up, so I went through my entire system setup checking everything that could influence mail. I then discovered the problem is specific to mailman. Not sure what info I can provide to help, but I'd be willing to supply upon request. I am using FreeBSD 5.5, Python 2.5.

----------------------------------------------------------------------

>Comment By: Mark Sapiro (msapiro)
Date: 2007-01-12 07:44

Message:
Logged In: YES 
user_id=1123998
Originator: NO

Deleted per submitter's comment.

----------------------------------------------------------------------

Comment By: Michael Reynolds (wshs)
Date: 2007-01-12 05:33

Message:
Logged In: YES 
user_id=96949
Originator: YES

I've tracked the problem down to internal stupidity, and it is not related
at all to Mailman. However, it wasn't noticed until Mailman made me aware
of it (patch that adversely affected smtp relaying). I do apologize for
blaming mailman.

----------------------------------------------------------------------

Comment By: Mark Sapiro (msapiro)
Date: 2007-01-05 07:11

Message:
Logged In: YES 
user_id=1123998
Originator: NO

There are many people using Mailman 2.1.9 and probably several using the
FreeBSD port. This is the first report of this issue. It may have something
to do with Python 2.5 or perhaps the combination of the FreeBSD port and
Python 2.5.

The following is an interactive Python snippet (Python responses other
than prompts omitted) that sends mail in exactly the same way as Mailman
does. If you have changed the assignments of SMTPHOST and/or SMTPPORT in
mm_cfg.py, change them here too. Try this and see if the problem exists
with it. If so, the problem is with Python, not Mailman.

>>> import smtplib
>>> msg = """Subject: Test Message
... Message-Id: <some-id at nowhere.example.com>
... From: poster at example.com
... To: you
...
... The body
... """
>>> rcpts = ['user1 at example.com', 'userb at example.com']
>>> env = 'list-bounces at example.com'
>>> SMTPHOST = 'localhost'
>>> SMTPPORT = 0
>>> x = smtplib.SMTP()
>>> x.set_debuglevel(1)
>>> x.connect(SMTPHOST, SMTPPORT)
>>> x.sendmail(env, rcpts, msg)
>>> x.quit()


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1628753&group_id=103

From noreply at sourceforge.net  Fri Jan 12 16:45:40 2007
From: noreply at sourceforge.net (SourceForge.net)
Date: Fri, 12 Jan 2007 07:45:40 -0800
Subject: [ mailman-Bugs-1629971 ] Repeat Emails from Mailman 2.1.9
Message-ID: <E1H5Ob6-00048r-NX@sc8-sf-web11.sourceforge.net>

Bugs item #1629971, was opened at 2007-01-07 08:45
Message generated for change (Settings changed) made by msapiro
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1629971&group_id=103

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: mail delivery
Group: None
>Status: Pending
Resolution: None
Priority: 5
Private: No
Submitted By: mfr301 (mfr301)
Assigned to: Nobody/Anonymous (nobody)
Summary: Repeat Emails from Mailman 2.1.9

Initial Comment:
Hello,

 

I currently use your software as a reseller client with ResellerZoom.com.  3 days ago my clients and myself started receiving numerous repeat emails.  The emails were being sent by the mailing list section of Mailman 2.1.9.   The problem is that every time (Since it started and has been going on for 3 straight days), I receive emails, they are the SAME emails over and over.  Their not visible on the mailing list, their not in a que, and their not in pending messages.  

 

I have a client who kept deleting mailing lists (like test at .....) and it kept re-appearing.  I have been on line with the ResellerZoom tech support CONSTANTLY from my blackberry for 3 days since the problem started and they have not been able to rectify the problem.  Is there anything you can suggest?


Mike
mfr301 at aol.com

----------------------------------------------------------------------

Comment By: Mark Sapiro (msapiro)
Date: 2007-01-07 10:21

Message:
Logged In: YES 
user_id=1123998
Originator: NO

Until you determine that there actually is a bug in Mailman, it would be
better to discuss issues like this on the mailman-users at python.org list.
See <http://mail.python.org/mailman/listinfo/mailman-users>.

You say the mails you receive were sent by Mailman, but they are 'not
visible on the mailing list'. What do you mean by 'not visible on the
mailing list' and how do you know they are sent by Mailman?

Re: deleted lists reappearing, How are the lists being deleted?

It might be more productive for ResellerZoom to contact
mailman-users at python.org directly.

Also, if the Mailman is cPanel's, see
<http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq06.011.htp>.




----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1629971&group_id=103

From noreply at sourceforge.net  Sat Jan 13 03:36:42 2007
From: noreply at sourceforge.net (SourceForge.net)
Date: Fri, 12 Jan 2007 18:36:42 -0800
Subject: [ mailman-Bugs-1634501 ] Does mailman blow away <x-flowed> 
Message-ID: <E1H5Yl8-0006rU-0x@sc8-sf-web5.sourceforge.net>

Bugs item #1634501, was opened at 2007-01-12 18:36
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1634501&group_id=103

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Dave Yost (daveyost)
Assigned to: Nobody/Anonymous (nobody)
Summary: Does mailman blow away <x-flowed> 

Initial Comment:
Somebody to a list message, with To going to a person, and Cc going to the list.  The person gets this body:

<x-flowed>

Dave Yost wrote:
> blah blah blah
</x-flowed>

Whereas the list gets this body:


Dave Yost wrote:
> blah blah blah
_______________________________________________
Foo mailing list
foo at bar.com
https://bar.com/cgi-bin/mailman/listinfo/foo


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1634501&group_id=103

From noreply at sourceforge.net  Sat Jan 13 03:38:08 2007
From: noreply at sourceforge.net (SourceForge.net)
Date: Fri, 12 Jan 2007 18:38:08 -0800
Subject: [ mailman-Bugs-1634501 ] Does mailman blow away <x-flowed> 
Message-ID: <E1H5YmW-0002cw-8q@sc8-sf-web6.sourceforge.net>

Bugs item #1634501, was opened at 2007-01-12 18:36
Message generated for change (Settings changed) made by daveyost
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1634501&group_id=103

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
>Status: Deleted
Resolution: None
Priority: 5
Private: No
Submitted By: Dave Yost (daveyost)
Assigned to: Nobody/Anonymous (nobody)
Summary: Does mailman blow away <x-flowed> 

Initial Comment:
Somebody to a list message, with To going to a person, and Cc going to the list.  The person gets this body:

<x-flowed>

Dave Yost wrote:
> blah blah blah
</x-flowed>

Whereas the list gets this body:


Dave Yost wrote:
> blah blah blah
_______________________________________________
Foo mailing list
foo at bar.com
https://bar.com/cgi-bin/mailman/listinfo/foo


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1634501&group_id=103

From noreply at sourceforge.net  Sat Jan 13 03:41:22 2007
From: noreply at sourceforge.net (SourceForge.net)
Date: Fri, 12 Jan 2007 18:41:22 -0800
Subject: [ mailman-Bugs-1634504 ] Mailman blows away <x-flowed>
Message-ID: <E1H5Ype-0006Rf-5X@sc8-sf-web2.sourceforge.net>

Bugs item #1634504, was opened at 2007-01-12 18:41
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1634504&group_id=103

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: 2.0.x
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Dave Yost (daveyost)
Assigned to: Nobody/Anonymous (nobody)
Summary: Mailman blows away <x-flowed>

Initial Comment:
Somebody replies to a list message, with To going to a me, and Cc going to the list.

The former has this body:

<x-flowed>

Dave Yost wrote:
> blah blah blah
</x-flowed>

Whereas the latter has this body:

Dave Yost wrote:
> blah blah blah
_______________________________________________
Foo mailing list
foo at bar.com
https://bar.com/cgi-bin/mailman/listinfo/foo


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1634504&group_id=103

From noreply at sourceforge.net  Sat Jan 13 04:13:51 2007
From: noreply at sourceforge.net (SourceForge.net)
Date: Fri, 12 Jan 2007 19:13:51 -0800
Subject: [ mailman-Bugs-1634504 ] Mailman blows away <x-flowed>
Message-ID: <E1H5ZL5-0007Fn-9s@sc8-sf-web11.sourceforge.net>

Bugs item #1634504, was opened at 2007-01-12 18:41
Message generated for change (Comment added) made by msapiro
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1634504&group_id=103

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: 2.0.x
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Dave Yost (daveyost)
Assigned to: Nobody/Anonymous (nobody)
Summary: Mailman blows away <x-flowed>

Initial Comment:
Somebody replies to a list message, with To going to a me, and Cc going to the list.

The former has this body:

<x-flowed>

Dave Yost wrote:
> blah blah blah
</x-flowed>

Whereas the latter has this body:

Dave Yost wrote:
> blah blah blah
_______________________________________________
Foo mailing list
foo at bar.com
https://bar.com/cgi-bin/mailman/listinfo/foo


----------------------------------------------------------------------

>Comment By: Mark Sapiro (msapiro)
Date: 2007-01-12 19:13

Message:
Logged In: YES 
user_id=1123998
Originator: NO

Mailman is not doing this unless the original message contains alternative
parts and content filtering is removing the part with <x-flowed></x-flowed>
tags.

Under some circumstances, Mailman will remove an RFC 3676 Format=Flowed
parameter from the Content-Type: header. This is bug #1495122
<https://sourceforge.net/tracker/index.php?func=detail&aid=1495122&group_id=103&atid=100103>.

If some MTA/MDA/MUA is generating the <x-flowed></x-flowed> tags from the
Format=Flowed parameter, then Mailman could be indirectly responsible.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1634504&group_id=103

From noreply at sourceforge.net  Sat Jan 13 04:58:18 2007
From: noreply at sourceforge.net (SourceForge.net)
Date: Fri, 12 Jan 2007 19:58:18 -0800
Subject: [ mailman-Bugs-1634521 ] Need admin alerts
Message-ID: <E1H5a26-0008Ez-2J@sc8-sf-web8.sourceforge.net>

Bugs item #1634521, was opened at 2007-01-12 19:58
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1634521&group_id=103

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: 2.0.x
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Dave Yost (daveyost)
Assigned to: Nobody/Anonymous (nobody)
Summary: Need admin alerts

Initial Comment:
I just noticed that for some reason none of our mailing lists have been archived for a while.  Yikes.

It would be good if mailman by default would notify admins if anything goes wrong with archiving.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1634521&group_id=103

From noreply at sourceforge.net  Sat Jan 13 05:31:08 2007
From: noreply at sourceforge.net (SourceForge.net)
Date: Fri, 12 Jan 2007 20:31:08 -0800
Subject: [ mailman-Feature Requests-1634521 ] Need admin alerts
Message-ID: <E1H5aXs-0000zt-LI@sc8-sf-web5.sourceforge.net>

Feature Requests item #1634521, was opened at 2007-01-12 19:58
Message generated for change (Comment added) made by msapiro
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1634521&group_id=103

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
>Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Dave Yost (daveyost)
Assigned to: Nobody/Anonymous (nobody)
Summary: Need admin alerts

Initial Comment:
I just noticed that for some reason none of our mailing lists have been archived for a while.  Yikes.

It would be good if mailman by default would notify admins if anything goes wrong with archiving.

----------------------------------------------------------------------

>Comment By: Mark Sapiro (msapiro)
Date: 2007-01-12 20:31

Message:
Logged In: YES 
user_id=1123998
Originator: NO

I am moving this to feature requests because that's what it is.

As far as your issue of not archiving is concerned, it seems that perhaps
ArchRunner is/was not running. If this is the case, addressing the issuue
that caused it to die and restarting it will probably archive all the
unprocessed messages in the archive/ queue.

OTOH, possible there is some issue causing the messages to be shunted. In
this case, fixing the underlying issue and running bin/unshunt should
archive the messages.

It would be very unusual if the messages were completely lost.

Regarding your feature request, look at the "Daily status report script"
(mmdsr)
<http://sourceforge.net/tracker/index.php?func=detail&aid=1123383&group_id=103&atid=300103>
and in Mailman's contrib/ directory since 2.1.7. It's not a 'default' but
it does a good job of reporting things that go wrong.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1634521&group_id=103

From noreply at sourceforge.net  Sat Jan 13 08:32:10 2007
From: noreply at sourceforge.net (SourceForge.net)
Date: Fri, 12 Jan 2007 23:32:10 -0800
Subject: [ mailman-Patches-1123383 ] Daily Status Report script...
Message-ID: <E1H5dN4-0003Ww-Jy@sc8-sf-web3.sourceforge.net>

Patches item #1123383, was opened at 2005-02-15 12:14
Message generated for change (Comment added) made by daveyost
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1123383&group_id=103

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: list administration
Group: Mailman 2.1
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Brad Knowles (shub)
Assigned to: Nobody/Anonymous (nobody)
Summary: Daily Status Report script...

Initial Comment:
Folks,

I quickly whacked together a Daily Status Report script for 
Mailman (using Bourne shell, not Python ;), and thought that other 
folks might be interested in seeing it.

The basic concept is a program that gets fired off at 23:59 every 
night, and goes through a variety of log files looking for entries 
specific to that date, and indicating problems or certain types of 
activity that might be of interest to someone trying to administer 
the server.  It also does an "ls -la" of /usr/local/mailman/qfiles/*, 
so that you can see what is in the queue at the time of the running 
of the script.

My concept was that this daily report would get e-mailed to the 
admin, or posted to a "reports" mailing list, where they could be 
archived and kept for future reference.

The script does not (yet) do any statistics calculations, although it 
should be relatively easy to hack together some basic stats using 
awk, sort, etc....

Anyway, I thought I'd share it and let folks take a look at it, and if 
anyone has any recommended improvements, we can incorporate 
those and share them back out with everyone.

The code is written under a BSD-style license, so if you don't want 
to contribute any changes back to me, that's okay.  Of course, I 
would prefer that you did, but I leave the choice up to you.

----------------------------------------------------------------------

Comment By: Dave Yost (daveyost)
Date: 2007-01-12 23:32

Message:
Logged In: YES 
user_id=330919
Originator: NO

I suggest incorporating the readme into the shell script, so there is only
the one file.

----------------------------------------------------------------------

Comment By: Brad Knowles (shub)
Date: 2006-01-25 17:55

Message:
Logged In: YES 
user_id=18417

Folks,

Okay, I just uploaded version 0.0.15, which addresses the most recent 
comments here from Mark and Tom, and makes a few additional tweaks as 
well.  See the version comments at the top of the script.

----------------------------------------------------------------------

Comment By: Mark Sapiro (msapiro)
Date: 2005-11-06 10:25

Message:
Logged In: YES 
user_id=1123998

The vette log summary lists posts held for moderation
individually under "Other Errors:". The following patch
(watch out for wrapped lines) summarizes them by list instead.

--- mmdsr	2005-09-29 21:31:33.000000000 -0700
+++ mmdsrx	2005-11-06 08:20:58.835895418 -0800
@@ -415,10 +415,15 @@
 	    echo "------------------------------" >> $TMP
 	    $GREP -i 'Posting to a moderated newsgroup' $TMPLOG |
$AWK '{ print $6 }' | $SORT | $UNIQ -c | $SORT -nr >> $TMP
 
+            echo "" >> $TMP
+            echo "Post to moderated list (by list):" >> $TMP
+            echo "------------------------------" >> $TMP
+            $GREP -i 'Post to moderated list' $TMPLOG |
$AWK '{ print $6 }' | $SORT | $UNIQ -c | $SORT -nr >> $TMP
+
 	    echo "" >> $TMP
 	    echo "Other Errors:" >> $TMP
 	    echo "------------------------------" >> $TMP
-	    $EGREP -vi '(Post by non-member|suspicious
header|message approved|Discarded posting|bulk message
discarded|junk message discarded|Message has implicit
destination|Posting to a moderated newsgroup|Message
discarded, msgid)' $TMPLOG | $SED 's/^.* ([0-9]*) //' |
$SORT | $UNIQ -c | $SORT -nr >> $TMP 
+	    $EGREP -vi '(Post by non-member|suspicious
header|message approved|Discarded posting|bulk message
discarded|junk message discarded|Message has implicit
destination|Posting to a moderated newsgroup|Post to
moderated list|Message discarded, msgid)' $TMPLOG | $SED
's/^.* ([0-9]*) //' | $SORT | $UNIQ -c | $SORT -nr >> $TMP 
 
 	else
 


----------------------------------------------------------------------

Comment By: Tom G. Christensen (tgc99)
Date: 2005-10-19 01:23

Message:
Logged In: YES 
user_id=1159458

ps output on solaris is full of whitespace but a further
echo get's rid of it.
The lines in the smtp log are sometimes broken up by a
newline (right before the msgid) which throws of the
summary. Piping it through sed first will rejoin the broken
lines.
Use $AWK instead of awk.

Patch inserted below:
--- mmdsr.orig  2005-10-19 09:42:30.000000000 +0200
+++ mmdsr       2005-10-19 09:44:23.000000000 +0200
@@ -203,7 +203,8 @@
 #      there is an easier cross-platform way to do it,
please let me know.

###############################################################################
 
-MYUID=`$PS -o user -p $$ | $TAIL -1`
+GRABUID=`$PS -o user -p $$ | $TAIL -1`
+MYUID=`echo $GRABUID`
 RUNAS="mailman"
 

###############################################################################
@@ -254,7 +255,7 @@
     $TOUCH $TMPLOG
     echo "Log file: $LOG" >> $TMP
     echo "==============================" >> $TMP
-    $GREP -si "^$DAY [0-9][0-9:]* $YEAR" $LOGDIR/$LOG >>
$TMPLOG
+    $SED -e :a -e '$!N;s/\n //;ta' -e 'P;D' $LOGDIR/$LOG |
$GREP -si "^$DAY [0-9][0-9:]* $YEAR" >> $TMPLOG
 
     if [ -f "$LOGDIR/${LOG}" ] ; then
 
@@ -264,7 +265,7 @@
            echo "Hourly Summary of Posts" >> $TMP
            echo "-----------------------" >> $TMP
 
-           $SED -e 's/^[A-Z][a-z][a-z] *[0-9]* //' -e
's/:.*$//' $TMPLOG | $UNIQ -c | $SORT -n +1 | awk '{ printf(
"%8d  %02d:00-%02d
:59\n", $1, $2, $2 ) }' >> $TMP
+           $SED -e 's/^[A-Z][a-z][a-z] *[0-9]* //' -e
's/:.*$//' $TMPLOG | $UNIQ -c | $SORT -n +1 | $AWK '{
printf( "%8d  %02d:00-%02
d:59\n", $1, $2, $2 ) }' >> $TMP
 
            echo "" >> $TMP
            echo "Post Count by List" >> $TMP
@@ -295,7 +296,7 @@
            echo "" >> $TMP
            echo "Hourly Summary of Messages Sent" >> $TMP
            echo "-------------------------------" >> $TMP
-           $SED -e 's/^[A-Z][a-z][a-z] *[0-9]* //' -e
's/:.* for / /' -e 's/ recips,.*$//' $TMPLOG | awk '{
val=int($1); sum[val]+=$2
 } END { for (i=0; i<24; i++) { printf "%8d
%02d:00-%02d:59\n", sum[i], i, i } }' >> $TMP
+           $SED -e 's/^[A-Z][a-z][a-z] *[0-9]* //' -e
's/:.* for / /' -e 's/ recips,.*$//' $TMPLOG | $AWK '{
val=int($1); sum[val]+=$
2 } END { for (i=0; i<24; i++) { printf "%8d
%02d:00-%02d:59\n", sum[i], i, i } }' >> $TMP
 
        else


----------------------------------------------------------------------

Comment By: Brad Knowles (shub)
Date: 2005-09-22 16:17

Message:
Logged In: YES 
user_id=18417

Okay, I took Mark's comments and incorporated them.  Adrian Wells also 
pointed out a log file difference between Mailman 2.1.5 and 2.1.6 that 
caused the summary of the "smtp" log to be munged.

I've now fixed these bugs, deleted the old file, and uploaded the new one

(version 0.0.12).

Thanks!

----------------------------------------------------------------------

Comment By: Mark Sapiro (msapiro)
Date: 2005-09-10 19:22

Message:
Logged In: YES 
user_id=1123998

Oooops!  I mistakenly thought I could add the mmdsr.patch as
a downloadable file, but I can't so here it is. Watch out
for wrapped lines ...

--- mmdsr.orig	2005-09-06 20:37:53.000000000 -0700
+++ mmdsr	2005-09-10 18:33:14.532393572 -0700
@@ -132,6 +132,7 @@
 
 MMDIR="/usr/local/mailman"
 TMPDIR="/tmp"
+LOGDIR="/var/log/mailman"
 

###############################################################################
 # Maximum number of subdirectory entries to display in report
@@ -234,9 +235,9 @@
     $TOUCH $TMPLOG
     echo "Log file: $LOG" >> $TMP
     echo "==============================" >> $TMP
-    $GREP -si "^$DAY [0-9][0-9:]* $YEAR" logs/$LOG >> $TMPLOG
+    $GREP -si "^$DAY [0-9][0-9:]* $YEAR" $LOGDIR/$LOG >>
$TMPLOG
 
-    if [ -f "logs/${LOG}" ] ; then
+    if [ -f "$LOGDIR/${LOG}" ] ; then
 
 	if [ "${LOG}" = "post" ] ; then
 
@@ -304,9 +305,9 @@
     $TOUCH $TMPLOG
     echo "Log file: $LOG" >> $TMP
     echo "==============================" >> $TMP
-    $GREP -si "^$DAY [0-9][0-9:]* $YEAR" logs/$LOG >> $TMPLOG
+    $GREP -si "^$DAY [0-9][0-9:]* $YEAR" $LOGDIR/$LOG >>
$TMPLOG
 
-    if [ -f "logs/${LOG}" ] ; then
+    if [ -f "$LOGDIR/${LOG}" ] ; then
 
 	if [ "${LOG}" = "error" ] ; then
 
@@ -453,4 +454,4 @@
     $CAT $TMP
 fi
 
-$RM $TMP
+$RM -f $TMP $TMPLOG


----------------------------------------------------------------------

Comment By: Mark Sapiro (msapiro)
Date: 2005-09-10 19:16

Message:
Logged In: YES 
user_id=1123998

I tried the script and other than the expected site specific
changes, I found two issues which are both addressed by the
patch in the mmdsr.patch file.

1) Mailman's log files are not necessarily in
$var_prefix/logs/ - they can be in any directory. The patch
adds a LOGDIR directory independant of MMDIR.

2) The $TMPLOG file is not removed at completion. The patch
removes it.

----------------------------------------------------------------------

Comment By: Brad Knowles (shub)
Date: 2005-09-06 07:06

Message:
Logged In: YES 
user_id=18417

Okay, I've deleted the old version of the mmdsr script that was attached,

and uploaded the latest version.  This is what we're currently using to 
monitor the lists on python.org, and we have found it very useful.

Any comments you may have will be appreciated.

----------------------------------------------------------------------

Comment By: Brad Knowles (shub)
Date: 2005-02-22 12:10

Message:
Logged In: YES 
user_id=18417

The UID variable in the current code was already replaced by MYUID, 
because I got complaints on other platforms.  But UID wasn't available to

me as a useful constant, so I had to use something else to obtain the 
value.

The recommended patch from tgc99 does work, and I will be uploading a 
new version of the code soon.

----------------------------------------------------------------------

Comment By: adrianwi (adrianwi)
Date: 2005-02-22 07:22

Message:
Logged In: YES 
user_id=1175103

Use of variable named UID does work well with OS X (version
10.2.8).  Apparently the variable UID is a constant already
in use.  When trying to the run the script without
modification, I was receiving the following error message:

UID: readonly variable

This issue was resolved by changing the name of variable,
UID, to something else, such as MMUID.  Works fine with this
change.

As an aside (& for what it is worth), the UID grab command
suggested by tgc99 on 2005-02-16 03:15 works on this system
(OS X - version 10.2.8)

----------------------------------------------------------------------

Comment By: Tom G. Christensen (tgc99)
Date: 2005-02-16 00:15

Message:
Logged In: YES 
user_id=1159458

The current UID grab command doesn't work on Solaris (2.6 &
8 tested).

I'd recommend this instead:
ps -o user -p $$|tail -1

This is tested and works on RH 6.2, RH 7.3, RHEL 2.1, RHEL3,
FC3, FreeBSD 4.9, Solaris 2.6, 8.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1123383&group_id=103

From noreply at sourceforge.net  Mon Jan 15 15:31:02 2007
From: noreply at sourceforge.net (SourceForge.net)
Date: Mon, 15 Jan 2007 06:31:02 -0800
Subject: [ mailman-Bugs-1635915 ] Variables in the template postauth.txt are
	not substituted
Message-ID: <E1H6SrW-0005hT-Ch@sc8-sf-web2.sourceforge.net>

Bugs item #1635915, was opened at 2007-01-15 16:31
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1635915&group_id=103

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Jussi Hirvi (jhirvi)
Assigned to: Nobody/Anonymous (nobody)
Summary: Variables in the template postauth.txt are not substituted

Initial Comment:
The template file postauth.txt contains: 

> As list administrator, your authorization is requested for thefollowing 
> mailing list posting:
> List:    %(listname)s@%(hostname)s    From:    %(sender)s    Subject: 
> %(subject)s    Reason:  %(reason)s
> 
> At your convenience, visit:
> %(admindb_url)s
> to approve or deny the request.

When an email is sent to the administrator, the variables are of course supposed to be substituted with their respective values. THis didn't happen, however. I cannot think of another explanation than a bug. My Mailman version is 2.1.8. In this case, I'm using Finnish versions of the templates (modified by me), but that shouldn't affect this, I think. 


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1635915&group_id=103

From noreply at sourceforge.net  Mon Jan 15 17:57:56 2007
From: noreply at sourceforge.net (SourceForge.net)
Date: Mon, 15 Jan 2007 08:57:56 -0800
Subject: [ mailman-Bugs-1635915 ] Variables in the template postauth.txt are
	not substituted
Message-ID: <E1H6V9g-0002gZ-NP@sc8-sf-web4.sourceforge.net>

Bugs item #1635915, was opened at 2007-01-15 06:31
Message generated for change (Comment added) made by msapiro
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1635915&group_id=103

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: 2.1 (stable)
>Status: Pending
Resolution: None
Priority: 5
Private: No
Submitted By: Jussi Hirvi (jhirvi)
Assigned to: Nobody/Anonymous (nobody)
Summary: Variables in the template postauth.txt are not substituted

Initial Comment:
The template file postauth.txt contains: 

> As list administrator, your authorization is requested for thefollowing 
> mailing list posting:
> List:    %(listname)s@%(hostname)s    From:    %(sender)s    Subject: 
> %(subject)s    Reason:  %(reason)s
> 
> At your convenience, visit:
> %(admindb_url)s
> to approve or deny the request.

When an email is sent to the administrator, the variables are of course supposed to be substituted with their respective values. THis didn't happen, however. I cannot think of another explanation than a bug. My Mailman version is 2.1.8. In this case, I'm using Finnish versions of the templates (modified by me), but that shouldn't affect this, I think. 


----------------------------------------------------------------------

>Comment By: Mark Sapiro (msapiro)
Date: 2007-01-15 08:57

Message:
Logged In: YES 
user_id=1123998
Originator: NO

Perhaps the 'bug' is in your modified template. It seems to me that your
modification of the template is the most likely cause of this.

Have you changed the substitution strings %(listname)s, %(hostname)s, etc.
in any way? If you change anything in these strings, they will cease to
work.

Please check for

lists/<listname>/fi/postauth.txt
templates/<list.host_name>/fi/postauth.txt
templates/site/fi/postauth.txt
templates/fi/postauth.txt

The first of these that exists is the Finnish template that will be used.
Review that template, and if you can't find a problem there, I don't know
where it can be unless somehow the call to
 Utils.maketext('postauth.txt', d, raw=1, mlist=mlist),
in Mailman/Handlers/Hold.py has been changed.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1635915&group_id=103

From noreply at sourceforge.net  Tue Jan 16 08:36:09 2007
From: noreply at sourceforge.net (SourceForge.net)
Date: Mon, 15 Jan 2007 23:36:09 -0800
Subject: [ mailman-Feature Requests-1636541 ] non-interactive use of newlist
Message-ID: <E1H6irZ-0005o2-Eg@sc8-sf-web4.sourceforge.net>

Feature Requests item #1636541, was opened at 2007-01-16 08:36
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1636541&group_id=103

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Schoinobates Volans (schoinobates)
Assigned to: Nobody/Anonymous (nobody)
Summary: non-interactive use of newlist

Initial Comment:
(This is Debian bug #36063)

The comment at the top of /usr/sbin/newlist says:

 Create a new, unpopulated mailing list.

   newlist <list-name> <list-admin's-address> <admin-password> <immediate>

 You can specify as many of the arguments as you want on the command line. The optional <immediate> argument, if present, means to send out the notice immediately.  Otherwise, the script hangs pending input, to give time for the person creating the list to customize it before sending the admin an email notice about the existence of the new list.

It is useful that there is a way to use this noninteractively. Unfortunately this is made more difficult because the password has to be passed in as a command line argument where `ps' can see it.

Furthermore, since the script (correctly) uses a real
password-gathering function when a password isn't supplied, it is not easy to have a script feed it a password on stdin (the script will require a tty, etc.)

It would be good if there were a way to pass the password in via stdin or some such, eg by passing a special option, or a special format of `password', or an environment variable giving the fd to use.

Perhaps this should be in the python module getpass, or perhaps it should be in mailman.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1636541&group_id=103

From noreply at sourceforge.net  Tue Jan 16 09:57:21 2007
From: noreply at sourceforge.net (SourceForge.net)
Date: Tue, 16 Jan 2007 00:57:21 -0800
Subject: [ mailman-Bugs-1635915 ] Variables in the template postauth.txt are
	not substituted
Message-ID: <E1H6k89-00054C-2o@sc8-sf-monitor2.sourceforge.net>

Bugs item #1635915, was opened at 2007-01-15 16:31
Message generated for change (Comment added) made by jhirvi
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1635915&group_id=103

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: 2.1 (stable)
>Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Jussi Hirvi (jhirvi)
Assigned to: Nobody/Anonymous (nobody)
Summary: Variables in the template postauth.txt are not substituted

Initial Comment:
The template file postauth.txt contains: 

> As list administrator, your authorization is requested for thefollowing 
> mailing list posting:
> List:    %(listname)s@%(hostname)s    From:    %(sender)s    Subject: 
> %(subject)s    Reason:  %(reason)s
> 
> At your convenience, visit:
> %(admindb_url)s
> to approve or deny the request.

When an email is sent to the administrator, the variables are of course supposed to be substituted with their respective values. THis didn't happen, however. I cannot think of another explanation than a bug. My Mailman version is 2.1.8. In this case, I'm using Finnish versions of the templates (modified by me), but that shouldn't affect this, I think. 


----------------------------------------------------------------------

>Comment By: Jussi Hirvi (jhirvi)
Date: 2007-01-16 10:57

Message:
Logged In: YES 
user_id=1692540
Originator: YES

I think I found the error in my /templates/fi/postauth.txt, just as you
suspected! One s (for string, I guess) was missing.   I have not tested,
but I'm reasonably sure this was what caused the error. 

I feel kind of stupid... but I'm glad this was solved! 

----------------------------------------------------------------------

Comment By: Mark Sapiro (msapiro)
Date: 2007-01-15 18:57

Message:
Logged In: YES 
user_id=1123998
Originator: NO

Perhaps the 'bug' is in your modified template. It seems to me that your
modification of the template is the most likely cause of this.

Have you changed the substitution strings %(listname)s, %(hostname)s, etc.
in any way? If you change anything in these strings, they will cease to
work.

Please check for

lists/<listname>/fi/postauth.txt
templates/<list.host_name>/fi/postauth.txt
templates/site/fi/postauth.txt
templates/fi/postauth.txt

The first of these that exists is the Finnish template that will be used.
Review that template, and if you can't find a problem there, I don't know
where it can be unless somehow the call to
 Utils.maketext('postauth.txt', d, raw=1, mlist=mlist),
in Mailman/Handlers/Hold.py has been changed.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1635915&group_id=103

From noreply at sourceforge.net  Tue Jan 16 18:18:56 2007
From: noreply at sourceforge.net (SourceForge.net)
Date: Tue, 16 Jan 2007 09:18:56 -0800
Subject: [ mailman-Bugs-1635915 ] Variables in the template postauth.txt are
	not substituted
Message-ID: <E1H6rxY-0004Yi-E6@sc8-sf-web2.sourceforge.net>

Bugs item #1635915, was opened at 2007-01-15 06:31
Message generated for change (Comment added) made by msapiro
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1635915&group_id=103

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: 2.1 (stable)
>Status: Closed
>Resolution: Invalid
Priority: 5
Private: No
Submitted By: Jussi Hirvi (jhirvi)
Assigned to: Nobody/Anonymous (nobody)
Summary: Variables in the template postauth.txt are not substituted

Initial Comment:
The template file postauth.txt contains: 

> As list administrator, your authorization is requested for thefollowing 
> mailing list posting:
> List:    %(listname)s@%(hostname)s    From:    %(sender)s    Subject: 
> %(subject)s    Reason:  %(reason)s
> 
> At your convenience, visit:
> %(admindb_url)s
> to approve or deny the request.

When an email is sent to the administrator, the variables are of course supposed to be substituted with their respective values. THis didn't happen, however. I cannot think of another explanation than a bug. My Mailman version is 2.1.8. In this case, I'm using Finnish versions of the templates (modified by me), but that shouldn't affect this, I think. 


----------------------------------------------------------------------

>Comment By: Mark Sapiro (msapiro)
Date: 2007-01-16 09:18

Message:
Logged In: YES 
user_id=1123998
Originator: NO

I am closing this per the submitter's comment.

Note that you should not edit /templates/fi/postauth.txt as your changes
will be lost in an upgrade. If you want a modified version of this template
to apply sitewide, it should be put in templates/site/fi/postauth.txt. See
<http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq04.048.htp> for
more information.

----------------------------------------------------------------------

Comment By: Jussi Hirvi (jhirvi)
Date: 2007-01-16 00:57

Message:
Logged In: YES 
user_id=1692540
Originator: YES

I think I found the error in my /templates/fi/postauth.txt, just as you
suspected! One s (for string, I guess) was missing.   I have not tested,
but I'm reasonably sure this was what caused the error. 

I feel kind of stupid... but I'm glad this was solved! 

----------------------------------------------------------------------

Comment By: Mark Sapiro (msapiro)
Date: 2007-01-15 08:57

Message:
Logged In: YES 
user_id=1123998
Originator: NO

Perhaps the 'bug' is in your modified template. It seems to me that your
modification of the template is the most likely cause of this.

Have you changed the substitution strings %(listname)s, %(hostname)s, etc.
in any way? If you change anything in these strings, they will cease to
work.

Please check for

lists/<listname>/fi/postauth.txt
templates/<list.host_name>/fi/postauth.txt
templates/site/fi/postauth.txt
templates/fi/postauth.txt

The first of these that exists is the Finnish template that will be used.
Review that template, and if you can't find a problem there, I don't know
where it can be unless somehow the call to
 Utils.maketext('postauth.txt', d, raw=1, mlist=mlist),
in Mailman/Handlers/Hold.py has been changed.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1635915&group_id=103

From noreply at sourceforge.net  Sat Jan 20 20:40:30 2007
From: noreply at sourceforge.net (SourceForge.net)
Date: Sat, 20 Jan 2007 11:40:30 -0800
Subject: [ mailman-Patches-1587651 ] Roster should list private members to
	admins
Message-ID: <E1H8M4k-0007FK-1t@sc8-sf-web7.sourceforge.net>

Patches item #1587651, was opened at 2006-10-30 18:59
Message generated for change (Settings changed) made by msapiro
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1587651&group_id=103

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Web UI
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Eric Price (eprice)
>Assigned to: Mark Sapiro (msapiro)
Summary: Roster should list private members to admins

Initial Comment:
The roster page omits members of a list who choose to
remain concealed, even when the viewer has admin
authorization.  This means admins cannot get a single
list of all list members from the web interface.

The roster should instead list hidden members to people
who logged in with the admin password.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1587651&group_id=103

From noreply at sourceforge.net  Tue Jan 23 12:04:33 2007
From: noreply at sourceforge.net (SourceForge.net)
Date: Tue, 23 Jan 2007 03:04:33 -0800
Subject: [ mailman-Bugs-1642388 ] Mailman re-enables delivery when your
	address changes.
Message-ID: <E1H9JS5-00048A-GQ@sc8-sf-web3.sourceforge.net>

Bugs item #1642388, was opened at 2007-01-23 12:04
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1642388&group_id=103

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: configuring/installing
Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Laura Creighton (lcreighton)
Assigned to: Nobody/Anonymous (nobody)
Summary: Mailman re-enables delivery when your  address changes.

Initial Comment:
My email address changed.  I went to a list on python.org
(edu-sig) where I am subscribed, and changed my address
to reflect the new address.  I then clicked the box to
change this globally.  I immediately started receiving
mail messages from the high-volume list, python-list
which is also on python.org even though I have disabled
the delivery there.  I had to disable this by hand.

I'm running a stable 2.1 but I suspect this will be
a bug everywhere.

Laura Creighton
now lac at openend.se
(who doesn't want tracker confirmations)

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1642388&group_id=103

From noreply at sourceforge.net  Tue Jan 23 12:09:19 2007
From: noreply at sourceforge.net (SourceForge.net)
Date: Tue, 23 Jan 2007 03:09:19 -0800
Subject: [ mailman-Bugs-1642388 ] Mailman re-enables delivery when your
	address changes.
Message-ID: <E1H9JWh-00052F-Mr@sc8-sf-web11.sourceforge.net>

Bugs item #1642388, was opened at 2007-01-23 12:04
Message generated for change (Comment added) made by lcreighton
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1642388&group_id=103

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: configuring/installing
Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Laura Creighton (lcreighton)
Assigned to: Nobody/Anonymous (nobody)
Summary: Mailman re-enables delivery when your  address changes.

Initial Comment:
My email address changed.  I went to a list on python.org
(edu-sig) where I am subscribed, and changed my address
to reflect the new address.  I then clicked the box to
change this globally.  I immediately started receiving
mail messages from the high-volume list, python-list
which is also on python.org even though I have disabled
the delivery there.  I had to disable this by hand.

I'm running a stable 2.1 but I suspect this will be
a bug everywhere.

Laura Creighton
now lac at openend.se
(who doesn't want tracker confirmations)

----------------------------------------------------------------------

>Comment By: Laura Creighton (lcreighton)
Date: 2007-01-23 12:09

Message:
Logged In: YES 
user_id=376262
Originator: YES


Hmmm, edu-sig is 2.1.9  Maybe that is not the stable version? I forget
which is which.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1642388&group_id=103

From noreply at sourceforge.net  Wed Jan 24 07:34:30 2007
From: noreply at sourceforge.net (SourceForge.net)
Date: Tue, 23 Jan 2007 22:34:30 -0800
Subject: [ mailman-Feature Requests-1643206 ] Automatically adding recipients
	to accept_these_nonmembers.
Message-ID: <E1H9biI-0005za-GM@sc8-sf-web11.sourceforge.net>

Feature Requests item #1643206, was opened at 2007-01-24 17:34
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1643206&group_id=103

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Mark Ennis (mennis309)
Assigned to: Nobody/Anonymous (nobody)
Summary: Automatically adding recipients to accept_these_nonmembers.

Initial Comment:
We have a situation where we have a support mailing list to which our customers email their support issues. It is receiving a ridiculous amount of spam and we are going to change it over to a members-only list with a web submission form for our customers. It struck me that it would be very useful if the mailing list could automatically add non-member recipients of mailing list messages to the accept_these_nonmembers list so that we could continue using normal email for discussing support issues with customers after an initial contact is made through the web submission form. We would normally reply to the customer and CC the mailing list. Is there any way to do this in mailman or could this be a useful feature that might be added in the future? We are currently using mailman 2.1.6 on Linux.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=1643206&group_id=103

From noreply at sourceforge.net  Sat Jan 27 04:20:04 2007
From: noreply at sourceforge.net (SourceForge.net)
Date: Fri, 26 Jan 2007 19:20:04 -0800
Subject: [ mailman-Bugs-1629971 ] Repeat Emails from Mailman 2.1.9
Message-ID: <200701270320.l0R3K4PA019974@sc8-sf-db2-new-b.sourceforge.net>

Bugs item #1629971, was opened at 2007-01-07 08:45
Message generated for change (Comment added) made by sf-robot
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1629971&group_id=103

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: mail delivery
Group: None
>Status: Closed
Resolution: None
Priority: 5
Private: No
Submitted By: mfr301 (mfr301)
Assigned to: Nobody/Anonymous (nobody)
Summary: Repeat Emails from Mailman 2.1.9

Initial Comment:
Hello,

 

I currently use your software as a reseller client with ResellerZoom.com.  3 days ago my clients and myself started receiving numerous repeat emails.  The emails were being sent by the mailing list section of Mailman 2.1.9.   The problem is that every time (Since it started and has been going on for 3 straight days), I receive emails, they are the SAME emails over and over.  Their not visible on the mailing list, their not in a que, and their not in pending messages.  

 

I have a client who kept deleting mailing lists (like test at .....) and it kept re-appearing.  I have been on line with the ResellerZoom tech support CONSTANTLY from my blackberry for 3 days since the problem started and they have not been able to rectify the problem.  Is there anything you can suggest?


Mike
mfr301 at aol.com

----------------------------------------------------------------------

>Comment By: SourceForge Robot (sf-robot)
Date: 2007-01-26 19:20

Message:
Logged In: YES 
user_id=1312539
Originator: NO

This Tracker item was closed automatically by the system. It was
previously set to a Pending status, and the original submitter
did not respond within 14 days (the time period specified by
the administrator of this Tracker).

----------------------------------------------------------------------

Comment By: Mark Sapiro (msapiro)
Date: 2007-01-07 10:21

Message:
Logged In: YES 
user_id=1123998
Originator: NO

Until you determine that there actually is a bug in Mailman, it would be
better to discuss issues like this on the mailman-users at python.org list.
See <http://mail.python.org/mailman/listinfo/mailman-users>.

You say the mails you receive were sent by Mailman, but they are 'not
visible on the mailing list'. What do you mean by 'not visible on the
mailing list' and how do you know they are sent by Mailman?

Re: deleted lists reappearing, How are the lists being deleted?

It might be more productive for ResellerZoom to contact
mailman-users at python.org directly.

Also, if the Mailman is cPanel's, see
<http://www.python.org/cgi-bin/faqw-mm.py?req=show&file=faq06.011.htp>.




----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1629971&group_id=103