It sounds like your goal is to track the delivery of email throughout your org.
in reply to Re^2: document tracking in perl
in thread document tracking in perl
In this case, a programming project is perhaps not so much what you have as much as a design problem with regards to your email infrastructure. You should look into topics like "delivery status notification", "return receipt", etc. Of course, Perl would probably be suitable for any glue code you'd need for this.
On the other hand, you could write a CGI in Perl that one would use to send these kinds of documents; it would present a form with fields for the department, particular recipients, and the paths(s) of the documents. However, in my experience people will think this is a clunky solution because it would disrupt the normal flow of sending what really just amounts to an email.
One last suggestion: if the org had standardized on an email client then you might be able to add a feature to it, or extend it, to allow an interface to your tracking system. This may or may not be easier than trying to retrofit your email infrastructure for tracking attachment flow.