@Frankie The screenshot shows the SavaPage Proxy Print Dialog that connects to a CUPS queue. So, at this point a PS Driver for Windows is irrelevant.
Hi @rijkr ,
Thanks for the reply. How can I get the A3 icon shows on the web app when I select the printer? Thanks!
lpstat no show any erro and I can see A3 in the printer ppd.
*DefaultPageSize: A3
*PageSize A3: “<</PageSize[841.889763779528 1190.551181102362]>>setpagedevice”
*DefaultPageRegion: A3
*PageRegion A3: “<</PageSize[841.889763779528 1190.551181102362]>>setpagedevice”
*DefaultImageableArea: A3
*DefaultPaperDimension: A3
*ImageableArea A3: “11.622047244094 11.622047244094 830.267716535433 1178.929133858268”
*PaperDimension A3: “841.889763779528 1190.551181102362”
And I also add the Mapping PPD to IPP
*VENMedia media
*VENMedia VENA3 iso_a3_297x420mm
*VENMedia *VENA4 iso_a4_210x297mm
*VENMedia VENA5 iso_a5_148x210mm
*VENMedia VENA6 iso_a6_105x148mm
*VENMediaSource media-source
*VENMediaSource *VENAuto auto
*VENMediaSource VENMain main
*VENMediaSource VENTop top
*VENMediaSource VENMiddle middle
*VENMediaSource VENBottom bottom
*VENMediaSource VENBypassTray by-pass-tray
*VENMediaSource VENManual manual
*VENMediaSource VENTray1 tray-1
*VENMediaSource VENTray1 tray-2
*VENMediaSource VENTray1 tray-3
*VENMediaSource VENTray1 tray-4
*VENMediaSource VENTray1 tray-5
I update paper size in every tray to A3 but I still can not get the A3 icon shows.
@Frankie, your PPD to IPP mapping is not correct. You should map the PPD keyword, in your case PageSize to IPP, like this:
*PageSize media
*PageSize A3 iso_a3_297x420mm
*PageSize *A4 iso_a4_210x297mm
*PageSize A5 iso_a5_148x210mm
*PageSize A6 iso_a6_105x148mm
This .ppde file shows how to do this, it also includes other mappings you might need.
Hi @rijkr
As my test in these days, I find out only Windows IPP class driver supports printing to A3. But Windows IPP class driver doesn’t support duplex printing.
My case is ,
I set up the Savapage in ubuntu and created two printers with ipp://printerIP/ipp
I create a print queue IT with two printers.
I install a printer in Win 10, the target is http://SavaPage:8631/printers/IT , the driver is Windows IPP class driver.
With the Windows IPP class driver, A3 or A4 is automactically recogized. But duplex(two sided) setting from Excel/Word can not be tranferred to Savapage with the Windows IPP class driver.
May I have some idea how I can improve the Windows printing experience so that the user print preference can be transferred to SavaPage? Which means what ever user selects in his/her print dialog, the selected parameter can be translated and overwrite the Savapage proxy printer options. Thanks!
Hi @rijkr
I can find the following in the help document session K.6.1, fit-to-page is applied to Fast Print Mode by default. My question is that, how I can change this default option? I don’t want to have fit-to-page applied by default for the Fast Print mode. Thanks!
K.6.1. Fast Print A4 and Letter to Single Tray
For Fast Mode printers with a single tray holding A4 media, PPDE can be used to configure an extra (virtual) IPP media-source entry for Letter, that maps to the same A4 tray. The two media sources will be visible in the Proxy Printer Edit dialog, so A4 and Letter media size can be assigned to them, and both A4 and Letter jobs will be Fast Print candidates. With an SPExtra rule the Letter media is substituted with A4. And, since fit-to-page print-scaling is applied for Fast Mode printing by default, the Letter job will correctly scale to A4.
@Frankie The latest release candidate supports Restricting Standard Options for print-scaling. So, add the following lines in the .ppde file linked to your Fast Print Mode Proxy Printer.
*print-scaling print-scaling
*print-scaling none none
In this way print scaling will be disabled.
@rijkr Good day,
May I ask where to add the web-login.ttp.apikey and web-login.ttp.enable configuration properly ? I read doc C.2. Web Services but seems not too much info.
I didn’t find any in the sample config files and I tried to add something like
web-login.ttp.enable=Y
web-login.ttp.apikey=MY-API-KEY
in /opt/savapage/server/server.properties, after restart the savapage I ran a test script to check if I can get one-time token. However I can see log
WARN OneTimeAuthHandler:91 - TTP login key missing (user “user-name” from ipipip) [jetty-threadpool-50]
I’m not sure it’s my python mistake or config wrong. I am a bit worried because I don’t see any uncommented line about web-login in /opt/savapage/server/server.properties. It would be great if you could take a look, thanks a lot.
@eraaaa Welcome to SavaPage. I have added an explanation to the User Manual. See C.2.1.1. onetime-auth.createToken . Does this answer your question?
Thanks sir, that works perfectly for me. A big step to my follow-me print plan.
Can’t seem to create a new topic, so I have to post here. Having a lot of trouble with setting up Savapage at the moment in one specific area: page sizes.
The context is a Savapage server. A Windows print server, with Savapage added as a local printer (I have tried both HP Unviersal PS Driver and Xerox Global, both of which appear to be highly recommended for this sort of application and I set the PS flavour to portability / archive for better compatibility). The Windows print server shares Savapage to our Windows clients.
I can upload an A3 PDF to the Savapage web UI and it will import as A3 size and print perfectly well. However when I print to the shared Savapage printer, the web UI shows it as an A4 page.
Interestingly, when I fast release the print job to my A3 and A4 capable printer, it prints on an A3 page (but A4 sized, in the middle, not scaled up).
If I print the earlier mentioned uploaded A3 document from the web UI, it prints A3 sized, on A3 paper. Perfect. So it really seems that the specific problem lies in Windows sending the correct PS to Savapage.
Any ideas?
Gave up on “generic drivers.” @rijkr this might interest you (but still isn’t a full solution to my problem):
As described here Adobe colaborate with MS to create a Windows Postscript driver, what finaly included the PSCRIPT5.DLL as a part of MS-Windows instalation. You can now use this correct PS driver in MS-Windows-10 by Create a new printer; Local or Network manualy; Choose existing or Create a new Port; Vendor: Generic, Printer: MS Publisher Color Printer (or Imagesetter - for some other features); give it the name and finish.
To complete the job, you have to make a changes in the folder: C:\Windows\System32\spool\drivers\x64\3\ where you have to delete both files: MSGENCOL.PPD and MSGENCOL.BPD, and then rename your myprinter.ppd file to MSGENCOL.PPD and move it in the folder.
This allowed me to add the Savapage PPD. Using this super generic driver, I am able to print A3 and A4 (and probably whatever else) correctly. However, the PPD hack only works on the print server. Clients connecting seem to get the default driver without the updated PPD. So extra features like duplex printing are not possible.
A side note to the Xerox and HP drivers: the quality is absolutely abysmal. So far, this MS Publisher printer driver with and without the PPD hack is true to quality, page size, etc. but is missing the Duplex printing feature. Surely there’s a simple solution here?
@sduze Welcome to SavaPage. Thanks for sharing your (partial) solution. As you mentioned in your previous message “it really seems that the specific problem lies in Windows sending the correct PS to Savapage”. This corresponds with your observation that “Clients connecting seem to get the default driver without the updated PPD”. Unfortunately, this issue is beyond the scope of SavaPage.
Thanks rijkr, I was actually just hoping you might have some up to date recommendation on what “generic” PS print driver to use on Windows. Which I guess technically isn’t within the scope of SavaPage either, but perhaps you have some experience with it.
Regardless, I will give my feedback here in case someone else in future searches it (or in case you decide to expand your scope a little bit).
HP Universal Print Driver - quality sucks, at least with the Kyocera printers that we have, and document size does not work. All other major features do work (duplex, paper size). I blame the driver for this (not the printer) because Archive mode should theoretically have broad PS compatibility.
Xerox Global Print Driver - exactly the same as above. To clarify what I mean by document size and paper size: if I, from Windows, print a page in A3 scaled to fill the full size: SavaPage will receive an A4 document, and the printer will release an A3 paper with an A4 sized document in the middle and huge margins. I expect this behavior would be the same with all non-A4 paper sizes. It matches the comment in the other thread about “the only driver that can print A4 not letter” (I assume that person had their default size as letter, whereas I have mine as A4).
All other Windows-pre-installed manufacturer PS emulator drivers that I’ve tested (and there’s been various, but I didn’t track exactly which) seem to have the same problems as above.
TOSHIBA e-STUDIO Colour PS3 mini driver - from the recommendation in that thread. Quality is great, documents arrive to SavaPage with the correct size, and print as expected. I think duplex printing works. Driver is very basic (and I don’t like that print size is hidden under advanced features), but it is technically the best so far.
If I find a better featured simple driver or if you have a better recommendation that doesn’t have the failings of the above, then I’ll update this post with the info for future reference.
@sduze Thanks. Please report any findings at Which PostScript driver to use in Windows?
I have SavaPage installed as a test for my school and I would really like to use it. I have 1.6.0-rc build 20250903 installed. (It looks so amazing).
I am experiencing a couple issues-
I cannot get anything to “print into” savapage queue. I am testing with the IP-based option to correspond the print to the account, which leads to my second issue.
I cannot get Google LDAP to connect. I am getting an error: User synchronization error: [LDAP: error code 49 - Incorrect password]. I have followed the instructions in the documentation as well as I am able to get the LDAP key and password set up and the authentication credentials.
I can upload files into the queue and print them once they are there. Works great!
Any hints or troubleshooting documentation on getting printing to work would be appreciated. I have followed the instructions on setting up a printer in Windows and I have met with no success.
Is there a way to make the Mail Print queue print automatically?
SavaPage v1.7.0 – AD domain username parsing issue when using Fast Printer (regression)
After upgrading SavaPage from v1.6.0 to v1.7.0 (latest), Active Directory users are no longer recognized when printing via Fast Printer, although the configuration has not changed.
Example log messages:
User “KEK\tekir.test” print on queue “/” from 192.168.0.100 denied.
Reason: user unkown Reason: user unkown jetty-threadpool-153
Environment details:
Printing method: Fast Printer
AD domain: KEK
Incoming username format: KEK\username
Configuration:
internal-users.username-prefix = KEK
Despite the domain being correctly defined in internal-users.username-prefix, usernames in the DOMAIN\username format are not parsed in v1.7.0 when Fast Printer is used, and users are treated as unknown.
The same setup works without any issue in v1.6.0.
Due to production impact, we had to rollback to v1.6.0.
This strongly looks like a regression in v1.7.0 related to Fast Printer and domain\username parsing.
Has anyone experienced this issue or found a workaround for v1.7.0?
Any feedback would be appreciated.
1 Like
@GACS Welcome to SavaPage. Can you be more specific on “print automatically”? There is a Fast Print Mode scenario that may provide a solution.
Thank you for your reply!
We are looking to set one of the Savapage printers to print any PDF/Text attachment that come to a specific email address, with out any user interaction. The person would just send the email and it would print. The webapp work flow does work, but we do not always have staff available to assist.
@GACS SavaPage complies to the European General Data Protection Regulation (GDPR). It is difficult to guarantee privacy when a printout rolls out of the printer without the appropriate person being present. A document left unattended on a printer tray can easily be considered a violation of the GDPR. Bottom line: your print scenario is not supported.