JP6288199B2 - Mail processing program, mail processing apparatus and mail processing method - Google Patents

Description

  This case relates to a mail processing program, a mail processing apparatus, and a mail processing method.

  Conventionally, when searching for a desired mail from a large number of mails, the user needs to perform operations such as scrolling the screen to search for the desired mail, or searching for the desired mail by keyword search of the text or sender. there were. However, when searching for a desired mail by scrolling the screen, it takes time and effort, and it may take a long time to search. Further, when searching for a keyword, it is necessary to select an appropriate keyword and input a keyword, which is troublesome. In addition, when an appropriate keyword cannot be selected, it is not possible to properly narrow down mails, and it may take a long time to search for a desired mail.

  Recently, an e-mail system that classifies received e-mails based on a database including organization information is known (see, for example, Patent Document 1).

Japanese Patent Laid-Open No. 5-260084

  However, in the technique disclosed in Patent Document 1 and the like, received e-mails are sorted into folders, so that a user who wants to separately use a display of unsorted status (such as reception order display) and a sorted status display. May be inconvenient.

  In one aspect, an object of the present invention is to provide an easy-to-use mail processing program, mail processing apparatus, and mail processing method.

The mail processing program described in this specification includes a process for automatically acquiring personnel information from a personnel information storage unit that accepts an update to new personnel information for personnel information before update, and a transmitted mail stored in the storage unit. Or refer to the personnel information before the update by the process of automatically acquiring the determination of at least one of the section, department of the mail, or outside the mail when displaying the status of the received mail. Or a mail processing program that causes a computer to execute processing performed by referring to the updated personnel information .

The mail processing apparatus described in this specification includes an acquisition unit that automatically acquires personnel information from a personnel information storage unit that accepts an update to new personnel information for personnel information before the update, and a transmission unit that has been stored in the storage unit Refer to the personnel information before the update by the process of automatically acquiring the judgment of at least one of the section, department of the mail, or outside the mail when displaying the status of the mail or the received mail. Or a determination unit that is performed with reference to the updated personnel information .

The mail processing method described in this specification includes a process for automatically acquiring personnel information from a personnel information storage unit that accepts an update to new personnel information for personnel information before the update, and a transmitted email stored in the storage unit. Or refer to the personnel information before the update by the process of automatically acquiring the determination of at least one of the section, department of the mail, or outside the mail when displaying the status of the received mail. Or a process performed with reference to the updated personnel information, is executed by the computer.

  The mail processing program, the mail processing apparatus, and the mail processing method described in the present embodiment have an effect of improving user convenience.

