[Mailman-Users] Re: Python 2.7.15, etc, vs Python3...

On Tue, 2023-07-18 at 02:05 +, Carl Zwanzig wrote: > On 7/17/2023 5:54 PM, Grant Taylor via Mailman-Users wrote: > > Python 2 and Python 3 are enough different to effectively be > > different languages. > > BTW, there is a python2 to 3 converter,  There's also this project:

[Mailman-Users] Re: AT RBL again

On Tue, 2021-03-30 at 14:14 -0700, Mark Sapiro wrote: > On 3/30/21 1:50 PM, Robert Heller wrote: > > At Tue, 30 Mar 2021 10:41:47 -0700 Mark Sapiro wrote: > > > > > That's probably correct, but are there other cloud VPS providers that > > > are better at hosting MTAs? > > > > Almost certainly.

[Mailman-Users] Re: mailman v2.x

On Sun, 2020-09-20 at 23:40 +0900, Stephen J. Turnbull wrote: > Jim Popovitch via Mailman-Users writes: > > On Sun, 2020-09-20 at 18:23 +0900, Stephen J. Turnbull wrote: > > > I imagine ARC support is something Jim Popovitch would like to have. > > > You imagine w

[Mailman-Users] Re: mailman v2.x

; fairly easy to port (I'm pretty sure the underlying libraries are 2/3 > compatible). (Ports are fair game because we're talking "future", and > I imagine ARC support is something Jim Popovitch would like to have.) You imagine wrong. I see ARC as a piece of the delivery ph

[Mailman-Users] Re: mailman v2.x

On Thu, 2020-09-17 at 14:56 -0400, Brian Carpenter wrote: > On 9/17/20 2:27 PM, Jim Popovitch via Mailman-Users wrote: > > On Thu, 2020-09-17 at 14:15 -0400, Brian Carpenter wrote: > > Absolutely not. I'm intrigued by the idea of mailman-core (1/3 of mm3) > > with a ligh

[Mailman-Users] Re: mailman v2.x

On Thu, 2020-09-17 at 14:15 -0400, Brian Carpenter wrote: > On 9/17/20 1:45 PM, Jim Popovitch via Mailman-Users wrote: > > That's kind of my point. mm2 works for me and my use, I'd much rather > > prefer to keep it working than to rip it out and replace it, including > > inst

[Mailman-Users] Re: mailman v2.x

On Thu, 2020-09-17 at 09:07 -0700, Mark Sapiro wrote: > On 9/17/20 8:04 AM, Jim Popovitch via Mailman-Users wrote: > > On Thu, 2020-09-17 at 07:54 -0700, Mark Sapiro wrote: > > > Forward to where? > > > > Oh the irony of you asking that question. :) If we go bac

[Mailman-Users] Re: mailman v2.x

On Thu, 2020-09-17 at 07:54 -0700, Mark Sapiro wrote: > On 9/17/20 7:36 AM, Jim Popovitch via Mailman-Users wrote: > > Here's my POV, if mm2 can (and it appears to me that it > > can somewhat easily) be fixed to use py3 then all the installed bases of > > mm2 don't have to l

[Mailman-Users] Re: mailman v2.x

