[Mailman-Users] Re: Mailman-Users Digest, Vol 237, Issue 2

Dig around in their control panel. There should be cron jobs and the ability to enable ssh per "SFTP User". Lots of ads and upsells are in their panel now which hadn't been there before so be careful what you click. >Ugh.  Dream Host does not give me cron job / command line access. I'll >t

Re: [Mailman-Users] Very strange issue With Mailman + Exchange(?)

On 4/27/20 11:21 AM, Bruce Johnson wrote: > I am not sure how to figure this out. > > Lengthy explanation: > > For two users and ONLY these two users, somewhere between them and mailman > and back, the Mailman list is being expanded to put all the members of the > list on the CC line. It then g

Re: [Mailman-Users] Trouble migrating

On 4/26/20 11:04 PM, Lothar Schilling wrote: > > ps -fwwA | grep qrunner > > mailman   7439  7438  0 07:51 ?    00:00:00 /usr/bin/python > /usr/lib/mailman/bin/qrunner --runner=ArchRunner:0:1 -s > mailman   7440  7438  0 07:51 ?    00:00:00 /usr/bin/python > /usr/lib/mailman/bin/qrunner -

Re: [Mailman-Users] Trouble migrating

Am 26.04.2020 um 19:46 schrieb Mark Sapiro: On 4/26/20 9:57 AM, Lothar Schilling wrote: Yes I did check the permissons several times, everything is fine. And no, SELinux was and still is disabled. What user is running Mailman's qrunners? ps -fwwA|grep qrunner And what does ls -laR /var/spoo

Re: [Mailman-Users] Trouble migrating

On 4/26/20 9:57 AM, Lothar Schilling wrote: > Yes I did check the permissons several times, everything is fine. And > no, SELinux was and still is disabled. What user is running Mailman's qrunners? ps -fwwA|grep qrunner And what does ls -laR /var/spool/mailman /var/lib/mailman give? -- Mark

Re: [Mailman-Users] Trouble migrating

Hi Tom, this is not meant for me, is it? My name's not David. Also, my problem is of a different kind. Regards Lothar Schilling Am 26.04.2020 um 18:44 schrieb Tom Coradeschi: David: Your qrunner exceptions sound surprisingly like a problem I had earlier this week with a new install of 2.1.3

Re: [Mailman-Users] Trouble migrating

Yes I did check the permissons several times, everything is fine. And no, SELinux was and still is disabled. Am 26.04.2020 um 18:37 schrieb Mark Sapiro: On 4/26/20 9:05 AM, Lothar Schilling wrote: Hi everybody, today I tried to migrate our whole mailman installation to another server. Old se

Re: [Mailman-Users] Trouble migrating

