ietf-nntp E-mail address field of LIST ACTIVE.TIMES

[Charles Lindsey]

In <ylzoaj56wz.fsf at windlord.stanford.edu> Russ Allbery <rra at stanford.edu> writes:


>Clive D W Feather <clive at demon.net> writes:

>> I think the address should be any valid form that is acceptable to email
>> software; um, probably RFC 2821 or 2822 answers this and we should just
>> include a reference. So the brackets are optional, and we should have
>> some examples with and some without.

>> However, can the addresses include spaces and comments ? Things like:
>>     [S] misc.test 987654321 Clive Feather <clive at demon.net>
>>     [S] misc.test 987654321 clive at demon.net (This is a comment)

Yes, that is the current behaviour of Cnews. Examples from my own system:

local.foo 993236816 news at clerew
uk.local.essx 993349296 Iain Bowen as Control <control at usenet.org.uk>

>Both of those suggestions have the same problem, namely that the e-mail
>address field would no longer be a single field if you were splitting on
>spaces.  ("this has a space"@stanford.edu is a valid RFC 2822 e-mail
>address.)

But who wants to split it anyway? It is the last field of the line, so you
take the rest of the line. Anyway, is there ever any need to parse this? I
thought that field was just for humans to read.

-- 
Charles H. Lindsey ---------At Home, doing my own thing------------------------
Tel: +44 161 436 6131 Fax: +44 161 436 6133   Web: http://www.cs.man.ac.uk/~chl
Email: chl at clw.cs.man.ac.uk      Snail: 5 Clerewood Ave, CHEADLE, SK8 3JU, U.K.
PGP: 2C15F1A9      Fingerprint: 73 6D C2 51 93 A0 01 E7 65 E8 64 7E 14 A4 AB A5