1 is a diagram schematically showing a configuration of an electronic mail system according to an embodiment. FIG. FIG. 2A is a diagram illustrating the hardware configuration of the server, and FIG. 2B is a diagram illustrating the hardware configuration of the client. It is a functional block diagram of a server and a client. It is a figure which shows an example of the data structure of personnel affairs DB (old). It is a figure which shows an example of the data structure of personnel affairs DB (present). It is a figure which shows an example of the data structure of mail DB. It is a figure which shows an example of the data structure of attribute setting DB. It is a figure which shows an example of the data structure of the dispatch time system DB. It is a figure which shows an example of the data structure of receiving DB classified by attribute (at the time of transmission). It is a figure which shows an example of the data structure of receiving DB classified by attribute (present). It is a flowchart (the 1) which shows a series of processes of a mail process part. It is a flowchart (the 2) which shows a series of processes of a mail process part. It is a flowchart (the 3) which shows a series of processes of a mail process part. FIG. 14A is a diagram illustrating an example of a user ID / password input screen, and FIG. 14B is a diagram illustrating an example of an authentication error screen. It is a figure which shows an example of a received mail list display screen. It is a flowchart which shows the specific process of step S28 of FIG. It is a figure which shows an example of an attribute setting screen (initial screen). FIG. 18A is a diagram showing a supervisor subordinate setting screen (kuroda@x.jp), and FIG. 18B is a diagram showing a supervisor subordinate setting screen (satou@x.jp). It is a flowchart which shows the specific process of step S30 of FIG. FIG. 5 is a diagram (part 1) illustrating an example of a display screen according to attributes. It is FIG. (1) which shows an example of a mail list display screen. It is a figure which shows an example of a message display screen. It is a flowchart which shows the specific process of step S56 of FIG. 12, and step S88 of FIG. It is a figure which shows an example of a message preparation screen. It is FIG. (2) which shows an example of a mail list display screen. It is FIG. (2) which shows an example of the display screen according to attribute. It is a flowchart which shows the specific process of step S54 of FIG. It is a figure which shows an example of an attribute setting screen (update screen). It is a flowchart which shows the process simultaneously processed in parallel with the process of FIGS.

  Hereinafter, an embodiment of an electronic mail system will be described in detail with reference to FIGS. FIG. 1 schematically shows an e-mail system 100 according to an embodiment.

  As shown in FIG. 1, the electronic mail system 100 of the present embodiment includes a server 10 as a mail processing device and a client 20 as a display device. The server 10 and the client 20 are connected to a network 80 such as the Internet or a LAN (Local Area Network). This e-mail system 100 exchanges e-mails between clients 20 when a user (user) performs input or operation on a WEB mail screen (provided from the server 10) displayed on a browser in the client 20. It is a system that enables

  FIG. 2A shows the hardware configuration of the server 10. As shown in FIG. 2A, the server 10 includes a CPU (Central Processing Unit) 90, a ROM (Read Only Memory) 92, a RAM (Random Access Memory) 94, and a storage unit (here, an HDD (Hard Disk Drive)). 96, a network interface 97, a portable storage medium drive 99, and the like. Each component of the server 10 is connected to a bus 98. In the server 10, the CPU 90 executes a program (including a processing program) stored in the ROM 92 or the HDD 96, or a program (including a processing program) read from the portable storage medium 91 by the portable storage medium drive 99. Thus, the function as the mail processing unit 40 shown in FIG. 3 is realized. The mail processing unit 40 has a function of generating and transmitting a screen to be displayed on the client 20 in addition to transmission / reception of electronic mail. In FIG. 3, a personnel database (database) 30 stored in the HDD 96 of the server 10, a mail DB 32, an attribute setting DB 34, a call origination DB 36, and an attribute-specific reception DB (during transmission) 38 also shows an attribute-specific reception DB (current) 39 as the latest classification information storage unit. The specific data structure of each DB 30 to 39 will be described later. In the following, electronic mail is abbreviated as “mail”.

  FIG. 2B shows the hardware configuration of the client 20. As shown in FIG. 2B, the client 20 includes a CPU 190, a ROM 192, a RAM 194, a storage unit (HDD) 196, a display unit 193, an input unit 195, a network interface 197, and a portable storage medium drive 199. Each component of the client 20 is connected to the bus 198. The display unit 193 includes a liquid crystal display and the like, and the input unit 195 includes a keyboard, a mouse, a touch panel, and the like. In the client 20, the functions as the display processing unit 50 and the input processing unit 52 illustrated in FIG. 3 are realized by the CPU 190 executing the program. In response to an instruction from the mail processing unit 40 of the server 10, the display processing unit 50 displays a screen related to mail browsing, mail creation, transmission / reception, and the like on the display unit 193 of the client 20. The input processing unit 52 receives information input by the user of the client 20 via the input unit 195 and transmits the information to the mail processing unit 40 of the server 10.

  Here, various DBs included in the server 10 will be described.

  4 and 5 show examples of the data structure of the personnel database 30. FIG. FIG. 4 shows an example of the personnel DB before update (HR DB (old)), and FIG. 5 shows an example of the updated personnel DB (HR DB (current)). The personnel DB 30 is a database that stores personnel information of persons belonging to the company. As shown in FIGS. 4 and 5, the personnel DB 30 includes “user address (ID)”, “password”, “user name”, “position”, “position flag”, “affiliation section code”, “section” It has fields of “name”, “affiliation department code”, “department name”, “affiliation headquarter code”, “headquarter name”, and “group”.

  In the “user address (ID)” field, a mail address (user ID) possessed by the user is stored. A password set by each user is stored in the “password” field. In the “user name” field, the name of the user (only in FIG. 4 and FIG. 5) is stored, and in the “position” field, the title of the user is stored. In the “title flag” field, a flag set for each title is stored. In FIG. 4 and FIG. 5, a flag is set for each position such that “0” is general, “1” is the section manager, “2” is the general manager, and “3” is the general manager. The “affiliation section code” field stores a code assigned to the section to which the user belongs, and the “section name” field stores a user such as a patent section, a design section, a trademark section, or a contract section. Stores the name of the section to which it belongs. The “Department Code” field stores the code assigned to the department to which the user belongs, and the “Department Name” field stores the name of the department to which the user belongs, such as the Intellectual Property Department or the Legal Department. Is done. In the “affiliation headquarters code” field, the code assigned to the headquarters to which the user belongs is stored, and in the “headquarter name” field, the name of the section to which the user belongs. Further, the name of the group to which the user belongs is stored in the “group” field. 4 and 5 show a state in which the user “Fuji” has been transferred from the Legal Department Contract Section to the Intellectual Property Department Patent Section due to personnel changes.

  FIG. 6 shows an example of the data structure of the mail DB 32. The mail DB 32 is a database prepared for each user, and is a database that stores mail transmitted and received by each user. As shown in FIG. 6, the mail DB includes “transmission / reception classification”, “message ID”, “sender address (user address)”, “destination”, “opening status”, “sending date / time”, “mail information”. (Subject, Body) "fields.

  The field of “reception / transmission classification” stores a classification indicating whether the mail is “received” or “sent” by the user. In the “message ID” field, a unique ID determined for each mail is stored. The field of “sender address (user address)” stores the address of the mail sender (sender). In the case of a mail whose “transmission / reception classification” field is “transmission”, the address of the user of the mail DB 32 is stored in the “sender address (user address)” field. In the “destination” field, one or a plurality of mail destination addresses are stored. Note that in the case of a mail in which the “transmission / reception classification” field is “reception”, the address stored in the “destination” field includes the address of the user of the mail DB 32. Information on whether or not the user has viewed the mail is stored in the “opening status” field. As an example, in FIG. 6, if the unsealing status is “1”, it means that it has been opened (viewed), and if the unsealing status is “0”, it means that it has not been opened (unviewed). The “date and time of sending” field stores information on the date and time of sending the mail, and the “mail information (subject, body)” field stores the subject of the mail and the text itself.

  FIG. 7 shows an example of the data structure of the attribute setting DB 34. The attribute setting DB 34 is a database that stores a result of setting how a user displays an email. As shown in FIG. 7, the attribute setting DB 34 includes “user address”, “same section”, “same part (not including same section)”, “same part (including same section)”, “boss (range)”. , “Subordinates (range)”, “All other departments”, “Other department executives”, “Other department general”, and “External” fields.

  For example, in the record whose user address is “inoue@x.jp”, the flag “1” is set in the fields of “same department”, “same department (not including same department)”, “all other departments”, and “external”. Stored. Therefore, according to the attribute setting DB 34, the user “Inoue” classifies the mail according to four attributes of “same section”, “same part (not including the same department)”, “all other departments”, and “outside”. Is displayed, it is set. In addition, since “2” is stored in the “subordinate (range)” field, the user “Inoue” sets up to two positions below the same organization as subordinates, and even with the attribute of “subordinate” If you categorize and display, you have set.

  Further, for example, in the record with the user address “yamada@x.jp”, the flag “1” is stored in the fields “same part (includes same department)”, “all other parts”, and “outside”. . Therefore, according to the attribute setting DB 34, the user “Yamada” is set to display the mail by dividing it into three attributes of “same part (including the same section)”, “all other parts”, and “external”. It will be. In addition, since “1” is stored in the fields of “supervisor (range)” and “subordinate (range)”, the user “Yamada” has a position in the hierarchy of the same organization as the supervisor, Up to a position one level below is set as a subordinate, and when the mail is divided and displayed even with the attributes of “superior” and “subordinate”, it is set.

  FIG. 8 shows an example of a data structure of the outgoing job system DB 36. The outgoing call system DB 36 is a database that stores information (relationships) between a sender (sender) and a receiver (destination) at the time when the mail is sent and received when the mail is sent and received. As shown in FIG. 8, the outgoing call system DB 36 has fields of “message ID”, “sender information”, and “receiver (destination) information”.

  In the “message ID” field, a message ID assigned when mail information is stored in the mail DB 32 is stored. The “sender information” field stores information on the organization at the time of sending the sender's mail. Specifically, the user ID of the sender, the post flag, the section code, the department code, and the head office code are input. The caller information stored in FIG. 8 can be acquired from the personnel database 30. In the “receiver (destination) information” field, information on the organization of the recipient (destination) at the time of mail transmission is stored. The specific information stored is the same as the sender information.

  FIG. 9 shows an example of the data structure of the attribute-specific reception DB (at the time of transmission) 38. The attribute-specific reception DB (during transmission) 38 is a database prepared for each user. The attribute-specific reception DB (at the time of transmission) 38 stores the number of mails received from users of each attribute (attributes set in the attribute setting DB 34) during a predetermined period. The attribute-specific reception DB (during transmission) 38 includes “start date” and “end date” that define a period, “number of cases” for each attribute set in the attribute setting DB 34 by the user, “number of unopened cases”, “Message ID” is stored. In “Number of cases”, the number of mails sent from users belonging to each attribute is entered. In “Number of unopened cases”, mails that are unopened among mails sent from users belonging to each attribute. The number of records is entered. The “message ID” stores a message ID assigned to an email transmitted from a user belonging to each attribute.

  FIG. 10 shows an example of the data structure of the attribute-specific reception DB (current) 39. The attribute-specific reception DB (current) 39 is a database prepared for each user, and the number of mails received from users belonging to each attribute (attributes set in the attribute setting DB 34) in the latest personnel DB 30. Is stored every predetermined period. The data structure of the attribute-specific reception DB (current) 39 is the same as the data structure of the attribute-specific reception DB (during transmission) 38, but the data indicated by the bold line frame in FIG. 10 is different from that in FIG. Yes.

