Email processing

• US 20020091776A1
• Filed: 10/16/2001
• Published: 07/11/2002
• Est. Priority Date: 10/16/2000
• Status: Abandoned Application

• Current Assignee: Mail Morph Limited
• Original Assignee: Mail Morph Limited
• Inventors: Donnelly, William, De Leastar, Eamonn, Nolan, Brendan, Conheady, Gerald, Kennedy, Lorcan
• Application Number:
  US09/977,262
• Publication Number:
  US 20020091776A1
• Time in Patent Office: Days
• US Class Current: 709/206
• CPC Class Codes: G06Q 10/107 Computer-aided management of electronic mailing [e-mailing]
• CPC Class Codes: H04L 51/066 Format adaptation, e.g. format conversion or compression

Abstract

An email received from an email server (2) is delivered to a mail store controller (3) from which it is then stored in a mail store memory (5) with attachments in another storage location (6). The server controller (4) prepares a header for the email classifying the email having regard to what information it can immediately read. The first or initial header is sent to a router (15). The router (15) reads the header and sends it firstly to a profile controller (12) where the header is read and a profile database (13) is consulted which would have been inputted by management with various rules. Then, the header may be augmented with some instruction such as the need to copy another individual with the email and sent back to the router (15) where it is then sent to various conversion controllers (10, 12, 14) where various conversion operations take place. Each time a conversion operation takes place on an attachment, this is carried out by removing the attachment from the attachment store (6), carrying out the operation on the attachment, altering the header to record the particular operation has taken place and then sending the attachment back for storage. A similar process may take place on the other constituents of the email such as the message body or the subject. When all the necessary operations have been carried out in the email to make it understandable by the recipient, the header is delivered from the router (15) back to the server controller (4) which then retrieves the message, attachments and header and delivers to the mail store controller (3) and in turn back out to the email server (2) for subsequent delivery to the recipient.

Claims

1. A method in an email processing assembly having a mail server, processors, processor engines for processing an email into formats suitable for the recipient and storage means associated therewith for the distribution of an email to an intended recipient in a predetermined format suitable for the recipient, the email having a message and an initial header comprising email data comprising:

routing data including originating data, address data identifying the intended recipient;

constituent data indicating the nature of the email; and

content data comprising reference to the components of the email message itself, the email being received in a mail server in which the following steps were carried out, prior to receiving the email, to prepare tet processing assembly to carry out the method;

storing in a recipients database the formats suitable for each recipient as processing requirements;

storing in an instruction list database the instructions necessary to mute the email through the various processing engines;

storing in a management rules database data specifying the manner in which the email will be processed and distributed and comprising, on an email being received;

taking the initial header;

searching the management rules database;

retrieving appropriate rules having regard to the initial header;

adding the rules to the initial header to form a system header;

retrieving the processing requirements for the recipients;

adding the processing requirements to the system header;

carrying out any necessary processing of the email having regard to the system header; and

distributing the email having regard to the system header.

2. A method as claimed in claim 1, in which initially there is provided:

a classification database comprising a plurality of classifications of emails having regard to their attributes; and

at least one processing route with suitable processing instructions associated therewith allocated to each classification to provide a classification instruction list.

3. A method as claimed in claim 2, in which on receiving the email, the email is classified having regard to those attributes which can be ascertained from the header and the email message itself and the classification is added to the system header to control the manner in which the necessary processing requirements are carried out.

4. A method as claimed in claim 2, in which on receiving an email, the email is classified having regard to those attributes which can be ascertained from the header and the email message itself and if the full attributes of the email cannot be ascertained, an interim classification is allocated to identify the necessary processing requirements to ascertain the attributes of the email, the interim classification is added to the system header, the necessary processing is carried out having regard to the interim classification, the email is reclassified having regard to the attributes which can now be ascertained from the header and the email and the new classification is added to provide the system header and thus those necessary processing requirements.

5. A method as claimed in claim 1, in which on receiving an email, the email is classified having regard to those attributes which can be ascertained from the header and the email message itself and if the full attributes of the email cannot be ascertained to provide a full system header:

an interim classification is allocated to identify the necessary processing requirements to ascertain the attributes of the email;

the interim classification is added to the system header;

the necessary processing is carried out having regard to the interim classification;

the email is reclassified having regard to the attributes which can now be ascertained from the header and the email;

the classification is added to the initial header; and

the management rules database is then searched and the system header is provided.

