[Mailman-Users] Soft bounces....
Hallo! Running into a small bit of frustration. Yahoo expects me to respond promptly to 5xx bounces, disabling any subscriptions, otherwise it starts generating 'greylist' 4xx bounces for my mail. Unfortunately, if I try to lower the bounce threshold, the now-daily occurence of 4xx bounces guarantees that all yahoo addresses will end up disabled. Is there any way, short of fiddling with and recompiling from source, to separate 'hard' bounce handling from 'soft' bounce handling, or to change the 'scores' that each accumulates? Or any other trick to handle bounces properly when yahoo is tossing out greylist deferrals. At this point is just amounts to a nuisance with delayed deliveries for a lot of list mail. But it would be better to have our mailman properly disable when 5xx errors occur - Charles, HWCN -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
[Mailman-Users] Can't change host name preference
Hello, I am trying to set up Mailman on a new domain. I have done it in the past without issue, but now I have a really bizzare problem. When I go to the MYLIST mailing list administration General Options Section page, I notice the following entry preloaded in the Host name this list prefers for email field... syd.xobas.net I have NO IDEA where this is coming from. It is not my domain, so I replace it with my own. However, when I click the Submit your changes button, it goes to an invalid page. When I try again, I notice that when I hover over the button, the URL that it translates to incorporates that syd.xobas.net domain into the URL. I looked all over my server (a vps running CentOS 5) for where that entry might be coming from. I did find an occurance of it in /var/lib/mailman/archives/private/MYLIST/index.html and /var/lib/mailman/archives/private/mailman/index.html But I don't know how it got there. Where is the proper place to replace that domain with my own? Thanks Much, Mike -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
[Mailman-Users] Problems in Mailman
Hi list, I'm having some problems with a Mailman. When I accept an email that was received in a list, I get this in the error log: Apr 01 14:57:01 2009 (2315) SHUNTING: 1238608621.3245921+6e71fad398d2eba77746fc941cf6b1123ed7ecd3 Apr 01 14:57:01 2009 (2315) Uncaught runner exception: invalid load key, '7'. Apr 01 14:57:01 2009 (2315) Traceback (most recent call last): File /usr/lib/mailman/Mailman/Queue/Runner.py, line 112, in _oneloop self._onefile(msg, msgdata) File /usr/lib/mailman/Mailman/Queue/Runner.py, line 170, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File /usr/lib/mailman/Mailman/Queue/IncomingRunner.py, line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File /usr/lib/mailman/Mailman/Queue/IncomingRunner.py, line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File /usr/lib/mailman/Mailman/Handlers/Moderate.py, line 109, in process Hold.hold_for_approval(mlist, msg, msgdata, Hold.NonMemberPost) File /usr/lib/mailman/Mailman/Handlers/Hold.py, line 243, in hold_for_approval cookie = mlist.pend_new(Pending.HELD_MESSAGE, id) File /usr/lib/mailman/Mailman/Pending.py, line 65, in pend_new db = self.__load() File /usr/lib/mailman/Mailman/Pending.py, line 95, in __load return cPickle.load(fp) UnpicklingError: invalid load key, '7'. And this: Apr 01 15:09:57 2009 (2312) SHUNTING: 1238609343.8684261+bff1c62c38a18427c91c1a4bb7ca5f7dfe15a267 Apr 01 15:11:01 2009 (2312) Uncaught runner exception: bad marshal data Apr 01 15:11:01 2009 (2312) Traceback (most recent call last): File /usr/lib/mailman/Mailman/Queue/Runner.py, line 112, in _oneloop self._onefile(msg, msgdata) File /usr/lib/mailman/Mailman/Queue/Runner.py, line 170, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File /usr/lib/mailman/Mailman/Queue/ArchRunner.py, line 73, in _dispose mlist.ArchiveMail(msg) File /usr/lib/mailman/Mailman/Archiver/Archiver.py, line 216, in ArchiveMail h.processUnixMailbox(f) File /usr/lib/mailman/Mailman/Archiver/pipermail.py, line 583, in processUnixMailbox self.add_article(a) File /usr/lib/mailman/Mailman/Archiver/pipermail.py, line 635, in add_article article.parentID = parentID = self.get_parent_info(arch, article) File /usr/lib/mailman/Mailman/Archiver/pipermail.py, line 667, in get_parent_info article.subject) File /usr/lib/mailman/Mailman/Archiver/HyperDatabase.py, line 311, in getOldestArticle self.__openIndices(archive) File /usr/lib/mailman/Mailman/Archiver/HyperDatabase.py, line 251, in __openIndices t = DumbBTree(os.path.join(arcdir, archive + '-' + i)) File /usr/lib/mailman/Mailman/Archiver/HyperDatabase.py, line 65, in __init__ self.load() File /usr/lib/mailman/Mailman/Archiver/HyperDatabase.py, line 170, in load self.dict = marshal.load(fp) ValueError: bad marshal data The qfiles/shunt directory is empty: [r...@andromeda01 mailman]# ls -la qfiles/shunt/ total 8 drwxrwsr-x 2 mailman mailman 4096 Mar 25 10:36 . drwxrwsr-x 11 rootmailman 4096 Mar 25 10:36 .. In the data directory I have some files .pck, like this: [r...@andromeda01 mailman]# ls -la data/ total 69048 drwsrwsr-x 2 rootmailman 20480 Abr 1 15:46 . drwxrwsr-x 9 rootmailman4096 Abr 1 14:37 .. -rw-rw-r-- 1 mailman mailman 2295278 Abr 1 15:46 heldmsg-cobranca-23.pck -rw-rw-r-- 1 mailman mailman 489013 Abr 1 15:46 heldmsg-cobranca-24.pck -rw-rw-r-- 1 mailman mailman1463 Abr 1 15:46 heldmsg-cobranca-35.pck -rw-rw-r-- 1 mailman mailman4431 Abr 1 15:45 heldmsg-informatica-10.pck -rw-rw-r-- 1 mailman mailman5026 Abr 1 15:45 heldmsg-informatica-11.pck -rw-rw-r-- 1 mailman mailman 98672 Abr 1 15:45 heldmsg-informatica-12.pck -rw-rw-r-- 1 mailman mailman4431 Abr 1 15:45 heldmsg-informatica-13.pck [snip] I run the check_db command, and it's report this: [r...@andromeda01 mailman]# check_db --all --verbose Lista: direta /var/lib/mailman/lists/direta/config.pck: Ok /var/lib/mailman/lists/direta/config.pck.last: Ok [Errno 2] No such file or directory: '/var/lib/mailman/lists/direta/config.db' [Errno 2] No such file or directory: '/var/lib/mailman/lists/direta/config.db.last' Lista: vendasf /var/lib/mailman/lists/vendasf/config.pck: Ok /var/lib/mailman/lists/vendasf/config.pck.last: Ok [Errno 2] No such file or directory: '/var/lib/mailman/lists/vendasf/config.db' [Errno 2] No such file or directory: '/var/lib/mailman/lists/vendasf/config.db.last' Lista: marketing /var/lib/mailman/lists/marketing/config.pck: Ok /var/lib/mailman/lists/marketing/config.pck.last: Ok [Errno 2] No such file or directory: '/var/lib/mailman/lists/marketing/config.db' [Errno 2] No such file or directory: '/var/lib/mailman/lists/marketing/config.db.last' Lista: juridico
Re: [Mailman-Users] Bounce updating
Hi all, I have a question about the mailman bounce procedure. Is it possible to obtain a list of bounces that were removed from the list due to a high score? Essentially what I want to do is create a list of members that were removed from the list due to bounces and present that list to the list owner. Is there a built in function that can do it, or is there a way I can do it manually? If this question has already been addressed in the FAQ, I apologize, I might have missed it (there were a lot of topics). If you can just point me in the right direction in that case, I would be very grateful. Cheers, Sam Hello Sam (and others), I had a similar-ish scenario a few weeks back. Quick story: the Mailman setup here had a short spate of auto-unsubscribing people from various lists at 9am every day for about four days. One of the lists had about 100 people removed in one morning and the list owner queried whether I could supply them with a list of those who were unsubscribed . The easy solution I found was to grep the 'subscribe' logfile for the listname and the phrase 'auto-unsubscribe' which returns lines like: Mar 11 09:00:02 2009 (1577) somelist: ...@***.***.net auto-unsubscribed [reason: BYBOUNCE] Looking into it a bit further I found that the 'bounce' logfile records some (minorly) useful info about what it is doing. Doing a grep on the term 'disabled' returns lines such as: Mar 10 09:00:02 2009 (3577) Notifying disabled member *...@***.org for list: somelist What may be of most use to you however is to modify this grep to match the phrase deleted after exhausting notices which I believe is the error line given when an email address goes over its bounce score. This returns lines such as: Mar 12 09:00:02 2009 (3388) somelist: ***...@.com deleted after exhausting notices From there it is a short hop to having a script running under cron that'll grep through the bounce logfile, matching lines containing deleted after exhausting notices within the cronjob cycle period which would dump the output to stdio and so by default email back to you. Regards, Steff Watkins === -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
[Mailman-Users] Moderator and Admin emails not being sent...
I've been debugging this for some time now, multiple google searches, etc... all to no avail. I have a mailman list setup and working fine, with the exception of moderator and admin emails not being sent (at least not received). I've narrowed down to one fairly simple test case, that is to leave an unmoderated email in the list, and then to run the following command on my server: % /usr/local/bin/python -S checkdbs After running this command, my expectation is to get an email sent out notifying me of the unmoderated email in the list. I never get this email, but I do get the following entries in various logs directly after running that above command: /var/log/maillog: Apr 2 18:22:02 gileszone.com sendmail[12438]: n330M2rP012438: from=sandia-bounces+sandia-owner=gileszone@gileszone.com, size=990, class=-60, nrcpts=1, msgid=mailman.0.1238718120.12361.san...@gileszone.com, proto=ESMTP, relay=gileszone.com [69.36.169.41] Apr 2 18:22:02 gileszone.com sendmail[12438]: n330M2rP012438: to=|/home/gileszone/mailman/mail/mailman post sandia, ctladdr= sandia-ow...@gileszone.com (2058/0), delay=00:00:00, xdelay=00:00:00, mailer=prog, pri=139180, dsn=2.0.0, stat=Sent mailman/logs/smtp: Apr 02 18:22:02 2009 (9073) mailman.0.1238718120.12361.san...@gileszone.com smtp to sandia for 1 recips, completed in 0.104 second mailman/logs/vette: Apr 02 18:22:03 2009 (9071) Message discarded, msgid: mailman.0.1238718120.12361.san...@gileszone.com All other mailman logs have no new entries. I've verified many times that the list owner email address is setup properly (which it is - with a single entry of this email address). I'm currently at a loss as to why I'm unable to get admin and moderator emails sent out to me --- any help would be greatly appreciated! Thanks, -Todd -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Debugging question
On Wed, Apr 01, 2009 at 07:54:33AM -0700, Mark Sapiro wrote: See http://wiki.list.org/x/A4E9. Thanks Mark. I hadn't found that page. That was plenty to fix it. I'd looked at the wiki without finding that. Maybe it's because the Site Administrator Tasks page it's linked from is an unordered hodge-podge. Maybe I didn't find it because debugging an install seemed like something that would be included in Downloading and Installing, or Integration Issues. Since Downloading and Installing and Integration Issues are also tasks for the site administrator, would it make better sense to also break out sections on Debugging, Site Upgrades, and perhaps Mods? Or maybe to fold thse all under Site Administrator Tasks but have that all subsectioned logically, rather than a mostly-random list? I know - it's a wiki and presumably I could jump in and rearrange stuff. I'd do that, if there's a sense that it's appropriate and no one with real expertise on Mailman wants to take it on. Best, Whit -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Debugging question
on 4/2/09 9:11 AM, Whit Blauvelt said: Since Downloading and Installing and Integration Issues are also tasks for the site administrator, would it make better sense to also break out sections on Debugging, Site Upgrades, and perhaps Mods? Or maybe to fold thse all under Site Administrator Tasks but have that all subsectioned logically, rather than a mostly-random list? Problem is, what makes sense for one person doesn't necessarily make sense for someone else. What's there is not as well organized as it could be, but from my perspective it's not so horribly bad. That said, perhaps there is some middle ground that might be more useful than what we have now, and would make sense to a broader group of people. IMO, what would be really useful would be a tagging-based system, so that a single entry could show up in multiple sections. But I think that would mean either a complete re-write of the wiki code itself, or at least a substantial change to the way we use the wiki. I'm not sure that either of those are feasible in the short term. I know - it's a wiki and presumably I could jump in and rearrange stuff. I'd do that, if there's a sense that it's appropriate and no one with real expertise on Mailman wants to take it on. I'd say that you have the power to make whatever changes you think should be made, and if we don't like them then we can revert to earlier versions. So, feel free to hack away! -- Brad Knowles b...@shub-internet.orgIf you like Jazz/RB guitar, check out LinkedIn Profile: my friend bigsbytracks on YouTube at http://tinyurl.com/y8kpxuhttp://preview.tinyurl.com/bigsbytracks -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Soft bounces....
On Thu, 2 Apr 2009, Charles Gregory wrote: Yahoo expects me to respond promptly to 5xx bounces, disabling any subscriptions, otherwise it starts generating 'greylist' 4xx bounces for my mail. Unfortunately, if I try to lower the bounce threshold, the now-daily occurence of 4xx bounces guarantees that all yahoo addresses will end up This doesn't quite make sense, because 4xx isn't a bounce. It's a delay code to your mail server to try again later. sendmail, by default, generates a warning back to the sender if it hasn't been able to deliver it for 4 hours, and that notice MIGHT be interpreted as a bounce, but that's the only thing I could think of. == Chris Candreva -- ch...@westnet.com -- (914) 948-3162 WestNet Internet Services of Westchester http://www.westnet.com/ -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Triggering password reminders from the Web UI?
Beau James wrote: MailMan 2.1.11, on a shared-hosting ISP ... Is there any way from the Web UI for the list administrator to trigger mailman to send the password reminder to all list members? (The administrator can trigger it to a specific member.) No. Is there any way to find out via the Web UI, the schedule on which password reminders will be sent to the entire list when send monthly password reminders is selected on the general list properties? No. The reminders are sent by Mailman's cron/mailpasswds. The default schedule is 5:00 A.M. server local time on the first of the month, but the ISP could change this or not run the job at all. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Soft bounces....
Charles Gregory wrote: Yahoo expects me to respond promptly to 5xx bounces, disabling any subscriptions, otherwise it starts generating 'greylist' 4xx bounces for my mail. Unfortunately, if I try to lower the bounce threshold, the now-daily occurence of 4xx bounces guarantees that all yahoo addresses will end up disabled. Is there any way, short of fiddling with and recompiling from source, to separate 'hard' bounce handling from 'soft' bounce handling, or to change the 'scores' that each accumulates? Or any other trick to handle bounces properly when yahoo is tossing out greylist deferrals. At this point is just amounts to a nuisance with delayed deliveries for a lot of list mail. But it would be better to have our mailman properly disable when 5xx errors occur Why is your MTA returning 4xx status to Mailman as a bounce? Your MTA should be retrying these and eventually delivering them. If you're getting bounces like message undeliverable after 4 hours; will keep trying until message is 5 days old Mailman should be ignoring those. If it isn't, send me a complete, raw copy of the DSN, and I'll fix it and tell you how to fix yours. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Can't change host name preference
Mike Flaherty wrote:
I am trying to set up Mailman on a new domain. I have done it in the past
without issue, but now I have a really bizzare problem.
When I go to the MYLIST mailing list administration General Options Section
page, I notice the following entry preloaded in the Host name this list
prefers for email field...
syd.xobas.net
I have NO IDEA where this is coming from. It is not my domain, so I replace
it with my own.
It comes from the add_virtualhost() entry for the domain. There should
be an
add_virtualhost('web_domain', 'email_domain')
line in mm_cfg.py. Then if you create the list from the web interface
with a URL whose host name is 'web_domain', the list will be created
with host_name = 'email_domain'.
Likewise if you create the list with bin/newlist -u 'web_domain'
However, when I click the Submit your changes button, it goes to an invalid
page.
You mean a 404? If so, the list's web_page_url is also messed up.
When I try again, I notice that when I hover over the button, the URL
that it translates to incorporates that syd.xobas.net domain into
the URL.
Huh? The button is a submit action for a form. Are you saying the POST
action URL has host syd.xobas.net? If so, my best guess is that that
is the value of DEFAULT_URL_HOST and DEFAULT_EMAIL_HOST in your
installation.
I looked all over my server (a vps running CentOS 5) for where that entry
might be coming from. I did find an occurance of it in
/var/lib/mailman/archives/private/MYLIST/index.html
and
/var/lib/mailman/archives/private/mailman/index.html
But I don't know how it got there. Where is the proper place to replace that
domain with my own?
In mm_cfg.py
DEFAULT_URL_HOST = 'your_web_domain'
DEFAULT_EMAIL_HOST = 'your_email_domain'
VIRTUAL_HOSTS.clear()
add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
plus add_virtualhost() lines for any additional domains.
Then run fix_url to fix the existing list, e.g.
bin/withlist -l -a -r fix_url
--
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Problems in Mailman
Mario Sergio wrote: I'm having some problems with a Mailman. When I accept an email that was received in a list, I get this in the error log: Apr 01 14:57:01 2009 (2315) SHUNTING: 1238608621.3245921+6e71fad398d2eba77746fc941cf6b1123ed7ecd3 Apr 01 14:57:01 2009 (2315) Uncaught runner exception: invalid load key, '7'. Apr 01 14:57:01 2009 (2315) Traceback (most recent call last): File /usr/lib/mailman/Mailman/Queue/Runner.py, line 112, in _oneloop self._onefile(msg, msgdata) File /usr/lib/mailman/Mailman/Queue/Runner.py, line 170, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File /usr/lib/mailman/Mailman/Queue/IncomingRunner.py, line 130, in _dispose more = self._dopipeline(mlist, msg, msgdata, pipeline) File /usr/lib/mailman/Mailman/Queue/IncomingRunner.py, line 153, in _dopipeline sys.modules[modname].process(mlist, msg, msgdata) File /usr/lib/mailman/Mailman/Handlers/Moderate.py, line 109, in process Hold.hold_for_approval(mlist, msg, msgdata, Hold.NonMemberPost) File /usr/lib/mailman/Mailman/Handlers/Hold.py, line 243, in hold_for_approval cookie = mlist.pend_new(Pending.HELD_MESSAGE, id) File /usr/lib/mailman/Mailman/Pending.py, line 65, in pend_new db = self.__load() File /usr/lib/mailman/Mailman/Pending.py, line 95, in __load return cPickle.load(fp) UnpicklingError: invalid load key, '7'. For this one, the lists/listname/pending.pck is corrupt. Just remove it or move it aside. And this: Apr 01 15:09:57 2009 (2312) SHUNTING: 1238609343.8684261+bff1c62c38a18427c91c1a4bb7ca5f7dfe15a267 Apr 01 15:11:01 2009 (2312) Uncaught runner exception: bad marshal data Apr 01 15:11:01 2009 (2312) Traceback (most recent call last): File /usr/lib/mailman/Mailman/Queue/Runner.py, line 112, in _oneloop self._onefile(msg, msgdata) File /usr/lib/mailman/Mailman/Queue/Runner.py, line 170, in _onefile keepqueued = self._dispose(mlist, msg, msgdata) File /usr/lib/mailman/Mailman/Queue/ArchRunner.py, line 73, in _dispose mlist.ArchiveMail(msg) File /usr/lib/mailman/Mailman/Archiver/Archiver.py, line 216, in ArchiveMail h.processUnixMailbox(f) File /usr/lib/mailman/Mailman/Archiver/pipermail.py, line 583, in processUnixMailbox self.add_article(a) File /usr/lib/mailman/Mailman/Archiver/pipermail.py, line 635, in add_article article.parentID = parentID = self.get_parent_info(arch, article) File /usr/lib/mailman/Mailman/Archiver/pipermail.py, line 667, in get_parent_info article.subject) File /usr/lib/mailman/Mailman/Archiver/HyperDatabase.py, line 311, in getOldestArticle self.__openIndices(archive) File /usr/lib/mailman/Mailman/Archiver/HyperDatabase.py, line 251, in __openIndices t = DumbBTree(os.path.join(arcdir, archive + '-' + i)) File /usr/lib/mailman/Mailman/Archiver/HyperDatabase.py, line 65, in __init__ self.load() File /usr/lib/mailman/Mailman/Archiver/HyperDatabase.py, line 170, in load self.dict = marshal.load(fp) ValueError: bad marshal data For this one, one of the archives/private/LISTNAME/database/* files is corrupt, probably for the current month. The qfiles/shunt directory is empty: [r...@andromeda01 mailman]# ls -la qfiles/shunt/ total 8 drwxrwsr-x 2 mailman mailman 4096 Mar 25 10:36 . drwxrwsr-x 11 rootmailman 4096 Mar 25 10:36 .. That's strange. Try to find them. E.g. locate 1238609343.8684261+bff1c62c38a18427c91c1a4bb7ca5f7dfe15a267.pck or find / -name 1238609343.8684261+bff1c62c38a18427c91c1a4bb7ca5f7dfe15a267.pck -print In the data directory I have some files .pck, like this: [r...@andromeda01 mailman]# ls -la data/ total 69048 drwsrwsr-x 2 rootmailman 20480 Abr 1 15:46 . drwxrwsr-x 9 rootmailman4096 Abr 1 14:37 .. -rw-rw-r-- 1 mailman mailman 2295278 Abr 1 15:46 heldmsg-cobranca-23.pck -rw-rw-r-- 1 mailman mailman 489013 Abr 1 15:46 heldmsg-cobranca-24.pck -rw-rw-r-- 1 mailman mailman1463 Abr 1 15:46 heldmsg-cobranca-35.pck -rw-rw-r-- 1 mailman mailman4431 Abr 1 15:45 heldmsg-informatica-10.pck -rw-rw-r-- 1 mailman mailman5026 Abr 1 15:45 heldmsg-informatica-11.pck -rw-rw-r-- 1 mailman mailman 98672 Abr 1 15:45 heldmsg-informatica-12.pck -rw-rw-r-- 1 mailman mailman4431 Abr 1 15:45 heldmsg-informatica-13.pck Those are held messages for the respective lists I run the check_db command, and it's report this: [r...@andromeda01 mailman]# check_db --all --verbose Lista: direta /var/lib/mailman/lists/direta/config.pck: Ok /var/lib/mailman/lists/direta/config.pck.last: Ok [Errno 2] No such file or directory: '/var/lib/mailman/lists/direta/config.db' [Errno 2] No such file or directory: '/var/lib/mailman/lists/direta/config.db.last' Lista: vendasf /var/lib/mailman/lists/vendasf/config.pck: Ok /var/lib/mailman/lists/vendasf/config.pck.last: Ok [Errno 2] No such file or directory:
Re: [Mailman-Users] Debugging question
Whit Blauvelt wrote: I know - it's a wiki and presumably I could jump in and rearrange stuff. I'd do that, if there's a sense that it's appropriate and no one with real expertise on Mailman wants to take it on. Oh, I've been trying to find someone willing to do this for months now (pretty much since I moved the FAQ wizard stuff to the new wiki). If you want to volunteer, please do so with my blessing! The current FAQ is ordered by number when the answer was added which is why it's kinda hard to find things. No organization other than the top level sections. If you could keep those old numbers in the post somewhere so anyone searching for old FAQ entry 4.24, say, can just search for 4.24 and find it, that would be good. But other than that, please feel free to take a stab at it. Pretty please? :) Terri -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Bounce updating
Steff Watkins wrote: Looking into it a bit further I found that the 'bounce' logfile records some (minorly) useful info about what it is doing. Doing a grep on the term 'disabled' returns lines such as: Mar 10 09:00:02 2009 (3577) Notifying disabled member *...@***.org for list: somelist The above log entry is written when a member whose delivery has been disabled by bounce is sent a warning message by cron/disabled. What may be of most use to you however is to modify this grep to match the phrase deleted after exhausting notices which I believe is the error line given when an email address goes over its bounce score. This returns lines such as: Mar 12 09:00:02 2009 (3388) somelist: ***...@.com deleted after exhausting notices Actually, the above log entry is written when the member is removed from the list which may or may not be at the same time as when the member's score hits the threshold depending of bonce_you_are_disabled_warnings. When a member's score reaches the threshold, the bounce log entry is Mar 22 12:32:05 2009 (5641) LISTNAME: u...@example.com disabling due to bounce score n.n = n.n -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] To-Do-list admin
From: Mark Sapiro m...@msapiro.net Helmut Schneider wrote: From: Mark Sapiro m...@msapiro.net Helmut Schneider wrote: I did not touch the MTA setting, the only things I added are DEFAULT_EMAIL_HOST DEFAULT_URL_HOST DEFAULT_URL_PATTERN PUBLIC_ARCHIVE_URL add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST) DELIVERY_MODULE = 'SMTPDirect' SMTPHOST SMTPPORT Communication itself seems fine, i recieved a subscription reminder this morning from mailman-owner. What is/are the address(es) listed for the owner of the mailman list? postmas...@domain.tld Are they deliverable? This is where the aliases mail is sent. What happens if you send mail to mailman-ow...@...? A mail to mailman-ow...@domain.tld is forwarded to postmas...@domain.tld and gets delivered. And is that also true if it is sent via SMTPHOST:SMTPPORT (assuming they are different from localhost)? Yes. Nevermind, I kicked the installation and installed from scratch, now it's fine. Thanks, Helmut -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Moderator and Admin emails not being sent...
Todd Giles wrote: I've been debugging this for some time now, multiple google searches, etc... all to no avail. I have a mailman list setup and working fine, with the exception of moderator and admin emails not being sent (at least not received). I've narrowed down to one fairly simple test case, that is to leave an unmoderated email in the list, and then to run the following command on my server: % /usr/local/bin/python -S checkdbs After running this command, my expectation is to get an email sent out notifying me of the unmoderated email in the list. I never get this email, but I do get the following entries in various logs directly after running that above command: /var/log/maillog: Apr 2 18:22:02 gileszone.com sendmail[12438]: n330M2rP012438: from=sandia-bounces+sandia-owner=gileszone@gileszone.com, size=990, class=-60, nrcpts=1, msgid=mailman.0.1238718120.12361.san...@gileszone.com, proto=ESMTP, relay=gileszone.com [69.36.169.41] Apr 2 18:22:02 gileszone.com sendmail[12438]: n330M2rP012438: to=|/home/gileszone/mailman/mail/mailman post sandia, ctladdr= sandia-ow...@gileszone.com (2058/0), delay=00:00:00, xdelay=00:00:00, mailer=prog, pri=139180, dsn=2.0.0, stat=Sent It appears that the problem is that your alias for sandia-owner is sandia-owner: |/home/gileszone/mailman/mail/mailman post sandia instead of sandia-owner: |/home/gileszone/mailman/mail/mailman owner sandia Thus mailman sends the notice to sandia-owner and instead of being received as a message to -owner, it is received as a post and discarded as being a post from a non-member. You would probably do well to check all your aliases. mailman/logs/smtp: Apr 02 18:22:02 2009 (9073) mailman.0.1238718120.12361.san...@gileszone.com smtp to sandia for 1 recips, completed in 0.104 second message sent to sandia-owner mailman/logs/vette: Apr 02 18:22:03 2009 (9071) Message discarded, msgid: mailman.0.1238718120.12361.san...@gileszone.com received as a list post from sandia-bounces+sandia-owner=gileszone@gileszone.com and discarded as a non-member post. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Googlegroups vs mailman
On Fri, Mar 06, 2009 at 02:59:00AM +, Adam McGreggor wrote: (and, my own experience, config'ing a Mailman list is *so* much easier (and obvious). Particulary when trying to get a code-repo commit messages...) Oh, and another thing, Mailman is *so* much easier to config allowed senders (from non-list-members), particularly, when, for example, the Googlegroups' owner's email address contains an alias, but one can't add that alias as an authorized-sender (equiv), IME. (e.g, f...@gmail.com is the owner, and associated to that account is b...@example.org; sending mail from b...@example.org will cause a hold-up/moderation note, but one can't add b...@example.org to the group, as it already exists or something of that ilk.) Wretchedly annoying, particularly on a commits list, for a google-code project. Bah! -- ``Freedom of the press in Britain means freedom to print such of the proprietor's prejudices as the advertisers don't object to.'' (Hannen Swaffer) -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] [-0.5] Re: Soft bounces....
Charles Gregory wrote: On Fri, 3 Apr 2009, Mark Sapiro wrote: If you're getting bounces like message undeliverable after 4 hours; will keep trying until message is 5 days old Mailman should be ignoring those. I apologize for not thinking through the fact that a 4xx would have to continue for 4 hours before mailman ever heard about it, but now you are saying that notice is ignored. So, I seem to have misunderstood the docs. I thought '4xx' errors (when they get back to mailman) were 'soft', so if 'message undeliverable for 4 hours' doesn't count, then what messages does mailman treat as a 'soft' bounce and only score 0.5? If it's an RFC 3464 compliant DSN with and action of delayed or some heuristically recognized equivalent, it is ignored. The difference between a hard 1.0 bounce and a soft 0.5 bounce was never implemented even though the docs say it works that way. The difference, if it were implemented, would be that failure action with a 4xx or 552 status would count as 0.5 and other failures would count as 1.0, but this is not the way it currently works. All failures count as 1.0 (but only one bounce per day counts). If it isn't, send me a complete, raw copy of the DSN, and I'll fix it and tell you how to fix yours. I'm not working on DSN's, I'm fighting with yahoo over large numbers of stupid, needless 4xx delays in my mail logs (and log reports). There aren't very many things in their generic 'explanations' that seem to apply. So I'm trying to cut down on our system attempting to send mail to 5xx recipients at Yahoo. However, it's only DSNs that Mailman sees, unless your MTA reports a 4xx or 5xx status back to Mailman during Mailman's SMTP with the MTA. In this case, Mailman will log these in smtp-failure and retry the 4xx and 552 statuses at 15 minute intervals for 5 days, and treat the other 5xx statuses as hard bounces. Further to this topic, another suggestion from Yahoo would be to use different IP addresses for different classes of mail. Short of running the mail on a separate server, I was thinking I might try running a separate instance of postfix to send mail from a separate IP. But then how would I tell mailman to use *that* instance of postfix? SMTPHOST and SMTPPORT in mm_cfg.py -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Password reminder on private archive login page
Cihan Yildirim-Yucel wrote: Can I put the password reminder on private archive login page? So that, list members who want to see the archive, but do not remember their passwords, can quickly learn their passwords. Otherwise, password reminder is too hard to find using the links on general list info page.. This is a good idea. I think I'll implement it for Mailman 2.2. What needs to be done is the reminder button has to be added to the private.html archive login template and code needs to be added to Mailman/Cgi/private.py to recognize the button and send the reminder. You can look at Mailman/Cgi/options.py for how it's done there. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] mm_cfg.py in /usr : SELinux problem
Daniel Novotny wrote: The solution I created is to create a new script called mailman-update-cfg'which contains the following: #!/usr/bin/python import py_compile py_compile.compile(/usr/lib/mailman/Mailman/mm_cfg.py) in the mm_cfg.py there's a note, that if you use SELinux, you have to run this script as root after you change the configuration what do you think about this? it's more of a work-around, but it can be a part of the mailman init script in /etc/init.d Since the RedHat package already installs its own /etc/init.d/mailman, I think this is a good solution for the RedHat package. For the rest of us, we're pretty far from FHS compliance and presumably good security policy manager compliance anyway. -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
[Mailman-Users] Testing, checking
Is there a checklist of things to look over, once Mailman is installed, to make sure the site becomes visible to the internet? My site, http://fyrenice.com/mailman works when I am at home on my LAN, but I can't access it when not at home, i.e., it's not yet working correctly. I have these ports opened: 22, 25, 80, 110, 443 via my router. What other ports should I consider? Please advise! Scott -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Testing, checking
Jones, Scott wrote: Is there a checklist of things to look over, once Mailman is installed, to make sure the site becomes visible to the internet? My site, http://fyrenice.com/mailman works when I am at home on my LAN, but I can't access it when not at home, i.e., it's not yet working correctly. I have these ports opened: 22, 25, 80, 110, 443 via my router. What other ports should I consider? Port 25 for incoming mail and ports 80/443 for incoming http/https are all you need. Is your router forwarding those ports to the Mailman machine? Is 75.145.58.209 (the A record address for fyrenice.com and mail.fyrenice.com) the IP address of the router. Is there any other firewall involved? -- Mark Sapiro m...@msapiro.netThe highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Testing, checking
Mark Sapiro wrote: Port 25 for incoming mail and ports 80/443 for incoming http/https are all you need. Is your router forwarding those ports to the Mailman machine? Is 75.145.58.209 (the A record address for fyrenice.com and mail.fyrenice.com) the IP address of the router. Is there any other firewall involved? Maybe the ISP is blocking inbound port 25 and/or 80/443? -- Brad Knowles b...@shub-internet.orgIf you like Jazz/RB guitar, check out LinkedIn Profile: my friend bigsbytracks on YouTube at http://tinyurl.com/y8kpxuhttp://preview.tinyurl.com/bigsbytracks -- Mailman-Users mailing list Mailman-Users@python.org http://mail.python.org/mailman/listinfo/mailman-users Mailman FAQ: http://wiki.list.org/x/AgA3 Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ Unsubscribe: http://mail.python.org/mailman/options/mailman-users/archive%40jab.org Security Policy: http://wiki.list.org/x/QIA9
Re: [Mailman-Users] Mailman password reminders - Resolved
With the excellent help of Mark Sapiro, I was able to resolve my issue with
password reminders. Basically, we wanted for the majority of our lists to have
the normal monthly reminders. For the select few lists, we wanted quarterly
reminders. I made a few modifications to mailpasswds which Mark cleaned
up/refined to allow on option to exclude a list from password reminders. This
was needed since my select few lists need to leave the send_reminders setting
to on but I didn't want the monthly reminders to go out for them. Now, my cron
job for the monthly reminders can exclude the select few lists and I can add
additional cron jobs to send reminders to only the select few lists. E.G.
# send reminders to all lists except for list-a, list-b, and list-c
0 5 1 * * mailman /usr/lib/mailman/cron/mailpasswds -x list-a -x list-b -x
list-c
# send reminders to list-a and list-c in Jan, Apr, and Oct
0 5 1 1,4,10 * mailman /usr/lib/mailman/cron/mailpasswds -l list-a -l list-c
# send reminders to list-b in Aug
0 5 1 8 * mailman /usr/lib/mailman/cron/mailpasswds -l list-b
The new option/switch added is -x or --exclude-list (in long form). I am
including a diff of the changes from Mailman v2.1.9 below. The options of -l
and -x are mutually exclusive.
Thanks,
Chris
--- Diff Begins ---
34c34,40
allowed.
---
allowed. This and the -x/--exclude-list option are mutually
exclusive.
-x listname
--exclude-list
Do not send password reminders for the excluded list. If omitted,
reminders are sent for all lists. Multiple -x/--exclude-list options
are allowed. This and the -l/--listname option are mutually
exclusive.
91,92c97,98
opts, args = getopt.getopt(sys.argv[1:], 'l:h',
['listname=', 'help'])
---
opts, args = getopt.getopt(sys.argv[1:], 'l:x:h',
['listname=', 'exclude-list=', 'help'])
99a106
excludedlists = None
103a111,112
if excludedlists:
usage(1, '-l/--listname and -x/--exclude-list are mutually
exclusive')
107a117,123
if opt in ('-x', '--exclude-list'):
if listnames:
usage(1, '-l/--listname and -x/--exclude-list are mutually
exclusive')
if excludedlists is None:
excludedlists = [arg]
else:
excludedlists.append(arg)
111a128,130
if excludedlists:
listnames = set(listnames) - set(excludedlists)
--- Diff Ends --
Mark Sapiro m...@msapiro.net Thursday, April 02, 2009 2:22 PM
Chris Nulk wrote:
I know I can stop password reminders from going out to list members by turning
off the reminders in the list configuration. I also know I can comment out
the cron entry for mailpasswd to stop it for all lists. In addition, I know I
can send reminders using mailpasswd to a specific list(s). But, can I
exclude sending reminders to specifics lists with mailpasswd. What I would
like to do is send the normal monthly reminders to most of our lists. There
is a small group of lists that I want reminders to be sent to but on a
quarterly/yearly basis instead.
Can I do this using mailpasswd or some other way? Or should I pull out the
big hacking sword, close my eyes, and have a go at mailpasswd? And, does
anyone really want to see the results if I do?
I don't recommend the hack away with eyes closed method, but it
shouldn't be too difficult to add a -x/--exclude option to mailpasswds.
On the other hand you could do something like
#!/bin/sh
excludes=`cat /path/to/lists/to/exclude`
for list in `/path/to/bin/list_lists --bare` ; do
skip=0
for xlist in $excludes ; do
if [ $list == $xlist ] ; then skip=1 ; fi
done
if [ $skip == 0 ] ; then
/path/to/cron/mailpasswds -l $list
fi
done
--
Mark Sapiro m...@msapiro.netThe highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: http://www.mail ( http://www.mail/
)-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/cnulk%40scu.edu
Security Policy: http://wiki.list.org/x/QIA9
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe:
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org
Security Policy: http://wiki.list.org/x/QIA9
