Scott Kitterman
Scott Kitterman
There's no standard format for the private keys (or there wasn't when I started working on dkimpy-milter).
Relative to the original suggestion, it's my understanding that if you want to sign with both RSA and ed25119, you need to run it through opendkim twice. In dkimpy-milter, if...
> Definitely better. Okay will go pull your git master from your repo and work on setting up dkimpy-milter. Probably makes sense for any further discussion if I take it...
> interesting your opendkim set up works while mine does not verify. Scott do you know how to convert the opendkim keys (rsa and ed25519) to a format usable by...
Here's what I have that works in python3: def envfrom(self, f, *str): [...] self.fp = io.BytesIO() def header(self, name, val): [...] if self.fp: self.fp.write(b"%s: %s\n" % (codecs.encode(name, 'ascii'), codecs.encode(val, 'ascii')))...
Actually, Looking at that, the use of ascii is probably a bug in my code. I suspect that should be utf-8. Scott K
It's a distutils versus setuptools thing I think. You've got long_description_content_type='text/markdown', in setup.py, but it's not recognized (with twine check I get: Checking distribution dist/pyspf-2.0.14.tar.gz: warning: `long_description_content_type` missing. defaulting to...
Pypi wants rst because of the difference in the PKG-INFO file in the sdist. Here's the diff going from Pkg-Info generated by distutils and setuptools: >diff -ruN pyspf-2.0.14/PKG-INFO pyspf.egg-info/PKG-INFO ---...
The Python community has pretty well left distutils behind and focused on setuptools, so even though there are a few things about it I find annoying, it's the future. We...
On Wednesday, April 8, 2020 3:04:26 PM EDT Stuart D. Gathman wrote: > @joaoreis81 The example container is up, but doesn't include any test data. > I'll try copying to...