6. A method as claimed in claim 2, in which on an email being received:

the email is accepted from the mail server;

the email is copied to a mail store memory;

the email is immediately transmitted in accordance with the header;

the method is carried out by retrieving the stared email from the mail store memory and the email is distributed in accordance with the method including substituting, where necessary, this email for the original email transmitted.

7. A method as claimed in claim 2, comprising:

accepting the email from the mail server in a mail store memory;

allocating the system header;

storing the email message with the system header in at least one unique boation in a mail store database and then carrying out any necessary processing of the email;

reading the system header;

retrieving the appropriate instruction from the classification database;

sending an instruction to carry out the operation on the message;

retrieving the message from the mail store database;

carrying out the operation on the message;

entering a record of the completion of the instruction in the header to provide a revised system header;

storing the email in the mail store; and

reading the revised system header and if the email is suitable for sending to the intended recipient, transmitting the email in accordance with the routing data in the system header.

8. A method as claimed in claim 2, in which the classification is chosen from one or more of:

single recipient with no attachment,

single recipient with multiple attachments,

single recipient with compressed attachments,

single recipient with encrypted attachments,

multiple recipients with no attachments,

multiple recipients with multiple attachments,

multiple recipients with compressed attachments,

multiple recipients with encrypted attachments,

the size of the email message,

the size of any attachments,

known encryption algorithm;

externally originating email,

internally originating email, and

urgency marking.

9. A method as claimed in claim 2, in which when the classification allocated to an email requires the carrying out of more than one instruction, the instructions are carried out in a predetermined order, the system header being updated each time an instruction is carried out to provide a new system header.

10. A method as claimed in claim 2, in which, on carrying out the instruction or the last of the instructions, the email is not suitable for sending:

the header is read again;

a new classification is allocated to the email;

a new system header is prepared from the new classification and the routing data; and

then the operations required by the new system header are carried out.

11. A method as claimed in claim 2, in which, on retrieving the instruction from the classification instruction list

the instruction is stored in a processors routing database as a queue for a processor engine chosen to carry out the operation in response to the instruction;

the processor engine accesses the instruction;

the message is retrieved from the mail store database;

the processor engine carries out the operation on the message; and

the revised system header is returned to the routing database for further routing of the email.

12. A method as claimed in claim 2, in which the preparation of the system header includes allocating a priority to the email.

13. A method as claimed in claim 2, in which, on an instruction requiring a specific operation to be carried out for which there is more than one processor or more than a number of processors capable of carrying out the instruction, the header is read and optimum choice of the processors is made.

14. A method as claimed in claim 2, in which:

there is provided a processor resource database in which is contained all the processor engines for carrying out a particular instruction listed singly and in combination as individual processor engines;

a system resource usage is listed for each processor engine;

a processing time for the instruction to be carried out is listed for each processor engine; and

on an instruction requiring a specific operation to be carried out for which there is more than one processor engine or more than a number of processor engines capable of carrying out the instruction, the header is read and optimum choice of the processors is made.

15. A method as claimed in claim 2, in which on transmitting the email, the identifier of the sender is stored together with the instructions carried out for transmittal between sender and recipient and on the subsequent sending of an email to the original sender, the instructions are retrieved and used to reformat the outgoing email for ease of receipt by the original sender.

16. A method as claimed in claim 1, in which on an email being received:

the email is accepted from the mail server;

the email is copied to a mail store memory;

the email is immediately transmitted in accordance with the header;

the method is carried out by retrieving the stored email from the mail store memory and the email is distributed in accordance with the method including substituting, where necessary, this email for the original email transmitted.

17. A method as claimed in claim 16, in which on receiving the email, the email is classified having regard to those attributes which can be ascertained from the header and the email message itself and the classification is added to the system header to control the manner in which the necessary processing requirements are carried out.

18. A method as claimed in claim 16, in which on receiving an email, the email is classified having regard to those attribute which can be ascertained from the header and the email message itself and if the full attributes of the email cannot be ascertained, an interim classification is allocated to identify the necessary processing requirements to ascertain the attributes of the email, the interim classification is added to the system header, the necessary processing is carried out having regard to the interim classification, the email is reclassified having regard to the attributes which can now be ascertained from the header and the email and the new classification is added to provide the system header and thus those necessary processing requirements.

19. A method as claimed in claim 16, in which on receiving an email, the email is classified having regard to those attributes which can be ascertained from the header and the email message itself and if the full attributes of the email cannot be ascertained to provide a full system header:

