Suggest cargo install --locked option, wording
This commit is contained in:
parent
2e1443578a
commit
6f36f8868a
4 changed files with 12 additions and 11 deletions
|
@ -4,8 +4,8 @@
|
||||||
|
|
||||||
* Add `--reply-code`, `--reply-status-code`, and `--reply-text` options to
|
* Add `--reply-code`, `--reply-status-code`, and `--reply-text` options to
|
||||||
allow customising the SMTP reply when rejecting spam.
|
allow customising the SMTP reply when rejecting spam.
|
||||||
* Log a warning and do not truncate message body when `--max-message-size` is
|
* Log a warning and do not truncate the message body when `--max-message-size`
|
||||||
misconfigured (must be ≥ `spamc` max size as documented).
|
is misconfigured (must be ≥ `spamc` max size as documented).
|
||||||
* Update dependencies in `Cargo.lock`.
|
* Update dependencies in `Cargo.lock`.
|
||||||
|
|
||||||
## 0.1.2 (2020-06-07)
|
## 0.1.2 (2020-06-07)
|
||||||
|
|
4
Cargo.lock
generated
4
Cargo.lock
generated
|
@ -212,9 +212,9 @@ dependencies = [
|
||||||
|
|
||||||
[[package]]
|
[[package]]
|
||||||
name = "unicode-width"
|
name = "unicode-width"
|
||||||
version = "0.1.7"
|
version = "0.1.8"
|
||||||
source = "registry+https://github.com/rust-lang/crates.io-index"
|
source = "registry+https://github.com/rust-lang/crates.io-index"
|
||||||
checksum = "caaa9d531767d1ff2150b9332433f32a24622147e5ebb1f26409d5da67afd479"
|
checksum = "9337591893a19b88d8d87f2cec1e73fad5cdfd10e5a6f349f498ad6ea2ffb1e3"
|
||||||
|
|
||||||
[[package]]
|
[[package]]
|
||||||
name = "unicode-xid"
|
name = "unicode-xid"
|
||||||
|
|
10
README.md
10
README.md
|
@ -70,7 +70,7 @@ SpamAssassin Milter can be installed using Cargo. The program will be installed
|
||||||
in the local installation’s `bin` directory as usual:
|
in the local installation’s `bin` directory as usual:
|
||||||
|
|
||||||
```
|
```
|
||||||
cargo install spamassassin-milter
|
cargo install --locked spamassassin-milter
|
||||||
```
|
```
|
||||||
|
|
||||||
Again, if your distribution does not provide pkg-config metadata, try using the
|
Again, if your distribution does not provide pkg-config metadata, try using the
|
||||||
|
@ -81,8 +81,8 @@ then run the above install command with `PKG_CONFIG_PATH` set to that directory.
|
||||||
|
|
||||||
Once installed, SpamAssassin Milter can be invoked as `spamassassin-milter`.
|
Once installed, SpamAssassin Milter can be invoked as `spamassassin-milter`.
|
||||||
`spamassassin-milter` takes one mandatory argument, namely the listening socket
|
`spamassassin-milter` takes one mandatory argument, namely the listening socket
|
||||||
of the milter (the socket to which the MTA will connect). The socket spec can be
|
of the milter (the socket to which the MTA will connect). The socket spec should
|
||||||
in one of the formats <code>inet:<em>port</em>@<em>host</em></code> or
|
be in one of the formats <code>inet:<em>port</em>@<em>host</em></code> or
|
||||||
<code>inet6:<em>port</em>@<em>host</em></code> (for IPv6), or
|
<code>inet6:<em>port</em>@<em>host</em></code> (for IPv6), or
|
||||||
<code>unix:<em>path</em></code>, for a TCP or UNIX domain socket, respectively.
|
<code>unix:<em>path</em></code>, for a TCP or UNIX domain socket, respectively.
|
||||||
|
|
||||||
|
@ -234,8 +234,8 @@ submitted via a SASL-authenticated channel).
|
||||||
|
|
||||||
## Integration with mail delivery
|
## Integration with mail delivery
|
||||||
|
|
||||||
A further component that can be useful with SpamAssassin Milter is a
|
A further component that may be useful with SpamAssassin Milter is a
|
||||||
[Sieve]-capable mail delivery service. A Sieve script can for example look at
|
[Sieve]-capable mail delivery service. A Sieve script may for example look at
|
||||||
the `X-Spam-` SpamAssassin headers of the incoming message, and take action
|
the `X-Spam-` SpamAssassin headers of the incoming message, and take action
|
||||||
based on those.
|
based on those.
|
||||||
|
|
||||||
|
|
|
@ -70,7 +70,7 @@ If this option is not used, authenticated senders are trusted, and their
|
||||||
messages are not processed with SpamAssassin.
|
messages are not processed with SpamAssassin.
|
||||||
.TP
|
.TP
|
||||||
.BR \-n ", " \-\-dry-run
|
.BR \-n ", " \-\-dry-run
|
||||||
Process messages as usual, but do not take action or apply any modifications.
|
Process messages normally, but do not take action or apply any modifications.
|
||||||
Combined with
|
Combined with
|
||||||
.BR \-\-verbose ,
|
.BR \-\-verbose ,
|
||||||
this gives accurate insight into what would happen if run without
|
this gives accurate insight into what would happen if run without
|
||||||
|
@ -90,7 +90,8 @@ size configured for
|
||||||
.BR spamc .
|
.BR spamc .
|
||||||
Defaults to the
|
Defaults to the
|
||||||
.B spamc
|
.B spamc
|
||||||
default, 512000.
|
default,
|
||||||
|
.BR 512000 .
|
||||||
.TP
|
.TP
|
||||||
.BR \-B ", " \-\-preserve-body
|
.BR \-B ", " \-\-preserve-body
|
||||||
Suppress rewriting of spam message body.
|
Suppress rewriting of spam message body.
|
||||||
|
|
Loading…
Reference in a new issue