Re: [Mailman-Users] Changing non-member message

On 4/22/19 6:22 PM, Bernie Cosell wrote: > Is it possible [at least without hacking the python code] to change the > default > reject message that gets sent when a not-allowed member posts to a list. Go to the list admin Privacy options... -> Sender filters If the non-member posts are rejected

Re: [Mailman-Users] Mapping -owners alias to a separate list

On Fri, 19 Apr 2019 06:53:38 -0700 Mark Sapiro wrote: > > And pretty easy - the list will accept mail from nonsubs, it just > > sticks any such messages in the mod queue. =) > > > And if that's not what you want, set Privacy options... -> Sender > filters -> generic_nonmember_action to Accept r

Re: [Mailman-Users] [SPAM?] Mapping -owners alias to a separate list

On Thu, 18 Apr 2019 20:00:23 -0400 Richard Damon wrote: > That just means that you need to setup the -admins list to accept > mail from non-subscribers, which is a perfectly valid configuration. And pretty easy - the list will accept mail from nonsubs, it just sticks any such messages in the mod

Re: [Mailman-Users] Restrict archives to Administrator

Mark Dale writes: > We had a customer ask for their lists to have this option. Their > lists are used with some kind of automated entry/exit logging > processes. Jim Popovitch via Mailman-Users writes: > Ack. It's a narrow need, but there are reasons. Not every list is for raw > public con

Re: [Mailman-Users] [SPAM?] Mapping -owners alias to a separate list

> On Apr 18, 2019, at 6:41 PM, Dennis Carr > wrote: > > Hey, guys. > ... > So to this end, my thought is to route that mail over to a separate > -admins list instead of 'mailman list admins'. The expected side > effect is that this will wind up in the -admins list "not-subscribed" > trap. I

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 d

Re: [Mailman-Users] Restrict archives to Administrator

On Thu, 2019-04-18 at 20:31 +1000, Mark Dale 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. > > From: Stephen J. Turnbull [mailto:turnbull.stephen...@u.tsukuba.ac.jp] > > > Again, I'm not

Re: [Mailman-Users] Restrict archives to Administrator

> 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. From: Stephen J. Turnbull [mailto:turnbull.stephen...@u.tsukuba.ac.jp] > Again, I'm not saying these are bad ideas, just that I want more > information

Re: [Mailman-Users] creating an announce only list?

On 4/14/19 12:03 AM, Adam Morris wrote: > Hi all, > > Can someone remind me what I need to do to make an email list announce > only opposed to a normal list where people can post and reply to messages. See . -- Mark Sapiro The highway is for gamblers, S

Re: [Mailman-Users] creating an announce only list?

On Sun, 14 Apr 2019 at 15:33, Adam Morris wrote: > Hi all, > > Can someone remind me what I need to do to make an email list announce > only opposed to a normal list where people can post and reply to messages. > > TIA. In summary, 1. De

Re: [Mailman-Users] Now that Python 2 is dead

On Sat, 13 Apr 2019 21:05:39 +1000 Steven D'Aprano wrote: > If you're running MM2 under Python 2.7, and you also have Python 3.7 > installed, the two Python interpreters don't share packages unless > you're doing something unusual. So updating one version of the > installed package shouldn't to

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