(About processing of the mail processing unit 40)
Next, the processing of the mail processing unit 40 in the present embodiment will be described in detail along the flowcharts of FIGS. 11 to 13 with reference to other drawings as appropriate.

  In the process of FIG. 9, first, in step S <b> 10, the mail processing unit 40 stands by until a mail display request is received from the client 20. The user of the client 20 can issue a mail use request by accessing the address of the WEB mail service on the browser displayed on the display unit 193 of the client 20. The mail use request is transmitted from the input processing unit 52 of the client 20.

  When the mail processing unit 40 receives the mail use request transmitted from the input processing unit 52 (when the determination in step S10 is affirmed), the mail processing unit 40 proceeds to step S12. In step S <b> 12, the mail processing unit 40 transmits a user ID (mail address) and password input screen to the client 20. The user ID and password input screen in this case is assumed to be a screen as shown in FIG. In the client 20, the display processing unit 50 displays the received user ID and password input screen on the display unit 193.

  Next, in step S <b> 14, the mail processing unit 40 stands by until a user ID (mail address) and password are received from the client 20. When the user inputs the user ID and password on the screen of FIG. 14A and presses the “Send” button, the input processing unit 52 transmits the user ID and password to the mail processing unit 40. .

  When the user ID and password are transmitted to the mail processing unit 40 by the input processing unit 52 (when the determination in step S14 is affirmed), the process proceeds to step S16. In step S16, the mail processing unit 40 authenticates the user using the personnel database 30 (FIG. 5). That is, the mail processing unit 40 determines whether or not the combination of the input user ID (mail address) and password exists in the personnel management DB 30. Next, in step S18, the mail processing unit 40 determines whether or not the authentication is OK. If the determination here is negative, all the processes in FIGS. 11 to 13 are terminated. Note that after the determination in step S18 is denied, the mail processing unit 40 displays the authentication error screen (FIG. 14B) on the client 20 (display processing unit 50) before ending all the processes in FIGS. ) May be transmitted. In this case, the display processing unit 50 displays the screen of FIG. 14B on the display unit 193.

  On the other hand, if the determination in step S18 is affirmative, that is, if the authentication is OK, the process proceeds to step S20. In step S <b> 20, the mail processing unit 40 determines an attribute-specific reception DB (referred to as a target attribute-specific reception DB) used for processing as an attribute-specific reception DB (at the time of transmission) 38.

  Next, in step S22, the mail processing unit 40 acquires information on received mail from the user's mail DB 32, creates a received mail list screen (see FIG. 15), and transmits the data on the screen to the client 20 (display processing). Part 50). The display processing unit 50 displays the received mail list screen of FIG. 15 on the display unit 193.

  Next, when the process proceeds to step S <b> 24 in FIG. 12, the mail processing unit 40 determines whether or not a sender attribute display request is received from the client 20. When judgment here is affirmed, it transfers to step S26. It is assumed that the user of the client 20 presses a “sender attribute distribution” button on the received mail list display screen of FIG. 15 when issuing a sender attribute display request. When the user presses the button, the input processing unit 52 transmits a sender attribute display request to the mail processing unit 40.

  Upon receiving the sender attribute display request, the mail processing unit 40 proceeds to step S26 and determines whether or not the ID of the user of the client 20 is included in the attribute setting DB 34 (FIG. 7). In step S26, it can be said that the user has already determined whether or not the attribute has been set. The attribute setting refers to setting which attribute is displayed when the received mail is displayed by attribute.

  If the determination in step S26 is negative, that is, if attribute setting has not yet been performed, the process proceeds to step S28, and the mail processing unit 40 executes a subroutine for attribute registration processing. The attribute registration processing subroutine will be described below with reference to the flowchart of FIG.

(Attribute registration process)
In the process of FIG. 16, first, in step S120, the mail processing unit 40 acquires all field names other than the “user address” in the attribute setting DB 34, and displays the attribute setting screen (initial screen) (see FIG. 17). create. Then, the mail processing unit 40 transmits the created screen data to the display processing unit 50 of the client 20. In the attribute setting screen of FIG. 17, the user selects an item (attribute) included in registration (not currently set) and presses a “confirm” button to register (attribute setting). Can be done. Note that the user can select one or more attributes.

  Next, in step S122, the mail processing unit 40 waits until an attribute selection is received from the client 20, that is, until the user of the client 20 selects an attribute and presses the “OK” button. When the user presses the “OK” button on the attribute setting screen, the mail processing unit 40 proceeds to step S124, registers the user address in the attribute setting DB 34, sets the flag of the selected attribute to 1, and others Set the attribute to 0.

  Next, in step S126, the mail processing unit 40 determines whether or not the user has selected a boss or a subordinate, that is, whether or not the flag of the attribute “boss” or “subordinate” is 1. If the determination here is negative, the entire process of FIG. 16 is terminated (the process proceeds to step S30 in FIG. 12). If the determination is affirmative, the process proceeds to step S128.

  In step S128, the mail processing unit 40 creates a supervisor / subordinate setting screen (see FIG. 18A and FIG. 18B) using the contents of the personnel DB 30, and transfers the data of the screen to the client 20 ( To the display processing unit 50). In this case, the mail processing unit 40 creates a superior / subordinate setting screen based on whether or not there is a flag larger or smaller than the user's post flag in the personnel DB 30. FIG. 18A shows an example when the position of the personnel DB 30 is “general” (position flag is 0), and FIG. 18B shows the case where the position of the personnel DB 30 is “section manager” ( An example where the post flag is 1) is shown. When the display processing unit 50 acquires the data of the supervisor / subordinate setting screen, the display processing unit 50 displays the screen on the display unit 193. It should be noted that the user of the client 20 can input range information indicating how many levels above the boss and how many levels below the boss setting and subordinate setting. The input processing unit 52 transmits the information to the mail processing unit 40 when the range information is input from the user (when the “confirm” button is pressed).

  Next, in step S <b> 130, the mail processing unit 40 stands by until it receives range information of a supervisor or subordinate from the input processing unit 52. And after receiving, it transfers to step S132. In step S132, the mail processing unit 40 records a number indicating the received range in the attribute setting DB 34 as a supervisor subordinate attribute flag. In the example of the user address “kuroda@x.jp” in FIG. 7, the case where up to the second hierarchy is selected as the boss is shown.

  As described above, when the attribute registration process (S28) in FIG. 16 is completed, the mail processing unit 40 proceeds to step S30 in FIG. If the determination in step S26 in FIG. 12 is affirmative, that is, if the user attribute has already been set, the above-described subroutine processing in step S28 (processing in FIG. 16) is not executed. Then, the process proceeds to step S30.

  When the process proceeds to step S30, the mail processing unit 40 executes a subroutine of attribute-based reception DB creation processing. Hereinafter, a sub-routine for attribute-based reception DB creation processing will be described with reference to the flowchart of FIG.