an interim classification is allocated to identity the necessary processing requirements to ascertain the attributes of the email;

the interim classification is added to the system header;

the necessary processing is carried out having regard to the interim classification;

the email is re-classified having regard to the attributes which can now be ascertained from the header and the email;

the classification is added to the initial header; and

the management rules database is then searched and the system header is provided.

20. A method as claimed in claim 16, in which on an email being received:

the email is accepted from the mail server;

the email is copied to a mail store memory;

the email is immediately transmitted in accordance with the header;

the method is carried out by retrieving the stored email from the mail store memory and the email is distributed in accordance with the method including substituting, where necessary, this email for the original email transmitted.

22. A method as claimed in claim 16, comprising:

accepting the email from the mail server in a mail store memory;

allocating the system header;

storing the email message with the system header in at least one unique location in a mail store database and then carrying out any necessary processing of the email;

reading the system header;

retrieving the appropriate instruction from the classification database;

sending an instruction to carry out the operation on the message;

retrieving the message from the mail store database;

carrying out the operation on the message;

entering a record of the completion of the instruction in the header to provide a revised system header;

storing the email in the mail store; and

reading the revised system header and if the email is suitable for sending to the intended recipient, transmitting the email in accordance the routing data in the system header.

23. A method as claimed in claim 16, in which when the classification allocated to an email requires the carrying out of more than one instruction, the instructions are carried out in a predetermined order, the system header being updated each time an instruction is carried out to provide a new system header.

24. A method as claimed in claim 16, in which, on carrying out be instruction or the last of the instructions, the email is not suitable for sending:

the header is read again;

a new classification is allocated to the email;

a new system header is prepared from the new classification and the routing data; and

then the operations required by the new system header are carried out.

25. A method as claimed in claim 16, in which initially there is provided:

a classification database comprising a plurality of classifications of emails having regard to their attributes; and

at least one processing operation with suitable processing instructions associated therewith allocated to each classification to provide a classification instruction list and in which on retrieving the instruction from the classification instruction list;

the instruction is stored in a processors routing database as a queue for a processor engine chosen to carry out the operation in response to the instruction;

the processor engine accesses the instruction;

the message is retrieved from the mail store database;

the processor engine carries out the operation on the message; and

the revised system header is returned to the routing database for further routing of the email.

26. A method as claimed in claim 16, in which the preparation of the system header includes allocating a priority to the email.

27. A method as claimed in claim 16, in which on an instruction requiring a specific operation to be carried out for which there is more than one processor or more than a number of processors capable of carrying out the instruction, the header is read and optimum choice of the processors is made.

28. A method as claimed in claim 16, in which:

there is provided a processor resource database in which is contained all the processor engines for carrying out a particular instruction listed singly and in combination as individual processor engines;

a system resource usage is listed for each processor engine;

a processing time for the instruction to be carried out is listed for each processor engine; and

on an instruction requiring a specific operation to be carried out for which there is more than one processor engine or more than a number of processor engines capable of carrying out the instruction, the header is read and optimum choice of the processors is made.

29. A method as claimed in claim 16, in which on transmitting the email, the identifier of the sender is stored together with the instructions carried out for transmittal between sender and recipient and on the subsequent sending of an email to the original sender, the instructions are retrieved and used to reformat the outgoing email for ease of receipt by the original sender.

30. A method as claimed in claim 1, in which on receiving the email, the email is classified having regard to those attributes which can be ascertained from the header and the email message itself and the classification is added to the system header to control the manner in which the necessary processing requirements are carried out.

31. A method as claimed in claim 30, in which on an email being received:

the email is accepted from the mail server;

the email is copied to a mail store memory;

the email is immediately transmitted in accordance with the header;

the method is carried out by retrieving the stored email from the mail store memory and the email is distributed in accordance with the method including substituting, where necessary, this email for the original email transmitted.

32. A method as claimed in claim 30, in which initially there is provided:

a classification database comprising a plurality of classifications of emails having regard to their attributes; and

at least one processing route with suitable processing instructions associated therewith allocated to each classification to provide a classification instruction list.

33. A method as claimed in claim 30, comprising:

accepting the email from the mail server in a mail store memory;

allocating the system header;

storing the email message with the system header in at least one unique location in a mail store database and then carrying out any necessary processing of the email;

reading the system header;

retrieving the appropriate instruction from the classification database;