On 4/10/19 7:36 PM, Dave McGuire wrote: > On 4/10/19 12:25 PM, 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. > > On that note, I migrated my half-dozen lists (a few hundred re

Re: [Mailman-Users] Now that Python 2 is dead

On Thu, Apr 11, 2019 at 03:25:50PM -0500, Dimitri Maziuk via Mailman-Users wrote: > The problem is reliance on third-party libraries coupled with absence of > usable package management system. It will "generally" run within the > same major interpreter version unless it imports a package that got

Re: [Mailman-Users] Now that Python 2 is dead

Matthew Goebel writes: > Won't redhat just apply/support fixes provided the software vendor? For RHEL, no, they'll do a lot more than that if it's covered by the support contract. That's the business model: if they were just providing the integration testing, Centos would eat their lunch. > I

Re: [Mailman-Users] Now that Python 2 is dead

On 4/12/19 10:21 AM, Matthew Goebel wrote: > Won't redhat just apply/support fixes provided the software vendor? If > something comes up with python > how likely are they to build their own fix? https://access.redhat.com/security/updates/backporting/ -- Dimitri Maziuk Programmer/sysadmin BioMa

Re: [Mailman-Users] Now that Python 2 is dead

Won't redhat just apply/support fixes provided the software vendor? If something comes up with python how likely are they to build their own fix? Matt On Fri, Apr 12, 2019 at 11:17 AM Dmitri Maziuk via Mailman-Users < mailman-users@python.org> wrote: > On Fri, 12 Apr 2019 15:58:36 +0900 > "Ste

Re: [Mailman-Users] Now that Python 2 is dead

On Fri, 12 Apr 2019 15:58:36 +0900 "Stephen J. Turnbull" wrote: > PS Just saw this: > > https://mobile.twitter.com/zooba/status/1116364827146854401 Whoever came up with that should upgrade to centos/SL/orrible 6: RedHat will maintain and fix RHEL6 with its python 2.6 and apache 2.2 until 2034,

Re: [Mailman-Users] Now that Python 2 is dead

Mike Flannigan writes: > I'm surprised to hear there is so much migration in Python with > limited backward compatibility. Perl has never had that problem. Of course it has. I had Perl 4 on my Debian box for a decade after Perl 5 was released, because various apps had scripts or something that

Re: [Mailman-Users] Now that Python 2 is dead

PS not that I disagree that the practical way out right now is to make a simple e.g. flask-based UI for MM3. -- Dimitri Maziuk Programmer/sysadmin BioMagResBank, UW-Madison -- http://www.bmrb.wisc.edu signature.asc Description: OpenPGP digital signature --

Re: [Mailman-Users] Now that Python 2 is dead

On 4/11/19 12:15 PM, Mark Sapiro wrote: > Generally older Python 3 code will run on newer versions. The issues are > trying to run code developed for newer Python 3 versions on older versions. The problem is reliance on third-party libraries coupled with absence of usable package management syste

Re: [Mailman-Users] Now that Python 2 is dead

On 4/11/19 10:05 AM, Mike Flannigan wrote: > > I'm surprised to hear there is so much migration in > Python with limited backward compatibility.?? Perl > has never had that problem.?? I almost never have to > modify my old code.?? I'd recommend you use Perl, but > everybody knows Perl is dead :-)

Re: [Mailman-Users] Now that Python 2 is dead

I'm surprised to hear there is so much migration in Python with limited backward compatibility.?? Perl has never had that problem.?? I almost never have to modify my old code.?? I'd recommend you use Perl, but everybody knows Perl is dead :-) Mike On 4/10/2019 6:03 PM, mailman-users-requ...@

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

On 4/11/2019 3:22 AM, Stephen J. Turnbull wrote: ... If you want something that's never going to change, Python 2.7 is as good as anything else. Some orgs have "cybersecurity" with "vulnerability scanners". You may have to spend more time hiding your python version from them, then you'll sp

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

Carl Zwanzig writes: > On 4/10/2019 11:36 AM, Dimitri Maziuk via Mailman-Users wrote: > > (That said, given the history of python, my question would be if there > > are any plans to port MM2 to golang or maybe gnat.) Not within the Mailman project. It seems pointless to me. If you want some

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

On 4/10/19 12:25 PM, 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. On that note, I migrated my half-dozen lists (a few hundred recipients in total) to MM3 yesterday. I'm having

Re: [Mailman-Users] Malformed URLs for some admin web page links

On 4/10/19 12:10 PM, Jeff Hunter wrote: > I have a mailman list that is working correctly, except for some of the links > on the base admin web page and it's child pages. The list is at > listserv.mydomain.com and all of the links on the list admin page start with > that base url, except the lin

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

On 4/10/19 2:53 PM, Jim Popovitch via Mailman-Users wrote: > > What Mailman things need assistance in MM3? I've avoided jumping in because > honestly every time I looked it seemed like all the focus was everything but > the email reflector bits. There are (at the moment) 509 open issues at

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

On 4/10/19 12:08 PM, Carl Zwanzig wrote: > > Maybe there's a place for a community-driven port of MM2 onto python3. I > am not volunteering, too many other projects currently. I think a much more productive use of the community's resources would be implementation of a light weight, non-Django we

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

On 4/10/19 12:08 PM, Carl Zwanzig wrote: > > The main thing is that from appearances MM3 is large enterprise-grade > list manager, but many of us don't need that, we need something for a > few (<100?) lists with a few (<500?) members. I can run that on a small > BSD box; spinning up django, sass,

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 tim

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