David: Your qrunner exceptions sound surprisingly like a problem I had earlier this week with a new install of 2.1.30. In Mailman/Archiver/pipermail.py change line 60 from: while i>0 and (L[i-1][0] in lowercase or to: while i>0 and (L[i-1][0] in lowercase[:26] or Restart mailman and see how th

Re: [Mailman-Users] Trouble migrating

On 4/26/20 9:05 AM, Lothar Schilling wrote: > Hi everybody, > > today I tried to migrate our whole mailman installation to another server. > > Old server: Centos 6.10, Mailman 2.1.29, Python 2.6.6 > > New server: Centos 7.7, Mailman 2.1.30 (from the tgz file), Python 2.7.5 > > It seemed to be a

Re: [Mailman-Users] dkim for several mailman lists on one server

On 4/24/20 2:36 PM, csa--- via Mailman-Users wrote: > Ubuntu 16, Mailman 2.1.20, postfix 3.1.0 > > I'm running several mailing lists each with a virtual domain. I set up DKIM > for lists.domainname.tld but am getting DKIM signature missing at > https://dkimvalidator.com . It's saying it wants a DK

Re: [Mailman-Users] Toggle plain text setting for new users

Am Mittwoch, 22. April 2020, 17:59:53 CEST schrieb Mark Sapiro: > On 4/22/20 7:36 AM, Johannes Rohr wrote: > > What I am asking about is the per-user setting: > > > > When you go to /members you will see that in the members table, the > > second column from the right is called "plain" and if the

Re: [Mailman-Users] Toggle plain text setting for new users

On 4/22/20 7:36 AM, Johannes Rohr wrote: > > What I am asking about is the per-user setting: > > When you go to /members you will see that in the members table, the second > column > from the right is called "plain" and if the box is ticket, messages are > delivered as plain text. > And the

Re: [Mailman-Users] Toggle plain text setting for new users

Am Mittwoch, 22. April 2020, 16:09:49 CEST schrieb Mailman-admin: > Hello > > Per default mailman is distributing whatever it gets. > Check your settings in admin page topic "Content filtering". Thanks, but I am not asking about global filtering rules (which are disabled anyway (The preset is t

Re: [Mailman-Users] Toggle plain text setting for new users

Hello Per default mailman is distributing whatever it gets. Check your settings in admin page topic "Content filtering". Kind regards, Christian Mack Am 22.04.20 um 15:11 schrieb Johannes Rohr: Dear all, I would like to toggle a default setting for new users, name the HTML/plain text switch.

Re: [Mailman-Users] Who gets notices - was: Topic Filtering

On 4/7/20 8:20 AM, Batchelor, Oliver wrote: > > Do list administrators get moderator messages too? The administrator of one > of my department lists is an administrator, but keeps getting prompts to > approve things. Any info on this? Yes. owners get moderator messages too. See

Re: [Mailman-Users] Topic Filtering

_ From: Mailman-Users on behalf of John Marsden Sent: Sunday, April 5, 2020 7:02 AM To: mailman-users@python.org Subject: Re: [Mailman-Users] Topic Filtering Hello Mark Thanks for this further clarification. I can live with the anomaly (have to!) but it is good to know the position. Regards

Re: [Mailman-Users] Topic Filtering

Hello Mark Thanks for this further clarification. I can live with the anomaly (have to!) but it is good to know the position. Regards John John Marsden Webmaster: www.lancashirebmd.org.uk www.cumbriabmd.org.uk www.1851-unfilmed.org.uk www.mlfhs.org.uk On 03/04/2020 16:02, Mark Sapiro wrote:

Re: [Mailman-Users] Topic Filtering

On 4/3/20 2:24 AM, John Marsden wrote: > Hello Mark > > Thanks for this confirmation. I suspected it would be the case, but it > is good to have it confirmed. Maybe one for the developers to think > about... > > Do you, or does anyone else, know whether Mailman 3 behaves in the same > way? Yes,

Re: [Mailman-Users] Topic Filtering

Hello Mark Thanks for this confirmation. I suspected it would be the case, but it is good to have it confirmed. Maybe one for the developers to think about... Do you, or does anyone else, know whether Mailman 3 behaves in the same way? Regards John John Marsden Webmaster: www.lancashirebmd.

Re: [Mailman-Users] Topic Filtering

On 4/1/20 8:00 AM, John Marsden wrote: > > This works perfectly for those members who subscribe to receive > individual messages, but those who subscribe to Digests still receive > ALL messages in their digests, despite having selected the topic. > > As far as I can see, this is a 'feature' of Ma

Re: [Mailman-Users] New installation sudo /etc/init.d/mailman start

Christian Mack Thanks for your reply. Blooming obvious now you have pointed it out. I had to do one or two more things to get the web interface to work eg implement cgi but now at least that part is working. Thanks again. CHRIS -- Sent from: http://mailman.9.n7.nabble.com/Mailman-Users-f3.h

Re: [Mailman-Users] Find a smtp server to send out emails

You could definitely try other SMTP services like Sendinblue, Pepipost, etc. I have found more at - https://digitalmarketingtipsy.com/email-marketing/best-smtp-services/ and also at https://digitalmarketingtipsy.com/email-marketing/best-smtp-servers/ These posts feature some good SMTP servers th

Re: [Mailman-Users] New installation sudo /etc/init.d/mailman start

Hello Am 18.03.20 um 13:06 schrieb scoutdubna: I have made a new installation of mailman using https://www.howtoforge.com/how-to-install-and-configure-mailman-with-postfix-on-debian-squeeze This is on an Ubuntu 18.04 server hosted by IONOS I get all the way through but when I input th

Re: [Mailman-Users] mailman queues

On 3/16/20 1:20 PM, k...@keldix.com wrote: > I have a problem with removing failing subscription requests > eg from a bogus requester. I thought I could remove the request > from a queue somewhere but cannot find it. > the subscription requests keep recurring, over 1000 in my maillog -postfix The

Re: [Mailman-Users] rejecting messages with any HTML

On March 12, 2020 1:11:28 AM GMT+00:00, "Jason A. Donenfeld" wrote: >Hi, > >I run several mailing lists over at lists.zx2c4.com using mailman >2.1.30rc1. I would like to reject incoming messages that have any HTML >parts in them at all. Or, perhaps, I'd like to whitelist a few >different mimetype

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

On 3/3/20 6:47 AM, Jim Popovitch via Mailman-Users wrote: > > Can you share with me (us) the number and size, along with the industry > or operations arena, of those people who are creating their own web UI. I have no information about that. > I honestly don't believe that there is that much i

Re: [Mailman-Users] multiple explicit reply addresses?

My work-around would then be: Set up an address on my server, say specialr...@mydomain.dom, which acts as a forwarder to the two addresses e...@x.com and e...@y.com Christian Mark Sapiro schrieb am 03.03.20 um 17:26: On 3/3/20 2:25 AM, Bernie Cosell wrote: I don't want to break my lists, s

Re: [Mailman-Users] multiple explicit reply addresses?

On 3/3/20 2:25 AM, Bernie Cosell wrote: > I don't want to break my lists, so I'll ask first..:o)Does mailman do the > right > thing if I want explicit replies to go to two addresses? It seems very > explicit that > the explicit reply address is singular.. would making it e...@x.com, > e.

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 api provide to church group

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

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 api provide to church groups, and tech lists like nanog or mailop? It provides a st

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

On 3/2/20 4:55 PM, Jim Popovitch via Mailman-Users wrote: While I applaud Brian's efforts, I'm not convinced that I would run PHP on a public facing portal, even in 2020. But that's just me, others may feel differently. And so it begins. -- Please let me know if you need further assistance.

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 posted in Jan of this > > year). >

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

On Sat, 29 Feb 2020 10:53:19 -0500 Jim Popovitch via Mailman-Users wrote: > but I have vague recollections that both Barry and Mark have > > said repeatedly that doing so would be substantially anything built on the > > MM2 > > architecture. assuming that's so I think the "anything built on

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

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 posted in Jan of this > year). The question is what do people want when they say they want Mailman

Re: [Mailman-Users] MM3 filter content

On 3/2/20 12:35 AM, Eduardo Costa via Mailman-Users wrote: > Hello, > > How do I manage to activate and define the content filters in order to > remove attachments at MM3? The list for questions about Mailman 3 is mailman-us...@mailman3.org

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 would have preferred yo

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

Jim Popovitch via Mailman-Users writes: > Interestingly enough, here's a roadmap on exactly how to do it: :) Jim, you're not helping. Until there are "I'll do it" hands up, no port to Python 3 that is faithful to current Mailman 2 is viable. Pushing it just serves to annoy those who are curren

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

Mark Sapiro writes: > I'd say it depend on the details of how serious the vulnerability is, > how easy it is to exploit and how hard it is to fix. I am not opposed to > Mailman 2.1.30-x security fix releases. Mark speaks for me, although it's been a long time since I've worked on Mailman 2, an

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 how serious the vulnerability is, > how

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

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 how serious the vulnerability is, how easy it is to exploit and how hard it is to fix. I am not oppos

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

On 2/28/20 11:28 PM, 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. None whatsoever, at least not from me ;) -- Mark Sapiro

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 > > a > > lot of support for tha

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 mailman

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

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 mailman-users@python.org is not going away. Furthermore, I expect that Mark and I, a

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

