[Mailman-Users] mailman is receiving, but not forwarding emails.

[Kevin Nowaczyk via Mailman-Users]

I performed a massive debian update last week, which included a postfix update. 
Mailman may have updated too (it is currently 2.1.26). All other mail services 
on my server appear to still work (Drupal password resets, Roundcube webmail 
send/receive, virtual mailbox forwarding), but mailman is no longer sending out 
messages. The mailman archives are showing any messages that are sent to the 
list, but users are not receiving a copy. The mailman log files are 
suspiciously empty. The vet file does show where I tried to message a list I am 
not a member to, but nothing about the numerous times posting to a list that I 
am a member to, which is in the archive.
here is a typical log message:
May  5 11:55:12 bunsen postfix/smtpd[3101]: 3876038119: 
client=mail-qt0-f177.google.com[209.85.216.177]

May  5 11:55:12 bunsen postfix/cleanup[28458]: 3876038119: 
message-id=

May  5 11:55:12 bunsen opendkim[557]: 3876038119: mail-qt0-f177.google.com 
[209.85.216.177] not internal

May  5 11:55:12 bunsen opendkim[557]: 3876038119: not authenticated

May  5 11:55:12 bunsen opendkim[557]: 3876038119: DKIM verification successful

May  5 11:55:12 bunsen opendkim[557]: 3876038119: s=google 
d=google-hosted-domain SSL

May  5 11:55:12 bunsen postfix/qmgr[4308]: 3876038119: 
from=, size=2305, nrcpt=1 (queue active)

May  5 11:55:12 bunsen postfix/local[27003]: 3876038119: 
to=, 
orig_to=, relay=local, delay=0.3, 
delays=0.16/0/0/0.14, dsn=2.0.0, status=sent (delivered to command: 
/var/lib/mailman/mail/mailman post listname)

May  5 11:55:12 bunsen postfix/qmgr[4308]: 3876038119: removed

Thanks for any help,Kevin Nowaczyk
--
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] mailman is receiving, but not forwarding emails.

[Mark Sapiro]

On 5/5/18 11:08 AM, Kevin Nowaczyk via Mailman-Users wrote:
> I performed a massive debian update last week, which included a postfix 
> update. Mailman may have updated too (it is currently 2.1.26). All other mail 
> services on my server appear to still work (Drupal password resets, Roundcube 
> webmail send/receive, virtual mailbox forwarding), but mailman is no longer 
> sending out messages. The mailman archives are showing any messages that are 
> sent to the list, but users are not receiving a copy. The mailman log files 
> are suspiciously empty. The vet file does show where I tried to message a 
> list I am not a member to, but nothing about the numerous times posting to a 
> list that I am a member to, which is in the archive.


The message is archived so IncomingRunner and ArchRunner are running.
Messages aren't being sent and nothing is in Mailman's post or smtp logs
so OutgoingRunner is not processing the messages. Nothing in Mailman's
error log indicates OutgoingRunner just isn't running and the messages
are probably all waiting in Mailman's out queue.

Look in Mailman's qrunner log for messages about OutgoingRunner.
Stopping and starting (not restarting) Mailman may help.

-- 
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] Still having trouble with an email filter vis-a-vis Chinese crap.

[Kenneth G. Gordon]

In my mailman Privacy options/Spam filters/Regexps my expression:

^Subject: =\?utf-8\?B\?

does NOT appear to work to discard all posts with that expression in the 
subject line.

That traffic always contains this:

Subject =?utf-8?B?

before all the following garbage.

Sometimes that expression beginning with = is contained multiple times in the 
traffic I want 
to discard.

As you can see above, I have escaped all the ? characters.

Is there something further I need to do to make this work as it should?

Obviously, I am still doing something wrong, but I can't see it.

I thought the escape character was the \, but maybe it is a / . ?

What?

I am, presently, not all that happy, although I have cut down the Chinese 
garbage by about 
90% since I implemented other filters. There remains the 10% which is still 
very annoying.

Ken Gordon

---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

--
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] Still having trouble with an email filter vis-a-vis Chinese crap.

[Mark Sapiro]

On 05/05/2018 12:44 PM, Kenneth G. Gordon wrote:
> In my mailman Privacy options/Spam filters/Regexps my expression:
> 
> ^Subject: =\?utf-8\?B\?
> 
> does NOT appear to work to discard all posts with that expression in the 
> subject line.
> 
> That traffic always contains this:
> 
> Subject =?utf-8?B?


Do you really mean it doesn't contain the ':'?

You could try

^Subject:?\s*=\?utf-8\?B\?

