Re: [Mailman-Users] Bogus mail to list from JavaMail.yahoo
On 3/6/19 2:55 PM, Mark Dale wrote: > Hi All, > > This may be a Postfix issue rather than a Mailman one, but the Mailman > post log (snip below) is showing some relevant info, so here goes. > > This morning there was a legitimate post to a list from a subscriber > with a Gmail account. > > Shortly after, there was a deluge of bogus posts (one every minute) > repeating the same email to the list purporting to come from the same > address. Look in your mail logs and see where these posts come from and anything else you can see. Also look in the list's archives/private/redacted-listname.mbox/redacted-listname.mbox file at all the headers from these posts. I suspect some list member has some process that's echoing received posts back to the list. It's not a simple .forward because that would preserve the X-BeenThere: header which would prevent the message from being reposted. -- 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] Bogus mail to list from JavaMail.yahoo
Hi All, This may be a Postfix issue rather than a Mailman one, but the Mailman post log (snip below) is showing some relevant info, so here goes. This morning there was a legitimate post to a list from a subscriber with a Gmail account. Shortly after, there was a deluge of bogus posts (one every minute) repeating the same email to the list purporting to come from the same address. The Mailman "post" logs below show the original at 13:43 with the google.com ID, and the following bogus messages all with a yahoo.com ID This appears to be happening to only the one list on the server. If anyone could shed some light on this, or point me in the right direction, it'd be much appreciated. Regards, Mark Mar 06 13:43:12 2019 (21321) post to redacted-listname from john.citi...@gmail.com, size=18763, message-id=<0aa0c90583715...@google.com>, success Mar 06 13:44:09 2019 (21321) post to redacted-listname from john.citi...@gmail.com, size=16906, message-id=<1951431589.1505.1551897769010.javamail.ya...@tardis008.cal.bf1.yahoo.com>, success Mar 06 13:45:09 2019 (21321) post to redacted-listname from john.citi...@gmail.com, size=16896, message-id=<1838256988.2441.1551897771539.javamail.ya...@tardis064.cal.bf1.yahoo.com>, success Mar 06 13:46:06 2019 (21321) post to redacted-listname from john.citi...@gmail.com, size=16889, message-id=<574641303.2211.1551897775604.javamail.ya...@tardis001.cal.bf1.yahoo.com>, success ... and on and on ... -- 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] Mailing list "Mailman" mandatory?
On 3/6/19 10:22 AM, Davide Marchi wrote: > Hi Friends, and excuse me for my silly question! > > I've read from a non official documentation, here: > https://www.howtoforge.com/how-to-install-and-configure-mailman-with-postfix-on-debian-squeeze > > that "Before we can start to use Mailman, we must create a mailing list > called mailman; this is obligatory - without it Mailman won't start:" > > is this information right? > Or is it mandatory to start up Mailman and then (after the new lists > creation) it can be removed? Mailman 2.1 requires the site list, normally named 'mailman'. In a new installation, you need to create this list before you can start Mailman. Typically, you create it with Mailman's bin/newlist command. And no, you can't remove it. -- 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] Mailing list "Mailman" mandatory?
Hi Friends, and excuse me for my silly question! I've read from a non official documentation, here: https://www.howtoforge.com/how-to-install-and-configure-mailman-with-postfix-on-debian-squeeze that "Before we can start to use Mailman, we must create a mailing list called mailman; this is obligatory - without it Mailman won't start:" is this information right? Or is it mandatory to start up Mailman and then (after the new lists creation) it can be removed? Many thanks and excuse again! Davide -- 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] Uncaught runner exception
Thank you and sorry for my belated answer. Was out of office for a few
days, carneval season in Germany...
Am 02.03.2019 um 23:20 schrieb Mark Sapiro:
> On 3/1/19 9:00 PM, Mark Sapiro wrote:
>> To try to diagnose this further, you could try:
>>
>> === modified file 'Mailman/Archiver/pipermail.py'
>> --- Mailman/Archiver/pipermail.py2018-05-03 21:23:47 +
>> +++ Mailman/Archiver/pipermail.py2019-03-02 04:51:23 +
>> @@ -60,9 +60,12 @@
>> else:
>> # Mixed case; assume that small parts of the last name will be
>> # in lowercase, and check them against the list.
>> -while i>0 and (L[i-1][0] in lowercase or
>> - L[i-1].lower() in smallNameParts):
>> -i = i - 1
>> +try:
>> +while i>0 and (L[i-1][0] in lowercase or
>> + L[i-1].lower() in smallNameParts):
>> +i = i - 1
>> +except:
>> +syslog('error', 'Exception in fixAuthor: %s', author)
>> author = SPACE.join(L[-1:] + L[i:-1]) + ', ' + SPACE.join(L[:i])
>> return author
>>
>>
>> and see what gets logged in Mailman's error log and what the archived
>> message looks like
>>
Following your instruction errors get now logged like this (where x is
lower case, X upper case alphabet).
Mar 06 10:36:56 2019 (16870) Exception in fixAuthor: Kxx Wxxx
Mar 06 10:36:56 2019 (16870) Exception in fixAuthor: NXX - Fx▒xxx XX
x.X.
Mar 06 10:36:57 2019 (16870) Exception in fixAuthor: Fx▒
Tx▒xxx x.X.
Mar 06 10:36:57 2019 (16870) Exception in fixAuthor: RXX x.X.
The missing characters ▒ are German "Umlaute".
The messages have now been archived and look ok, not mutilated anyhow.
But of course they are still stuck in qfiles/shunt
> Also, in your original post you posted
>
>
>> Feb 28 12:29:02 2019 (3123) Uncaught runner exception: 'ascii' codec
>> can't decode byte 0xb5 in position 26: ordinal not in range(128)
>> Feb 28 12:29:02 2019 (3123) Traceback (most recent call last):
>> File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 119, in _oneloop
>> self._onefile(msg, msgdata)
>> File "/usr/lib/mailman/Mailman/Queue/Runner.py", line 190, in _onefile
>> keepqueued = self._dispose(mlist, msg, msgdata)
>> File "/usr/lib/mailman/Mailman/Queue/ArchRunner.py", line 77, 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 596, in
>> processUnixMailbox
>> self.add_article(a)
>> File "/usr/lib/mailman/Mailman/Archiver/pipermail.py", line 640, in
>> add_article
>> author = fixAuthor(article.decoded['author'])
>> File "/usr/lib/mailman/Mailman/Archiver/pipermail.py", line 63, in
>> fixAuthor
>> while i>0 and (L[i-1][0] in lowercase or [error message stops right
>> here]
> Following that in the log there should be two more lines, one describing
> the UnicodeDecodeError exception and one referring to the message being
> shunted and pointing to a qfiles/shunt/*.pck file. You can see the
> contents of that file with either Mailman's bin/show_qfiles or
> bin/dumpdb commands and the From: header in the message may give more info.
>
As for the "From: headers", some appear distorted, some don't:
From: =?UTF-8?Q?L_M=c3=bc?=
From: Kxx W
--
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
