[cups.general] NDPS supplied LPR jobs always autodetected as

[Helge Blischke]

Andrew Steven Dixon wrote:
> 
> Hi!
> 
> I am trying to funnel print jobs from a Netware 5.1 NDPS setup into a
> CUPS server, using lpr protocol (Reason: Cutting down on the number of
> client driver types needed). For some reason, the CUPS server always
> assumes vnd.cups/raw even if the job is *DEFINITELY* postscript (from
> LaserWriter v23 or MS Publisher Color Printer/Imagesetter driver). The
> most interesting part is that re-submitting the data file with lpr
> straight from the cups spool directory (temporarily set PreserveJobFiles
> Yes) results in the job being *correctly* graded application/postscript.
> 
> Yes, I double checked that no banner insertion mechanism or windows side
> print preprocessor is at play here.
> 
> Submission of same job from same machine (win xp) with the same driver
> directly via internet printing also works correctly....!
> 
> If anybody knows in which direction to look... ancient LPD protocol
> format options? Ghost in the machine....?
> 
> About only thing that is special about NDPS lpd protocol is long
> usernames, like .joe_johnson.apple.tree (with the leading dot).
> 
> TIAFAH,
> 

I think NDPS usually assumes that the print jobs contain "print-ready"
jobs
for the respective printer. Thus the control file statements probably
will specify
"l" (literal) as data type, which is translated into the CUPS "raw"
option by
cups-lpd.
To settle this issue, try to launch cups-lpd with the option 
	-o document-format=application/octet-stream
on the command line (see the manal page for further details) do force
the autodetection
of the print file type.

Helge




-- 
Helge Blischke
Softwareentwicklung
SRZ Berlin | Firmengruppe besscom
http://www.srz.de