job-originating-user-name not working suddenly?

[Brett Ussher]

I set the following option on two of my queues:

job-originating-user-name-default=<username>

and it worked like a charm.  However, all of the sudden my print jobs don't seem to be going out to the printer with the username I defined.  CUPS is logging that it did use the correct username, however when I used wireshark to watch the traffic going to the printer, the packets show two instances where the wrong username (which is the one I'm logged in with on my linux system) was sent with the job.  The first packet seems to announce a job to the printer server I'm printing to.  The packet states the filename of what I'm printing and my linux username.  The next instance is inside the postscript sent to the print server.  It has a line "%%For:(username)" where username is, once again, my linux account.  I need it it to use the username that I defined with job-originating-user-name, why isn't it doing this all of the sudden?

Thanks for any help you can offer,

Brett