Phil Stracchino writes: > On 2020-02-28 05:44, Stephen J. Turnbull wrote: > > str in Python 1, and the history of Mailman as an MLM for an American > > rock band (who needs no steekin' accents, we just hammer and bend the > > strings!) > > This is clearly a story I didn't know. :) And now

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

Brian Carpenter writes: > On 2/28/20 1:55 PM, Mark Sapiro wrote: > > Quite a few core settings are not exposed in Postorius but we're > > chipping away at that. > > Is there a list somewhere to see what core settings have not been > exposed in Postorius yet? Implicit in the Postorius UI an

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

@mailman-users I'm going to get into a lot of design here, so I'm moving the thread to mailman-develop...@python.org. Reply-To set; please respect. Brian kept in Reply-To as a courtesy, don't know if he's subscribed over there. @mailman-developers Brian is planning to develop an alternative web

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

On 2/28/20 1:55 PM, Mark Sapiro wrote: Quite a few core settings are not exposed in Postorius but we're chipping away at that. Is there a list somewhere to see what core settings have not been exposed in Postorius yet? -- Please let me know if you need further assistance. Thank you for your

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

On 2/28/20 10:24 AM, Jim Popovitch via Mailman-Users wrote: > > I think that is Brian's and a lot of other people's concern. 3 years to > implement something into MM3 that was a core feature in MM2. I realize > this next question is going to sound bombastic, I assure you it's not > meant that wa

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 professional PHP developer to begin work on a new > > >

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

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 professional PHP developer to begin work on a new >> > admin/forum interface for Mailman 3. >> >> Too bad. I really sympat

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

