Mailman 3 October 2020 - Twisted

[Twisted-Python] Request for new Twisted release?
by Craig Rodrigues Oct. 12, 2020

Oct. 12, 2020

Amber, Can we have a new Twisted release within the next two months, say in Nov./Dec. timeframe, or sooner if you'd like? In Twisted trunk, there are a lot of things that would be good to have in a new release. Here are some of the high order items: *Python 3 Fixes* - twist dns --pyzone now works on Python 3 (I had a project 6 months ago where I would have liked to have this in a release) - twisted.web.twcgi now works on Python 3 *Python 3.8 Fixes* - all tests pass on all platforms on Python 3.8, including asyncio tests on Windows *Python 3.9 Fixes* - all tests pass on Python 3.9.0rc2 (at least on Mac and Linux), (thanks to Michał Górny) *Python 2.7* - Python 2.7 support has been dropped in trunk *Black* - black code formatter has been integrated into the CI for Twisted, and all Twisted code is now formatted with Black (thanks to Tom Most) *Mypy* - mypy is now run as part of Twisted CI and checks the code for every PR. Type annotations compatible with Python 3.5+ are slowly being added to the codebase. There are a lot of other small fixes and enhancements that people have contributed since the last Twisted release. I would like this new release to be the last release supporting Python 3.5, so that Python 3.5 support can be removed in trunk, and PEP-526 style variable annotations can be added in trunk. Thanks for your consideration. -- Craig

5 12

[Twisted-Python] Weekly Bug Summary
by trac＠twistedmatrix.com Oct. 11, 2020

Oct. 11, 2020

1 0

[Twisted-Python] Mailgun Email Service Replacement Proposal
by Glyph Oct. 4, 2020

Oct. 4, 2020

Hello Twistors, As many of you know, Twisted's email infrastructure for the past few years has been generously provided by Mailgun. This was a huge upgrade to our sender reputation over running our own Exim instance at the time, and I'm tremendously grateful for all the effort it's saved the project. However, Mailgun has never been a super close fit for what we actually want as a project (see for example https://github.com/glyph/mg2dsn <https://github.com/glyph/mg2dsn> which papers over some of the differences between what they provide and what we actually want), and over the years there have been several hiccups in service as Mailgun tweaks its pricing and their plan-upgrade machinery doesn't know what to do with our discounted account. Right now, I'm dealing with a minor issue where our "plan" (which, again, Mailgun has generously given us for free) no longer includes the ability to process incoming email... so, for example, this email is only reaching you because the pre-existing inbound routes are grandfathered in, and continue to work (whew!); however, I can no longer add new @twistedmatrix.com email addresses nor change the configuration of existing ones. Now, for this particular issue I've opened a ticket with Mailgun and hopefully they'll be kind enough to extend their support to us yet again, but in the longer term, it feels like we might want to go back to hosting our own thing; ideally a thing that allows us to dogfood Twisted and maybe learn interesting things about our SMTP support. What we need is not trivial, but it's also not too complicated. Critically we do not need to host a full-featured mail storage service, as we only do forwarding to and from other services. So what we need is a thing that can: listen on TLS ports with a certificate generate an RSA key for DKIM spit out something we can plug into our twisted.names configuration instead of this - https://github.com/twisted-infra/braid/blob/1df63c5d8b44e079487be2f0bf09910… <https://github.com/twisted-infra/braid/blob/1df63c5d8b44e079487be2f0bf09910…> distinguish between inbound-forwarded and outbound-sent email authenticate users to send for particular addresses (i.e. set "From" and "Sender" headers, and confirm consistency with MAIL FROM & auth, reject if anything doesn't match; with a caveat for messages forwarded via mailman); sign these outbound messages with https://pypi.org/project/dkimpy/ <https://pypi.org/project/dkimpy/> forward inbound messages which have DMARC alignment maybe run spambayes and junk stuff that's obviously spammy before forwarding if we want to get fancy DKIM sign messages on their way through take over port 25, somehow talk to mailman (either via talking to Debian's Exim on some alternate port or by running mailman's receipt scripts itself). Basically, a signing / authenticating MX relay. Anyone interested in attempting to write such a thing with Twisted? :) -glyph

2 2

[Twisted-Python] Weekly Bug Summary
by trac＠twistedmatrix.com Oct. 4, 2020

Oct. 4, 2020

1 0

[Twisted-Python] Twisted with pypy3 on Ubuntu 20.4, SSL error: 'ee key too small'
by Craig Rodrigues Oct. 1, 2020

Oct. 1, 2020

Hi, I ran an experiment to run the Twisted tests on Ubuntu 20.4 using this version of using pypy3: *Python 3.6.9 (2ad108f17bdb, Apr 07 2020, 02:29:05* *Pypy 7.3.1 with GCC 7.3.1 20180303 (Red Hat 7.3.1-5)* A bunch of the conch tests failed in this Ubuntu environment: https://github.com/twisted/twisted/runs/1173397508 like this: *===============================================================================Error: Traceback (most recent call last): File "/home/runner/work/twisted/twisted/build/alldeps-withcov-posix/site-packages/twisted/test/test_sslverify.py", line 1780, in test_ellipticCurveDiffieHellman onData=onData, File "/home/runner/work/twisted/twisted/build/alldeps-withcov-posix/site-packages/twisted/test/test_sslverify.py", line 716, in loopback self.serverPort = reactor.listenSSL(0, serverFactory, serverCertOpts) File "/home/runner/work/twisted/twisted/build/alldeps-withcov-posix/site-packages/twisted/internet/posixbase.py", line 593, in listenSSL tlsFactory = tls.TLSMemoryBIOFactory(contextFactory, False, factory) File "/home/runner/work/twisted/twisted/build/alldeps-withcov-posix/site-packages/twisted/protocols/tls.py", line 748, in __init__ contextFactory = _ContextFactoryToConnectionFactory(contextFactory) File "/home/runner/work/twisted/twisted/build/alldeps-withcov-posix/site-packages/twisted/protocols/tls.py", line 629, in __init__ oldStyleContextFactory.getContext() File "/home/runner/work/twisted/twisted/build/alldeps-withcov-posix/site-packages/twisted/internet/_sslverify.py", line 1636, in getContext self._context = self._makeContext() File "/home/runner/work/twisted/twisted/build/alldeps-withcov-posix/site-packages/twisted/internet/_sslverify.py", line 1645, in _makeContext ctx.use_certificate(self.certificate) File "/home/runner/work/twisted/twisted/build/alldeps-withcov-posix/site-packages/OpenSSL/SSL.py", line 960, in use_certificate _raise_current_error() File "/opt/hostedtoolcache/PyPy/3.6.9/x64/lib_pypy/_functools.py", line 80, in __call__ return self._func(*(self._args + fargs), **fkeywords) File "/home/runner/work/twisted/twisted/build/alldeps-withcov-posix/site-packages/OpenSSL/_util.py", line 54, in exception_from_error_queue raise exception_type(errors)OpenSSL.SSL.Error: [('SSL routines', 'SSL_CTX_use_certificate', 'ee key too small')]twisted.test.test_sslverify.OpenSSLOptionsECDHIntegrationTests.test_ellipticCurveDiffieHellman===============================================================================* I'm not sure what the root problem is, but my suspicion is that the SSL library in this particular Ubuntu environment does not permit keys smaller than 2048 bits. Anyone have any other ideas as to the cause of this error? Thanks. -- Craig

2 2