A method and system to effectively and easily handle email-attachments.
Original Publication Date: 2005-Jan-05
Included in the Prior Art Database: 2005-Jan-05
Quite often in our day to day job-related activities we are required to send a number of attachments via email. For example take the case of project deliverables, documentation and other related stuffs. We send these via email attachments to - say a contact person who is at a remote location or to the architect etc and also copy (Cc or Bcc) it to persons in the management . The primary motive of copying the mail (with attachments) to management people is to keep them informed on the current status of the project, to notify them that the respective deadlines has been honored and the project has been successfully completed. However all the people copied in the mail(management people) may not be interested in the attachments. Just an indication that the work is completed and the deadline was honored is more than enough. Sending attachments to all the people is a waste of both mail storage space and network bandwidth. An easy and obvious solution to this is to compose two separate emails one for the persons to whom the attachment needs to be sent and another for those who are interested in knowing the status. But this has one serious drawback. The management people don?t have any concrete proof that the email has indeed been sent to the concerned person/s. This can be taken care if one of the management people sends an email to the concerned person/s and confirm it. But how to decide who will send this mail? If only one management person is involved then no problem, but in normal circumstances the number of management persons involved is more than one. This can result in unnecessary delays and confusions. The solution described here handles the above mentioned problem in a very simple, easy and effective way. All that is required is a slight modification in the way present day email clients send the encoded mail contents to the SMTP server.An important advantage of this method is that appropriate changes are required in the email clients only. No changes are required in the email servers. Also no changes are required in the defined communication standards for email communication.