Re: [Nmh-workers] 128 byte field name limit in NAMESZ breaks scan(1)

[David Levine]

I've noticed this, too.  Glad that you tracked it down,
thanks :-)

I don't see any problem with your fix.  It behaves properly
for me and valgrind is happy with it.

How about 512 instead of 192?  The only downside would be
higher memory usage, but I don't expect that's an issue
here.

David


Mark wrote:

> Messages with very long envelope "From" lines break scan(1). This
> behavior happens with nmh 1.3 and 1.2.
> 
> These messages are typically from mailing lists (Yahoo groups, in
> particular ).  The "Subject" field in the scan listing is displayed
> as just an asterisk (*) .
> 
> When I run scan, I get errors like:
> 
> -----------------------------------------------------------------
> scan: field name "From SRS0=+Q5m=2Z=returns.groups.yahoo.com=sentto-xxxxxxxx
> address@hidden" excee
> ds 127 bytes
> ??Format error (message 1764) in component 1
> 1764+ 10/17*
> scan: field name "From SRS0=+Q5m=2Z=returns.groups.yahoo.com=sentto-xxxxxxxx
> address@hidden" excee
> ds 127 bytes
> ??Format error (message 1765) in component 1
> -----------------------------------------------------------------
> 
> The warning comes from sbr/m_getfld.c, which uses the value of
> NAMESZ (set to 128 in h/mh.h).
> 
> 
> I've increased NAMESZ to 192, which fixes scan(1), and nothing seems
> to have blown up...but I'd appreciate some guidance on whether this
> is the correct solution and if there are unforeseen side-effects.
> 
> 
> Thanks,
> 
> Mark

______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________