On Tue, 8 Jul 2003, henrik wrote: > Of course, the thought occurred to me too after I had sent the message. > Still, I think it should be parsed as an E: field, because the error is so > easily spotted by the user, and you only have to insert a space to correct > it, e.g. > E: |
or E :| Anyway, the standard should define explicitly whether E:| is to be interpreted as a header or as a field, or in other words what the relative priority of the ":" and the ":|" tokens is. Furthermore, I think E: as a header should be deprecated in favour of [E:] . Groeten, Irwin Oppenheim [EMAIL PROTECTED] ~~~* Chazzanut Online: http://www.joods.nl/~chazzanut/ To subscribe/unsubscribe, point your browser to: http://www.tullochgorm.com/lists.html