On 2/28/20 5:52 AM, Stephen J. Turnbull wrote: Too bad. I really sympathize with your goals but am unlikely to be able to contribute directly to implementation (assuming an eventual open-sourcing). Never learned PHP, not going to do it anytime soon. That's OK, the point of REST is so*you* *can

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

On 2020-02-28 05:44, Stephen J. Turnbull wrote: > Mailman has the opposite problem. We *wish* str was Unicode from the > get-go, but it wasn't, and Mailman 2 is rife with potential encoded/ > decoded confusion because of the nature of email and the dual usage of > str in Python 1, and the history

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 d

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

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 directly to implementation (assuming an eventual open-sourcing). Never learn

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

Phil Stracchino writes: > Rewriting without breaking is hard. True. > There is a Python framework called Twisted. Not an example appropriate to Mailman, though. The Twisted people were doing amazing things with str, to which Unicode was irrelevant, because their job was to shovel bytes from

Re: [Mailman-Users] Setting MM 3 attributes

On 2/27/20 10:18 PM, Mark Sapiro wrote: >>> Setting Maximum message size works in current Postorius. What version do >>> you have? >> >> I'm running 1.1.2; it's from the Ubuntu repo. > > Actually, the issue is Mailman core, not Postorius. max_message_size was > not exposed in REST before version

Re: [Mailman-Users] Setting MM 3 attributes

On 2/27/20 6:21 PM, Dave McGuire wrote: > >> Setting Maximum message size works in current Postorius. What version do >> you have? > > I'm running 1.1.2; it's from the Ubuntu repo. Actually, the issue is Mailman core, not Postorius. max_message_size was not exposed in REST before version 3.2.0

Re: [Mailman-Users] Setting MM 3 attributes

On 2/27/20 9:08 PM, Mark Sapiro wrote: > On 2/27/20 5:44 PM, Dave McGuire wrote: >> >> Not to hijack, but is it possible to set the maximum message size by >> the mailman shell? I've a problem with that in one of my MM3 lists, I >> really need to set that, but the web interface does not allow me

Re: [Mailman-Users] Setting MM 3 attributes

