Case-insensitive parsing of <id-right> in message-IDs

Russ Allbery rra at stanford.edu
Fri Dec 25 19:11:26 UTC 2009


Julien ÉLIE <julien at trigofacile.com> writes:

> Couldn't we change the code of HashMessageID() to always return the
> case-sensitive hash and, in case the given message-ID was found to be
> case-insensitively parsed, we add a new entry to the history database
> with the case-sensitive hash, if it does not exist yet, (with the same
> information as the case-insensitive one) and we replace the
> case-insensitive entry with NULL information so that is will be expired
> the next time expire runs?

Ah, yes, that would work.

> We have to check whether that behaviour can be done every time the
> HashMessageID() is called.

It might slow us down a little bit, since we have to check both the
case-sensitive and case-insensitive hashes for every hash miss, so at some
point we'll want to stop doing it.  Hard to know when it's safe to stop,
though.

-- 
Russ Allbery (rra at stanford.edu)             <http://www.eyrie.org/~eagle/>

    Please send questions to the list rather than mailing me directly.
     <http://www.eyrie.org/~eagle/faqs/questions.html> explains why.



More information about the inn-workers mailing list