sending an instruction to carry out the operation on the message;

retrieving the message from the mail store database;

carrying out the operation on the message;

entering a record of the completion of the instruction in the header to provide a revised system header;

storing the email in the mail store; and

reading the revised system header and if the email is suitable for sending to the intended recipient, transmitting the email in accordance with the routing data in the system header.

34. A method as claimed in claim 30, in which the classification is chosen from one or more of:

single recipient with no attachment,

single recipient with multiple attachments,

single recipient with compressed attachments,

single recipient with encrypted attachments,

multiple recipients with no attachments,

multiple recipients with multiple attachments,

multiple recipients with compressed attachments,

multiple recipients with encrypted attachments,

the size of the email message,

the size of any attachments,

known encryption algorithm;

externally originating email;

internally originating email, and

urgency marking.

35. A method as claimed in claim 30, in which when the classification allocated to an email requires the carrying out of more than one instruction, the instructions are carried out in a predetermined order, the system header being updated each time an instruction is carried out to provide a new system header.

36. A method as claimed in claim 30, in which, on carrying out the instruction or the last of the instructions, the email is not suitable for sending:

the header is read again;

a new classification is allocated to the email;

a new system header is prepare from the new classification and the routing data; and

then the operations required by the new system header are carried out.

37. A method as claimed in claim 30, in which, on retrieving the instruction from the classification instruction list—

the instruction is stored in a processors routing database as a queue for a processor engine chosen to carry out the operation in response to the instruction;

the processor engine accesses the instruction;

the message is retrieved from the mail store database;

the processor engine carries out the operation on the message; and

the revised system header is returned to the routing database for further routing of the email.

38. A method as claimed in claim 30, in which:

there is provided a processor resource database in which is contained all the processor engines for carrying out a particular instruction listed singly and in combination as individual processor engines;

a system resource usage is listed for each processor engine;

a processing time for the instruction to be carried out is listed for each processor engine; and

on an instruction requiring a specific operation to be carded out for which there is more than one processor engine or more than a number of processor engines capable of carrying out the instruction, the header is read and optimum choice of the processors is made.

39. A method as claimed in claim 1, in which on receiving an email, the email is classified having regard to those attributes which can be ascertained from the header and the email message itself and if the full attributes of the email cannot be ascertained, an interim classification is allocated to identify the necessary processing requirements to ascertain the attributes of the email, the interim classification is added to the system header, the necessary processing is carried out having regard to the interim classification, the email is reclassified having regard to the attributes which can now be ascertained from the header and the email and the new classification is added to provide the system header and thus those necessary processing requirements.

40. A method as claimed in claim 39, in which on an email being received:

the email is accepted from the mail server;

the email is copied to a mail store memory;

the email is immediately transmitted in accordance with the header;

the method is carried out by retrieving the stored email from the mail store memory and the email is distributed in accordance with the method including substituting, where necessary, this email for the original email transmitted.

41. A method as claimed in claim 39, in which initially there is provided:

a classification database comprising a plurality of classifications of emails having regard to heir attributes; and

at least one processing route with suitable processing instructions associated therewith allocated to each classification to provide a classification instruction list.

42. A method as claimed in claim 39, comprising:

accepting the email from the mail server in a mail store memory;

allocating the system header;

storing the email message with the system header in at least one unique location in a mail store database and then carrying out any necessary processing of the email;

reading the system header;

retrieving the appropriate instruction from the classification database;

sending an instruction to carry out the operation on the message;

retrieving the message from the mail store database;

carrying out the operation on the message;

entering a record of the completion of the instruction in the header to provide a revised system header;

storing the email in the mail store; and

reading the revised system header and if the email is suitable for sending to the intended recipient transmitting the email in accordance with the routing data in the system header.

43. A method as claimed in claim 39, in which the classification is chosen from one or more of:

single recipient with no attachment,

single recipient with multiple attachments,

single recipient with compressed attachments,

single recipient with encrypted attachments,

multiple recipients with no attachments,

multiple recipients with multiple attachments,

multiple recipients with compressed attachments,

multiple recipients with encrypted attachments,

the size of the email message,

the size of any attachments,

known encryption algorithm;

extremely originating email;

internally originating email, and

urgency marking.

44. A method as claimed in claim 39, in which when the classification allocated to an email requires the carrying out of more than one instruction, the instructions are carried out in a predetermined order, the system header being updated each time an instruction is carried out to provide a new system header.