(Attribute-based reception DB creation processing)
In the process of FIG. 19, first, in step S160, the mail processing unit 40 determines whether the mail is sent (sender, received) based on the contents of the outgoing call system DB 36 (FIG. 8) and the mail DB 32 (FIG. 6). Compare job codes Then, the mail processing unit 40 stores the number of mails, opening status, and message ID transmitted by the user having the attribute set in the attribute setting DB 34 (FIG. 7) in the attribute-specific reception DB (at the time of outgoing) 38 (FIG. 9). Record. Here, the mail processing unit 40 classifies the message ID based on the relationship between the sender and receiver of the mail and stores it in the attribute-specific reception DB (at the time of transmission) 38. As described above, the outgoing job system DB 36 stores the sender and receiver (destination) office codes (position flag, section code, department code, The headquarters code) is registered. The data registration in the outgoing call system DB 36 will be described in the process (mail transmission process) of FIG.

  Next, in step S162, the mail processing unit 40 compares the current job code of the sender and receiver of the mail based on the mail DB 32 and the personnel DB 30, and determines the number of attributes set in the attribute setting DB 34 and the unsealing status. Is recorded in the attribute-specific reception DB (current) 39 (FIG. 10).

  Next, in step S164, the mail processing unit 40 determines whether the boss or subordinate flag of the attribute setting DB 34 is 1 or more. If the determination here is negative, that is, if the boss and subordinate flags are 0, the entire process of FIG. 19 is terminated. On the other hand, if the determination in step S164 is affirmed, the process proceeds to step S166.

  When the process proceeds to step S166, the mail processing unit 40 acquires the supervisor subordinate range information from the attribute setting DB 34 of FIG. For example, if the user address is “inoue@x.jp”, the supervisor range = 0 and the subordinate range = 2 are acquired from the attribute setting DB 34. Next, in step S168, the mail processing unit 40 uses the mail DB 32, the position flag of the outgoing call system DB 36, the job code, and the superior / subordinate range information at the time of outgoing mail (of the sender and receiver). Extract emails in the subordinate range. Then, the mail processing unit 40 records the number of mails, opening status, and message ID transmitted by the user belonging to the superior / subordinate attribute in the attribute-specific reception DB (during outgoing) 38. For example, since the user address “inoue@x.jp” is the head of the headquarters of the quality control headquarters, the mail of the head of the quality control headquarters and the section manager is extracted, and the information of the mail is received by attribute-specific reception DB Time) 38.

  Next, in step S170, the mail processing unit 40 uses the mail DB 32 and the position flag and office code of the personnel DB 30 to extract mails of the sender / recipient range of the mail and the supervisor subordinate attribute. The number of records and the opening status are recorded in the attribute-specific reception DB (current) 39.

  By performing the processing as described above, in the attribute-specific reception DB (during outgoing) 38 (FIG. 9), the number of cases and the number of unopened cases based on the relationship between the sender and the recipient when each mail is sent. The message ID is classified. On the other hand, in the attribute-based reception DB (current) 39 (FIG. 10), the number of cases, the number of unopened cases, and the message ID are classified based on the relationship between the current sender and recipient.

  Returning to FIG. 12, after the attribute-based reception DB creation process in step S30 described above, the process proceeds to step S32. In step S32, the mail processing unit 40 creates an attribute-specific display screen (FIG. 20) using the target attribute-specific reception DB, and transmits data on the screen to the client 20 (display processing unit 50). Here, it is assumed that the attribute-specific reception DB (during outgoing call) 38 is set as the target attribute-specific reception DB (see step S20 in FIG. 11).

  On the attribute-specific display screen of FIG. 20, the total number of emails received within a predetermined period (one week), the number of emails for each sender attribute received in each period, and the number of unopened messages are shown in a band graph. Has been. Upon receiving the data on the attribute-specific display screen in FIG. 20, the display processing unit 50 displays the attribute-specific display screen on the display unit 193. Note that the user of the client 20 can select each area on the attribute-specific display screen of FIG. When the user selects any of the areas, the input processing unit 52 transmits information on the selected area to the mail processing unit 40.

  Next, in step S34, the mail processing unit 40 stands by until any area of the attribute-specific display screen is selected. And if the information from which the area was selected is received from the input process part 52, it will transfer to step S36. In step S36, the mail processing unit 40 acquires the message ID corresponding to the selected period and the selected attribute from the target attribute-specific reception DB (here, the attribute-specific reception DB (during transmission) 38). For example, when the attribute “other executives” of the period (2012/8/6 to 2012/8/12) is selected by the user, the message IDs “0011”, “0006”, “ "0005" and "0003" are acquired.

  Next, in step S38, the mail processing unit 40 acquires information corresponding to the acquired message ID from the mail DB 32, and generates a mail list display screen (FIG. 21). Note that the mail list screen in FIG. 21 is a screen that displays a mail list of the attribute “other executives” for the period 2012/8 / 6-12.

  Next, in step S40, the mail processing unit 40 transmits the data of the mail list display screen to the client 20 (display processing unit 50). The display processing unit 50 displays the mail list display screen on the display unit 193 when the data of the mail list display screen is received. In addition, when the process of step S40 is complete | finished, it transfers to step S60.

  By the way, if the determination in step S24 is negative, that is, if the “sender attribute distribution” button in FIG. 15 is not pressed by the user, the process proceeds to step S42.

  When the process proceeds to step S42, the mail processing unit 40 determines whether or not information indicating that the mail is selected by the user has been received on the received mail list screen (FIG. 15). If the determination is negative, the process proceeds to step S54. If the determination is positive, the process proceeds to step S44.

  When the process proceeds to step S44 (when any mail is selected), the mail processing unit 40 sets the opening status of the selected mail in the mail DB 32 to 1. Next, in step S46, the mail processing unit 40 determines whether or not the user ID exists in the attribute setting DB 34. When judgment here is affirmed, it transfers to step S48. In addition, the case where it transfers to step S48 means the case where receiving DBs 38 and 39 classified by attribute corresponding to a user (FIG. 9, FIG. 10) already exist.

  In step S48, the mail processing unit 40 determines the number of unopened cases including the message ID of the selected mail in the attribute-specific reception DB (current) 39 and the attribute-specific reception DB (during transmission) 38. Decrement (-1). Thereafter, the process proceeds to step S50. If the determination in step S46 is negative, that is, if the attribute-specific reception DBs 38 and 39 corresponding to the user do not yet exist, the process proceeds to step S50 without passing through step S48.

  In step S50, the mail processing unit 40 acquires information such as the subject and text of the selected mail, creates data for the message display screen (FIG. 22), and sends the data to the client 20 (display processing unit 50). To send. The display processing unit 50 displays the message display screen on the display unit 193 when the message display screen data is received. After step S50, the process proceeds to step S52.

  In step S52, the mail processing unit 40 determines whether a request for displaying a subject list is received from the input processing unit 52 of the client 20. The request for displaying the subject list is output from the input processing unit 52 when the user of the client 20 presses the “return to list” button on the message display screen of FIG.

  If the determination in step S52 is affirmative, the process returns to step S22 in FIG. 11, but if the determination is negative, the process proceeds to step S54.

  If the determination in step S52 is negative or the determination in step S42 is negative and the process proceeds to step S54, the mail processing unit 40 determines whether a mail transmission request has been received. The mail transmission request is made when the user of the client 20 presses the “Reply” button on the message display screen of FIG. 22 or when the “Mail Send” button is pressed on the received mail list display screen of FIG. The input processing unit 52 outputs.

  If the determination in step S54 is negative, the process proceeds to step S58. If the determination is affirmative, a mail transmission processing subroutine in step S56 is executed. Hereinafter, the subroutine of the mail transmission process will be described with reference to the flowchart of FIG.

