This may have been fixed in the latest version, but it is sufficiently obscure that it might not have been (I'm using 2.8.1rel.2 (1998))... In a recent highly obfuscated spam that I received, almost all the characters where replaced by numeric entities. These included the spaces, as  . Lynx just output the entity code! It looks like there might be a one out boundary error in the logic for deciding when to decode entities. ; To UNSUBSCRIBE: Send "unsubscribe lynx-dev" to [EMAIL PROTECTED]
- Re: lynx-dev   treated as error David Woolley
- Re: lynx-dev   treated as error Leonid Pauzner
- Re: lynx-dev   treated as error David Woolley
- Re: lynx-dev   treated as error Leonid Pauzner