which would match Subject followed by a colon or not and any amount of
white space.


> before all the following garbage.
> 
> Sometimes that expression beginning with = is contained multiple times in the 
> traffic I want 
> to discard.


That's because each '=?utf-8?B?...?=' is and RFC 2047 encoded 'word' and
there can be  any number of them in the Subject: header.


> As you can see above, I have escaped all the ? characters.
> 
> Is there something further I need to do to make this work as it should?


What you have will match a line beginning with 'Subject: =?utf-b?B?'
case insensitively, but only if there is a colon followed by exactly one
space.


> Obviously, I am still doing something wrong, but I can't see it.
> 
> I thought the escape character was the \, but maybe it is a / . ?


It is '\'.


> I am, presently, not all that happy, although I have cut down the Chinese 
> garbage by about 
> 90% since I implemented other filters. There remains the 10% which is still 
> very annoying.


As has been mentioned before the above pattern will match any Subject:
header which begins with a base-64 RFC 2047 encoded word with a utf-8
encoding. This includes some non-english language subjects (more than
just Chinese) and also some English language subjects that might begin
with an emoji or other non-ascii symbol and doesn't include Chinese
language subjects that might be encoded in gb-2312 or some other
non-utf-8 encoding.

This may work for you, but in general might discard a wanted post.

-- 
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] Still having trouble with an email filter vis-a-vis Chinese crap.

[Kenneth G. Gordon]

On 5 May 2018 at 13:20, Mark Sapiro wrote:

> > Subject =?utf-8?B?
> 
> Do you really mean it doesn't contain the ':'?
 
I am reasonably sure that SOME do not, possibly those few which are getting 
through, but 
since you brought that up (although I DID suspect as much), I have not been 
able to check 
on the accuracy of my memory since so far this morning, I have had no more of 
them show 
up.

> You could try
> 
> ^Subject:?\s*=\?utf-8\?B\?
> 
> which would match Subject followed by a colon or not and any amount of
> white space.

OK. That sounds perfect.

> What you have will match a line beginning with 'Subject: =?utf-b?B?'
> case insensitively, but only if there is a colon followed by exactly one
> space.

Ah. Makes sense.

> > I thought the escape character was the \, but maybe it is a / . ?
> 
> It is '\'.

As I thoughtfrom my years as a Unix SYSAD...but that was a long time ago. 
I'm 76 now.

> > I am, presently, not all that happy, although I have cut down the Chinese 
> > garbage by about 
> > 90% since I implemented other filters. There remains the 10% which is still 
> > very annoying.
> 
> 
> As has been mentioned before the above pattern will match any Subject:
> header which begins with a base-64 RFC 2047 encoded word with a utf-8
> encoding. This includes some non-english language subjects (more than
> just Chinese) and also some English language subjects that might begin
> with an emoji or other non-ascii symbol and doesn't include Chinese
> language subjects that might be encoded in gb-2312 or some other
> non-utf-8 encoding.
> 
> This may work for you, but in general might discard a wanted post.

For the two forums I am managing, that is NOT a problem.

Thanks. You are (obviously) a real genius at this stuff with loads of 
experience.

Much appreciated.

Ken Gordon

---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

--
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] Still having trouble with an email filter vis-a-vis Chinese crap.

[Mark Sapiro]

On 05/05/2018 02:05 PM, Kenneth G. Gordon wrote:
> On 5 May 2018 at 13:20, Mark Sapiro wrote:
> 
>>> Subject =?utf-8?B?
>>
>> Do you really mean it doesn't contain the ':'?
>  
> I am reasonably sure that SOME do not, possibly those few which are getting 
> through, but 
> since you brought that up (although I DID suspect as much), I have not been 
> able to check 
> on the accuracy of my memory since so far this morning, I have had no more of 
> them show 
> up.
> 
>> You could try
>>
>> ^Subject:?\s*=\?utf-8\?B\?
>>
>> which would match Subject followed by a colon or not and any amount of
>> white space.


However, if the colon is missing, the

Subject =?utf-8?B?...

line is not a header and it can't be matched by header_filter_rules.

I.e., a message like

   To: someone
   From: someone
   Message-ID: 
   Subject hi there
   Date: some date

   body

will be parsed as headers

   To: someone
   From: someone
   Message-ID: 

and body

   Subject hi there
   Date: some date

   body

so there's no way you can match that 'Subject' with header_filter_rules
because it isn't a header. If that's really what you're looking at, you
would have to implement a custom handler to match that. See
.

On the other hand, if some MUA actually displays the decoded line as the
message subject, it almost certainly does have the colon.

-- 
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