45. A method as claimed in claim 39, in which, on carrying out the instruction or the last of the instructions, the email is not suitable for sending:

the header is read again;

a new classification is allocated to the email;

a new system header is prepared from the new classification and the routing data; and

then the operations required by the new system header are carried out.

46. A method as claimed in claim 39, in which, on retrieving the instruction from the classification instruction list:

the instruction is stored in a processors routing database as a queue for a processor engine chosen to carry out the operation in response to the instruction;

the processor engine accesses the instruction;

the message is retrieved from the mail store database;

the processor engine carries out the operation on the message; and

the revised system header is returned to the routing database for further routing of the email.

47. A method as claimed in claim 39, in which:

there is provided a processor resource database in which is confined all the processor engines for carrying out a particular instruction listed singly and in combination as individual processor engines;

a system resource usage is listed for each processor engine;

a processing time for the instruction to be carried out is listed for each processor engine; and

on an instruction requiring a specific operation to be carried out for which there is more than one processor engine or more than a number of processor engines capable of carrying out the instruction, the header is read and optimum choice of the processors is made.

48. A method as claimed in claim 1, in which on receiving an email the email is classified having regard to those attributes which can be ascertained from the header and the email message itself and if the full attributes of the email cannot be ascertained to provide a full system header:

an interim classification is allocated to identify the necessary processing requirements to ascertain the attributes of the email;

the interim classification is added to the system header;

the necessary processing is carried out having regard to the interim classification;

the email is re-classified having regard to the attributes which can now be ascertained from the header and the email;

the classification is added to the initial header; and

the management rules database is then searched and the system header is provided.

49. A method as claimed in claim 48, in which on an email being received:

the email is accepted from the mail server;

the email is copied to a mail store memory;

the email is immediately transmitted in accordance with the header;

the method is carried out by retrieving the stored email from the mail store memory and the email is distributed in accordance with the method including substituting, where necessary, this email for the original email transmitted.

50. A method as claimed in claim 48, in which initially there is provided:

a classification database comprising a plurality of classifications of emails having regard to their attributes; and

at least one processing route with suitable processing instructions associated therewith allocated to each classification to provide a classification instruction list.

51. A method as claimed in claim 48, comprising:

accepting the email from the mail server in a mail store memory;

allocating the system header;

storing the email message with the system header in at least one unique location in a mail store database and then carrying out any necessary processing of the email;

reading the system header;

retrieving the appropriate instruction from the classification database;

sending an instruction to carry out the operation on the message;

retrieving the message from the mail store database;

carrying out the operation on the message;

entering a record of the completion of the instruction in the header to provide a revised system header;

storing the email in the mail store; and

reading the revised system header and if the email is suitable for sending to the intended recipient, transmitting the email in accordance with the routing data in the system header.

52. A method as claimed in claim 48, in which initially there is provided:

a classification database comprising a plurality of classifications of emails having regard to their attributes, and

at least one processing operation with suitable processing instructions associated therewith allocated to each classification to provide a classification instruction list and in which on retrieving the instruction from the classification instruction list;

the instruction is stored in a processors routing database as a queue for a processor engine chosen to carry out the operation in response to the instruction;

the processor engine accesses the instruction;

the message is retrieved from the mail store database;

the processor engine carries out the operation on the message; and

the revised system header is returned to the routing database for further routing of the email.

53. A method as claimed in claim 48, in which the classification is chosen from one or more of:

single recipient with no attachment,

single recipient with multiple attachments,

single recipient with compressed attachments,

single recipient with encrypted attachments,

multiple recipients with no attachments,

multiple recipients with multiple attachments,

multiple recipients with compressed attachments,

multiple recipients with encrypted attachments,

the size of the email message,

the size of any attachments,

known encryption algorithm;

externally originating email;

internally originating email, and

urgency marking.

54. A method as claimed in claim 48, when the classification allocated to an email requires the carrying out of more than one instruction, the instructions are carried out in a predetermined order, the system header being updated each time an instruction is claimed out to provide a new system header.

55. A method as claimed in claim 48, in which, on carrying out the instruction or the last of the instructions the email is not suitable for sending:

the header is read again;

a new classification is allocated to the email;

a new system header is prepared from the new classification and the routing data; and

then the operations required by the new system header are carried out.

56. A method as claimed in claim 48, in which, on retrieving the instruction from the classification instruction list:

