Re: A request, and a question

From	Keith Thompson <Keith.S.Thompson+u@gmail.com>
Newsgroups	comp.lang.c
Subject	Re: A request, and a question
Date	2024-01-30 13:06 -0800
Organization	None to speak of
Message-ID	<87h6iu4jke.fsf@nosuchdomain.example.com> (permalink)
References	(1 earlier) <ACClDmHp8lLCxWc1B@bongo-ra.co> <up9ve1$roj9$1@dont-email.me> <20240129214606.542@kylheku.com> <87jznr5mk6.fsf@nosuchdomain.example.com> <20240130123802.569@kylheku.com>

Show all headers | View raw

Kaz Kylheku <433-929-6894@kylheku.com> writes:
> On 2024-01-30, Keith Thompson <Keith.S.Thompson+u@gmail.com> wrote:
>> Kaz Kylheku <433-929-6894@kylheku.com> writes:
>>> On 2024-01-30, James Kuyper <jameskuyper@alumni.caltech.edu> wrote:
>>>> Those links don't work for me. They are interpreted as mailto:// links,
>>>> and the link itself says not to mail them. I don't know what to do with
>>>> them, and neither do Thunderbird or (when I'm using Google Groups)
>>>> Firefox or Chrome.
>>>
>>> You have to find the feature in your NNTP client which retrieves a
>>> Usenet article by Message-ID, and paste that into its UI, possibly after
>>> manually removing the delimiting angle brackets.
>>
>> The angle brackets are actually part of the Message-ID.  (Some software
>> might let them be omitted.)
>
> If true, that is surprising; but it doesn't sound right. The angle brackets are
> just a delimiter used when the ID appears in headers, similarly to brackets
> around e-mail addresses.
>
> Indeed, RFC 2392:
>
>      Notes: In Internet mail messages, the addr-spec in a Content-ID
>      [MIME] or Message-ID [822] header is enclosed in angle brackets
>      (<>).   [Section 2. The MID and CID Url Schemes]
>
> Elsewhere in the document, the grammar doesn't mention the angle
> brackets.
>
> An NNTP client should definitely accept a Message ID without the angle
> brackets. To be user-friendly, it should strip them if they are present.
> This is similar to accepting e-mail addresses with or without
> angle brackets. you can compose a message to foo@example.com or
> to Foo Bar <foo@example.com>, and the latter should be accepted
> even without the display name.

RFC 2822 defines the internet message format.

The grammar for a message-id header line is:

    message-id      =       "Message-ID:" msg-id CRLF

msg-id is defined as:

    msg-id          =       [CFWS] "<" id-left "@" id-right ">" [CFWS]

("CFWS" refers to comments and foldable white space).

So yes, the angle brackets are officially part of the message-id.

If I'm reading this correctly, given:

    Message-ID: <foo@example.com>

the space before the '<' is also part of the msg-id.  I don't know
whether that was intended, but I don't think it's relevant to the
current discussion.

-- 
Keith Thompson (The_Other_Keith) Keith.S.Thompson+u@gmail.com
Working, but not speaking, for Medtronic
void Void(void) { Void(); } /* The recursive call of the void */

Back to comp.lang.c | Previous | Next — Previous in thread | Next in thread | Find similar

Thread

A request, and a question Tim Rentsch <tr.17687@z991.linuxsc.com> - 2024-01-28 12:13 -0800
  Re: A request, and a question Spiros Bousbouras <spibou@gmail.com> - 2024-01-28 21:17 +0000
    Re: A request, and a question Tim Rentsch <tr.17687@z991.linuxsc.com> - 2024-01-29 11:36 -0800
    Re: A request, and a question John McCue <jmccue@qball.jmcunx.com> - 2024-01-29 21:49 +0000
      Re: A request, and a question Michael S <already5chosen@yahoo.com> - 2024-01-30 14:59 +0200
      Re: A request, and a question Spiros Bousbouras <spibou@gmail.com> - 2024-01-30 16:47 +0000
    Re: A request, and a question James Kuyper <jameskuyper@alumni.caltech.edu> - 2024-01-29 23:54 -0500
      Re: A request, and a question Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-01-29 21:19 -0800
        Re: A request, and a question Paul <nospam@needed.invalid> - 2024-01-30 00:45 -0500
        Re: A request, and a question Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-01-30 12:49 -0800
      Re: A request, and a question Kaz Kylheku <433-929-6894@kylheku.com> - 2024-01-30 05:48 +0000
        Re: A request, and a question Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-01-29 23:04 -0800
          Re: A request, and a question Kaz Kylheku <433-929-6894@kylheku.com> - 2024-01-30 20:50 +0000
            Re: A request, and a question Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-01-30 13:06 -0800
              Re: A request, and a question Kaz Kylheku <433-929-6894@kylheku.com> - 2024-01-30 21:12 +0000
                Re: A request, and a question Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-01-30 13:44 -0800
                Re: A request, and a question Richard Damon <richard@damon-family.org> - 2024-02-03 09:17 -0500
                Re: A request, and a question Kaz Kylheku <433-929-6894@kylheku.com> - 2024-02-03 18:28 +0000
      Re: A request, and a question David Brown <david.brown@hesbynett.no> - 2024-01-30 09:54 +0100
        Re: A request, and a question mjos_examine <m6502x64@gmail.com> - 2024-01-30 09:53 -0500
          Re: A request, and a question Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2024-01-30 12:32 -0800
            Re: A request, and a question mjos_examine <m6502x64@gmail.com> - 2024-01-30 16:41 -0500
        Re: A request, and a question Spiros Bousbouras <spibou@gmail.com> - 2024-01-30 16:24 +0000
      Re: A request, and a question tTh <tth@none.invalid> - 2024-01-30 11:14 +0100
      Re: A request, and a question Tim Rentsch <tr.17687@z991.linuxsc.com> - 2024-02-03 11:25 -0800
  Re: A request, and a question Lawrence D'Oliveiro <ldo@nz.invalid> - 2024-01-29 00:26 +0000
    Re: A request, and a question Anthony Cuozzo <anthony@cuozzo.us> - 2024-01-28 23:57 -0500
      Re: A request, and a question Tim Rentsch <tr.17687@z991.linuxsc.com> - 2024-01-29 19:31 -0800
    Re: A request, and a question Tim Rentsch <tr.17687@z991.linuxsc.com> - 2024-01-29 11:45 -0800

csiph-web