Re: [Mailman-Users] Error in pipermail

[Mark Sapiro]

On 10/25/18 12:03 PM, David Gibbs wrote:
> I just upgraded from a pretty old version of MM to 2.1.29 and everything
> appears to be working OK.
> 
> I noticed the following in my error log though.
> 
> I only have a few lists that archive using the built in functionality.
> 
> Oct 24 07:57:40 2018 (18940) Uncaught runner exception: 'ascii' codec
> can't decode byte 0xb5 in position 26: ordinal not in range(128)
> Oct 24 07:57:40 2018 (18940) 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/ArchRunner.py", line 77, in
> _dispose
>     mlist.ArchiveMail(msg)
>   File "/usr/local/mailman/Mailman/Archiver/Archiver.py", line 216, in
> ArchiveMail
>     h.processUnixMailbox(f)
>   File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 596, in
> processUnixMailbox
>     self.add_article(a)
>   File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 640, in
> add_article
>     author = fixAuthor(article.decoded['author'])
>   File "/usr/local/mailman/Mailman/Archiver/pipermail.py", line 63, in
> fixAuthor
>     while i>0 and (L[i-1][0] in lowercase or
> UnicodeDecodeError: 'ascii' codec can't decode byte 0xb5 in position 26:
> ordinal not in range(128)
> 
> Any suggestions on how to fix this?


There should be a 'SHUNTING: .pck' message immediately following the
above traceback. This points to an entry in Mailman' qfiles/shunt/
directory.

You can see the message by pointing Mailman's bin/show_qfiles at that
file. There is something bogus and/or non-ascii in that message's From:
header, possibly an RFC 2047 encoded word with the 'wrong' character set.

Please post the message or at least the headers of the message here, and
I will investigate further.

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] mm-handler support

[Mark Sapiro]

On 10/25/18 10:00 AM, Grant Taylor via Mailman-Users wrote:
> On 10/25/2018 09:22 AM, Mark Sapiro wrote:
>> Please make whatever changes you feel are needed and post them here,
>> and I will include them in the next release.
> 
> What is the authoritative version / source of mm-handler?


The most up to date version is
.
For some info on the differences between this and the original
,
see the thread beginning at
.

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Reply-to header not set in mime encoded digest's

[Mark Sapiro]

On 10/29/18 12:42 PM, David Gibbs wrote:
> 
> When MM 2.1.29 sends out a mime encoded digest, the individual messages
> in the digest don't have the reply-to header set so replies go back to
> the list (as with non-digest messages).
> 
> Is there any way to have the reply-to header set correctly on
> mime-digest messages?


This is a consequence of the way in which DMARC mitigations are applied
to outgoing messages. The modifications to the From:, Reply-To: and Cc:
headers are not applied to the message that is archived, sent in digests
or gated to usenet.

This is generally a good thing, but is problematic in that non-DMARC
Reply-To: munging is also deferred.

A simple, but possibly unsatisfactory solution is to put the following
two lines in mm_cfg.py

GLOBAL_PIPELINE.remove('ToDigest')
GLOBAL_PIPELINE.insert(GLOBAL_PIPELINE.index('ToOutgoing'), 'ToDigest')

This will cause the message to not be added to the digests until after
the header munging has occurred, but also means any DMARC actions to
munge the From: or wrap the message will be applied to the digested
message which may be undesirable.

-- 
Mark Sapiro The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan
--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] Reply-to header not set in mime encoded digest's

[David Gibbs]

Folks:

On my lists, I have reply_goes_to_list set so users reply's default to the list 
address.


When MM 2.1.29 sends out a mime encoded digest, the individual messages in the 
digest don't have the reply-to header set so replies go back to the list (as 
with non-digest messages).


Is there any way to have the reply-to header set correctly on mime-digest 
messages?

Thanks!

david

--
IBM i on Power Systems: For when you can't afford to be out of business!

I'm riding 615 miles (Yes, you read that right) in the American Diabetes 
Association's Tour de Cure to raise money for diabetes research, education, 
advocacy, and awareness.  You can make a tax deductible donation to my ride by 
visiting https://gmane.diabetessucks.net.


You can see where my donations come from by visiting my interactive donation map 
... https://gmane.diabetessucks.net/map (it's a geeky thing).


I may have diabetes, but diabetes doesn't have me!

--
Mailman-Users mailing list Mailman-Users@python.org
https://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
https://mail.python.org/mailman/options/mailman-users/archive%40jab.org