On 2/27/20 5:44 PM, Dave McGuire wrote: > > Not to hijack, but is it possible to set the maximum message size by > the mailman shell? I've a problem with that in one of my MM3 lists, I > really need to set that, but the web interface does not allow me to set > it. I get the dreaded "Unknown at

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

On 2/27/20 8:01 PM, Mark Sapiro wrote: >> Bounce processing will still not be available for new users of Mailman >> which is my big concern. I assume new lists will have to have those >> settings adjusted via the Mailman shell? > > Sure it will. All the settings have reasonable defaults just like

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

On 2/27/20 5:01 PM, Mark Sapiro wrote: > > True, until they are exposed in some list admin UI they will need to be > set via mailman shell or the REST API, ... That is IF they need to be changed from the default. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, Califo

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

On 2/27/20 3:09 PM, Brian Carpenter wrote: > > Bounce processing will still not be available for new users of Mailman > which is my big concern. I assume new lists will have to have those > settings adjusted via the Mailman shell? Sure it will. All the settings have reasonable defaults just like

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

On 2/27/20 5:30 PM, Mark Sapiro wrote: I don't know why Mailman 3's DMARC mitigation is considered improved over Mailman 2.1. It's the same. The Settings and Postorius UI for them are more logical than MM 2.1, but they ultimately boil down to the same things. The latest Mailman core (not yet rel

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

On 2/27/20 1:37 PM, Brian Carpenter wrote: Brian makes a number of good points. I just have a couple of remarks/questions. > 5. MM3 DMARC handling seems to have improved from reviews I have seen > but NO BOUNCE PROCESSING. I don't know why Mailman 3's DMARC mitigation is considered improved ove

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

On 2/27/20 2:44 PM, Mark Sapiro wrote: I have said before that a much better use of time and resources would be the implementation of a light weight, non-Django web UI for Mailman 3, but I don't see anyone raising a hand to do either. Let me be more clearer on this. I have hired a professional

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

On 2/27/20 3:40 PM, Brian Carpenter wrote: >> If you want to port Mailman 2 to Python 3, you are welcome to do it. I >> have said before that a much better use of time and resources would be >> the implementation of a light weight, non-Django web UI for Mailman 3, >> but I don't see anyone raising

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

On 2/27/20 2:44 PM, Mark Sapiro wrote: If you want to port Mailman 2 to Python 3, you are welcome to do it. I have said before that a much better use of time and resources would be the implementation of a light weight, non-Django web UI for Mailman 3, but I don't see anyone raising a hand to do e

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

On 2/27/20 2:08 PM, Phil Stracchino wrote: ... > What has this yielded? > > "Most of the most commonly used parts" of Twisted are now Python 3 > compatible. I hear this how upgrading any django installation from one python-3 version to another python-3 version usually goes. I.e. long-term, at thi

Re: [Mailman-Users] Handling Munged From Addresses

On 2/27/20 11:54 AM, Dennis Putnam wrote: > > I didn't realize that there were OS dependencies in the DMARC > mitigation. I thought it was all within the mailman code. It's not an OS dependency. It's a downstream package dependency. If I look at

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

On 2020-02-27 14:51, 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 >> a >> lot of support for that. > > I'm sure t

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

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 a lot of support for that. I'm sure there would be widespread applause and congratulations

Re: [Mailman-Users] Handling Munged From Addresses

On 2/27/2020 1:38 PM, Mark Sapiro wrote: > On 2/27/20 10:17 AM, Dennis Putnam wrote: >> Thanks for the reply. I am not seeing that. The From: looks like this: >> >> From: Rushtalk Discussion List via Rushtalk > > That must be a RedHat thing having to do with their backport of DMARC > mitigations.

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

On 2/27/20 11:24 AM, Jim Popovitch via Mailman-Users wrote: > > Who decides that there will be no more releases of MM2 from the GNU > Mailman project? I do. I am the release manager and the only one making releases so I get to decide. > I've got to be honest, Mailman 3 still looks unstable t

Re: [Mailman-Users] Handling Munged From Addresses

