lp:~bmcbm/dkimpy-milter

Author: Casper Bruun Møller
Author Date: 2021-08-02 20:57:04 UTC

Fix possible TypeError in UTF-8 string decoding.

Author: Scott Kitterman
Author Date: 2020-08-09 18:21:50 UTC

Update version in setup.py to 1.2.2, prepare for release

Author: Scott Kitterman
Author Date: 2020-08-09 18:12:05 UTC

Minimal fix for dnspython 2.0.0 compatibility (still works with 1.16.0)

Author: Scott Kitterman
Author Date: 2020-01-15 14:17:53 UTC

Fix typo in log message

Author: Scott Kitterman
Author Date: 2020-01-15 14:17:10 UTC

Fix typo in log message

Author: Scott Kitterman
Author Date: 2019-03-13 02:01:00 UTC

Merge branch 'dkg/socket-activation' into 1_0

Author: dkg
Author Date: 2019-02-21 00:01:30 UTC

Convert __init__.py to python3

The main work here is about bytes vs. strings. This work was
confusing for several reasons:

 * pymilter thinks that headers are all strings, but body is bytes

 * dkimpy wants to deal with bytes objects generally (though it
   accepts a string object as an ed25519 secret key for some reason,
   despite requiring bytes as an RSA secret key)

 * authres.AuthenticationResultsHeader object converts easily to a
   string, but has no direct bytes conversion. meanwhile, it wants
   its arguments as strings, but will accept them if they are bytes
   and convert them with something like str(), which leaves weird
   cruft like "header.a=b'ed25519-sha256'"

 * dkimpy_milter/utils.py contains fold() which expects bytes

 * self.fp needs to accumulate the on-the-wire version of the message
   as a whole (so it needs to be bytes). That means converting the
   headers. Header names and values are US-ASCII, per §2.2 of RFC
   5322, so they should be convertible cleanly, but we still have to
   convert them explicitly so that python knows the right thing to do.

At any rate, tests/runtests all passes with these changes, and the
output for both Authentication-Results: and DKIM-Signature headers
looks the same.

Author: dkg
Author Date: 2019-02-21 22:12:59 UTC

Enable sd_listen_fds(3)-style socket-activation support

I've added straightforward systemd unit files in
system/socket-activation/ that make use of this approach, and a
README.md in the same location that describes the tradeoffs.

Author: dkg
Author Date: 2019-02-21 15:49:22 UTC

Expand test suite to cover RSA as well as ed25519