From mark at msapiro.net  Fri Jun  1 11:36:15 2018
From: mark at msapiro.net (Mark Sapiro)
Date: Fri, 1 Jun 2018 08:36:15 -0700
Subject: [Mailman-Users] Problems Erasing Subscribe Spam
In-Reply-To: <51323a6b-4953-7aeb-93e5-341d9cc89b11@stura.uni-heidelberg.de>
References: <51323a6b-4953-7aeb-93e5-341d9cc89b11@stura.uni-heidelberg.de>
Message-ID: <e2d083f6-5114-e6f5-fc72-304d1b7bd232@msapiro.net>

On 05/31/2018 07:46 AM, R?diger Wolf wrote:
> 
> It works nicely for a bunch of lists, but I don't get why it doesn't
> work with all of them. Looking more closely I found in
> /var/lib/mailman/lists/<listname> the pending.pck file the script is
> operating on.
> 
> Does someone have an idea why it might not work for all lists?


'list_pending' lists requests waiting user confirmation. These are in
the various pending.pck files. 'erase' does not remove them unless you
specify the -p/--pending option. Without that option, 'erase' only
removes list members and moderator requests for the address(es).

Further, even with -p, 'erase' only removes pending subscription
confirmations (type 'S') from pending.pck.

If that doesn't explain what is happening, what does 'list_pending' show
that isn't removed? Also, if 'list_pending' shows subscription
confirmations that aren't removed, what does

ls -la var/lib/mailman/lists/<listname>

show?

-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan

From ruediger at stura.uni-heidelberg.de  Fri Jun  1 11:26:16 2018
From: ruediger at stura.uni-heidelberg.de (=?UTF-8?Q?R=c3=bcdiger_Wolf?=)
Date: Fri, 1 Jun 2018 17:26:16 +0200
Subject: [Mailman-Users] Problems Erasing Subscribe Spam
In-Reply-To: <51323a6b-4953-7aeb-93e5-341d9cc89b11@stura.uni-heidelberg.de>
References: <51323a6b-4953-7aeb-93e5-341d9cc89b11@stura.uni-heidelberg.de>
Message-ID: <e08b114f-265a-0088-0451-6c07fe67b1db@stura.uni-heidelberg.de>

Oh my, sorry. Got posted a bit late...

I've had success in deleting all of the subscription spam, but currently 
I struggle fighting some bounces from all of these failed addresses. 
I'll come back to you; meanwhile I'd be glad to get hints :)

All the best, Ruediger



Am 31.05.2018 um 16:46 schrieb R?diger Wolf:
> We're currently dealing with some Subscribe Spam. Dealing with it, I 
> encountered a problem I need help with:
>
> I used Mark's scrip list_pending 
> (https://www.msapiro.net/scripts/list_pending) to find out how many 
> Subscriptions we got and which adresses were used. I iterated over all 
> lists I got from list_lists --bare and took just the ones with "type: 
> S". Turns out we got 66608 subscriptions from 66560 different 
> adresses. Luckily, they all match the regex \w*\+\w*@gmail\.com, so I 
> tried to wipe the mess whith another script of Mark, erase 
> (https://www.msapiro.net/scripts/erase).
>
> It works nicely for a bunch of lists, but I don't get why it doesn't 
> work with all of them. Looking more closely I found in 
> /var/lib/mailman/lists/<listname> the pending.pck file the script is 
> operating on.
>
> Does someone have an idea why it might not work for all lists?
>
> Regards, Ruediger
>
> ------------------------------------------------------
> Mailman-Users mailing list Mailman-Users at 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/ruediger%40stura.uni-heidelberg.de


From andrew at hodgson.io  Fri Jun  1 04:47:47 2018
From: andrew at hodgson.io (Andrew Hodgson)
Date: Fri, 1 Jun 2018 08:47:47 +0000
Subject: [Mailman-Users] Mailman3 domain aliases
Message-ID: <AM6PR08MB3351EBA2B04F942FD1F40E64AF620@AM6PR08MB3351.eurprd08.prod.outlook.com>

Hi,

I want to create some lists in Mailman3 which can be accessed via web and email with 2 different domains.  There will of course be a default domain which Mailman uses on outgoing emails etc, but I want users to be able to use either the old or new domain to access the website or sending email.

Is this possible in Mailman3?  it is essentially giving me the behaviour I have in Mailman2.

I will be hosting other domains as separate virtual hosts in Mailman3 as well so any changes I have to make to get this to work need to not brake the new virtual host functionality.

Thanks.
Andrew.

From mark at msapiro.net  Fri Jun  1 21:53:15 2018
From: mark at msapiro.net (Mark Sapiro)
Date: Fri, 1 Jun 2018 18:53:15 -0700
Subject: [Mailman-Users] Mailman3 domain aliases
In-Reply-To: <AM6PR08MB3351EBA2B04F942FD1F40E64AF620@AM6PR08MB3351.eurprd08.prod.outlook.com>
References: <AM6PR08MB3351EBA2B04F942FD1F40E64AF620@AM6PR08MB3351.eurprd08.prod.outlook.com>
Message-ID: <77b52e82-8b50-a0c2-59a4-c8fa2298a9ea@msapiro.net>

On 06/01/2018 01:47 AM, Andrew Hodgson wrote:
> Hi,
> 
> I want to create some lists in Mailman3 which can be accessed via web and email with 2 different domains.  There will of course be a default domain which Mailman uses on outgoing emails etc, but I want users to be able to use either the old or new domain to access the website or sending email.
> 
> Is this possible in Mailman3?  it is essentially giving me the behaviour I have in Mailman2.


It's more complicated in Mailman 3 because the domain is part of the
list name. You have some of the same controls such as
require_explicit_destination and acceptable_aliases which can be used to
allow mail to list at domain1 to accept mail addressed To: list at domain2,
but even if you get the incoming MTA to deliver the list at domain2 mail to
Mailman, Mailman's incoming LMTP server that receives the mail will not
know that mail with envelope to list at domain2 is destined for the
list at domain1 list so you not only have to get the incoming MTA to
deliver the mail to Mailman, it also has to rewrite the envelope to
list at domain1.

-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan

From futatuki at poem.co.jp  Sat Jun  2 02:14:01 2018
From: futatuki at poem.co.jp (Yasuhito FUTATSUKI)
Date: Sat, 2 Jun 2018 15:14:01 +0900
Subject: [Mailman-Users] "Freezing" mailing list
In-Reply-To: <20180529.232007.1988814293118828690.t-ishii@sraoss.co.jp>
References: <20180529.232007.1988814293118828690.t-ishii@sraoss.co.jp>
Message-ID: <3d48f0fe-63d0-eeaf-0812-4f71f9851c8c@poem.co.jp>

Hi,

Though already it has been resolved, JFYI.

On 05/29/18 23:20, Tatsuo Ishii wrote:
> I would like to "freeze" an existing mailing list: I want to keep the
> mailing list but I want no one newly subscribe the list.

I've implemented new list's subscribe_policy 'forbid' for this purpose.
https://code.launchpad.net/~futatuki/mailman/2.1-forbid-subscription

(patch against latest mailman:
https://mm.poem.co.jp/mailman-jp/forbid-subscription-r1762-patch.txt )

With 'forbid' subscribe_policy,
* it hide subscription form on list's listinfo page (by using new
   template listinfo_nosubscribe.html).
* it reject all subscription request from users via Web UI and via email.
* following operations are still allowed, inspite of ban_lists rule
   to prevent any email address to subscribe doesn't allow them.
     - changing email address of users already subscribing both by users
       themselves operations and by list owners.
     - adding new member via operations by list owner or site owner.

On the other hand, the things to be worse,
* this breakes translations of some conpicious message by modification.
   (this is one reason why this modification won't be merged into
    upstream)
* it also is needed to prepare new translated template for listinfo
   page without subscription form, for all languages used by lists
   (otherwise, fall back to English template if 'forbid' policy is
   choosed)
* new value for subscribe_policy 4 as 'forbid' may conflict with
   future release of mailman 2.1 and already this value is
   incompatible with current version. (to migrate list config data
   file from modified version to upstream, make sure its
   subscribe_policy should be other than 'forbid')

-- 
Yasuhito FUTATSUKI <futatuki at poem.co.jp>

From ishii at sraoss.co.jp  Sat Jun  2 04:21:19 2018
From: ishii at sraoss.co.jp (Tatsuo Ishii)
Date: Sat, 02 Jun 2018 17:21:19 +0900 (JST)
Subject: [Mailman-Users] "Freezing" mailing list
In-Reply-To: <3d48f0fe-63d0-eeaf-0812-4f71f9851c8c@poem.co.jp>
References: <20180529.232007.1988814293118828690.t-ishii@sraoss.co.jp>
 <3d48f0fe-63d0-eeaf-0812-4f71f9851c8c@poem.co.jp>
Message-ID: <20180602.172119.1583615921359757816.t-ishii@sraoss.co.jp>

> Hi,
> 
> Though already it has been resolved, JFYI.
> 
> On 05/29/18 23:20, Tatsuo Ishii wrote:
>> I would like to "freeze" an existing mailing list: I want to keep the
>> mailing list but I want no one newly subscribe the list.
> 
> I've implemented new list's subscribe_policy 'forbid' for this
> purpose.
> https://code.launchpad.net/~futatuki/mailman/2.1-forbid-subscription
> 
> (patch against latest mailman:
> https://mm.poem.co.jp/mailman-jp/forbid-subscription-r1762-patch.txt )

Thank you for letting know me your work. I myself is not a mailman
admin but I will forward this to our admin so that he could think
about employig the patch.

Best regards,
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese:http://www.sraoss.co.jp

From dandrews at visi.com  Sat Jun  2 21:55:16 2018
From: dandrews at visi.com (David Andrews)
Date: Sat, 02 Jun 2018 20:55:16 -0500
Subject: [Mailman-Users] Spam Subscriptions
In-Reply-To: <8f5c2153-4f29-35a2-8c4d-91dfb58fd83c@msapiro.net>
References: <auto-000099162678@mailfront2.g2host.com>
 <8f5c2153-4f29-35a2-8c4d-91dfb58fd83c@msapiro.net>
Message-ID: <auto-000104810660@mailfront2.g2host.com>

A couple months ago I asked a question and got a 
response from Mark Sapiro, see below. We are 
having trouble implementing anything. We are 
trying recaptcha, but it isn't popular with our 
users, thousands of whom are blind. Here is what my Linux guy asks:

Does anyone have any solution for dealing with spam subscriptions from gmail
addresses?
The requests are coming from random addresses that contain a few words, a
plus sign, then another random string of characters. I can't figure out how
we block this without blocking all addresses with plus characters in them,
which is not a good option.
We are getting hundreds of held subscription messages per day. Is blocking
this kind of thing through Exim an option? We are using cpanel.


p.s. The number of messages is causing my ISP to throttle my e-mail!

Dave


At 01:50 PM 2/23/2018, Mark Sapiro wrote:
>On 02/23/2018 07:07 AM, David Andrews wrote: > > 
>I have just two lists that receive a bunch of 
>spam subscribes each day > -- hundreds of them, 
>in fact. For some reason -- which is good, they 
>are > held, so don't go through, not quite sure 
>why.?  Two questions -- first > is there a file 
>I can erase for each list that will get rid of 
>all the > held subscriptions, without breaking 
>anything else.?  I tried once, and > my 
>installation broke -- don't know if it is 
>related, but don't want to > try again unless I 
>do it right. See the script at 
><https://www.msapiro.net/scripts/erase> 
>(mirrored at 
><https://fog.ccsf.edu/~msapiro/scripts/erase>). 
>This will remove everything for an address or 
>addresses that match a regexp. Also for any list 
>you can remove the lists/LISTNAME/request.pck 
>file, but if there are any held messages for the 
>list, they too will disappear from the pending 
>requests although the 
>data/heldmsg-LISTNAME-nnn.pck file will still be 
>there. The best thing is to handle all held 
>messages before removing the requests.pck file, 
>but there is a script at 
><https://www.msapiro.net/scripts/hold_again> 
>(mirrored as above) that can reprocess the 
>data/heldmsg-LISTNAME-nnn.pck files or they can 
>be removed if not wanted. > Secondly, there is 
>some commonality in the subscribe addresses, 
>are > there strings I can use to discard the 
>subscribes so I never have to see > them. > > 
>Below are examples, there is a common word, or a 
>common word, a period > ., and another common 
>word, then a plus sign + then a 4 5 or 6 
>character > word, all alpha, and @gmail.com > 
>Here are examples: > > > dragonommz+ > 
>jwmidnight+ > nommz.naidoo+ Since Mailman 2.1.21 
>there is a GLOBAL_BAN_LIST. See 
><https://mail.python.org/pipermail/mailman-users/2018-January/082905.html> 
>for a bit on how to use this. You will find more 
>in the archives from this Google search 
><https://www.google.com/search?q=site%3Amail.python.org+inurl%3Amailman-users+%22global_ban_list%22> 
>Also, if you haven't done so, set 
>SUBSCRIBE_FORM_SECRET to some string unique to 
>your site. Both the above are mm_cfg.py 
>settings. Also, I don't know when cPanel will 
>upgrade to Mailman 2.1.26 but it contains an 
>ability to enable reCAPTCHA on the listinfo page 
>subscribe form. > Finally, I know it is probably 
>too late in the Mailman2 cycle to get a > new 
>feature, but in the web UI, it would be nice if 
>you could delete all > deferred 
>subscriptions.?  You can do so with deferred 
>messages, that are > held, but not 
>subscriptions. If someone wants to do it, I'd 
>accept a merge request, but I'm not likely to do 
>it myself -- Mark Sapiro 
><mark at msapiro.net>        The highway is for 
>gamblers, San Francisco Bay Area, 
>California    better use your sense - B. Dylan 
>------------------------------------------------------ 
>Mailman-Users mailing list 
>Mailman-Users at 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/dandrews%40visi.com


---
This email has been checked for viruses by AVG.
https://www.avg.com


From mark at msapiro.net  Sat Jun  2 23:29:04 2018
From: mark at msapiro.net (Mark Sapiro)
Date: Sat, 2 Jun 2018 20:29:04 -0700
Subject: [Mailman-Users] Spam Subscriptions
In-Reply-To: <auto-000104810660@mailfront2.g2host.com>
References: <auto-000099162678@mailfront2.g2host.com>
 <8f5c2153-4f29-35a2-8c4d-91dfb58fd83c@msapiro.net>
 <auto-000104810660@mailfront2.g2host.com>
Message-ID: <3f1929b0-40dd-517e-e088-917d0f395ffb@msapiro.net>

On 06/02/2018 06:55 PM, David Andrews wrote:
> 
> Does anyone have any solution for dealing with spam subscriptions from
> gmail
> addresses?
> The requests are coming from random addresses that contain a few words, a
> plus sign, then another random string of characters.


I use this regexp in the GLOBAL_BAN_LIST

^[0-9a-z.]{8,}\+[0-9a-z]{4,}@gmail\.com$

That blocks subscribe attempts from any address which is 8 or more
letters, digits and periods followed by a plus followed by 4 or more
letters and digits @gmail.com.

Recently, I've seen some with only 6 letters before the + so you might
reduce {8,} to {6,}. I think I'll try that too.

I also have

^.*\+.*\d{3,}@

which blocks anything with a + followed by anything ending in 3 or more
digits. Scanning the membership of all the Mailman 2.1 lists @python.org
(over 132K addresses) shows only 10 matches 4 of which were members of
the python-3000 at python.org with addresses .*+python-3000 at .* and the
other 6 were nabble.com or googlegroups.com, so it's very unlikely that
legitimate regular subscribers will match that.

The advantage of the global ban list for this is all the ones I've seen
are web subscribes. This blocks them with a web response and doesn't
send any confirmation email.


> We are getting hundreds of held subscription messages per day. Is blocking
> this kind of thing through Exim an option? We are using cpanel. 


If these as I've seen are all web subscribes, the only thing you could
do in Exim is drop the outgoing confirmation email, but banning them
stops the subscribe attempt before any mail is sent.

-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan

From mark at msapiro.net  Sat Jun  2 23:50:07 2018
From: mark at msapiro.net (Mark Sapiro)
Date: Sat, 2 Jun 2018 20:50:07 -0700
Subject: [Mailman-Users] Spam Subscriptions
In-Reply-To: <3f1929b0-40dd-517e-e088-917d0f395ffb@msapiro.net>
References: <auto-000099162678@mailfront2.g2host.com>
 <8f5c2153-4f29-35a2-8c4d-91dfb58fd83c@msapiro.net>
 <auto-000104810660@mailfront2.g2host.com>
 <3f1929b0-40dd-517e-e088-917d0f395ffb@msapiro.net>
Message-ID: <8e4443d6-f525-22ff-d556-6c54a7292b26@msapiro.net>

I have a different question.

For a few weeks now the Mailman 2.1 lists @python.org have seen a
massive number of web subscribes from addresses @yahoo.com and @aol.com
addresses. The aol.com ones seem to have abated but yahoo.com continues.
They mostly have local parts that look like first and last names and
display names that don't match the local part name. I implemented
reCAPTCHA on the listinfo subscribe forms and that didn't seem to slow
them down. Also, at first at least some of the subscriptions waiting
user confirmation were being confirmed, some by email and some by web.

I have resorted to scraping Mailman's logs with an hourly cron looking
for subscribes and attempts and when it find 4 or more for a single
address, it uses my erase script to remove them.

This seems to slow down on weekends and pick up during the week.

My question is does anyone have a clue as to who might be doing this and
what they are trying to accomplish. As far as I know, even when they've
succeeded in subscribing, they don't try to post.

Are they just script kiddies trying to be noticed or are they actually
trying to accomplish something.

-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan

From dandrews at visi.com  Sun Jun  3 00:14:27 2018
From: dandrews at visi.com (David Andrews)
Date: Sat, 02 Jun 2018 23:14:27 -0500
Subject: [Mailman-Users] Spam Subscriptions
In-Reply-To: <3f1929b0-40dd-517e-e088-917d0f395ffb@msapiro.net>
References: <auto-000099162678@mailfront2.g2host.com>
 <8f5c2153-4f29-35a2-8c4d-91dfb58fd83c@msapiro.net>
 <auto-000104810660@mailfront2.g2host.com>
 <3f1929b0-40dd-517e-e088-917d0f395ffb@msapiro.net>
Message-ID: <auto-000104812091@mailfront2.g2host.com>

At 10:29 PM 6/2/2018, Mark Sapiro wrote:
>On 06/02/2018 06:55 PM, David Andrews wrote:
> >
> > Does anyone have any solution for dealing with spam subscriptions from
> > gmail
> > addresses?
> > The requests are coming from random addresses that contain a few words, a
> > plus sign, then another random string of characters.
>
>
>I use this regexp in the GLOBAL_BAN_LIST
>
>^[0-9a-z.]{8,}\+[0-9a-z]{4,}@gmail\.com$
>
>That blocks subscribe attempts from any address which is 8 or more
>letters, digits and periods followed by a plus followed by 4 or more
>letters and digits @gmail.com.
>
>Recently, I've seen some with only 6 letters before the + so you might
>reduce {8,} to {6,}. I think I'll try that too.
>
>I also have
>
>^.*\+.*\d{3,}@
>
>which blocks anything with a + followed by anything ending in 3 or more
>digits. Scanning the membership of all the Mailman 2.1 lists @python.org
>(over 132K addresses) shows only 10 matches 4 of which were members of
>the python-3000 at python.org with addresses .*+python-3000 at .* and the
>other 6 were nabble.com or googlegroups.com, so it's very unlikely that
>legitimate regular subscribers will match that.
>
>The advantage of the global ban list for this is all the ones I've seen
>are web subscribes. This blocks them with a web response and doesn't
>send any confirmation email.
>

Thanks very much -- we are trying it!

You always have the answer -- thanks!

Dave



> > We are getting hundreds of held subscription messages per day. Is blocking
> > this kind of thing through Exim an option? We are using cpanel.
>
>
>If these as I've seen are all web subscribes, the only thing you could
>do in Exim is drop the outgoing confirmation email, but banning them
>stops the subscribe attempt before any mail is sent.


---
This email has been checked for viruses by AVG.
https://www.avg.com


From jimpop at domainmail.org  Sun Jun  3 00:08:07 2018
From: jimpop at domainmail.org (Jim Popovitch)
Date: Sun, 03 Jun 2018 00:08:07 -0400
Subject: [Mailman-Users] Spam Subscriptions
In-Reply-To: <8e4443d6-f525-22ff-d556-6c54a7292b26@msapiro.net>
References: <auto-000099162678@mailfront2.g2host.com>
 <8f5c2153-4f29-35a2-8c4d-91dfb58fd83c@msapiro.net>
 <auto-000104810660@mailfront2.g2host.com>
 <3f1929b0-40dd-517e-e088-917d0f395ffb@msapiro.net>
 <8e4443d6-f525-22ff-d556-6c54a7292b26@msapiro.net>
Message-ID: <1527998887.1292.1.camel@domainmail.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On Sat, 2018-06-02 at 20:50 -0700, Mark Sapiro wrote:
> Are they just script kiddies trying to be noticed or are they
> actually trying to accomplish something.

I don't think they know what potential they have, but they know there
has to be something worth building a collection for.  I'm fairly
confident that they've achieved some level of non-moderated
subscriptions on some lists, the question is what do they intend to do
with that megaphone.

- -Jim P.
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEPxwe8uYBnqxkbORSJxVetMRaJwUFAlsTaagACgkQJxVetMRa
JwUguA/8DdKmlfjve8q8I7RyAUq3c2FwHfmsrn4iph7cdjs+kek/6dI5Vi59A11n
ctvkbZkzCBrLwJH1T2nSZkeQ0jNbVcScCX4Iy8nscjUhU+k7Rq4E46kZbkzIzCVl
nCzhi4HEgiDv3wFCxNThBFYBxJPH8yiHIaIne4B324Q62ZordzR2KRKkoOGefU/w
wtCmUlLujvyeW1QGbBxQO5b5B9hwCwsu9izqtsS0evu+fV9uNF74Eu9J/XT82dQR
qRc+g3pDTdwMo71HLMxsY5mrZ1ZRBe0z4sSN2baDe3mr4yy2X+ebNZbPms4g7GaA
TV9vmxWDV4+SPlHLXfauD21ByTGC98GeNMaOOHsaBLiZ9CGQ41GtAsSzuR7xqmqb
PzPx/tui8bXvL+Yt6GXZq9qLBcQVeQxO3OSoYrsJt8I0+XNqtU8z/UzEoaEoqxrF
ZFXypa/+bPavINNW5h4jSCAvtT+QJso501N4HzGG/pGbWvI8+6Q80nXFB5PqFrCp
NNEAAfZmNZtsqm4nMYG65lcsmB2d3t/KpLWz9yB3y2uZWZUD0Hh/2Tet8zIrfMCT
p7sigLH0gbjaCR5dcsXoyiQoXQAraubG/D/LJ5yEhrBIuM4QLllAbqUwnqLkFu+A
S/TLW0uext7nL1HnhzRa4w/MXwme8LRF31UoDsh1hdIxiRjAYA0=
=YSGk
-----END PGP SIGNATURE-----


From enseikou at gmail.com  Sun Jun  3 02:53:13 2018
From: enseikou at gmail.com (=?UTF-8?Q?Rub=c3=a9n_Fern=c3=a1ndez_Asensio?=)
Date: Sun, 3 Jun 2018 08:53:13 +0200
Subject: [Mailman-Users] Cascading lists
Message-ID: <7aa0be49-9cae-d97a-7937-0dd11ebd9ee3@gmail.com>

Hello all,
I'm a new list administrator and a bit lost among Mailman's many 
features. Could you please give some advice?
I'm trying to implement an announcement list and an unmoderated 
discussion list, and having the second receive all mail sent to the 
first one. The announcement list will prevent everybody but a few 
addresses to post, and will attach a personalized footer to every post 
with a link to the subscriber's option page. The discussion list will 
attach its own generalized footer.
In sum, I want a single place to manage permissions to send 
announcements to both lists. I don't care about duplicates, as I want 
people to actively unsubscribe from the announcement list if they've 
joined both by mistake. However, it would be nice if the announcements 
received by the discussion list wouldn't have any personalized footer. 
Also, I want subscribers of the discussion list to be able to send 
replies to the announcement into the discussion list itself, whereas 
subscribers of the announcement list will get their own 'Reply-to' heading.
What's the best setup to achieve this? Umbrella lists, sibling lists, or 
something else?

Thanks in advance,
Rub?n Fern?ndez

From suporte at aprendendolinux.com  Sun Jun  3 12:52:17 2018
From: suporte at aprendendolinux.com (Henrique Fagundes)
Date: Sun, 3 Jun 2018 13:52:17 -0300
Subject: [Mailman-Users] Fail2ban on the Mailman web interface
Message-ID: <24b57bb9-91ce-0a49-9d19-00619a9967ee@aprendendolinux.com>

Dear Colleagues,

Good afternoon!

I begin by apologizing for the fact that this text is difficult to 
interpret because I am Brazilian and I do not have many English language 
skills.

I'm having a hard time using Fail2Ban along with MailMan mailing list 
management software.

My idea is that when the attacker / attacker incorrectly enters the 
password of the login field in the web interface, it is blocked. But for 
this to work, it is necessary for MailMan to report unsuccessful login 
attempts in its log.

I have already checked to see if there is a plugin or extension (just 
like it exists for Wordpress and PHPMyAdmin), but it seems like there is 
nothing developed for this.

So I would like to know if anyone has ever had the need to do this 
implementation, so I can have some way.

If anyone can help me, I will be very grateful.

Regards,

Henrique Fagundes
Linux Support Analyst
suporte at aprendendolinux.com
Skype: magnata-br-rj
Linux User: 475399

https://www.aprendendolinux.com
https://www.facebook.com/AprendendoLinux
https://youtube.com/AprendendoLinux
https://twitter.com/AprendendoLinux
https://telegram.me/AprendendoLinux
______________________________________________________________________
Join the Learning Linux Group
https://listas.aprendendolinux.com/listinfo/aprendendolinux

Or send an email to:
aprendendolinux-subscribe at listas.aprendendolinux.com

BRASIL acima de tudo, DEUS acima de todos!


From gtaylor at tnetconsulting.net  Sun Jun  3 12:53:39 2018
From: gtaylor at tnetconsulting.net (Grant Taylor)
Date: Sun, 3 Jun 2018 10:53:39 -0600
Subject: [Mailman-Users] Spam Subscriptions
In-Reply-To: <3f1929b0-40dd-517e-e088-917d0f395ffb@msapiro.net>
References: <auto-000099162678@mailfront2.g2host.com>
 <8f5c2153-4f29-35a2-8c4d-91dfb58fd83c@msapiro.net>
 <auto-000104810660@mailfront2.g2host.com>
 <3f1929b0-40dd-517e-e088-917d0f395ffb@msapiro.net>
Message-ID: <1ca36e73-b064-eb90-1a9b-60af756624e1@spamtrap.tnetconsulting.net>

On 06/02/2018 09:29 PM, Mark Sapiro wrote:
> I use this regexp in the GLOBAL_BAN_LIST
> 
> ^[0-9a-z.]{8,}\+[0-9a-z]{4,}@gmail\.com$

Are you not looking for capital letters?

I can see how the period in the first class would work, but I don't see 
that in the second class.

What am I missing?



-- 
Grant. . . .
unix || die

From jimpop at domainmail.org  Sun Jun  3 13:04:02 2018
From: jimpop at domainmail.org (Jim Popovitch)
Date: Sun, 03 Jun 2018 13:04:02 -0400
Subject: [Mailman-Users] Fail2ban on the Mailman web interface
In-Reply-To: <24b57bb9-91ce-0a49-9d19-00619a9967ee@aprendendolinux.com>
References: <24b57bb9-91ce-0a49-9d19-00619a9967ee@aprendendolinux.com>
Message-ID: <1528045442.1331.3.camel@domainmail.org>

On Sun, 2018-06-03 at 13:52 -0300, Henrique Fagundes wrote:
> Dear Colleagues,
> 
> Good afternoon!
> 
> I begin by apologizing for the fact that this text is difficult to?
> interpret because I am Brazilian and I do not have many English
> language?
> skills.
> 
> I'm having a hard time using Fail2Ban along with MailMan mailing
> list?
> management software.
> 
> My idea is that when the attacker / attacker incorrectly enters the?
> password of the login field in the web interface, it is blocked. But
> for?
> this to work, it is necessary for MailMan to report unsuccessful
> login?
> attempts in its log.
> 
> I have already checked to see if there is a plugin or extension
> (just?
> like it exists for Wordpress and PHPMyAdmin), but it seems like there
> is?
> nothing developed for this.
> 
> So I would like to know if anyone has ever had the need to do this?
> implementation, so I can have some way.
> 
> If anyone can help me, I will be very grateful.

Hello,

I use the attached patch for Mailman/Utils.py to log the listname and
remoteIP to the mischief log.

Mark, if you think this should be in the regular release let me know
and I'll submit a merge request.

-Jim P.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: 1498_1497.diff
Type: text/x-patch
Size: 810 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/mailman-users/attachments/20180603/daea5abf/attachment.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part
URL: <http://mail.python.org/pipermail/mailman-users/attachments/20180603/daea5abf/attachment.sig>

From suporte at aprendendolinux.com  Sun Jun  3 13:44:17 2018
From: suporte at aprendendolinux.com (Henrique Fagundes)
Date: Sun, 3 Jun 2018 14:44:17 -0300
Subject: [Mailman-Users] Fail2ban on the Mailman web interface
In-Reply-To: <1528045442.1331.3.camel@domainmail.org>
References: <24b57bb9-91ce-0a49-9d19-00619a9967ee@aprendendolinux.com>
 <1528045442.1331.3.camel@domainmail.org>
Message-ID: <08d0e462-6676-ff37-a3ed-414afeb9c070@aprendendolinux.com>

Dear,

Where should I put this file?
First I put it in "/ etc / mailman", and it did not work.

Then I tried to add the contents of it to the file 
"/usr/lib/mailman/Mailman/Utils.py" also did not work.

I use Mailman in version 2.1.23, installed in Debian 9 through "apt-get".

I'll be grateful if you can help.

Atenciosamente,

Henrique Fagundes
Analista de Suporte Linux
suporte at aprendendolinux.com
Skype: magnata-br-rj
Linux User: 475399

https://www.aprendendolinux.com
https://www.facebook.com/AprendendoLinux
https://youtube.com/AprendendoLinux
https://twitter.com/AprendendoLinux
https://telegram.me/AprendendoLinux
______________________________________________________________________
Participe do Grupo Aprendendo Linux
https://listas.aprendendolinux.com/listinfo/aprendendolinux

Ou envie um e-mail para:
aprendendolinux-subscribe at listas.aprendendolinux.com

BRASIL acima de tudo, DEUS acima de todos!

Em 03/06/2018 14:04, Jim Popovitch via Mailman-Users escreveu:
> On Sun, 2018-06-03 at 13:52 -0300, Henrique Fagundes wrote:
>> Dear Colleagues,
>>
>> Good afternoon!
>>
>> I begin by apologizing for the fact that this text is difficult to
>> interpret because I am Brazilian and I do not have many English
>> language
>> skills.
>>
>> I'm having a hard time using Fail2Ban along with MailMan mailing
>> list
>> management software.
>>
>> My idea is that when the attacker / attacker incorrectly enters the
>> password of the login field in the web interface, it is blocked. But
>> for
>> this to work, it is necessary for MailMan to report unsuccessful
>> login
>> attempts in its log.
>>
>> I have already checked to see if there is a plugin or extension
>> (just
>> like it exists for Wordpress and PHPMyAdmin), but it seems like there
>> is
>> nothing developed for this.
>>
>> So I would like to know if anyone has ever had the need to do this
>> implementation, so I can have some way.
>>
>> If anyone can help me, I will be very grateful.
> 
> Hello,
> 
> I use the attached patch for Mailman/Utils.py to log the listname and
> remoteIP to the mischief log.
> 
> Mark, if you think this should be in the regular release let me know
> and I'll submit a merge request.
> 
> -Jim P.
> 
> 
> 
> ------------------------------------------------------
> Mailman-Users mailing list Mailman-Users at 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/suporte%40aprendendolinux.com
> 


From jimpop at domainmail.org  Sun Jun  3 14:00:15 2018
From: jimpop at domainmail.org (Jim Popovitch)
Date: Sun, 03 Jun 2018 18:00:15 +0000
Subject: [Mailman-Users] Fail2ban on the Mailman web interface
In-Reply-To: <08d0e462-6676-ff37-a3ed-414afeb9c070@aprendendolinux.com>
References: <24b57bb9-91ce-0a49-9d19-00619a9967ee@aprendendolinux.com>
 <1528045442.1331.3.camel@domainmail.org>
 <08d0e462-6676-ff37-a3ed-414afeb9c070@aprendendolinux.com>
Message-ID: <E27BD20A-4CE5-4A2B-8E44-028B2427AD42@domainmail.org>

On June 3, 2018 5:44:17 PM UTC, Henrique Fagundes <suporte at aprendendolinux.com> wrote:
>Dear,
>
>Where should I put this file?
>First I put it in "/ etc / mailman", and it did not work.
>

It's intended to be an example of modifications that can be made to Utils.py in order to get better logging.  If you look in the mischief log there should already be some errors related to failures.   I don't use fail2ban, but there should be examples in /etc/fail2ban/scripts.d (I think that's the dir) that you can modify to process /car/log/mailman/mischief.

-Jim P.

From mark at msapiro.net  Sun Jun  3 18:11:49 2018
From: mark at msapiro.net (Mark Sapiro)
Date: Sun, 3 Jun 2018 15:11:49 -0700
Subject: [Mailman-Users] Spam Subscriptions
In-Reply-To: <1ca36e73-b064-eb90-1a9b-60af756624e1@spamtrap.tnetconsulting.net>
References: <auto-000099162678@mailfront2.g2host.com>
 <8f5c2153-4f29-35a2-8c4d-91dfb58fd83c@msapiro.net>
 <auto-000104810660@mailfront2.g2host.com>
 <3f1929b0-40dd-517e-e088-917d0f395ffb@msapiro.net>
 <1ca36e73-b064-eb90-1a9b-60af756624e1@spamtrap.tnetconsulting.net>
Message-ID: <748fdfec-5588-2410-5323-d67378ffacb5@msapiro.net>

On 06/03/2018 09:53 AM, Grant Taylor via Mailman-Users wrote:
> On 06/02/2018 09:29 PM, Mark Sapiro wrote:
>> I use this regexp in the GLOBAL_BAN_LIST
>>
>> ^[0-9a-z.]{8,}\+[0-9a-z]{4,}@gmail\.com$
> 
> Are you not looking for capital letters?


Ban list regexps are case insensitive.


> I can see how the period in the first class would work, but I don't see
> that in the second class.
> 
> What am I missing?


The fact that the ones I saw never had periods following the plus sign.

-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan

From mark at msapiro.net  Sun Jun  3 18:53:09 2018
From: mark at msapiro.net (Mark Sapiro)
Date: Sun, 3 Jun 2018 15:53:09 -0700
Subject: [Mailman-Users] Fail2ban on the Mailman web interface
In-Reply-To: <24b57bb9-91ce-0a49-9d19-00619a9967ee@aprendendolinux.com>
References: <24b57bb9-91ce-0a49-9d19-00619a9967ee@aprendendolinux.com>
Message-ID: <ec10890b-ce09-4b47-06f2-80b9179d2091@msapiro.net>

On 06/03/2018 09:52 AM, Henrique Fagundes wrote:
> 
> My idea is that when the attacker / attacker incorrectly enters the
> password of the login field in the web interface, it is blocked. But for
> this to work, it is necessary for MailMan to report unsuccessful login
> attempts in its log.


Mailman reports all authentication failures to the web server with a 401
status. Here are some typical messages from the Apache access log.

45.24.217.241 - - [03/Jun/2018:15:41:23 -0700] "POST
/mailman/options/LISTNAME HTTP/1.1" 401 4532
"https://www.example.com/mailman/options/LISTNAME" "Mozilla/5.0 (X11;
Ubuntu; Linux x86_64; rv:60.0) Gecko/20100101 Firefox/60.0"

45.24.217.241 - - [03/Jun/2018:15:40:46 -0700] "POST
/mailman/admindb/LISTNAME HTTP/1.1" 401 2715
"https://www.example.com/mailman/admindb/LISTNAME" "Mozilla/5.0 (X11;
Ubuntu; Linux x86_64; rv:60.0) Gecko/20100101 Firefox/60.0"

You should be able to recognize those with fail2ban without any
modification to Mailman's logging.

-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan

From mark at mailmanlists.net  Sun Jun  3 19:28:31 2018
From: mark at mailmanlists.net (Mark Dale)
Date: Mon, 4 Jun 2018 09:28:31 +1000
Subject: [Mailman-Users] Spam Subscriptions
In-Reply-To: <3f1929b0-40dd-517e-e088-917d0f395ffb@msapiro.net>
References: <auto-000099162678@mailfront2.g2host.com>
 <8f5c2153-4f29-35a2-8c4d-91dfb58fd83c@msapiro.net>
 <auto-000104810660@mailfront2.g2host.com>
 <3f1929b0-40dd-517e-e088-917d0f395ffb@msapiro.net>
Message-ID: <20180603232831.rhvi4w7wkvlox4km@mailmanlists.net>


> I use this regexp in the GLOBAL_BAN_LIST
> 
> ^[0-9a-z.]{8,}\+[0-9a-z]{4,}@gmail\.com$

I'm getting errors with the above however it seems to do the job 
if I enclose it in quotes and remove the trailing $ - like so:

GLOBAL_BAN_LIST = ['^[0-9a-z.]{6,}\+[0-9a-z]{4,}@gmail\.com']

Am I missing something?

Cheers,
Mark

From mark at msapiro.net  Sun Jun  3 20:19:33 2018
From: mark at msapiro.net (Mark Sapiro)
Date: Sun, 3 Jun 2018 17:19:33 -0700
Subject: [Mailman-Users] Spam Subscriptions
In-Reply-To: <20180603232831.rhvi4w7wkvlox4km@mailmanlists.net>
References: <auto-000099162678@mailfront2.g2host.com>
 <8f5c2153-4f29-35a2-8c4d-91dfb58fd83c@msapiro.net>
 <auto-000104810660@mailfront2.g2host.com>
 <3f1929b0-40dd-517e-e088-917d0f395ffb@msapiro.net>
 <20180603232831.rhvi4w7wkvlox4km@mailmanlists.net>
Message-ID: <73fb1203-a717-53fe-fa56-26b1b76fb89b@msapiro.net>

On 06/03/2018 04:28 PM, Mark Dale wrote:
> 
>> I use this regexp in the GLOBAL_BAN_LIST
>>
>> ^[0-9a-z.]{8,}\+[0-9a-z]{4,}@gmail\.com$
> 
> I'm getting errors with the above however it seems to do the job 
> if I enclose it in quotes and remove the trailing $ - like so:
> 
> GLOBAL_BAN_LIST = ['^[0-9a-z.]{6,}\+[0-9a-z]{4,}@gmail\.com']


What you have done is correct. I don't know why you would have needed to
remove the '$'. Did you get an error and if so, what?.

The regexp I gave was just intended to be an example regexp. The
BAN_LIST is actually a list of strings so regexps in the BAN_LIST have
to be quoted and enclosed in [] and comma separated if more than one.

Also, it doesn't matter in this case because \+ and \. are not
meaningful string metacharacters, but it never hurts to define them as
raw strings like, e.g.,

GLOBAL_BAN_LIST = [r'^[0-9a-z.]{8,}\+[0-9a-z]{4,}@gmail\.com$']

-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan

From mark at mailmanlists.net  Sun Jun  3 20:58:39 2018
From: mark at mailmanlists.net (Mark Dale)
Date: Mon, 4 Jun 2018 10:58:39 +1000
Subject: [Mailman-Users] Spam Subscriptions
In-Reply-To: <73fb1203-a717-53fe-fa56-26b1b76fb89b@msapiro.net>
References: <auto-000099162678@mailfront2.g2host.com>
 <8f5c2153-4f29-35a2-8c4d-91dfb58fd83c@msapiro.net>
 <auto-000104810660@mailfront2.g2host.com>
 <3f1929b0-40dd-517e-e088-917d0f395ffb@msapiro.net>
 <20180603232831.rhvi4w7wkvlox4km@mailmanlists.net>
 <73fb1203-a717-53fe-fa56-26b1b76fb89b@msapiro.net>
Message-ID: <20180604005839.5gtsjr4lpvjjuo7x@mailmanlists.net>

> >> ^[0-9a-z.]{8,}\+[0-9a-z]{4,}@gmail\.com$
> > 
> > I'm getting errors with the above however it seems to do the job 
> > if I enclose it in quotes and remove the trailing $ - like so:
> > 
> > GLOBAL_BAN_LIST = ['^[0-9a-z.]{6,}\+[0-9a-z]{4,}@gmail\.com']

-----
 
> What you have done is correct. I don't know why you would have needed to
> remove the '$'. Did you get an error and if so, what?.

I can't see why either, but with the '$' left in place, the 
Mailman Web UI displayed the error "Sorry, we hit a bug..."

-----

> Also, it doesn't matter in this case because \+ and \. are not
> meaningful string metacharacters, but it never hurts to define them as
> raw strings like, e.g.,

Understood. Thanks.
 
> GLOBAL_BAN_LIST = [r'^[0-9a-z.]{8,}\+[0-9a-z]{4,}@gmail\.com$']

The 'r' that precedes the first quote - is that correct?

-----

Cheers.

From gtaylor at tnetconsulting.net  Sun Jun  3 21:41:15 2018
From: gtaylor at tnetconsulting.net (Grant Taylor)
Date: Sun, 3 Jun 2018 19:41:15 -0600
Subject: [Mailman-Users] Spam Subscriptions
In-Reply-To: <748fdfec-5588-2410-5323-d67378ffacb5@msapiro.net>
References: <auto-000099162678@mailfront2.g2host.com>
 <8f5c2153-4f29-35a2-8c4d-91dfb58fd83c@msapiro.net>
 <auto-000104810660@mailfront2.g2host.com>
 <3f1929b0-40dd-517e-e088-917d0f395ffb@msapiro.net>
 <1ca36e73-b064-eb90-1a9b-60af756624e1@spamtrap.tnetconsulting.net>
 <748fdfec-5588-2410-5323-d67378ffacb5@msapiro.net>
Message-ID: <2d51d3f6-7881-a020-e45d-eccfa106ae6d@spamtrap.tnetconsulting.net>

On 06/03/2018 04:11 PM, Mark Sapiro wrote:
> Ban list regexps are case insensitive.

Thank you for the clarification Mark.

> The fact that the ones I saw never had periods following the plus sign.

ACK



-- 
Grant. . . .
unix || die

From mark at msapiro.net  Sun Jun  3 22:01:50 2018
From: mark at msapiro.net (Mark Sapiro)
Date: Sun, 3 Jun 2018 19:01:50 -0700
Subject: [Mailman-Users] Cascading lists
In-Reply-To: <7aa0be49-9cae-d97a-7937-0dd11ebd9ee3@gmail.com>
References: <7aa0be49-9cae-d97a-7937-0dd11ebd9ee3@gmail.com>
Message-ID: <018e1fd5-d3a5-1c2f-ecd6-5c8a16e8c94f@msapiro.net>

On 06/02/2018 11:53 PM, Rub?n Fern?ndez Asensio wrote:
> Hello all,
> I'm a new list administrator and a bit lost among Mailman's many
> features. Could you please give some advice?
> I'm trying to implement an announcement list and an unmoderated
> discussion list, and having the second receive all mail sent to the
> first one. The announcement list will prevent everybody but a few
> addresses to post, and will attach a personalized footer to every post
> with a link to the subscriber's option page. The discussion list will
> attach its own generalized footer.


See this FAQ article for advice on setting up an announcement list
<https://wiki.list.org/x/4030685>.


> In sum, I want a single place to manage permissions to send
> announcements to both lists. I don't care about duplicates, as I want
> people to actively unsubscribe from the announcement list if they've
> joined both by mistake. However, it would be nice if the announcements
> received by the discussion list wouldn't have any personalized footer.


OK.


> Also, I want subscribers of the discussion list to be able to send
> replies to the announcement into the discussion list itself, whereas
> subscribers of the announcement list will get their own 'Reply-to' heading.
> What's the best setup to achieve this? Umbrella lists, sibling lists, or
> something else?


There are pluses and minuses to both umbrella lists and sibling lists.
There are FAQs you should read if you haven't already. They are
<https://wiki.list.org/x/4030574> and <https://wiki.list.org/x/4030540>.

I'm going to assume that neither list will have digest members. That
adds an additional complication.

Your choices are:

1) Add the discussion list address to regular_include_lists of the
announce list. If you do this everyone will get announcement list posts
from the announcement list. These will have the announcement list's
footer. The members of the discussion list who aren't members of the
announce list will get the post from the announce list. It appears that
you want to munge Reply-To: in some way on both lists (I'll refrain from
giving my opinion on this). Here, the message received by the discussion
list members who aren't announce list members will have the footer and
Reply-To: of the announce list. You probably don't want that.

2) Subscribe the discussion list to the announce list. This means
members of either list will receive the posts to the announce list from
their own list with its footer and Reply-To: and members of both lists
will receive the post from both lists. This seems more like what you
want, but there are two kinds of issues.

Issue #1 is acceptance of posts to the announce list by the discussion
list. This is discussed in the FAQ at <https://wiki.list.org/x/4030574>.

Issue #2 is an Umbrella list is a list whose members are all other
lists. Lists with both individuals and one or more lists as members are
an in between configuration that isn't well supported. Your issue is
whether or not to set the announce list as an umbrella list. If you
don't, anyone can request a password reminder and it will be sent to the
entire discussion list. Because of this, you can set the announce list
umbrella_list to Yes. This, at least with default umbrella_member_suffix
will send these to the owner of the discussion list instead, but it also
means that individual members of the announce list can't get password
reminders or subscription confirmation requests.

-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan

From mark at msapiro.net  Sun Jun  3 22:05:23 2018
From: mark at msapiro.net (Mark Sapiro)
Date: Sun, 3 Jun 2018 19:05:23 -0700
Subject: [Mailman-Users] Spam Subscriptions
In-Reply-To: <20180604005839.5gtsjr4lpvjjuo7x@mailmanlists.net>
References: <auto-000099162678@mailfront2.g2host.com>
 <8f5c2153-4f29-35a2-8c4d-91dfb58fd83c@msapiro.net>
 <auto-000104810660@mailfront2.g2host.com>
 <3f1929b0-40dd-517e-e088-917d0f395ffb@msapiro.net>
 <20180603232831.rhvi4w7wkvlox4km@mailmanlists.net>
 <73fb1203-a717-53fe-fa56-26b1b76fb89b@msapiro.net>
 <20180604005839.5gtsjr4lpvjjuo7x@mailmanlists.net>
Message-ID: <ab237d34-dcc6-720d-7e7e-9298fa348e2e@msapiro.net>

On 06/03/2018 05:58 PM, Mark Dale wrote:
> 
> I can't see why either, but with the '$' left in place, the 
> Mailman Web UI displayed the error "Sorry, we hit a bug..."


And what is the error in Mailman's error log.

-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan

From mark at mailmanlists.net  Sun Jun  3 22:48:41 2018
From: mark at mailmanlists.net (Mark Dale)
Date: Mon, 4 Jun 2018 12:48:41 +1000
Subject: [Mailman-Users] Spam Subscriptions
In-Reply-To: <ab237d34-dcc6-720d-7e7e-9298fa348e2e@msapiro.net>
References: <auto-000099162678@mailfront2.g2host.com>
 <8f5c2153-4f29-35a2-8c4d-91dfb58fd83c@msapiro.net>
 <auto-000104810660@mailfront2.g2host.com>
 <3f1929b0-40dd-517e-e088-917d0f395ffb@msapiro.net>
 <20180603232831.rhvi4w7wkvlox4km@mailmanlists.net>
 <73fb1203-a717-53fe-fa56-26b1b76fb89b@msapiro.net>
 <20180604005839.5gtsjr4lpvjjuo7x@mailmanlists.net>
 <ab237d34-dcc6-720d-7e7e-9298fa348e2e@msapiro.net>
Message-ID: <20180604024841.s2yd66jvg2ggmcip@mailmanlists.net>

> And what is the error in Mailman's error log.


GLOBAL_BAN_LIST = ['^[0-9a-z.]{6,}\+[0-9a-z]{4,}@gmail\.com$']

D'oh. My apologies. The error was not from the trailing '$' but 
from not having the quotes in place originally. All is now well 
(with the above).

Thanks,
Mark

2018/06/04 10:33:14 [error] 17956#17956: *4956 FastCGI sent in 
stderr: "[Mailman: low level unrecoverable exception]" while 
reading response header from upstream, client: 68.235.48.108, 
server: mailmanlists.sg, request: "GET /mailman/listinfo 
HTTP/1.1", upstream: 
"fastcgi://unix:///var/run/fcgiwrap.socket:", host: 
"www.mailmanlists.sg"

From turnbull.stephen.fw at u.tsukuba.ac.jp  Mon Jun  4 04:24:38 2018
From: turnbull.stephen.fw at u.tsukuba.ac.jp (Stephen J. Turnbull)
Date: Mon, 4 Jun 2018 17:24:38 +0900
Subject: [Mailman-Users] Spam Subscriptions
In-Reply-To: <20180604024841.s2yd66jvg2ggmcip@mailmanlists.net>
References: <auto-000099162678@mailfront2.g2host.com>
 <8f5c2153-4f29-35a2-8c4d-91dfb58fd83c@msapiro.net>
 <auto-000104810660@mailfront2.g2host.com>
 <3f1929b0-40dd-517e-e088-917d0f395ffb@msapiro.net>
 <20180603232831.rhvi4w7wkvlox4km@mailmanlists.net>
 <73fb1203-a717-53fe-fa56-26b1b76fb89b@msapiro.net>
 <20180604005839.5gtsjr4lpvjjuo7x@mailmanlists.net>
 <ab237d34-dcc6-720d-7e7e-9298fa348e2e@msapiro.net>
 <20180604024841.s2yd66jvg2ggmcip@mailmanlists.net>
Message-ID: <23316.63302.359868.563116@turnbull.sk.tsukuba.ac.jp>

Mark Dale writes:

 > D'oh. My apologies. The error was not from the trailing '$' but 
 > from not having the quotes in place originally. All is now well 
 > (with the above).

No big deal; on the contrary, we really appreciate your report
confirming that the regex works as expected for you, after all.

Thank *you*!

Steve




From suporte at aprendendolinux.com  Mon Jun  4 10:03:52 2018
From: suporte at aprendendolinux.com (Henrique Fagundes)
Date: Mon, 4 Jun 2018 11:03:52 -0300
Subject: [Mailman-Users] Fail2ban on the Mailman web interface
In-Reply-To: <ec10890b-ce09-4b47-06f2-80b9179d2091@msapiro.net>
References: <24b57bb9-91ce-0a49-9d19-00619a9967ee@aprendendolinux.com>
 <ec10890b-ce09-4b47-06f2-80b9179d2091@msapiro.net>
Message-ID: <e4565009-326f-6210-758c-98bc51e4f6d0@aprendendolinux.com>

Thank you friend,

With this, I can configure Fail2Ban to stop the attack.
Block the IP on which you tried to log in without success for more than 
three consecutive times.

Regards,

Henrique Fagundes
suporte at aprendendolinux.com
Skype: magnata-br-rj
Linux User: 475399

https://www.aprendendolinux.com
https://www.facebook.com/AprendendoLinux
https://youtube.com/AprendendoLinux
https://twitter.com/AprendendoLinux
https://telegram.me/AprendendoLinux
______________________________________________________________________
Participe do Grupo Aprendendo Linux
https://listas.aprendendolinux.com/listinfo/aprendendolinux

Ou envie um e-mail para:
aprendendolinux-subscribe at listas.aprendendolinux.com

Em 03/06/2018 19:53, Mark Sapiro escreveu:
> Mailman reports all authentication failures to the web server with a 401
> status. Here are some typical messages from the Apache access log.
> 
> 45.24.217.241 - - [03/Jun/2018:15:41:23 -0700] "POST
> /mailman/options/LISTNAME HTTP/1.1" 401 4532
> "https://www.example.com/mailman/options/LISTNAME"  "Mozilla/5.0 (X11;
> Ubuntu; Linux x86_64; rv:60.0) Gecko/20100101 Firefox/60.0"
> 
> 45.24.217.241 - - [03/Jun/2018:15:40:46 -0700] "POST
> /mailman/admindb/LISTNAME HTTP/1.1" 401 2715
> "https://www.example.com/mailman/admindb/LISTNAME"  "Mozilla/5.0 (X11;
> Ubuntu; Linux x86_64; rv:60.0) Gecko/20100101 Firefox/60.0"
> 
> You should be able to recognize those with fail2ban without any
> modification to Mailman's logging.


