[14588] in Athena Bugs

home help back first fref pref prev next nref lref last post

sgi 8.0F: scan

daemon@ATHENA.MIT.EDU (Jacob Morzinski)
Fri Aug 23 17:17:08 1996

To: bugs@MIT.EDU
Date: Fri, 23 Aug 1996 17:17:04 EDT
From: "Jacob Morzinski" <jmorzins@MIT.EDU>

System name:		w20-575-82
Type and version:	IP22 8.0F
Display type:		NG1



[[ I not sure if there's anything you can actually _do_ about this
   bug, but I figured I'd report it anyway, just so you have a
   record of it.  Press the 'd' key now...  :-)  ]]



What were you trying to do?
	scan a piece of mail with a mangled From: heaer.

What's wrong:
	Scan cannot understand the From: header at all.  If you have
	chosen the right scan -format, you can get scan to
	segmentation fault.

What should have happened:
	Scan ought not to die, because every time it dies it kills
	my 'inc' process, and I can't get at the rest of my mail.
	(Well, actually, I did, by doing an 'inc -form scan.default')

Please describe any relevant documentation references:

A mangled message that reproduces this behavior is:
-----------------------------------------------------------------
	Newsgroups: news.answers
	From: Catherine Northcutt <Temp.User.\<kidney1@heart.med.uth.tmc.edu
	Subject: First Day of School
	Date: 23 Aug 1996 19:24:29 GMT
	Message-Id: <4vl0hd$f0p@oac2.hsc.uth.tmc.edu>
	
	Message text.
-----------------------------------------------------------------

/usr/athena/etc/scan.default is:
-----------------------------------------------------------------
%; NOTE: This file is supplied for reference only; it shows the default
%;	format string (for non-UK sites) which was compiled into "scan".
%;	See the source file "h/scansbr.h" for details.
%4(msg)%<(cur)+%| %>%<{replied}-%?{encrypted}E%| %>\
%02(mon{date})/%02(mday{date})%<{date} %|*%>\
%<(mymbox{from})%<{to}To:%14(friendly{to})%>%>%<(zero)%17(friendly{from})%>  \
%{subject}%<{body}<<%{body}>>%>
-----------------------------------------------------------------

Scanning with this formfile works fine ("scan -form scan.default").
If I change the sixth line, to use the function "(proper{from})"
instead of the function "(friendly{from})", then scan dies.

Ideally, the scan program shouldn't be so choosy about which
functions you are permitted to apply to mangled headers.  (*sigh*)

-- 
 Jacob Morzinski                                jmorzins@mit.edu

home help back first fref pref prev next nref lref last post