the instruction is stored in a processors routing database as a queue for a processor engine chosen to carry out he operation in response to the instruction;

the processor engine accesses the instruction;

the message is retrieved from the mail store database;

the processor engine carries out the operation on the message; and

the revised system header is returned to the routing database for further routing of the email.

57. A method as claimed in claim 48, in which:

there is provided a processor resource database in which is contained all the processor engines for carrying out a particular instruction listed singly and in combination as individual processor engines;

a system resource usage is listed for each processor engine;

a processing time for the instruction to be carried out is listed for each processor engine; and

on an instruction requiring a specific operation to be carried out for which there is more than one processor engine or more than a number of processor engines capable of carrying out the instruction, the header is read and optimum choice of the processors is made.

59. A method as claimed in claim 58, in which on receiving the email, the email is classified having regard to those attributes which can be ascertained from the header and the email message itself and the classification is added to the system header to control the manner in which the necessary processing requirements are carried out.

60. A method as claimed in claim 58, in which on receiving an email, the email is classified having regard to those atXr-2p-e-2p- which can be ascertained from the header and the email message itself and if the full attributes of the email cannot be ascertained, an interim classification is allocated to identify the necessary processing requirements to ascertain the attributes of the email, the interim classification is added to the system header, the necessary processing is carried out having regard to the interim classification, the email is reclassified having regard to the attributes which can now be ascertained from the header and the small and the new classification is added to provide the system header and thus those necessary processing requirements.

61. A method as claimed in claim 58, in which on receiving an email, the email is classified having regard to those attributes which can be ascertained from the header and the email message itself and if the full attributes of the email cannot be ascertained to provide a full system header:

an interim classification is allocated to identify the necessary processing requirements to ascertain the attributes of the email;

the interim classification is added to the system header the necessary processing is carried out having regard to the interim classification;

the email is classified having regard to the attributes which can now be ascertained from the header and the email;

the classification is added to the initial header; and

the management rules database is then searched and the system header is provided.

62. A method as claimed in claim 58, comprising:

accepting the email from the mail server in a mail store memory;

allocating the system header;

storing the email message with the system header in at least one unique location in a mail store database and then carrying out any necessary processing of the email;

reading the system header;

retrieving the appropriate instruction from the classification database;

sending an instruction to carry out the operation on the message;

retrieving the message from the mail store database;

carrying out the operation on the message;

entering a record of the completion of the instruction in the header to provide a revised system header;

storing the email in the mail store; and

reading the revised system header and it the email is suitable for sending to the intended recipient, transmitting the email in accordance with the routing data in the system header.

63. A method as claimed in claim 58, in which the classification is chosen from one or more of:

single recipient with no attachment,

single recipient with multiple attachments,

single recipient with compressed attachments,

single recipient with encrypted attachments,

multiple recipients with no attachments,

multiple recipients with multiple attachments,

multiple recipients with compressed attachments,

multiple recipients with encrypted attachments,

the size of the email message,

the size of any attachments,

known encryption algorithm;

externally originating email;

internally originating email, and

urgency marking.

64. A method as claimed in claim 58, in which:

there is provided a processor resource database in which is contained all the processor engines for carrying out a particular instruction listed singly and in combination as individual processor engines;

a system resource usage is listed for each processor engine;

a processing tine for the instruction to be carried out is listed for each processor engine; and

on an instruction requiring a specific operation to be carried out for which there is more than one processor engine or more than a number of processor engines capable of carrying out the instruction, the header is read and optimum choice of the processors is made.

65. A method as claimed in claim 58, in which when the classification allocated to an email requires the carrying out of more than one instruction, the instructions are carried out in a predetermined order, the system header being updated each time an instruction is carried out to provide a new system header.

66. A method as claimed in claim 58, in which, on carrying out the instruction or the last of the instructions, the email is not suitable for sending:

the header is read again;

a new classification is allocated to the email;

a new system header is prepared from the new classification and the routing data; and

then the operations required by the new system header are carried out.

68. A method as claimed in claim 67, in which on receiving the email, the email is classified having regard to those attributes which can be ascertained from the header and the email message itself and the classification is added to the system header to control the manner in which the necessary processing requirements are carried out.