From Michael.D.Parker at ga.com  Mon Jun  4 14:47:13 2018
From: Michael.D.Parker at ga.com (Parker, Michael D.)
Date: Mon, 4 Jun 2018 18:47:13 +0000
Subject: [Mailman-Users] Any scripting available for global site admin
Message-ID: <678a3cca4e4f40dfb8fbcba3b4b62025@ASGEXCPWP05.ga.com>

I have mailman 2.x and am specifically interested in knowing how to do the following two tasks:


1.       List all users with all their mailing lists

2.       Globally remove a user from all mailing lists

Thanks.

***** ***** *****
Michael D. Parker - provisional CISSP
General Atomics - ElectroMagnetics Systems Group (EMS)
Michael.d.parker at ga.com<mailto:Michael.d.parker at ga.com>  <<<<< NOTE: Remember to include my middle initial >>>>>

*****************************************************************************************
The information contained in this electronic message is intended only for the use of the individual or entity to
which it is addressed and may contain information that is privileged, confidential and exempt from disclosure
under applicable law. This message may also contain technical data, export of which is restricted by the
International Traffic in Arms Regulations (ITAR). Disclosure to foreign persons without prior U.S. Government
approval is prohibited. Violations of these export laws and regulations are subject to severe civil and criminal
penalties.

This message may include Company Sensitive and/or Proprietary Information.  If the reader
of this message is not the intended recipient, you are informed that any dissemination, copying or disclosure of
the material contained herein, in whole or in part, is strictly prohibited. If you received this message in error,
please notify the sender by reply e-mail and delete all copies of this message.
******************************************************************************************


From jimpop at domainmail.org  Mon Jun  4 15:06:39 2018
From: jimpop at domainmail.org (Jim Popovitch)
Date: Mon, 04 Jun 2018 15:06:39 -0400
Subject: [Mailman-Users] Any scripting available for global site admin
In-Reply-To: <678a3cca4e4f40dfb8fbcba3b4b62025@ASGEXCPWP05.ga.com>
References: <678a3cca4e4f40dfb8fbcba3b4b62025@ASGEXCPWP05.ga.com>
Message-ID: <1528139199.1597.1.camel@domainmail.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On Mon, 2018-06-04 at 18:47 +0000, Parker, Michael D. wrote:
> I have mailman 2.x and am specifically interested in knowing how to
> do the following two tasks:
> 
> 
> 1.???????List all users with all their mailing lists

list_members -h

> 
> 2.???????Globally remove a user from all mailing lists


remove_members -h


- -Jim P.
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEPxwe8uYBnqxkbORSJxVetMRaJwUFAlsVjcAACgkQJxVetMRa
JwXfNA/+JKUTpU6s/Pgw38RVt0gieuymvcfY4F9tQcJTlXbGJmfEL1AYAdZKRWrd
idQ8Ct1g4ZW3C8Xp3t28fXF2xPGxrNpXq7RSCaJWkrYGt4qpR/3W8fHgkXpQy/8V
zYXPk2W+rncbTYY2NyXfQK+OaMNT5bpsQ/ZpInI5rnS48pfFS8dlTahC1bTRqMf3
VVj7IlVFs2VvNznVXOPLI9axyHZECFVlQ5x3/KMi7NWipqHn6JzYqSAWGoUEOrps
dY7eh3DxPkS4yCDMe8RssSCzjDBmJRBdAyrvk9njmhNGRhDRDRPAIrRc8LrFsSJ9
DENmNdNYqUSHuryHNG0YvMRyFxj4QLlyBQaS6F2QBaK1KkYCX8her9y94FVi+dXA
HexGBbEsLIN0j/3pGQcQLXiidZv8BS3O6+pAmoRMeBDE+yC4+sdZiNDE5pF4zSKI
Z9yyrPDe4ZMZa5dVXzbVHc9HSwcAW/9uW7Lftq36G9t1SeypBdRnDbYT5u8bXN2o
0DYNCwriyxKwil/KeSBHaP+aqxloI6Poh07z1Wz8i/WzSCFux/dmVttQgLklu6Ra
Ww5vqj23oDHytr5rERKKCpjNUOC5HwhNO5o6VBktvfj609e1RQlGRs9Tio2ue1ka
wqY18555JQr6lJxCz6je5uF3Wb4N60jAM/pehsIafJpzpCtS3h4=
=mSvT
-----END PGP SIGNATURE-----


From cmupythia at cmu.edu  Mon Jun  4 15:05:54 2018
From: cmupythia at cmu.edu (Gretchen R Beck)
Date: Mon, 4 Jun 2018 19:05:54 +0000
Subject: [Mailman-Users] Any scripting available for global site admin
In-Reply-To: <678a3cca4e4f40dfb8fbcba3b4b62025@ASGEXCPWP05.ga.com>
References: <678a3cca4e4f40dfb8fbcba3b4b62025@ASGEXCPWP05.ga.com>
Message-ID: <d9028b9241ec4ccb9a0ff7f69190b45c@cmu.edu>

Global remove is easy. The bin/remove_members application as a --fromall option

So something like this:

<yourprefix>/bin/remove_members --fromall idtoremove at their.domain


Gretchen Beck

Carnegie Mellon


________________________________
From: Mailman-Users <mailman-users-bounces+cmupythia=cmu.edu at python.org> on behalf of Parker, Michael D. <Michael.D.Parker at ga.com>
Sent: Monday, June 4, 2018 2:47 PM
To: mailman-users at python.org
Subject: [Mailman-Users] Any scripting available for global site admin

I have mailman 2.x and am specifically interested in knowing how to do the following two tasks:


1.       List all users with all their mailing lists

2.       Globally remove a user from all mailing lists

Thanks.

***** ***** *****
Michael D. Parker - provisional CISSP
General Atomics - ElectroMagnetics Systems Group (EMS)
Michael.d.parker at ga.com<mailto:Michael.d.parker at ga.com>  <<<<< NOTE: Remember to include my middle initial >>>>>

*****************************************************************************************
The information contained in this electronic message is intended only for the use of the individual or entity to
which it is addressed and may contain information that is privileged, confidential and exempt from disclosure
under applicable law. This message may also contain technical data, export of which is restricted by the
International Traffic in Arms Regulations (ITAR). Disclosure to foreign persons without prior U.S. Government
approval is prohibited. Violations of these export laws and regulations are subject to severe civil and criminal
penalties.

This message may include Company Sensitive and/or Proprietary Information.  If the reader
of this message is not the intended recipient, you are informed that any dissemination, copying or disclosure of
the material contained herein, in whole or in part, is strictly prohibited. If you received this message in error,
please notify the sender by reply e-mail and delete all copies of this message.
******************************************************************************************

------------------------------------------------------
Mailman-Users mailing list Mailman-Users at 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/cmupythia%40cmu.edu

From rclemings at gmail.com  Mon Jun  4 17:48:53 2018
From: rclemings at gmail.com (Russell Clemings)
Date: Mon, 4 Jun 2018 14:48:53 -0700
Subject: [Mailman-Users] Mailman-Users Digest, Vol 172, Issue 6
In-Reply-To: <mailman.2287.1528076427.2803.mailman-users@python.org>
References: <mailman.2287.1528076427.2803.mailman-users@python.org>
Message-ID: <CAN7RX0aLvOrjfjF9M=Mz_C-CUXRm14mh+MjbC-4hbjzryeJk0Q@mail.gmail.com>

They seem to be changing their tactics pretty much regularly now. Just
tailing the subscribe log I see all of these:

Jun 04 21:28:16 2018 (16689) LISTNAME1: pending Steven Lugo <
support at quickbitcoin.co.uk>  159.203.88.55
Jun 04 21:30:06 2018 (17063) LISTNAME1: pending Steve Asher <
support at bitcoin.com.au>  185.237.98.51
Jun 04 21:30:38 2018 (17503) LISTNAME2: pending Sterling Leng <
support at vaultoro.com>  185.237.98.51
Jun 04 21:31:26 2018 (17651) LISTNAME3: pending Cristina Hibbard <
support at vaultoro.com>  59.152.95.54
Jun 04 21:32:01 2018 (17754) LISTNAME3: pending Kirk Maddox <
support at bitcoin.com.au>  185.237.98.51
Jun 04 21:33:58 2018 (18188) LISTNAME4: pending Jarrod Rand <
support at vaultoro.com>  80.211.240.206
Jun 04 21:36:54 2018 (19212) LISTNAME5: pending Anna Glen <
support at quickbitcoin.co.uk>  159.203.88.55
Jun 04 21:36:59 2018 (19231) LISTNAME1: pending John Savage <
support at bitflyer.com>  39.137.69.9
Jun 04 21:38:21 2018 (19476) LISTNAME4: pending Sarah Adami <
support at coindirect.com>  185.237.98.51




> ---------- Forwarded message ----------
> From: Mark Sapiro <mark at msapiro.net>
> To: mailman-users at python.org
> Cc:
> Bcc:
> Date: Sun, 3 Jun 2018 17:19:33 -0700
> Subject: Re: [Mailman-Users] Spam Subscriptions
> On 06/03/2018 04:28 PM, Mark Dale wrote:
> >
> >> I use this regexp in the GLOBAL_BAN_LIST
> >>
> >> ^[0-9a-z.]{8,}\+[0-9a-z]{4,}@gmail\.com$
> >
> > I'm getting errors with the above however it seems to do the job
> > if I enclose it in quotes and remove the trailing $ - like so:
> >
> > GLOBAL_BAN_LIST = ['^[0-9a-z.]{6,}\+[0-9a-z]{4,}@gmail\.com']
>
>
> What you have done is correct. I don't know why you would have needed to
> remove the '$'. Did you get an error and if so, what?.
>
> The regexp I gave was just intended to be an example regexp. The
> BAN_LIST is actually a list of strings so regexps in the BAN_LIST have
> to be quoted and enclosed in [] and comma separated if more than one.
>
> Also, it doesn't matter in this case because \+ and \. are not
> meaningful string metacharacters, but it never hurts to define them as
> raw strings like, e.g.,
>
> GLOBAL_BAN_LIST = [r'^[0-9a-z.]{8,}\+[0-9a-z]{4,}@gmail\.com$']
>
> --
> Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
> San Francisco Bay Area, California    better use your sense - B. Dylan
>
>

From jimpop at domainmail.org  Mon Jun  4 18:10:57 2018
From: jimpop at domainmail.org (Jim Popovitch)
Date: Mon, 04 Jun 2018 18:10:57 -0400
Subject: [Mailman-Users] Bogus Subscriptions (was: Mailman-Users Digest,
 Vol 172, Issue 6)
In-Reply-To: <CAN7RX0aLvOrjfjF9M=Mz_C-CUXRm14mh+MjbC-4hbjzryeJk0Q@mail.gmail.com>
References: <mailman.2287.1528076427.2803.mailman-users@python.org>
 <CAN7RX0aLvOrjfjF9M=Mz_C-CUXRm14mh+MjbC-4hbjzryeJk0Q@mail.gmail.com>
Message-ID: <1528150257.3295.1.camel@domainmail.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On Mon, 2018-06-04 at 14:48 -0700, Russell Clemings wrote:
> They seem to be changing their tactics pretty much regularly now.
> Just
> tailing the subscribe log I see all of these:
> 
> Jun 04 21:28:16 2018 (16689) LISTNAME1: pending Steven Lugo <
> support at quickbitcoin.co.uk>??159.203.88.55
> Jun 04 21:30:06 2018 (17063) LISTNAME1: pending Steve Asher <
> support at bitcoin.com.au>??185.237.98.51
> Jun 04 21:30:38 2018 (17503) LISTNAME2: pending Sterling Leng <
> support at vaultoro.com>??185.237.98.51
> Jun 04 21:31:26 2018 (17651) LISTNAME3: pending Cristina Hibbard <
> support at vaultoro.com>??59.152.95.54
> Jun 04 21:32:01 2018 (17754) LISTNAME3: pending Kirk Maddox <
> support at bitcoin.com.au>??185.237.98.51
> Jun 04 21:33:58 2018 (18188) LISTNAME4: pending Jarrod Rand <
> support at vaultoro.com>??80.211.240.206
> Jun 04 21:36:54 2018 (19212) LISTNAME5: pending Anna Glen <
> support at quickbitcoin.co.uk>??159.203.88.55
> Jun 04 21:36:59 2018 (19231) LISTNAME1: pending John Savage <
> support at bitflyer.com>??39.137.69.9
> Jun 04 21:38:21 2018 (19476) LISTNAME4: pending Sarah Adami <
> support at coindirect.com>??185.237.98.51
> 

Interesting, I see delimited email addrs for those same domains.

Jun 04 20:57:11 2018 (5670) users: pending James Sturgill <support+qjrr
@quickbitcoin.co.uk>??111.13.56.16
Jun 04 21:19:10 2018 (7469) users: pending John Heninger <support+qwnpn
@bitflyer.com>??152.231.81.122
Jun 04 21:35:52 2018 (8894) users: pending Judith Route <support+xwwrk@
vaultoro.com>??149.202.38.124
Jun 04 21:42:25 2018 (9149) users: pending Donna Watts <support+yvdmgcn
@vaultoro.com>??212.73.137.45
Jun 04 21:49:33 2018 (9323) users: pending Justin Rybij <support+jzmpfp
rm at bitflyer.com>??67.197.233.15

FWIW,

here's the list I've accumulated so far:
alec768+kxqun at gmail.com
alec768+kyccjs at gmail.com
alec768+orfeij at gmail.com
alec768+tmtkl at gmail.com
alexmanalo76+engl at gmail.com
alexmanalo76+hrrfbr at gmail.com
alexmanalo76+nbkdtau at gmail.com
alexmanalo76+vhffieas at gmail.com
alexmanalo76+vlkpqi at gmail.com
alexmanalo76+vnsjpy at gmail.com
alexmanalo76+zasnfp at gmail.com
cybertuna94+cxrp at gmail.com
cybertuna94+gjuhtqwq at gmail.com
cybertuna94+jhitu at gmail.com
cybertuna94+wdlgmeq at gmail.com
cybertuna94+xgosrla at gmail.com
cybertuna94+xkon at gmail.com
desertkaiju+fylzc at gmail.com
desertkaiju+piurldte at gmail.com
desertkaiju+rvkvz at gmail.com
desertkaiju+tajkn at gmail.com
desertkaiju+vwsgneo at gmail.com
desertkaiju+wffbf at gmail.com
desertkaiju+zczm at gmail.com
khongthong94+baduvtj at gmail.com
khongthong94+bhctkgb at gmail.com
khongthong94+veyaqcw at gmail.com
spikedmauler+jlxz at gmail.com
sqrlyjack+hbqlyxc at gmail.com
sqrlyjack+hdhpu at gmail.com
sqrlyjack+nypxw at gmail.com
sqrlyjack+vamjnvg at gmail.com
sqrlyjack+vdfltrta at gmail.com
support+jzmpfprm at bitflyer.com
support+qjrr at quickbitcoin.co.uk
support+qwnpn at bitflyer.com
support+xwwrk at vaultoro.com
support+yvdmgcn at vaultoro.com
tinyowl94+dcjfcsq at gmail.com
tinyowl94+ftmydowx at gmail.com
tinyowl94+kffmkq at gmail.com
tinyowl94+pfayzh at gmail.com
tinyowl94+sdch at gmail.com
tinyowl94+zoqbn at gmail.com
yllwdg+gitvhnt at gmail.com

And these are the IPs:

