New major features:

• Admin alerts. Administrators can now choose to be notified via email (or SMS if you have an email-SMS gateway) on the following events:
  • Printer errors - be notified when a printer goes into error. For example when there is a paper jam or the printer is out of toner. This feature allows administrators to be aware of issues faster, rather than waiting for an irate user

This release contains the following changes:

• Add improved support for authenticating using Windows Active Directory UPN user names (e.g. [email protected]).
• Improve reports to display a friendly message when the report contains no data.
• Fixed problem importing users/groups from some LDAP servers.
• Fixed problem using cards for authentication in the release station when the card-number trailer character is not

This release contains the following changes:

• Add a new feature to display the environmental impact of each user's printing. This is intended to encourage users to reduce their printing. It displays the number of trees consumed, amount of CO2 produced and how much energy used.
• Add a "Rates" page to the end-user

This release contains the following changes:

• Added the ability to schedule reports. This feature allows reports to be automatically generated and emailed to a list of recipients. More information is available in the user manual.
• The report naming scheme has been revised to ensure they are consistent and give a good idea as to what they will look

This release contains the following changes:

• Fixed problem with database upgrade that would occur if upgrading from a version prior to 7.1 (Build 4550).

This release contains the following changes:

• Added a printer filter to deny print jobs based on the number of copies.
• Fixed an issue where some common errors such as network timeouts or corrupt print jobs would be reported many times. This could cause a delay in the processing of print jobs, and in some situations crash the application server.
• Greatly improved memory usage when running PaperCut with PostgreSQL. This was a workaround