69. A method as claimed in claim 67, in which on receiving an email, the email is classified having regard to those attributes which can be ascertained from the header and the email message itself and if the full attributes of the email cannot be ascertained, an interim classification is allocated to identify the necessary processing requirements to ascertain the attributes of tee email, the interim classification is added to the system header, the necessary processing is carried out having regard to the interim classification, the email is re classified having regard to the attributes which can now be ascertained from the header and the email and the new classification is added to provide the system header and thus those necessary processing requirements.

70. A method as claimed in claim 67, in which on receiving an email, the email is classified having regard to those attributes which can be ascertained from the header and the email message itself and if the hill attribute of the email cannot be ascertained to provide a full system header:

an interim classification is allocated to identify the necessary processing requirements to ascertain the attributes of the email;

the interim classification is added to the system header;

the necessary processing is carried out having regard to the interim classification;

the email is reclassified having regard to the attributes which can now be ascertained from the header and the email;

the classification is added to the initial header; and

the management rules database is then searched and the system header is provided.

71. A method as claimed in claim 67, comprising:

accepting the email from the mail server in a mail store memory;

allocating the system header;

storing the email message with the system header in at least one unique location in a mail store database and then carrying out any necessary processing of the email;

reading the system header;

retrieving the appropriate instruction from the classification database;

sending an instruction to carry out the operation on the message;

retrieving the message from the mail store database;

carrying out the operation on the message;

entering a record of the completion of the instruction in the header to provide a revised system header;

storing the email in the mail store; and

reading the revised system header and if the email is suitable for sending to the intended recipient, transmitting the email in accordance with the routing data in the system header.

72. A method as claimed in claim 67, in which the classification is chosen from one or more of:

single recipient with no attachment,

single recipient with multiple attachments,

single recipient with compressed attachments,

single recipient with encrypted attachments,

multiple recipients with no attachments,

multiple recipients with multiple attachments,

multiple recipients with compressed attachments,

multiple recipients with encrypted attachments,

the size of the email message,

the size of any attachments,

known encryption algorithm;

externally originating email;

internally originating email, and

urgency marking.

73. A method as claimed in claim 87, in which:

there is provided a processor resource database in which is contained all the processor engines for carrying out a particular instruction listed singly and in combination as individual processor engines;

a system resource usage is listed for each processor engine;

a processing time for the instruction to be carried out is listed for each processor engine; and

on an instruction requiring a specific operation to be carried out for which there is more than one processor engine or more than a number of processor engines capable of carrying out the instruction, the header is read and optimum choice of the processors is made.

74. A method as claimed in claim 67, in which when the classification allocated to an email requires the carrying out of more than one instruction, the instructions are carried out in a predetermined order, the system header being updated each time an instruction is carried out to provide a new system header.

75. A method as claimed in claim 67, in which, on carrying out the instruction or the last of the instructions, the email is not suitable for sending:

the header is read again;

a new classification is allocated to the email;

a new system header is prepared from the new classification and the routing data; and

then the operations required by the new system header are carried out.

82. A computer program comprising program instructions for causing one or more computers carry out the method as claimed in claim 1.

83. A computer program comprising program instructions for causing one or more computers carry out the method as claimed in claim 2.

84. A computer program comprising program instructions for causing one or more computers carry out the method as claimed in claim 16.

85. A computer program comprising program instructions for causing one or more computers carry out the method as claimed in claim 30.

86. A computer program comprising program instructions for causing one or more computers carry out the method as claimed in claim 39.

87. A computer program comprising program instructions for causing one or more computers carry out the method as claimed in claim 48.

88. A computer program comprising program instructions for causing one or more computers carry out the method as claimed in claim 56.

21. A method as claimed in claim 167 in which initially there is provided:

a classification database comprising a plurality of classifications of emails having regard to their attributes; and

at least one processing route with suitable processing instructions associated therewith allocated to each classification to provide a classification instruction list.

58. A method in an email processing assembly having a mail server, processors, processor engines for processing an email into formats suitable for the recipient and storage means associated therewith for the distribution of an email to an intended recipient in a predetermined format suitable for the recipient, the email having a message and an initial header comprising email data comprising:

routing data including originating data, address data identifying the intended recipient;

constituent data indicating the nature of the email; and

content data comprising reference to the components of the email message itself, the small being received in a mail server in which the following steps were carried out, prior to receiving the email, to prepare the processing assembly to carry out the method;

preparing a classification database comprising;

a plurality of classifications of emails having regard to their attributes; and

at least one processing operation with suitable processing instructions associated therewith allocated to each classification to provide a classification instruction list for routing the email through the processing engines;