101.132.136.83
103.35.168.166
110.37.200.83
111.13.56.16
121.10.118.70
138.122.2.7
139.224.24.26
144.76.62.29
149.13.80.46
149.202.38.124
150.109.44.245
152.231.81.122
176.235.99.166
179.180.144.28
181.118.183.153
186.251.102.85
187.106.238.241
187.12.46.218
187.190.221.71
187.245.88.185
188.211.227.149
189.76.93.64
190.12.47.246
190.144.39.34
190.214.1.26
191.0.70.90
193.165.144.66
197.210.216.22
197.255.255.91
200.165.177.66
200.202.229.218
201.10.154.50
201.49.98.58
202.179.186.138
202.179.4.70
202.191.121.171
212.49.84.113
212.73.137.45
218.60.8.99
221.214.208.226
36.67.233.131
67.197.233.15
78.66.102.104
80.122.84.246

- -Jim P.
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEPxwe8uYBnqxkbORSJxVetMRaJwUFAlsVuPIACgkQJxVetMRa
JwX5/g/9FxkduLZPPimqHFxFs61SynPIIslEIUV8JgBNdrJakX4NPiTPfzmta8SZ
+MX10z+yj2SFFcDhJfL0qfoQj7qRHQsShE7hH3KG+bZVVqTpyr5p6JjbA8fiZsiw
q9JcywF3SLDpGDQaMYL0htTFKA70blfhIdzTPxs0HFKN6lAL2C57QDNNHGTtlv0Q
UZC0HQp9YiFrdoIKAxQnp7/h/91MKV8Z6GlkdSPjK20aMDIm9pku49QZ50v1yNtN
+KhMBDAzRYMzSVhPEPpDs5AcziuqiLNm3DmuK0Xbj+OYxH17FYNjREACBua0VNE/
mJ0eza1wfCEUPLfqrQlM37BtkFyWdQdn4QM+2k4uQuV+zdWdxdtiXc54OBAEwbrZ
TcPK4xM02trDIQwUJz8cb7dJD1S2oI3KofnrhNwwF1Dg7FzpnQSCSoseLjWljnvo
uD8th/qww/dVSyxP3abSqDu2VrIxPxYw8Q7Lqrx41Q5h1pfx9MrApkymwxLo+B2t
GIPCdYF1NxH58K3dZkmY/syXWbkPnerT7rNOcwolh0CBiPXD0n7ag23RozAmVh9J
WIrJVR/CPFlX9YoMTfT13+XWvpjH526msYUAK6ER/m5webuV3ltElWG9M0aOSocM
shlPEdYkCTZZXrPpTc290KHIyd20hj3uyT2xkj7AKwlelnLhfwM=
=rw6m
-----END PGP SIGNATURE-----


From jimpop at domainmail.org  Mon Jun  4 18:27:43 2018
From: jimpop at domainmail.org (Jim Popovitch)
Date: Mon, 04 Jun 2018 18:27:43 -0400
Subject: [Mailman-Users] Bogus Subscriptions (was: Mailman-Users Digest,
 Vol 172, Issue 6)
In-Reply-To: <1528150257.3295.1.camel@domainmail.org>
References: <mailman.2287.1528076427.2803.mailman-users@python.org>
 <CAN7RX0aLvOrjfjF9M=Mz_C-CUXRm14mh+MjbC-4hbjzryeJk0Q@mail.gmail.com>
 <1528150257.3295.1.camel@domainmail.org>
Message-ID: <1528151263.3295.3.camel@domainmail.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On Mon, 2018-06-04 at 18:10 -0400, Jim Popovitch wrote:
> On Mon, 2018-06-04 at 14:48 -0700, Russell Clemings wrote:
> > They seem to be changing their tactics pretty much regularly now.
> > Just
> > tailing the subscribe log I see all of these:
> > 
> > Jun 04 21:28:16 2018 (16689) LISTNAME1: pending Steven Lugo <
> > support at quickbitcoin.co.uk>??159.203.88.55
> > Jun 04 21:30:06 2018 (17063) LISTNAME1: pending Steve Asher <
> > support at bitcoin.com.au>??185.237.98.51
> > Jun 04 21:30:38 2018 (17503) LISTNAME2: pending Sterling Leng <
> > support at vaultoro.com>??185.237.98.51
> > Jun 04 21:31:26 2018 (17651) LISTNAME3: pending Cristina Hibbard <
> > support at vaultoro.com>??59.152.95.54
> > Jun 04 21:32:01 2018 (17754) LISTNAME3: pending Kirk Maddox <
> > support at bitcoin.com.au>??185.237.98.51
> > Jun 04 21:33:58 2018 (18188) LISTNAME4: pending Jarrod Rand <
> > support at vaultoro.com>??80.211.240.206
> > Jun 04 21:36:54 2018 (19212) LISTNAME5: pending Anna Glen <
> > support at quickbitcoin.co.uk>??159.203.88.55
> > Jun 04 21:36:59 2018 (19231) LISTNAME1: pending John Savage <
> > support at bitflyer.com>??39.137.69.9
> > Jun 04 21:38:21 2018 (19476) LISTNAME4: pending Sarah Adami <
> > support at coindirect.com>??185.237.98.51
> > 
> 
> Interesting, I see delimited email addrs for those same domains.
> 
> Jun 04 20:57:11 2018 (5670) users: pending James Sturgill
> <support+qjrr
> @quickbitcoin.co.uk>??111.13.56.16
> Jun 04 21:19:10 2018 (7469) users: pending John Heninger
> <support+qwnpn
> @bitflyer.com>??152.231.81.122
> Jun 04 21:35:52 2018 (8894) users: pending Judith Route
> <support+xwwrk@
> vaultoro.com>??149.202.38.124
> Jun 04 21:42:25 2018 (9149) users: pending Donna Watts
> <support+yvdmgcn
> @vaultoro.com>??212.73.137.45
> Jun 04 21:49:33 2018 (9323) users: pending Justin Rybij
> <support+jzmpfp
> rm at bitflyer.com>??67.197.233.15
> 
> FWIW,
> 
> here's the list I've accumulated so far:
> alec768+kxqun at gmail.com
> alec768+kyccjs at gmail.com
> alec768+orfeij at gmail.com
> alec768+tmtkl at gmail.com
> alexmanalo76+engl at gmail.com
> alexmanalo76+hrrfbr at gmail.com
> alexmanalo76+nbkdtau at gmail.com
> alexmanalo76+vhffieas at gmail.com
> alexmanalo76+vlkpqi at gmail.com
> alexmanalo76+vnsjpy at gmail.com
> alexmanalo76+zasnfp at gmail.com
> cybertuna94+cxrp at gmail.com
> cybertuna94+gjuhtqwq at gmail.com
> cybertuna94+jhitu at gmail.com
> cybertuna94+wdlgmeq at gmail.com
> cybertuna94+xgosrla at gmail.com
> cybertuna94+xkon at gmail.com
> desertkaiju+fylzc at gmail.com
> desertkaiju+piurldte at gmail.com
> desertkaiju+rvkvz at gmail.com
> desertkaiju+tajkn at gmail.com
> desertkaiju+vwsgneo at gmail.com
> desertkaiju+wffbf at gmail.com
> desertkaiju+zczm at gmail.com
> khongthong94+baduvtj at gmail.com
> khongthong94+bhctkgb at gmail.com
> khongthong94+veyaqcw at gmail.com
> spikedmauler+jlxz at gmail.com
> sqrlyjack+hbqlyxc at gmail.com
> sqrlyjack+hdhpu at gmail.com
> sqrlyjack+nypxw at gmail.com
> sqrlyjack+vamjnvg at gmail.com
> sqrlyjack+vdfltrta at gmail.com
> support+jzmpfprm at bitflyer.com
> support+qjrr at quickbitcoin.co.uk
> support+qwnpn at bitflyer.com
> support+xwwrk at vaultoro.com
> support+yvdmgcn at vaultoro.com
> tinyowl94+dcjfcsq at gmail.com
> tinyowl94+ftmydowx at gmail.com
> tinyowl94+kffmkq at gmail.com
> tinyowl94+pfayzh at gmail.com
> tinyowl94+sdch at gmail.com
> tinyowl94+zoqbn at gmail.com
> yllwdg+gitvhnt at gmail.com
> 
> And these are the IPs:
> 
> 101.132.136.83
> 103.35.168.166
> 110.37.200.83
> 111.13.56.16
> 121.10.118.70
> 138.122.2.7
> 139.224.24.26
> 144.76.62.29
> 149.13.80.46
> 149.202.38.124
> 150.109.44.245
> 152.231.81.122
> 176.235.99.166
> 179.180.144.28
> 181.118.183.153
> 186.251.102.85
> 187.106.238.241
> 187.12.46.218
> 187.190.221.71
> 187.245.88.185
> 188.211.227.149
> 189.76.93.64
> 190.12.47.246
> 190.144.39.34
> 190.214.1.26
> 191.0.70.90
> 193.165.144.66
> 197.210.216.22
> 197.255.255.91
> 200.165.177.66
> 200.202.229.218
> 201.10.154.50
> 201.49.98.58
> 202.179.186.138
> 202.179.4.70
> 202.191.121.171
> 212.49.84.113
> 212.73.137.45
> 218.60.8.99
> 221.214.208.226
> 36.67.233.131
> 67.197.233.15
> 78.66.102.104
> 80.122.84.246