(E-mail transmission process)
In the process of FIG. 23, first, in step S200, the mail processing unit 40 generates data of a message creation screen (FIG. 24) and transmits it to the client 20 (display processing unit 50). The display processing unit 50 displays a message creation screen (FIG. 24) on the display unit 193 when the data is received. If the user proceeds to step S200 after pressing the “Reply” button on the message display screen of FIG. 22, the mail processing unit 40 generates a reply message creation screen. In the case of a reply to the mail shown in FIG. 22, as the message creation screen, the user address in the sender field in FIG. 22 is entered in the address field, “Re: intelligence” is entered in the subject, and the text in FIG. Generate a message creation screen with the generated quotation entered.

  Next, in step S <b> 202, the mail processing unit 40 stands by until receiving the destination, title, text, and caller ID from the input processing unit 52. The input processing unit 52 inputs the necessary items on the screen of FIG. 24 and, when the user presses the “Send” button, the destination, subject, text, and sender ID are sent to the mail processing unit 40. To send. When this transmission is performed, the process proceeds to step S204.

  In step S204, the mail processing unit 40 generates a message ID, and records the subject and text as a record in which the transmission / reception classification of the destination mail DB 32 is “reception”.

  Next, in step S206, the mail processing unit 40 records the message ID, the subject, and the text in the transmission column of the mail DB 32 of the user (sender). Next, in step S208, the mail processing unit 40 associates the current office code of the destination, the user (sender) office code, and the message ID, and records them in the outgoing job DB 36. For example, when the message ID is “0012”, the user ID “tanaka@x.jp” and the office code of the user “Tanaka” are input as the sender information, and the user “Kuroda” is received as the receiver information. User ID “kuroda@x.jp” and job code are entered.

  Next, in step S210, the mail processing unit 40 determines whether there is a destination user ID that has transmitted the mail to the attribute setting DB 34. That is, the mail processing unit 40 determines whether or not the attribute-specific reception DB (at the time of outgoing) 38 and the attribute-specific reception DB (current) 39 corresponding to the destination user already exist. If the determination here is affirmed, the process proceeds to step S212. If the determination is negative, all the processes in FIG. 23 are terminated.

  In step S212, the mail processing unit 40 acquires an attribute-specific reception DB (at the time of transmission) 38 and an attribute-specific reception DB (current) 39 corresponding to the destination (user ID). Next, in step S214, the mail processing unit 40 increments (+1) the number corresponding to the attribute of the mail in the received attribute-specific reception DB (at the time of transmission) 38 and attribute-specific reception DB (current) 39, and the number of unopened cases. In addition, the message ID of the mail is added.

  When the process in FIG. 23 is completed as described above, the process proceeds to step S58 in FIG.

  When the process proceeds to step S58 after step S56 or after the determination in step S54 is denied, the mail processing unit 40 determines whether or not a logout request is received from the input processing unit 52. The logout request is transmitted from the input processing unit 52 to the mail processing unit 40 when the user presses the “logout” button on the screen displayed on the display unit 193. When the logout request is issued, the mail processing unit 40 ends all the processes in FIGS. 11 to 13, but if the logout request is not issued, the process returns to step S <b> 42.

  By the way, after the process of step S40 described above is performed, when the process proceeds to step S60 of FIG. 13, the mail processing unit 40 determines whether or not a mail is selected. At this stage, the mail list display screen (FIG. 21) is displayed on the display unit 193 of the client 20, and if the user selects mail on the screen of FIG. Judgment is affirmed. Thus, when the determination in step S60 is affirmed, the process proceeds to step S62.

  In step S62, the mail processing unit 40 sets the opening status of the selected mail in the mail DB 32 to 1. Next, in step S64, the mail processing unit 40 determines the number of unopened cases including the message ID of the selected mail in the attribute-specific reception DB (current) 39 and the attribute-specific reception DB (during outgoing) 38. Decrement (-1). Next, in step S66, the mail processing unit 40 acquires information such as the text of the selected mail, creates data of a message display screen (FIG. 22), and transmits it to the client 20 (display processing unit 50). The display processing unit 50 displays a message display screen on the display unit 193 when the data is received. Thereafter, the process proceeds to step S68.

  On the other hand, if the determination in step S60 is negative, the process proceeds to step S70. In step S70, the mail processing unit 40 determines whether or not the user has pressed the “forward” or “return” button on the mail list display screen of FIG. If the determination here is affirmed, the process proceeds to step S72, and the mail processing unit 40 receives the message ID of the next period or the previous period (corresponding to advance / return) of the same attribute as the target attribute reception DB (attribute The mail list display screen is created from the separate reception DB (during outgoing call) 38 or the attribute-specific reception DB (current) 39). Then, the mail processing unit 40 transmits the data of the created mail list display screen to the client 20 (display processing unit 50). If no message ID exists in the next period or the previous period (corresponding to advance / return) of the same attribute, a mail list display screen as shown in FIG. 25 is created. On the mail list display screen of FIG. 25, the message “There is no mail with the specified attribute during this period” is displayed. The display processing unit 50 displays the mail list display screen on the display unit 193 when it receives the data of the mail list display screen. After that, the process returns to step S70.

  On the other hand, when the determination in step S70 is negative (when the “forward” and “return” buttons are not pressed), the process proceeds to step S74. In step S <b> 74, the mail processing unit 40 determines whether a current attribute display request has been received from the input processing unit 52. The current attribute display request is issued when the user presses the “during / current attribute display” button in FIG. 21 or FIG. 25 or when the user presses the “current attribute display” button in FIG. The data is output from the input processing unit 52 to the mail processing unit 40. If the determination in step S74 is affirmed, the process moves to step S76, and the mail processing unit 40 sets the attribute-specific reception DB (current) 39 as the target attribute-specific reception DB, and returns to step S32 in FIG. . By executing step S32, an attribute-specific display screen based on the attribute-specific reception DB (current) 39 shown in FIG. 10 is displayed on the display unit 193 of the client 20 as shown in FIG. Will be. Thereafter, the processing after step S34 using the screen of FIG. 26 is performed.

  On the other hand, if the determination in step S74 of FIG. 13 is negative, the process proceeds to step S78.

  In step S <b> 78, the mail processing unit 40 determines whether or not an outgoing call attribute display request has been received from the input processing unit 52. The outgoing attribute display request is issued when the user presses the “current / current attribute display” button in FIG. 21 or 25 or when the user presses the “current attribute display” button in FIG. Are output from the input processing unit 52 to the mail processing unit 40. If the determination in step S78 is affirmative, the process moves to step S80, and the mail processing unit 40 sets the target attribute-specific reception DB as the attribute-specific reception DB (during transmission), and returns to step S32 in FIG.

  On the other hand, if the determination in step S78 is negative, the process proceeds to step S82. When the process proceeds to step S82, the mail processing unit 40 determines whether a setting change request has been received. The setting change request is output from the input processing unit 52 to the mail processing unit 40 when the user presses the “setting change” button on the attribute-specific display screen of FIG. 20 or FIG. If the determination in step S82 is affirmative, the process proceeds to step S84. Hereinafter, the attribute update processing subroutine of step S84 will be described with reference to the flowchart of FIG.