On 2/27/20 10:27 AM, Dennis Putnam wrote: > > From: Jane Doe (jane.doe at domain.tld) via Listname > On 2/27/20 10:27 AM, Jim Popovitch via Mailman-Users wrote: > > Sorry, I meant this: > > From: Jane Doe (jane.doe#domain.tld) via Listname Both of those still have the domain which is also con

Re: [Mailman-Users] Handling Munged From Addresses

On 2/27/20 10:17 AM, Dennis Putnam wrote: > > Thanks for the reply. I am not seeing that. The From: looks like this: > > From: Rushtalk Discussion List via Rushtalk That must be a RedHat thing having to do with their backport of DMARC mitigations. If you don't like it, install from source. >

Re: [Mailman-Users] Handling Munged From Addresses

On 2/27/2020 1:23 PM, 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 specifically do not do that because it is said that mult

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 specifically do not do that because i

Re: [Mailman-Users] Handling Munged From Addresses

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 specifically do not do that because it is said that multiple email addresses in From: trigger spam fi

Re: [Mailman-Users] Handling Munged From Addresses

On 2/27/2020 12:58 PM, 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 folks doing to hand

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 folk

Re: [Mailman-Users] Possible Backup Issue

On 2/27/2020 12:47 PM, Mark Sapiro wrote: > On 2/27/20 6:27 AM, Dennis Putnam wrote: >> It has not happened in 2 days however, there are no files in any of >> those directories. Does that not imply the backups are not working? Is >> that handled by a cronjob? > > This has nothing to do with backups

Re: [Mailman-Users] Handling Munged From Addresses

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 folks doing to handle that? > Other than having list members add t

Re: [Mailman-Users] Possible Backup Issue

On 2/27/20 6:27 AM, Dennis Putnam wrote: > > It has not happened in 2 days however, there are no files in any of > those directories. Does that not imply the backups are not working? Is > that handled by a cronjob? This has nothing to do with backups per se. The error messages are somewhat diffe

Re: [Mailman-Users] Possible Backup Issue

On 2/26/2020 9:14 PM, Mark Sapiro wrote: > On 2/26/20 8:18 AM, Dennis Putnam wrote: >> mailman   5129  5125  0 Feb24 ?    00:00:16 /usr/bin/python >> /usr/lib/mailman/bin/qrunner --runner=BounceRunner:0:1 -s >> >> I think that means there is only 1 process. > > Yes, but maybe that wasn't the ca

Re: [Mailman-Users] Possible Backup Issue

On 2/26/20 8:18 AM, Dennis Putnam wrote: > > mailman   5129  5125  0 Feb24 ?    00:00:16 /usr/bin/python > /usr/lib/mailman/bin/qrunner --runner=BounceRunner:0:1 -s > > I think that means there is only 1 process. Yes, but maybe that wasn't the case at the time of those messages. Are the err

Re: [Mailman-Users] Possible Backup Issue

On 2/26/2020 11:09 AM, Mark Sapiro wrote: > On 2/26/20 6:56 AM, Dennis Putnam wrote: >> I'm not sure why I am getting these errors but it seems to be associated >> with backups. Is there a backup cronjob that didn't run, fail or is >> something else wrong? The directories do exist but not the indic

Re: [Mailman-Users] Possible Backup Issue

On 2/26/20 6:56 AM, Dennis Putnam wrote: > I'm not sure why I am getting these errors but it seems to be associated > with backups. Is there a backup cronjob that didn't run, fail or is > something else wrong? The directories do exist but not the indicated pck > files. TIA I haven't looked at thi

Re: [Mailman-Users] Archives Permission Denied

On 2/25/2020 5:11 PM, Mark Sapiro wrote: > On 2/25/20 10:25 AM, Dennis Putnam wrote: > >> So shouldn't 'check_perms -f' have fixed that? > > check_perms is not perfect. See below for more. > > >> This is a server used strictly for mailman. There are only 2 users with >> access so I am not worried a

Re: [Mailman-Users] Archives Permission Denied

On 2/25/20 10:25 AM, Dennis Putnam wrote: > So shouldn't 'check_perms -f' have fixed that? check_perms is not perfect. See below for more. > This is a server used strictly for mailman. There are only 2 users with > access so I am not worried about the caveat in that article. It looks > like yo

Re: [Mailman-Users] Archives Permission Denied

On 2/25/2020 12:12 PM, Mark Sapiro wrote: > On 2/25/20 6:34 AM, Brian Carpenter wrote: >> On 2/25/20 5:49 AM, Dennis Putnam wrote: >>> IOError: [Errno 13] Permission denied: >>> '/var/lib/mailman/archives/private/rushtalk/2020-February.txt' >>> >>>   I ran check_perms and it found no issues. Howeve

Re: [Mailman-Users] Membership List Include Legend Link Wrong

On 2/25/2020 9:37 AM, Brian Carpenter wrote: > On 2/25/20 5:36 AM, Dennis Putnam wrote: >> The link to include legend on the membership management page is: >> >> http://localhost.localdomain/mailman/admin/rushtalk/members/list?legend=yes >> >> >> Why is that not defaulting to the real host and how

Re: [Mailman-Users] Archives Permission Denied

On 2/25/20 6:34 AM, Brian Carpenter wrote: > On 2/25/20 5:49 AM, Dennis Putnam wrote: >> IOError: [Errno 13] Permission denied: >> '/var/lib/mailman/archives/private/rushtalk/2020-February.txt' >> >>   I ran check_perms and it found no issues. However, when I look at the >> ownership of the archive

Re: [Mailman-Users] Membership List Include Legend Link Wrong

On 2/25/20 5:36 AM, Dennis Putnam wrote: The link to include legend on the membership management page is: http://localhost.localdomain/mailman/admin/rushtalk/members/list?legend=yes Why is that not defaulting to the real host and how do I fix it? TIA. Have you tried running: /mailman_install

Re: [Mailman-Users] Archives Permission Denied

On 2/25/20 5:49 AM, Dennis Putnam wrote: IOError: [Errno 13] Permission denied: '/var/lib/mailman/archives/private/rushtalk/2020-February.txt'  I ran check_perms and it found no issues. However, when I look at the ownership of the archives I get this: -rw-r--r--.    1 root mailman   72404 Feb

Re: [Mailman-Users] I18n for Mailman 2.1.30

On 2/17/20 3:44 PM, Mark Sapiro wrote: > Over a month ago, I posted the following announcement particularly > asking for i18n updates prior to the final release of Mailman 2.1. > > To date I have only received updates for the Japanese translation. I have now received an updated German translatio

Re: [Mailman-Users] Mailman 2.1.30rc1 released

Over a month ago, I posted the following announcement particularly asking for i18n updates prior to the final release of Mailman 2.1. To date I have only received updates for the Japanese translation. If you can help update any of the other translations, please submit changes as indicated below.

Re: [Mailman-Users] mailman 2.1.18 for RHEL 5

On 2/17/20 2:27 AM, Dennis Putnam wrote: > It turns out that the only version available for RHEL 7 is 2.1.12. > However, the mailman documentation indicates that also has DMARC > mitigation. What documentation? I assume Red Hat's. In any case, what you will have, as others have said, is 2.1.12 w

Re: [Mailman-Users] mailman 2.1.18 for RHEL 5

On 2/17/2020 11:24 AM, Lindsay Haisley (linode) wrote: This is common practice for all major distributions. The only way to keep up with upstream versions is to install from same from the git-go. This has its own pitfalls, but I do this for Mailman and have never had a problem. I'm still

Re: [Mailman-Users] mailman 2.1.18 for RHEL 5

On Feb 17, 2020, at 10:45 AM, Phil Stracchino wrote: > >> On 2020-02-17 10:56, Bill Cole wrote: >> RedHat has a policy of nailing down nominal versions of software with >> each major RHEL release and then backporting whatever fixes they deem >> important into their packages over the life of t

  1   2   3   4   5   6   7   8   9   10   >