• Designed to function in most desktop laser and inkjet printers
• Easy to set up and create professional looking labels
• Durable polyester label stock
• Self laminating wrap around design
• Available in US letter sheet size of 8.5" x 11" inches
• Clear polyester with white print-on areas
• Polyester rated for 0°F to 275°F for indoor and outdoor applications

ViewVC is a browser interface for CVS and Subversion version control repositories. It generates templatized HTML to present navigable directory, revision, and change log listings. It can display specific versions of files as well as diffs between those versions. Basically, ViewVC provides the bulk of the report-like functionality you expect out of your version control tool, but much more prettily than the average textual command-line program output.

Here are some of the additional features of ViewVC:

• Support for filesystem-accessible CVS and Subversion repositories
• Individually configurable virtual host support
• Line-based annotation/blame display
• Revision graph capabilities (CVS only)
• Syntax highlighting support
• Commit metadata query facilities
• Template-driven output generation
• Colorized, side-by-side differences
• Tarball generation (by tag for CVS, by revision for Subversion)
• Localization support based on the Accept-Language request header
• Ability to run either as CGI script or as a standalone server
• Regexp-based file searching
• INI-like configuration file (as opposed to requiring actual code tweaks)

Bounce Address Tag Validation (BATV) provides a mechanism for assessing the validity of an email's envelope return (bounce) address. It permits the original submitter of a message to sign the SMTP MailFrom address. This enables detection of invalid bounce addresses.

Wikipedia Excerpt

The basic idea is to send all e-mail with a return address that includes a timestamp and a cryptographic token that can not be forged. Any e-mail that is returned as a bounce without a valid signature can then be rejected. E-mail that is being bounced back should have an empty (null) return address so that bounces are never created for a bounce and therefore you can't get messages bouncing back and forth forever.