(Attribute update process)
In the process of FIG. 27, first, in step S220, the mail processing unit 40 creates an attribute setting screen (update screen) (see FIG. 28) using information in the attribute setting DB 34, and displays it in the display processing unit 50 of the client 20. Send to. Here, already set attributes are displayed in the right column (deleted (currently set)) of the attribute setting screen (update screen) in FIG. In the left column of FIG. 28 (registration (not currently set)), attributes that are not displayed in the right column (attributes that are not currently set) are displayed. In the attribute setting screen of FIG. 28, an item (attribute) included in registration (not currently set) can be selected and registered by pressing the “Confirm” button. In addition, an item (attribute) included in the deletion (currently set) can be selected and deleted by pressing the “confirm” button. Note that the user can select one or more attributes.

  Next, in step S222, the mail processing unit 40 waits until an attribute selection is received from the client 20, that is, until the user of the client 20 selects an attribute and presses the “OK” button. When the user presses the “confirm” button, the mail processing unit 40 proceeds to step S224 and updates the item corresponding to the user address in the attribute setting DB 34 (sets the registered attribute flag to 1 and deletes it). Set the flag of the assigned attribute to 0).

  Next, in step S226, the mail processing unit 40 determines whether there is a superior or subordinate in the item whose flag is changed from 0 to 1. If the determination here is negative, the entire process of FIG. 27 is terminated. If the determination is positive, the process proceeds to step S228.

  In step S228, the mail processing unit 40 creates a supervisor / subordinate setting screen (see FIGS. 18A and 18B) using the contents of the personnel DB 30, and the client 20 (display processing unit 50). Send to. When the display processing unit 50 acquires the data of the supervisor / subordinate setting screen, the display processing unit 50 displays the screen on the display unit 193. It should be noted that the user of the client 20 can input range information indicating how many levels above the boss and how many levels below the boss setting and subordinate setting. When the range information is input from the user, the input processing unit 52 transmits the information to the mail processing unit 40.

  Next, in step S <b> 230, the mail processing unit 40 waits until it receives range information of a supervisor or subordinate from the input processing unit 52. And after receiving, it transfers to step S232. In step S232, the mail processing unit 40 records a number indicating the received range in the attribute setting DB 34 as a supervisor subordinate attribute flag.

  As described above, when the attribute update process (S84) in FIG. 27 ends, the mail processing unit 40 proceeds to step S68 in FIG. If the determination in step S82 of FIG. 13 is negative, that is, if the setting change request is not received, the process proceeds to step S68 without executing the above-described subroutine of step S84.

  In step S68 of FIG. 13, the mail processing unit 40 determines whether or not a received mail list display request has been received. The received mail list display request is output from the input processing unit 52 to the mail processing unit 40 when the user presses the “return to list” button on the screen of FIG. 20, FIG. If the determination in step S68 is negative, the process returns to step S22 in FIG. On the other hand, if the determination in step S68 is negative, the process proceeds to step S86.

  When the process proceeds to step S86, the mail processing unit 40 determines whether a mail transmission request has been received. The mail transmission request is output from the input processing unit 52 to the mail processing unit 40 when the user presses the “Reply” button on the screen of FIG. If the determination in step S86 is affirmed, the process proceeds to step S88. If the determination is negative, the process proceeds to step S90. Note that the processing in step S88 is performed according to the flowchart of FIG. 23, as in step S56 described above. Therefore, detailed description of step S88 is omitted. After the process of step S88 is complete | finished, it transfers to step S90.

  In step S90, the mail processing unit 40 determines whether a logout request has been received. The logout request is transmitted from the input processing unit 52 to the mail processing unit 40 when the user presses the “logout” button on the screen displayed on the display unit 193. When the logout request is issued, the mail processing unit 40 ends all the processes in FIGS. 11 to 13. However, if the logout request is not issued, the process returns to step S60 (the first process in FIG. 13).

  Incidentally, the mail processing unit 40 also executes processing according to the flowchart of FIG. 29 in parallel with executing the processing of FIGS. Hereinafter, the process of FIG. 29 will be described.

  In the process of FIG. 29, first, in step S300, the mail processing unit 40 waits until the personnel DB 30 is updated. When the personnel DB 30 is updated, the process proceeds to step S302, and the mail processing unit 40 executes an attribute-based reception DB creation process using the latest personnel DB 30. In step S302, the processing of FIG. 19 excluding steps S160 and S168 is performed using the latest personnel database 30.

  As described above, by executing the processing of FIG. 29, the attribute-specific reception DB (current) 39 can be updated to correspond to the latest personnel DB 30 at the timing when the personnel DB 30 is updated.

  In the above description, the case where the received mail is classified and displayed according to the attribute of the sender has been described. However, the present invention is not limited to this, and the outgoing mail may be classified according to the attributes of the recipient and displayed by attribute according to the request from the user in the same manner as described above.

  As can be seen from the above description, the mail processing unit 40 realizes functions as a storage unit, an acquisition unit, a classification unit, and a screen generation unit.

  As described above in detail, according to the present embodiment, when the transmission of the mail from the transmission source user to the destination user is accepted, the mail information is stored in the mail DB 32 (S204). Referring to the personnel DB 30 that stores the affiliation information (employee code, etc.) of the person, the relationship between the transmission source and the destination when the mail stored in the mail DB 32 is transmitted is acquired and recorded in the outgoing time management DB 36 (S208), the message ID of the mail stored in the mail DB 32 is classified on the basis of the relationship between the transmission source and the destination stored in the outgoing time management DB 36, and recorded in the attribute-specific reception DB (at the time of outgoing) 38 (S214) In response to a browsing request from the destination user, the mail browsing screen stored in the mail DB 32 (attribute-specific display screen (transmission attribute display) (FIG. 20)) is changed to the attribute-specific reception DB. It generated based on the origination) 38, to the display processing unit 50 to execute display of the browsing screen of the display unit 193 (S32). Thereby, in this embodiment, as shown in FIG. 20, the number of receptions and the number of unopened cases can be displayed for each attribute of the sender. In addition, when the user selects an attribute, a list of corresponding mails can be displayed. Therefore, it is easy to search for a desired mail, the burden on the user can be reduced, and the work time can be shortened, so that the user's convenience can be improved. In the present embodiment, the message ID is managed (classified) for each attribute in the attribute-specific reception DB (at the time of outgoing) 38 without dividing the mail into folders for each attribute. The attribute-specific display screen of FIG. 20 and the received mail list display screen of FIG. 15 can be switched and displayed, and the usability of the user can also be improved from this point.

  Further, in the present embodiment, in the process of recording the message ID in the attribute-specific reception DB (during outgoing call) 38, the mail message ID stored in the mail DB 32 is replaced with information other than the relationship between the transmission source and the destination (this embodiment). In the form, it is further classified by the transmission date (period). Thereby, since the user can search for a desired mail based on the attribute of the sender and the transmission date and time, the search operation becomes easier. In the above description, a case where message IDs are classified based on the relationship between the transmission source and the destination and the transmission date and time (period) in the process of recording the message ID in the attribute-specific reception DB (during transmission) 38 will be described. However, it is not limited to this. For example, instead of the transmission date and time (period), the message IDs may be classified based on the transmission day of the week or the time zone in one day such as morning or afternoon. Moreover, it is good also as classifying message ID based on a sender | caller's information, for example, a man, a woman, age, an address, etc. instead of transmission date / time (period). Further, the message ID may be classified based on the date and time when a specific process is performed on the mail other than the transmission date and time.

  In the present embodiment, the latest (current) personnel DB 30 is referred to obtain the latest (current) relationship between the transmission source user and the destination user, and the mail DB 32 is based on the relationship. The message IDs of the mails stored in the mail are classified and recorded in the attribute-specific reception DB (current) 39 (S162, S170), and the mail stored in the mail DB 32 in response to a viewing request from the user. A browsing screen (attribute-specific display screen (current attribute display) (FIG. 26)) is generated based on the attribute-specific reception DB (current) 39 and displayed on the display processing unit 50 (S32). Thereby, since the attribute-specific display screen (FIG. 26) based on the current attribute can be displayed, the user can search for the mail based on the current attribute. In this case, the user does not need to remember or check the attribute of the sender at the time when the mail is received, and work efficiency can be improved.

  In the above embodiment, there may be a mail that is not included in any attribute on the attribute-specific display screen (FIGS. 20 and 26). In such a case, the number of such mails may be displayed as the attribute “others” on the attribute-specific display screen, or may not be displayed on the attribute-specific display screen.

  Note that the screens and databases described in the above embodiments are examples. In other words, the screen configuration and the data structure of the database may be variously changed. Also, with respect to the processing of the flowchart, some processing may be omitted or the order of some processing may be changed.

  The above processing functions can be realized by a computer. In that case, a program describing the processing contents of the functions that the processing apparatus should have is provided. By executing the program on a computer, the above processing functions are realized on the computer. The program describing the processing contents can be recorded on a computer-readable recording medium (except for a carrier wave).

  When the program is distributed, for example, it is sold in the form of a portable recording medium such as a DVD (Digital Versatile Disc) or a CD-ROM (Compact Disc Read Only Memory) on which the program is recorded. It is also possible to store the program in a storage device of a server computer and transfer the program from the server computer to another computer via a network.

  The computer that executes the program stores, for example, the program recorded on the portable recording medium or the program transferred from the server computer in its own storage device. Then, the computer reads the program from its own storage device and executes processing according to the program. The computer can also read the program directly from the portable recording medium and execute processing according to the program. Further, each time the program is transferred from the server computer, the computer can sequentially execute processing according to the received program.

  The above-described embodiment is an example of a preferred embodiment of the present invention. However, the present invention is not limited to this, and various modifications can be made without departing from the scope of the present invention.

