summaryrefslogtreecommitdiff
path: root/gnu/dist/postfix/implementation-notes
diff options
context:
space:
mode:
authorchristos <christos@NetBSD.org>2008-06-22 14:00:13 +0000
committerchristos <christos@NetBSD.org>2008-06-22 14:00:13 +0000
commit0eea94d78f23f8bf0f882d7bb6c49045c02b70b1 (patch)
tree67674837d9c18e613715948b7dc787eda4450a18 /gnu/dist/postfix/implementation-notes
parentbe0b2f64b3f1718c337b830133bdd01159c96446 (diff)
import 2.5.2, requested by perry, approved by releng.
Diffstat (limited to 'gnu/dist/postfix/implementation-notes')
-rw-r--r--gnu/dist/postfix/implementation-notes/MILTER6
1 files changed, 5 insertions, 1 deletions
diff --git a/gnu/dist/postfix/implementation-notes/MILTER b/gnu/dist/postfix/implementation-notes/MILTER
index 0da7cc5dbb0..f67fb90c5e0 100644
--- a/gnu/dist/postfix/implementation-notes/MILTER
+++ b/gnu/dist/postfix/implementation-notes/MILTER
@@ -247,4 +247,8 @@ or backward compatibility.
It does mean, however, that a pointer record can easily exceed the
length of a header record. This is why we go through the trouble
-of record relocation and dummy records.
+of record relocation and dummy records.
+
+In Postfix 2.4 we fixed this by adding padding to short message
+header records so that we can always write a pointer record over a
+message header. This immensly simplifies the code.