Hello all,
we're using mailman-2.1.29 to operate a list where all users are moderated.
The MTA used is postfix 3.2.0.
Generally everything seems to be working fine. I.e. when I send out an e-mail I have
several confirmations that it arrives under the addresses subscribed to the list.
However, (at least) for one user the e-mail does not arrive. And I would at least
like to find out the reason. But there's no trace of the address in any of the
logfiles that should hold an entry (see below).
Generally I'm able to send messages using my MUA to the corresponding e-mail address
using the very same postfix also delivering the mailman messages. So I'm guessing
it's nothing like DMARC problems or the likes.
Like I said, what really puzzles me is that I cannot find the address in either
/var/log/mail (postfix)
or /var/lib/mailman/logs/* (mailman)
/var/lib/mailman/logs/error doesn't contain any entries.
/var/lib/mailman/logs/bounce does contain some addresses with a bounce score of 1.0
which are for /other/ e-mail addresses also subscribed to the list in question.
/var/log/mail contains entries for /some/ of the addresses subscribed (including some
bounces), but *not* for all.
/var/lib/mailman/logs/smtp gives me a log entry with the original messages and claims
to have sent it to 416 recips (which is correct).
But overall I'm only able to find roughly half in either /var/log/mail or
/var/lib/mailman/logs/*.
Why are not all 416 addresses listed in /var/log/mail, assuming that mailman handed
416 mails to postfix?
Do I have any chance of finding out what happened to the mails to the addresses which
don't appear in any of the log files?
Any hints/insights are greatly appreciated!
Thanks -- Till
--
PRESENSE Technologies GmbH Sachsenstr. 5, D-20097 HH
Geschäftsführer/Managing Directors AG Hamburg, HRB 107844
Till Dörges, Jürgen Sander USt-IdNr.: DE263765024
Wir sind wieder auf dem BSI IT-Sicherheitskongress
21.-23. Mai 2019 – Bonn
https://wiki.list.org/DOC/How%20do%20I%20move%20a%20list%20to%20a%20differe….
The linked examples don't show copying the qfiles directory. I'm
migrating a very busy server (lists.gnu.org), that always has lots of
queue files in the qfiles directory. Shouldn't I copy that directory
over too after shutting down mailman?
--
Ian Kelling | Senior Systems Administrator, Free Software Foundation
GPG Key: B125 F60B 7B28 7FF6 A2B7 DF8F 170A F0E2 9542 95DF
https://fsf.org | https://gnu.org
I've got a mailman 2.1.26 install I've taken over. I've attempted to turn
on DMARC message wrapping by setting DEFAULT_DMARC_MODERATION_ACTION in my
mm_cfg.py file, but it doesn't seem to have had the desired effect. I'm
still seeing messages from p=reject domains going out with their original
headers, and subscribers being blocked as a result of the bounces.
These are the (non-comment) contents of my mm_cfg.py, with the mail domain
anonymized:
from Defaults import *
DEFAULT_URL_HOST = 'lists.example.com'
VIRTUAL_HOSTS.clear()
add_virtualhost('lists.example.com', 'lists.example.com')
DEFAULT_URL_PATTERN = 'https://%s/mailman/'
DEFAULT_DMARC_MODERATION_ACTION = 2
The docs say this sets a minimum bar for the per-list configurations, but
when I go to look at those they're all still set to 0/Accept, and in the
web UI the full range of options is still available.
There is a distinct possibility I've got my hands on the wrong config
file. This install isn't using the version from the system package
manager.. it's a manually compiled install that looks like it has an
install prefix of /usr/local/mailman. This file is
/usr/local/mailman/Mailman/mm_cfg.py. I don't see an obvious way to get
mailman to spit out the full path it's actually checking for the file, but
the output of mailman-config suggests it's probably looking in the right
place.
% ./mailman-config -h
Configuration and build information for Mailman
Mailman version: 2.1.26
Build Date: Wed May 2 13:10:19 UTC 2018
prefix: /usr/local/mailman
var_prefix: /usr/local/mailman
mailman_user: mailman
mailman_group: mailman
mail_group: mail
cgi_group: www-data
configure_opts: "--with-mail-gid=mail --with-cgi-gid=www-data"
I see no mention of mm_cfg.py in the mailman logs.. so nothing clearly
indicating it's failing to find the file (nor positive feedback that it has
found the file).
But I'm not convinced that's the problem anyway, since mailman clearly is
picking up the virtual host and list URL settings. Any suggestions for
what else I should be looking at to get Mailman to pick up this config
change?
Thanks!
(I'm using Mailman 2.1.29.)
I would like to eventually remove Digest mode from a couple of lists,
but I don't want to interfere with users who currently use it.
Can I remove the choice for new members, but still keep the digests
working? I guess just removing the lines about it in the listinfo page
and the personal member page for regular subscribers would suffice for
me, if that can be achieved.
--
Per Starbäck <starback(a)stp.lingfil.uu.se>
Hi,
As part of some upgrade projects I am testing using a transactional email service (Sendgrid) and have eventually got bounce forwarding working. However Mailman is not seeing the address in the bounce so is forwarding it to the list owner. I am probably not going to use Sendgrid long-term, as they seem to have a worse reputation than our static IPs, but wanted to know if I could get Mailman to process this bounce somehow?
Here is the bounce message, I know I can enable VERP and this problem should go away, but I wanted to see if I could get this working without VERP as we have a large mail traffic on the list.
Thanks.
Andrew.
Received: from o198-37-151-26.outbound-mail.sendgrid.net ([198.37.151.26]) by
samwise.hodgsonfamily.org with esmtps
(TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.89) (envelope-from
<no-reply(a)sendgrid.net>) id 1hQs8e-0000Nl-9y for
bcab-bounces(a)lists.bcab.org.uk; Wed, 15 May 2019 12:32:07 +0100
Date: Wed, 15 May 2019 11:00:09 +0000
To: bcab-bounces(a)lists.bcab.org.uk
From: no-reply(a)sendgrid.net
Subject: Undelivered Mail Returned to Sender
X-Spam-Score: -0.3 (/)
X-Spam-Report: BAYES_00=-1.9, HELO_STATIC_HOST=-0.001, INVALID_DATE=1.096,
MISSING_MID=0.497, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001,
URIBL_BLOCKED=0.001
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
--66728b7fa14ce3ed
Content-Type: text/plain
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Content-Description: Notification
This is an automatically generated message from SendGrid.
We are sorry to tell you that your email was unable to be
delivered to one of its intended recipients.
If you require assistance with this, please contact SendGrid support.
[TSS04] Messages from 167.89.106.6 temporarily deferred due to user complaint=
s - 4.16.55.1; see https://help.yahoo.com/kb/postmaster/SLN3434.html
--66728b7fa14ce3ed
Content-Type: message/delivery-status
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
Content-Description: Delivery Report
X-SendGrid-Sender: bcab-bounces(a)lists.bcab.org.uk
Arrival-Date: 2019-05-05 11-00-00
Final-Recipient: rfc822; redacted(a)yahoo.com
Original-Recipient: rfc822; redacted(a)yahoo.com
Action: failed
Status: 4.7.0
Diagnostic-Code: 421 4.7.0 [TSS04] Messages from 167.89.106.6 temporarily def=
erred due to user complaints - 4.16.55.1; see https://help.yahoo.com/kb/postm=
aster/SLN3434.html
--66728b7fa14ce3ed
Content-Type: message/rfc822; name=3D"66728b7fa14ce3ed"
Content-Disposition: inline; filename=3D"66728b7fa14ce3ed"
Content-Transfer-Encoding: binary
Content-Description: Undelivered Message
DKIM-Signature: v=3D1; a=3Drsa-sha1; c=3Drelaxed/relaxed;=20
d=3Dlists.bcab.org.uk;=20
h=3Dfrom:subject:to:reply-to:mime-version:content-type:content-transfer-enco=
ding:list-id:list-unsubscribe:list-archive:list-help:list-subscribe;=20
s=3Ds1; bh=3DHSwHQmEzYnh8RVhCdSgx3+oQCI4=3D; b=3DqbnxUiQh9/93x0IvtPJnds+
UzsUGMTysX0jwFGtM3/aaJ2DkmCOa9RaIOHjhFopdNp2jEdDCN3PvxQeCps2t86G
3s2XXATdnbyBklvfuFDnoZ7kDoDbJbbyh4xKFTdBGWjMhYa1qg6Lz6A4Ey3SYeOr
m1uhNPykiWFEriAFs0Bw=3D
DKIM-Signature: v=3D1; a=3Drsa-sha1; c=3Drelaxed/relaxed; d=3Dsendgrid.info; =
h=3Dfrom:subject:to:reply-to:mime-version:content-type:content-transfer-enco=
ding:list-id:list-unsubscribe:list-archive:list-help:list-subscribe;=20
s=3Dsmtpapi; bh=3DHSwHQmEzYnh8RVhCdSgx3+oQCI4=3D; b=3DvLaOMgJkVx4gOD/ISt
q2+4i+yYm+BPygXDX+oQSBYKFqD8m6xiSDL6szf/9ggGawmmE7SZXURlPoBd/iEG
iL7oUIdYMFmhw7hpf8weXvet3pHpSYjDm/V8x01v5j4e9nldPkIqa0UNRPd/2BaN
ggsr2TCLKTtlTmHMm/kJJUGTw=3D
Received: by filter0033p3las1.sendgrid.net with SMTP id filter0033p3las1-1221=
3-5CD7FCB8-37
2019-05-12 11:00:09.005418638 +0000 UTC m=3D+233538.834188040
Received: from samwise.hodgsonfamily.org (samwise.hodgsonfamily.org [213.138.=
110.233])
by ismtpd0002p1lon1.sendgrid.net (SG) with ESMTP id z_pYT4dYT-eVrj9RAaq_jQ
Sun, 12 May 2019 11:00:08.469 +0000 (UTC)
Received: from [::1] (helo=3Dsamwise.hodgsonfamily.org)
by samwise.hodgsonfamily.org with esmtp (Exim 4.89)
(envelope-from <bcab-bounces(a)lists.bcab.org.uk>)
id 1hPmD9-0001xg-KD; Sun, 12 May 2019 12:00:07 +0100
From: bcab-request(a)lists.bcab.org.uk
Subject: Bcab Digest, Vol 444, Issue 7
To: bcab(a)lists.bcab.org.uk
Reply-To: bcab(a)lists.bcab.org.uk
Date: Sun, 12 May 2019 11:00:09 +0000 (UTC)
Message-ID: <mailman.1.1557658803.7540.bcab(a)lists.bcab.org.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=3D"us-ascii"
Content-Transfer-Encoding: 7bit
X-BeenThere: bcab(a)lists.bcab.org.uk
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: BCAB Discussion List <bcab.lists.bcab.org.uk>
List-Unsubscribe: <https://lists.bcab.org.uk/options/bcab>,
<mailto:bcab-request@lists.bcab.org.uk?subject=3Dunsubscribe>
List-Archive: <https://lists.bcab.org.uk/pipermail/bcab/>
List-Help: <mailto:bcab-request@lists.bcab.org.uk?subject=3Dhelp>
List-Subscribe: <https://lists.bcab.org.uk/listinfo/bcab>,
<mailto:bcab-request@lists.bcab.org.uk?subject=3Dsubscribe>
Errors-To: bcab-bounces(a)lists.bcab.org.uk
X-SG-EID: CdqM+Q1xrT/kSH2coGhbodTclTkyEKQEtO7KLouUOI9+psGGnYF6zXb7HRiZwFI6WBd=
pZoQ+G2T2gJ
PFi38sgTGhL9o9OeuLakXU5N+LB7ojKmPXJAXw+RJO/rqiCjQwOgxjJ65jrwb1pFdv1g+rgeWpSP=
D4
TRJYSwUf9eT74JrfEt3RStrhQgSdkn8r3XNU7nG7mWZlCBBZpZkPiZlN+g=3D=3D
[...]
--66728b7fa14ce3ed--
=00
Realizing I didn't respond to the list. So scroll down for my response. Then come back here to continue reading.
Now that I have my Python-fu working I'm retesting Mark's suggestion:
webserv:~# python
Python 2.7.13 (default, Sep 26 2018, 18:42:22)
[GCC 6.3.0 20170516] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import string
>>> string.lowercase
'abcdefghijklmnopqrstuvwxyz'
>>>
It appears that lowercase does return an apparent properly lowercased string of letters. So, I'm uncertain why the hand-edited code would function differently.
Thanks,
Jason Morrill
IT Director
Child and Family Agency
860-443-2896 x1422
http://www.childandfamilyagency.org/
________________________________________
From: Jason Morrill
Sent: Monday, May 13, 2019 10:29 AM
To: Mark Sapiro
Subject: RE: [Mailman-Users] utf-8 error with all lists
Mark, Thanks for the suggestions and link to the remainder of that prior message thread.
I too get the same results related to Python and lowercase.
Now, I'm not a Python programmer but can certainly stumble through to sort things out. Here's what I'm seeing:
webserv:~# python
Python 2.7.13 (default, Sep 26 2018, 18:42:22)
[GCC 6.3.0 20170516] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import string
>>> lowercase
Traceback (most recent call last):
File "<stdin>", line 1, in <module>
NameError: name 'lowercase' is not defined
>>> string
<module 'string' from '/usr/lib/python2.7/string.pyc'>
>>>
Per your suggestion I modified /var/lib/mailman/Mailman/Archiver/pipermail.py to set lowercase = 'abcdefghijklmnopqrstuvwxyz'
And indeed the issue worked itself out. No more errors and I was able to clear the qfiles/shunt folder too.
Per the Python docs, and your info, the string returned by lowercase should be a-z. And it depends upon the locale of the server. Something I've never purposefully changed.
In Debian it looks at /etc/locale.gen
In that file I see my locale set to be
en_US ISO-8859-1
Could that somehow be related to this issue?
Thanks,
Jason Morrill
IT Director
Child and Family Agency
860-443-2896 x1422
http://www.childandfamilyagency.org/
________________________________________
From: Mailman-Users [mailman-users-bounces+morrillj=childandfamilyagency.org(a)python.org] on behalf of Mark Sapiro [mark(a)msapiro.net]
Sent: Saturday, May 11, 2019 2:13 PM
To: mailman-users(a)python.org
Subject: Re: [Mailman-Users] utf-8 error with all lists
On 5/10/19 12:37 PM, Jason Morrill wrote:
> Since the beginning of May I've had a problem with all messages going through Mailman. They are being delivered to the lists properly but copies are staying in qfiles/shunt
>
> The errors appearing in the Mailman error.1 log file indicate
> "
> May 05 10:16:29 2019 (1167) Uncaught runner exception: 'utf8' codec can't decode byte 0xaa in position 26: invalid start byte
...
> File "/var/lib/mailman/Mailman/Archiver/pipermail.py", line 63, in fixAuthor
> while i>0 and (L[i-1][0] in lowercase or
> UnicodeDecodeError: 'utf8' codec can't decode byte 0xaa in position 26: invalid start byte
>
> May 05 10:16:29 2019 (1167) SHUNTING: 1557065787.914554+25c37ef6e662cc98d41ac9d45855fe04f151e11a
>
> "
>
> This is on Debian 9.6 with Python 2.7.13 and Mailman 2.1.23 , all installed from the Debian package manager.
>
> I've spent several hours hunting around for a potential solution. Then stumbled upon this:
> https://mail.python.org/pipermail/mailman-users/2019-March/084243.html
If you read the entire thread (which is split in the archive with the
second part beginning at
<https://mail.python.org/pipermail/mailman-users/2019-March/084266.html>),
you will see that I think the issue is that whatever changed in your
system at the beginning of May is causing the Python
from string import lowercase
in /var/lib/mailman/Mailman/Archiver/pipermail.py to import a lowercase
object which should be the string 'abcdefghijklmnopqrstuvwxyz', but in
fact is longer and has non-ascii accented characters following 'z'.
The OP in that thread couldn't verify that that was the case, but I am
convinced that it is.
There doesn't seem to be a Debian patch to mailman 1:2.1.23-1+deb9u4
that would affect this so it is apparently something in Python or the OS.
I am certain that if you start with the base
/var/lib/mailman/Mailman/Archiver/pipermail.py and change
from string import lowercase
at line 13 to
lowercase = 'abcdefghijklmnopqrstuvwxyz'
the problem will be fixed.
--
Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
------------------------------------------------------
Mailman-Users mailing list Mailman-Users(a)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/morrillj%40childandfa…
I believe this issue is related to my other trouble with utf-8.
https://mail.python.org/pipermail/mailman-users/2019-May/084435.html
Once I hand-edited /var/lib/mailman/Mailman/Archiver/pipermail.py, per the suggestion in that message. I restarted Mailman and ran the unshunt command again.
The shunted messages cleared out and no errors appeared. Though there was no positive affirmation the shunted messages were cleared either. Is the 'shunt' command meant to display anything?
==== Per Mark
No. All unshunt does is move the .pck files from the shunt queue to the
original queue from which they were shunted. It does this silently.
The requeued entry is then processed again by the respective qrunner,
and this process either succeeds or possibly throws the same exception
that caused the shunting in the first place, in which case the message
is shunted again.
=====
Thanks,
Jason Morrill
IT Director
Child and Family Agency
860-443-2896 x1422
http://www.childandfamilyagency.org/
________________________________________
From: Mailman-Users [mailman-users-bounces+morrillj=childandfamilyagency.org(a)python.org] on behalf of Mark Sapiro [mark(a)msapiro.net]
Sent: Saturday, May 11, 2019 1:45 PM
To: mailman-users(a)python.org
Subject: Re: [Mailman-Users] unshunt does nothing
On 5/10/19 12:46 PM, Jason Morrill wrote:
> I have messages accumulating in the qfiles/shunt folder.
>
> Running unshunt does nothing. Literally.
>
> No error message, no progress message. The only change I see is the timestamp on the shunted messages is updated to when I ran the unshunt command.
This is because the message is restored to it's original queue and
processed and throws the same exception that occurred before and is
shunted again.
Are there new entries in Mailman's error log when you unshunt?
> This is on Debian 9.6 with Python 2.7.13 and Mailman 2.1.23 , all installed from the Debian package manager.
>
> BTW - I've been using Mailman for 10+ years on this machine. It's not a new install and these are not new lists.
What changed? Was the Debian package updated?
--
Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
------------------------------------------------------
Mailman-Users mailing list Mailman-Users(a)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/morrillj%40childandfa…
Okay. That worked. Now I have upgraded Mailman from an early 2x to 2.1.29.
the script alias is not working consistently now across all lists. Some web
page admin links are broken requiring me to manually insert the /cgi-bin/
into the web browser to bring up admin pages. Other links work w.o. the
cgi-bin. I cannot admin one of my lists too. Any link I click on in the
General Options Section takes me back to asking me for the list admin
password, i.e. stuck in a loop.
Thank you again.
-----Original Message-----
From: Mailman-Users
[mailto:mailman-users-bounces+csa=web-analysts.net@python.org] On Behalf Of
Mark Sapiro
Sent: Saturday, May 11, 2019 11:22 AM
To: mailman-users(a)python.org
Subject: Re: [Mailman-Users] mailman start error
On 5/11/19 7:43 AM, Web Analysts via Mailman-Users wrote:
> I'm now getting an error when I start Mailman:
>
> root@primeo:~# /etc/init.d/mailman start
> Traceback (most recent call last):
> File "/usr/local/mailman/bin/mailmanctl", line 106, in <module>
> from Mailman import mm_cfg
> File "/usr/local/mailman/Mailman/mm_cfg.py", line 54, in <module>
> add_virtualhost(lists.domainname.tld, lists.domainname.tld)
> NameError: name 'lists' is not defined
> root@primeo:~#
>
>
> What did I inadvertently break?
In the line
add_virtualhost(lists.domainname.tld, lists.domainname.tld)
which you added to mm_cfg.py, the domain names need to be quoted as in
add_virtualhost('lists.domainname.tld', 'lists.domainname.tld')
--
Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
------------------------------------------------------
Mailman-Users mailing list Mailman-Users(a)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/csa%40web-analysts.net
I'm now getting an error when I start Mailman:
root@primeo:~# /etc/init.d/mailman start
Traceback (most recent call last):
File "/usr/local/mailman/bin/mailmanctl", line 106, in <module>
from Mailman import mm_cfg
File "/usr/local/mailman/Mailman/mm_cfg.py", line 54, in <module>
add_virtualhost(lists.domainname.tld, lists.domainname.tld)
NameError: name 'lists' is not defined
root@primeo:~#
What did I inadvertently break?
-----Original Message-----
From: Mailman-Users
[mailto:mailman-users-bounces+csa=web-analysts.net@python.org] On Behalf Of
Mark Sapiro
Sent: Friday, March 22, 2019 9:14 AM
To: mailman-users(a)python.org
Subject: Re: [Mailman-Users] iterative loop
On 3/22/19 5:42 AM, Web Analysts via Mailman-Users wrote:
> Okay here's the output from 'postconf -n'
>
>
> alias_database = hash:/etc/aliases
> alias_maps = hash:/etc/aliases, hash:/var/lib/mailman/data/aliases
OK
...
> mydestination = mail.domainname.tld, mail1.domainname.tld,
> lists.domainname.tld, localhost.domainname.tld, localhost
OK
...
> relay_domains = $mydestination, lists.domainname.tld
lists.domainname.tld is redundant here as it's in $mydestination, but I
think this in combination with
virtual_transport = lmtp:unix:private/dovecot-lmtp
is the issue. I suggest setting
relay_domains = mail.domainname.tld, mail1.domainname.tld,
localhost.domainname.tld, localhost
I.e. everything in $mydestination except lists.domainname.tld.
> relay_recipient_maps = hash:/var/lib/mailman/data/virtual-mailman
Then this will be unnecessary.
If that doesn't fix your issue, look at /var/lib/mailman/data/aliases
and ensure that the aliases for each list that look like
> LISTNAME: "|/var/lib/mailman/mail/mailman post LISTNAME"
> LISTNAME-admin: "|/var/lib/mailman/mail/mailman admin LISTNAME"
> LISTNAME-bounces: "|/var/lib/mailman/mail/mailman bounces LISTNAME"
> LISTNAME-confirm: "|/var/lib/mailman/mail/mailman confirm LISTNAME"
> LISTNAME-join: "|/var/lib/mailman/mail/mailman join LISTNAME"
> LISTNAME-leave: "|/var/lib/mailman/mail/mailman leave LISTNAME"
> LISTNAME-owner: "|/var/lib/mailman/mail/mailman owner LISTNAME"
> LISTNAME-request: "|/var/lib/mailman/mail/mailman request LISTNAME"
> LISTNAME-subscribe: "|/var/lib/mailman/mail/mailman subscribe LISTNAME"
> LISTNAME-unsubscribe: "|/var/lib/mailman/mail/mailman unsubscribe
LISTNAME"
In particular, that the quotes around the commands are not missing,
although I don't see how they could be unless you edited this by hand.
If there is an issue, running Mailman's bin/genaliases as the Mailman user
--
Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
------------------------------------------------------
Mailman-Users mailing list Mailman-Users(a)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/csa%40web-analysts.net
Since the beginning of May I've had a problem with all messages going through Mailman. They are being delivered to the lists properly but copies are staying in qfiles/shunt
The errors appearing in the Mailman error.1 log file indicate
"
May 05 10:16:29 2019 (1167) Uncaught runner exception: 'utf8' codec can't decode byte 0xaa in position 26: invalid start byte
May 05 10:16:29 2019 (1167) Traceback (most recent call last):
File "/var/lib/mailman/Mailman/Queue/Runner.py", line 119, in _oneloop
self._onefile(msg, msgdata)
File "/var/lib/mailman/Mailman/Queue/Runner.py", line 190, in _onefile
keepqueued = self._dispose(mlist, msg, msgdata)
File "/var/lib/mailman/Mailman/Queue/ArchRunner.py", line 77, in _dispose
mlist.ArchiveMail(msg)
File "/var/lib/mailman/Mailman/Archiver/Archiver.py", line 214, in ArchiveMail
h.processUnixMailbox(f)
File "/var/lib/mailman/Mailman/Archiver/pipermail.py", line 596, in processUnixMailbox
self.add_article(a)
File "/var/lib/mailman/Mailman/Archiver/pipermail.py", line 640, in add_article
author = fixAuthor(article.decoded['author'])
File "/var/lib/mailman/Mailman/Archiver/pipermail.py", line 63, in fixAuthor
while i>0 and (L[i-1][0] in lowercase or
UnicodeDecodeError: 'utf8' codec can't decode byte 0xaa in position 26: invalid start byte
May 05 10:16:29 2019 (1167) SHUNTING: 1557065787.914554+25c37ef6e662cc98d41ac9d45855fe04f151e11a
"
This is on Debian 9.6 with Python 2.7.13 and Mailman 2.1.23 , all installed from the Debian package manager.
I've spent several hours hunting around for a potential solution. Then stumbled upon this:
https://mail.python.org/pipermail/mailman-users/2019-March/084243.html
Before making the code edits suggested in that post I was performing a simple test using the 'arch' command.
With the original code the arch command fails with every single list in my system. The error it throws looks like this:
"
Updating HTML for article 66
Pickling archive state into /var/lib/mailman/archives/private/jtest/pipermail.pck
Traceback (most recent call last):
File "./arch", line 201, in <module>
main()
File "./arch", line 189, in main
archiver.processUnixMailbox(fp, start, end)
File "/var/lib/mailman/Mailman/Archiver/pipermail.py", line 606, in processUnixMailbox
self.add_article(a)
File "/var/lib/mailman/Mailman/Archiver/pipermail.py", line 650, in add_article
author = fixAuthor(article.decoded['author'])
File "/var/lib/mailman/Mailman/Archiver/pipermail.py", line 72, in fixAuthor
while i>0 and (L[i-1][0] in lowercase or
UnicodeDecodeError: 'utf8' codec can't decode byte 0xaa in position 26: invalid start byte
"
With the modified code the arch command works perfectly with every single list and no errors are generated in the log file.
I'm going to leave the hand-edited code in-place for the time being. If anyone would like to work with me to diagnose this mystery problem I'd be happy to assist however I can.
Thanks,
Jason Morrill
IT Director
Child and Family Agency
860-443-2896 x1422
http://www.childandfamilyagency.org/