BTW, most of those IPs are listed in the XBL (https://www.spamhaus.org/
xbl/).  I think I'll work on a patch to block signups from IPs in the
XBL and domains in the DBL (https://www.spamhaus.org/dbl/)

- -Jim P.
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEPxwe8uYBnqxkbORSJxVetMRaJwUFAlsVvN8ACgkQJxVetMRa
JwUaug/+IUCgta0kc6d6zUUvVqo26UGlMGA7xGyhSFwc5MHArRMp9HL02ZvvB3V5
7COmUt1BDpuXN+ANESWVan/ZUQtwo3B6TbJlItrquUyOlr0vsOAcIENaLF9M70Zn
lZNq7RbiuX1NqLwgCE5+XUBLqrBv/UN01TLjPyYIMhKvWzes/rFpyYNIoUECLX1J
DVqvlo03EQddZmccVFyQ9FBBJfYKYOjWx2U6Im2mtf11tRIrPScGNZHrUzEYXJJr
1ilFBEr4MAPAdGgN+NiX7X7ei/O516lZGpXyjt60Mod1x62FCxXTUTYEUQ8Lshza
kULK8QtECBANbNZP23NG7U7NnLINbC8qKkSKh5mkmhjlU+qhLh+6STTv/uyA5s6v
MllrEt72ycJIFH7Xt5hUH3RuHlNR/1OgM4d8yLbDeCy5S/WjXxfGG/PeSIBCtG3l
lZw/thIBxRcxOCa/s55PBvhIz0qgv1YSA4RgCBbw5MhsO+GbV9+/lX5/fkNKd+uE
nntLBr9TPtuRDLAMOatcz3L/Yc355DXVteGNxi4eHhcJJboWr24ACOChVCvsy63y
RH2lrZC+jsVr+f+HP4oZdoYGEtUZdxmVZYalRDmgHyFQL1pOfBzt7XyA11yFgWYq
/sSUuVrQxIeSmBjnnfyJWI8xC/ZDi8qniWaWl7AKsIQsXCp2tng=
=duQI
-----END PGP SIGNATURE-----


From rclemings at gmail.com  Mon Jun  4 18:31:07 2018
From: rclemings at gmail.com (Russell Clemings)
Date: Mon, 4 Jun 2018 15:31:07 -0700
Subject: [Mailman-Users] Bogus Subscriptions
Message-ID: <CAN7RX0Y=6tz9huyY5kXm+kYiNMT8JwcmGzS1QgQ6RWtO1=xoWQ@mail.gmail.com>

I can add a few more:

glacierponi+ (etc.)
hanakage777+
icecreamkatana+
nasamok2+
oddjuice11+

and all of these (plus one that probably wouldn't make it past a spam
filter):

info at bitbroker.co.uk
info at btcsolutions.ca
oddjuice at yahoo.com
s7g7j7 at yahoo.com
support at cryptopay.me






> ---------- Forwarded message ----------
> From: Jim Popovitch <jimpop at domainmail.org>
> To: mailman-users at python.org
> Cc:
> Bcc:
> Date: Mon, 04 Jun 2018 18:10:57 -0400
> Subject: Re: [Mailman-Users] Bogus Subscriptions (was: Mailman-Users
> Digest, Vol 172, Issue 6)
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA512
>
> On Mon, 2018-06-04 at 14:48 -0700, Russell Clemings wrote:
> > They seem to be changing their tactics pretty much regularly now.
> > Just
> > tailing the subscribe log I see all of these:
> >
> > Jun 04 21:28:16 2018 (16689) LISTNAME1: pending Steven Lugo <
> > support at quickbitcoin.co.uk>  159.203.88.55
> > Jun 04 21:30:06 2018 (17063) LISTNAME1: pending Steve Asher <
> > support at bitcoin.com.au>  185.237.98.51
> > Jun 04 21:30:38 2018 (17503) LISTNAME2: pending Sterling Leng <
> > support at vaultoro.com>  185.237.98.51
> > Jun 04 21:31:26 2018 (17651) LISTNAME3: pending Cristina Hibbard <
> > support at vaultoro.com>  59.152.95.54
> > Jun 04 21:32:01 2018 (17754) LISTNAME3: pending Kirk Maddox <
> > support at bitcoin.com.au>  185.237.98.51
> > Jun 04 21:33:58 2018 (18188) LISTNAME4: pending Jarrod Rand <
> > support at vaultoro.com>  80.211.240.206
> > Jun 04 21:36:54 2018 (19212) LISTNAME5: pending Anna Glen <
> > support at quickbitcoin.co.uk>  159.203.88.55
> > Jun 04 21:36:59 2018 (19231) LISTNAME1: pending John Savage <
> > support at bitflyer.com>  39.137.69.9
> > Jun 04 21:38:21 2018 (19476) LISTNAME4: pending Sarah Adami <
> > support at coindirect.com>  185.237.98.51
> >
>
> Interesting, I see delimited email addrs for those same domains.
>
> Jun 04 20:57:11 2018 (5670) users: pending James Sturgill <support+qjrr
> @quickbitcoin.co.uk>  111.13.56.16
> Jun 04 21:19:10 2018 (7469) users: pending John Heninger <support+qwnpn
> @bitflyer.com>  152.231.81.122
> Jun 04 21:35:52 2018 (8894) users: pending Judith Route <support+xwwrk@
> vaultoro.com>  149.202.38.124
> Jun 04 21:42:25 2018 (9149) users: pending Donna Watts <support+yvdmgcn
> @vaultoro.com>  212.73.137.45
> Jun 04 21:49:33 2018 (9323) users: pending Justin Rybij <support+jzmpfp
> rm at bitflyer.com>  67.197.233.15
>
> FWIW,
>
> here's the list I've accumulated so far:
> alec768+kxqun at gmail.com
> alec768+kyccjs at gmail.com
> alec768+orfeij at gmail.com
> alec768+tmtkl at gmail.com
> alexmanalo76+engl at gmail.com
> alexmanalo76+hrrfbr at gmail.com
> alexmanalo76+nbkdtau at gmail.com
> alexmanalo76+vhffieas at gmail.com
> alexmanalo76+vlkpqi at gmail.com
> alexmanalo76+vnsjpy at gmail.com
> alexmanalo76+zasnfp at gmail.com
> cybertuna94+cxrp at gmail.com
> cybertuna94+gjuhtqwq at gmail.com
> cybertuna94+jhitu at gmail.com
> cybertuna94+wdlgmeq at gmail.com
> cybertuna94+xgosrla at gmail.com
> cybertuna94+xkon at gmail.com
> desertkaiju+fylzc at gmail.com
> desertkaiju+piurldte at gmail.com
> desertkaiju+rvkvz at gmail.com
> desertkaiju+tajkn at gmail.com
> desertkaiju+vwsgneo at gmail.com
> desertkaiju+wffbf at gmail.com
> desertkaiju+zczm at gmail.com
> khongthong94+baduvtj at gmail.com
> khongthong94+bhctkgb at gmail.com
> khongthong94+veyaqcw at gmail.com
> spikedmauler+jlxz at gmail.com
> sqrlyjack+hbqlyxc at gmail.com
> sqrlyjack+hdhpu at gmail.com
> sqrlyjack+nypxw at gmail.com
> sqrlyjack+vamjnvg at gmail.com
> sqrlyjack+vdfltrta at gmail.com
> support+jzmpfprm at bitflyer.com
> support+qjrr at quickbitcoin.co.uk
> support+qwnpn at bitflyer.com
> support+xwwrk at vaultoro.com
> support+yvdmgcn at vaultoro.com
> tinyowl94+dcjfcsq at gmail.com
> tinyowl94+ftmydowx at gmail.com
> tinyowl94+kffmkq at gmail.com
> tinyowl94+pfayzh at gmail.com
> tinyowl94+sdch at gmail.com
> tinyowl94+zoqbn at gmail.com
> yllwdg+gitvhnt at gmail.com
>
>
>

From mark at msapiro.net  Mon Jun  4 18:26:51 2018
From: mark at msapiro.net (Mark Sapiro)
Date: Mon, 4 Jun 2018 15:26:51 -0700
Subject: [Mailman-Users] Bogus Subscriptions (was: Mailman-Users Digest,
 Vol 172, Issue 6)
In-Reply-To: <1528150257.3295.1.camel@domainmail.org>
References: <mailman.2287.1528076427.2803.mailman-users@python.org>
 <CAN7RX0aLvOrjfjF9M=Mz_C-CUXRm14mh+MjbC-4hbjzryeJk0Q@mail.gmail.com>
 <1528150257.3295.1.camel@domainmail.org>
Message-ID: <00fa4cb3-cf30-9289-ffa7-ad2805942726@msapiro.net>

My own production server started getting these a few hours ago. I am
currently banning '^support[@+].*' and '^info[@+].*'

These are addresses I've banned within the last 2 hours:

info at bitbroker.co.uk
info at btcsolutions.ca
support+aalmte at bitflyer.com
support+adqyynrm at coindirect.com
support+aogfqd at coindirect.com
support+atpou at vaultoro.com
support+aypxfue at coindirect.com
support+azrqohm at btc-alpha.com
support+bcnksqq at bitcoin.com.au
support+bdfx at coinexchange.io
support+bfowcb at coinexchange.io
support+bjbpu at coinexchange.io
support+brjhp at quickbitcoin.co.uk
support+bsbv at bitflyer.com
support+bxmry at bitflyer.com
support+cdnbwozc at quickbitcoin.co.uk
support+cgfqdzx at quickbitcoin.co.uk
support+cilpfshx at bitcoin.com.au
support+cooje at cryptopay.me
support+cshwpk at coindirect.com
support+csnnimza at vaultoro.com
support+ctok at bitcoin.com.au
support+dptvtrb at coindirect.com
support+drajp at coindirect.com
support+dsrsirup at quickbitcoin.co.uk
support+dswqogik at coinexchange.io
support+dvzw at btc-alpha.com
support+dwckt at cryptopay.me
support+ehfrpij at bitcoin.com.au
support+ekdhf at bitflyer.com
support+eklw at btc-alpha.com
support+eyppcyts at coindirect.com
support+ezkerj at btc-alpha.com
support+feyal at bitcoin.com.au
support+fjirxrnn at bitflyer.com
support+fpwf at btc-alpha.com
support+frermpv at bitcoin.com.au
support+frsntfb at bitflyer.com
support+frvesq at bitflyer.com
support+fxoizf at bitflyer.com
support+gbnvyarl at btc-alpha.com
support+gdvnv at coindirect.com
support+geqkcxm at btc-alpha.com
support+ggbleaw at vaultoro.com
support+gsughixq at btc-alpha.com
support+gxrrnokx at btc-alpha.com
support+gysjauv at cryptopay.me
support+hbfwyhw at btc-alpha.com
support+hdkykau at coindirect.com
support+hebxros at coinexchange.io
support+hgvd at cryptopay.me
support+hhwwfn at bitflyer.com
support+hioga at bitcoin.com.au
support+hlghl at btc-alpha.com
support+hnkadhx at coindirect.com
support+hpccnygf at quickbitcoin.co.uk
support+ifxz at vaultoro.com
support+igabxygi at quickbitcoin.co.uk
support+iqbe at bitcoin.com.au
support+iqnzyi at bitflyer.com
support+iuzqqivx at cryptopay.me
support+ixcy at coindirect.com
support+iyvj at bitcoin.com.au
support+izhwfexl at coindirect.com
support+jiqqto at bitcoin.com.au
support+jiwv at cryptopay.me
support+jtbw at coinexchange.io
support+jtlsbjez at cryptopay.me
support+jzcxkmlq at coindirect.com
support+kftenm at btc-alpha.com
support+kgtkssb at vaultoro.com
support+kwcsdoc at vaultoro.com
support+kzsq at bitcoin.com.au
support+ldhjdtop at cryptopay.me
support+levko at btc-alpha.com
support+mabxeuje at cryptopay.me
support+majlv at coindirect.com
support+mjbbt at coindirect.com
support+mndt at btc-alpha.com
support+mpllw at quickbitcoin.co.uk
support+mtamxiw at bitcoin.com.au
support+ncauab at coindirect.com
support+ncfb at vaultoro.com
support+nhstjmki at vaultoro.com
support+nltk at bitflyer.com
support+npqfyebo at cryptopay.me
support+nqhynm at coinexchange.io
support+ntaeieoe at coindirect.com
support+nyiqpijf at bitflyer.com
support+ojnibwah at bitcoin.com.au
support+orfgdhk at quickbitcoin.co.uk
support+osre at coinexchange.io
support+oswxguk at bitflyer.com
support+otzykwm at coindirect.com
support+oykm at bitcoin.com.au
support+pfgrza at quickbitcoin.co.uk
support+pneiob at cryptopay.me
support+psuoivkd at coinexchange.io
support+pxwz at coindirect.com
support+pzad at quickbitcoin.co.uk
support+qedmfkxq at bitcoin.com.au
support+qgdwyt at quickbitcoin.co.uk
support+rhrc at bitflyer.com
support+riyci at bitflyer.com
support+rjvael at bitcoin.com.au
support+rjzdmf at coindirect.com
support+rrdqsi at bitflyer.com
support+rves at bitflyer.com
support+rxvg at coinexchange.io
support+ryhxoryd at cryptopay.me
support+sehl at btc-alpha.com
support+sftkj at quickbitcoin.co.uk
support+skwpxwnn at coinexchange.io
support+slaeax at btc-alpha.com
support+slkxeljb at vaultoro.com
support+tauqn at btc-alpha.com
support+tbdpk at quickbitcoin.co.uk
support+tekix at coindirect.com
support+tocqexn at cryptopay.me
support+tsuqdfh at bitflyer.com
support+tuyvzo at btc-alpha.com
support+twwpox at bitflyer.com
support+txlro at vaultoro.com
support+tzzfxagz at coinexchange.io
support+ufytnr at btc-alpha.com
support+ugkifei at bitcoin.com.au
support+uhdqnea at btc-alpha.com
support+ulawwl at quickbitcoin.co.uk
support+ulxdo at vaultoro.com
support+umstfxa at quickbitcoin.co.uk
support+uqmc at bitcoin.com.au
support+urlhl at cryptopay.me
support+vbshvf at bitcoin.com.au
support+vdtcsbz at cryptopay.me
support+vdtwjpbi at vaultoro.com
support+vjjiiff at cryptopay.me
support+vqwil at quickbitcoin.co.uk
support+vump at coindirect.com
support+vyctq at btc-alpha.com
support+waivtmdz at coindirect.com
support+wesh at btc-alpha.com
support+wrbr at btc-alpha.com
support+xbkitu at coindirect.com
support+xcan at cryptopay.me
support+xdsbima at bitcoin.com.au
support+xiyyqzb at bitcoin.com.au
support+xpbivdk at bitflyer.com
support+xqen at coindirect.com
support+xqkuhy at vaultoro.com
support+xsrefjzz at btc-alpha.com
support+xxrzlggh at btc-alpha.com
support+yaadukuu at coinexchange.io
support+yeaqvoos at coinexchange.io
support+yebxwfy at btc-alpha.com
support+yeklq at quickbitcoin.co.uk
support+yffavl at vaultoro.com
support+yfixk at coindirect.com
support+yfpd at coinexchange.io
support+yhouqj at coindirect.com
support+yjnbe at vaultoro.com
support+ymyciihc at cryptopay.me
support+yndcfzy at vaultoro.com
support+zaktrsc at quickbitcoin.co.uk
support+zfzquveu at coindirect.com
support+zgxlowj at bitflyer.com
support+zjcd at cryptopay.me


-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <http://mail.python.org/pipermail/mailman-users/attachments/20180604/8d91e88f/attachment.sig>

From mark at msapiro.net  Mon Jun  4 20:48:11 2018
From: mark at msapiro.net (Mark Sapiro)
Date: Mon, 4 Jun 2018 17:48:11 -0700
Subject: [Mailman-Users] Bogus Subscriptions (was: Mailman-Users Digest,
 Vol 172, Issue 6)
In-Reply-To: <1528151263.3295.3.camel@domainmail.org>
References: <mailman.2287.1528076427.2803.mailman-users@python.org>
 <CAN7RX0aLvOrjfjF9M=Mz_C-CUXRm14mh+MjbC-4hbjzryeJk0Q@mail.gmail.com>
 <1528150257.3295.1.camel@domainmail.org>
 <1528151263.3295.3.camel@domainmail.org>
Message-ID: <f1a487d2-44cf-f1e3-2ef4-202ffdb8ccd8@msapiro.net>

On 06/04/2018 03:27 PM, Jim Popovitch via Mailman-Users wrote:
> 
> BTW, most of those IPs are listed in the XBL (https://www.spamhaus.org/
> xbl/).  I think I'll work on a patch to block signups from IPs in the
> XBL and domains in the DBL (https://www.spamhaus.org/dbl/)


I just checked against spamhaus ZEN and of the 196 IPs associated with
the banned subscribes I reported earlier in this thread, 168 are listed.

I have applied the attached patch to a couple of installations. We'll
see if it helps.

-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan
-------------- next part --------------
A non-text attachment was scrubbed...
Name: spamhaus.patch
Type: text/x-patch
Size: 1721 bytes
Desc: not available
URL: <http://mail.python.org/pipermail/mailman-users/attachments/20180604/b1773e81/attachment-0001.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <http://mail.python.org/pipermail/mailman-users/attachments/20180604/b1773e81/attachment-0001.sig>

From mark at msapiro.net  Mon Jun  4 21:22:54 2018
From: mark at msapiro.net (Mark Sapiro)
Date: Mon, 4 Jun 2018 18:22:54 -0700
Subject: [Mailman-Users] Bogus Subscriptions (was: Mailman-Users Digest,
 Vol 172, Issue 6)
In-Reply-To: <f1a487d2-44cf-f1e3-2ef4-202ffdb8ccd8@msapiro.net>
References: <mailman.2287.1528076427.2803.mailman-users@python.org>
 <CAN7RX0aLvOrjfjF9M=Mz_C-CUXRm14mh+MjbC-4hbjzryeJk0Q@mail.gmail.com>
 <1528150257.3295.1.camel@domainmail.org>
 <1528151263.3295.3.camel@domainmail.org>
 <f1a487d2-44cf-f1e3-2ef4-202ffdb8ccd8@msapiro.net>
Message-ID: <4a36e111-a0e6-ea43-a9d2-e35a5652ac82@msapiro.net>

On 06/04/2018 05:48 PM, Mark Sapiro wrote:
> I have applied the attached patch to a couple of installations. We'll
> see if it helps.


I have made this a feature contingent on setting

mm_cfg.BLOCK_SPAMHAUS_LISTED_IP_SUBSCRIBE = Yes

and committed it for the next release.

-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <http://mail.python.org/pipermail/mailman-users/attachments/20180604/55d2056a/attachment.sig>

From mark at msapiro.net  Mon Jun  4 22:29:43 2018
From: mark at msapiro.net (Mark Sapiro)
Date: Mon, 4 Jun 2018 19:29:43 -0700
Subject: [Mailman-Users] Bogus Subscriptions (was: Mailman-Users Digest,
 Vol 172, Issue 6)
In-Reply-To: <01000163cd9a98e9-de1b9a6e-d76e-45f9-8ed5-4a0255d25c30-000000@email.amazonses.com>
References: <mailman.2287.1528076427.2803.mailman-users@python.org>
 <CAN7RX0aLvOrjfjF9M=Mz_C-CUXRm14mh+MjbC-4hbjzryeJk0Q@mail.gmail.com>
 <1528150257.3295.1.camel@domainmail.org>
 <1528151263.3295.3.camel@domainmail.org>
 <f1a487d2-44cf-f1e3-2ef4-202ffdb8ccd8@msapiro.net>
 <4a36e111-a0e6-ea43-a9d2-e35a5652ac82@msapiro.net>
 <01000163cd9a98e9-de1b9a6e-d76e-45f9-8ed5-4a0255d25c30-000000@email.amazonses.com>
Message-ID: <ffb74901-1390-cb91-87b8-5573f2124609@msapiro.net>

On 06/04/2018 06:40 PM, Adam Goldberg wrote:
> Mark - did you consider generalizing the patch a little bit (so it works with Spamhaus, but also with other RBLs)?  Spamhaus is one RBL provider, but there are a bunch (and most of them work the same way).


Yes, I know, but I wanted something simple. I'm actually in the process
of restricting Spamhaus a bit to not include PBL hits because those are
IPs that by policy don't send mail and they're probably not appropriate
for this purpose.

I am trying to do something simple. I certainly don't want to introduce
a complicated configuration option to select RBLs. As time permits, I
may add other lists, but for now I'm just querying Spamhaus ZEN but only
accepting hits from SBL, CSS or XBL.

-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan

From jimpop at domainmail.org  Tue Jun  5 01:15:05 2018
From: jimpop at domainmail.org (Jim Popovitch)
Date: Tue, 05 Jun 2018 05:15:05 +0000
Subject: [Mailman-Users] Bogus Subscriptions (was: Mailman-Users Digest,
 Vol 172, Issue 6)
In-Reply-To: <4a36e111-a0e6-ea43-a9d2-e35a5652ac82@msapiro.net>
References: <mailman.2287.1528076427.2803.mailman-users@python.org>
 <CAN7RX0aLvOrjfjF9M=Mz_C-CUXRm14mh+MjbC-4hbjzryeJk0Q@mail.gmail.com>
 <1528150257.3295.1.camel@domainmail.org>
 <1528151263.3295.3.camel@domainmail.org>
 <f1a487d2-44cf-f1e3-2ef4-202ffdb8ccd8@msapiro.net>
 <4a36e111-a0e6-ea43-a9d2-e35a5652ac82@msapiro.net>
Message-ID: <2D20F6D5-F44F-47FC-9151-06D925FDAC4F@domainmail.org>

On June 5, 2018 1:22:54 AM UTC, Mark Sapiro <mark at msapiro.net> wrote:
>On 06/04/2018 05:48 PM, Mark Sapiro wrote:
>> I have applied the attached patch to a couple of installations. We'll
>> see if it helps.
>
>
>I have made this a feature contingent on setting
>
>mm_cfg.BLOCK_SPAMHAUS_LISTED_IP_SUBSCRIBE = Yes
>

Thank you very much Mark.  The latest patch (from bzr) applies cleanly and there's something new in the vette log already:

Jun 05 04:55:44 2018 (1812) Users banned subscription: info at bitbroker.co.uk from 116.255.35.23 (Spamhaus IP)

Very nice!

Thanks again,

-Jim P.



From adam at agp-llc.com  Mon Jun  4 21:40:51 2018
From: adam at agp-llc.com (Adam Goldberg)
Date: Tue, 5 Jun 2018 01:40:51 +0000
Subject: [Mailman-Users] Bogus Subscriptions (was: Mailman-Users Digest,
 Vol 172, Issue 6)
In-Reply-To: <4a36e111-a0e6-ea43-a9d2-e35a5652ac82@msapiro.net>
References: <mailman.2287.1528076427.2803.mailman-users@python.org>
 <CAN7RX0aLvOrjfjF9M=Mz_C-CUXRm14mh+MjbC-4hbjzryeJk0Q@mail.gmail.com>
 <1528150257.3295.1.camel@domainmail.org>
 <1528151263.3295.3.camel@domainmail.org>
 <f1a487d2-44cf-f1e3-2ef4-202ffdb8ccd8@msapiro.net>
 <4a36e111-a0e6-ea43-a9d2-e35a5652ac82@msapiro.net>
Message-ID: <01000163cd9a9871-7c3c1f29-f5e4-47bf-821f-2acfd3391c8d-000000@email.amazonses.com>

Mark - did you consider generalizing the patch a little bit (so it works with Spamhaus, but also with other RBLs)?  Spamhaus is one RBL provider, but there are a bunch (and most of them work the same way).

--
Adam Goldberg
571-276-0305


-----Original Message-----
From: Mailman-Users [mailto:mailman-users-bounces+adam=agp-llc.com at python.org] On Behalf Of Mark Sapiro
Sent: Monday, June 04, 2018 9:23 PM
To: mailman-users at python.org
Subject: Re: [Mailman-Users] Bogus Subscriptions (was: Mailman-Users Digest, Vol 172, Issue 6)

On 06/04/2018 05:48 PM, Mark Sapiro wrote:
> I have applied the attached patch to a couple of installations. We'll 
> see if it helps.


I have made this a feature contingent on setting

mm_cfg.BLOCK_SPAMHAUS_LISTED_IP_SUBSCRIBE = Yes

and committed it for the next release.

-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan


From brentk at birs.ca  Mon Jun  4 20:31:13 2018
From: brentk at birs.ca (Brent Kearney)
Date: Mon, 4 Jun 2018 18:31:13 -0600
Subject: [Mailman-Users] mailman-2.1.26: `make install` fails
Message-ID: <904FDA08-BA30-4687-9CE4-441BA6412A53@birs.ca>

Hello,

When I run 'make install? on mailman-2.1.26 (with python 2.7), I get a fatal error in the ?misc? directory. The complete output is below.

I notice that the "for p in   ; \? has an empty list of packages. Perhaps that for loop should be surrounded by a conditional checking that the $(PACKAGES) variable is non-empty?

Best regards,
Brent


mailman-2.1.26]$ sudo make install
Creating architecture independent directories...
chmod o-r /opt/mailman/archives/private
Creating architecture dependent directories...
for f in mmsitepass newlist rmlist add_members  list_members remove_members clone_member update arch  sync_members check_db withlist check_perms find_member  version config_list list_lists dumpdb cleanarch  list_admins genaliases change_pw mailmanctl qrunner inject  unshunt fix_url.py convert.py transcheck b4b5-archfix  list_owners msgfmt.py show_qfiles discard rb-archfix  reset_pw.py export.py mailman-config; \
do \
    /opt/csw/bin/ginstall -c -m 755 ../build/bin/$f /opt/mailman/bin; \
done
for f in crontab.in; \
do \
    /opt/csw/bin/ginstall -c -m 644 $f /opt/mailman/cron; \
done
for f in checkdbs mailpasswds senddigests gate_news  nightly_gzip bumpdigests disabled cull_bad_shunt; \
do \
    /opt/csw/bin/ginstall -c -m 755 ../build/cron/$f /opt/mailman/cron; \
done
for i in ./*.jpg ./*.png ./*.ico; \
do \
  /opt/csw/bin/ginstall -c -m 644 $i /opt/mailman/icons; \
done
for d in bin cron scripts tests; \
do \
    dir=/opt/mailman/$d; \
    /opt/csw/bin/ginstall -c -m 644 paths.py $dir; \
done
/opt/csw/bin/ginstall -c -m 755 mailman /opt/mailman/scripts
/opt/csw/bin/ginstall -c -m 644 sitelist.cfg /opt/mailman/data
if [ -z "" -a -d /opt/mailman/pythonlib/email ] ; \
then \
    rm -rf /opt/mailman/pythonlib/email* ; \
fi
for p in   ; \
do \
    gunzip -c ./$p.tar.gz | (cd . ; tar xf -); \
    (cd ./$p ; umask 02 ; PYTHONPATH=/opt/mailman/pythonlib /opt/csw/bin/python2.7 setup.py --quiet install --install-lib /opt/mailman/pythonlib  --install-purelib /opt/mailman/pythonlib  --install-data /opt/mailman/pythonlib); \
done
sh: syntax error at line 1: `;' unexpected
*** Error code 2
make: Fatal error: Command failed for target `install-packages'
Current working directory /opt/src/mailman-2.1.26/misc
*** Error code 1
The following command caused the error:
for d in bin cron misc Mailman scripts src templates messages tests; \
do \
    (cd $d; make DESTDIR= install); \
done
make: Fatal error: Command failed for target `doinstall'


From mark at msapiro.net  Tue Jun  5 16:17:33 2018
From: mark at msapiro.net (Mark Sapiro)
Date: Tue, 5 Jun 2018 13:17:33 -0700
Subject: [Mailman-Users] mailman-2.1.26: `make install` fails
In-Reply-To: <904FDA08-BA30-4687-9CE4-441BA6412A53@birs.ca>
References: <904FDA08-BA30-4687-9CE4-441BA6412A53@birs.ca>
Message-ID: <813787ab-c496-80f6-5382-08fdbdd51b51@msapiro.net>

On 06/04/2018 05:31 PM, Brent Kearney wrote:
> Hello,
> 
> When I run 'make install? on mailman-2.1.26 (with python 2.7), I get a fatal error in the ?misc? directory. The complete output is below.
> 
> I notice that the "for p in   ; \? has an empty list of packages. Perhaps that for loop should be surrounded by a conditional checking that the $(PACKAGES) variable is non-empty?


What version of make do you have. It works fine for me with GNU Make 4.1.

Also, since Mailman 2.1.13, the settings for EMAILPKG, JACODECSPKG and
KOCODECSPKG and hence for PACKAGES are always empty if the underlying
Python on the system running configure has email>=2.5.8 and iso-2022-jp
and euc-kr codecs in its library which is true of Python since 2.4, and
this is the first I've heard of this issue.

-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan

From brentk at birs.ca  Tue Jun  5 16:40:18 2018
From: brentk at birs.ca (Brent Kearney)
Date: Tue, 5 Jun 2018 14:40:18 -0600
Subject: [Mailman-Users] mailman-2.1.26: `make install` fails
In-Reply-To: <813787ab-c496-80f6-5382-08fdbdd51b51@msapiro.net>
References: <904FDA08-BA30-4687-9CE4-441BA6412A53@birs.ca>
 <813787ab-c496-80f6-5382-08fdbdd51b51@msapiro.net>
Message-ID: <C0766BA9-E604-449E-BD15-44AE7B388745@birs.ca>

Thanks Mark; its an old Sun Solaris 10 system. I?m not sure how to get the version from make itself, but the GCC version is 3.4.3.



> On Jun 5, 2018, at 14:17, Mark Sapiro <mark at msapiro.net> wrote:
> 
> On 06/04/2018 05:31 PM, Brent Kearney wrote:
>> Hello,
>> 
>> When I run 'make install? on mailman-2.1.26 (with python 2.7), I get a fatal error in the ?misc? directory. The complete output is below.
>> 
>> I notice that the "for p in   ; \? has an empty list of packages. Perhaps that for loop should be surrounded by a conditional checking that the $(PACKAGES) variable is non-empty?
> 
> 
> What version of make do you have. It works fine for me with GNU Make 4.1.
> 
> Also, since Mailman 2.1.13, the settings for EMAILPKG, JACODECSPKG and
> KOCODECSPKG and hence for PACKAGES are always empty if the underlying
> Python on the system running configure has email>=2.5.8 and iso-2022-jp
> and euc-kr codecs in its library which is true of Python since 2.4, and
> this is the first I've heard of this issue.
> 
> -- 
> Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
> San Francisco Bay Area, California    better use your sense - B. Dylan
> ------------------------------------------------------
> Mailman-Users mailing list Mailman-Users at 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/brentk%40birs.ca


From mark at msapiro.net  Tue Jun  5 17:10:40 2018
From: mark at msapiro.net (Mark Sapiro)
Date: Tue, 5 Jun 2018 14:10:40 -0700
Subject: [Mailman-Users] mailman-2.1.26: `make install` fails
In-Reply-To: <C0766BA9-E604-449E-BD15-44AE7B388745@birs.ca>
References: <904FDA08-BA30-4687-9CE4-441BA6412A53@birs.ca>
 <813787ab-c496-80f6-5382-08fdbdd51b51@msapiro.net>
 <C0766BA9-E604-449E-BD15-44AE7B388745@birs.ca>
Message-ID: <0f239147-deda-b02c-0c6c-9e1a1517de37@msapiro.net>

On 06/05/2018 01:40 PM, Brent Kearney wrote:
> Thanks Mark; its an old Sun Solaris 10 system. I?m not sure how to get the version from make itself, but the GCC version is 3.4.3.


Try

make --version

or if that doesn't work,

make --help

to see the options.

-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan

From Michael.D.Parker at ga.com  Tue Jun  5 18:55:09 2018
From: Michael.D.Parker at ga.com (Parker, Michael D.)
Date: Tue, 5 Jun 2018 22:55:09 +0000
Subject: [Mailman-Users] -EXT-Re: Any scripting available for server
 site admin
Message-ID: <b5859f6760be4ea2ab22aebbe0b6dd18@ASGEXCPWP05.ga.com>

Hmmm....these commands operate on a list basis, not a system basis (i.e. global)  as I had hoped for..

Again I am wondering about commands that operate on a server basis....like list all members in all groups in one command....remove selected user from all lists in my server.  The latter would be used in our supported lists to remove people that have left the company preventing the excess mail in the system (that would bounce).  This type of stuff cannot necessarily be delegated to each list administrator.

Now I know that I could shell some of this out but I thought given the maturity of the product that site tools would be available ... thus preventing me from re-inventing the wheel if you will.  I am sure that I am not the only one in this situation.

Thanks for any additional help.

***** ***** *****

-----Original Message-----
From: Mailman-Users <mailman-users-bounces+michael.d.parker=ga.com at python.org> On Behalf Of Jim Popovitch via Mailman-Users
Sent: Monday, June 4, 2018 12:07
To: mailman-users at python.org
Subject: -EXT-Re: [Mailman-Users] Any scripting available for global site admin

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On Mon, 2018-06-04 at 18:47 +0000, Parker, Michael D. wrote:
> I have mailman 2.x and am specifically interested in knowing how to do 
> the following two tasks:
> 
> 
> 1.???????List all users with all their mailing lists

list_members -h

> 
> 2.???????Globally remove a user from all mailing lists


remove_members -h


- -Jim P.
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEPxwe8uYBnqxkbORSJxVetMRaJwUFAlsVjcAACgkQJxVetMRa
JwXfNA/+JKUTpU6s/Pgw38RVt0gieuymvcfY4F9tQcJTlXbGJmfEL1AYAdZKRWrd
idQ8Ct1g4ZW3C8Xp3t28fXF2xPGxrNpXq7RSCaJWkrYGt4qpR/3W8fHgkXpQy/8V
zYXPk2W+rncbTYY2NyXfQK+OaMNT5bpsQ/ZpInI5rnS48pfFS8dlTahC1bTRqMf3
VVj7IlVFs2VvNznVXOPLI9axyHZECFVlQ5x3/KMi7NWipqHn6JzYqSAWGoUEOrps
dY7eh3DxPkS4yCDMe8RssSCzjDBmJRBdAyrvk9njmhNGRhDRDRPAIrRc8LrFsSJ9
DENmNdNYqUSHuryHNG0YvMRyFxj4QLlyBQaS6F2QBaK1KkYCX8her9y94FVi+dXA
HexGBbEsLIN0j/3pGQcQLXiidZv8BS3O6+pAmoRMeBDE+yC4+sdZiNDE5pF4zSKI
Z9yyrPDe4ZMZa5dVXzbVHc9HSwcAW/9uW7Lftq36G9t1SeypBdRnDbYT5u8bXN2o
0DYNCwriyxKwil/KeSBHaP+aqxloI6Poh07z1Wz8i/WzSCFux/dmVttQgLklu6Ra
Ww5vqj23oDHytr5rERKKCpjNUOC5HwhNO5o6VBktvfj609e1RQlGRs9Tio2ue1ka
wqY18555JQr6lJxCz6je5uF3Wb4N60jAM/pehsIafJpzpCtS3h4=
=mSvT
-----END PGP SIGNATURE-----

------------------------------------------------------
Mailman-Users mailing list Mailman-Users at 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/michael.d.parker%40ga.com

From mark at msapiro.net  Tue Jun  5 19:08:15 2018
From: mark at msapiro.net (Mark Sapiro)
Date: Tue, 5 Jun 2018 16:08:15 -0700
Subject: [Mailman-Users] -EXT-Re: Any scripting available for server
 site admin
In-Reply-To: <b5859f6760be4ea2ab22aebbe0b6dd18@ASGEXCPWP05.ga.com>
References: <b5859f6760be4ea2ab22aebbe0b6dd18@ASGEXCPWP05.ga.com>
Message-ID: <0cd34d6d-2f47-89d1-2735-d628a26c5f67@msapiro.net>

On 06/05/2018 03:55 PM, Parker, Michael D. wrote:
> 
> Again I am wondering about commands that operate on a server basis....like list all members in all groups in one command...


bin/find_member .

The '.' is a pattern that matches any address.


>.remove selected user from all lists in my server. 


bin/remove_members --fromall <address>

(maybe you'll see it this time. It was in a prior reply at
<https://mail.python.org/pipermail/mailman-users/2018-June/083425.html>)

-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <http://mail.python.org/pipermail/mailman-users/attachments/20180605/9359d225/attachment.sig>

From Michael.D.Parker at ga.com  Tue Jun  5 19:54:10 2018
From: Michael.D.Parker at ga.com (Parker, Michael D.)
Date: Tue, 5 Jun 2018 23:54:10 +0000
Subject: [Mailman-Users] FW: -EXT-Re: Any scripting available for server
 site admin
References: <b5859f6760be4ea2ab22aebbe0b6dd18@ASGEXCPWP05.ga.com>
 <0cd34d6d-2f47-89d1-2735-d628a26c5f67@msapiro.net> 
Message-ID: <c548b6340d7344ad8152223a2f431f98@ASGEXCPWP05.ga.com>

----Original Message-----
From: Parker, Michael D. 
Sent: Tuesday, June 5, 2018 16:46
To: 'Mark Sapiro' <mark at msapiro.net>
Subject: RE: [Mailman-Users] -EXT-Re: Any scripting available for server site admin

Thanks....

Hmmm.....I also note something interesting about find_member, it treats email addresses with different character case-ing differently.

Thus Michael.d.parker at ga.com lists are put in a separate grouping from michael.d.parker at ga.com lists.

Do email user addresses out there on the web support names in this manner differently?  Off hand, I cannot think of a mailer that does this these days.

******************************************************************************************


-----Original Message-----
From: Mailman-Users <mailman-users-bounces+michael.d.parker=ga.com at python.org> On Behalf Of Mark Sapiro
Sent: Tuesday, June 5, 2018 16:08
To: mailman-users at python.org
Subject: Re: [Mailman-Users] -EXT-Re: Any scripting available for server site admin

On 06/05/2018 03:55 PM, Parker, Michael D. wrote:
> 
> Again I am wondering about commands that operate on a server basis....like list all members in all groups in one command...


bin/find_member .

The '.' is a pattern that matches any address.


>.remove selected user from all lists in my server. 


bin/remove_members --fromall <address>

(maybe you'll see it this time. It was in a prior reply at
<https://mail.python.org/pipermail/mailman-users/2018-June/083425.html>)

-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan


From Richard at Damon-Family.org  Tue Jun  5 20:34:19 2018
From: Richard at Damon-Family.org (Richard Damon)
Date: Tue, 5 Jun 2018 20:34:19 -0400
Subject: [Mailman-Users] FW: -EXT-Re: Any scripting available for server
 site admin
In-Reply-To: <c548b6340d7344ad8152223a2f431f98@ASGEXCPWP05.ga.com>
References: <b5859f6760be4ea2ab22aebbe0b6dd18@ASGEXCPWP05.ga.com>
 <0cd34d6d-2f47-89d1-2735-d628a26c5f67@msapiro.net>
 <c548b6340d7344ad8152223a2f431f98@ASGEXCPWP05.ga.com>
Message-ID: <caec5a56-a90f-12ea-6254-a7f157c3c36f@Damon-Family.org>

The user part of an email address MIGHT be case sensitive, so unless you
KNOW that a given domain is case insensitive, changing the case of an
email entails some risk. Mailman is just being appropriately cautious here.

On 6/5/18 7:54 PM, Parker, Michael D. wrote:
> ----Original Message-----
> From: Parker, Michael D. 
> Sent: Tuesday, June 5, 2018 16:46
> To: 'Mark Sapiro' <mark at msapiro.net>
> Subject: RE: [Mailman-Users] -EXT-Re: Any scripting available for server site admin
>
> Thanks....
>
> Hmmm.....I also note something interesting about find_member, it treats email addresses with different character case-ing differently.
>
> Thus Michael.d.parker at ga.com lists are put in a separate grouping from michael.d.parker at ga.com lists.
>
> Do email user addresses out there on the web support names in this manner differently?  Off hand, I cannot think of a mailer that does this these days.
>
> ******************************************************************************************
>
>
> -----Original Message-----
> From: Mailman-Users <mailman-users-bounces+michael.d.parker=ga.com at python.org> On Behalf Of Mark Sapiro
> Sent: Tuesday, June 5, 2018 16:08
> To: mailman-users at python.org
> Subject: Re: [Mailman-Users] -EXT-Re: Any scripting available for server site admin
>
> On 06/05/2018 03:55 PM, Parker, Michael D. wrote:
>> Again I am wondering about commands that operate on a server basis....like list all members in all groups in one command...
>
> bin/find_member .
>
> The '.' is a pattern that matches any address.
>
>
>> .remove selected user from all lists in my server. 
>
> bin/remove_members --fromall <address>
>
> (maybe you'll see it this time. It was in a prior reply at
> <https://mail.python.org/pipermail/mailman-users/2018-June/083425.html>)
>

-- 
Richard Damon


From mark at msapiro.net  Tue Jun  5 20:35:35 2018
From: mark at msapiro.net (Mark Sapiro)
Date: Tue, 5 Jun 2018 17:35:35 -0700
Subject: [Mailman-Users] FW: -EXT-Re: Any scripting available for server
 site admin
In-Reply-To: <c548b6340d7344ad8152223a2f431f98@ASGEXCPWP05.ga.com>
References: <b5859f6760be4ea2ab22aebbe0b6dd18@ASGEXCPWP05.ga.com>
 <0cd34d6d-2f47-89d1-2735-d628a26c5f67@msapiro.net>
 <c548b6340d7344ad8152223a2f431f98@ASGEXCPWP05.ga.com>
Message-ID: <70d03178-6159-e0ea-4d50-96ec25844fbf@msapiro.net>

On 06/05/2018 04:54 PM, Parker, Michael D. wrote:
> 
> Hmmm.....I also note something interesting about find_member, it treats email addresses with different character case-ing differently.
> 
> Thus Michael.d.parker at ga.com lists are put in a separate grouping from michael.d.parker at ga.com lists.
> 
> Do email user addresses out there on the web support names in this manner differently?  Off hand, I cannot think of a mailer that does this these days.


RFC 5321 (sec 2.3.11) and predecessors say:

   The standard mailbox naming convention is defined to be
   "local-part at domain"; contemporary usage permits a much broader set of
   applications than simple "user names".  Consequently, and due to a
   long history of problems when intermediate hosts have attempted to
   optimize transport by modifying them, the local-part MUST be
   interpreted and assigned semantics only by the host specified in the
   domain part of the address.

Sec 4.1.2 further defines and qualifies local-part as

   Local-part     = Dot-string / Quoted-string
                  ; MAY be case-sensitive

but adds

   While the above definition for Local-part is relatively permissive,
   for maximum interoperability, a host that expects to receive mail
   SHOULD avoid defining mailboxes where the Local-part requires (or
   uses) the Quoted-string form or where the Local-part is case-
   sensitive.

What this all means is local-parts may be case sensitive allthough it is
recommended that they not be. Most if not all major ESPs treat
local-parts case insensitively, but it is not a requirement. In other
words, Michael.d.parker at ga.com and michael.d.parker at ga.com may or may
not refer to the same mailbox, but only qa.com can say which.

>From Mailman's point of view, we use lower-case email addresses as keys
so it is not possible for two members of a single list to have email
addresses that differ only in case, but we remember the case-preserved
address and use that for sending mail. Thus, you can be a member of one
list with the case-preserved email Michael.d.parker at ga.com and a member
of another list with the case-preserved email michael.d.parker at ga.com.

Mailman 3 is different. there would be one global user, possibly with
multiple email addresses, but they should all be case-insensitively
distinct, and that single user can be a member of some set of lists, and
an owner of some, possibly overlapping set of lists and possibly other
roles like moderator or non-member allowed to post.

-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan

From mcepl at cepl.eu  Wed Jun  6 10:54:25 2018
From: mcepl at cepl.eu (=?UTF-8?Q?Mat=C4=9Bj?= Cepl)
Date: Wed, 06 Jun 2018 16:54:25 +0200
Subject: [Mailman-Users] Upgradeability of 2.1.* releases?
Message-ID: <1528296865.27157.0.camel@cepl.eu>

Hello,

Where could I find how smooth is the upgrade between different
2.1.* releases? Are there any tools for the conversion of the
configuration, if it is not completely automagical?

I work for SUSE and we have 2.1.14 on SLE 11, but for
https://bugs.launchpad.net/mailman/+bug/775294 it seems the only
redress is upgrade to the latest release, right?

Meanwhile, because of CVE-2016-6893 we will probably upgrade to
2.1.15, but from that to 2.1.26 is still a long way to go.

Any advice?

Thank you,

Mat?j Cepl


-- 
https://matej.ceplovi.cz/blog/, Jabber: mcepl at ceplovi.cz
GPG Finger: 3C76 A027 CA45 AD70 98B5  BC1D 7920 5802 880B C9D8
 
Thou shalt not nede to be afrayed for any bugges by night.
  -- Coverdale's 1535 translation of Psalm 91
     (or Christopher Higley's 1972 thesis explaining why
      programmers' are nocturnal beasts)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part
URL: <http://mail.python.org/pipermail/mailman-users/attachments/20180606/e49fd3ac/attachment-0001.sig>

From enseikou at gmail.com  Wed Jun  6 11:41:02 2018
From: enseikou at gmail.com (=?UTF-8?Q?Rub=c3=a9n_Fern=c3=a1ndez_Asensio?=)
Date: Wed, 6 Jun 2018 17:41:02 +0200
Subject: [Mailman-Users] Cascading lists
In-Reply-To: <018e1fd5-d3a5-1c2f-ecd6-5c8a16e8c94f@msapiro.net>
References: <7aa0be49-9cae-d97a-7937-0dd11ebd9ee3@gmail.com>
 <018e1fd5-d3a5-1c2f-ecd6-5c8a16e8c94f@msapiro.net>
Message-ID: <7555475b-142e-ee07-3f57-8cb2da555cd4@gmail.com>

I'm now trying to make an umbrella list encompassing both lists. 
Unfortunately, the wiki's wording is extremely poor on this issue:
https://wiki.list.org/DOC/How%20do%20I%20set%20up%20an%20umbrella%20list%3F

After the sentence "posts from the umbrella list will be held for 
"implicit destination" by a sublist." it's simply undeciferable.
"Taking these in reverse order.." Really? This is just a very badly 
planned text, if at all. What if I don't need sublist members to post to 
the umbrella list? What do I have to do?

I subscribed both lists to the umbrella list, but both are rejecting 
messages from the umbrella.
What are the exact steps I have to follow from now? One by one, and not 
"in reverse order", please.

Ruben Fernandez

El 04/06/18 a les 04:01, Mark Sapiro ha escrit:
> On 06/02/2018 11:53 PM, Rub?n Fern?ndez Asensio wrote:
>> Hello all,
>> I'm a new list administrator and a bit lost among Mailman's many
>> features. Could you please give some advice?
>> I'm trying to implement an announcement list and an unmoderated
>> discussion list, and having the second receive all mail sent to the
>> first one. The announcement list will prevent everybody but a few
>> addresses to post, and will attach a personalized footer to every post
>> with a link to the subscriber's option page. The discussion list will
>> attach its own generalized footer.
> 
> 
> See this FAQ article for advice on setting up an announcement list
> <https://wiki.list.org/x/4030685>.
> 
> 
>> In sum, I want a single place to manage permissions to send
>> announcements to both lists. I don't care about duplicates, as I want
>> people to actively unsubscribe from the announcement list if they've
>> joined both by mistake. However, it would be nice if the announcements
>> received by the discussion list wouldn't have any personalized footer.
> 
> 
> OK.
> 
> 
>> Also, I want subscribers of the discussion list to be able to send
>> replies to the announcement into the discussion list itself, whereas
>> subscribers of the announcement list will get their own 'Reply-to' heading.
>> What's the best setup to achieve this? Umbrella lists, sibling lists, or
>> something else?
> 
> 
> There are pluses and minuses to both umbrella lists and sibling lists.
> There are FAQs you should read if you haven't already. They are
> <https://wiki.list.org/x/4030574> and <https://wiki.list.org/x/4030540>.
> 
> I'm going to assume that neither list will have digest members. That
> adds an additional complication.
> 
> Your choices are:
> 
> 1) Add the discussion list address to regular_include_lists of the
> announce list. If you do this everyone will get announcement list posts
> from the announcement list. These will have the announcement list's
> footer. The members of the discussion list who aren't members of the
> announce list will get the post from the announce list. It appears that
> you want to munge Reply-To: in some way on both lists (I'll refrain from
> giving my opinion on this). Here, the message received by the discussion
> list members who aren't announce list members will have the footer and
> Reply-To: of the announce list. You probably don't want that.
> 
> 2) Subscribe the discussion list to the announce list. This means
> members of either list will receive the posts to the announce list from
> their own list with its footer and Reply-To: and members of both lists
> will receive the post from both lists. This seems more like what you
> want, but there are two kinds of issues.
> 
> Issue #1 is acceptance of posts to the announce list by the discussion
> list. This is discussed in the FAQ at <https://wiki.list.org/x/4030574>.
> 
> Issue #2 is an Umbrella list is a list whose members are all other
> lists. Lists with both individuals and one or more lists as members are
> an in between configuration that isn't well supported. Your issue is
> whether or not to set the announce list as an umbrella list. If you
> don't, anyone can request a password reminder and it will be sent to the
> entire discussion list. Because of this, you can set the announce list
> umbrella_list to Yes. This, at least with default umbrella_member_suffix
> will send these to the owner of the discussion list instead, but it also
> means that individual members of the announce list can't get password
> reminders or subscription confirmation requests.
> 

From cpz at tuunq.com  Wed Jun  6 11:57:42 2018
From: cpz at tuunq.com (Carl Zwanzig)
Date: Wed, 6 Jun 2018 08:57:42 -0700
Subject: [Mailman-Users] Upgradeability of 2.1.* releases?
In-Reply-To: <1528296865.27157.0.camel@cepl.eu>
References: <1528296865.27157.0.camel@cepl.eu>
Message-ID: <87e685c6-a8ce-29fb-ed48-1e29c4c0d2b3@tuunq.com>

On 6/6/2018 7:54 AM, Mat?j Cepl wrote:
> Where could I find how smooth is the upgrade between different
> 2.1.* releases? Are there any tools for the conversion of the
> configuration, if it is not completely automagical?

Generally, if you're upgrading via source (instead of some distro's 
package), going from 2.1.x to current is automagic.  Most of the problems 
seem to be with packages, which may have been customized for different file 
locations.

See- 
https://wiki.list.org/DOC/4.80%20How%20do%20I%20upgrade%20from%20Mailman%202.1.x%20to%20a%20later%20Mailman%202.1.y%3F

If you're back at 2.1.15, I'd definitely update.

Later,

z!

From mark at msapiro.net  Wed Jun  6 12:22:42 2018
From: mark at msapiro.net (Mark Sapiro)
Date: Wed, 6 Jun 2018 09:22:42 -0700
Subject: [Mailman-Users] Upgradeability of 2.1.* releases?
In-Reply-To: <1528296865.27157.0.camel@cepl.eu>
References: <1528296865.27157.0.camel@cepl.eu>
Message-ID: <807eaa90-a883-4ab6-c296-ce47cd40ac42@msapiro.net>

On 06/06/2018 07:54 AM, Mat?j Cepl wrote:
> Hello,
> 
> Where could I find how smooth is the upgrade between different
> 2.1.* releases? Are there any tools for the conversion of the
> configuration, if it is not completely automagical?


You could read the UPGRADING document in the source distribution.

To upgrade any 2.1.5+ release to  the latest release is very
straightforward except 2.1.18+ requires that you have the Python
dnspython package. This is discussed in the "UPGRADING FROM 2.1.5+ to
2.1.18+" section of the UPGRADING document.

When 'make install' detects a version change, it runs
Mailman/versions.py which does any necessary conversions.


> Any advice?


Just do it. Unpack the current Mailman 2.1.26 release (or wait for
2.1.27 which is coming soon, or grab the branch from
<https://code.launchpad.net/~mailman-coders/mailman/2.1> which is what's
running on the @python.org lists), run 'configure' with the same options
as you used on the current install and then 'make install'.

Also note that every time a list is instantiated, its data_version is
checked against that of the installation and if it is older, it is
automatically upgraded.

-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <http://mail.python.org/pipermail/mailman-users/attachments/20180606/1f02483b/attachment.sig>

From mark at msapiro.net  Wed Jun  6 12:42:05 2018
From: mark at msapiro.net (Mark Sapiro)
Date: Wed, 6 Jun 2018 09:42:05 -0700
Subject: [Mailman-Users] Cascading lists
In-Reply-To: <7555475b-142e-ee07-3f57-8cb2da555cd4@gmail.com>
References: <7aa0be49-9cae-d97a-7937-0dd11ebd9ee3@gmail.com>
 <018e1fd5-d3a5-1c2f-ecd6-5c8a16e8c94f@msapiro.net>
 <7555475b-142e-ee07-3f57-8cb2da555cd4@gmail.com>
Message-ID: <9d731f5c-f2dc-2198-6440-c1d796dfd146@msapiro.net>

On 06/06/2018 08:41 AM, Rub?n Fern?ndez Asensio wrote:
> I'm now trying to make an umbrella list encompassing both lists.
> Unfortunately, the wiki's wording is extremely poor on this issue:
> https://wiki.list.org/DOC/How%20do%20I%20set%20up%20an%20umbrella%20list%3F
> 
> After the sentence "posts from the umbrella list will be held for
> "implicit destination" by a sublist." it's simply undeciferable.
> "Taking these in reverse order.." Really? This is just a very badly
> planned text, if at all. What if I don't need sublist members to post to
> the umbrella list? What do I have to do?


The text is clear to me, but then I wrote it. What it says is there are
3 issues, bullet points 1, 2 and 3, and taking these in reverse order,
i.e. point 3 first and then point 2 and finally point 1.

I suppose instead of

"Taking these in reverse order, If a sublist's ..."

it could say

"The third issue is if a sublist's ..."

or

"The last of these issues is if a sublist's ..."

What do you think.


> I subscribed both lists to the umbrella list, but both are rejecting
> messages from the umbrella.
> What are the exact steps I have to follow from now? One by one, and not
> "in reverse order", please.


Why are the messages being rejected? Which of ther three bullet points
applies?

If it's point 1, scroll down to "The first issue can be hardest to deal
with." and read that.

If it's point 2, read the 4 paragraphs beginning with "The second issue
is when ..."

If it's point 3, add the posting address of the umbrella list to Privacy
options...->Recipient filters->acceptable_aliases of each of the sub-lists.

If you really don't have members of the sublists posting to the
umbrella, point 1 and possibly point 2 don't apply.

-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan

From enseikou at gmail.com  Wed Jun  6 16:49:30 2018
From: enseikou at gmail.com (=?UTF-8?Q?Rub=c3=a9n_Fern=c3=a1ndez_Asensio?=)
Date: Wed, 6 Jun 2018 22:49:30 +0200
Subject: [Mailman-Users] Cascading lists
In-Reply-To: <9d731f5c-f2dc-2198-6440-c1d796dfd146@msapiro.net>
References: <7aa0be49-9cae-d97a-7937-0dd11ebd9ee3@gmail.com>
 <018e1fd5-d3a5-1c2f-ecd6-5c8a16e8c94f@msapiro.net>
 <7555475b-142e-ee07-3f57-8cb2da555cd4@gmail.com>
 <9d731f5c-f2dc-2198-6440-c1d796dfd146@msapiro.net>
Message-ID: <165e1a36-fac7-db7e-c949-b43ab31dc150@gmail.com>



El 06/06/18 a les 18:42, Mark Sapiro ha escrit:
> 
> The text is clear to me, but then I wrote it. What it says is there are
> 3 issues, bullet points 1, 2 and 3, and taking these in reverse order,
> i.e. point 3 first and then point 2 and finally point 1.

I'm a language teacher and you can have my professional assessment for 
free: it is a very unclear text.

There aren't three issues but 2: either sublist members can't post to 
the umbrella list, or the umbrella list can't post to the sublists. And 
you have to tell the reader how to know what's causing the second issue, 
if it can really be caused by two different settings.

Anyway these issues, and especially the second, just defeat the purpose 
of an umbrella list, which means the umbrella list is only half set up, 
because you're holding the reader in the middle of the procedure instead 
of going straight through it. Wy don't you just tell us step two instead 
of rambling about what happens if you only do step one?

> Why are the messages being rejected? Which of ther three bullet points
> applies?

Well, how am I supposed to know? The Wiki doesn't describe the symptoms 
for each of them, if they're supposed to look different at all. All I 
get is a notification from each list's "bounces" address that the 
message was automatically discarded.

> If it's point 1, scroll down to "The first issue can be hardest to deal
> with." and read that.
> 
> If it's point 2, read the 4 paragraphs beginning with "The second issue
> is when ..."
> 
> If it's point 3, add the posting address of the umbrella list to Privacy
> options...->Recipient filters->acceptable_aliases of each of the sub-lists.

What about putting them in their logical order?
Also, when you write "There are a few ways to deal with this" in the 
middle of what is supposed to be issue 2, you should disentangle that 
mess into clearly numbered paragraphs 2.1, 2.2 and 2.3.

> If you really don't have members of the sublists posting to the
> umbrella, point 1 and possibly point 2 don't apply.
> 

I just added the umbrella's address to the "acceptable_aliases" of one 
of the sublists but they're both still discarding messages from the 
umbrella.

Seriously, if you give a title like "How do I set up an umbrella list?" 
to a wiki article, you'd better write it like a howto, with a step by 
step procedure like "if you want A, do either B and C or D and E", 
without getting distracted explaining the technical nitty-gritty of why 
you have to set this and this like that. Or get all that out of the way 
and into a footnote. On the other hand, you're too scarce on really 
necessary information: what's the "@Listname syntax" that might fix the 
second problem?

From brentk at birs.ca  Wed Jun  6 17:26:44 2018
From: brentk at birs.ca (Brent Kearney)
Date: Wed, 6 Jun 2018 15:26:44 -0600
Subject: [Mailman-Users] mailman-2.1.26: `make install` fails
In-Reply-To: <0f239147-deda-b02c-0c6c-9e1a1517de37@msapiro.net>
References: <904FDA08-BA30-4687-9CE4-441BA6412A53@birs.ca>
 <813787ab-c496-80f6-5382-08fdbdd51b51@msapiro.net>
 <C0766BA9-E604-449E-BD15-44AE7B388745@birs.ca>
 <0f239147-deda-b02c-0c6c-9e1a1517de37@msapiro.net>
Message-ID: <04DEB36E-E4C2-417C-A10B-29D306688D30@birs.ca>

That was the first thing I tried :). It is whatever version of make shipped with SunStudio 12, around 2008, I think. I wouldn?t worry about this, its an edge-case, and was easy to monkey-patch myself to make it work. In retrospect, I should have run `gmake`, for GNU make.

$ make --help
Usage : make [ -f makefile ][ -K statefile ]... [ -d ][ -dd ][ -D ][ -DD ]
             [ -e ][ -i ][ -k ][ -n ][ -p ][ -P ][ -q ][ -r ][ -s ][ -S ][ -t ]
             [ -u ][ -w ][ -V ][ target... ][ macro=value... ][ "macro +=value"... ]
make: Fatal error: Missing argument after `?'

$ make --version
make: Warning: Ignoring DistributedMake -v option
make: Warning: Ignoring DistributedMake -o option
make: Fatal error: No dmake output dir argument after -o flag

Best wishes,
Brent



> On Jun 5, 2018, at 15:10, Mark Sapiro <mark at msapiro.net> wrote:
> 
> On 06/05/2018 01:40 PM, Brent Kearney wrote:
>> Thanks Mark; its an old Sun Solaris 10 system. I?m not sure how to get the version from make itself, but the GCC version is 3.4.3.
> 
> 
> Try
> 
> make --version
> 
> or if that doesn't work,
> 
> make --help
> 
> to see the options.
> 
> -- 
> Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
> San Francisco Bay Area, California    better use your sense - B. Dylan
> ------------------------------------------------------
> Mailman-Users mailing list Mailman-Users at 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/brentk%40birs.ca


From mark at msapiro.net  Wed Jun  6 17:31:53 2018
From: mark at msapiro.net (Mark Sapiro)
Date: Wed, 6 Jun 2018 14:31:53 -0700
Subject: [Mailman-Users] Cascading lists
In-Reply-To: <165e1a36-fac7-db7e-c949-b43ab31dc150@gmail.com>
References: <7aa0be49-9cae-d97a-7937-0dd11ebd9ee3@gmail.com>
 <018e1fd5-d3a5-1c2f-ecd6-5c8a16e8c94f@msapiro.net>
 <7555475b-142e-ee07-3f57-8cb2da555cd4@gmail.com>
 <9d731f5c-f2dc-2198-6440-c1d796dfd146@msapiro.net>
 <165e1a36-fac7-db7e-c949-b43ab31dc150@gmail.com>
Message-ID: <e4e4ccdf-5370-20ab-1e1f-58006f8342a7@msapiro.net>

On 06/06/2018 01:49 PM, Rub?n Fern?ndez Asensio wrote:
> 
> I'm a language teacher and you can have my professional assessment for
> free: it is a very unclear text.
> 
> There aren't three issues but 2: either sublist members can't post to
> the umbrella list, or the umbrella list can't post to the sublists. And
> you have to tell the reader how to know what's causing the second issue,
> if it can really be caused by two different settings.


Thank you for your opinion. It is after all a wiki and if you look at
<https://wiki.list.org/DOC/How%20do%20I%20set%20up%20an%20umbrella%20list%3F?action=info>
you'll see that the language actually predates any of my edits and
despite what I said earlier, I didn't write the parts that offend you.

Anyway, If you are willing to create an account on the wiki, I'll be
happy to give you write permission and you can update the page as you
see fit.


>> Why are the messages being rejected? Which of ther three bullet points
>> applies?
> 
> Well, how am I supposed to know? The Wiki doesn't describe the symptoms
> for each of them, if they're supposed to look different at all. All I
> get is a notification from each list's "bounces" address that the
> message was automatically discarded.


Look in Mailman's vette log and see if that gives a reason. If not, do
the cautious thing one does when experimenting and change all the list
settings that are currently "Discard" to "Hold" and see why the messages
are held.

I suspect your issue is that the sublist(s) are discarding the message
from the umbrella because Privacy options... -> Sender filters ->
generic_nonmember_action is Discard and the post is not from a list
member. This is the second issue.
	


> On the other hand, you're too scarce on really
> necessary information: what's the "@Listname syntax" that might fix the
> second problem?


It is a way to reference all the members of a different list in a list's
*_these_nonmembers (accept_these_nonmembers in this case. Follow the
(Details for accept_these_nonmembers) link in the admin Privacy
options... -> Sender filters UI.

-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan

From enseikou at gmail.com  Fri Jun  8 03:05:26 2018
From: enseikou at gmail.com (=?UTF-8?Q?Rub=c3=a9n_Fern=c3=a1ndez_Asensio?=)
Date: Fri, 8 Jun 2018 09:05:26 +0200
Subject: [Mailman-Users] Cascading lists
In-Reply-To: <e4e4ccdf-5370-20ab-1e1f-58006f8342a7@msapiro.net>
References: <7aa0be49-9cae-d97a-7937-0dd11ebd9ee3@gmail.com>
 <018e1fd5-d3a5-1c2f-ecd6-5c8a16e8c94f@msapiro.net>
 <7555475b-142e-ee07-3f57-8cb2da555cd4@gmail.com>
 <9d731f5c-f2dc-2198-6440-c1d796dfd146@msapiro.net>
 <165e1a36-fac7-db7e-c949-b43ab31dc150@gmail.com>
 <e4e4ccdf-5370-20ab-1e1f-58006f8342a7@msapiro.net>
Message-ID: <5368baeb-0da9-145d-9e60-49effe95599e@gmail.com>


Finally I got it working!

As for your offer to edit the wiki, thanks, but I don't have time to 
test all the different possible setups. I can only offer information for 
one, which would be as follows:

"If you want an umbrella list to post anonymous announcements to several 
sublists at once, always getting the appropriate footer from each list, 
and not allowing sublist members to post, follow this procedure:

1. Create the umbrella list and set it up as anonymous (General Options 
 > anonymous_list) and as umbrella (General Options > umbrella_list).

2. Add the sublists' posting addresses as members of the umbrella list.

3. Either add the addresses of people allowed to post to the umbrella as 
umbrella members, or authorize them to post as nonmembers (Privacy > 
Sender filters > accept_these_nonmembers).

4. In every sublist, put the umbrella's posting address as accepted 
non-member (Privacy > Sender filters > accept_these_nonmembers).

5. In every sublist, put the umbrella's posting address as acceptable 
alias (Privacy > Recipient filters > acceptable_aliases). This last step 
is necessary only if require_explicit_destination is set to 'Yes'.

If you don't get the expected results, check the /var/log/mailman/vette 
log and the value of the USE_ENVELOPE_SENDER directive in mm_cfg.py or 
Defaults.py."

And then you could add footnotes and alternative fixes to debug the 
procedure. However, you'd need to add two more howtos on setting up 
non-anonymous umbrellas and cross-posting umbrellas, which I didn't try. 
In any way, that messy wiki must be fixed. Features won't be used unless 
they're well documented.

Ruben Fernandez

El 06/06/18 a les 23:31, Mark Sapiro ha escrit:
> On 06/06/2018 01:49 PM, Rub?n Fern?ndez Asensio wrote:
> 
> Thank you for your opinion. It is after all a wiki and if you look at
> <https://wiki.list.org/DOC/How%20do%20I%20set%20up%20an%20umbrella%20list%3F?action=info>
> you'll see that the language actually predates any of my edits and
> despite what I said earlier, I didn't write the parts that offend you.
> 
> Anyway, If you are willing to create an account on the wiki, I'll be
> happy to give you write permission and you can update the page as you
> see fit.
> 
> Look in Mailman's vette log and see if that gives a reason. If not, do
> the cautious thing one does when experimenting and change all the list
> settings that are currently "Discard" to "Hold" and see why the messages
> are held.
> 
> I suspect your issue is that the sublist(s) are discarding the message
> from the umbrella because Privacy options... -> Sender filters ->
> generic_nonmember_action is Discard and the post is not from a list
> member. This is the second issue.
> 	
> 
> 
>> On the other hand, you're too scarce on really
>> necessary information: what's the "@Listname syntax" that might fix the
>> second problem?
> 
> 
> It is a way to reference all the members of a different list in a list's
> *_these_nonmembers (accept_these_nonmembers in this case. Follow the
> (Details for accept_these_nonmembers) link in the admin Privacy
> options... -> Sender filters UI.
> 

From mmlists at ds-gmbh.de  Sat Jun  9 11:23:55 2018
From: mmlists at ds-gmbh.de (Martin Schulte)
Date: Sat, 9 Jun 2018 17:23:55 +0200
Subject: [Mailman-Users] Some patterns for ban_list and script to
 automatically update it
Message-ID: <20180609172355.251c3c9f165b3e7e5e9ee461@ds-gmbh.de>

Hello Mailman-Users,

to cope with the still ongoing subscription spam I've started to maintain
a list of patterns and a script to automatically load them to a list (in
case to can't/don't want to use GLOBAL_BAN_LIST).

Feel free to access them via

  git clone https://github.com/noabospam/abospam.git

Greetings,

Martin

From mark at msapiro.net  Sat Jun  9 12:54:58 2018
From: mark at msapiro.net (Mark Sapiro)
Date: Sat, 9 Jun 2018 09:54:58 -0700
Subject: [Mailman-Users] Some patterns for ban_list and script to
 automatically update it
In-Reply-To: <20180609172355.251c3c9f165b3e7e5e9ee461@ds-gmbh.de>
References: <20180609172355.251c3c9f165b3e7e5e9ee461@ds-gmbh.de>
Message-ID: <73ff60d6-a21c-3fbb-d1ed-440725d9aefb@msapiro.net>

On 6/9/18 8:23 AM, Martin Schulte wrote:
> 
> Feel free to access them via
> 
>   git clone https://github.com/noabospam/abospam.git


The README.txt is missing a slash at

  cp update_banlist.py /usr/lib/mailman bin

Also, you might want to mention using the --all option to withlist to do
all lists.

-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan

From brian at emwd.com  Sun Jun 10 14:21:06 2018
From: brian at emwd.com (Brian Carpenter)
Date: Sun, 10 Jun 2018 14:21:06 -0400
Subject: [Mailman-Users] Repeating Outgoing Messages
Message-ID: <beb901d400e7$cc9ec6b0$65dc5410$@emwd.com>

Dear Mailman Community,

 

I have a strange issue that has been occurring for the last 2 weeks. One of
our mailman servers continues to have 4-5 messages stuck in the qfiles/out
folder. These messages are being removed and then readded to the folder. The
same messages over and over and over. It is causing significant I/O usage. I
have to stop the mailman server and then manually remove the messages. They
are coming from one list via different members. I checked the list archives
and there is only one copy of each message listed in the archive and they
are not being resent to list members. It's just that these 4/5 messages are
being removed and then rewritten to the qfiles/out folder over and over.
Suggestions?

 



 

Brian Carpenter
Owner



Providing Mailman Hosting and more for over 15 years.


T: 336.755.0685
E: brian at emwd.com
www.emwd.com <http://www.emwd.com> 

www.mailmanhost.com <http://www.mailmanhost.com> 

 

 

 <https://www.facebook.com/pages/EMWDcom/192156034142506>
<http://www.linkedin.com/in/brianemwd> 



 


From mark at msapiro.net  Sun Jun 10 17:28:39 2018
From: mark at msapiro.net (Mark Sapiro)
Date: Sun, 10 Jun 2018 14:28:39 -0700
Subject: [Mailman-Users] Repeating Outgoing Messages
In-Reply-To: <beb901d400e7$cc9ec6b0$65dc5410$@emwd.com>
References: <beb901d400e7$cc9ec6b0$65dc5410$@emwd.com>
Message-ID: <c69e4cc3-e81a-ca9a-5b3a-af982f987cac@msapiro.net>

On 6/10/18 11:21 AM, Brian Carpenter wrote:
> 
> I have a strange issue that has been occurring for the last 2 weeks. One of
> our mailman servers continues to have 4-5 messages stuck in the qfiles/out
> folder. These messages are being removed and then readded to the folder. The
> same messages over and over and over. It is causing significant I/O usage. I
> have to stop the mailman server and then manually remove the messages. They
> are coming from one list via different members. I checked the list archives
> and there is only one copy of each message listed in the archive and they
> are not being resent to list members. It's just that these 4/5 messages are
> being removed and then rewritten to the qfiles/out folder over and over.
> Suggestions?


My first guess is they are outgoing messages that have encountered some
'retryable' SMTP error on one or more recipients and are being retried.

Normally, they would only be retried every 15 minutes, but possibly this
is occurring more often for some reason.

Are there entries in qfiles/retry?
What is logged in Mailman's smtp-failure log?
What does Mailman's bin/dumpdb show on the .pck (or maybe .bak - need a
-p option for that) files in qfiles/out and qfiles/retry? Look
particularly at the second object from dumpdb - bin/show-qfiles doesn't
show that.

What does the MTA say about these?

-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan

From brian at emwd.com  Sun Jun 10 19:06:43 2018
From: brian at emwd.com (Brian Carpenter)
Date: Sun, 10 Jun 2018 19:06:43 -0400
Subject: [Mailman-Users] Repeating Outgoing Messages
In-Reply-To: <c69e4cc3-e81a-ca9a-5b3a-af982f987cac@msapiro.net>
References: <beb901d400e7$cc9ec6b0$65dc5410$@emwd.com>
 <c69e4cc3-e81a-ca9a-5b3a-af982f987cac@msapiro.net>
Message-ID: <c07701d4010f$b3716f80$1a544e80$@emwd.com>

Hi Mark,

There are no entries in the qfiles/retry folder. There are entries in the
smtp-failure log. It seems the outgoing post is not being sent to the recips
(8) listed in the transaction though the post is being sent to the rest of
the list members. There are no log entries for those 8 in the exim_mainlog
file which is the outgoing MTA but there are corresponding entries for the
rest of the list members. Here is what the entry in the smtp-failure log is
showing:

Jun 10 18:20:34 2018 (16020) Low level smtp error: Connection unexpectedly
closed, msgid: <BECAFE5D-21EE-478C-B042-2EFA8A3244F1 at gmail.com>
Jun 10 18:20:34 2018 (16020) delivery to *****@***** failed with code -1:
Connection unexpectedly closed

The last line is repeated for each address in the transaction.

The transaction is being re-tried every 2-3 seconds.

Brian Carpenter
Owner

Providing Cloud Services and more for over 15 years.

T: 336.755.0685
E: brian at emwd.com
www.emwd.com

?



> -----Original Message-----
> From: Mailman-Users <mailman-users-
> bounces+brian=emwd.com at python.org> On Behalf Of Mark Sapiro
> Sent: Sunday, June 10, 2018 5:29 PM
> To: mailman-users at python.org
> Subject: Re: [Mailman-Users] Repeating Outgoing Messages
> 
> On 6/10/18 11:21 AM, Brian Carpenter wrote:
> >
> > I have a strange issue that has been occurring for the last 2 weeks. One
of
> > our mailman servers continues to have 4-5 messages stuck in the
qfiles/out
> > folder. These messages are being removed and then readded to the folder.
> The
> > same messages over and over and over. It is causing significant I/O
usage. I
> > have to stop the mailman server and then manually remove the messages.
> They
> > are coming from one list via different members. I checked the list
archives
> > and there is only one copy of each message listed in the archive and
they
> > are not being resent to list members. It's just that these 4/5 messages
are
> > being removed and then rewritten to the qfiles/out folder over and over.
> > Suggestions?
> 
> 
> My first guess is they are outgoing messages that have encountered some
> 'retryable' SMTP error on one or more recipients and are being retried.
> 
> Normally, they would only be retried every 15 minutes, but possibly this
> is occurring more often for some reason.
> 
> Are there entries in qfiles/retry?
> What is logged in Mailman's smtp-failure log?
> What does Mailman's bin/dumpdb show on the .pck (or maybe .bak - need a
> -p option for that) files in qfiles/out and qfiles/retry? Look
> particularly at the second object from dumpdb - bin/show-qfiles doesn't
> show that.
> 
> What does the MTA say about these?
> 
> --
> Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
> San Francisco Bay Area, California    better use your sense - B. Dylan
> ------------------------------------------------------
> Mailman-Users mailing list Mailman-Users at 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/brian%40emwd.com


From brian at emwd.com  Sun Jun 10 19:11:03 2018
From: brian at emwd.com (Brian Carpenter)
Date: Sun, 10 Jun 2018 19:11:03 -0400
Subject: [Mailman-Users] Repeating Outgoing Messages
In-Reply-To: <c69e4cc3-e81a-ca9a-5b3a-af982f987cac@msapiro.net>
References: <beb901d400e7$cc9ec6b0$65dc5410$@emwd.com>
 <c69e4cc3-e81a-ca9a-5b3a-af982f987cac@msapiro.net>
Message-ID: <c07901d40110$4e168430$ea438c90$@emwd.com>

> On 6/10/18 11:21 AM, Brian Carpenter wrote:
> >
> > I have a strange issue that has been occurring for the last 2 weeks. One
of
> > our mailman servers continues to have 4-5 messages stuck in the
qfiles/out
> > folder. These messages are being removed and then readded to the folder.
> The
> > same messages over and over and over. It is causing significant I/O
usage. I
> > have to stop the mailman server and then manually remove the messages.
> They
> > are coming from one list via different members. I checked the list
archives
> > and there is only one copy of each message listed in the archive and
they
> > are not being resent to list members. It's just that these 4/5 messages
are
> > being removed and then rewritten to the qfiles/out folder over and over.
> > Suggestions?
> 
> 
> My first guess is they are outgoing messages that have encountered some
> 'retryable' SMTP error on one or more recipients and are being retried.
> 
> Normally, they would only be retried every 15 minutes, but possibly this
> is occurring more often for some reason.
> 
> Are there entries in qfiles/retry?
> What is logged in Mailman's smtp-failure log?
> What does Mailman's bin/dumpdb show on the .pck (or maybe .bak - need a
> -p option for that) files in qfiles/out and qfiles/retry? Look
> particularly at the second object from dumpdb - bin/show-qfiles doesn't
> show that.
> 
> What does the MTA say about these?
> 
> --
> Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
> San Francisco Bay Area, California    better use your sense - B. Dylan

I think I found the problem. Several of those members had periods at the end
of their email addresses.

Brian


From mark at msapiro.net  Sun Jun 10 19:40:31 2018
From: mark at msapiro.net (Mark Sapiro)
Date: Sun, 10 Jun 2018 16:40:31 -0700
Subject: [Mailman-Users] Repeating Outgoing Messages
In-Reply-To: <c07701d4010f$b3716f80$1a544e80$@emwd.com>
References: <beb901d400e7$cc9ec6b0$65dc5410$@emwd.com>
 <c69e4cc3-e81a-ca9a-5b3a-af982f987cac@msapiro.net>
 <c07701d4010f$b3716f80$1a544e80$@emwd.com>
Message-ID: <55a28eec-ab26-dba1-cf43-d91e62eb6467@msapiro.net>

On 6/10/18 4:06 PM, Brian Carpenter wrote:
> 
> There are no entries in the qfiles/retry folder. There are entries in the
> smtp-failure log. It seems the outgoing post is not being sent to the recips
> (8) listed in the transaction though the post is being sent to the rest of
> the list members. There are no log entries for those 8 in the exim_mainlog
> file which is the outgoing MTA but there are corresponding entries for the
> rest of the list members.


Yes, Exim logging does sometimes leave things to be desired.


> Here is what the entry in the smtp-failure log is
> showing:
> 
> Jun 10 18:20:34 2018 (16020) Low level smtp error: Connection unexpectedly
> closed, msgid: <BECAFE5D-21EE-478C-B042-2EFA8A3244F1 at gmail.com>
> Jun 10 18:20:34 2018 (16020) delivery to *****@***** failed with code -1:
> Connection unexpectedly closed
> 
> The last line is repeated for each address in the transaction.


And yet nothing in the exim log ...


> The transaction is being re-tried every 2-3 seconds.


This is the mystery. It is possibly a cPanel thing, but that seems not
too likely.

What should happen is after this failure, the message should be queued
in the retry queue to be retried at 15 minute intervals for 5 days and
then recorded as a bounce.

Why it isn't working like that here is the question.

-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan

From mark at msapiro.net  Sun Jun 10 19:42:44 2018
From: mark at msapiro.net (Mark Sapiro)
Date: Sun, 10 Jun 2018 16:42:44 -0700
Subject: [Mailman-Users] Repeating Outgoing Messages
In-Reply-To: <c07901d40110$4e168430$ea438c90$@emwd.com>
References: <beb901d400e7$cc9ec6b0$65dc5410$@emwd.com>
 <c69e4cc3-e81a-ca9a-5b3a-af982f987cac@msapiro.net>
 <c07901d40110$4e168430$ea438c90$@emwd.com>
Message-ID: <270e737c-f624-d64e-294b-0f28f99ee8ef@msapiro.net>

On 6/10/18 4:11 PM, Brian Carpenter wrote:
> 
> I think I found the problem. Several of those members had periods at the end
> of their email addresses.


OK, but that still doesn't answer why the messages are being continually
retried for weeks rather than being retried once in 15 minutes for 5 days.

What's in Mailman's error log?

-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan

From brian at emwd.com  Sun Jun 10 21:02:40 2018
From: brian at emwd.com (Brian Carpenter)
Date: Sun, 10 Jun 2018 21:02:40 -0400
Subject: [Mailman-Users] Repeating Outgoing Messages
In-Reply-To: <270e737c-f624-d64e-294b-0f28f99ee8ef@msapiro.net>
References: <beb901d400e7$cc9ec6b0$65dc5410$@emwd.com>
 <c69e4cc3-e81a-ca9a-5b3a-af982f987cac@msapiro.net>
 <c07901d40110$4e168430$ea438c90$@emwd.com>
 <270e737c-f624-d64e-294b-0f28f99ee8ef@msapiro.net>
Message-ID: <c0ff01d4011f$e6275ba0$b27612e0$@emwd.com>

> 
> OK, but that still doesn't answer why the messages are being continually
> retried for weeks rather than being retried once in 15 minutes for 5 days.
> 
> What's in Mailman's error log?
> 
> --
> Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
> San Francisco Bay Area, California    better use your sense - B. Dylan

Nothing in the error log that pertains to the issue. It does seem to only
happen if the post is coming from a Gmail user.

Brian


From jrolland194 at gmail.com  Mon Jun 11 07:36:30 2018
From: jrolland194 at gmail.com (Jeffrey Rolland)
Date: Mon, 11 Jun 2018 06:36:30 -0500
Subject: [Mailman-Users] Migrating Mailman to New Server (Same Domain)
Message-ID: <CAPw9k4m7LfwaXb-eb+sJCGO7Ub0yc0JuBdBQPPmN7och7gXgPg@mail.gmail.com>

I tried using your script. The tar_list.sh script works fine. But, for the
untar_list.sh script, I had two fairly big problems.

1) the mailman user account did not have a home director or shell; I fixed
those problems handily.

2) I got a ton of permission/owner errors trying to untar the archives. The
private archives on the new server appeared to have been owned by root,
while the public archives appeared to be owned by www.-data; neither
untar-ed well with the script being owned by mailman.

Can you help? I'd really like to migrate my server today, and this is my
last task before switching over the firewall exceptions to the new server's
inside-NAT IP address.

Thanks much in advance.

Sincerely,
-- 
Jeffrey Rolland
<jrolland194 at gmail.com>

"The weed of crime bears bitter fruit; crime does NOT pay! The Shadow
knows!"
 - The Shadow, _The Shadow_ (1994)

 -----BEGIN GEEK CODE BLOCK-----
Version: 3.1
GM d-- s:+ a+ C++>$ UL+>$
P? L+++>+++++$ E--- W+++>$ N+++>+++$ o? K--? !w--- !O---- !M- !V-- PS++
PE- Y? PGP+++ t+++ 5? X+ R+>$ tv++ !b DI+++>+++++ !D G+ e++++$ h+ r--
y++
------END GEEK CODE BLOCK------

FWIW, I've done two complete migrations of a number of mailman (v2)
lists as I've changed servers over the past few years. A couple of
scripts I've used have worked perfectly in every case. In every
migration, the basic Mailman installation is set up and running on the
new server. Mailman versions, as long as we're talking about v2.x.x,
are a no-nevermind.

The first, which runs on the old server is called tar_list.sh, is kept
in /usr/local/sbin and is run as root:

    #!/bin/sh
    if [ "$1" = "" ]; then
    	    echo 'Usage: tar_list.sh <listname>'
    	    exit
    fi

    if [ ! -e /var/lib/mailman/lists/$1 ]; then
    	    echo "$1: No such list!"
    	    exit
    fi

    mkdir /tmp/$1
    cd /var/lib/mailman/lists/

    echo Creating $1_list.tar.gz ....
    tar -czvf $1_list.tar.gz $1
    mv $1_list.tar.gz /tmp/$1

    cd /var/lib/mailman/archives/private/

    echo Creating $1_archive.tar.gz ....
    tar -czvf $1_archive.tar.gz $1
    mv  $1_archive.tar.gz /tmp/$1

    echo Creating $1_archive_mbox.tar.gz ....
    tar -czvf $1_archive_mbox.tar.gz $1.mbox
    mv $1_archive_mbox.tar.gz /tmp/$1

    if [ -L /var/lib/mailman/archives/public/$1 ]; then
    	    touch /tmp/$1/$1_archive_is_public
    fi

The second script, on the new server, lives in ~mailman/bin and is run
as the mailman user (which, on my server, has a real, usable shell):

    #!/bin/sh
    if [ "$2" = "" ]; then
            echo 'Usage: untar_list.sh <server> <listname>'
            exit
    fi

    cd ~/tmp/
    echo "Give root password on remote system ..."
    scp root@$1:/tmp/$2/* .
    cd /var/lib/mailman/lists/

    echo ""
    echo "Creating list $2 ..."
    tar -xzvpf ~/tmp/$2_list.tar.gz

    cd /var/lib/mailman/archives/private/

    echo ""
    echo "Creating archive for $2 ..."
    tar --same-owner -xzvpf ~/tmp/$2_archive.tar.gz

    echo "Creating archive mbox for $1 ..."
    tar --same-owner -xzvpf ~/tmp/$2_archive_mbox.tar.gz

    if [ -e ~/tmp/$2_archive_is_public ]; then
    	    ln -s /var/lib/mailman/archives/private/$2
/var/lib/mailman/archives/public/$2
    fi

    echo""
    echo "If no errors, delete files in ~/tmp and delete /tmp/$2
directory on remote system"

This does require (and this may be a show-stopper for some) that the
mailman user on the new system be able to ssh to the old server as
root. I'm sure there's an easy workaround for this, but since I've
always has full root access to my servers and run connections between
servers via encrypted VPNs, it's been simply a matter of modifying the
sshd_config file to allow this

From mark at msapiro.net  Mon Jun 11 10:59:40 2018
From: mark at msapiro.net (Mark Sapiro)
Date: Mon, 11 Jun 2018 07:59:40 -0700
Subject: [Mailman-Users] Migrating Mailman to New Server (Same Domain)
In-Reply-To: <CAPw9k4m7LfwaXb-eb+sJCGO7Ub0yc0JuBdBQPPmN7och7gXgPg@mail.gmail.com>
References: <CAPw9k4m7LfwaXb-eb+sJCGO7Ub0yc0JuBdBQPPmN7och7gXgPg@mail.gmail.com>
Message-ID: <327ac394-75db-efcf-3cb9-b207423286eb@msapiro.net>

On 6/11/18 4:36 AM, Jeffrey Rolland wrote:
> I tried using your script. The tar_list.sh script works fine. But, for the
> untar_list.sh script, I had two fairly big problems.


Where did you find these scripts? They are not distributed by the GNU
mailman project.


> 1) the mailman user account did not have a home director or shell; I fixed
> those problems handily.


If your new server has a Debian/Ubuntu Mailman package, the Mailman user
is 'list', not 'mailman'.


> 2) I got a ton of permission/owner errors trying to untar the archives. The
> private archives on the new server appeared to have been owned by root,
> while the public archives appeared to be owned by www.-data; neither
> untar-ed well with the script being owned by mailman.


The best way to move archives is to just move the
archives/private/<listname>.mbox/<listname>.mbox file from the old
server to the new and then run Mailman's

bin/arch --wipe <listname>

on the new server. See <https://wiki.list.org/x/4030624>.

-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan

From jimpop at domainmail.org  Mon Jun 11 13:26:47 2018
From: jimpop at domainmail.org (Jim Popovitch)
Date: Mon, 11 Jun 2018 13:26:47 -0400
Subject: [Mailman-Users] pending subscription to list "mailman"
Message-ID: <1528738007.3840.1.camel@domainmail.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Hello,

For some unknown reason a legitimate human sent a subscribe request to 
mailman-subscribe at domain.tld and now I'm receiving pending subscriber
notifications for the "mailman" list, which isn't a list with an
available web interface.  Is there a cmd line way to discard pending
subscribers?

Also, should the mailman/data/aliases.db even contain aliases for the
mailman list?

tia,

- -Jim P.
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEPxwe8uYBnqxkbORSJxVetMRaJwUFAlsesNcACgkQJxVetMRa
JwVVCw//bsx0xZaY/9ypdkkhf/+zNEGB0i4yauLogAsZyeGaWz/CS2oCrlei6Ghm
0f95MdCBAegtbkRizQP0iMmYOsUmyul0K/22Cp8UJiHegqeMvsA99yvMgREiuhck
nMDg1A+7s2yYy7VaZw390OMMWnfB23zjfGUQqvuGhR21mK8HyygxEYtzXK4jj2Sf
n1EiEc9+UxiVIK27ZhiCkSm0jY5OJ5GaQpCV9KJ7x1cEn33suIzUwksiXvWeHJNu
YgQ5tUZcY9f1Vk/iF6h5dcR05N+Dj3afnwp0p8SHesOlep2zwyIeH2UD2EbvuFTv
dOlDpjspnhhbMzm2m1A+bDZaNd2wlBoC7Hzdm7Zru9LjuZtEz90HQvgAcD3rNEUj
AtH1U/CKrmC9quDQFZPGdhzqIo3svFyJgF9havCYdUq3Dyt+FP6nVIR/D+amRWZQ
CMrtAiyMJUPMdtj3UnsuZ3dH8VJSpxIf2nx0ztOhLGhIJcSs4aVe0dJ8iFwOaB/C
3rwtpJ9FDWyr2K2AQ8js7eepHQpp6ccxqkdC/D1E5L7bmPAz+HaBrNBeGACpFUn/
+uy0HlA1r4UC80Jx76Tl1sf1IVmEiI3JdZCjnDkIbhWilfwZ0OHub8YV/MuMyTdI
dlExCvR95DGJMCOMUdVTKQNI3jZPORC3zX04YAvcRVvcWUrwSXM=
=ScFr
-----END PGP SIGNATURE-----


From mark at msapiro.net  Mon Jun 11 15:21:12 2018
From: mark at msapiro.net (Mark Sapiro)
Date: Mon, 11 Jun 2018 12:21:12 -0700
Subject: [Mailman-Users] pending subscription to list "mailman"
In-Reply-To: <1528738007.3840.1.camel@domainmail.org>
References: <1528738007.3840.1.camel@domainmail.org>
Message-ID: <3cc07d4c-9c69-fbc4-b51a-604871858e0b@msapiro.net>

On 6/11/18 10:26 AM, Jim Popovitch via Mailman-Users wrote:
> 
> For some unknown reason a legitimate human sent a subscribe request to 
> mailman-subscribe at domain.tld and now I'm receiving pending subscriber
> notifications for the "mailman" list, which isn't a list with an
> available web interface.  Is there a cmd line way to discard pending
> subscribers?

Why do you think there's no web interface. Have you tried going to
http(s)://any.of.your.domains/admindb/mailman/ ?

There are a couple of scripts at <https://www.msapiro.net/scripts/>,
namely 'erase' and 'list_requests' that can do the discard.


> Also, should the mailman/data/aliases.db even contain aliases for the
> mailman list?


The address mailman at domain.tld is exposed in both the listinfo and admin
overview pages as a place for questions. Also,
mailman-bounces at domain.tld is the envelope sender of password reminders
and some owner notices and some MTA configurations don't accept outging
mail that isn't from a deliverable address, although I think this is
mostly an Exim issue and Exim doesn't use aliases.

Also, if you don't put a MAILTO in Mailman's crontab, any errors from
Mailman's crons will be sent to mailman at domain.tld.

For all these reasons, I recommend setting up the 'mailman' list with
the Mailman site admins as owners and members and setting
generic_nonmember_action to accept.

Anyway, the short answer to "should the mailman/data/aliases.db even
contain aliases for the mailman list?" is Yes, but if it makes sense in
your installation to remove them, you can.


-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 195 bytes
Desc: OpenPGP digital signature
URL: <http://mail.python.org/pipermail/mailman-users/attachments/20180611/39fbb9cd/attachment.sig>

From jimpop at domainmail.org  Mon Jun 11 15:28:19 2018
From: jimpop at domainmail.org (Jim Popovitch)
Date: Mon, 11 Jun 2018 15:28:19 -0400
Subject: [Mailman-Users] pending subscription to list "mailman"
In-Reply-To: <3cc07d4c-9c69-fbc4-b51a-604871858e0b@msapiro.net>
References: <1528738007.3840.1.camel@domainmail.org>
 <3cc07d4c-9c69-fbc4-b51a-604871858e0b@msapiro.net>
Message-ID: <1528745299.8940.1.camel@domainmail.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On Mon, 2018-06-11 at 12:21 -0700, Mark Sapiro wrote:
> On 6/11/18 10:26 AM, Jim Popovitch via Mailman-Users wrote:
> > 
> > For some unknown reason a legitimate human sent a subscribe request
> > to?
> > mailman-subscribe at domain.tld and now I'm receiving pending
> > subscriber
> > notifications for the "mailman" list, which isn't a list with an
> > available web interface.??Is there a cmd line way to discard
> > pending
> > subscribers?
> 
> Why do you think there's no web interface. Have you tried going to
> http(s)://any.of.your.domains/admindb/mailman/ ?

There's no web interface on domain.tld because it's the backend domain
that's hosting virtual lists.

Using one of the virtual domains, as you described, works to show the
pending sub request, but Submit action is based on mlist settings
(domain.tld) so the submit never occurs.

> There are a couple of scripts at <https://www.msapiro.net/scripts/>,
> namely 'erase' and 'list_requests' that can do the discard.

Perfect, thanks!

> 
> > Also, should the mailman/data/aliases.db even contain aliases for
> > the
> > mailman list?
> 
> 
> The address mailman at domain.tld is exposed in both the listinfo and
> admin
> overview pages as a place for questions. Also,
> mailman-bounces at domain.tld is the envelope sender of password
> reminders
> and some owner notices and some MTA configurations don't accept
> outging
> mail that isn't from a deliverable address, although I think this is
> mostly an Exim issue and Exim doesn't use aliases.
> 
> Also, if you don't put a MAILTO in Mailman's crontab, any errors from
> Mailman's crons will be sent to mailman at domain.tld.
> 
> For all these reasons, I recommend setting up the 'mailman' list with
> the Mailman site admins as owners and members and setting
> generic_nonmember_action to accept.
> 
> Anyway, the short answer to "should the mailman/data/aliases.db even
> contain aliases for the mailman list?" is Yes, but if it makes sense
> in
> your installation to remove them, you can.

I'm going to leave them but disable (comment out) the
subscribe/join/etc ones.

Thanks for the help!

- -Jim P.
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEPxwe8uYBnqxkbORSJxVetMRaJwUFAlsezVMACgkQJxVetMRa
JwVhrg/+NT5FhIwJzONvxuERO5KFPGKz4lYm0ofCEbvagu7YXaxMrU8u8obhb0ho
+pNyPpWSOM41Hk4Bkkwna0bSEakhDQV6NZcfwvvVB4lg39bbpEfYrZ/J/4hYhMwg
huTn4zYvH5mojJnRslRGODgTNQFJ6/mnitvuqvsYUVg1BuuAmL6FcExCTjCFUqcQ
a6YnWgKgvD3ij0innOCn/yyrafJ0yEHwjs2h3NWbUGd+wPKNSY6pPv8vt8ltujnw
ZCUj+Jd96+ihBdw9VSH1mUPzi8MHbFcOX3I4ULeldt9WrvQMofI5l6gU1bzp1qFq
3ISjENRfy7uCO6KDeJozxnJfpS90PP8Og1VWFQWH2/39Dw8TxeDCfsiRtf5fVtEL
HcHzxOjn4h73g4kdphaBuDJnlP12sECzViqEXCpzMJuj5kGP+n5iz6NUSTy89ysC
HSGQrY2WpuIan5XEBxVFOMbRNczOaZ4hulNP6/T212XezvAzwRDAkrMiJndhHZ6v
x6KkEkCI7tqjUJSa7KzpaWrjTwWwP/LXBZKuI0Y9cxgvAQMNbqy6grrRzn5VChje
INv+/vHCboMrhKdHoJjPWlNk3uuiRcj/YaUIJc0V+864G9jlJ1dTZNrR6JQIltJ+
SIYpDAKkRrhwRx60YtSBBGGQcVushHCiYjeNgJmNW5BjFFPeKok=
=rp6+
-----END PGP SIGNATURE-----


From turnbull.stephen.fw at u.tsukuba.ac.jp  Tue Jun 12 04:52:35 2018
From: turnbull.stephen.fw at u.tsukuba.ac.jp (Stephen J. Turnbull)
Date: Tue, 12 Jun 2018 17:52:35 +0900
Subject: [Mailman-Users] Migrating Mailman to New Server (Same Domain)
In-Reply-To: <327ac394-75db-efcf-3cb9-b207423286eb@msapiro.net>
References: <CAPw9k4m7LfwaXb-eb+sJCGO7Ub0yc0JuBdBQPPmN7och7gXgPg@mail.gmail.com>
 <327ac394-75db-efcf-3cb9-b207423286eb@msapiro.net>
Message-ID: <23327.35283.153716.839652@turnbull.sk.tsukuba.ac.jp>

Mark Sapiro writes:
 > On 6/11/18 4:36 AM, Jeffrey Rolland wrote:
 > > I tried using your script. The tar_list.sh script works fine. But, for the
 > > untar_list.sh script, I had two fairly big problems.
 > 
 > 
 > Where did you find these scripts? They are not distributed by the GNU
 > mailman project.

I suspect he's talking about Lindsay's scripts from
https://mail.python.org/pipermail/mailman-users/2013-November/075737.html

I wonder if his system might default to a non-GNU tar.

FWIW

Steve


-- 
Associate Professor              Division of Policy and Planning Science
http://turnbull.sk.tsukuba.ac.jp/     Faculty of Systems and Information
Email: turnbull at sk.tsukuba.ac.jp                   University of Tsukuba
Tel: 029-853-5175                 Tennodai 1-1-1, Tsukuba 305-8573 JAPAN

From fmouse at fmp.com  Tue Jun 12 11:16:54 2018
From: fmouse at fmp.com (Lindsay Haisley)
Date: Tue, 12 Jun 2018 10:16:54 -0500
Subject: [Mailman-Users] Migrating Mailman to New Server (Same Domain)
In-Reply-To: <23327.35283.153716.839652@turnbull.sk.tsukuba.ac.jp>
References: <CAPw9k4m7LfwaXb-eb+sJCGO7Ub0yc0JuBdBQPPmN7och7gXgPg@mail.gmail.com>
 <327ac394-75db-efcf-3cb9-b207423286eb@msapiro.net>
 <23327.35283.153716.839652@turnbull.sk.tsukuba.ac.jp>
Message-ID: <1528816614.127582.14.camel@fmp.com>

On Tue, 2018-06-12 at 17:52 +0900, Stephen J. Turnbull wrote:
> Mark Sapiro writes:
> ?> On 6/11/18 4:36 AM, Jeffrey Rolland wrote:
> ?> > I tried using your script. The tar_list.sh script works fine. But, for the
> ?> > untar_list.sh script, I had two fairly big problems.
> ?>?
> ?>?
> ?> Where did you find these scripts? They are not distributed by the GNU
> ?> mailman project.
> 
> I suspect he's talking about Lindsay's scripts from
> https://mail.python.org/pipermail/mailman-users/2013-November/075737.html
> 
> I wonder if his system might default to a non-GNU tar.

No, I use GNU tar.

These are pretty simple scripts, and I posted them pretty much as an
example of how _I_ automated the process of migrating lists. There are
some conditions on which this process depends, one being that remote
action as the root user on the new system be allowed by sshd
configuration. Another being that the versions and file and directory
layouts and ownerships on the old and new systems be sufficiently
congruent.

I didn't post these as drop-and-run scripts so much as illustrations of
how I automated the process, and how others might proceed to do so.
Sufficient knowledge of bash scripting and basic Unix permissions and
such may well be required to properly modify and use these scripts on
other systems.

-- 
Lindsay Haisley       | "The first casualty when
FMP Computer Services |         war comes is truth."
512-259-1190          |            
http://www.fmp.com    |     -- Hiram W Johnson


From acravens at uen.org  Tue Jun 12 11:33:53 2018
From: acravens at uen.org (Andy Cravens)
Date: Tue, 12 Jun 2018 15:33:53 +0000
Subject: [Mailman-Users] Unsubscribe emails - saved anywhere?
Message-ID: <69E77D11-D429-48D8-AF5E-FE052FFCB362@umail.utah.edu>

Using mailman 2.1.26.  When someone sends an unsubscribe email to a mailman server, does that email get saved anywhere after it is processed?

From mark at msapiro.net  Tue Jun 12 11:54:20 2018
From: mark at msapiro.net (Mark Sapiro)
Date: Tue, 12 Jun 2018 08:54:20 -0700
Subject: [Mailman-Users] Unsubscribe emails - saved anywhere?
In-Reply-To: <69E77D11-D429-48D8-AF5E-FE052FFCB362@umail.utah.edu>
References: <69E77D11-D429-48D8-AF5E-FE052FFCB362@umail.utah.edu>
Message-ID: <6ff45d41-6780-6730-7706-21b6c4413c68@msapiro.net>

On 6/12/18 8:33 AM, Andy Cravens wrote:
> Using mailman 2.1.26.  When someone sends an unsubscribe email to a mailman server, does that email get saved anywhere after it is processed?


No.

If you want them saved, you may be able to configure the MTA to save them.

-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan

From rclemings at gmail.com  Tue Jun 12 17:21:46 2018
From: rclemings at gmail.com (Russell Clemings)
Date: Tue, 12 Jun 2018 14:21:46 -0700
Subject: [Mailman-Users] change listinfo url?
Message-ID: <CAN7RX0YMj0iyn=_08Dpnvreg-3TWTeZFLha2H8Jn9Rg=D1Sbxg@mail.gmail.com>

The bots are killing me. I've set all of our lists to 'advertise' = 'no',
but the bots are still hitting the /mailman/listinfo/listname URLs.

Is there a straightforward way of changing that URL without changing the
list or host name? Maybe make it /mailman/listinfo1/listname?

All I can see in the faq/archives concerns changing the host/list name.



-- 
===============================================
Russell Clemings
<russell at clemings.com>
===============================================

From mark at msapiro.net  Tue Jun 12 17:34:45 2018
From: mark at msapiro.net (Mark Sapiro)
Date: Tue, 12 Jun 2018 14:34:45 -0700
Subject: [Mailman-Users] change listinfo url?
In-Reply-To: <CAN7RX0YMj0iyn=_08Dpnvreg-3TWTeZFLha2H8Jn9Rg=D1Sbxg@mail.gmail.com>
References: <CAN7RX0YMj0iyn=_08Dpnvreg-3TWTeZFLha2H8Jn9Rg=D1Sbxg@mail.gmail.com>
Message-ID: <a9f9f82f-46e6-201f-7c63-baf50cd07006@msapiro.net>

On 6/12/18 2:21 PM, Russell Clemings wrote:
> The bots are killing me. I've set all of our lists to 'advertise' = 'no',
> but the bots are still hitting the /mailman/listinfo/listname URLs.
> 
> Is there a straightforward way of changing that URL without changing the
> list or host name? Maybe make it /mailman/listinfo1/listname?


Rename mailman/cgi-bin/listinfo. Assuming your web server has something
like the apache

ScriptAlias /mailman/  /path/to/mailman/cgi-bin/

whatever you name it to is what goes in the URL.

-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan

From rclemings at gmail.com  Tue Jun 12 17:50:45 2018
From: rclemings at gmail.com (Russell Clemings)
Date: Tue, 12 Jun 2018 14:50:45 -0700
Subject: [Mailman-Users] change listinfo url?
In-Reply-To: <a9f9f82f-46e6-201f-7c63-baf50cd07006@msapiro.net>
References: <CAN7RX0YMj0iyn=_08Dpnvreg-3TWTeZFLha2H8Jn9Rg=D1Sbxg@mail.gmail.com>
 <a9f9f82f-46e6-201f-7c63-baf50cd07006@msapiro.net>
Message-ID: <CAN7RX0bai1-Ghh-U1iDr_xyQ3e9sf92fxc4WedFOMxRor-8t_A@mail.gmail.com>

Thanks, that works. But the listinfo_url variable (for the message footer)
seems unchanged. I tried withlist/fix_url and restarted Mailman but no luck.



On Tue, Jun 12, 2018 at 2:34 PM, Mark Sapiro <mark at msapiro.net> wrote:

> On 6/12/18 2:21 PM, Russell Clemings wrote:
> > The bots are killing me. I've set all of our lists to 'advertise' = 'no',
> > but the bots are still hitting the /mailman/listinfo/listname URLs.
> >
> > Is there a straightforward way of changing that URL without changing the
> > list or host name? Maybe make it /mailman/listinfo1/listname?
>
>
> Rename mailman/cgi-bin/listinfo. Assuming your web server has something
> like the apache
>
> ScriptAlias /mailman/  /path/to/mailman/cgi-bin/
>
> whatever you name it to is what goes in the URL.
>
> --
> Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
> San Francisco Bay Area, California    better use your sense - B. Dylan
> ------------------------------------------------------
> Mailman-Users mailing list Mailman-Users at 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/
> rclemings%40gmail.com
>



-- 
===============================================
Russell Clemings
<russell at clemings.com>
===============================================

From mark at msapiro.net  Tue Jun 12 18:00:36 2018
From: mark at msapiro.net (Mark Sapiro)
Date: Tue, 12 Jun 2018 15:00:36 -0700
Subject: [Mailman-Users] change listinfo url?
In-Reply-To: <CAN7RX0bai1-Ghh-U1iDr_xyQ3e9sf92fxc4WedFOMxRor-8t_A@mail.gmail.com>
References: <CAN7RX0YMj0iyn=_08Dpnvreg-3TWTeZFLha2H8Jn9Rg=D1Sbxg@mail.gmail.com>
 <a9f9f82f-46e6-201f-7c63-baf50cd07006@msapiro.net>
 <CAN7RX0bai1-Ghh-U1iDr_xyQ3e9sf92fxc4WedFOMxRor-8t_A@mail.gmail.com>
Message-ID: <f10e3490-35d5-6e46-0489-bc67b051b6ff@msapiro.net>

On 6/12/18 2:50 PM, Russell Clemings wrote:
> Thanks, that works. But the listinfo_url variable (for the message footer)
> seems unchanged. I tried withlist/fix_url and restarted Mailman but no luck.


You can edit msg_footer and digest_footer to put whatever you want
there. It may currently have something like

%(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s

you can edit the whole string or just the 'listinfo' part.

-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan

From rclemings at gmail.com  Tue Jun 12 18:29:56 2018
From: rclemings at gmail.com (Russell Clemings)
Date: Tue, 12 Jun 2018 15:29:56 -0700
Subject: [Mailman-Users] change listinfo url?
In-Reply-To: <f10e3490-35d5-6e46-0489-bc67b051b6ff@msapiro.net>
References: <CAN7RX0YMj0iyn=_08Dpnvreg-3TWTeZFLha2H8Jn9Rg=D1Sbxg@mail.gmail.com>
 <a9f9f82f-46e6-201f-7c63-baf50cd07006@msapiro.net>
 <CAN7RX0bai1-Ghh-U1iDr_xyQ3e9sf92fxc4WedFOMxRor-8t_A@mail.gmail.com>
 <f10e3490-35d5-6e46-0489-bc67b051b6ff@msapiro.net>
Message-ID: <CAN7RX0aoyxfUtZBF1i9D0Y48nWdNXC24UTxv5C6v7MP63iY_Nw@mail.gmail.com>

Good, thanks. Any way to change listinfo_url globally though? I'd like it
to be right on all the "listname list run by listowner" spaghetti on the
listinfo and admin pages as well. It looks to be used in some of the
"edithtml"  templates as well.

On Tue, Jun 12, 2018 at 3:00 PM, Mark Sapiro <mark at msapiro.net> wrote:

> On 6/12/18 2:50 PM, Russell Clemings wrote:
> > Thanks, that works. But the listinfo_url variable (for the message
> footer)
> > seems unchanged. I tried withlist/fix_url and restarted Mailman but no
> luck.
>
>
> You can edit msg_footer and digest_footer to put whatever you want
> there. It may currently have something like
>
> %(web_page_url)slistinfo%(cgiext)s/%(_internal_name)s
>
> you can edit the whole string or just the 'listinfo' part.
>
> --
> Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
> San Francisco Bay Area, California    better use your sense - B. Dylan
> ------------------------------------------------------
> Mailman-Users mailing list Mailman-Users at 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/
> rclemings%40gmail.com
>



-- 
===============================================
Russell Clemings
<russell at clemings.com>
===============================================

From mark at msapiro.net  Tue Jun 12 18:47:10 2018
From: mark at msapiro.net (Mark Sapiro)
Date: Tue, 12 Jun 2018 17:47:10 -0500
Subject: [Mailman-Users] change listinfo url?
In-Reply-To: <CAN7RX0aoyxfUtZBF1i9D0Y48nWdNXC24UTxv5C6v7MP63iY_Nw@mail.gmail.com>
References: <CAN7RX0YMj0iyn=_08Dpnvreg-3TWTeZFLha2H8Jn9Rg=D1Sbxg@mail.gmail.com>
 <a9f9f82f-46e6-201f-7c63-baf50cd07006@msapiro.net>
 <CAN7RX0bai1-Ghh-U1iDr_xyQ3e9sf92fxc4WedFOMxRor-8t_A@mail.gmail.com>
 <f10e3490-35d5-6e46-0489-bc67b051b6ff@msapiro.net>
 <CAN7RX0aoyxfUtZBF1i9D0Y48nWdNXC24UTxv5C6v7MP63iY_Nw@mail.gmail.com>
Message-ID: <C6D77537-CD9A-4AAC-B26F-3148D3039A9C@msapiro.net>

On June 12, 2018 5:29:56 PM CDT, Russell Clemings <rclemings at gmail.com> wrote:
>Good, thanks. Any way to change listinfo_url globally though? I'd like
>it
>to be right on all the "listname list run by listowner" spaghetti on
>the
>listinfo and admin pages as well. It looks to be used in some of the
>"edithtml"  templates as well.

You have to edit (I think multiple places in) the code. And rebuild the archives to get those. I just boarded a plane and can't say more at this time.



-- 
Mark Sapiro <mark at msapiro.net>
Sent from my Not_an_iThing with standards compliant, open source software.

From mmlists at ds-gmbh.de  Wed Jun 13 00:47:46 2018
From: mmlists at ds-gmbh.de (Martin Schulte)
Date: Wed, 13 Jun 2018 06:47:46 +0200
Subject: [Mailman-Users] change listinfo url?
In-Reply-To: <CAN7RX0YMj0iyn=_08Dpnvreg-3TWTeZFLha2H8Jn9Rg=D1Sbxg@mail.gmail.com>
References: <CAN7RX0YMj0iyn=_08Dpnvreg-3TWTeZFLha2H8Jn9Rg=D1Sbxg@mail.gmail.com>
Message-ID: <20180613064746.69d057ef424372730fd1797b@ds-gmbh.de>

Hi Russell!

On Tue, 12 Jun 2018 14:21:46 -0700
Russell Clemings <rclemings at gmail.com> wrote:

> The bots are killing me. 

Did you try https://github.com/noabospam/abospam ;-)

Greetings,

Martin

From rclemings at gmail.com  Wed Jun 13 10:51:29 2018
From: rclemings at gmail.com (Russell Clemings)
Date: Wed, 13 Jun 2018 07:51:29 -0700
Subject: [Mailman-Users] change listinfo url?
In-Reply-To: <20180613064746.69d057ef424372730fd1797b@ds-gmbh.de>
References: <CAN7RX0YMj0iyn=_08Dpnvreg-3TWTeZFLha2H8Jn9Rg=D1Sbxg@mail.gmail.com>
 <20180613064746.69d057ef424372730fd1797b@ds-gmbh.de>
Message-ID: <CAN7RX0aqfXreZKzFfJGfTr=gSwUyFnyS=sNRr0k=V2U1o3E=+w@mail.gmail.com>

Not yet, no. How often does your banlist get updated?

On Tue, Jun 12, 2018 at 9:47 PM, Martin Schulte <mmlists at ds-gmbh.de> wrote:

> Hi Russell!
>
> On Tue, 12 Jun 2018 14:21:46 -0700
> Russell Clemings <rclemings at gmail.com> wrote:
>
> > The bots are killing me.
>
> Did you try https://github.com/noabospam/abospam ;-)
>
> Greetings,
>
> Martin
> ------------------------------------------------------
> Mailman-Users mailing list Mailman-Users at 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/
> rclemings%40gmail.com
>



-- 
===============================================
Russell Clemings
<russell at clemings.com>
===============================================

From rclemings at gmail.com  Wed Jun 13 11:28:05 2018
From: rclemings at gmail.com (Russell Clemings)
Date: Wed, 13 Jun 2018 08:28:05 -0700
Subject: [Mailman-Users] change listinfo url?
In-Reply-To: <C6D77537-CD9A-4AAC-B26F-3148D3039A9C@msapiro.net>
References: <CAN7RX0YMj0iyn=_08Dpnvreg-3TWTeZFLha2H8Jn9Rg=D1Sbxg@mail.gmail.com>
 <a9f9f82f-46e6-201f-7c63-baf50cd07006@msapiro.net>
 <CAN7RX0bai1-Ghh-U1iDr_xyQ3e9sf92fxc4WedFOMxRor-8t_A@mail.gmail.com>
 <f10e3490-35d5-6e46-0489-bc67b051b6ff@msapiro.net>
 <CAN7RX0aoyxfUtZBF1i9D0Y48nWdNXC24UTxv5C6v7MP63iY_Nw@mail.gmail.com>
 <C6D77537-CD9A-4AAC-B26F-3148D3039A9C@msapiro.net>
Message-ID: <CAN7RX0Yvk3VdFyn1f61HszkQZ7P-euLQ6pBLzg=FpmogZE0c4A@mail.gmail.com>

Would it be easier just to hide the spaghetti on the listinfo pages?

On Tue, Jun 12, 2018 at 3:47 PM, Mark Sapiro <mark at msapiro.net> wrote:

> On June 12, 2018 5:29:56 PM CDT, Russell Clemings <rclemings at gmail.com>
> wrote:
> >Good, thanks. Any way to change listinfo_url globally though? I'd like
> >it
> >to be right on all the "listname list run by listowner" spaghetti on
> >the
> >listinfo and admin pages as well. It looks to be used in some of the
> >"edithtml"  templates as well.
>
> You have to edit (I think multiple places in) the code. And rebuild the
> archives to get those. I just boarded a plane and can't say more at this
> time.
>
>
>
> --
> Mark Sapiro <mark at msapiro.net>
> Sent from my Not_an_iThing with standards compliant, open source software.
>



-- 
===============================================
Russell Clemings
<russell at clemings.com>
===============================================

From mark at msapiro.net  Wed Jun 13 12:32:29 2018
From: mark at msapiro.net (Mark Sapiro)
Date: Wed, 13 Jun 2018 09:32:29 -0700
Subject: [Mailman-Users] change listinfo url?
In-Reply-To: <CAN7RX0Yvk3VdFyn1f61HszkQZ7P-euLQ6pBLzg=FpmogZE0c4A@mail.gmail.com>
References: <CAN7RX0YMj0iyn=_08Dpnvreg-3TWTeZFLha2H8Jn9Rg=D1Sbxg@mail.gmail.com>
 <a9f9f82f-46e6-201f-7c63-baf50cd07006@msapiro.net>
 <CAN7RX0bai1-Ghh-U1iDr_xyQ3e9sf92fxc4WedFOMxRor-8t_A@mail.gmail.com>
 <f10e3490-35d5-6e46-0489-bc67b051b6ff@msapiro.net>
 <CAN7RX0aoyxfUtZBF1i9D0Y48nWdNXC24UTxv5C6v7MP63iY_Nw@mail.gmail.com>
 <C6D77537-CD9A-4AAC-B26F-3148D3039A9C@msapiro.net>
 <CAN7RX0Yvk3VdFyn1f61HszkQZ7P-euLQ6pBLzg=FpmogZE0c4A@mail.gmail.com>
Message-ID: <92efa1d2-6c54-98aa-efb6-bdfae77aa50a@msapiro.net>

On 06/13/2018 08:28 AM, Russell Clemings wrote:
> Would it be easier just to hide the spaghetti on the listinfo pages?

I'm not sure what you mean by "hide the spaghetti", but if you mean
remove the subscribe form (or actually, whatever you mean), that's
pretty simple.

In Mailman's templates/ directory, create a site/ subdirectory and a
site/en/ subdirectory and a site/LC/ subdirectory for any other
languages you support. Then copy templates/en/listinfo.html to
templates/site/en/listinfo.html and similarly for any other languages.

Then, in templates/site/en/listinfo.html, remove what you don't want.

This will create a sitewide, default listinfo template that will survive
upgrades. It will still be oferridden by domain and list specific
templates - see <https://wiki.list.org/x/4030605>.

Or you can just create/edit list specific templates per list via "Edit
the public HTML pages and text files -> General list information page"
in the list's web admin UI.

-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan

From rclemings at gmail.com  Wed Jun 13 14:13:14 2018
From: rclemings at gmail.com (Russell Clemings)
Date: Wed, 13 Jun 2018 11:13:14 -0700
Subject: [Mailman-Users] change listinfo url?
In-Reply-To: <92efa1d2-6c54-98aa-efb6-bdfae77aa50a@msapiro.net>
References: <CAN7RX0YMj0iyn=_08Dpnvreg-3TWTeZFLha2H8Jn9Rg=D1Sbxg@mail.gmail.com>
 <a9f9f82f-46e6-201f-7c63-baf50cd07006@msapiro.net>
 <CAN7RX0bai1-Ghh-U1iDr_xyQ3e9sf92fxc4WedFOMxRor-8t_A@mail.gmail.com>
 <f10e3490-35d5-6e46-0489-bc67b051b6ff@msapiro.net>
 <CAN7RX0aoyxfUtZBF1i9D0Y48nWdNXC24UTxv5C6v7MP63iY_Nw@mail.gmail.com>
 <C6D77537-CD9A-4AAC-B26F-3148D3039A9C@msapiro.net>
 <CAN7RX0Yvk3VdFyn1f61HszkQZ7P-euLQ6pBLzg=FpmogZE0c4A@mail.gmail.com>
 <92efa1d2-6c54-98aa-efb6-bdfae77aa50a@msapiro.net>
Message-ID: <CAN7RX0bswBK1r8a+YvxYwH0SvhYfJZR6qoNzkXF6gbzT5t4YBQ@mail.gmail.com>

By "spaghetti" I mean this at the bottom of the listinfo page:

Mailman-Users list run by mailman-users-owner at python.org
Mailman-Users administrative interface (requires authorization)
Overview of all python.org mailing lists

The "Mailman-Users" and "Overview" links both go to /mailman/listinfo/ and
I've moved /listinfo/ to a different URL.

In any case, the instructions at https://wiki.list.org/x/4030605 seem to
work.

Apparently cPanel (yeah, I know, but we're stuck with it) puts a
listinfo.html in each lists/<listname>/<language> directory though, so I
guess I have to edit each one.


On Wed, Jun 13, 2018 at 9:32 AM, Mark Sapiro <mark at msapiro.net> wrote:

> On 06/13/2018 08:28 AM, Russell Clemings wrote:
> > Would it be easier just to hide the spaghetti on the listinfo pages?
>
> I'm not sure what you mean by "hide the spaghetti", but if you mean
> remove the subscribe form (or actually, whatever you mean), that's
> pretty simple.
>
> In Mailman's templates/ directory, create a site/ subdirectory and a
> site/en/ subdirectory and a site/LC/ subdirectory for any other
> languages you support. Then copy templates/en/listinfo.html to
> templates/site/en/listinfo.html and similarly for any other languages.
>
> Then, in templates/site/en/listinfo.html, remove what you don't want.
>
> This will create a sitewide, default listinfo template that will survive
> upgrades. It will still be oferridden by domain and list specific
> templates - see <https://wiki.list.org/x/4030605>.
>
> Or you can just create/edit list specific templates per list via "Edit
> the public HTML pages and text files -> General list information page"
> in the list's web admin UI.
>
> --
> Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
> San Francisco Bay Area, California    better use your sense - B. Dylan
> ------------------------------------------------------
> Mailman-Users mailing list Mailman-Users at 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/ma
> ilman-users%40python.org/
> Unsubscribe: https://mail.python.org/mailman/options/mailman-users/rclemi
> ngs%40gmail.com
>



-- 
===============================================
Russell Clemings
<russell at clemings.com>
===============================================

From rclemings at gmail.com  Wed Jun 13 14:33:56 2018
From: rclemings at gmail.com (Russell Clemings)
Date: Wed, 13 Jun 2018 11:33:56 -0700
Subject: [Mailman-Users] change listinfo url?
In-Reply-To: <CAN7RX0bswBK1r8a+YvxYwH0SvhYfJZR6qoNzkXF6gbzT5t4YBQ@mail.gmail.com>
References: <CAN7RX0YMj0iyn=_08Dpnvreg-3TWTeZFLha2H8Jn9Rg=D1Sbxg@mail.gmail.com>
 <a9f9f82f-46e6-201f-7c63-baf50cd07006@msapiro.net>
 <CAN7RX0bai1-Ghh-U1iDr_xyQ3e9sf92fxc4WedFOMxRor-8t_A@mail.gmail.com>
 <f10e3490-35d5-6e46-0489-bc67b051b6ff@msapiro.net>
 <CAN7RX0aoyxfUtZBF1i9D0Y48nWdNXC24UTxv5C6v7MP63iY_Nw@mail.gmail.com>
 <C6D77537-CD9A-4AAC-B26F-3148D3039A9C@msapiro.net>
 <CAN7RX0Yvk3VdFyn1f61HszkQZ7P-euLQ6pBLzg=FpmogZE0c4A@mail.gmail.com>
 <92efa1d2-6c54-98aa-efb6-bdfae77aa50a@msapiro.net>
 <CAN7RX0bswBK1r8a+YvxYwH0SvhYfJZR6qoNzkXF6gbzT5t4YBQ@mail.gmail.com>
Message-ID: <CAN7RX0ZSxzEVDudRUOXPK-JuaE93+qDLCRxyVEjeQATO+myYZA@mail.gmail.com>

Correction: That wasn't cPanel's fault. Must be something I did so long ago
I can't remember it. I deleted them and the global fix works now.

On Wed, Jun 13, 2018 at 11:13 AM, Russell Clemings <rclemings at gmail.com>
wrote:

> By "spaghetti" I mean this at the bottom of the listinfo page:
>
> Mailman-Users list run by mailman-users-owner at python.org
> Mailman-Users administrative interface (requires authorization)
> Overview of all python.org mailing lists
>
> The "Mailman-Users" and "Overview" links both go to /mailman/listinfo/ and
> I've moved /listinfo/ to a different URL.
>
> In any case, the instructions at https://wiki.list.org/x/4030605 seem to
> work.
>
> Apparently cPanel (yeah, I know, but we're stuck with it) puts a
> listinfo.html in each lists/<listname>/<language> directory though, so I
> guess I have to edit each one.
>
>
> On Wed, Jun 13, 2018 at 9:32 AM, Mark Sapiro <mark at msapiro.net> wrote:
>
>> On 06/13/2018 08:28 AM, Russell Clemings wrote:
>> > Would it be easier just to hide the spaghetti on the listinfo pages?
>>
>> I'm not sure what you mean by "hide the spaghetti", but if you mean
>> remove the subscribe form (or actually, whatever you mean), that's
>> pretty simple.
>>
>> In Mailman's templates/ directory, create a site/ subdirectory and a
>> site/en/ subdirectory and a site/LC/ subdirectory for any other
>> languages you support. Then copy templates/en/listinfo.html to
>> templates/site/en/listinfo.html and similarly for any other languages.
>>
>> Then, in templates/site/en/listinfo.html, remove what you don't want.
>>
>> This will create a sitewide, default listinfo template that will survive
>> upgrades. It will still be oferridden by domain and list specific
>> templates - see <https://wiki.list.org/x/4030605>.
>>
>> Or you can just create/edit list specific templates per list via "Edit
>> the public HTML pages and text files -> General list information page"
>> in the list's web admin UI.
>>
>> --
>> Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
>> San Francisco Bay Area, California    better use your sense - B. Dylan
>> ------------------------------------------------------
>> Mailman-Users mailing list Mailman-Users at 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/ma
>> ilman-users%40python.org/
>> Unsubscribe: https://mail.python.org/mailman/options/mailman-users/rclemi
>> ngs%40gmail.com
>>
>
>
>
> --
> ===============================================
> Russell Clemings
> <russell at clemings.com>
> ===============================================
>



-- 
===============================================
Russell Clemings
<russell at clemings.com>
===============================================

From mark at msapiro.net  Wed Jun 13 14:43:52 2018
From: mark at msapiro.net (Mark Sapiro)
Date: Wed, 13 Jun 2018 11:43:52 -0700
Subject: [Mailman-Users] change listinfo url?
In-Reply-To: <CAN7RX0bswBK1r8a+YvxYwH0SvhYfJZR6qoNzkXF6gbzT5t4YBQ@mail.gmail.com>
References: <CAN7RX0YMj0iyn=_08Dpnvreg-3TWTeZFLha2H8Jn9Rg=D1Sbxg@mail.gmail.com>
 <a9f9f82f-46e6-201f-7c63-baf50cd07006@msapiro.net>
 <CAN7RX0bai1-Ghh-U1iDr_xyQ3e9sf92fxc4WedFOMxRor-8t_A@mail.gmail.com>
 <f10e3490-35d5-6e46-0489-bc67b051b6ff@msapiro.net>
 <CAN7RX0aoyxfUtZBF1i9D0Y48nWdNXC24UTxv5C6v7MP63iY_Nw@mail.gmail.com>
 <C6D77537-CD9A-4AAC-B26F-3148D3039A9C@msapiro.net>
 <CAN7RX0Yvk3VdFyn1f61HszkQZ7P-euLQ6pBLzg=FpmogZE0c4A@mail.gmail.com>
 <92efa1d2-6c54-98aa-efb6-bdfae77aa50a@msapiro.net>
 <CAN7RX0bswBK1r8a+YvxYwH0SvhYfJZR6qoNzkXF6gbzT5t4YBQ@mail.gmail.com>
Message-ID: <a08249b9-b673-ea49-98ef-1a5ba3d20ec5@msapiro.net>

On 06/13/2018 11:13 AM, Russell Clemings wrote:
> 
> In any case, the instructions at https://wiki.list.org/x/4030605 seem to
> work.


Yes, and if you simply remove the <MM-Mailman-Footer> tag from near the
end of the listinfo.html template, that will do it.


> Apparently cPanel (yeah, I know, but we're stuck with it) puts a
> listinfo.html in each lists/<listname>/<language> directory though, so I
> guess I have to edit each one.


Either cPanel put them there or someone at some point edited them via
the web UI which puts the edited version there.

-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan

From Michael.D.Parker at ga.com  Thu Jun 14 19:35:07 2018
From: Michael.D.Parker at ga.com (Parker, Michael D.)
Date: Thu, 14 Jun 2018 23:35:07 +0000
Subject: [Mailman-Users] Suppressing Archive AND Digest Generation and
 collection
Message-ID: <fe72e6d9200f462ca96d0db06b8abfb5@ASGEXCPWP05.ga.com>

I previously asked how to permanently and globally remove archives.

Based on a previous note, I added to my mm_cfg.py:
                GLOBAL_PIPELINE.remove('ToArchive')

I assumed that the Digest file would be suppressed as well but I guess that is something different.
I note that a digest file is now created in /var/lib/mailman/lists/<listname> for each note received to be reflected further.

How can the digest functionality be globally suppressed as well.

Thanks.



From mark at tafn.org.uk  Thu Jun 14 19:41:42 2018
From: mark at tafn.org.uk (Mark T)
Date: Fri, 15 Jun 2018 00:41:42 +0100
Subject: [Mailman-Users] Bouncing emails.
Message-ID: <416KzD5QWNzFr2V@mail.python.org>

Hi is there any way I can stop my mailman list
Members emails bouncing keeps saying to reply to the email they do that and it keeps happening
Mark.

Tune in to the number one station on the web TAFN radio 
http://tafn.org.uk/listen
Or for our catch up service on demand http://www.tafn.org.uk/on-demand 
or for our upcoming weekly schedule 
http://www.tafn.org.uk/radio
part of the accessible friends network 
www.tafn.org.uk
Registered UK Charity: #1108043.
Sent from Windows 10 Mail.


From mark at msapiro.net  Thu Jun 14 19:56:45 2018
From: mark at msapiro.net (Mark Sapiro)
Date: Thu, 14 Jun 2018 16:56:45 -0700
Subject: [Mailman-Users] Suppressing Archive AND Digest Generation and
 collection
In-Reply-To: <fe72e6d9200f462ca96d0db06b8abfb5@ASGEXCPWP05.ga.com>
References: <fe72e6d9200f462ca96d0db06b8abfb5@ASGEXCPWP05.ga.com>
Message-ID: <74e4eb37-eb20-972a-6637-9fe6cab74c87@msapiro.net>

On 06/14/2018 04:35 PM, Parker, Michael D. wrote:
> 
> How can the digest functionality be globally suppressed as well.


In a fashion similar to what you did for archiving, you can put

GLOBAL_PIPELINE.remove('ToDigest')

in mm_cfg.py. Archiving and digesting can also be disabled on a per-list
basis by setting the list's Archiving Options -> archive and/or Digest
options -> digestable settings to No.

-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan

From mark at msapiro.net  Thu Jun 14 20:09:16 2018
From: mark at msapiro.net (Mark Sapiro)
Date: Thu, 14 Jun 2018 17:09:16 -0700
Subject: [Mailman-Users] Bouncing emails.
In-Reply-To: <416KzD5QWNzFr2V@mail.python.org>
References: <416KzD5QWNzFr2V@mail.python.org>
Message-ID: <dc46ec2b-96cd-67e8-660c-1c2c0b811ac8@msapiro.net>

On 06/14/2018 04:41 PM, Mark T wrote:
> Hi is there any way I can stop my mailman list
> Members emails bouncing keeps saying to reply to the email they do that and it keeps happening

I don't understand. What keeps happening?  What is the email asking for
a reply?

Are you saying that a user's delivery is disabled by bounce and the user
receives a notice that looks something like:

> Your membership in the mailing list %(listname)s has been disabled
> %(reason)s.  You will not get any more messages from this
> list until you re-enable your membership.  You will receive
> %(noticesleft)s more reminders like this before your membership in the
> list is deleted.
> 
> To re-enable your membership, you can simply respond to this message
> (leaving the Subject: line intact), or visit the confirmation page at
> 
>     %(confirmurl)s


and the user responds and after a time the user's delivery is disabled
again. If so, the underlying delivery issue needs to be fixed. If you
ensure that the list's Bounce processing Notifications
bounce_notify_owner_on_disable and if your Mailman is new enough,
bounce_notify_owner_on_bounce_increment are set to Yes. Then the owner
notice will say why the mail is bouncing, Or if you have access, you can
just look in the MTA logs.

-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan

From turnbull.stephen.fw at u.tsukuba.ac.jp  Fri Jun 15 00:51:38 2018
From: turnbull.stephen.fw at u.tsukuba.ac.jp (Stephen J. Turnbull)
Date: Fri, 15 Jun 2018 13:51:38 +0900
Subject: [Mailman-Users] Migrating Mailman to New Server (Same Domain)
In-Reply-To: <1528816614.127582.14.camel@fmp.com>
References: <CAPw9k4m7LfwaXb-eb+sJCGO7Ub0yc0JuBdBQPPmN7och7gXgPg@mail.gmail.com>
 <327ac394-75db-efcf-3cb9-b207423286eb@msapiro.net>
 <23327.35283.153716.839652@turnbull.sk.tsukuba.ac.jp>
 <1528816614.127582.14.camel@fmp.com>
Message-ID: <23331.17882.331850.206789@turnbull.sk.tsukuba.ac.jp>

Lindsay Haisley writes:
 > On Tue, 2018-06-12 at 17:52 +0900, Stephen J. Turnbull wrote:

 > > I wonder if his system might default to a non-GNU tar.
 > 
 > No, I use GNU tar.

Sorry for the confusion.  I was thinking the OP might not be using GNU
tar.

 > Sufficient knowledge [...] may well be required

I for one think it is well to require knowledge! :-)

From mark at msapiro.net  Fri Jun 15 12:05:09 2018
From: mark at msapiro.net (Mark Sapiro)
Date: Fri, 15 Jun 2018 09:05:09 -0700
Subject: [Mailman-Users] Bouncing emails.
In-Reply-To: <dc46ec2b-96cd-67e8-660c-1c2c0b811ac8@msapiro.net>
References: <416KzD5QWNzFr2V@mail.python.org>
 <dc46ec2b-96cd-67e8-660c-1c2c0b811ac8@msapiro.net>
Message-ID: <aa2a0703-87a5-7a76-631a-ea2a8bf066a2@msapiro.net>

On 06/15/2018 05:50 AM, Mark T wrote:
> Hi here is a copy of one of my members bounce email
> 
> This is a Mailman mailing list bounce action notice:
> 
> ?
> 
> ??? List:?????? All-write
> 
> ??? Member:????
> 
> bscription disabled.
> 
> ??? Reason:???? Excessive or fatal bounces.
> 
> They have replyed? to the email but was still removed


The above message is a notice to the list owner that the users delivery
has been disabled due to bouncing. Replying to this notice simly sends
the reply to the list owner but does nothing to re-enable the user's
delivery.

If the owner is convinced that the user's address is actually
deliverable, the owner can go to the list admin web UI Membership
Management... -> Membership List and uncheck the "nomail/[reason]" box
for the user and submit the change.

However, it is more likely that the address is actually not deliverable
and should be unsubscribed. The bounce message attached to the notice
will give more information about the actual bounce reason.

-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan

From kevin.t.bowen at gmail.com  Mon Jun 18 14:44:07 2018
From: kevin.t.bowen at gmail.com (Kevin Bowen)
Date: Mon, 18 Jun 2018 11:44:07 -0700
Subject: [Mailman-Users] Global blacklist recipient address?
Message-ID: <CACHqquBwFPNiD-N9007=z+TZU+FYRDOmszqy7dOrPB3noB4-Jw@mail.gmail.com>

What is the best way to block a particular recipient address site-wide? I
see there's a KNOWN_SPAMMERS variable, but I'm not sure if that's what I
need since I want to block any mail from getting sent TO this address, not
from it. Someone is being maliciously subscribed to multiple mailing lists
and getting spammed with subscription requests.

Kevin Bowen
kevin.t.bowen at gmail.com <kevin at ucsd.edu>

From mark at msapiro.net  Mon Jun 18 16:41:12 2018
From: mark at msapiro.net (Mark Sapiro)
Date: Mon, 18 Jun 2018 13:41:12 -0700
Subject: [Mailman-Users] Global blacklist recipient address?
In-Reply-To: <CACHqquBwFPNiD-N9007=z+TZU+FYRDOmszqy7dOrPB3noB4-Jw@mail.gmail.com>
References: <CACHqquBwFPNiD-N9007=z+TZU+FYRDOmszqy7dOrPB3noB4-Jw@mail.gmail.com>
Message-ID: <db4658c2-c828-30e9-2a5c-e6b81f093697@msapiro.net>

On 06/18/2018 11:44 AM, Kevin Bowen wrote:
> What is the best way to block a particular recipient address site-wide? I
> see there's a KNOWN_SPAMMERS variable, but I'm not sure if that's what I
> need since I want to block any mail from getting sent TO this address, not
> from it. Someone is being maliciously subscribed to multiple mailing lists
> and getting spammed with subscription requests.


If you have access to Mailman's configuration in Mailman/mm_cfg.py, you
can add the address or a regexp matching the address to the
GLOBAL_BAN_LIST to prevent new subscriptions.

You can use a script such as the one at
<https://www.msapiro.net/scripts/erase> to completely remove an address
or addresses matching a regexp from the Mailman installation.

Adding the address to the GLOBAL_BAN_LIST will block any attempts to
subscribe it to any list. Most of these subscribe attacks (all that I've
seen) are web subscribes so the person doing the subscribe gets a web
response denying it an no email is sent. This will not stop the response
email to an attempted email subscribe, but you probably aren't seeing those.

There is no convenient way in Mailman to block all outgoing mail to a
given address.

-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan

From kevin.t.bowen at gmail.com  Mon Jun 18 17:05:43 2018
From: kevin.t.bowen at gmail.com (Kevin Bowen)
Date: Mon, 18 Jun 2018 14:05:43 -0700
Subject: [Mailman-Users] Global blacklist recipient address?
In-Reply-To: <db4658c2-c828-30e9-2a5c-e6b81f093697@msapiro.net>
References: <CACHqquBwFPNiD-N9007=z+TZU+FYRDOmszqy7dOrPB3noB4-Jw@mail.gmail.com>
 <db4658c2-c828-30e9-2a5c-e6b81f093697@msapiro.net>
Message-ID: <CACHqquAajvwAUcat2eEgJz91rcfOtikp_+-hcjFeeEwTCHYRRw@mail.gmail.com>

That sounds like what I need, but I don't see GLOBAL_BAN_LIST in mm_cfg.py.
After doing some googling, it looks like that feature wasn't added until
version 2.1.21, is that correct? I'm on 2.1.9, and upgrading won't be
possible any time soon. Any other options for accomplishing the same thing?
Maybe a scriptable way I could individually ban it from each list?

Kevin Bowen
kevin.t.bowen at gmail.com <kevin at ucsd.edu>

On Mon, Jun 18, 2018 at 1:41 PM, Mark Sapiro <mark at msapiro.net> wrote:

> On 06/18/2018 11:44 AM, Kevin Bowen wrote:
> > What is the best way to block a particular recipient address site-wide? I
> > see there's a KNOWN_SPAMMERS variable, but I'm not sure if that's what I
> > need since I want to block any mail from getting sent TO this address,
> not
> > from it. Someone is being maliciously subscribed to multiple mailing
> lists
> > and getting spammed with subscription requests.
>
>
> If you have access to Mailman's configuration in Mailman/mm_cfg.py, you
> can add the address or a regexp matching the address to the
> GLOBAL_BAN_LIST to prevent new subscriptions.
>
> You can use a script such as the one at
> <https://www.msapiro.net/scripts/erase> to completely remove an address
> or addresses matching a regexp from the Mailman installation.
>
> Adding the address to the GLOBAL_BAN_LIST will block any attempts to
> subscribe it to any list. Most of these subscribe attacks (all that I've
> seen) are web subscribes so the person doing the subscribe gets a web
> response denying it an no email is sent. This will not stop the response
> email to an attempted email subscribe, but you probably aren't seeing
> those.
>
> There is no convenient way in Mailman to block all outgoing mail to a
> given address.
>
> --
> Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
> San Francisco Bay Area, California    better use your sense - B. Dylan
> ------------------------------------------------------
> Mailman-Users mailing list Mailman-Users at 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/
> kevin.t.bowen%40gmail.com
>

From mark at msapiro.net  Mon Jun 18 17:48:05 2018
From: mark at msapiro.net (Mark Sapiro)
Date: Mon, 18 Jun 2018 14:48:05 -0700
Subject: [Mailman-Users] Global blacklist recipient address?
In-Reply-To: <CACHqquAajvwAUcat2eEgJz91rcfOtikp_+-hcjFeeEwTCHYRRw@mail.gmail.com>
References: <CACHqquBwFPNiD-N9007=z+TZU+FYRDOmszqy7dOrPB3noB4-Jw@mail.gmail.com>
 <db4658c2-c828-30e9-2a5c-e6b81f093697@msapiro.net>
 <CACHqquAajvwAUcat2eEgJz91rcfOtikp_+-hcjFeeEwTCHYRRw@mail.gmail.com>
Message-ID: <89bc62e8-d5ca-2ab4-4017-48637acde4cd@msapiro.net>

On 06/18/2018 02:05 PM, Kevin Bowen wrote:
> That sounds like what I need, but I don't see GLOBAL_BAN_LIST in mm_cfg.py.
> After doing some googling, it looks like that feature wasn't added until
> version 2.1.21, is that correct? I'm on 2.1.9, and upgrading won't be
> possible any time soon. Any other options for accomplishing the same thing?
> Maybe a scriptable way I could individually ban it from each list?


The implementation is pretty simple. See
<https://bazaar.launchpad.net/~mailman-coders/mailman/2.1/revision/1574>.

There is also a withlist script at
<https://www.msapiro.net/scripts/add_banned.py> that you can use to add
an address or pattern to the ban_list of all lists.

-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan

From mark at msapiro.net  Fri Jun 22 13:37:32 2018
From: mark at msapiro.net (Mark Sapiro)
Date: Fri, 22 Jun 2018 10:37:32 -0700
Subject: [Mailman-Users] Mailman 2.1.27 released
Message-ID: <575ec64d-1d07-8044-124b-637d96c89121@msapiro.net>

I am pleased to announce the release of Mailman 2.1.27.

Python 2.6 is the minimum supported, but Python 2.7 is strongly recommended.

This is a routine bug fix release with a few new features and some minor
security enhancements. See the attached README.txt for details.

Mailman is free software for managing email mailing lists and
e-newsletters. Mailman is used for all the python.org and
SourceForge.net mailing lists, as well as at hundreds of other sites.

For more information, please see our web site at one of:

http://www.list.org
https://www.gnu.org/software/mailman
http://mailman.sourceforge.net/
https://mirror.list.org/

Mailman 2.1.27 can be downloaded from

https://launchpad.net/mailman/2.1/
https://ftp.gnu.org/gnu/mailman/
https://sourceforge.net/projects/mailman/

-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan

-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: README.txt
URL: <http://mail.python.org/pipermail/mailman-users/attachments/20180622/35a38873/attachment.txt>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <http://mail.python.org/pipermail/mailman-users/attachments/20180622/35a38873/attachment.sig>

From raj at mischievous.us  Mon Jun 25 14:27:05 2018
From: raj at mischievous.us (Richard Johnson)
Date: Mon, 25 Jun 2018 11:27:05 -0700
Subject: [Mailman-Users] Mailman 2.1.27 released
In-Reply-To: <575ec64d-1d07-8044-124b-637d96c89121@msapiro.net>
References: <575ec64d-1d07-8044-124b-637d96c89121@msapiro.net>
Message-ID: <F24E0A24-D99E-448D-A927-46B4181AAAFE@mischievous.us>

I see I'm still running 2.1.22.  I'd like to upgrade to 2.1.27, however.  Is there a document with instructions on how to upgrade?

Thanks!

/raj

> On Jun 22, 2018, at 10:37 AM, Mark Sapiro <mark at msapiro.net> wrote:
> 
> I am pleased to announce the release of Mailman 2.1.27.
> 
> Python 2.6 is the minimum supported, but Python 2.7 is strongly recommended.
> 
> This is a routine bug fix release with a few new features and some minor
> security enhancements. See the attached README.txt for details.
> 
> Mailman is free software for managing email mailing lists and
> e-newsletters. Mailman is used for all the python.org and
> SourceForge.net mailing lists, as well as at hundreds of other sites.
> 
> For more information, please see our web site at one of:
> 
> http://www.list.org
> https://www.gnu.org/software/mailman
> http://mailman.sourceforge.net/
> https://mirror.list.org/
> 
> Mailman 2.1.27 can be downloaded from
> 
> https://launchpad.net/mailman/2.1/
> https://ftp.gnu.org/gnu/mailman/
> https://sourceforge.net/projects/mailman/
> 
> -- 
> Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
> San Francisco Bay Area, California    better use your sense - B. Dylan
> 
> <README.txt>------------------------------------------------------
> Mailman-Users mailing list Mailman-Users at 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/raj%40mischievous.us


From raj at mischievous.us  Mon Jun 25 14:39:12 2018
From: raj at mischievous.us (Richard Johnson)
Date: Mon, 25 Jun 2018 11:39:12 -0700
Subject: [Mailman-Users] How to track down someone mislabeling msgs as abuse?
Message-ID: <198406E0-25DA-4268-9A17-D31F7D6039A4@mischievous.us>

I have a mailing list which has 51 members, all friends of mine.  We use it to communicate on things related to our history club.  About 1-2 times a month, I receive an automated message from AOL's abuse list, saying that someone has marked one of the messages as "abuse".  Unfortunately, there's no way to track down who this could be, since there are about 5 addresses on the list which are AOL addresses.  All I get is this:

Feedback-Type: abuse
User-Agent: AOL SComp
Version: 0.1
Received-Date: Mon, 25 Jun 2018 10:04:00 -0400 (EDT)
Source-IP: 98.173.52.230
Reported-Domain: mischievous.us
Redacted-Address: redacted
Redacted-Address: redacted@

Along with also a copy of the original message.

Using the "Received-Date" header, I can see that it looks as if the timing would point to one particular list member, but he says he's not doing anything like that.  (As a matter of fact, he has told me, on a few occasions, that he didn't even see the message in question at all!)

I've read that some people have addressed this by inserting a unique string at the end of each person's message.  I don't see a way to do this with Mailman 2.1.22.  Would something like this be possible with more recent versions such as 2.1.27, or even the latest 3.x version?  Are there other ways to address this?  I don't want to reprimand the person, I just want to educate them to not mark list messages as abuse!

Any help would be greatly appreciated!

/raj


From rclemings at gmail.com  Mon Jun 25 15:23:55 2018
From: rclemings at gmail.com (Russell Clemings)
Date: Mon, 25 Jun 2018 12:23:55 -0700
Subject: [Mailman-Users] How to track down someone mislabeling msgs as
 abuse?
In-Reply-To: <198406E0-25DA-4268-9A17-D31F7D6039A4@mischievous.us>
References: <198406E0-25DA-4268-9A17-D31F7D6039A4@mischievous.us>
Message-ID: <CAN7RX0av_+W0+aZwcgu0yJvioekTLZJ0Cirv-XVDmUtwjK=q1w@mail.gmail.com>

I put %(user_address)s in the message footer; that doesn't seem to get
sanitized by the feedback loops.

It doesn't work for digests though, just regular messages.

I believe it also requires you to set OWNERS_CAN_ENABLE_PERSONALIZATION
on mm_cfg.py.

As to your suspect, since he says he's not seeing the messages, is it
possible he has an autofilter that's routing them directly to spam? I had a
user like that recently.



On Mon, Jun 25, 2018 at 11:39 AM, Richard Johnson <raj at mischievous.us>
wrote:

> I have a mailing list which has 51 members, all friends of mine.  We use
> it to communicate on things related to our history club.  About 1-2 times a
> month, I receive an automated message from AOL's abuse list, saying that
> someone has marked one of the messages as "abuse".  Unfortunately, there's
> no way to track down who this could be, since there are about 5 addresses
> on the list which are AOL addresses.  All I get is this:
>
> Feedback-Type: abuse
> User-Agent: AOL SComp
> Version: 0.1
> Received-Date: Mon, 25 Jun 2018 10:04:00 -0400 (EDT)
> Source-IP: 98.173.52.230
> Reported-Domain: mischievous.us
> Redacted-Address: redacted
> Redacted-Address: redacted@
>
> Along with also a copy of the original message.
>
> Using the "Received-Date" header, I can see that it looks as if the timing
> would point to one particular list member, but he says he's not doing
> anything like that.  (As a matter of fact, he has told me, on a few
> occasions, that he didn't even see the message in question at all!)
>
> I've read that some people have addressed this by inserting a unique
> string at the end of each person's message.  I don't see a way to do this
> with Mailman 2.1.22.  Would something like this be possible with more
> recent versions such as 2.1.27, or even the latest 3.x version?  Are there
> other ways to address this?  I don't want to reprimand the person, I just
> want to educate them to not mark list messages as abuse!
>
> Any help would be greatly appreciated!
>
> /raj
>
> ------------------------------------------------------
> Mailman-Users mailing list Mailman-Users at 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/
> rclemings%40gmail.com
>



-- 
===============================================
Russell Clemings
<russell at clemings.com>
===============================================

From raj at mischievous.us  Mon Jun 25 15:36:21 2018
From: raj at mischievous.us (Richard Johnson)
Date: Mon, 25 Jun 2018 12:36:21 -0700
Subject: [Mailman-Users] How to track down someone mislabeling msgs as
 abuse?
In-Reply-To: <CAN7RX0av_+W0+aZwcgu0yJvioekTLZJ0Cirv-XVDmUtwjK=q1w@mail.gmail.com>
References: <198406E0-25DA-4268-9A17-D31F7D6039A4@mischievous.us>
 <CAN7RX0av_+W0+aZwcgu0yJvioekTLZJ0Cirv-XVDmUtwjK=q1w@mail.gmail.com>
Message-ID: <F315E1B3-8F6F-4271-BC9A-0262881228D1@mischievous.us>

Thanks for the suggestion!  I'll try it out.

As for routing directly to spam, I actually thought of that and asked him to verify that wasn't the case.  He says he has no such filter.

I'm hoping that if I can provide proof that it's him, he'll take it more seriously and take a closer look.  At any rate, if I can prove it's him, I'll have justification for removing him from the list or at least ask if he has a different email address I can use.

Thanks again!

/raj


> On Jun 25, 2018, at 12:23 PM, Russell Clemings <rclemings at gmail.com <mailto:rclemings at gmail.com>> wrote:
> 
> I put %(user_address)s in the message footer; that doesn't seem to get sanitized by the feedback loops.
> 
> It doesn't work for digests though, just regular messages.
> 
> I believe it also requires you to set OWNERS_CAN_ENABLE_PERSONALIZATION on mm_cfg.py.
> 
> As to your suspect, since he says he's not seeing the messages, is it possible he has an autofilter that's routing them directly to spam? I had a user like that recently.
> 
> 
> 
> On Mon, Jun 25, 2018 at 11:39 AM, Richard Johnson <raj at mischievous.us <mailto:raj at mischievous.us>> wrote:
> I have a mailing list which has 51 members, all friends of mine.  We use it to communicate on things related to our history club.  About 1-2 times a month, I receive an automated message from AOL's abuse list, saying that someone has marked one of the messages as "abuse".  Unfortunately, there's no way to track down who this could be, since there are about 5 addresses on the list which are AOL addresses.  All I get is this:
> 
> Feedback-Type: abuse
> User-Agent: AOL SComp
> Version: 0.1
> Received-Date: Mon, 25 Jun 2018 10:04:00 -0400 (EDT)
> Source-IP: 98.173.52.230
> Reported-Domain: mischievous.us <http://mischievous.us/>
> Redacted-Address: redacted
> Redacted-Address: redacted@
> 
> Along with also a copy of the original message.
> 
> Using the "Received-Date" header, I can see that it looks as if the timing would point to one particular list member, but he says he's not doing anything like that.  (As a matter of fact, he has told me, on a few occasions, that he didn't even see the message in question at all!)
> 
> I've read that some people have addressed this by inserting a unique string at the end of each person's message.  I don't see a way to do this with Mailman 2.1.22.  Would something like this be possible with more recent versions such as 2.1.27, or even the latest 3.x version?  Are there other ways to address this?  I don't want to reprimand the person, I just want to educate them to not mark list messages as abuse!
> 
> Any help would be greatly appreciated!
> 
> /raj
> 
> ------------------------------------------------------
> Mailman-Users mailing list Mailman-Users at python.org <mailto:Mailman-Users at python.org>
> https://mail.python.org/mailman/listinfo/mailman-users <https://mail.python.org/mailman/listinfo/mailman-users>
> Mailman FAQ: http://wiki.list.org/x/AgA3 <http://wiki.list.org/x/AgA3>
> Security Policy: http://wiki.list.org/x/QIA9 <http://wiki.list.org/x/QIA9>
> Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ <http://www.mail-archive.com/mailman-users%40python.org/>
> Unsubscribe: https://mail.python.org/mailman/options/mailman-users/rclemings%40gmail.com <https://mail.python.org/mailman/options/mailman-users/rclemings%40gmail.com>
> 
> 
> 
> -- 
> ===============================================
> Russell Clemings
> <russell at clemings.com <mailto:russell at clemings.com>>
> ===============================================


From raj at mischievous.us  Mon Jun 25 16:04:22 2018
From: raj at mischievous.us (Richard Johnson)
Date: Mon, 25 Jun 2018 13:04:22 -0700
Subject: [Mailman-Users] How to track down someone mislabeling msgs as
 abuse?
In-Reply-To: <F315E1B3-8F6F-4271-BC9A-0262881228D1@mischievous.us>
References: <198406E0-25DA-4268-9A17-D31F7D6039A4@mischievous.us>
 <CAN7RX0av_+W0+aZwcgu0yJvioekTLZJ0Cirv-XVDmUtwjK=q1w@mail.gmail.com>
 <F315E1B3-8F6F-4271-BC9A-0262881228D1@mischievous.us>
Message-ID: <92F2A0E2-E555-4C8B-912A-93E4BC5EDBE7@mischievous.us>

I tried this just now, adding "%(user_address)" to the footer, and I'm geting:

Warning: The following illegal substitution variables were found in the msg_footer string: user_address

(I included "OWNERS_CAN_ENABLE_PERSONALIZATION = Yes" into mm_cfg.py, and I did bin/mailmanctl restart.)

What version of mailman are you using?  Mine is 2.1.22, which I know is old.

/raj


> On Jun 25, 2018, at 12:36 PM, Richard Johnson <raj at mischievous.us> wrote:
> 
> Thanks for the suggestion!  I'll try it out.
> 
> As for routing directly to spam, I actually thought of that and asked him to verify that wasn't the case.  He says he has no such filter.
> 
> I'm hoping that if I can provide proof that it's him, he'll take it more seriously and take a closer look.  At any rate, if I can prove it's him, I'll have justification for removing him from the list or at least ask if he has a different email address I can use.
> 
> Thanks again!
> 
> /raj
> 
> 
>> On Jun 25, 2018, at 12:23 PM, Russell Clemings <rclemings at gmail.com <mailto:rclemings at gmail.com>> wrote:
>> 
>> I put %(user_address)s in the message footer; that doesn't seem to get sanitized by the feedback loops.
>> 
>> It doesn't work for digests though, just regular messages.
>> 
>> I believe it also requires you to set OWNERS_CAN_ENABLE_PERSONALIZATION on mm_cfg.py.
>> 
>> As to your suspect, since he says he's not seeing the messages, is it possible he has an autofilter that's routing them directly to spam? I had a user like that recently.
>> 
>> 
>> 
>> On Mon, Jun 25, 2018 at 11:39 AM, Richard Johnson <raj at mischievous.us <mailto:raj at mischievous.us>> wrote:
>> I have a mailing list which has 51 members, all friends of mine.  We use it to communicate on things related to our history club.  About 1-2 times a month, I receive an automated message from AOL's abuse list, saying that someone has marked one of the messages as "abuse".  Unfortunately, there's no way to track down who this could be, since there are about 5 addresses on the list which are AOL addresses.  All I get is this:
>> 
>> Feedback-Type: abuse
>> User-Agent: AOL SComp
>> Version: 0.1
>> Received-Date: Mon, 25 Jun 2018 10:04:00 -0400 (EDT)
>> Source-IP: 98.173.52.230
>> Reported-Domain: mischievous.us <http://mischievous.us/>
>> Redacted-Address: redacted
>> Redacted-Address: redacted@
>> 
>> Along with also a copy of the original message.
>> 
>> Using the "Received-Date" header, I can see that it looks as if the timing would point to one particular list member, but he says he's not doing anything like that.  (As a matter of fact, he has told me, on a few occasions, that he didn't even see the message in question at all!)
>> 
>> I've read that some people have addressed this by inserting a unique string at the end of each person's message.  I don't see a way to do this with Mailman 2.1.22.  Would something like this be possible with more recent versions such as 2.1.27, or even the latest 3.x version?  Are there other ways to address this?  I don't want to reprimand the person, I just want to educate them to not mark list messages as abuse!
>> 
>> Any help would be greatly appreciated!
>> 
>> /raj
>> 
>> ------------------------------------------------------
>> Mailman-Users mailing list Mailman-Users at python.org <mailto:Mailman-Users at python.org>
>> https://mail.python.org/mailman/listinfo/mailman-users <https://mail.python.org/mailman/listinfo/mailman-users>
>> Mailman FAQ: http://wiki.list.org/x/AgA3 <http://wiki.list.org/x/AgA3>
>> Security Policy: http://wiki.list.org/x/QIA9 <http://wiki.list.org/x/QIA9>
>> Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/ <http://www.mail-archive.com/mailman-users%40python.org/>
>> Unsubscribe: https://mail.python.org/mailman/options/mailman-users/rclemings%40gmail.com <https://mail.python.org/mailman/options/mailman-users/rclemings%40gmail.com>
>> 
>> 
>> 
>> -- 
>> ===============================================
>> Russell Clemings
>> <russell at clemings.com <mailto:russell at clemings.com>>
>> ===============================================
> 
> ------------------------------------------------------
> Mailman-Users mailing list Mailman-Users at 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/raj%40mischievous.us


From turnbull.stephen.fw at u.tsukuba.ac.jp  Mon Jun 25 22:32:14 2018
From: turnbull.stephen.fw at u.tsukuba.ac.jp (Stephen J. Turnbull)
Date: Tue, 26 Jun 2018 11:32:14 +0900
Subject: [Mailman-Users] How to track down someone mislabeling msgs as
 abuse?
In-Reply-To: <92F2A0E2-E555-4C8B-912A-93E4BC5EDBE7@mischievous.us>
References: <198406E0-25DA-4268-9A17-D31F7D6039A4@mischievous.us>
 <CAN7RX0av_+W0+aZwcgu0yJvioekTLZJ0Cirv-XVDmUtwjK=q1w@mail.gmail.com>
 <F315E1B3-8F6F-4271-BC9A-0262881228D1@mischievous.us>
 <92F2A0E2-E555-4C8B-912A-93E4BC5EDBE7@mischievous.us>
Message-ID: <23345.42414.516718.341146@turnbull.sk.tsukuba.ac.jp>

Richard Johnson writes:

 > I tried this just now, adding "%(user_address)" to the footer,

Executive summary: Try adding "s" to the end of that.

The format string is "%s", which in very old Pythons needed to be
referred to according to its position in the string.  More modern
Pythons allow you to interpolate "(user_address)" which looks up the
variable user_address in a dictionary.  But you still need the "s" at
the end to tell Python to format the variable's value is expected to
be a string, not an integer or something like that.

The error message seems unclear.  I'm not sure if it's easy to do
anything about it though.  The format string language is complex, and
I'm not sure it's easy for the program to diagnose the error more
precisely.

Regards,

Steve

-- 
Associate Professor              Division of Policy and Planning Science
http://turnbull.sk.tsukuba.ac.jp/     Faculty of Systems and Information
Email: turnbull at sk.tsukuba.ac.jp                   University of Tsukuba
Tel: 029-853-5175                 Tennodai 1-1-1, Tsukuba 305-8573 JAPAN

From mark at msapiro.net  Tue Jun 26 00:55:21 2018
From: mark at msapiro.net (Mark Sapiro)
Date: Mon, 25 Jun 2018 21:55:21 -0700
Subject: [Mailman-Users] Mailman 2.1.27 released
In-Reply-To: <F24E0A24-D99E-448D-A927-46B4181AAAFE@mischievous.us>
References: <575ec64d-1d07-8044-124b-637d96c89121@msapiro.net>
 <F24E0A24-D99E-448D-A927-46B4181AAAFE@mischievous.us>
Message-ID: <205a813a-a9b9-e731-ce61-1cd936b341bd@msapiro.net>

On 6/25/18 11:27 AM, Richard Johnson wrote:
> I see I'm still running 2.1.22.  I'd like to upgrade to 2.1.27, however.  Is there a document with instructions on how to upgrade?


See the UPGRADING document in the tarball or at
<https://bazaar.launchpad.net/~mailman-coders/mailman/2.1/view/head:/UPGRADING>.

-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan

From mark at msapiro.net  Tue Jun 26 01:12:02 2018
From: mark at msapiro.net (Mark Sapiro)
Date: Mon, 25 Jun 2018 22:12:02 -0700
Subject: [Mailman-Users] How to track down someone mislabeling msgs as
 abuse?
In-Reply-To: <198406E0-25DA-4268-9A17-D31F7D6039A4@mischievous.us>
References: <198406E0-25DA-4268-9A17-D31F7D6039A4@mischievous.us>
Message-ID: <446b725d-c351-6f59-d79e-2ebc2aef6a61@msapiro.net>

On 6/25/18 11:39 AM, Richard Johnson wrote:
> Feedback-Type: abuse
> User-Agent: AOL SComp
> Version: 0.1
> Received-Date: Mon, 25 Jun 2018 10:04:00 -0400 (EDT)
> Source-IP: 98.173.52.230
> Reported-Domain: mischievous.us
> Redacted-Address: redacted
> Redacted-Address: redacted@
> 
> Along with also a copy of the original message.
> 
> Using the "Received-Date" header, I can see that it looks as if the timing would point to one particular list member, but he says he's not doing anything like that.  (As a matter of fact, he has told me, on a few occasions, that he didn't even see the message in question at all!)
> 
> I've read that some people have addressed this by inserting a unique string at the end of each person's message.  I don't see a way to do this with Mailman 2.1.22.  Would something like this be possible with more recent versions such as 2.1.27, or even the latest 3.x version?  Are there other ways to address this?  I don't want to reprimand the person, I just want to educate them to not mark list messages as abuse!
> 
> Any help would be greatly appreciated!
> 
> /raj
> 
> ------------------------------------------------------
> Mailman-Users mailing list Mailman-Users at 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/mark%40msapiro.net


-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan

From mark at msapiro.net  Tue Jun 26 01:19:50 2018
From: mark at msapiro.net (Mark Sapiro)
Date: Mon, 25 Jun 2018 22:19:50 -0700
Subject: [Mailman-Users] How to track down someone mislabeling msgs as
 abuse?
In-Reply-To: <198406E0-25DA-4268-9A17-D31F7D6039A4@mischievous.us>
References: <198406E0-25DA-4268-9A17-D31F7D6039A4@mischievous.us>
Message-ID: <5c44ad66-7398-2bd0-a1c7-d000a7a6280a@msapiro.net>

On 6/25/18 11:39 AM, Richard Johnson wrote:
> I have a mailing list which has 51 members, all friends of mine.  We use it to communicate on things related to our history club.  About 1-2 times a month, I receive an automated message from AOL's abuse list, saying that someone has marked one of the messages as "abuse".  Unfortunately, there's no way to track down who this could be, since there are about 5 addresses on the list which are AOL addresses.  


Sorry about the prior fumbled send :(

In my experience, AOL's redaction is not always complete, particularly
if the message is VERPed, but in any case, beginning with Mailman 2.1.24
we have

>     - There is a new RCPT_BASE64_HEADER_NAME setting.  If this is set to a
>       non-empty string, that string is the name of a header that will be added
>       to personalized and VERPed deliveries with value equal to the base64
>       encoding of the recipient's email address.  This is intended to enable
>       identification of the recipient otherwise redacted from "spam report"
>       feedback loop messages.

E.g., set

RCPT_BASE64_HEADER_NAME = 'X-My-Recip'

in mm_cfg.py and the VERPed or personalized message will have a

X-My-Recip: header with the base64 encoded recip. The name of the header
is a setting to prevent AOL from knowing what it is and redacting it too.

-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan

From dandrews at visi.com  Tue Jun 26 14:12:53 2018
From: dandrews at visi.com (David Andrews)
Date: Tue, 26 Jun 2018 13:12:53 -0500
Subject: [Mailman-Users] Changing Characters
Message-ID: <auto-000106097873@mailfront2.g2host.com>

I am running Mailman 2.1.26, cPanel. I had a message that I forwarded 
to a list using Outlook 2010. It looked fine in Outlook, but when it 
went to list all ' apostrophes were changed to ? question mark. What 
causes this, and how can I prevent it.

Dave


---
This email has been checked for viruses by AVG.
https://www.avg.com


From Richard at Damon-Family.org  Tue Jun 26 20:03:28 2018
From: Richard at Damon-Family.org (Richard Damon)
Date: Tue, 26 Jun 2018 20:03:28 -0400
Subject: [Mailman-Users] Changing Characters
In-Reply-To: <auto-000106097873@mailfront2.g2host.com>
References: <auto-000106097873@mailfront2.g2host.com>
Message-ID: <8e46263f-58bd-602d-9809-741f164ce8c5@Damon-Family.org>

On 6/26/18 2:12 PM, David Andrews wrote:
> I am running Mailman 2.1.26, cPanel. I had a message that I forwarded
> to a list using Outlook 2010. It looked fine in Outlook, but when it
> went to list all ' apostrophes were changed to ? question mark. What
> causes this, and how can I prevent it.
>
> Dave 
The lists language is set to use a National Code page, and Outlook
formatted the message to use a 'Smart Quote' that isn't part of that
Code Page.

-- 
Richard Damon


From mark at msapiro.net  Tue Jun 26 20:40:53 2018
From: mark at msapiro.net (Mark Sapiro)
Date: Tue, 26 Jun 2018 17:40:53 -0700
Subject: [Mailman-Users] Changing Characters
In-Reply-To: <8e46263f-58bd-602d-9809-741f164ce8c5@Damon-Family.org>
References: <auto-000106097873@mailfront2.g2host.com>
 <8e46263f-58bd-602d-9809-741f164ce8c5@Damon-Family.org>
Message-ID: <129a3a13-8136-0518-5a71-e6c2cbd66589@msapiro.net>

On 6/26/18 5:03 PM, Richard Damon wrote:
> On 6/26/18 2:12 PM, David Andrews wrote:
>> I am running Mailman 2.1.26, cPanel. I had a message that I forwarded
>> to a list using Outlook 2010. It looked fine in Outlook, but when it
>> went to list all ' apostrophes were changed to ? question mark. What
>> causes this, and how can I prevent it.
>>
>> Dave 
> The lists language is set to use a National Code page, and Outlook
> formatted the message to use a 'Smart Quote' that isn't part of that
> Code Page.


I'm not sure what's happening. Yes, Outlook represented the message in a
character set (code page) which wasn't compatible with the list's
language character set, probably us-ascii, but this should affect only
plain format digests and archives where the message is represented in
the list's character set. For individual messages sent to the list
members and MIME format digest, there should be no transliteration.

-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan

From raj at mischievous.us  Tue Jun 26 21:06:43 2018
From: raj at mischievous.us (Richard Johnson)
Date: Tue, 26 Jun 2018 18:06:43 -0700
Subject: [Mailman-Users] How to track down someone mislabeling msgs as
 abuse?
In-Reply-To: <5c44ad66-7398-2bd0-a1c7-d000a7a6280a@msapiro.net>
References: <198406E0-25DA-4268-9A17-D31F7D6039A4@mischievous.us>
 <5c44ad66-7398-2bd0-a1c7-d000a7a6280a@msapiro.net>
Message-ID: <FE10F218-EF3A-4CD4-B091-BC2B0E27B87A@mischievous.us>

Thanks!  I have now upgraded to 2.1.27 and inserted this config.  My test worked and I see how to decode it.  Hopefully, I'm well placed when I see some of this "abuse" nonsense again.  :)

/raj



> On Jun 25, 2018, at 10:19 PM, Mark Sapiro <mark at msapiro.net> wrote:
> 
> On 6/25/18 11:39 AM, Richard Johnson wrote:
>> I have a mailing list which has 51 members, all friends of mine.  We use it to communicate on things related to our history club.  About 1-2 times a month, I receive an automated message from AOL's abuse list, saying that someone has marked one of the messages as "abuse".  Unfortunately, there's no way to track down who this could be, since there are about 5 addresses on the list which are AOL addresses.  
> 
> 
> Sorry about the prior fumbled send :(
> 
> In my experience, AOL's redaction is not always complete, particularly
> if the message is VERPed, but in any case, beginning with Mailman 2.1.24
> we have
> 
>>    - There is a new RCPT_BASE64_HEADER_NAME setting.  If this is set to a
>>      non-empty string, that string is the name of a header that will be added
>>      to personalized and VERPed deliveries with value equal to the base64
>>      encoding of the recipient's email address.  This is intended to enable
>>      identification of the recipient otherwise redacted from "spam report"
>>      feedback loop messages.
> 
> E.g., set
> 
> RCPT_BASE64_HEADER_NAME = 'X-My-Recip'
> 
> in mm_cfg.py and the VERPed or personalized message will have a
> 
> X-My-Recip: header with the base64 encoded recip. The name of the header
> is a setting to prevent AOL from knowing what it is and redacting it too.
> 
> -- 
> Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
> San Francisco Bay Area, California    better use your sense - B. Dylan
> ------------------------------------------------------
> Mailman-Users mailing list Mailman-Users at 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/raj%40mischievous.us


From dandrews at visi.com  Tue Jun 26 23:09:46 2018
From: dandrews at visi.com (David Andrews)
Date: Tue, 26 Jun 2018 22:09:46 -0500
Subject: [Mailman-Users] Changing Characters
In-Reply-To: <129a3a13-8136-0518-5a71-e6c2cbd66589@msapiro.net>
References: <auto-000106097873@mailfront2.g2host.com>
 <8e46263f-58bd-602d-9809-741f164ce8c5@Damon-Family.org>
 <129a3a13-8136-0518-5a71-e6c2cbd66589@msapiro.net>
Message-ID: <auto-000106907495@mailfront1.g2host.com>

At 07:40 PM 6/26/2018, Mark Sapiro wrote:
>On 6/26/18 5:03 PM, Richard Damon wrote:
> > On 6/26/18 2:12 PM, David Andrews wrote:
> >> I am running Mailman 2.1.26, cPanel. I had a message that I forwarded
> >> to a list using Outlook 2010. It looked fine in Outlook, but when it
> >> went to list all ' apostrophes were changed to ? question mark. What
> >> causes this, and how can I prevent it.
> >>
> >> Dave
> > The lists language is set to use a National Code page, and Outlook
> > formatted the message to use a 'Smart Quote' that isn't part of that
> > Code Page.
>
>
>I'm not sure what's happening. Yes, Outlook represented the message in a
>character set (code page) which wasn't compatible with the list's
>language character set, probably us-ascii, but this should affect only
>plain format digests and archives where the message is represented in
>the list's character set. For individual messages sent to the list
>members and MIME format digest, there should be no transliteration.

This wasn't in the digest, it was in a regular message.

Dave




---
This email has been checked for viruses by AVG.
https://www.avg.com


From cwieland at uci.edu  Tue Jun 26 23:44:26 2018
From: cwieland at uci.edu (cwieland at uci.edu)
Date: Tue, 26 Jun 2018 20:44:26 -0700
Subject: [Mailman-Users] can not add subscribers to list
Message-ID: <A9BE70FB-00AE-40F6-8554-2F89BC3BA0B2@uci.edu>

I have one list that will not add subscribers. I get this in the logs:

subscribe:Jun 26 20:35:40 2018 (24695) cogsci-aic: pending "thehdguy at cathyscorner.us" <thehdguy at cathyscorner.us>  128.200.115.74

but it adds -owner to the address so the email fails

Jun 26 20:35:41 department-lists postfix/smtp[24704]: 4A37512C057: to=<thehdguy-owner at cathyscorner.us>, relay=vade-in1.mail.dreamhost.com[66.33.205.212]:25, delay=0.49, delays=0.02/0.01/0.42/0.05, dsn=5.7.1, status=bounced (host vade-in1.mail.dreamhost.com[66.33.205.212] said: 550 5.7.1 <thehdguy-owner at cathyscorner.us>: Recipient address rejected: User unknown. (in reply to RCPT TO command))

I have looked thru the configuration and can not find anything unusual. Theis server has 100?s of lists. A quick check and other lists all seem to be working as expected. 

Any ideas would be greatly appreciated.

Best,
Con Wieland

From cwieland at uci.edu  Wed Jun 27 00:26:39 2018
From: cwieland at uci.edu (cwieland at uci.edu)
Date: Tue, 26 Jun 2018 21:26:39 -0700
Subject: [Mailman-Users] can not add subscribers to list
In-Reply-To: <A9BE70FB-00AE-40F6-8554-2F89BC3BA0B2@uci.edu>
References: <A9BE70FB-00AE-40F6-8554-2F89BC3BA0B2@uci.edu>
Message-ID: <5F3E55F1-C9BD-4923-9E89-35714A70137B@uci.edu>


Problem solved. It was the 

Send password reminders to, eg, "-owner" address instead of directly to user. 
(Details for umbrella_list)

set to yes so was appending -owner to the requests.


> On Jun 26, 2018, at 8:44 PM, cwieland at uci.edu wrote:
> 
> I have one list that will not add subscribers. I get this in the logs:
> 
> subscribe:Jun 26 20:35:40 2018 (24695) cogsci-aic: pending "thehdguy at cathyscorner.us" <thehdguy at cathyscorner.us>  128.200.115.74
> 
> but it adds -owner to the address so the email fails
> 
> Jun 26 20:35:41 department-lists postfix/smtp[24704]: 4A37512C057: to=<thehdguy-owner at cathyscorner.us>, relay=vade-in1.mail.dreamhost.com[66.33.205.212]:25, delay=0.49, delays=0.02/0.01/0.42/0.05, dsn=5.7.1, status=bounced (host vade-in1.mail.dreamhost.com[66.33.205.212] said: 550 5.7.1 <thehdguy-owner at cathyscorner.us>: Recipient address rejected: User unknown. (in reply to RCPT TO command))
> 
> I have looked thru the configuration and can not find anything unusual. Theis server has 100?s of lists. A quick check and other lists all seem to be working as expected. 
> 
> Any ideas would be greatly appreciated.
> 
> Best,
> Con Wieland
> ------------------------------------------------------
> Mailman-Users mailing list Mailman-Users at 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/cwieland%40uci.edu
> 


From mark at msapiro.net  Wed Jun 27 01:25:26 2018
From: mark at msapiro.net (Mark Sapiro)
Date: Tue, 26 Jun 2018 22:25:26 -0700
Subject: [Mailman-Users] Changing Characters
In-Reply-To: <auto-000106907495@mailfront1.g2host.com>
References: <auto-000106097873@mailfront2.g2host.com>
 <8e46263f-58bd-602d-9809-741f164ce8c5@Damon-Family.org>
 <129a3a13-8136-0518-5a71-e6c2cbd66589@msapiro.net>
 <auto-000106907495@mailfront1.g2host.com>
Message-ID: <c005fb62-fc85-134e-5038-8947f3850824@msapiro.net>

On 6/26/18 8:09 PM, David Andrews wrote:
> At 07:40 PM 6/26/2018, Mark Sapiro wrote:
>>
>> I'm not sure what's happening. Yes, Outlook represented the message in a
>> character set (code page) which wasn't compatible with the list's
>> language character set, probably us-ascii, but this should affect only
>> plain format digests and archives where the message is represented in
>> the list's character set. For individual messages sent to the list
>> members and MIME format digest, there should be no transliteration.
> 
> This wasn't in the digest, it was in a regular message.


I suppose it's possible that an HTML message was converted to plain text
by content filtering, but in order to say more, we'd need to see a
complete raw message, preferably both as sent to the list and as
received from the list.

-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan

From mark at msapiro.net  Wed Jun 27 01:33:10 2018
From: mark at msapiro.net (Mark Sapiro)
Date: Tue, 26 Jun 2018 22:33:10 -0700
Subject: [Mailman-Users] can not add subscribers to list
In-Reply-To: <A9BE70FB-00AE-40F6-8554-2F89BC3BA0B2@uci.edu>
References: <A9BE70FB-00AE-40F6-8554-2F89BC3BA0B2@uci.edu>
Message-ID: <6d4d3c0d-ef08-bfb7-974a-7e46a73781f8@msapiro.net>

On 6/26/18 8:44 PM, cwieland at uci.edu wrote:
> 
> but it adds -owner to the address so the email fails
> 
> Jun 26 20:35:41 department-lists postfix/smtp[24704]: 4A37512C057: to=<thehdguy-owner at cathyscorner.us>, relay=vade-in1.mail.dreamhost.com[66.33.205.212]:25, delay=0.49, delays=0.02/0.01/0.42/0.05, dsn=5.7.1, status=bounced (host vade-in1.mail.dreamhost.com[66.33.205.212] said: 550 5.7.1 <thehdguy-owner at cathyscorner.us>: Recipient address rejected: User unknown. (in reply to RCPT TO command))


It adds -owner because the list's General Options -> umbrella_list is Yes.

-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan

From steve at pearwood.info  Wed Jun 27 01:37:32 2018
From: steve at pearwood.info (Steven D'Aprano)
Date: Wed, 27 Jun 2018 15:37:32 +1000
Subject: [Mailman-Users] Changing Characters
In-Reply-To: <auto-000106907495@mailfront1.g2host.com>
References: <auto-000106097873@mailfront2.g2host.com>
 <8e46263f-58bd-602d-9809-741f164ce8c5@Damon-Family.org>
 <129a3a13-8136-0518-5a71-e6c2cbd66589@msapiro.net>
 <auto-000106907495@mailfront1.g2host.com>
Message-ID: <20180627053731.GZ14437@ando.pearwood.info>

On Tue, Jun 26, 2018 at 10:09:46PM -0500, David Andrews wrote:
> At 07:40 PM 6/26/2018, Mark Sapiro wrote:
> >On 6/26/18 5:03 PM, Richard Damon wrote:
> >> On 6/26/18 2:12 PM, David Andrews wrote:
> >>> I am running Mailman 2.1.26, cPanel. I had a message that I forwarded
> >>> to a list using Outlook 2010. It looked fine in Outlook, but when it
> >>> went to list all ' apostrophes were changed to ? question mark. What
> >>> causes this, and how can I prevent it.
> >>>
> >>> Dave
> >> The lists language is set to use a National Code page, and Outlook
> >> formatted the message to use a 'Smart Quote' that isn't part of that
> >> Code Page.
> >
> >
> >I'm not sure what's happening. Yes, Outlook represented the message in a
> >character set (code page) which wasn't compatible with the list's
> >language character set, probably us-ascii, but this should affect only
> >plain format digests and archives where the message is represented in
> >the list's character set. For individual messages sent to the list
> >members and MIME format digest, there should be no transliteration.
> 
> This wasn't in the digest, it was in a regular message.

Look at the charset used by the email, the charset the mail client uses, 
and the actual characters in use. If there's a discrepency between any 
of them, weird things are displayed.

Look at the email's Content-Type header, it should look something like 
this:

    Content-Type: text/plain; charset="us-ascii";

(Actually email should use utf-8, ALWAYS, but hardly anything does.)

Given that this has some sort of curly quotes, it ought to use UTF-8, 
not ASCII, but so many Windows applications fail to UTF-8 when they 
should it is heart-breaking.
 
Second-best should be Windows-1252, sometimes called CP-1252. If it is 
labelled "iso-8859-1" that's wrong but common. If there's no charset 
declared at all, assume the encoding is actually Windows-1252 given 
that it has come from Outlook.

Then look at your email client. (Which is...?) It ought to honour the 
Content-Type header, but some older email clients don't and just assume 
everything is ASCII or the machine's default code page, whatever that 
is. If there is a way to instruct your client to change encodings (there 
is often an "Encoding" menu, try setting it by hand and see if the 
invalid question marks change to ? characters. (That's a U+2019 RIGHT 
SINGLE QUOTATION MARK.)

Finally, try looking at the "Raw Contents" or "Full Email" or whatever 
your email client calls it -- you want to look at the raw content of the 
email, in full. Find the places where the mystery question marks are, 
and see what you can see. If you're lucky, it will be some sort of 
little square box with a four-digit hex code in it, like 0098 or FFFF.

(But don't be surprised if it isn't visible at all.)


-- 
Steve

From Michael.D.Parker at ga.com  Wed Jun 27 17:26:09 2018
From: Michael.D.Parker at ga.com (Parker, Michael D.)
Date: Wed, 27 Jun 2018 21:26:09 +0000
Subject: [Mailman-Users] Changing the name of existing mailing lists
Message-ID: <55a78d4de7ac45dabce83b152fa5badc@ASGEXCPWP05.ga.com>

Is there a way to change the name of a mailing list?

Thanks.

From Michael.D.Parker at ga.com  Wed Jun 27 17:23:56 2018
From: Michael.D.Parker at ga.com (Parker, Michael D.)
Date: Wed, 27 Jun 2018 21:23:56 +0000
Subject: [Mailman-Users] Supressing storage of attachments
Message-ID: <c131b28a9f384564966cdf71bde903f1@ASGEXCPWP05.ga.com>

On mailman2 .... I'd like to inhibit the storage of attachments in the archives.

Is there a global option to inhibit this?

Thanks.



From mark at msapiro.net  Wed Jun 27 17:32:23 2018
From: mark at msapiro.net (Mark Sapiro)
Date: Wed, 27 Jun 2018 14:32:23 -0700
Subject: [Mailman-Users] Supressing storage of attachments
In-Reply-To: <c131b28a9f384564966cdf71bde903f1@ASGEXCPWP05.ga.com>
References: <c131b28a9f384564966cdf71bde903f1@ASGEXCPWP05.ga.com>
Message-ID: <fc4f7d2f-bb04-4866-5b44-fea48d9b8e5c@msapiro.net>

On 6/27/18 2:23 PM, Parker, Michael D. wrote:
> On mailman2 .... I'd like to inhibit the storage of attachments in the archives.
> 
> Is there a global option to inhibit this?


No. You can use content filtering to remove them, but if you want them
to remain in list mail they will also be in the archives.

-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan

From Michael.D.Parker at ga.com  Wed Jun 27 17:38:25 2018
From: Michael.D.Parker at ga.com (Parker, Michael D.)
Date: Wed, 27 Jun 2018 21:38:25 +0000
Subject: [Mailman-Users] -EXT-Re:  Supressing storage of attachments
In-Reply-To: <fc4f7d2f-bb04-4866-5b44-fea48d9b8e5c@msapiro.net>
References: <c131b28a9f384564966cdf71bde903f1@ASGEXCPWP05.ga.com>
 <fc4f7d2f-bb04-4866-5b44-fea48d9b8e5c@msapiro.net>
Message-ID: <d67b13c6887f4be2a709f86b7ac84c10@ASGEXCPWP05.ga.com>

Since I am suppressing the generation of Archives globally....would it be ok to periodically remove these attachment directories and files left in the archive directory for each mailing list?

***** ***** ***** ***** ***** *****
Michael D. Parker 
CyberSecurity Engineering
General Atomics - ElectroMagnetics Systems Group
Office: +1 858 964 6675 // Cell: +1 858 376 7474
16969 Mesamint Street / San Diego / CA / 92127
michael.d.parker at ga.com      <<<<< NOTE:  Remember to include my middle initial >>>>>


************************************************************************** 
CONFIDENTIALITY NOTICE: This communication is intended to be confidential to the person(s)
 to whom it is addressed. If you are not the intended recipient or the agent of the intended 
recipient or if you are unable to deliver this communication to the intended recipient, you 
must not read, use or disseminate this information. If you have received this communication 
in error, please advise the sender immediately by telephone and delete this message and any
 attachments without retaining a copy. 
**************************************************************************


-----Original Message-----
From: Mailman-Users <mailman-users-bounces+michael.d.parker=ga.com at python.org> On Behalf Of Mark Sapiro
Sent: Wednesday, June 27, 2018 14:32
To: mailman-users at python.org
Subject: -EXT-Re: [Mailman-Users] Supressing storage of attachments

On 6/27/18 2:23 PM, Parker, Michael D. wrote:
> On mailman2 .... I'd like to inhibit the storage of attachments in the archives.
> 
> Is there a global option to inhibit this?


No. You can use content filtering to remove them, but if you want them to remain in list mail they will also be in the archives.

-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan
------------------------------------------------------
Mailman-Users mailing list Mailman-Users at 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/michael.d.parker%40ga.com


From Michael.D.Parker at ga.com  Wed Jun 27 17:44:08 2018
From: Michael.D.Parker at ga.com (Parker, Michael D.)
Date: Wed, 27 Jun 2018 21:44:08 +0000
Subject: [Mailman-Users] Changing the name of existing mailing lists --
 found in wiki
Message-ID: <121cfbe457144cc3a92e69d0dbd9ea33@ASGEXCPWP05.ga.com>

Found it in the Wiki....I am using the Method 3 (moving files)....what confused me was the fact that the name of the mailing list once changed contained the OLD name and not the NEW name.  The Wiki entry addresses the fact too.

Sorry.

***** ***** ***** ***** ***** *****


-----Original Message-----
From: Mailman-Users <mailman-users-bounces+michael.d.parker=ga.com at python.org> On Behalf Of Parker, Michael D.
Sent: Wednesday, June 27, 2018 14:26
To: mailman-users at python.org
Subject: -EXT-[Mailman-Users] Changing the name of existing mailing lists

Is there a way to change the name of a mailing list?

Thanks.
------------------------------------------------------
Mailman-Users mailing list Mailman-Users at 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/michael.d.parker%40ga.com


From mark at msapiro.net  Wed Jun 27 17:48:51 2018
From: mark at msapiro.net (Mark Sapiro)
Date: Wed, 27 Jun 2018 14:48:51 -0700
Subject: [Mailman-Users] Changing the name of existing mailing lists
In-Reply-To: <55a78d4de7ac45dabce83b152fa5badc@ASGEXCPWP05.ga.com>
References: <55a78d4de7ac45dabce83b152fa5badc@ASGEXCPWP05.ga.com>
Message-ID: <cb9e4b8b-4276-63dc-8b9b-d25844dd3451@msapiro.net>

On 6/27/18 2:26 PM, Parker, Michael D. wrote:
> Is there a way to change the name of a mailing list?


There's a script at <https://www.msapiro.net/scripts/clone_list>
(mirrored at <https://fog.ccsf.edu/~msapiro/scripts/clone_list>) which
will create a duplicate list with a new name. It has options to
duplicate the membership and archives. There will be issues with the
archives as discussed in the script's help.

You can also do it manually by renaming lists/<listname>,
archives/private/<listname>/, archives/private/<listname>.mbox/ and
archives/private/<listname>.mbox/<listname>.mbox and changing the list's
real_name attribute and rebuilding or manually fixing archive links.

-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan

From mark at msapiro.net  Wed Jun 27 17:56:03 2018
From: mark at msapiro.net (Mark Sapiro)
Date: Wed, 27 Jun 2018 14:56:03 -0700
Subject: [Mailman-Users] -EXT-Re: Supressing storage of attachments
In-Reply-To: <d67b13c6887f4be2a709f86b7ac84c10@ASGEXCPWP05.ga.com>
References: <c131b28a9f384564966cdf71bde903f1@ASGEXCPWP05.ga.com>
 <fc4f7d2f-bb04-4866-5b44-fea48d9b8e5c@msapiro.net>
 <d67b13c6887f4be2a709f86b7ac84c10@ASGEXCPWP05.ga.com>
Message-ID: <52c3e238-e4b0-fef6-acc3-5168f18813ab@msapiro.net>

On 6/27/18 2:38 PM, Parker, Michael D. wrote:
> Since I am suppressing the generation of Archives globally....would it be ok to periodically remove these attachment directories and files left in the archive directory for each mailing list?


If you don't care about the fact that links in the archive and plain
digests that point to these files will be broken, there's no other issue.

But, what do you mean by "suppressing the generation of Archives
globally"? If you are not archiving, these files/directories will only
be created for attachments scrubbed from plain format digests, and I
suppose you could also make your lists not digestable to avoid that too.

-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan

From Michael.D.Parker at ga.com  Wed Jun 27 18:00:21 2018
From: Michael.D.Parker at ga.com (Parker, Michael D.)
Date: Wed, 27 Jun 2018 22:00:21 +0000
Subject: [Mailman-Users] -EXT-Re: Supressing storage of attachments
In-Reply-To: <52c3e238-e4b0-fef6-acc3-5168f18813ab@msapiro.net>
References: <c131b28a9f384564966cdf71bde903f1@ASGEXCPWP05.ga.com>
 <fc4f7d2f-bb04-4866-5b44-fea48d9b8e5c@msapiro.net>
 <d67b13c6887f4be2a709f86b7ac84c10@ASGEXCPWP05.ga.com>
 <52c3e238-e4b0-fef6-acc3-5168f18813ab@msapiro.net>
Message-ID: <5ad692aebc364865b2073cda81f9221c@ASGEXCPWP05.ga.com>

I've disabled Archives and Digesting via the global settings previously communicated in an earlier email here on the list.

Thus I don't think there would be any links to anything in this scenario.



-----Original Message-----
From: Mailman-Users <mailman-users-bounces+michael.d.parker=ga.com at python.org> On Behalf Of Mark Sapiro
Sent: Wednesday, June 27, 2018 14:56
To: mailman-users at python.org
Subject: Re: [Mailman-Users] -EXT-Re: Supressing storage of attachments

On 6/27/18 2:38 PM, Parker, Michael D. wrote:
> Since I am suppressing the generation of Archives globally....would it be ok to periodically remove these attachment directories and files left in the archive directory for each mailing list?


If you don't care about the fact that links in the archive and plain digests that point to these files will be broken, there's no other issue.

But, what do you mean by "suppressing the generation of Archives globally"? If you are not archiving, these files/directories will only be created for attachments scrubbed from plain format digests, and I suppose you could also make your lists not digestable to avoid that too.

-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan
------------------------------------------------------
Mailman-Users mailing list Mailman-Users at 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/michael.d.parker%40ga.com


From mark at msapiro.net  Wed Jun 27 20:02:21 2018
From: mark at msapiro.net (Mark Sapiro)
Date: Wed, 27 Jun 2018 17:02:21 -0700
Subject: [Mailman-Users] -EXT-Re: Supressing storage of attachments
In-Reply-To: <5ad692aebc364865b2073cda81f9221c@ASGEXCPWP05.ga.com>
References: <c131b28a9f384564966cdf71bde903f1@ASGEXCPWP05.ga.com>
 <fc4f7d2f-bb04-4866-5b44-fea48d9b8e5c@msapiro.net>
 <d67b13c6887f4be2a709f86b7ac84c10@ASGEXCPWP05.ga.com>
 <52c3e238-e4b0-fef6-acc3-5168f18813ab@msapiro.net>
 <5ad692aebc364865b2073cda81f9221c@ASGEXCPWP05.ga.com>
Message-ID: <b5bb9e9a-e62b-ab3c-1492-8517ceeca56e@msapiro.net>

On 6/27/18 3:00 PM, Parker, Michael D. wrote:
> I've disabled Archives and Digesting via the global settings previously communicated in an earlier email here on the list.


So you've removed ToArchive and ToDigest from the global pipiline in
which case, nothing should be creating anything in the archives/private/
hierarchy so there should be nothing to remove.

-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan

From Michael.D.Parker at ga.com  Wed Jun 27 20:15:46 2018
From: Michael.D.Parker at ga.com (Parker, Michael D.)
Date: Thu, 28 Jun 2018 00:15:46 +0000
Subject: [Mailman-Users] -EXT-Re: Supressing storage of attachments
In-Reply-To: <b5bb9e9a-e62b-ab3c-1492-8517ceeca56e@msapiro.net>
References: <c131b28a9f384564966cdf71bde903f1@ASGEXCPWP05.ga.com>
 <fc4f7d2f-bb04-4866-5b44-fea48d9b8e5c@msapiro.net>
 <d67b13c6887f4be2a709f86b7ac84c10@ASGEXCPWP05.ga.com>
 <52c3e238-e4b0-fef6-acc3-5168f18813ab@msapiro.net>
 <5ad692aebc364865b2073cda81f9221c@ASGEXCPWP05.ga.com>
 <b5bb9e9a-e62b-ab3c-1492-8517ceeca56e@msapiro.net>
Message-ID: <e51f6df2259c4907bcad74c0b00602d6@ASGEXCPWP05.ga.com>

Hmmm....I think that you are probably correct.  

I checked the date of the files involved and they date back to when I was doing the initial install and testing.

So I just deleted all the "attachment" directories in the archives area as there was only index.html files in there otherwise.



-----Original Message-----
From: Mailman-Users <mailman-users-bounces+michael.d.parker=ga.com at python.org> On Behalf Of Mark Sapiro
Sent: Wednesday, June 27, 2018 17:02
To: mailman-users at python.org
Subject: Re: [Mailman-Users] -EXT-Re: Supressing storage of attachments

On 6/27/18 3:00 PM, Parker, Michael D. wrote:
> I've disabled Archives and Digesting via the global settings previously communicated in an earlier email here on the list.


So you've removed ToArchive and ToDigest from the global pipiline in which case, nothing should be creating anything in the archives/private/ hierarchy so there should be nothing to remove.

-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan
------------------------------------------------------
Mailman-Users mailing list Mailman-Users at 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/michael.d.parker%40ga.com


From dandrews at visi.com  Wed Jun 27 22:56:37 2018
From: dandrews at visi.com (David Andrews)
Date: Wed, 27 Jun 2018 21:56:37 -0500
Subject: [Mailman-Users] Changing Characters
In-Reply-To: <c005fb62-fc85-134e-5038-8947f3850824@msapiro.net>
References: <auto-000106097873@mailfront2.g2host.com>
 <8e46263f-58bd-602d-9809-741f164ce8c5@Damon-Family.org>
 <129a3a13-8136-0518-5a71-e6c2cbd66589@msapiro.net>
 <auto-000106907495@mailfront1.g2host.com>
 <c005fb62-fc85-134e-5038-8947f3850824@msapiro.net>
Message-ID: <auto-000106975368@mailfront1.g2host.com>

At one time I changed some settings in Content Filtering, on all my 
lists.  It was quite a few versions ago, to solve some problem that I 
can't even remember.  I am still doing it, remove everything from 
filter these content types, I think. Would that do it, should I restore them?

Dave

At 12:25 AM 6/27/2018, Mark Sapiro wrote:
>On 6/26/18 8:09 PM, David Andrews wrote:
> > At 07:40 PM 6/26/2018, Mark Sapiro wrote:
> >>
> >> I'm not sure what's happening. Yes, Outlook represented the message in a
> >> character set (code page) which wasn't compatible with the list's
> >> language character set, probably us-ascii, but this should affect only
> >> plain format digests and archives where the message is represented in
> >> the list's character set. For individual messages sent to the list
> >> members and MIME format digest, there should be no transliteration.
> >
> > This wasn't in the digest, it was in a regular message.
>
>
>I suppose it's possible that an HTML message was converted to plain text
>by content filtering, but in order to say more, we'd need to see a
>complete raw message, preferably both as sent to the list and as
>received from the list.
>
>--
>Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
>San Francisco Bay Area, California    better use your sense - B. Dylan
>------------------------------------------------------
>Mailman-Users mailing list Mailman-Users at 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/dandrews%40visi.com


---
This email has been checked for viruses by AVG.
https://www.avg.com


From mark at msapiro.net  Wed Jun 27 23:11:04 2018
From: mark at msapiro.net (Mark Sapiro)
Date: Wed, 27 Jun 2018 20:11:04 -0700
Subject: [Mailman-Users] Changing Characters
In-Reply-To: <auto-000106975368@mailfront1.g2host.com>
References: <auto-000106097873@mailfront2.g2host.com>
 <8e46263f-58bd-602d-9809-741f164ce8c5@Damon-Family.org>
 <129a3a13-8136-0518-5a71-e6c2cbd66589@msapiro.net>
 <auto-000106907495@mailfront1.g2host.com>
 <c005fb62-fc85-134e-5038-8947f3850824@msapiro.net>
 <auto-000106975368@mailfront1.g2host.com>
Message-ID: <2d97d144-f874-8c31-a69a-4f78e0c9057a@msapiro.net>

On 6/27/18 7:56 PM, David Andrews wrote:
> At one time I changed some settings in Content Filtering, on all my
> lists.? It was quite a few versions ago, to solve some problem that I
> can't even remember.? I am still doing it, remove everything from filter
> these content types, I think. Would that do it, should I restore them?


A possibility is:

1) Outlook composes a message in some character set that supports 'right
single quote' as a fancy apostrophe.

2) The message is composed as HTML only - there are other possibilities,
but this is the simplest.

3) Mailman's content filtering accepts text/html anc
convert_html_to_plaintext is Yes.

4) The converted plain text is rendered as ascii and the fancy 'right
single quote' is rendered as '?'.

If this is the issue, you can set convert_html_to_plaintext to No to
avoid it.

-- 
Mark Sapiro <mark at msapiro.net>        The highway is for gamblers,
San Francisco Bay Area, California    better use your sense - B. Dylan