LISTSERV has never supported the PRINT  format; it is treated like PUNCH.
I regret to  say that there is  no clear definition of  what PRINT format
means - different virtual printer  types have different line lengths, and
with a virtual 3800  I can print "lines" of up to 32k.  I did not want to
support something which  could allow users to complain that  this or that
file is only  152 bytes wide and their networking  software can accept it
as a  print file, so  I make the change  and then someone  complains that
their networking software  won't accept more than 132.  Said another way,
you have  two types  of file  formats, "RAWnn" (where  nn is  the maximum
number of  columns) and "ENCODEDxx"  (where xx identifies  the particular
format). NETDATA, DISK, CARD and LPUNCH  are ENCODED formats and can send
you any  type of file (provided  you can receive RAW80  decks). RAWnn can
only send files up to nn bytes long,  and I really don't see the point of
arguing over the maximum  value of nn that your site or  the network as a
whole can  support. Everybody supports  RAW80, which is fine  for "normal
text" given  that most terminals display  80 columns, if you  want to get
other files the best  is to use an ENCODED format  which will support any
file, and "safely". Increasing the value  of nn only decreases the amount
of files you can't receive, and what do you do with those which are still
too wide?
 
  Eric