Re: [Mailman-Users] duplicate messages from shunt queue
On Mon, 31 Jul 2006, Mark Sapiro wrote: There are several possibilities here. 3) if a message is shunted because SMTPDirect.py can't write the 'post' log, it has already been sent, but OutgoingRunner.py doesn't know this when it catches the exception and shunts the message. So those messages which were shunted because of ownership/permission issues on the 'post' log probably were duplicated when you ran unshunt I think that solves the mystery then. What am I missing here? From what I've been able to dig up on the list archives the qfiles/shunt directory should only contain messages that never made it out to any lists due to some error in config, perms or some bug in mailman itself. This is not always true, as in case 3) above. Thus, you have to use judgement in unshunting. Will do. Also set up an snmp monitoring process to watch the shunt queue and let me know when things are piling up so I can investigate. In the case where the error occurs in delivery under OutgoingRunner, the message will have been archived, and when unshunted will be processed only by OutgoingRunner and not by ArchRunner, so no duplicate archive entry results. But, in this case, it is possible that some or all receipients received the original delivery and will receive duplicates when the message is unshunted. Excellent info. I put a question regarding this in the FAQ, so now I'll answer it. Thanks for the insight Mark, very much appreciated. Charles -- Mark Sapiro [EMAIL PROTECTED] The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] duplicate messages from shunt queue
Hi all, Recently I found a fairly huge amount of files in the shunt queue (around 1500). All I could gather from the error log is that most of them were from an old bug in parsing weird charsets and the later ones were due to the post and smtp-failur logfiles being owned by root. So I fixed the perms (had already upgraded to 2.1.8 a month or so ago) and all was well. Then I ran bin/unshunt. Then people started complaining that they were getting a few hundred old messages. :) What am I missing here? From what I've been able to dig up on the list archives the qfiles/shunt directory should only contain messages that never made it out to any lists due to some error in config, perms or some bug in mailman itself. But it's looking like these all did somehow make it through mailman previously and were sent a second time. A few other tidbits: -looking at some samples, msgids are the same, so it wasn't a user getting a rejection and then posting again -the dupes DO NOT show up in the web archive Any other info I can supply here? Mailman 2.1.8, ruby 1.8.2, FreeBSD 4.7. Thanks, Charles ___ Charles Sprickman NetEng/SysAdmin Bway.net - New York's Best Internet - www.bway.net [EMAIL PROTECTED] - 212.655.9344 -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Red Hat FHS packaging
On Wed, 15 Jun 2005, Steve Burling wrote: --On June 15, 2005 6:20:00 PM +0100 Andy Heath [EMAIL PROTECTED] wrote: I differ from your view. I think you've made your position clear. John's made his position clear. How about if the two of you take the rest of this discussion offline? Best idea yet. This is a Linux/RedHat issue of little interest to those not running RedHat. C -- Steve Burlingmailto:[EMAIL PROTECTED] University of Michigan, ICPSRVoice: +1 734 615.3779 330 Packard Street FAX: +1 734 647.8700 Ann Arbor, MI 48104-2910 -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/spork%40bway.net Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Setting sitewide defaults that can't be changed?
On Thu, 19 May 2005, Matthew Newton wrote: You could also use my patch (number 1164457 on sf.net): http://sourceforge.net/tracker/index.php?func=detailaid=1164457group_id=103atid=300103 This lets you write something like: SITE_HIDE_LIST_OPTIONS = ['owner'] in mm_cfg.py, and will then completely remove the owner option from the config pages. This is a list, so you can remove as many options as you like. Thanks for that patch! I was just about to ask for something like that. Between your patch and the ADMIN_CATEGORIES array, I've trimmed out the stuff that most of our users (announce-only for the most part) don't need. That leads to the next question... Where are the defaults initially set from? A few of the things I've hid are things I'd still like to flip a value on. I know I could do this with config_list, but I'm wondering if there is somewhere to twiddle the initial defaults. Thanks, Charles Matthew -- Matthew Newton [EMAIL PROTECTED] UNIX and e-mail Systems Administrator, Network Support Section, Computer Centre, University of Leicester, Leicester LE1 7RH, United Kingdom -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/spork%40bway.net Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Setting sitewide defaults that can't be changed?
On Sat, 21 May 2005, Brad Knowles wrote: At 8:59 PM -0400 2005-05-20, Charles Sprickman wrote: That leads to the next question... Where are the defaults initially set from? A few of the things I've hid are things I'd still like to flip a value on. I know I could do this with config_list, but I'm wondering if there is somewhere to twiddle the initial defaults. The defaults are set from Defaults.py. If you want to change them, you over-ride them in mm_cfg.py, otherwise you will lose your changes with the next upgrade. Doh! I guess I should have looked there. Sorry about that. This past week has been a bit Mailman-heavy with me chasing 5 or 6 different things at once, including moving to Postfix (which was so easy it was scary) and getting virus/spam scanning going, documenting things as I go in our internal Wiki, teaching sales people how to configure one-way lists... Thanks, Charles -- Brad Knowles, [EMAIL PROTECTED] Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. -- Benjamin Franklin (1706-1790), reply of the Pennsylvania Assembly to the Governor, November 11, 1755 SAGE member since 1995. See http://www.sage.org/ for more info. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Setting sitewide defaults that can't be changed?
On Wed, 18 May 2005, Brad Knowles wrote:
At 2:09 PM -0700 2005-05-18, Mark Sapiro wrote:
ADMIN_CATEGORIES.remove('archive')
Why not instead have the following in mm_cfg.py:
ADMIN_CATEGORIES = [
# First column
'general', 'passwords', 'language', 'members', 'nondigest', 'digest',
# Second column
# Old version commented out, and archive removed
# 'privacy', 'bounce', 'archive', 'gateway', 'autoreply',
'privacy', 'bounce', 'gateway', 'autoreply',
'contentfilter', 'topics',
]
This is getting interesting... I'm looking to hack up the admin interface
to lock in some defaults and also to remove some of the options that tend
to confuse simple announce list users.
I'm handy with PHP and perl, but I've never dug into Python at all. What
can you folks recommend as far as a crash-course in Python?
Thanks,
Charles
--
Brad Knowles, [EMAIL PROTECTED]
Those who would give up essential Liberty, to purchase a little
temporary Safety, deserve neither Liberty nor Safety.
-- Benjamin Franklin (1706-1790), reply of the Pennsylvania
Assembly to the Governor, November 11, 1755
SAGE member since 1995. See http://www.sage.org/ for more info.
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/spork%40bway.net
Security Policy:
http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Security Policy:
http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] bounce processing on seldom-used list
On Thu, 12 May 2005, Heather Madrone wrote: Any suggestions on how to hack in even some basic here's a list of people that bounced on this mailing for this list functionality? Even something outside of mailman itself? If you set the bounce threshold to 0.9, then members who have one hard bounce will be immediately disabled. If you set all the bounce notify options to Yes, then the list-owner will be notified about all bouncers. Thank you Heather, that works perfectly! Charles -- Heather Madrone [EMAIL PROTECTED] The Home-Ed List: http://www.madrone.com/Home-ed/helist.html You can lead a child to learning, but you can't make her think. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] shunt dir and Uncaught runner exception
On Fri, 13 May 2005, Charles Sprickman wrote:
Hello,
While exploring the qfiles directories, I found that shunt had about
47MB of .pck files in it. The FAQ entry I found recommended running
unshunt, so I did. Not a good idea, I found. Apparently this requeued
some very old messages, leading to a number of complaints from
long-unsubscribed list members.
Digging around the mail archives today I noticed some similar problems
related to Uncaught runner exception errors. Those posts seemed to
point to problems with oddly-formatted messages. My tracebacks in the
error log look a bit different. See [1] and [2] that represent quite a
jump in time.
First of all, thanks for the answers regarding 2.1.6, looks like that's
going final soon anyhow, so I'll stick to what I have for now. And I'm
seriously considering Postfix to replace Sendmail...
Now, does anyone have any clue what the error messages below mean?
Judging by the number of shunted messages, this happens fairly often. The
I/O error leads me towards permsissions, but on what?
Lastly, what are .pck files? How can I examine these as they show up?
Thanks,
Charles
References:
[1]
May 12 01:01:22 2005 (76306) SHUNTING:
1115874080.77584+b3ededd1f304c19064c28c92b0372d3cefb98c5d
May 12 01:20:52 2005 (76306) Uncaught runner exception: [Errno 5]
Input/output error
May 12 01:20:52 2005 (76306) Traceback (most recent call last):
File /usr/local/mailman/Mailman/Queue/Runner.py, line 111, in _oneloop
self._onefile(msg, msgdata)
File /usr/local/mailman/Mailman/Queue/Runner.py, line 167, in _onefile
keepqueued = self._dispose(mlist, msg, msgdata)
File /usr/local/mailman/Mailman/Queue/OutgoingRunner.py, line 73, in
_dispose
self._func(mlist, msg, msgdata)
File /usr/local/mailman/Mailman/Handlers/SMTPDirect.py, line 180, in
processmm_cfg.SMTP_LOG_EVERY_MESSAGE[1], kws=d)
File /usr/local/mailman/Mailman/Logging/Syslog.py, line 49, in
write_ex
logf = self._logfiles[kind] = StampedLogger(kind)
File /usr/local/mailman/Mailman/Logging/StampedLogger.py, line 52, in
__init__
Logger.__init__(self, category, nofail, immediate)
File /usr/local/mailman/Mailman/Logging/Logger.py, line 49, in
__init__
self.__get_f()
File /usr/local/mailman/Mailman/Logging/Logger.py, line 75, in __get_f
_logexc(self, e)
File /usr/local/mailman/Mailman/Logging/Utils.py, line 22, in _logexc
sys.__stderr__.write('Logging error: %s\n' % logger)
IOError: [Errno 5] Input/output error
[2]
Aug 13 16:00:29 2004 (336) SHUNTING:
1092240005.3389361+2b0889d711824ccdc73d79ecb14b0073db8831b2
Aug 13 16:00:29 2004 (336) Uncaught runner exception: [Errno 5]
Input/output error
Aug 13 16:00:29 2004 (336) Traceback (most recent call last):
File /usr/local/mailman/Mailman/Queue/Runner.py, line 111, in _oneloop
self._onefile(msg, msgdata)
File /usr/local/mailman/Mailman/Queue/Runner.py, line 167, in _onefile
keepqueued = self._dispose(mlist, msg, msgdata)
File /usr/local/mailman/Mailman/Queue/OutgoingRunner.py, line 73, in
_dispose
self._func(mlist, msg, msgdata)
File /usr/local/mailman/Mailman/Handlers/SMTPDirect.py, line 152, in
processdeliveryfunc(mlist, msg, msgdata, envsender, refused, conn)
File /usr/local/mailman/Mailman/Handlers/SMTPDirect.py, line 384, in
bulkdeliver
syslog('smtp-failure', 'Low level smtp error: %s, msgid: %s', e,
msgid)
File /usr/local/mailman/Mailman/Logging/Syslog.py, line 40, in write
self.write_ex(kind, msg, args, kws)
File /usr/local/mailman/Mailman/Logging/Syslog.py, line 49, in
write_ex
logf = self._logfiles[kind] = StampedLogger(kind)
File /usr/local/mailman/Mailman/Logging/StampedLogger.py, line 52, in
__init__
Logger.__init__(self, category, nofail, immediate)
File /usr/local/mailman/Mailman/Logging/Logger.py, line 49, in
__init__
self.__get_f()
File /usr/local/mailman/Mailman/Logging/Logger.py, line 75, in __get_f
_logexc(self, e)
File /usr/local/mailman/Mailman/Logging/Utils.py, line 22, in _logexc
sys.__stderr__.write('Logging error: %s\n' % logger)
IOError: [Errno 5] Input/output error
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/spork%40bway.net
Security Policy:
http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http
Re: [Mailman-Users] shunt dir and Uncaught runner exception
On Sat, 14 May 2005, Brad Knowles wrote: At 5:14 PM -0400 2005-05-14, Charles Sprickman wrote: Now, does anyone have any clue what the error messages below mean? Judging by the number of shunted messages, this happens fairly often. The I/O error leads me towards permsissions, but on what? I'd have to check the code, but from reading the traceback it seems to me like there was some sort of error writing to the log files. What is the ownership and permissions for the Mailman logs directory, all the log files within that directory, etc...? How full is that filesystem? How large are those log files? The perms look OK, but I do remember many months ago that the smtp logfile would sometimes revert to being owned by root rather than mailman. Very odd. If it is a permissions problem on a log, should that actually cause the message to get shunted? If that is what's happening, perhaps I should put that in the SF bug tracker... Lastly, what are .pck files? How can I examine these as they show up? Those are the Python pickle files which contain binary data regarding the message. Use the show_qfiles program in /usr/local/mailman/bin. For example, from the /usr/local/mailman directory, do the following: % bin/show_qfiles qfiles/shunt/*.pck However, if the pickle file is causing errors of this sort, then show_qfiles may come back with errors as well -- you'll just have to give it a try. Excellent! Thanks for that info, I appreciate it. Charles -- Brad Knowles, [EMAIL PROTECTED] Those who would give up essential Liberty, to purchase a little temporary Safety, deserve neither Liberty nor Safety. -- Benjamin Franklin (1706-1790), reply of the Pennsylvania Assembly to the Governor, November 11, 1755 SAGE member since 1995. See http://www.sage.org/ for more info. -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] shunt dir and Uncaught runner exception
Hello,
Please bear with me as I try and get my Mailman skills in order,
previously I was just babysitting this thing, but now I'm trying to dig in
and make sure everything is actually working as it should be.
While exploring the qfiles directories, I found that shunt had about
47MB of .pck files in it. The FAQ entry I found recommended running
unshunt, so I did. Not a good idea, I found. Apparently this requeued
some very old messages, leading to a number of complaints from
long-unsubscribed list members.
Digging around the mail archives today I noticed some similar problems
related to Uncaught runner exception errors. Those posts seemed to
point to problems with oddly-formatted messages. My tracebacks in the
error log look a bit different. See [1] and [2] that represent quite a
jump in time.
I'm also a bit lost at this point as to what the recommended production
release is. The website points to 2.1.5 as stable, but it seems like
most folks posting here are using a 2.1.6 snapshot. Which is preferred
for production use?
I'm also running sendmail basically by default. I'm not fond of sendmail.
Since I'm free to change, what is the recommended MTA for an older,
sluggish box?
Thanks,
Charles
References:
[1]
May 12 01:01:22 2005 (76306) SHUNTING:
1115874080.77584+b3ededd1f304c19064c28c92b0372d3cefb98c5d
May 12 01:20:52 2005 (76306) Uncaught runner exception: [Errno 5]
Input/output error
May 12 01:20:52 2005 (76306) Traceback (most recent call last):
File /usr/local/mailman/Mailman/Queue/Runner.py, line 111, in _oneloop
self._onefile(msg, msgdata)
File /usr/local/mailman/Mailman/Queue/Runner.py, line 167, in _onefile
keepqueued = self._dispose(mlist, msg, msgdata)
File /usr/local/mailman/Mailman/Queue/OutgoingRunner.py, line 73, in
_dispose
self._func(mlist, msg, msgdata)
File /usr/local/mailman/Mailman/Handlers/SMTPDirect.py, line 180, in
processmm_cfg.SMTP_LOG_EVERY_MESSAGE[1], kws=d)
File /usr/local/mailman/Mailman/Logging/Syslog.py, line 49, in
write_ex
logf = self._logfiles[kind] = StampedLogger(kind)
File /usr/local/mailman/Mailman/Logging/StampedLogger.py, line 52, in
__init__
Logger.__init__(self, category, nofail, immediate)
File /usr/local/mailman/Mailman/Logging/Logger.py, line 49, in
__init__
self.__get_f()
File /usr/local/mailman/Mailman/Logging/Logger.py, line 75, in __get_f
_logexc(self, e)
File /usr/local/mailman/Mailman/Logging/Utils.py, line 22, in _logexc
sys.__stderr__.write('Logging error: %s\n' % logger)
IOError: [Errno 5] Input/output error
[2]
Aug 13 16:00:29 2004 (336) SHUNTING:
1092240005.3389361+2b0889d711824ccdc73d79ecb14b0073db8831b2
Aug 13 16:00:29 2004 (336) Uncaught runner exception: [Errno 5]
Input/output error
Aug 13 16:00:29 2004 (336) Traceback (most recent call last):
File /usr/local/mailman/Mailman/Queue/Runner.py, line 111, in _oneloop
self._onefile(msg, msgdata)
File /usr/local/mailman/Mailman/Queue/Runner.py, line 167, in _onefile
keepqueued = self._dispose(mlist, msg, msgdata)
File /usr/local/mailman/Mailman/Queue/OutgoingRunner.py, line 73, in
_dispose
self._func(mlist, msg, msgdata)
File /usr/local/mailman/Mailman/Handlers/SMTPDirect.py, line 152, in
processdeliveryfunc(mlist, msg, msgdata, envsender, refused, conn)
File /usr/local/mailman/Mailman/Handlers/SMTPDirect.py, line 384, in
bulkdeliver
syslog('smtp-failure', 'Low level smtp error: %s, msgid: %s', e,
msgid)
File /usr/local/mailman/Mailman/Logging/Syslog.py, line 40, in write
self.write_ex(kind, msg, args, kws)
File /usr/local/mailman/Mailman/Logging/Syslog.py, line 49, in
write_ex
logf = self._logfiles[kind] = StampedLogger(kind)
File /usr/local/mailman/Mailman/Logging/StampedLogger.py, line 52, in
__init__
Logger.__init__(self, category, nofail, immediate)
File /usr/local/mailman/Mailman/Logging/Logger.py, line 49, in
__init__
self.__get_f()
File /usr/local/mailman/Mailman/Logging/Logger.py, line 75, in __get_f
_logexc(self, e)
File /usr/local/mailman/Mailman/Logging/Utils.py, line 22, in _logexc
sys.__stderr__.write('Logging error: %s\n' % logger)
IOError: [Errno 5] Input/output error
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Security Policy:
http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
[Mailman-Users] bounce processing on seldom-used list
Hello, We've just started digging into mailman a bit more here. Very happy with it so far... A list owner brought up a good question today. I was telling him how this is better than a long bcc: list in Outlook and one thing that I like about any modern mailing list software is that it handles bounces for you. But this situation was kind of unique... It's a large list, but it does not get used more than 5 or 6 times a year. The list owner would like to know when someone is bouncing, but right after the first bounce. Is there any way to do that? I didn't see too much about bounce processing in the FAQ, but it seems like it's built around lists that see traffic more often than a few times a year... Any suggestions on how to hack in even some basic here's a list of people that bounced on this mailing for this list functionality? Even something outside of mailman itself? Thanks, Charles -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://www.python.org/cgi-bin/faqw-mm.py?req=showamp;file=faq01.027.htp
Re: [Mailman-Users] Extract list of lists with population?
Here's some really ugly perl that I slapped together last night. I think
it does what the OP wanted. It sends mail and writes a log.
Thanks,
Charles
___
Charles Sprickman
NetEng/SysAdmin
Bway.net - New York's Best Internet - www.bway.net
[EMAIL PROTECTED] - 212.655.9344
On Thu, 1 Jul 2004, Mark J. Bradakis wrote:
Depending on your shell, something like
foreach l ( `/your/path/to/mailman/bin/list_lists -b `)
echo -n $l
/your/path/to/mailman/bin/list_members | wc -l
end
might do the trick.
mjb.
Unthinking respect for authority is the greatest enemy of truth.
-Albert Einstein.
--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
#!/usr/bin/perl
# $Id: list-lists.pl,v 1.4 2004/07/01 19:12:55 spork Exp $
# quick script to list all mailman lists and give a
# subscriber count for each
$mailman_bin = /usr/local/mailman/bin;
$lists_prog = $mailman_bin/list_lists;
$members_prog = $mailman_bin/list_members;
$owners_prog = $mailman_bin/list_owners;
$mail_recip = [EMAIL PROTECTED];
$mail_from = [EMAIL PROTECTED];
$logfile = /usr/local/adm/data/mailman-report.log;
$now = localtime;
open(LISTS, $lists_prog -b |);
while (LISTS) {
chomp;
push(@lists,$_);
}
close LISTS;
format MAIL_TOP =
This monthly report shows how many subscribers each hosted list
is using, who owns the list, and the list name.
Subscribers List Owner List Name
--- -- -
.
format LOG_TOP =
Subscribers List Owner List Name
--- -- -
.
format MAIL =
@ @ @
$member_count, $owner, $list
.
format LOG =
@ @ @
$member_count, $owner, $list
.
open(LOG, $logfile) || die Can't open log for writing\n;
print LOG report for $now\n\n;
open(MAIL, | /usr/sbin/sendmail -f $mail_from $mail_recip);
print MAIL To: $mail_recip\nSubject: Monthly Mailing List Report\n;
while (@lists) {
$list = $_;
$member_count = 0;
open(OWNERS, $owners_prog $list |);
$owner = OWNERS;
chomp($owner);
close OWNERS;
open(MEMBERS, $members_prog $list |);
while (MEMBERS) {
$member_count++;
}
close MEMBERS;
write MAIL;
write LOG;
#print $member_count\t\t$owner\t\t$list\n;
}
print LOG \nEND\n\n;
close MAIL;
close LOG;
--
Mailman-Users mailing list
[EMAIL PROTECTED]
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Re: [Mailman-Users] htdig and paths
On Wed, 30 Jun 2004, Richard Barrett wrote: This is explained in the INSTALL.htdig-mm file (or its HTML version) added to the $build directory by the patch: I can't tell you how many times I read that page. Lots of info in one page... :) Anyhow, today I went and double-checked my ScriptAlias lines, removed an Alias that referenced /htdig/, and it's working again... I'm not sure how I fixed it, as at some point yesterday I did not have the Alias line in there. Testing both private and public lists shows that it works as expected now (including trying to reach a private URL without logging in; I get a proper email/pass prompt). Anyhow, thanks for pointing out that htdig is indeed a cgi in the mailman cgi-bin, that fact slipped my mind yesterday. Is there any chance this set of patches will ever make it into Mailman? List archives without an integrated search (especially private lists) are an absolute necessity; no one wants to page through years of posts to find what they're looking for... Thanks for the help and for the excellent patch! Charles -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
[Mailman-Users] mass subscription options
Hello, I'm really happy with Mailman; I recently upgraded an install that was at least a year or two old, so I basically took ownership of the project. Nice stuff, especially with the htdig patches. I have one more little question. I don't want to let people do mass subscriptions via the web interface without an invite. Basically I figure if someone is going to go that route, I'd like to have the opportunity to catch any spammy activity, and I'd rather have the invite trigger that than the first message. Is there any way to disable the Subscribe option so that it HAS to be an invite? Thanks, Charles ___ Charles Sprickman NetEng/SysAdmin Bway.net - New York's Best Internet - www.bway.net [EMAIL PROTECTED] - 212.655.9344 -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
[Mailman-Users] htdig and paths
Hi, I'm at my wit's end here... I've got MM 2.1.5 w/htdig patches (via FreeBSD port), and while it seems very close to working, it's not quite right, or perhaps in my reading of the patch install/config guide I just missed something. Everything seems to be happening correctly; a new post to a list gets the htdig directory added. If I manually run the nightly script (as mailman), that works without error. I get the search box, and I get search results. However, the links to each message look like this: http://myhost.com/htdig/listname/2004-June/08.html Which of course isn't a valid URL; all the archives look either like this: http://myhost.com/pipermail/2004-June/08.html or http://myhost.com/private/2004-June/08.html Even if I go into the archive/private/htdig/listname.conf file and alter the URL (url_part_aliases) and run the nightly script I still get the bogus URL. What am I missing here? Was there some Alias I was supposed to add to my apache config? What else can I tell you about the config? Thanks, Charles ___ Charles Sprickman NetEng/SysAdmin Bway.net - New York's Best Internet - www.bway.net [EMAIL PROTECTED] - 212.655.9344 -- Mailman-Users mailing list [EMAIL PROTECTED] http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://www.python.org/cgi-bin/faqw-mm.py Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
