Description of problem:

We just recently upgraded to 6.. Our print server hasn't been updated to 6, and is still using an old LPRng print server at this point.  However, all of our clients are using CUPS.  If a student types "lpr -P<printer>" hits enter, then hits CTRL-D, the job stays in the queue:

prt is ready
Rank    Owner   Job     File(s)                         Total Size
1st     bob     5       (stdin)                         0 bytes

The job is never spooled to the server.

cups error log displays this error twice per minute forever:

E [15/Sep/2011:04:37:13 -0400] [Job 28] Remote host did not accept data file (2)

The queue is setup as with "ErrorPolicy abort-job".

Version-Release number of selected component (if applicable):

1:1.4.2-35.el6_0.1

Steps to Reproduce:
1. lpr
2. CTRL-D
 
Expected results:

Since "ErrorPolicy abort-job" is set, job should disappear from queue and be gone forever.

Additional info:

I know that CUPS probably won't do this for CUPS run queues, but the fact that it knows there is an error, abort-job is set, and it doesn't abort seems like there is an error present.