In addition, the following additional remarks are disclosed regarding description of the above embodiment.
(Appendix 1) When mail is sent and received between users, the mail information is stored in the mail information storage unit together with the mail identification information,
Based on the affiliation information storage unit that stores the affiliation information of the user, obtain the relationship between the sender and the receiver when the mail stored in the mail information storage unit is transmitted and received,
The identification information of the mail stored in the mail information storage unit is classified based on the relationship between the sender and the receiver, and stored in the classification information storage unit,
In response to a browsing request from a user, a mail browsing screen stored in the mail information storage unit is generated based on the identification information of the mail classified in the classification information storage unit, and the browsing screen is displayed on the display device. A mail processing program for causing a computer to execute processing to be displayed.
(Supplementary note 2) In the process of storing in the classification information storage unit, the identification information of the mail stored in the mail information storage unit is further classified by information other than the relationship between the sender and the receiver, and the classification information is stored. The mail processing program according to appendix 1, which is stored in a section.
(Supplementary note 3) The supplementary note 2 is characterized in that the information other than the relationship between the sender and the receiver is information on a date and time when a specific process is performed on the mail stored in the mail information storage unit. Mail processing program.
(Supplementary Note 4) Based on the affiliation information storage unit in which the latest affiliation information is stored at a predetermined timing, the relationship between the sender and receiver of the mail stored in the mail information storage unit is acquired,
Based on the acquired relationship between the sender and the recipient, classify the identification information of the mail stored in the mail information storage unit, and store it in the latest classification information storage unit,
In response to a browsing request from a user, a mail browsing screen stored in the mail information storage unit is generated based on the identification information of the mail classified in the latest classification information storage unit, and the browsing screen is displayed. The mail processing program according to any one of appendices 1 to 3, which causes a computer to execute processing to be displayed on the unit.
(Additional remark 5) When transmission / reception of mail is performed between users, the mail information storage part which stores the information of the said mail with the identification information of mail,
An affiliation information storage unit for storing user affiliation information;
Based on the affiliation information storage unit, an acquisition unit for acquiring a relationship between a sender and a receiver when mail stored in the mail information storage unit is transmitted and received,
A classification unit for classifying the identification information of the mail stored in the mail information storage unit based on the relationship between the sender and the receiver acquired by the acquisition unit;
A classification information storage unit for recording a classification result by the classification unit;
In response to a browsing request from a user, a mail browsing screen stored in the mail information storage unit is generated based on the identification information of the mail classified in the classification information storage unit, and the browsing screen is displayed on the display device. A mail processing apparatus comprising: a screen generation unit to be displayed.
(Additional remark 6) The said classification | category part further classify | categorizes the identification information of the mail stored in the said mail information storage part by information other than the relationship between the said sender and a receiver, and stores it in the said classification information storage part The mail processing device according to appendix 5, which is characterized.
(Supplementary note 7) The supplementary note 6 is characterized in that the information other than the relationship between the sender and the receiver is information on a date and time when a specific process is performed on the mail stored in the mail information storage unit. Mail processing device.
(Additional remark 8) The latest which acquires the relationship between the sender | mail sender and receiver of the mail stored in the said mail information storage part based on the said affiliation information storage part in which the newest affiliation information was stored at predetermined timing An information acquisition unit;
Based on the acquired relationship between the sender and the receiver, the latest classification unit that classifies the identification information of the email stored in the email information storage unit,
A latest classification information storage unit for recording a classification result by the latest classification unit, and
The image generation unit generates a mail browsing screen stored in the mail information storage unit based on the identification information of the mail classified in the latest classification information storage unit in response to a browsing request from the user, The mail processing device according to any one of appendices 5 to 7, wherein the browsing screen is displayed on the display device.
(Additional remark 9) When transmission / reception of mail is performed between users, the process of storing the information of the said mail in a mail information storage part with the identification information of mail,
Based on the affiliation information storage unit that stores the affiliation information of the user, obtaining a relationship between the sender and the receiver when the mail stored in the mail information storage unit is transmitted and received;
Classifying the identification information of the mail stored in the mail information storage unit based on the relationship between the sender and the receiver, and recording it in the classification information storage unit;
In response to a browsing request from a user, a mail browsing screen stored in the mail information storage unit is generated based on the identification information of the mail classified in the classification information storage unit, and the browsing screen is displayed on the display device. A mail processing method, wherein the computer executes the step of displaying.
(Appendix 10)
In the step of storing in the classification information storage unit, the identification information of the mail stored in the mail information storage unit is further classified by information other than the relationship between the sender and the receiver and stored in the classification information storage unit The mail processing method according to appendix 9, characterized in that:
(Appendix 11)
The mail processing method according to appendix 10, wherein the information other than the relationship between the sender and the receiver is information on a date and time when a specific process is performed on the mail stored in the mail information storage unit. .
(Appendix 12)
At a predetermined timing, based on the affiliation information storage unit in which the latest affiliation information is stored, obtaining a relationship between the sender and receiver of the mail stored in the mail information storage unit;
Classifying the identification information of the mail stored in the mail information storage unit based on the acquired relationship between the sender and the receiver and storing it in the latest classification information storage unit;
In response to a browsing request from a user, a mail browsing screen stored in the mail information storage unit is generated based on the identification information of the mail classified in the latest classification information storage unit, and the browsing screen is displayed. The mail processing method according to any one of appendices 9 to 11, wherein the computer executes the step of displaying on the apparatus.