On Thu, 2020-09-17 at 07:13 -0700, Mark Sapiro wrote: > On 9/17/20 6:54 AM, Matthew Pounsett wrote: > > If someone was going to undertake a rewrite of Postorius, using a different > > web development framework (e.g. Flask, but pretty much anything that isn't > > Django) would at least remove one

[Mailman-Users] Re: mailman v2.x

On Thu, 2020-09-17 at 18:47 +0900, Stephen J. Turnbull wrote: > Jim Popovitch via Mailman-Users writes: > > On Thu, 2020-09-17 at 02:34 +0900, Stephen J. Turnbull wrote: > > > > You don't need to have a title, an @mailman email address, or a commit &

[Mailman-Users] Re: mailman v2.x

On Thu, 2020-09-17 at 02:34 +0900, Stephen J. Turnbull wrote: > > You're right. If we're going to reopen the Mailman 2 branch to new > features, there should be a much larger body. So where is it? Mark > and I are not special. We're merely here every day, we have acquired > a lot of knowledge

[Mailman-Users] Re: mailman v2.x

On Tue, 2020-09-15 at 21:11 -0400, Brian Carpenter wrote: > On 9/15/20 8:18 PM, Jim Popovitch via Mailman-Users wrote: > > A small group, including myself, are planning to present a proposal. We > > are in the early stage of defining what that will involve, but we are > >

[Mailman-Users] Re: mailman v2.x

On Tue, 2020-09-15 at 16:51 -0700, Mark Sapiro wrote: > On 9/15/20 12:41 PM, Jim Popovitch via Mailman-Users wrote: > > I demanded nothing. I was told by Mark that I would need to apply for > > all those perks (sans the Cabal seat) when all I offered to do was > > suppor

[Mailman-Users] Re: mailman v2.x

On Wed, 2020-09-16 at 03:51 +0900, Stephen J. Turnbull wrote: > Jim Popovitch via Mailman-Users writes: > > > I personally think that you, Stephen, are digging high and low to find > > any reason for Mailman2 to not continue forward under the Mailman > > umbrella. >

[Mailman-Users] Re: mailman v2.x

On Tue, 2020-09-15 at 08:45 -0700, Mark Sapiro wrote: > On 9/15/20 4:40 AM, Jim Popovitch via Mailman-Users wrote: > > I'd use the new MM3 archive of this list to link to your posts, but > > interacting with it is an abysmal time waste. At a minimum someone > > should put B

[Mailman-Users] Re: mailman v2.x

On Tue, 2020-09-15 at 16:10 +0900, Stephen J. Turnbull wrote: > Jim Popovitch via Mailman-Users writes: > > > See Stephens previous comments about how there was no way he could > > or would work with anyone working on mm2 because it was against his > > object

[Mailman-Users] Re: mailman v2.x

On Sun, 2020-09-13 at 09:16 -0700, Mark Sapiro wrote: > On 9/13/20 9:01 AM, Jim Popovitch via Mailman-Users wrote: > > What I want to hear from the Cabal is that there is support and > > appreciation for efforts by others to carry on with mm2 in any direction &g

[Mailman-Users] Re: mailman v2.x

On Sun, 2020-09-13 at 15:36 +, Mark Sapiro wrote: > OK, I'm back and more or less caught up so I'm ready to continue this > discussion. > > In his initial post in this thread, Jim suggests that he and others want to > join the Mailman Coders team on Launchpad in order to commit to the

[Mailman-Users] Re: mailman v2.x

On Sun, 2020-08-30 at 14:29 +0900, Stephen J. Turnbull wrote: > I wrote a long screed, full of piss and vinegar. But on reflection, > clearly nobody is reading what I wrote earlier, so let's try pithy and > dry. It's still long. :-( > > Chip Davis writes: > > > OK guys, what's really going on

[Mailman-Users] Re: mailman v2.x

On Fri, 2020-08-28 at 23:47 -0700, Carl Zwanzig wrote: > > Or... it's pretty likely that MM2 maintenance, and maybe improvements, will > continue in some fashion. The question is whether that's under the auspices > of the gnu-mailman project or in a fork. If the existing gnu-mailman team >

[Mailman-Users] Re: mailman v2.x

On Sat, 2020-08-29 at 03:53 +0900, Stephen J. Turnbull wrote: > Jim Popovitch via Mailman-Users writes: > > > Again with the "Jim's team". Those other guys, that other group, them > > folks That's nauseating to hear from you Stephen. > > I use the word

[Mailman-Users] Re: mailman v2.x

On Thu, 2020-08-27 at 10:05 -0700, Mark Sapiro wrote: > On 8/27/20 3:29 AM, Jim Popovitch via Mailman-Users wrote: > > There is sooo much to respond to, but in order to stay on focus... > > Brian, you fail to identify the problem, in fact you mischaracterized > > it

[Mailman-Users] Re: mailman v2.x

On Thu, 2020-08-27 at 09:30 -0700, Mark Sapiro wrote: > On 8/27/20 3:41 AM, Jim Popovitch via Mailman-Users wrote: > > On Thu, 2020-08-27 at 17:41 +0900, Stephen J. Turnbull wrote: > > > The question for you is what benefit there is to anyone in having > > > M

[Mailman-Users] Re: mailman v2.x

On Thu, 2020-08-27 at 17:27 +0900, Stephen J. Turnbull wrote: > MM3, on the other hand, not only has three more or less active > developers, it also has frequent releases including new features as > well as bug fixes. That could still be happening for MM2 if not for some imaginary line in the

[Mailman-Users] Re: mailman v2.x

On Thu, 2020-08-27 at 17:41 +0900, Stephen J. Turnbull wrote: > > The question for you is what benefit there is to anyone in having > Mailman 2 maintenance inside the Mailman Project going forward. You mean inside the Mailman3 Project at mailman3.org? None. > The Mailman Project certainly

[Mailman-Users] Re: mailman v2.x

On Thu, 2020-08-27 at 17:24 +0900, Stephen J. Turnbull wrote: > Brian Carpenter writes: > > On 8/26/20 6:25 PM, Carl Zwanzig wrote: > > > > > > As someone regularly uses and maintains a fair bit of old and antique > > > machinery, MM2 still has a lot of life in it. > > In particular, MM2

[Mailman-Users] Re: mailman v2.x

On Wed, 2020-08-26 at 23:17 -0400, Brian Carpenter wrote: > > I am sure Mark has moved on from Mailman 2, at least he has said that on > numerous occasions. It is you folks that won't let him. There is sooo much to respond to, but in order to stay on focus... Brian, you fail to identify the

[Mailman-Users] Re: mailman v2.x

On Wed, 2020-08-26 at 20:25 -0400, Brian Carpenter wrote: > On 8/26/20 7:02 PM, Jim Popovitch via Mailman-Users wrote: > > I'm not sure where you think money comes into this, unless you are > > admitting that moving to mm3 requires expensive consulting contracts. > > I've tur

[Mailman-Users] Re: mailman v2.x

On Wed, 2020-08-26 at 17:05 -0400, Brian Carpenter wrote: snip-snip > I think the issue here is money and fear. Cheap cPanel hosts include > Mailman 2 with their budget hosting packages and I am pretty sure that > is who you are using. I'm not sure where you think money comes into this,

[Mailman-Users] Re: mailman v2.x

On Wed, 2020-08-26 at 23:52 +0900, Stephen J. Turnbull wrote: > Jim Popovitch via Mailman-Users writes: > > > A couple of days ago, over on the MAILOP mailinglist, there was a > > long thread titled 'Mailman confirmation email denial of service'. > > *sigh* The pric

[Mailman-Users] mailman v2.x

Hi Folks, A couple of days ago, over on the MAILOP mailinglist, there was a long thread titled 'Mailman confirmation email denial of service'. This detailed some of the problems we've all seen with Mailman subscription spam. The Mailman team has addressed a lot of these problems with ReCAPTCHA

[Mailman-Users] Re: Upgrading from 2.1.12

On Thu, 2020-07-23 at 10:15 -0500, Barry S. Finkel wrote: > > On Wed, Jul 22, 2020 at 11:40 PM Mark Sapiro wrote: > > > > > On 7/22/20 12:54 AM, Daniel Krause via Mailman-Users wrote: > > > > Good Day > > > > > > > > We have a running 2.1.12 installation that was done long ago via an > > > >

Re: [Mailman-Users] The last release from the GNU Mailman project (was: Handling Munged From Addresses)

On Mon, 2020-03-02 at 17:18 -0800, Mark Sapiro wrote: > On 3/2/20 1:55 PM, Jim Popovitch via Mailman-Users wrote: > > There are plenty of people who are still happy with pipermail and some > > of the other search options (Google, htdig, etc) What benefit does a > > REST

Re: [Mailman-Users] The last release from the GNU Mailman project (was: Handling Munged From Addresses)

On Mon, 2020-03-02 at 10:54 -0800, Mark Sapiro wrote: > On 3/2/20 8:56 AM, Jim Popovitch via Mailman-Users wrote: > > > Barry's roadmap > > for Python2 -> Python3 seems to counter the narrative that MM2 is ill- > > advised to be ported to Python3 (btw, that was pos

Re: [Mailman-Users] The last release from the GNU Mailman project (was: Handling Munged From Addresses)

On Mon, 2020-03-02 at 17:17 +0900, Stephen J. Turnbull wrote: > Jim Popovitch via Mailman-Users writes: > > > Interestingly enough, here's a roadmap on exactly how to do it: :) > > Jim, you're not helping. Stephen, thank you for taking the time to respond. Although I wo

Re: [Mailman-Users] The last release from the GNU Mailman project

On Sat, 2020-02-29 at 10:46 -0800, Mark Sapiro wrote: > On 2/29/20 7:02 AM, Jim Popovitch via Mailman-Users wrote: > > If > > a CSF/CSS is identified in Mailman v2.1.30 in May-2020, what will be > > done to address it? > > I'd say it depend on the details of ho

Re: [Mailman-Users] The last release from the GNU Mailman project (was: Handling Munged From Addresses)

On Thu, 2020-02-27 at 14:51 -0500, Bill Cole wrote: > On 27 Feb 2020, at 14:24, Jim Popovitch via Mailman-Users wrote: > > > Personally, I'd like to see the GNU Mailman project have a formal > > Mailman 2.3 release that supports Python3, I feel that there would be > &

Re: [Mailman-Users] The last release from the GNU Mailman project

On Sat, 2020-02-29 at 16:28 +0900, Stephen J. Turnbull wrote: > Mark Sapiro writes: > > > Well, Steve channeled me earlier, so I'll return the favor. > > And did it with extreme precision and accuracy. Sorry if I created > any misunderstandings. > > The only thing I have to add is that

Re: [Mailman-Users] The last release from the GNU Mailman project

On Fri, 2020-02-28 at 10:07 -0800, Mark Sapiro wrote: > On 2/28/20 6:17 AM, Jim Popovitch via Mailman-Users wrote: > > On Fri, 2020-02-28 at 19:52 +0900, Stephen J. Turnbull wrote: > > > Brian Carpenter writes: > > > > > > > I have hired a profession

Re: [Mailman-Users] The last release from the GNU Mailman project

On Fri, 2020-02-28 at 19:52 +0900, Stephen J. Turnbull wrote: > Brian Carpenter writes: > > > I have hired a professional PHP developer to begin work on a new > > admin/forum interface for Mailman 3. > > Too bad. I really sympathize with your goals but am unlikely to be > able to contribute

[Mailman-Users] The last release from the GNU Mailman project (was: Handling Munged From Addresses)

On Thu, 2020-02-27 at 10:56 -0800, Mark Sapiro wrote: > for Mailman 3, but that seems unduly kludgy. There won't be any change > in Mailman 2.1 which is only waiting for i18n updates for the final > 2.1.30 release which will be the last release from the GNU Mailman project. Who decides that there

Re: [Mailman-Users] Handling Munged From Addresses

On Thu, 2020-02-27 at 10:23 -0800, Mark Sapiro wrote: > On 2/27/20 10:05 AM, Jim Popovitch via Mailman-Users wrote: > > I've been wondering if we should change that to something like this: > > > > From: Jane Doe (jane@domain.tld) via Listname > > > > We sp

Re: [Mailman-Users] Handling Munged From Addresses

On Thu, 2020-02-27 at 09:58 -0800, Mark Sapiro wrote: > On 2/27/20 7:22 AM, Dennis Putnam wrote: > > I think this may have been addressed but I can't find it. Now that I am > > munging the from address to mitigate DMARC, recipients can no longer > > tell who the message is from. What are other

Re: [Mailman-Users] Apache subscription Referer rules

On Tue, 2020-01-14 at 00:19 -0500, Bill Cole wrote: > On 10 Jan 2020, at 10:52, Jim Popovitch via Mailman-Users wrote: > > > (I think I asked this a few months back, but I couldn't locate any > > emails on it) > > > > What is the Apache rule syntax for

[Mailman-Users] Apache subscription Referer rules

(I think I asked this a few months back, but I couldn't locate any emails on it) What is the Apache rule syntax for rejecting subscription linking that doesn't come from the same domain/site? tia, -Jim P. -- Mailman-Users mailing list

Re: [Mailman-Users] Mailman 3 Ready?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Mon, 2019-11-25 at 11:06 -0500, Jim Popovitch via Mailman-Users wrote: > On Mon, 2019-11-25 at 16:59 +0100, Johannes Rohr wrote: > > Am Mo., 25. Nov. 2019 um 16:47 Uhr schrieb Jim Popovitch via Mailman-Users > > : > > >

Re: [Mailman-Users] Mailman 3 Ready?

On Mon, 2019-11-25 at 16:59 +0100, Johannes Rohr wrote: > > Am Mo., 25. Nov. 2019 um 16:47 Uhr schrieb Jim Popovitch via Mailman-Users > : > > On Mon, 2019-11-25 at 10:17 -0500, Matthew Pounsett wrote: > > > Is there a timeline for that? Mailman 2.x requires python

Re: [Mailman-Users] Mailman 3 Ready?

On Mon, 2019-11-25 at 10:17 -0500, Matthew Pounsett wrote: > Is there a timeline for that? Mailman 2.x requires python 2.x, which is > EOL in about 40 days. I keep saying this a lot... the EOL you are referring to is Python's declared date that the Python team will no longer maintain Python2.

Re: [Mailman-Users] English (USA)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Tue, 2019-07-09 at 08:40 -0400, Timothy Jasionowski wrote: > I don’t really have a dog in this fight, but can we acknowledge that > this version of Mailman is effectively on life support for a variety > of reasons, that the limited developer

Re: [Mailman-Users] English (USA)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Mon, 2019-07-08 at 14:17 -0700, Carl Zwanzig wrote: > On 7/8/2019 1:51 PM, Jim Popovitch via Mailman-Users wrote: > > I just keep getting reminded that we specifically support USA English > > and we offer no other English l

Re: [Mailman-Users] English (USA)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Mon, 2019-07-08 at 13:32 -0700, Mark Sapiro wrote: > On 7/8/19 1:00 PM, Jim Popovitch via Mailman-Users wrote: > > > > Just to be clear, I'm not proposing changes to any po strings, rather > > just the labels. The end

Re: [Mailman-Users] English (USA)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Mon, 2019-07-08 at 12:46 -0700, Mark Sapiro wrote: > On 7/8/19 12:15 PM, Jim Popovitch via Mailman-Users wrote: > > > > > Now I'm confused. :-) I know about the differences in UK and US English > > are in general (colo

Re: [Mailman-Users] English (USA)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Mon, 2019-07-08 at 21:06 +0200, Christian F Buser wrote: > Hi Jim > > I do not know about where the English (US) and English (UK) languages differ > in Mailman. But in school, half a century ago, I learnt (learned) about the > differences in

[Mailman-Users] English (USA)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 It has been brought to my attention again that Mailman supports one dialect of English, but declares that it the USA variant. What in Mailman makes the English language (translations?) specific to USA? In the interest of world perspectives, would

Re: [Mailman-Users] What to do about SPF rejection?

On Mon, 2019-06-17 at 12:47 -0400, John Levine wrote: > In article you write: > > Dear all, > > > > I today saw three bounces where the receiving mail server had said: > > > > host mail.gfbv.de[185.199.217.16] said: 550 external MTA > >sending our header From: (in reply to > >end

Re: [Mailman-Users] Upgrading mm 2.1.26 on Ubuntu 18.04 to 2.1.29

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Thu, 2019-05-23 at 09:40 -0400, Fabian A. Santiago wrote: > also, that wiki page you sent me mention an error with missing dnspython > and it states to run this: > > "sudo apt-get install python-dnspython" > > but that claims it's already

Re: [Mailman-Users] Upgrading mm 2.1.26 on Ubuntu 18.04 to 2.1.29

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Thu, 2019-05-23 at 09:04 -0400, Fabian A. Santiago wrote: > > Thanks for this heads up. i should also mention adding the ppa to my apt > sources fails on gpg signing key import. i had to do it manually, > searching for the key on ubuntu's

Re: [Mailman-Users] Upgrading mm 2.1.26 on Ubuntu 18.04 to 2.1.29

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On Wed, 2019-05-22 at 08:42 -0700, Mark Sapiro wrote: > On 5/21/19 5:20 PM, Fabian Aldo Santiago wrote: > > > > So I started over (restored snapshot) and then tried adding a ppa apt > > source which contains 2.1.29: > > > >

Re: [Mailman-Users] Restrict archives to Administrator

On Thu, 2019-04-18 at 17:23 +0900, Stephen J. Turnbull wrote: > Mark Dale writes: > > > I've posted some notes on restricting a list's archive to Administrators > > only. They may be of use to some folks. > > Could you say something about the use case? If there's a common > enough reason for

Re: [Mailman-Users] Now that Python 2 is dead in 2020 what are people's plans with mailman2?

On Wed, 2019-04-10 at 09:25 -0700, Mark Sapiro wrote: > > The path forward is to increase the community of MM 3 users which will > result in more people contributing to the project and faster progress. What Mailman things need assistance in MM3? I've avoided jumping in because honestly every

Re: [Mailman-Users] Moderating if keywords mentioned?

On Sat, 2019-02-23 at 08:04 +1100, Peter Shute wrote: > Thanks. I assume that will work on subject lines, will it also > allow filtering on the message body? If not, is there any way > to do that? It won't work on msg body text. To do that you would need a custom handler (Mark sent that in his

Re: [Mailman-Users] Moderating if keywords mentioned?

On February 22, 2019 6:33:48 PM UTC, Peter Shute wrote: >Is it possible to specify keywords that will cause a matching message >to >held for moderation? I thought I'd seen something like this, but I >can't >find it in the admin interface. > It's under Privacy Options -> Spam Filters. Set a

Re: [Mailman-Users] Mailman & DMARC question

On Mon, 2018-11-05 at 10:07 -0600, David Gibbs wrote: > My quandary is: Is there any risk in implementing my own more > restrictive DMARC policy? > > Currently my DMARC policy is 'p=none' ... but I'd like to change that > to 'p=quarantine'. > > Is there any risk running mailing lists from a

Re: [Mailman-Users] GPG Sig parse error

On Thu, 2018-11-01 at 16:48 -0600, Grant Taylor via Mailman-Users wrote: > On 11/01/2018 01:49 PM, Jim Popovitch via Mailman-Users wrote: > > Apologies Grant it this is too much discussion of you :-) I'm only > > trying  > > to get to the root of the issue. > > No pro

Re: [Mailman-Users] GPG Sig parse error (was: Re: mm-handler starting version)

On Thu, 2018-11-01 at 13:07 -0700, Mark Sapiro wrote: > On 11/1/18 12:43 PM, Jim Popovitch via Mailman-Users wrote: > > > > Here's what I see https://i.imgur.com/xLDnojI.png in Evolution.  I > > was wrong to assume it was a PGP parse error, it does however look > > to

Re: [Mailman-Users] GPG Sig parse error (was: Re: mm-handler starting version)

On Thu, 2018-11-01 at 15:43 -0400, Jim Popovitch via Mailman-Users wrote: > On Thu, 2018-11-01 at 12:30 -0700, Mark Sapiro wrote: > > On 11/1/18 12:11 PM, Jim Popovitch via Mailman-Users wrote: > > > On Thu, 2018-11-01 at 12:27 -0600, Grant Taylor via Mailman

Re: [Mailman-Users] GPG Sig parse error (was: Re: mm-handler starting version)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On Thu, 2018-11-01 at 12:30 -0700, Mark Sapiro wrote: > On 11/1/18 12:11 PM, Jim Popovitch via Mailman-Users wrote: > > On Thu, 2018-11-01 at 12:27 -0600, Grant Taylor via Mailman-Users > > wrote: > > > Error verifyin

[Mailman-Users] GPG Sig parse error (was: Re: mm-handler starting version)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On Thu, 2018-11-01 at 12:27 -0600, Grant Taylor via Mailman-Users wrote: > Error verifying signature: parse error Hello, I changed the subject and have GPG signed this message. I've done this because I keep seeing GPG Sig parse errors for

[Mailman-Users] new Mailman Ubuntu builds (PPA)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hello, With some help from Mark and Barry, I was able to setup build "recipes" (Ubuntu Launchpad configurations) that will now automatically build and publish the latest greatest Mailman 2.x source that Mark releases. That's right, it's all

Re: [Mailman-Users] Microsoft blocking our Mailman lists

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On Mon, 2018-10-08 at 11:01 -0500, Lindsay Haisley wrote: > > I've generally had good luck with Linode. Their tech folks are real > geniuses and technically their service really rock. Next time you're on one of their nodes do this: egrep

Re: [Mailman-Users] help setting up mailman

On Tue, 2018-09-18 at 08:47 -0400, Matthew Draft wrote: > Hi, > I'm new to mailman and could use some advise as far as setting up a > new listserv.  Do I need to rent server space to hold the list data? Hi, If you don't want to rent a server and install and maintain mailman, you can find a list

Re: [Mailman-Users] Unexpected password reminder from this list

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On Mon, 2018-08-06 at 19:00 -0700, Mark Sapiro wrote: > On 08/06/2018 11:08 AM, Jim Popovitch via Mailman-Users wrote: > > > > What's your thoughts on adding reCAPTCHA to the 2nd half of the > > listinfo page in o

Re: [Mailman-Users] Unexpected password reminder from this list

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On Mon, 2018-08-06 at 16:20 -0400, Ruben Safir wrote: > On 08/06/2018 02:08 PM, Jim Popovitch via Mailman-Users wrote: > > > > What's your thoughts on adding reCAPTCHA to the 2nd half of the > > listinfo page in o

Re: [Mailman-Users] Unexpected password reminder from this list

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On Mon, 2018-08-06 at 05:33 -0700, Mark Sapiro wrote: > On August 6, 2018 3:14:05 AM PDT, Jayson Smith .com> wrote: > > Hi again, > > > > This was not a monthly password reminder. It specifically said > > that  > > "You—or someone posing as

Re: [Mailman-Users] enabling reCAPTCHA for older lists

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On Sun, 2018-07-22 at 16:36 -0700, Mark Sapiro wrote: > On 07/22/2018 12:49 PM, Jim Popovitch via Mailman-Users wrote: > > > > What could be set for an older list that would break reCAPTCHAs? > > > A list specific listin

[Mailman-Users] enabling reCAPTCHA for older lists

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hello, I've crossed over into reCAPTCHA hell (voluntarily!) currently looking for a savior. I have followed all the instructions in Defaults.py, and I have created the google account and setup the site-key and secret-key in mm_cfg.py, and

Re: [Mailman-Users] non-subscribers getting through--email address in "Real Name"

On July 19, 2018 6:53:52 PM UTC, Jim Popovitch wrote: >On July 19, 2018 5:28:24 PM UTC, Mark Sapiro wrote: >>On 07/19/2018 08:02 AM, Grant Taylor via Mailman-Users wrote: >>> >>> I have often wondered about enhancing Mailman, or augmenting it with >>a >&g

Re: [Mailman-Users] non-subscribers getting through--email address in "Real Name"

On July 19, 2018 5:28:24 PM UTC, Mark Sapiro wrote: >On 07/19/2018 08:02 AM, Grant Taylor via Mailman-Users wrote: >> >> I have often wondered about enhancing Mailman, or augmenting it with >a >> milter, to be able to test the SMTP envelope from, to, and body >content >> against list parameters

Re: [Mailman-Users] pending subscription to list "mailman"

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

[Mailman-Users] pending subscription to list "mailman"

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hello, For some unknown reason a legitimate human sent a subscribe request to mailman-subscr...@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

Re: [Mailman-Users] Bogus Subscriptions (was: Mailman-Users Digest, Vol 172, Issue 6)

On June 5, 2018 1:22:54 AM UTC, Mark Sapiro 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 >

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

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 <

Re: [Mailman-Users] Any scripting available for global site admin

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 On Mon, 2018-06-04 at 18:47 +, 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.   

Re: [Mailman-Users] Fail2ban on the Mailman web interface

On June 3, 2018 5:44:17 PM UTC, Henrique Fagundes 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

Re: [Mailman-Users] Fail2ban on the Mailman web interface

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

Re: [Mailman-Users] Spam Subscriptions

-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

Re: [Mailman-Users] Probable bug in Bouncers/DSN.py

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Argh! This was intended for just Mark, not the whole list. Sigh. - -Jim P. On Thu, 2018-05-24 at 11:40 -0400, Jim Popovitch via Mailman-Users wrote: > Hello! > > Given a bounce msg with a subpart of: > > >   messa

[Mailman-Users] Probable bug in Bouncers/DSN.py

-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Hello! Given a bounce msg with a subpart of: message/delivery-status: Final-Recipient: rfc822;u...@domain.tld Action: failed Status: 5.1.10 Diagnostic-Code: smtp;550 5.1.10 RESOLVER.ADR.RecipientNotFound; and the code

Re: [Mailman-Users] "Bounce action notification" emails for subscribes/unsubscribes

On Oct 24, 2017 04:20, "Stephen J. Turnbull" wrote: (Making it a list is a natural choice, and I don't see how that causes additional difficulties for cPanel.) I'm jumping in late here.. Is the problem possibly DMARC alignment failures? If so, I've been

Re: [Mailman-Users] Authenticated Received Chain in Mailman?

On Tue, Jun 6, 2017 at 3:11 PM, Joseph Brennan wrote: > On Tue, May 30, 2017 at 10:34 PM, Brett Delmage > wrote: >> Will Mailman 2 or 3 be incorporating Authenticated Received Chain (ARC) >> http://arc-spec.org/ ? > > > Wonderful, another

Re: [Mailman-Users] Emergency Moderation Problem

On Wed, May 24, 2017 at 7:30 PM, Mark Sapiro wrote: > On 5/18/17 7:53 AM, dwardell at mifnet.com wrote: >> >> Recently I enabled "Emergency Moderation" briefly, but when I disabled >> it the system doesn't return to the normal state--all traffic is still >> moderated even though

Re: [Mailman-Users] Mailman + nginx + uwsgi

On May 8, 2017 23:10, "j...@ohlste.in" wrote: Hello, Has anyone managed to get the above combination working on FreeBSD? I'm using fcgiwrap, but it isn't the most elegant solution for a variety of reasons. Hi Jim, I run mailman+nginx+uwsgi on Linux, but without fcgiwrap.

Re: [Mailman-Users] Fwd: Re: Mailing list membership.

On Wed, Mar 1, 2017 at 2:44 PM, willi uebelherr wrote: > What you think about? IETF is running Mailman v2.1.17, I think you need to upgrade and take advantage of the DMARC processing in newer versions of Mailman. -Jim P.

Re: [Mailman-Users] Spam to "-request" address generating backscatter spam

On Thu, Dec 22, 2016 at 6:55 PM, Mark Sapiro <m...@msapiro.net> wrote: > On 12/22/2016 03:38 PM, Jim Popovitch wrote: >> >> I'm seeing GET attempts like this: >> >> 77.247.181.165 - - [22/Dec/2016:23:30:10 +] "GET >>

Re: [Mailman-Users] Spam to "-request" address generating backscatter spam

On Thu, Dec 22, 2016 at 6:26 PM, Mark Sapiro <m...@msapiro.net> wrote: > On 12/22/2016 03:01 PM, Jim Popovitch wrote: >> >> I think i have a better solution, (but I'm not so sure how to do this >> in Apache). In Nginx you can use "limit_except PUT { deny al

Re: [Mailman-Users] Installing http://packages.ubuntu.com/zesty/mailman, stuck at "Temporary failure"

On Thu, Dec 22, 2016 at 6:07 PM, Caesar Samsi wrote: > Alright I'm stuck here now, been trolling google … haven’t found a clue yet. > > Dec 22 15:02:22 localhost postfix/smtpd[7643]: NOQUEUE: reject: RCPT from >

Re: [Mailman-Users] Spam to "-request" address generating backscatter spam

On Thu, Dec 22, 2016 at 4:53 PM, Jim Popovitch <jim...@gmail.com> wrote: > On Tue, Dec 13, 2016 at 12:35 PM, Mark Sapiro <m...@msapiro.net> wrote: >> >> Steve has answered most of this. I just want to add a couple of things. >> With respect to web subscribes, s

Re: [Mailman-Users] Spam to "-request" address generating backscatter spam

On Tue, Dec 13, 2016 at 12:35 PM, Mark Sapiro wrote: > > Steve has answered most of this. I just want to add a couple of things. > With respect to web subscribes, several sites including python.org have > seen mail bomb attacks via the web subscribe interface. > > These are

Re: [Mailman-Users] Mailman Hosting

On Wed, Dec 21, 2016 at 11:42 PM, Mark Dale wrote: > Hi Odhiambo and Steve, > > I'm one of the co-owners of MailmanLists.net that is mentioned in this post. > > As Odhiambo said, we've recently moved one of the servers that hosted > Odhiambo's list. This involved a change

  1   2   3   4   >