Patches item #1783633, was opened at 2007-08-28 20:55
Message generated for change (Settings changed) made by novalis_dt
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1783633&group_…
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: command line scripts
Group: Mailman 2.1
>Status: Closed
Resolution: Duplicate
Priority: 5
Private: No
Submitted By: David Turner (novalis_dt)
Assigned to: Nobody/Anonymous (nobody)
Summary: allow add_member to offer confirmation
Initial Comment:
Adds a -c option to add_member to allow it to be used to subscribe members with confirmation.
----------------------------------------------------------------------
Comment By: David Turner (novalis_dt)
Date: 2007-08-28 20:56
Message:
Logged In: YES
user_id=83137
Originator: YES
Oops. This duplicates #1765041
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1783633&group_…
Patches item #1783633, was opened at 2007-08-28 20:55
Message generated for change (Comment added) made by novalis_dt
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1783633&group_…
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: command line scripts
Group: Mailman 2.1
Status: Open
>Resolution: Duplicate
Priority: 5
Private: No
Submitted By: David Turner (novalis_dt)
Assigned to: Nobody/Anonymous (nobody)
Summary: allow add_member to offer confirmation
Initial Comment:
Adds a -c option to add_member to allow it to be used to subscribe members with confirmation.
----------------------------------------------------------------------
>Comment By: David Turner (novalis_dt)
Date: 2007-08-28 20:56
Message:
Logged In: YES
user_id=83137
Originator: YES
Oops. This duplicates #1765041
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1783633&group_…
Patches item #1783633, was opened at 2007-08-28 20:55
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1783633&group_…
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: command line scripts
Group: Mailman 2.1
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: David Turner (novalis_dt)
Assigned to: Nobody/Anonymous (nobody)
Summary: allow add_member to offer confirmation
Initial Comment:
Adds a -c option to add_member to allow it to be used to subscribe members with confirmation.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1783633&group_…
Patches item #1776178, was opened at 2007-08-17 13:53
Message generated for change (Comment added) made by tsmetana
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1776178&group_…
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: Mailman 2.2 / 3.0
>Status: Closed
>Resolution: Invalid
Priority: 5
Private: No
Submitted By: Tomas Smetana (tsmetana)
Assigned to: Nobody/Anonymous (nobody)
Summary: Use inotify instead of polling in Runner.py
Initial Comment:
Hi,
the Mailman wakes up 7 times per second which is somehow resource unfriendly. This is caused by qrunners that poll for new files in queue directory. The proposed patch replaces polling in Runner.py with inotify which enables CPU to idle when possible.
The patch requires python-inotify (http://pyinotify.sourceforge.net) to be installed.
--ts
----------------------------------------------------------------------
>Comment By: Tomas Smetana (tsmetana)
Date: 2007-08-24 10:07
Message:
Logged In: YES
user_id=1869522
Originator: YES
The patches will make Mailman working but unstoppable. It looks to be a
python's problem with handling signals in threads. I'm closing this ticket
until the issues got solved.
----------------------------------------------------------------------
Comment By: Tomas Smetana (tsmetana)
Date: 2007-08-21 10:04
Message:
Logged In: YES
user_id=1869522
Originator: YES
I'm adding updated patch for Mailman 2.2 and a new patch for Mailman 3.
I've moved the python-inotify parts in conditionals, so if inotify is not
present in the system, everything should work as in the unpatched version.
File Added: mailman3-inotify.patch
----------------------------------------------------------------------
Comment By: Tomas Smetana (tsmetana)
Date: 2007-08-21 10:00
Message:
Logged In: YES
user_id=1869522
Originator: YES
File Added: mailman-inotify.patch
----------------------------------------------------------------------
Comment By: Tomas Smetana (tsmetana)
Date: 2007-08-17 14:36
Message:
Logged In: YES
user_id=1869522
Originator: YES
Yes, you're right... I didn't realize that inotify is Linux specific. I
will add a configure script option -- this should solve the Linux-only
problem and make the python-inotify dependency optional. Also I will take
a look at Mailman 3 and try to create a patch for it as well.
----------------------------------------------------------------------
Comment By: Barry A. Warsaw (bwarsaw)
Date: 2007-08-17 14:16
Message:
Logged In: YES
user_id=12800
Originator: NO
IIUC, inotify is a Linux-only thing so this would have to be optional. I
haven't looked at the patch, but I would target this for Mailman 3 instead
of 2.2.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1776178&group_…
Bugs item #1778960, was opened at 2007-08-21 19:54
Message generated for change (Comment added) made by ninja_k
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1778960&group_…
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: bounce detection
Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Nick Lange (ninja_k)
Assigned to: Nobody/Anonymous (nobody)
Summary: Empty Bounces
Initial Comment:
I have a mailing list, X managed by Mailman 2.1.9 on FreeBSD 5.3 with Courier as our MTA.
All the member addresses of X are valid. The owner address is also valid. We allow non-member postings as well.
Every time we send an e-mail to the list, we get an e-mail with no subject, and no body from mailman-bounces. If I turn on Uncaught bounce notification, the message that is forwarded has no contents.
The logs show:
Aug 21 11:01:12 2007 (1493) bounce message w/no discernable addresses: None
Aug 21 11:01:12 2007 (1493) forwarding unrecognized, message-id: n/a
Aug 21 11:01:12 2007 (1493) bounce message w/no discernable addresses: None
Aug 21 11:01:12 2007 (1493) forwarding unrecognized, message-id: n/a
... I'm not quite sure what is going on, but I am fairly certain that this is a bug.
----------------------------------------------------------------------
>Comment By: Nick Lange (ninja_k)
Date: 2007-08-22 05:23
Message:
Logged In: YES
user_id=411568
Originator: YES
To answer your questions (apparently I can't quote your message, my
apologies)
1. No auto responders are in use. I will attempt to sanitize and post up
some courier logs for you tomorrow.
2. While I haven't gone as far as to capture individual messages in
transit, the attached "messages" are completely empty, yes.
With consideration to one, I'll try to enable some kind of tracing on the
programs as they are executed when I get into work...
----------------------------------------------------------------------
Comment By: Mark Sapiro (msapiro)
Date: 2007-08-21 23:46
Message:
Logged In: YES
user_id=1123998
Originator: NO
> ... I'm not quite sure what is going on, but I am fairly certain that
this
> is a bug.
Maybe, but not necessarily.
What do your Courier logs show?
It is even possible that one of your list members has a misconfigured
autoresponder of some kind.
In any case, Mailman is receiving this empty bounce message, and something
(presumably outside Mailman) is sending it.
> If I turn on Uncaught bounce
> notification, the message that is forwarded has no contents.
What are the headers of this message, or are there no headers either?
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1778960&group_…
Bugs item #1778960, was opened at 2007-08-21 12:54
Message generated for change (Comment added) made by msapiro
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1778960&group_…
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: bounce detection
Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Nick Lange (ninja_k)
Assigned to: Nobody/Anonymous (nobody)
Summary: Empty Bounces
Initial Comment:
I have a mailing list, X managed by Mailman 2.1.9 on FreeBSD 5.3 with Courier as our MTA.
All the member addresses of X are valid. The owner address is also valid. We allow non-member postings as well.
Every time we send an e-mail to the list, we get an e-mail with no subject, and no body from mailman-bounces. If I turn on Uncaught bounce notification, the message that is forwarded has no contents.
The logs show:
Aug 21 11:01:12 2007 (1493) bounce message w/no discernable addresses: None
Aug 21 11:01:12 2007 (1493) forwarding unrecognized, message-id: n/a
Aug 21 11:01:12 2007 (1493) bounce message w/no discernable addresses: None
Aug 21 11:01:12 2007 (1493) forwarding unrecognized, message-id: n/a
... I'm not quite sure what is going on, but I am fairly certain that this is a bug.
----------------------------------------------------------------------
>Comment By: Mark Sapiro (msapiro)
Date: 2007-08-21 16:46
Message:
Logged In: YES
user_id=1123998
Originator: NO
> ... I'm not quite sure what is going on, but I am fairly certain that
this
> is a bug.
Maybe, but not necessarily.
What do your Courier logs show?
It is even possible that one of your list members has a misconfigured
autoresponder of some kind.
In any case, Mailman is receiving this empty bounce message, and something
(presumably outside Mailman) is sending it.
> If I turn on Uncaught bounce
> notification, the message that is forwarded has no contents.
What are the headers of this message, or are there no headers either?
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1778960&group_…
Bugs item #1778960, was opened at 2007-08-21 19:54
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=1778960&group_…
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: bounce detection
Group: 2.1 (stable)
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Nick Lange (ninja_k)
Assigned to: Nobody/Anonymous (nobody)
Summary: Empty Bounces
Initial Comment:
I have a mailing list, X managed by Mailman 2.1.9 on FreeBSD 5.3 with Courier as our MTA.
All the member addresses of X are valid. The owner address is also valid. We allow non-member postings as well.
Every time we send an e-mail to the list, we get an e-mail with no subject, and no body from mailman-bounces. If I turn on Uncaught bounce notification, the message that is forwarded has no contents.
The logs show:
Aug 21 11:01:12 2007 (1493) bounce message w/no discernable addresses: None
Aug 21 11:01:12 2007 (1493) forwarding unrecognized, message-id: n/a
Aug 21 11:01:12 2007 (1493) bounce message w/no discernable addresses: None
Aug 21 11:01:12 2007 (1493) forwarding unrecognized, message-id: n/a
... I'm not quite sure what is going on, but I am fairly certain that this is a bug.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100103&aid=1778960&group_…
Patches item #1776178, was opened at 2007-08-17 13:53
Message generated for change (Comment added) made by tsmetana
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1776178&group_…
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: Mailman 2.2 / 3.0
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Tomas Smetana (tsmetana)
Assigned to: Nobody/Anonymous (nobody)
Summary: Use inotify instead of polling in Runner.py
Initial Comment:
Hi,
the Mailman wakes up 7 times per second which is somehow resource unfriendly. This is caused by qrunners that poll for new files in queue directory. The proposed patch replaces polling in Runner.py with inotify which enables CPU to idle when possible.
The patch requires python-inotify (http://pyinotify.sourceforge.net) to be installed.
--ts
----------------------------------------------------------------------
>Comment By: Tomas Smetana (tsmetana)
Date: 2007-08-21 10:04
Message:
Logged In: YES
user_id=1869522
Originator: YES
I'm adding updated patch for Mailman 2.2 and a new patch for Mailman 3.
I've moved the python-inotify parts in conditionals, so if inotify is not
present in the system, everything should work as in the unpatched version.
File Added: mailman3-inotify.patch
----------------------------------------------------------------------
Comment By: Tomas Smetana (tsmetana)
Date: 2007-08-21 10:00
Message:
Logged In: YES
user_id=1869522
Originator: YES
File Added: mailman-inotify.patch
----------------------------------------------------------------------
Comment By: Tomas Smetana (tsmetana)
Date: 2007-08-17 14:36
Message:
Logged In: YES
user_id=1869522
Originator: YES
Yes, you're right... I didn't realize that inotify is Linux specific. I
will add a configure script option -- this should solve the Linux-only
problem and make the python-inotify dependency optional. Also I will take
a look at Mailman 3 and try to create a patch for it as well.
----------------------------------------------------------------------
Comment By: Barry A. Warsaw (bwarsaw)
Date: 2007-08-17 14:16
Message:
Logged In: YES
user_id=12800
Originator: NO
IIUC, inotify is a Linux-only thing so this would have to be optional. I
haven't looked at the patch, but I would target this for Mailman 3 instead
of 2.2.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1776178&group_…
Patches item #1776178, was opened at 2007-08-17 13:53
Message generated for change (Comment added) made by tsmetana
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1776178&group_…
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: Mailman 2.2 / 3.0
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Tomas Smetana (tsmetana)
Assigned to: Nobody/Anonymous (nobody)
Summary: Use inotify instead of polling in Runner.py
Initial Comment:
Hi,
the Mailman wakes up 7 times per second which is somehow resource unfriendly. This is caused by qrunners that poll for new files in queue directory. The proposed patch replaces polling in Runner.py with inotify which enables CPU to idle when possible.
The patch requires python-inotify (http://pyinotify.sourceforge.net) to be installed.
--ts
----------------------------------------------------------------------
>Comment By: Tomas Smetana (tsmetana)
Date: 2007-08-21 10:00
Message:
Logged In: YES
user_id=1869522
Originator: YES
File Added: mailman-inotify.patch
----------------------------------------------------------------------
Comment By: Tomas Smetana (tsmetana)
Date: 2007-08-17 14:36
Message:
Logged In: YES
user_id=1869522
Originator: YES
Yes, you're right... I didn't realize that inotify is Linux specific. I
will add a configure script option -- this should solve the Linux-only
problem and make the python-inotify dependency optional. Also I will take
a look at Mailman 3 and try to create a patch for it as well.
----------------------------------------------------------------------
Comment By: Barry A. Warsaw (bwarsaw)
Date: 2007-08-17 14:16
Message:
Logged In: YES
user_id=12800
Originator: NO
IIUC, inotify is a Linux-only thing so this would have to be optional. I
haven't looked at the patch, but I would target this for Mailman 3 instead
of 2.2.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=300103&aid=1776178&group_…
Feature Requests item #403066, was opened at 2001-01-01 06:27
Message generated for change (Comment added) made by msapiro
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=403066&group_i…
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: Accepted
Priority: 3
Private: No
Submitted By: Mark Tearle (mtearle)
Assigned to: Mark Sapiro (msapiro)
Summary: Auto Approval of subscriptions for certain domains
Initial Comment:
A patch to enable automatic approval for certain domains, eg people
in the example.com are automatically approved all others have to wait for the moderator
----------------------------------------------------------------------
>Comment By: Mark Sapiro (msapiro)
Date: 2007-08-18 21:00
Message:
Logged In: YES
user_id=1123998
Originator: NO
Reopened. Pending/closed was a mistake.
----------------------------------------------------------------------
Comment By: Jim Popovitch (jimpop)
Date: 2006-07-31 15:13
Message:
Logged In: YES
user_id=3142
New feature request for this patch, seeking feedback.
Most of my lists automatically moderate new subscribers, in
addition some require admin approval for subsciption, except
for domains listed in subscribe_auto_approval. A nice
addition to this patch would be to not moderate subscribers
whose domains are listed in subscribe_auto_approval.
----------------------------------------------------------------------
Comment By: SourceForge Robot (sf-robot)
Date: 2006-03-25 19:21
Message:
Logged In: YES
user_id=1312539
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: Jim Popovitch (jimpop)
Date: 2006-03-12 19:12
Message:
Logged In: YES
user_id=3142
I've successfully applied this against a v2.1.8 system and
it works well. Thanks!!
----------------------------------------------------------------------
Comment By: Mark Sapiro (msapiro)
Date: 2006-03-11 10:36
Message:
Logged In: YES
user_id=1123998
The attached patch is against a 2.1.8a1 installed base
(installed because it patches Defaults.py and not
Defaults.py.in). It is a modification and extension of the
original patch. It implements a new list attribute
'subscribe_auto_approval' which is a list of email addresses
and regular expressions matching email addresses whose
subscriptions are exempt from admin approval. It implements
the original intent if one just uses regexps that match domains.
This will go in Mailman 2.2, but it would be nice to get
some feedback from people who are interested in this feature
and are willing to try the patch.
----------------------------------------------------------------------
Comment By: Thomas Wouters (twouters)
Date: 2003-03-11 05:31
Message:
Logged In: YES
user_id=34209
Is this still necessary with Mailman 2.1, which has more
'automatic' options (as well as 'memberadaptors') ? In any
case, the patch is likely heavily out of date by now, I'm
moving this to Feature Requests for now. Feel free to
respond if you (still) have a need.
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=350103&aid=403066&group_i…