DandelionNStuff/dkimpy-milter-smtputf8
4
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Improve README.md formating for markdown display on pypi

Browse Source
This commit is contained in:
Scott Kitterman
2020-01-06 02:07:49 -05:00
parent 04ef3629d7
commit bf578e7b86
2 changed files with 55 additions and 51 deletions
Download Patch File Download Diff File Expand all files Collapse all files
CHANGES
+3
View File
@@ -1,3 +1,6 @@
1.2.2
- Improve README.md formating for markdown display on pypi
1.2.1 2020-01-04 1.2.1 2020-01-04
- Fix expand option not to fail if files are missing since socket activation - Fix expand option not to fail if files are missing since socket activation
service files are not shipped in the sdist service files are not shipped in the sdist
README.md
+9 -8
View File
@@ -52,6 +52,7 @@ The package includes a custom setup command called expand. It allows various
file locations in init scripts, man pages, and config files to be over-ridden file locations in init scripts, man pages, and config files to be over-ridden
at install time. at install time.
expand: Expand @@ variables in input files, simlar to make macros. expand: Expand @@ variables in input files, simlar to make macros.
user_options: user_options:
--sysconfigdir=, e: Specify system configuration directory. --sysconfigdir=, e: Specify system configuration directory.
@@ -237,7 +238,7 @@ and deserve consideration.
By default, sendmail quotes to address header fields when there are no By default, sendmail quotes to address header fields when there are no
quotes and the display part of the address contains a period or an quotes and the display part of the address contains a period or an
apostrophe. However, opendkim only sees the raw, unmodified form of apostrophe. However, dkimpy-milter only sees the raw, unmodified form of
the header field, and so the content that gets verified and what gets the header field, and so the content that gets verified and what gets
signed will not be the same, guaranteeing the attached signature is not signed will not be the same, guaranteeing the attached signature is not
valid. valid.
@@ -263,16 +264,16 @@ and deserve consideration.
To: very long name <a@example.org>, To: very long name <a@example.org>,
anotherloo...ong name b <b@example.org> anotherloo...ong name b <b@example.org>
This rewrite is also done after opendkim has seen the message, meaning This rewrite is also done after dkimpy-milter has seen the message,
the signature opendkim attaches to the message does not match the meaning the signature dkimpy-milter attaches to the message does not match
content it signed. There is not a known configuration change to the content it signed. There is not a known configuration change to
mitigate this mutation. mitigate this mutation.
The only known mechanism for dealing with this is to have distinct The only known mechanism for dealing with this is to have distinct
instances of opendkim do the verifying (inbound) and signing (outbound) instances of dkimpy-milter do the verifying (inbound) and signing
so that the version that arrives at the signing instance is already (outbound) so that the version that arrives at the signing instance is
in the rewritten form, guaranteeing the input and output are the same already in the rewritten form, guaranteeing the input and output are the
and thus the signature matches the payload. same and thus the signature matches the payload.
### POSTFIX ### POSTFIX