3764 - Omit malformed References from outgoing news messages

Status: NEW

(MailNews Core :: Composition, defect)

Description

[Phil Peterson]

This is another problem brought up by the Good Netkeeping Seal of Approval
evaluation (see URL above).

When building the References header for outgoing news messages, we're supposed
to find invalid elements in the References list and drop them on the floor. The
requirement seems to be that the msg-id have the form <stuff@stuff>

Comment 1

[Phil Peterson]

JF, is this more a compose bug, or more a news bug (for sspitzer)?

Comment 2

[Phil Peterson]

M8

Comment 3

[Jean-Francois Ducarroz]

reaasign to rhp

Comment 4

[rhp (gone)]

Bumping out for now...

Seth: I think the issue is this:

       7e   Fails to omit `broken' Message-IDs.

How can you tell if its invalid or not?

Bumping way out...this is fine tuning.

- rhp

Comment 5

[lchiang]

I believe this is cross platform?  I'm going to change platform/OS from PC/WinNT
to All.

Comment 6

[sol]

I don't think this needs to be fixed for PR1

Comment 7

[Karen Huang]

Change QA Contact to me since it's my feature now.

Comment 8

[scottputterman]

reassigning to ducarroz

Comment 9

[Garth Wallace]

The gnksa.org website contains a small perl script that checks for malformed
references. It may be a useful reference. http://www.gnksa.org/restrict-refs.pl

Comment 10

[Garth Wallace]

That Perl script contains three different methods of weeding out bad references
(the first two are commented out):

Relatively permissive:
@refs = grep {/^<.+>$/} split /\s+/, $refs;

Relatively strict:
@refs = grep {/^<[^<>\@\s]+\@\S+\.\S+>$/} split /\s+/, $refs;

Very strict (RFC 1036bis):
@refs = grep {/^<[^<>!,;:\\\@\"\s]+\@\S+\.\S+>$/} split /\s+/, $refs;

Comment 11

[Jean-Francois Ducarroz]

Accepting

Comment 12

[Karen Huang]

Composition -> Sheela, Ccing Stephen since this is for news.

Comment 13

[Joshua Cranmer [:jcranmer]]

unassigning this bug since assignee hasn't touched it 6.5 years.

Comment 14

[Bruno Rohée]

The NetNews RFC got revised since, what is needed now is conformance with https://www.rfc-editor.org/rfc/rfc5536#section-3.2.10 that did take in account GNSKA.