git://git.exim.org
/
exim.git
/ commitdiff
commit
grep
author
committer
pickaxe
?
search:
re
summary
|
shortlog
|
log
|
commit
| commitdiff |
tree
raw
|
patch
|
inline
| side by side (from parent 1:
c5768a4
)
Docs: typoes
author
Jeremy Harris
<jgh146exb@wizmail.org>
Mon, 24 Jul 2023 20:01:22 +0000
(21:01 +0100)
committer
Jeremy Harris
<jgh146exb@wizmail.org>
Thu, 3 Aug 2023 10:20:33 +0000
(11:20 +0100)
doc/doc-docbook/spec.xfpt
patch
|
blob
|
history
diff --git
a/doc/doc-docbook/spec.xfpt
b/doc/doc-docbook/spec.xfpt
index b8173a1b836773090bd95e8649d903e91d62c959..f35ebf675aae45047491fdb05ecf1b273a6af09b 100644
(file)
--- a/
doc/doc-docbook/spec.xfpt
+++ b/
doc/doc-docbook/spec.xfpt
@@
-7384,7
+7384,7
@@
For example, the way to write the NIS+ query is
.endd
.cindex "tainted data" "in lookups"
.new
.endd
.cindex "tainted data" "in lookups"
.new
-&*All*& tainted data used in a qu
o
ery-style lookup must be quoted
+&*All*& tainted data used in a query-style lookup must be quoted
using a mechanism appropriate for the lookup type.
.wen
See chapter &<<CHAPexpand>>& for full coverage of string expansions. The quote
using a mechanism appropriate for the lookup type.
.wen
See chapter &<<CHAPexpand>>& for full coverage of string expansions. The quote
@@
-32211,7
+32211,7
@@
If multiple header lines match, all are removed.
There is no harm in attempting to remove the same header twice nor in removing
a non-existent header. Further header specifiers for removal may be accumulated
during the DATA and MIME ACLs, after which matching headers are removed
There is no harm in attempting to remove the same header twice nor in removing
a non-existent header. Further header specifiers for removal may be accumulated
during the DATA and MIME ACLs, after which matching headers are removed
-if present. In the case of non-SMTP messages, remove speifiers are
+if present. In the case of non-SMTP messages, remove spe
c
ifiers are
accumulated during the non-SMTP ACLs, and are acted on after
all the ACLs have run. If a message is rejected after DATA or by the non-SMTP
ACL, there really is no effect because there is no logging of what headers
accumulated during the non-SMTP ACLs, and are acted on after
all the ACLs have run. If a message is rejected after DATA or by the non-SMTP
ACL, there really is no effect because there is no logging of what headers