[Mailman-Users] periodic shunts might have been undetected bad bounce_matching_headers

[Julian H. Stacey]

Hi Mark, thanks for reply.
PS you'r doing a great job answering so many of us :-)

Mark Sapiro wrote:
> On 08/25/2017 06:29 AM, Julian H. Stacey wrote:
> > Hi mailman-users at python.org
> > I hope I may have solved some postings being shunted on a few of my lists,
> > necessitating occasional
> > 	cd /usr/local/mailman; unshunt qfiles/shunt
> > 
> > I discovered 3 lists had missing '\n', shown with
> > 	cd /usr/local/mailman/lists; config_list -o - ListName
> > bounce_matching_headers = """# Lines that *start* with a '#' are comments.
> 
> 
> What is the rest of this up to the terminating """?

Ah yes, I see what you mean, Its not a '' line, but a """ block:
Now I have:
	# Note that leading whitespace is trimmed from the regexp.  This can be
	# circumvented in a number of ways, e.g. by escaping or bracketing it.
	bounce_matching_headers = """
	# Lines that *start* with a '#' are comments.
	to: friend at public.com
	message-id: relay.comanche.denmark.eu
	from: list at listme.com
	from: .*@uplinkpro.com"""
	
	## Bounce options
before it was
	# Note that leading whitespace is trimmed from the regexp.  This can be
	# circumvented in a number of ways, e.g. by escaping or bracketing it.
	bounce_matching_headers = """# Lines that *start* with a '#' are comments.
	to: friend at public.com
	message-id: relay.comanche.denmark.eu
	from: list at listme.com
	from: .*@uplinkpro.com"""
	
	## Bounce options

So fixed, but I guess that wasnt the cause of the shunts. 
Especially as I rcall a shunt on one of the other lists that didnt have that damage.


> > Fixed with 
> > 	cd /usr/local/mailman/lists ; config_list -o ~/tmp/ListName ListName
> > 	vi  ~/tmp/ListName ; config_list -i ~/tmp/ListName ListName
> > & I hope the shunting will stop.
> > 
> > I did autopsy snapshots of /usr/local/mailman before & after last unshunt,
> > if anyone feels like telling me what to look for.
> 
> 
> What is the traceback from the 'shunt' message in Mailman's error log?

/usr/local/mailman/logs/error
  (Aside: I also spotted a few other unassociated errors such as Hostile
  listname: & fixed pages that pointed to non existant local Mailman list names)

All my remaining errors now seem to be the same sort:

	NameError: global name 'syslog' is not defined
	
	Aug 23 13:37:16 2017 (82399) SHUNTING: 1503488012.441064+20509f89ec545c49966a4f1d747c804ea1df5852
	Aug 24 20:56:44 2017 (18093) Uncaught runner exception: global name 'syslog' is not defined
	Aug 24 20:56:44 2017 (18093) Traceback (most recent call last):
	  File "/usr/local/mailman/Mailman/Queue/Runner.py", line 119, in _oneloop
	    self._onefile(msg, msgdata)
	  File "/usr/local/mailman/Mailman/Queue/Runner.py", line 190, in _onefile
	    keepqueued = self._dispose(mlist, msg, msgdata)
	  File "/usr/local/mailman/Mailman/Queue/IncomingRunner.py", line 130, in _dispose
	    more = self._dopipeline(mlist, msg, msgdata, pipeline)
	  File "/usr/local/mailman/Mailman/Queue/IncomingRunner.py", line 153, in _dopipeline
	    sys.modules[modname].process(mlist, msg, msgdata)
	  File "/usr/local/mailman/Mailman/Handlers/SpamDetect.py", line 136, in process
	    syslog('vette',
	NameError: global name 'syslog' is not defined
	
	Aug 24 20:56:44 2017 (18093) SHUNTING: 1503601003.748515+0146d084002ddd93cacadc41656c7632efc83301

/usr/local/mailman/Mailman/Handlers/SpamDetect.py line 136
	syslog('vette',
                    '%s: Automatically Moderated %s for verbose postings.',
                     mlist.real_name, sender)

	Line 34:	from Mailman import mm_cfg
	Mailman/mm_cfg.py has no syslog
	So I'm searching for syslog in my FreeBSD /usr/ports/mail/mailman 
	Got a bit lost maybe this might be FreeBSD specific,
	Added maintainer of the FreeBSD ports wrapper in case of a hint ?


> > Unfortunately the corrupt bounce_matching_headers lines in configuration
> > were undetected by these automatic checks 
> > 	cd /usr/local/etc/rc.d; ./mailman stop ; ./mailman start 
> > 	cd /usr/local/mailman/lists ; ../bin/check_db -a
> > 	cd /usr/local/mailman/lists ; ../bin/check_perms
> 
> 
> If bounce_matching_headers contains an invalid line, there should be
> entries in Mailman's 'config' log like
> 
> 'bad bounce_matching_header line: LISTNAME
> LINE
> 
> or
> 
> bad regexp in bounce_matching_header line: LISTNAME
> REGEXP (cause: ERROR)

cd /usr/local/mailman/logs
	grep bad *
	grep header *
No other errors, apart from 
	admin: No such list "admin":

Thanks,
Julian
-- 
Julian H. Stacey, Computer Consultant, BSD Linux Unix Systems Engineer, Munich
 Reply below, Prefix '> '. Plain text, No .doc, base64, HTML, quoted-printable.
 http://berklix.eu/brexit/#3,500,000_stolen_votes_inc_700,000_in_EU