storing in the instruction list database the instructions necessary to perform the processing from one format to another format;

storing in a recipients database the formats suitable for each recipient as recipients processing requirements;

storing in a management rules database data specifying the manner in which the email will be processed and distributed and comprising, on an email being received;

taking the initial header;

searching the management rules database;

retrieving appropriate rules having regard to the initial header;

adding the rules to the initial header to form a system header;

retrieving the processing requirements for the recipients urn the recipients database;

adding the recipients processing requirements to the system header;

carrying out any necessary processing of the email having regard to the system header by retrieving the instructions from the instructions list database; and

distributing the email having regard to the system header.

67. A method in an email processing assembly having a mail server, processors, processor engines for processing an email into formats suitable for the recipient and storage means associated therewith for the distribution of an email to an intended recipient in a predetermined format suitable for the recipient, the email having a message and an initial header comprising email data comprising:

routing data including originating data, address data identifying the intended recipient;

constituent data indicating the nature of the email; and

content data comprising reference to the components of the email message itself, the email being received in a mail server in which the following steps were carried out, prior to receiving the email, to prepare the processing assembly to carry out the method;

preparing a classification database comprising;

a plurality of classifications of emails having regard to their attributes; and

at least one processing operation with suitable processing instructions associated therewith allocated to each classification to provide a classification instruction list for routing the email through the processing engines;

storing in the instruction list database the instructions necessary to perform the processing from one format to another format;

storing in a recipients database the formats suitable for each recipient as recipients processing requirements;

storing in a management rules database data specifying the manner in which the email will be processed and distributed

and comprising, on an email being received;

the email is accepted from the mail server;

the email is copied to a mail store memory;

the email is immediately transmitted in accordance with the initial header;

retrieving the initial header;

searching the management rules database;

retrieving appropriate rules having regard to the initial header;

adding the rules to the initial header to form a system header;

retrieving the processing requirements for the recipients from the recipients database;

adding the recipients processing requirements to the system header;

retrieving the stored email from tile mail store memory;

carrying out any necessary processing of the email having regard to the system header by retrieving the instructions from the instructions list database; and

distributing the email in accordance with the system header including substituting the email where necessary for the originally distributed email.

89. A computer program comprising program instructions for causing one or more computers carry out the method as claimed in claim 67.

76. A processing system for the reception and transmittal of an email between a sender and recipient, the email comprising a message including one or more components and an initial header attached thereto, the initial header comprising email data comprising:

routing data including originating data, address data identifying the intended recipient;

constituent data indicating the nature of the email; and

content data comprising reference to the components of the email message itself, the system comprising;

a mail server capable of receiving and transmitting emails;

a plurality of processors each comprising a processor engine having means for identifying the format of a message component and for converting the format of a message component from at least one format to another;

a mail store memory for storage of an email message from the mail server;

a recipients database;

means for storing in the recipients database the formats suitable for each recipient as recipient processing requirements;

means for allocating a classification to an email having regard to the attributes of e email as obtained from its routing data, constituent data and content data;

means for storing in a classifications database the classifications;

means for allocating to each classification a routing through at least one processor means for adding recipient processing requirements to the initial header;

means for adding the classification to the header;

a management rules database;

means for storing in the management rules database management data specifying the manner in which the email will be processed and distributed;

means for adding the management data to the header; and

a router for delivering the header to one of the processors in response to the system header for delivering the email message between the mail store memory and the processor and for altering the header in response to the processing carried out by each processor.

77. A system as claimed in claim 76, in which the mail store memory comprises a separate store having a unique location for each attachment.

78. A system as claimed in claim 76, in which each processor is a separate stand alone processor connected only to the router and in which there is provided:

a database to store headers for forming a queue for each processor;

means to retrieve a component from the mail store memory for processing and to return the processed component to the mail store memory;

means to enter into the header confirmation of the processing; and

means to return the updated header to the router.

79. A system as claimed in claim 76, in which one of the processors is a profile controller and associated database for the reception of management data, the profile controller being connected to the router to after the header in response to the information in the management rules database.

80. A system as claimed in claim 76, in which the processor comprises a processor operated by a third party and the router includes means to establish a communications link with the processor.

81. A system as claimed in claim 76, in which there is provided a processor engine database in which there is listed the processor engines available for carrying out a particular processing operation both singly and in combination together with its system resource usage and means for allocating a processor engine or processor engines to carry out the particular operation having regard to the information in the database.