diff options
| author | pp <pp@455248ca-bdda-0310-9134-f4ebb693071a> | 2006-07-31 23:54:47 +0000 |
|---|---|---|
| committer | pp <pp@455248ca-bdda-0310-9134-f4ebb693071a> | 2006-07-31 23:54:47 +0000 |
| commit | 96d8d7227295125e2f8c8020b6e3adf7989e9400 (patch) | |
| tree | e8f433e7672dbe66f562eb55785cf01d6bdd6ccf /README | |
| parent | 033311a41c24fd801734b6ed983e922b3f94e384 (diff) | |
- information about recently discovered weakness of 1 pass version
git-svn-id: https://siedziba.pl:790/svn/repos/dbxrecover@239 455248ca-bdda-0310-9134-f4ebb693071a
Diffstat (limited to 'README')
| -rw-r--r-- | README | 7 |
1 files changed, 5 insertions, 2 deletions
@@ -20,8 +20,11 @@ It is caused by a fact, that it is impossible, in general, to detect the first fragment of a message. The last fragment is easy to find, as it has 0 as an id of the next fragment. The first fragment, on the other hand, is not marked in any way. Currently the script treats a fragment as first if it starts with one -of common headers such as "From:" or "Received:". The probability of writing -incomplete message is low though, due to the following factors: +of common headers such as "From:" or "Received:" (update: some mail systems and +antivirus/antispam solutions add their non standard headers at the top of the +message, thus making this test not effective; better solution is needed). The +probability of writing incomplete message is low though, due to the following +factors: - the message must contain one or more of the header strings in its body - the string must be located at the start of a fragment, which means a |
