summaryrefslogtreecommitdiffstats
path: root/src/cleanup/bug2.in
blob: 138ca3d42b500a5e06be98d3029f13ce6b64f713 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
#verbose on
open bug2.file.tmp

# Two bugs while updating a short Subject: header immediately before
# a still virgin "append header" pointer record.
#
# Symptom:
#
#    warning: <filename>: malformed pointer record value: <garbage>
#
# Cause:
#
#    Failure to recognize the "append header" record while updating
#    a short message header
#
# Analysis:
#
# This happened while updating a header record that was followed by
# the current "append header" record. The pointer could be the initial
# "append header" record between message header and body, or it could
# be a later version of that pointer somewhere in the heap.
#
# - Postfix considered the pointer record as any pointer record after
# a header record. Thus, it decided that some portion of the pointer
# record could be overwritten with the location of the new Subject:
# header on the heap. Later "append header" operations would then
# update old "append header" record and thus clobber part of the
# pointer to the new Subject: header value.  
#
# - While saving the "append header" pointer record value on the
# heap, Postfix did not replace the still virgin "0" append header"
# pointer record value by the actual location of the message body
# content.

upd_header 1 Subject hey!
add_header foo foobar
close