Re: [Fwd: failure notice]

[Jonathan Larmour <jlarmour@redhat.com>]

Jason Molenda wrote:
> 
> On Wed, Aug 30, 2000 at 03:36:22PM -0400, Chris Faylor wrote:
> 
> > I looked at the script and I can see why it does fail on two Cc: lines.
> > I don't see any obvious way to fix this.  Are two Cc: lines even legal in
> > a header? 

RFC822 sez about header fields:

    This specification permits multiple  occurrences  of  most
    fields.   Except  as  noted,  their  interpretation is not
    specified here, and their use is discouraged.

So it is frowned upon, but not illegal.

> Especially when the first line ends with a comma?

RFC822 #2.7 says that null elements are allowed, and therefore permits
trailing commas. But I've looked and this isn't the cause of the problem
anyway.
 
> I don't know if it's legal, but it got delivered.  If it were me,
> I'd probably say "Don't do that" - this is the first report I've
> ever seen of someone sending out a msg like that.  But if Jonathan
> thinks it's important enough, he can always dig in to it himself.
> 
> To fix it, I'd probably add some code to count the number of To: and Cc:
> lines in the headers, and then loop over them somehow.

Looking at check-for-listname.sh (thanks for the pointer Crash), the
relevant line is:
if cat $TMPFILE | sed -n '/^[Cc][Cc]: /,/^[a-zA-Z]/p' | sed '$d' |
   egrep -i "$VALID_LISTNAME" >/dev/null 2>&1                     

If the "sed '$d' |" is removed, it works correctly on this mail. I can't
see any reason for the "sed '$d'" to be there. Is there one? If not, I'll
just remove it.

Jifl
-- 
Red Hat, 35 Cambridge Place, Cambridge, UK. CB2 1NS  Tel: +44 (1223) 728762
"Plan to be spontaneous tomorrow."  ||  These opinions are all my own fault