10 server (mail processing device)
20 Client (display device)
30 Personnel DB (Affiliation Information Storage)
32 Mail DB (Mail information storage)
38 Receiving DB by attribute (during outgoing) (classification information storage)
39 Reception DB by attribute (current) (latest classification information storage)
40 Mail processing unit (storage unit, acquisition unit, classification unit, screen generation unit)

Claims (4)

A process of automatically acquiring personnel information from a personnel information storage unit that accepts an update to new personnel information for the personnel information before the update,
Processing for automatically obtaining a determination on at least one of a mail transmission destination or a transmission source section, department, or outside the company when displaying the status of sent mail or received mail stored in the storage unit A process performed by referring to the personnel information before update by, or a process performed by referring to the personnel information after update,
Is a mail processing program that causes a computer to execute. The determination includes determination of whether the transmission destination or the transmission source of the mail is a superior , and / or determination of whether it is a subordinate .
Mail processing program according to claim 1, characterized in that. An acquisition unit that automatically acquires personnel information from a personnel information storage unit that accepts updates to new personnel information for personnel information before update,
Processing for automatically obtaining a determination on at least one of a mail transmission destination or a transmission source section, department, or outside the company when displaying the status of sent mail or received mail stored in the storage unit A determination unit that refers to the personnel information before the update by, or refers to the personnel information after the update , and
A mail processing apparatus comprising: A process of automatically acquiring personnel information from a personnel information storage unit that accepts an update to new personnel information for the personnel information before the update,
Processing for automatically obtaining a determination on at least one of a mail transmission destination or a transmission source section, department, or outside the company when displaying the status of sent mail or received mail stored in the storage unit A process performed by referring to the personnel information before update by, or a process performed by referring to the personnel information after update,
A mail processing method characterized in that the computer executes.

Images