On 4/10/19 2:08 PM, Carl Zwanzig wrote: > Or rust, or python3 (which might be the easiest). I'm not sufficiently > up on the python differences, but. it can't be -that- difficult. > (and aren't there tools to assist? some code claims to be both v2 and v3 > compatible) (gnat? that's really

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

I'm more worried another DMARC style debacle myself, more than a Python security issue, although that could be an issue. Thanks, Matt On Wed, Apr 10, 2019 at 3:29 PM Sean McBride wrote: > On Wed, 10 Apr 2019 13:36:59 -0500, Dimitri Maziuk via Mailman-Users said: > > >On 4/10/19 12:49 PM, Sean

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

On Wed, Apr 10, 2019 at 11:36:24AM -0400, Matthew Goebel wrote: > Now that all support for Python 2 is supposed to go away in 2020 are people > going to move off of mailman 2? Most of my mailman lists are run off a CentOS 6 box, have done for a long time, quite stable. CentOS 8 will (is expected

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

On Wed, 10 Apr 2019 13:36:59 -0500, Dimitri Maziuk via Mailman-Users said: >On 4/10/19 12:49 PM, Sean McBride wrote: >> On Wed, 10 Apr 2019 12:38:34 -0500, Dimitri Maziuk via Mailman-Users said: >> >>> How much support for python 2 have you been getting until now, and why >>> do you believe you w

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

On 4/10/2019 11:36 AM, Dimitri Maziuk via Mailman-Users wrote: With a properly sandboxed application your security vulnerability has to be a) exploitable through that application and b) able to break out of the sandbox and wreak havoc to your host system. Exactly. (That said, given the histor

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

On 4/10/19 12:49 PM, Sean McBride wrote: > On Wed, 10 Apr 2019 12:38:34 -0500, Dimitri Maziuk via Mailman-Users said: > >> How much support for python 2 have you been getting until now, and why >> do you believe you will need it in the future? > > Fixes to security vulnerabilities basically. If/

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

On Wed, 10 Apr 2019 12:38:34 -0500, Dimitri Maziuk via Mailman-Users said: >> Now that all support for Python 2 is supposed to go away in 2020 are >> people going to move off of mailman 2? > >How much support for python 2 have you been getting until now, and why >do you believe you will need it

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

On 4/10/19 10:36 AM, Matthew Goebel wrote: > Hey, > > Now that all support for Python 2 is supposed to go away in 2020 are > people going to move off of mailman 2? How much support for python 2 have you been getting until now, and why do you believe you will need it in the future? -- Dimitri

Re: [Mailman-Users] Systemctl unit file for MM

On 4/10/19 9:32 AM, Stephen J. Turnbull wrote: > Mark Sapiro writes: > > > You may want to add > > > > PIPFile=/home/mailman/data/master-qrunner.pid > > should that variable be PIDFile? Absolutely yes. Thanks Steve. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Are

Re: [Mailman-Users] Systemctl unit file for MM

On Apr 10, 2019, at 11:44 AM, Mark Sapiro wrote: > > You may want to add > > PIPFile=/home/mailman/data/master-qrunner.pid Ok, thanks, will do. > > However, I don't think that's relevant to your issue. I don't know why > the rm command doesn't work. How do you know it doesn't? I touched a tes

Re: [Mailman-Users] Systemctl unit file for MM

Mark Sapiro writes: > You may want to add > > PIPFile=/home/mailman/data/master-qrunner.pid should that variable be PIDFile? -- Mailman-Users mailing list Mailman-Users@python.org https://mail.python.org/mailman/listinfo/mailman-users Mailm

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

On 4/10/19 8:46 AM, Carl Zwanzig wrote: > > I'll probably continue with MM2 until either it's ported > to python3 or I stop running these lists. The GNU Mailman project will never port Mailman 2.1 to Python 3. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, Californ

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

On 4/10/19 8:36 AM, Matthew Goebel wrote: > > Now that all support for Python 2 is supposed to go away in 2020 are > people going to move > off of mailman 2? I've been looking at mailman 3 and finding it hard to > grok after using > mailman 2 for many years. I haven't seen a discussion about t

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

On 4/10/2019 8:36 AM, Matthew Goebel wrote: Now that all support for Python 2 is supposed to go away in 2020 are people going to move off of mailman 2? I've been looking at mailman 3 and finding it hard to grok after using mailman 2 for many years. I haven't seen a discussion about this so I

Re: [Mailman-Users] Systemctl unit file for MM

On 4/10/19 8:06 AM, Bryan Blackwell wrote: > Hi folks, > > I'm learning how to use systemd on my Fedora box, since I still had MM as a > script startup I thought I'd fix that. Below is a unit file, it starts and > stops ok but the rm command doesn't work. Comments welcome. > > [Unit] > Descri

Re: [Mailman-Users] Spam / Email Spoofing Problem (SPF check possible?)

Grant Taylor via Mailman-Users writes: > Note: SPF by itself won't do anything to protect against From: header > spoofing. Sure, but if configured correctly, it gives you exactly the information you need. The problem with SPF is that a lot of header spoofing is legitimate (at least from the

Re: [Mailman-Users] Spam / Email Spoofing Problem (SPF check possible?)

On 4/5/19 11:59 AM, Valentin Schwarze via Mailman-Users wrote: Are there any settings that we as administrators of the list could change to end that behavior? For example, is it possible in any way, that Mailman only accepts emails that passed a SPF check? Or any other option to prevent email w

Re: [Mailman-Users] Spam / Email Spoofing Problem (SPF check possible?)

On 4/5/2019 10:59 AM, Valentin Schwarze via Mailman-Users wrote: We happend to have some spam issues on our mailman lists. These spammers were able to send emails on our lists through mail spoofing (only faking the From: field in the header is sufficient to get accepted). Do you have any mail

Re: [Mailman-Users] Spam / Email Spoofing Problem (SPF check possible?)

On 4/5/19 10:59 AM, Valentin Schwarze via Mailman-Users wrote: > > I am the administrator of some mailman lists of the student > self-administration of our university. We happend to have some spam issues on > our mailman lists. These spammers were able to send emails on our lists > through mail

Re: [Mailman-Users] Strange behavior with Outlook+Exchange

On 4/2/19 9:55 AM, Odhiambo Washington wrote: > I have a client who is facing a problem unseen before. > She's been using MS Outlook to send mail to a Newsletter managed by Mailman. > > It's all been good, using Approved:Password as the very first line to send > her newsletters using Outlook - unt

Re: [Mailman-Users] FetchMail feed into Mailman

On 3/26/19 4:12 PM, Grant Taylor via Mailman-Users wrote: > Sure, FetchMail can pull email from the ISP and inject it into the local > server.  But what advantage does that gain you?  Is said advantage worth > the complexity? Apparently lennartwware-infested linux distros no longer require MTA, p

Re: [Mailman-Users] FetchMail feed into Mailman

On 3/26/19 12:36 AM, Jim Ziobro wrote: You won't know how important until you start getting duplicate messages like RFC 1047 . How would having a local MTA change the behavior in the face of a duplicate message? I've seen symptoms of duplicate messages wh

Re: [Mailman-Users] FetchMail feed into Mailman

On 3/26/19 12:36 AM, Jim Ziobro wrote: why not setup standard Mailman under your favorite mail system and let FetchMail do what it does best? The unneeded complexity of a local mail system. FetchMail & SMTP Auth would work against an ISP's email server over dynamic / dial up connections. Su

Re: [Mailman-Users] mailman headers get corrupted / incomplete

On 3/24/19 1:14 PM, wally b wrote: > > Maybe I found the cause of this: > (last part of) the headers look like this: > > > X-SA-Exim-Scanned: No (on b(0, 0, = > 0);" class=3D"">Als u zich = > wilt afmelden voor deze emails, laat ... > > > > The text "..b(0,.." etc seems not to belong

Re: [Mailman-Users] mailman on google comput engine

On 3/25/19 8:21 AM, Grant Taylor via Mailman-Users wrote: > > Noted.  I think it would be possible to interject a shim between > fetchmail that would extract what's necessary to speak LMTP to Mailman. Yes, it would be possible. > Is the LMTP still STDIN / STDOUT or something else (possibly a U

Re: [Mailman-Users] mailman on google comput engine

On 3/24/19 11:50 PM, Stephen J. Turnbull wrote: This should work in Mailman 2, but won't in Mailman 3 (which expects incoming posts via LMTP). Noted. I think it would be possible to interject a shim between fetchmail that would extract what's necessary to speak LMTP to Mailman. Is the LMTP

Re: [Mailman-Users] mailman on google comput engine

Grant Taylor via Mailman-Users writes: > I'm talking about bypassing the local MTA all together. Pipe fetcmail's > STDOUT to a wrapper script to extract the command and mailing list > before piping it into the mailman executable with said command and > mailing list. This should work in Ma

Re: [Mailman-Users] iterative loop

On 3/22/19 5:42 AM, Web Analysts via Mailman-Users wrote: > Okay here's the output from 'postconf -n' > > > alias_database = hash:/etc/aliases > alias_maps = hash:/etc/aliases, hash:/var/lib/mailman/data/aliases OK ... > mydestination = mail.domainname.tld, mail1.domainname.tld, > lists.domain

Re: [Mailman-Users] Transactional email services with Mailman

-Original Message- From: Mailman-Users On Behalf Of Andrew Hodgson Sent: Friday, March 22, 2019 8:15 AM To: mailman-users@python.org Subject: [Mailman-Users] Transactional email services with Mailman Hi, I am looking at using a transactional email service with Mailman as I am having issu

Re: [Mailman-Users] iterative loop

rtual_transport = lmtp:unix:private/dovecot-lmtp -Original Message- From: Mailman-Users [mailto:mailman-users-bounces+csa=web-analysts@python.org] On Behalf Of Mark Sapiro Sent: Tuesday, March 19, 2019 7:24 PM To: mailman-users@python.org Subject: Re: [Mailman-Users] iterative loop

Re: [Mailman-Users] Fwd: Uncaught runner exception

Am 21.03.2019 um 17:48 schrieb Mark Sapiro: > On 3/21/19 9:20 AM, Lothar Schilling wrote: >> Python 2.6.6 (r266:84292, Aug 18 2016, 15:13:37) >> [GCC 4.4.7 20120313 (Red Hat 4.4.7-17)] on linux2 >> (InteractiveConsole) > from string import lowercase > lowercase >> 'abcdefghijklmnopqrstuvwxy

Re: [Mailman-Users] mailman on google comput engine

On 3/21/19 4:04 PM, Dimitri Maziuk via Mailman-Users wrote: I honestly don't remember the details but if I was passing mail to local MTA configured as my home MX, I don't see why mailman wouldn't work behind that. I think that it should. I'm talking about bypassing the local MTA all together.

Re: [Mailman-Users] mailman on google comput engine

On 3/21/19 3:57 PM, Grant Taylor via Mailman-Users wrote: > Fetchmail itself is plenty common.  I had no idea that it was as common > with Mailman.  209 hits on the link that Mark shared. I honestly don't remember the details but if I was passing mail to local MTA configured as my home MX, I don'

Re: [Mailman-Users] mailman on google comput engine

On 3/21/19 2:05 PM, Dimitri Maziuk via Mailman-Users wrote: IST vaguely R firing up fetchmail from a dip script to inject messages from my school mailbox into my local qmail... Plenty typical at the time. Fetchmail itself is plenty common. I had no idea that it was as common with Mailman. 20

Re: [Mailman-Users] mailman on google comput engine

On 3/21/19 1:56 PM, Mark Sapiro wrote: > On 3/21/19 11:29 AM, Grant Taylor via Mailman-Users wrote: >> >> I see no technical reason why Mailman couldn't function via something >> like fetchmail from a POP3 mailbox and SMTP Authentication to send. ... >> It would be quite atypical.  But I think it s

Re: [Mailman-Users] mailman on google comput engine

On 3/21/19 11:29 AM, Grant Taylor via Mailman-Users wrote: > > I see no technical reason why Mailman couldn't function via something > like fetchmail from a POP3 mailbox and SMTP Authentication to send. > > Fetchmail would pull the messages from an external 3rd party email > server, do a little p

Re: [Mailman-Users] mailman on google comput engine

On 3/21/19 11:58 AM, Adam Goldberg wrote: There are ways around this. I see no technical reason why Mailman couldn't function via something like fetchmail from a POP3 mailbox and SMTP Authentication to send. Fetchmail would pull the messages from an external 3rd party email server, do a lit

Re: [Mailman-Users] mailman on google comput engine

A consumer internet connection frequently has incoming port 25 simply blocked, and outgoing port 25 either blocked entirely or blocked for all but the ISP’s outgoing mail server. There are ways around this.Consider duocircle.com “backup mx” service. > On Mar 21, 2019, at 1:44 PM, Mark Sapi

Re: [Mailman-Users] mailman on google comput engine

On 3/20/19 11:40 PM, 황병희 wrote: > i just did make one vm instance Ubuntu 18.04 on google compute > engine. barely i did install postfix at there. hmm if possible, i wish > to run mailing service for my family and me -- it needs a little bit some > comunication plus some > records about family hist

Re: [Mailman-Users] mailman on google comput engine

On 3/21/19 12:40 AM, 황병희 wrote: in this case i can run mailman with other port (example 625)? again question, Mailman can act with 625 or 1625 or 2625, ...? No. Not directly. Mailman is not a mail server. You must have a mail server (daemon) sit in front of Mailman. You can make that mail

Re: [Mailman-Users] Fwd: Uncaught runner exception

On 3/21/19 9:20 AM, Lothar Schilling wrote: > > Python 2.6.6 (r266:84292, Aug 18 2016, 15:13:37) > [GCC 4.4.7 20120313 (Red Hat 4.4.7-17)] on linux2 > (InteractiveConsole) from string import lowercase lowercase > 'abcdefghijklmnopqrstuvwxyz' import string string > I'm out of

Re: [Mailman-Users] Fwd: Uncaught runner exception

Am 20.03.2019 um 18:54 schrieb Mark Sapiro: > On 3/20/19 5:31 AM, Lothar Schilling wrote: >> There is just one >> >> /usr/lib64/python2.6/string.py >> >> yielding >> >> lowercase = 'abcdefghijklmnopqrstuvwxyz'. > > You could try one more thing. Run Mailman's > > bin/withlist -i > ... from stri

Re: [Mailman-Users] Delivery errors and spam grading

Jim Dory writes: > On Mon, Mar 18, 2019 at 4:39 AM Stephen J. Turnbull < > turnbull.stephen...@u.tsukuba.ac.jp> wrote: > > (You probably should also disable the Digestable option in > > [Digest options] When I wrote this, I was thinking of a new list, in the context of personalization as a ha

Re: [Mailman-Users] Fwd: Uncaught runner exception

On 3/20/19 5:31 AM, Lothar Schilling wrote: > > There is just one > > /usr/lib64/python2.6/string.py > > yielding > > lowercase = 'abcdefghijklmnopqrstuvwxyz'. You could try one more thing. Run Mailman's bin/withlist -i ... >>> from string import lowercase >>> lowercase (response) >>> import

Re: [Mailman-Users] Fwd: Uncaught runner exception

Am 18.03.2019 um 17:06 schrieb Mark Sapiro: > On 3/18/19 2:29 AM, Lothar Schilling wrote: >> Exception in fixAuthor: D▒rthe Hinz - Fl▒chtlingsrat Nds. >> Mar 18 08:33:51 2019 (23745) lowercase value: >> 'abcdefghijklmnopqrstuvwxyz\xb5\xdf\xe0\xe1\xe2\xe3\xe4\xe5\xe6\xe7\xe8\xe9\xea\xeb\xec\xed\xee\

Re: [Mailman-Users] iterative loop

On 3/19/19 6:27 PM, Web Analysts via Mailman-Users wrote: > Well I removed hostname.domainname.tld from mydestination in > /etc/postfix/main.cf and restarted Postfix. No dice...see below: > > Mar 19 18:21:43 zarathustra postfix/smtpd[18769]: 925B210193B: > client=localhost.localdomain[127.0.0.1] >

Re: [Mailman-Users] iterative loop

o Sent: Tuesday, March 19, 2019 9:22 AM To: mailman-users@python.org Subject: Re: [Mailman-Users] iterative loop On 3/18/19 5:19 PM, Web Analysts via Mailman-Users wrote: > Using mailman 2.1.9 on ubuntu 14.04 using mysql for aliases and mail > accounts. Iy was working fine for a long time then

Re: [Mailman-Users] iterative loop

On 3/18/19 5:19 PM, Web Analysts via Mailman-Users wrote: > Using mailman 2.1.9 on ubuntu 14.04 using mysql for aliases and mail > accounts. Iy was working fine for a long time then something went awry. Now > I've got an iterative loop and multiple email lists are generating > 'Undelivered Mail Ret

Re: [Mailman-Users] Delivery errors and spam grading

On Mon, Mar 18, 2019 at 6:19 PM Mark Sapiro wrote: > > Does your outgoing MTA add an X-Ham-Report: header? Perhaps it does so > in a non-compliant way. > > > > is disabling the digest option something people do regularly to > > prevent issues like this? and if so - if I were to disable it now, wh

Re: [Mailman-Users] Delivery errors and spam grading

On 3/18/19 6:44 PM, Jim Dory wrote: > On Mon, Mar 18, 2019 at 4:39 AM Stephen J. Turnbull < > turnbull.stephen...@u.tsukuba.ac.jp> wrote: > >> >> (You probably should >> also disable the Digestable option in [Digest options] >> > > I'm also receiving several bounces back for errors such as: >

Re: [Mailman-Users] Delivery errors and spam grading

On 3/18/2019 8:44 PM, Jim Dory wrote: On Mon, Mar 18, 2019 at 4:39 AM Stephen J. Turnbull < turnbull.stephen...@u.tsukuba.ac.jp> wrote: (You probably should also disable the Digestable option in [Digest options] I'm also receiving several bounces back for errors such as: "SMTP error fr

Re: [Mailman-Users] Delivery errors and spam grading

On Mon, Mar 18, 2019 at 4:39 AM Stephen J. Turnbull < turnbull.stephen...@u.tsukuba.ac.jp> wrote: > > (You probably should > also disable the Digestable option in [Digest options] > I'm also receiving several bounces back for errors such as: "SMTP error from remote mail server after end of dat

Re: [Mailman-Users] Delivery errors and spam grading

On 3/18/19 5:39 AM, Stephen J. Turnbull wrote: > > If you mean any other kind of delivery failure that is detected by the > Mailman host, but is not returned to Mailman, then it is simply > impossible for Mailman to even be aware of them, and you would have to > check the MTA (mail server) logs.

Re: [Mailman-Users] Fwd: Uncaught runner exception

On 3/18/19 2:29 AM, Lothar Schilling wrote: > > Exception in fixAuthor: D▒rthe Hinz - Fl▒chtlingsrat Nds. > Mar 18 08:33:51 2019 (23745) lowercase value: > 'abcdefghijklmnopqrstuvwxyz\xb5\xdf\xe0\xe1\xe2\xe3\xe4\xe5\xe6\xe7\xe8\xe9\xea\xeb\xec\xed\xee\xef\xf0\xf1\xf2\xf3\xf4\xf5\xf6\xf8\xf9\xfa\xf

Re: [Mailman-Users] Delivery errors and spam grading

On 3/18/2019 4:51 AM, Davide Marchi wrote: 1) How is it possible from Mailman monitor the delivery errors? Only sysadmin mail server from the logs? This is what VERP deliveries are for. The FROM address is tagged so that bounces can be clearly identified. https://wiki.list.org/DOC/So%20what%2

Re: [Mailman-Users] Fwd: Uncaught runner exception

Mit herzlichem Dank und freundlichen Grüßen! Lothar Schilling Förderverein Pro Asyl e.V. Postfach 160624 60069 Frankfurt Tel. 069 242314-40 Am 15.03.2019 um 17:25 schrieb Mark Sapiro: > On 3/15/19 4:27 AM, Lothar Schilling wrote: >> Am 14.03.2019 um 18:55 schrieb Mark Sapiro: >>> On 3/14/19 2:3

Re: [Mailman-Users] Fwd: Uncaught runner exception

On 3/15/19 4:27 AM, Lothar Schilling wrote: > Am 14.03.2019 um 18:55 schrieb Mark Sapiro: >> On 3/14/19 2:39 AM, Lothar Schilling wrote: ... >>> string >>> ... > Sadly not: > > import string > string.lowercase >     'abcdefghijklmnopqrstuvwxyz' > string   >     This is interesting. Here you ge

Re: [Mailman-Users] Fwd: Uncaught runner exception

Am 14.03.2019 um 18:55 schrieb Mark Sapiro: > On 3/14/19 2:39 AM, Lothar Schilling wrote: >>  Am 12.03.2019 um 23:47 schrieb Mark Sapiro: >>> What is the path to the Python interpreter that Mailman is using? >> /usr/bin/python >> /usr/bin/python -V: Python 2.6.6 > > What is the python command in th

Re: [Mailman-Users] Is there a way to get a list of all lists with the list owner?

See . I think list_owners with '-w' and possibly '-m' is what you want. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users

Re: [Mailman-Users] Fwd: Uncaught runner exception

On 3/14/19 2:39 AM, Lothar Schilling wrote: >  Am 12.03.2019 um 23:47 schrieb Mark Sapiro: >> >> What is the path to the Python interpreter that Mailman is using? > > /usr/bin/python > /usr/bin/python -V: Python 2.6.6 What is the python command in the result of ps -fwwA|grep ArchRunner >> Wha

Re: [Mailman-Users] Fwd: Uncaught runner exception

On 3/14/19 8:14 AM, Stephen J. Turnbull wrote: > Lothar Schilling writes: > > > > What do you get if in that Python you do > > > > > > import string > > > lowercase > > I think this should be 'string.lowercase'. > > > import string > > > > lowercase > > Traceback (most recent call last)

Re: [Mailman-Users] MTA says too many recipients

On 3/12/19 8:47 AM, Ajay Guleria wrote: >> >> We are using mailman 2.x. We are relaying all mails though a postfix MTA >> server where smtpd_recipeint_limit is 36. On mailman server in logs we are >> getting 452: 4.5.3 Error: too many recipients. Our mailing list has 960 >> members and Ceiling

Re: [Mailman-Users] Uncaught runner exception

On 3/12/19 2:37 AM, Lothar Schilling wrote: > > An example of a complete error message: > > Mar 11 17:02:22 2019 (15400) SHUNTING: > 1552320069.504329+15fb4f71a5404fd1af3dafbe2780486d5b474cc7 > Mar 11 17:22:37 2019 (15400) Uncaught runner exception: 'ascii' codec > can't decode byte 0xb5 in posit

Re: [Mailman-Users] Uncaught runner exception

> On 3/8/19 8:17 AM, Mark Sapiro wrote: >> On 3/8/19 12:05 AM, Lothar Schilling wrote: >>> Am 07.03.2019 um 23:54 schrieb Mark Sapiro: I would still like to find the underlying issue. I have been unable to duplicate it locally. I would appreciate it if before you run bin/unshunt, yo

Re: [Mailman-Users] Uncaught runner exception

On 3/8/19 8:17 AM, Mark Sapiro wrote: > On 3/8/19 12:05 AM, Lothar Schilling wrote: >> Am 07.03.2019 um 23:54 schrieb Mark Sapiro: > >>> I would still like to find the underlying issue. I have been unable to >>> duplicate it locally. I would appreciate it if before you run >>> bin/unshunt, you cou

Re: [Mailman-Users] Uncaught runner exception

On 3/8/19 12:05 AM, Lothar Schilling wrote: > Am 07.03.2019 um 23:54 schrieb Mark Sapiro: >> >> You can now reprocess them and add them to the archive by running >> Mailman's 'bin/unshunt' command. > Oh, that's what I did, unshunting them. They were processed and > archived. But the messages - almo

Re: [Mailman-Users] How auto create Postfix virtual aliases on MySQL table

On 3/7/19 12:36 PM, Davide Marchi wrote: Hi Friends, We have a Postfix mail server on Debian Stretch, where all virtual user and virtual aliases are stored on MySQL tables. I would like to know if Mailman could provide its creation in automatic or alternatively is there a configuration file t

Re: [Mailman-Users] Mailing list "Mailman" mandatory?

On 3/7/19 12:23 PM, Davide Marchi wrote: Anyway, only just to prevent mistakes from our new members (that are not really technicians..), could you suggest me how is it possible to hide it from the list web page? You can not display it on the listinfo and admin web overview pages by setting

Re: [Mailman-Users] Uncaught runner exception

Am 07.03.2019 um 23:54 schrieb Mark Sapiro: > On 3/6/19 2:03 AM, Lothar Schilling wrote: > >> Following your instruction errors get now logged like this (where x is >> lower case, X upper case alphabet). >> >> Mar 06 10:36:56 2019 (16870) Exception in fixAuthor: Kxx Wxxx >> Mar 06 10:36:56 2019 (16

Re: [Mailman-Users] Uncaught runner exception

On 3/6/19 2:03 AM, Lothar Schilling wrote: > Following your instruction errors get now logged like this (where x is > lower case, X upper case alphabet). > > Mar 06 10:36:56 2019 (16870) Exception in fixAuthor: Kxx Wxxx > Mar 06 10:36:56 2019 (16870) Exception in fixAuthor: NXX - Fx▒xxx XX >

<    2   3   4   5   6   7   8   9   10   11   >