http://bugzilla.spamassassin.org/show_bug.cgi?id=3331
------- Additional Comments From [EMAIL PROTECTED] 2004-08-09 13:42 ------- In the relatively rare case of the field being exactly the maximum length, the code can tell if there was truncation by computing the SHA-1 hash and seeing if it matches the stored hash. In that case, displaying "..." after the maximum length would be unambiguously different from any real string that ends in "..." Given what Justin said about the token size being limited, I have no objections to this design, including truncating the stored tokens to 128 bytes and defining the field in the schema as VARCHAR(128). ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.
