Can it also made it possible to add an extra filter to this daemon to select only those requests with a certain location?
In fact, this can be a search for a string in the body of the mail.
"Why?
The building for our book storage has 3 levels (I1, I2 and I3) and every level has its own printer for the print request.
By making the print daemon to do the selection, you can fine-tune printouts.
At this moment this is done by outlook. Rules are looking for a string in the body and forward the mail to another mail address that prints the request.
As a result, you have always unwanted extra header information coming from outlook.
The print daemon just prints the body of the mail. And that is what you want, nothing more."
Can it also made it possible to add an extra filter to this daemon to select only those requests with a certain location? In fact, this can be a search for a string in the body of the mail.
"Why? The building for our book storage has 3 levels (I1, I2 and I3) and every level has its own printer for the print request. By making the print daemon to do the selection, you can fine-tune printouts. At this moment this is done by outlook. Rules are looking for a string in the body and forward the mail to another mail address that prints the request. As a result, you have always unwanted extra header information coming from outlook. The print daemon just prints the body of the mail. And that is what you want, nothing more."