JP6583934B2 - Mail server device, mail management method, and mail management program - Google Patents

Description

[Description of related applications]
The present invention is based on a Japanese patent application: Japanese Patent Application No. 2015-240987 (filed on Dec. 10, 2015), and the entire description of the application is incorporated herein by reference.
The present invention relates to a mail server device, a mail management method, and a mail management program.

  When sending an e-mail, using the TO, CC (Carbon Copy), BCC (Blind Carbon Copy), etc., the e-mail (hereinafter referred to as “the same e-mail text”) for two or more destinations. It is common to send a “report mail”.

  Hereinafter, a process for transmitting a broadcast mail to two or more destinations will be described in detail with reference to FIGS. 2, 3, 4, and 5.

  FIG. 2 is a diagram illustrating an example of an electronic mail structure. The e-mail includes, for example, information shown in FIG. Specifically, the e-mail includes a header part and a mail text. When an attached file exists, the e-mail includes a header part, a plurality of text documents, and data that combines the attached files into one. As shown in FIG. 2A, the header part includes a transmission destination address (To, Cc, Bcc), a transmission source address (From), unique information added to each mail (message ID (Message-ID)), It includes a subject, a mail text format (Content-Type), and the like. The mail text includes the information shown in FIG. 2B and the mail contents.

  FIG. 3 shows an example of an e-mail created with the configuration shown in FIG. FIG. 3 shows an example of an electronic mail for the destinations “To: kobe@example.xxx.jp, Cc: kyoto@example.xxx.jp, Bcc: osaka@example.xxx.jp”.

  FIG. 4 is a block diagram illustrating an example of transmission / reception of an electronic mail. First, it is assumed that the user creates the mail 3100 shown in FIG. 3 using the mail software 3200 and executes the transmission process. In this case, the terminal device that controls the mail software 3200 transmits the mail 3100 to the mail server 3300 of xxx.example.am by SMTP (Simple Mail Transfer Protocol). Here, it is assumed that xxx.example.am is the domain name of the source mail server.

  The mail server 3300 of xxx.example.am has a function of determining a destination mail server (destination mail server determination function 3310 shown in FIG. 4). The destination mail server determination function 3310 analyzes the header part of the received mail and determines the destination mail server. Here, the character string following “@” of the destination mail address indicates the name of the destination mail server. For example, in the case of the electronic mail shown in FIG. 3, the character string after “@” of the destination mail address is “example.xxx.jp”. Therefore, the destination mail server determination function 3310 determines that the destination mail server is the mail server 3400 of example.xxx.jp.

  Here, as shown in FIG. 3, the mail server 3300 of xxx.example.am transmits one received mail 3100 to the mail server 3400 of example.xxx.jp.

  The mail server 3400 of example.xxx.jp receives one mail 3100 as the mail 3410. The mail server 3400 of example.xxx.jp analyzes the header part of the mail 3410. Specifically, the mail server 3400 of example.xxx.jp uses kobe@example.xxx.jp, kyoto@example.xxx.jp as character strings following “To, Cc, Bcc” in the header part of the mail 3410. Read osaka@example.xxx.jp. Here, the character string before “@” of the destination mail address is the destination mailbox name. Therefore, in the mail 3410, the mail server 3400 of example.xxx.jp determines that the destination mailboxes are the kobe mailbox 3501, the kyoto mailbox 3502, and the osaka mailbox 3503. The mail server 3400 of example.xxx.jp stores a mail 3410 as a mail 3511, a mail 3512, and a mail 3513 in the mail box 3501, the mail box 3502 of kyoto, and the mail box 3503 of osaka, respectively.

  Here, for example, it is assumed that the mail software 3600 corresponding to osaka@example.xxx.jp executes the mail reception process. In this case, the terminal device that controls the mail software 3600 transmits a mail request to the mail server 3400 of example.xxx.jp using POP3 (Post Office Protocol 3) or the like. Specifically, the terminal device that controls the mail software 3600 transmits a mail request that requests the mail server 3400 of example.xxx.jp to transmit an email of osaka@example.xxx.jp. Based on the mail request, the mail server 3400 of example.xxx.jp accesses the mail box 3503 of osaka and extracts the mail 3513. Then, the mail server 3400 of example.xxx.jp transmits the mail 3513 to the terminal device that controls the mail software 3600 using the POP3 or the like. The terminal device that controls the mail software 3600 receives the mail 3513 as the mail 3700 and stores it.

  FIG. 5 is a block diagram illustrating an example of processing stored in a mailbox when sending a broadcast mail to two or more destinations.

  For example, it is assumed that the mail server 4000 (hereinafter referred to as the mail server 4000) of a.b.c shown in FIG. An e-mail received by the mail server 4000 includes a header portion 4100, a mail body 4101, and an attached file 4102. The header portion 4100 includes destination mail addresses “1@a.b.c, 2@a.b.c”.

  The mail server 4000 stores the received mail in the 1@a.b.c mailbox 4310 and the 2@a.b.c mailbox 4410. As a result, the mail server 4000 stores the same electronic mail (received electronic mail) in the mail box 4310 of 1@a.b.c and the mail box 4410 of 2@a.b.c. Specifically, the mail server 4000 stores a header part 4300, a mail text 4301, and an attached file 4302 in a 1@a.b.c mail box 4310 and a 2@a.b.c mail box 4410. The header part 4300, the mail text 4301, and the attached file 4302 correspond to the header part 4100, the mail text 4101, and the attached file 4102 of the received mail.

  Patent Document 1 describes an electronic mail system that includes a mail transmission terminal, a mail gateway (mail GW described in Patent Document 1), a mail server, a content server, and a mail receiving terminal. The mail GW described in Patent Document 1 separates a received mail into a header part, a mail text, and attached file data. And the mail server of patent document 1 stores the electronic mail comprised including a header part and a mail text. Further, the content server described in Patent Document 1 stores data of attached files. The content server described in Patent Literature 1 manages the data of the attached file in association with the message ID.

JP 2002-073504 A

  It should be noted that the disclosure of the above prior art document is incorporated herein by reference. The following analysis has been made from the viewpoint of the present invention.

  As shown in FIGS. 4 and 5, when sending a broadcast e-mail to two or more destinations, the same e-mail (e-mail with the same data) may be stored in each destination mailbox. However, if electronic mails of the same data are stored in two or more mailboxes, the mail server manages redundant data (duplicate data). Furthermore, storing electronic data with the same data in two or more mailboxes increases the size of the stored data.

  In addition, when a capacity limit is set for electronic mail managed by the mail server, an increase in data size can be prevented. However, regarding the e-mail managed by the mail server, when the capacity limit is set, the number of e-mails to be managed (that is, stored) decreases, and the convenience for the user is lowered. For example, when a capacity limit is set for an e-mail managed by a mail server, the user needs to pay attention to the capacity of the e-mail stored in the mail server. If it exceeds the limit, new mail cannot be received.

  Here, in the technique described in Patent Document 1, each mailbox provided in the mail server stores an e-mail including a header portion and a mail text. For this reason, when sending a broadcast mail to two or more destinations, the mail server described in Patent Document 1 stores an email of the same data in two or more mailboxes. Therefore, the mail server described in Patent Document 1 manages redundant data (duplicate data).

  Accordingly, an object of the present invention is to provide a mail server device, a mail management method, and a mail management program that suppress an increase in the data size of the managed email and contribute to efficiently managing the email. To do.

According to a first aspect, a mail server device is provided. The mail server apparatus includes a mail receiving unit that receives an electronic mail.
Further, the mail server device includes a mail header decoding means for separating the received mail into shared mail information including a mail text and a header portion when the mail receiving means receives the electronic mail. The
Further, the mail server device includes a first storage area.
Further, the mail server device includes a second storage area that is different for each e-mail destination.
The mail header decoding means stores the shared mail information of the received mail in the first storage area, and stores the header portion of the received mail in the second storage area for each destination of the received mail. Store.

According to a second aspect, a mail management method is provided. The mail management method includes a step in which a mail server device configured to include a first storage area and a second storage area that differs for each e-mail destination receives the e-mail.
Further, the mail management method includes a step in which the mail server device separates the received mail into shared mail information including a mail text and a header portion.
In the separating step, the mail server device stores the shared mail information of the received mail in the first storage area, and stores the received mail in the second storage area for each destination of the received mail. Of the header portion.
This method is linked to a specific machine called an information processing apparatus that controls transmission / reception of electronic mail.

According to a third aspect, a mail management program is provided. The mail management program is a program that is executed by a computer that controls a mail server device that includes a first storage area and a second storage area that differs for each e-mail destination.
The mail management program causes the computer to execute processing for receiving electronic mail.
Further, the mail management program causes the computer to execute processing for separating received mail into shared mail information including a mail text and a header portion.
In the process of separating, the mail management program stores the shared mail information of the received mail in the first storage area, and stores the received mail in the second storage area for each destination of the received mail. The computer is caused to execute the process of storing the header part.
The mail management program can be recorded on a computer-readable storage medium. The storage medium may be non-transient such as a semiconductor memory, a hard disk, a magnetic recording medium, an optical recording medium, or the like. The present invention can also be embodied as a computer program product.

  According to each aspect, an object of the present invention is to provide a mail server device, a mail management method, and a mail management program that suppress an increase in the data size of the managed email and contribute to efficiently managing the email. To do.

It is a figure for demonstrating the outline | summary of one Embodiment. It is a figure which shows an example of the structure of an email. It is a figure which shows an example of an email. It is a block diagram which shows an example of transmission / reception of an email. It is a block diagram which shows an example of the process which stores an email in a mailbox. It is a block diagram which shows an example of the whole structure of the mail server apparatus 10 which concerns on this embodiment. 4 is a diagram illustrating a data structure of a record stored in a message ID database 400. FIG. It is a flowchart which shows an example of an operation | movement at the time of receiving an electronic mail. It is a flowchart which shows an example of an operation | movement at the time of receiving an electronic mail. It is a figure which shows an example of a record. It is a figure which shows an example of a record. It is a figure which shows an example of a record. It is a figure which shows an example of a record. It is a flowchart which shows an example of an operation | movement at the time of receiving the request | requirement of an email. It is a flowchart which shows an example of an operation | movement at the time of receiving the deletion request | requirement of an email. It is a flowchart which shows an example of an operation | movement at the time of receiving the deletion request | requirement of an email. It is a block diagram which shows an example of the whole structure of the mail server apparatus 10a which concerns on 2nd Embodiment. It is a block diagram which shows an example of the whole structure of the mail server apparatus 10b which concerns on 3rd Embodiment.

  First, an outline of an embodiment will be described with reference to FIG. Note that the reference numerals of the drawings attached to the outline are attached to the respective elements for convenience as an example for facilitating understanding, and the description of the outline is not intended to be any limitation. In each drawing, the connection line between the blocks includes both bidirectional and unidirectional. The unidirectional arrow schematically shows the main signal (data) flow and does not exclude bidirectionality.

  As described above, a mail server device that suppresses an increase in the data size of the managed e-mail and contributes to efficiently managing the e-mail is desired.

  Therefore, as an example, the mail server device 1 shown in FIG. 1 is provided. The mail server device 1 includes a mail receiving unit 2, a mail header decoding unit 3, a first storage area 4, and a second storage area 5.

  When the mail receiving means 2 receives an electronic mail, the mail header decoding means 3 separates the received mail into the shared mail information 31 including the mail text and the header portion 32. Here, the received mail includes shared mail information 61 and a header portion 62. The shared mail information may be a mail text. Alternatively, when the received mail includes an attached file, the shared mail information may be configured to include a mail text and an attached file. Note that the shared mail information 31 corresponds to the shared mail information 61 of the received mail. The header portion 32 corresponds to the header portion 62 of the received mail. The header part 32 and the header part 62 include a message ID (Identification) for identifying an electronic mail.

  The mail server device 1 may be configured to include one or more first storage areas 4. The second storage area 5 is a storage area that is different for each e-mail destination. The mail server device 1 is configured to include one or more second storage areas 5. The second storage area 5 may be configured as a mailbox for each user.

  The mail header decoding means 3 stores the received mail shared mail information 31 in the first storage area 4, and stores the received mail header part 32 in the second storage area 5 for each destination of the received mail. The shared mail information 41 shown in FIG. 1 corresponds to the shared mail information 31 shown in FIG. Moreover, the header part 51 shown in FIG. 1 shall correspond to the header part 32 shown in FIG.

  For example, it is assumed that the mail receiving means 2 receives a broadcast mail to two or more destinations. In that case, the mail header decoding means 3 stores the mail sharing information including the mail body of the received mail in the first storage area 4. Further, the mail header decoding means 3 stores the header part of the received mail in the second storage area 5 corresponding to each destination. Therefore, even when the mail server device 1 receives a broadcast mail addressed to two or more destinations, it is possible to avoid storing the same data electronic mail in two or more mailboxes. Therefore, the mail server device 1 suppresses an increase in the data size of the managed email and contributes to efficiently managing the email.

[First Embodiment]
The first embodiment will be described in more detail with reference to the drawings. In the following description, the first storage area is referred to as a shared mail storage unit. Further, the second storage area corresponds to a so-called personal mailbox. Of course, when the electronic mail does not include an attached file, the attached file is excluded in the processing described in this document. In the following description, the mail body includes character information of the mail body and an image inserted as the mail body.

  FIG. 6 is a block diagram illustrating an example of the overall configuration of the mail server device 10 according to the present embodiment.

  The mail server device 10 includes a mail receiving unit 200, a mail header decoding unit 300, a message ID database 400, a shared mail storage unit 500, a personal mailbox 600, and a mail request receiving unit 700. The

  Each component of the mail server device 10 illustrated in FIG. 6 may be configured in the same device. Alternatively, at least one of the components of the mail server device 10 illustrated in FIG. 6 may be configured in another device. In that case, you may connect with another component via networks, such as the internet. Although there are various methods for realizing the network, it is sufficient that the functions described in this document can be realized, and details thereof are not limited.

  Specifically, the mail server device 10 is realized using a communication device, a control unit (CPU (Central Processing Unit)), and a storage device included in one or more computers. The storage device is realized by a magnetic disk device, an optical disk device, a semiconductor memory, or the like. The semiconductor memory is, for example, an SSD (Solid State Drive), may use a flash memory, and may include a DRAM (Dynamic Random Access Memory). Further, the mail server device 10 may be realized by a computer program that causes one or more computers to execute each process using the hardware thereof.

  One or two or more storage devices included in the mail server device 10 include a first storage area (shared mail storage unit 500) that differs for each email message ID and a second storage area that differs for each destination of the email. (Personal mailbox 600). Furthermore, the storage device included in the mail server device 10 stores a message ID, information for specifying the storage location of the shared mail information, and information for specifying the storage location of the header portion in association with each other. Is provided. Note that shared mail storage unit 500 (first storage area), personal mailbox 600 (second storage area), and third storage area may be configured in the same storage device. Alternatively, the shared mail storage unit 500 (first storage area), the personal mailbox 600 (second storage area), and the third storage area may be configured in different storage devices.

<Mail receiving means 200>
The mail receiving means 200 is connected to a mail server different from the mail server device 10 (hereinafter referred to as “other mail server 100”) via a network such as the Internet. Specifically, the mail receiving means 200 includes a communication device that is connected to a network. Then, the mail receiving unit 200 receives an electronic mail transmitted by SMTP from the other mail server 100. Then, the mail receiving means 200 transmits the received electronic mail (hereinafter also simply referred to as “electronic mail”) to the mail header decoding means 300.

<Mail header decoding means 300>
The mail header decoding means 300 separates the e-mail into shared mail information including a mail body and a header part. Here, the shared mail information is information including at least a mail text, and may include a mail text and an attached file. That is, as shown in FIG. 6, the mail header decoding unit 300 separates the e-mail into a header part 301, a mail body 302, and an attached file 303. The mail header decoding means 300 may be realized using a CPU, for example.

  Then, the mail header decoding means 300 stores the shared mail information of the e-mail in the first storage area (shared mail storage unit 500) corresponding to the message ID of the e-mail. Further, the mail header decoding means 300 stores the header part of the email in the second storage area (personal mail box 600) for each email destination.

<Message ID database 400>
As shown in FIG. 6, the message ID database 400 stores information 401 in which a message ID, a header part, a mail text, and an attached file are associated with each other. Specifically, the message ID database 400 stores, as a record, information in which a message ID, information for specifying the storage location of the shared mail information, and information for specifying the storage location of the header portion are associated with each other. When storing two or more message IDs, the message ID database 400 includes, for each message ID, a message ID, information for specifying the storage location of the shared mail information, and information for specifying the storage location of the header part. Store in association. Note that the message ID database 400 includes a third storage area that stores one or more records.

  FIG. 7 is a diagram illustrating a data structure of a record stored in the message ID database 400.

  The information for specifying the storage location of the shared mail information is information for specifying the location of the shared mail storage unit 500. That is, the information specifying the storage location of the shared mail information is information indicating the mail text and the storage location of the attached file. For example, the information specifying the location where the shared mail information is stored may be the mail text, the file path where the attached file is stored, or the like. Here, the information for specifying the location where the shared mail information is stored may be any information that enables access to the stored mail body and attached file after storage, and the details thereof are not limited.

  The information for specifying the storage location of the header portion is information for specifying the personal mailbox 600 (hereinafter also referred to as “personal mailbox information”). For example, the personal mailbox information may be a transmission destination address (mail address indicated by To, Cc, Bcc) of the header part of the electronic mail.

  In addition, the message ID database 400 has a function of controlling records to be stored. Specifically, the message ID database 400 has a function of maintaining a state where message IDs do not exist in duplicate.

  In response to the search request from the mail request receiving means 700, the message ID database 400 extracts a record to be stored and returns it to the search request source. Further, the message ID database 400 has functions such as search, result response, information update, and information deletion.

<Shared mail storage unit 500>
As described above, the shared mail storage unit 500 is configured to include different storage areas for each message ID of the electronic mail. The shared mail storage unit 500 stores shared mail information of electronic mail. Specifically, the shared mail storage unit 500 stores a mail text 302 and an attached file 303 of an electronic mail. Furthermore, the shared mail storage unit 500 includes a storage area and has a function of executing reading and writing of information with respect to the storage area.

<Personal mailbox 600>
The personal mailbox 600 stores an e-mail header (header 301 shown in FIG. 6). Furthermore, it is assumed that the personal mailbox 600 includes a storage area and reads / writes information from / to the storage area.

  As described above, it is assumed that the personal mailbox 600 includes different storage areas for each e-mail destination. In other words, a storage area that is different for each e-mail recipient is assigned as a storage area constituting the personal mailbox.

  For example, it is assumed that an electronic mail corresponding to one message ID is an electronic mail for two or more destinations. In that case, the mail header decoding means 300 stores the header portion 301 of the e-mail in the personal mailbox 600 corresponding to each destination. Then, the mail header decoding unit 300 stores the shared mail information corresponding to the message ID, specifically, the mail text 302 of the electronic mail and the attached file 303 in the shared mail storage unit 500.

<Mail Request Accepting Unit 700>
The mail request receiving means 700 is connected to a terminal device that controls a mailer application program (hereinafter also referred to as recipient mail software 800) via a network such as the Internet. Specifically, the mail request accepting unit 700 is configured to include a communication device connected to the network. Then, the mail request accepting unit 700 receives a mail request or a mail deletion request transmitted by the recipient mail software 800 using POP3 or the like. In the following description, a mail request means a request for obtaining an e-mail header, a mail text, and an attached file. In the following description, the mail deletion request means a request to delete the header part of the received electronic mail, the mail body, and the attached file. Note that the mail receiving means 200 and the mail request accepting means 700 may be realized using the same communication device. Alternatively, the mail receiving unit 200 and the mail request receiving unit 700 may be realized using different communication devices. Further, the mail request accepting unit 700 may realize the processing described in this document using a CPU.

  Next, the mail header decoding means 300 will be described in detail.

  The mail header decoding means 300 acquires the message ID from the header part 301 of the received mail. Then, the mail header decoding unit 300 determines whether or not the acquired message ID is stored in the message ID database 400.

  It is assumed that the acquired message ID is not stored in the message ID database 400. In that case, the mail header decoding means 300 creates a record in which the message ID, the information specifying the storage location of the shared mail information, and the information specifying the second storage area (personal mailbox) are associated with each other. . Here, it is assumed that the specified personal mailbox 600 corresponds to one destination in the header portion corresponding to the acquired message ID. Then, the mail header decoding means 300 registers the created record in the message ID database 400.

On the other hand, it is assumed that the acquired message ID is stored in the message ID database 400. In that case, it means that a record corresponding to the acquired message ID is registered in the message ID database 400. Therefore, the mail header decoding unit 300 specifies a record corresponding to the acquired message ID. Then, the mail header decoding unit 300 adds information specifying the second storage area (personal mailbox) corresponding to the destination of the electronic mail to the specified record. Here, it is assumed that the specified personal mailbox 600 corresponds to another destination different from the one destination in the header portion corresponding to the message ID.

  Next, the case where the mail request receiving unit 700 receives a mail request will be described in detail.

  When receiving the mail request, the mail request accepting unit 700 acquires the header portion 301 from the second storage area (personal mailbox 600) corresponding to the mail request source. Specifically, the mail request receiving means 700 identifies a mail request source (that is, an e-mail recipient), and specifies the personal mailbox 600 to be accessed. Then, the mail request accepting unit 700 accesses the specified personal mailbox 600 and acquires the header portion 301 stored in the personal mailbox 600.

It is assumed that the mail request accepting unit 700 is accessible to the identified personal mailbox 600. Therefore, mail request receiving means 700, personal mailbox 600 if it is inaccessible is assumed to shift the personal mailbox 600 accessible. When the personal mailbox 600 is stored in a device different from the mail request receiving unit 700, the mail request receiving unit 700 performs processing such as connecting to a device in which the personal mailbox 600 is stored. Execute.

  Then, the mail request accepting unit 700 identifies the first storage area (shared mail storage unit 500) based on the acquired message ID included in the header section 301, and the shared mail information, specifically, e-mail. Mail body 302 and attached file 303 are acquired.

  Specifically, the mail request receiving unit 700 acquires (extracts) a message ID from the acquired header portion 301. Then, the mail request receiving means 700 searches the message ID database 400 using the acquired message ID as a search key, and acquires (extracts) a record. Then, the mail request accepting unit 700 obtains information for identifying the storage location (first storage area) of the shared mail information, specifically, the email body 302 and the attached file 303 from the acquired record. Acquire (extract). Then, the mail request receiving means 700 accesses the storage location of the specified shared mail information and acquires the shared mail information. That is, the mail request accepting unit 700 acquires the mail text 302 and the attached file 303 from the storage location of the specified shared mail information.

  Then, the mail request accepting unit 700 combines the acquired header portion 301 with the acquired shared mail information, specifically, the mail text 302 of the electronic mail and the attached file 303 to create an electronic mail. In the following description, the mail request receiving unit 700 also refers to the acquired header part, the acquired mail text, and the acquired attached file as a header part 701, a mail text 702, and an attached file 703, respectively.

  Then, the mail request receiving unit 700 transmits the created electronic mail to the mail request source. That is, the mail request accepting means 700 transmits the created electronic mail to a terminal device (hereinafter also referred to as “client terminal”) that controls the recipient mail software 800. For example, the mail request accepting unit 700 transmits an electronic mail including the header part 701, the mail text 702, and the attached file 703 shown in FIG. 6 to the client terminal.

  Next, the case where the mail request receiving unit 700 receives a mail deletion request will be described in detail.

  When receiving the mail deletion request, the mail request receiving unit 700 specifies the storage location of the header part and the header part to be deleted based on the mail deletion request. Specifically, the mail request receiving means 700 specifies the personal mailbox 600 that is the mail deletion request source. Then, the mail request accepting unit 700 specifies the header part 301 stored in the specified personal mailbox 600.

  Then, the mail request receiving means 700 deletes information for identifying the personal mailbox 600 to be deleted from the record of the message ID database 400 based on the message ID included in the header part to be deleted. Specifically, the mail request accepting unit 700 specifies the message ID included in the header part of each email to be deleted. Then, the mail request receiving means 700 refers to the record of the message ID database 400 and deletes the information specifying the personal mailbox 600 of the personal mailbox information recorded in the record of each specified message ID.

  Then, the mail request receiving means 700 deletes the header portion 301 stored in the specified personal mailbox 600.

  Then, the mail request receiving means 700 determines whether any information is registered in the information for specifying the personal mailbox in the personal mailbox information of the record of the message ID database 400.

  If the information specifying the personal mailbox is empty as a result of the determination, the mail request accepting unit 700 includes the shared mail information of the record of the message ID database 400, specifically, the mail text 302 of the email, The storage location of the attached file 303 is specified.

  Then, the mail request accepting unit 700 deletes the specified shared mail information, specifically, the mail body 302 and the attached file 303 of the electronic mail.

  Then, the mail request receiving unit 700 deletes the record in the message ID database 400.

  Next, the operation of the mail server device 10 according to the present embodiment will be described in detail.

<Receive mail>
First, the operation when the mail server device 10 receives an e-mail will be described in detail. In the following description, a case where the mail server device 10 receives the electronic mail shown in FIG. 3 will be exemplified and described. That is, in the following description, the message ID is “20150610123456789@xxx.example.am”, the destination is “To: kobe@example.xxx.jp, Cc: kyoto@example.xxx.jp, Bcc: osaka @ An example of receiving an e-mail “example.xxx.jp” will be described. The e-mail structure shown in FIG. 2 and the e-mail shown in FIG. 3 are examples, and the e-mail according to the present embodiment is limited to the structure shown in FIG. 2 and the e-mail shown in FIG. is not.

  FIG. 8 and FIG. 9 are flowcharts showing an example of the operation when an e-mail is received. In the initial state, it is assumed that the message ID “20150610123456789@xxx.example.am” is not registered in the message ID database 400.

  First, it is assumed that the mail receiving means 200 receives an electronic mail by SMTP (step A1 shown in FIG. 8). For example, the mail receiving means 200 receives the electronic mail shown in FIG. 3 created with the structure shown in FIG. 2 by SMTP.

  When receiving the electronic mail, the mail receiving means 200 transmits the received mail to the mail header decoding means 300 (step A2). That is, the mail receiving unit 200 transmits the received mail data to the mail header decoding unit 300.

  In step B1, the mail header decoding unit 300 receives the received mail from the mail receiving unit 200. In step B2, the mail header decoding means 300 acquires the header part of the received mail. Specifically, the mail header decoding unit 300 extracts the header part of the received mail based on the structure of the electronic mail (for example, the structure shown in FIG. 2). In step B3, the mail header decoding unit 300 extracts the message ID from the header part.

  In step B4, the mail header decoding means 300 searches for the message ID. Specifically, the mail header decoding unit 300 transmits an instruction to search for a record including the extracted message ID to the message ID database 400. In other words, the mail header decoding means 300 transmits a command for searching for a record to the message ID database 400 using the extracted message ID as a search key.

  In step C1, the message ID database 400 performs a search. Specifically, the message ID database 400 searches for a record including the message ID of the received mail, and returns the search result to the mail header decoding unit 300.

  In step B5, the mail header decoding unit 300 determines whether or not a record including the message ID that is the search key is stored in the message ID database 400.

  Here, it is assumed that the search key is the message ID “20150610123456789@xxx.example.am”. The message ID “20150610123456789@xxx.example.am” is not registered in the message ID database 400. In that case, the mail header decoding unit 300 determines that a record including the message ID that is the search key is not stored in the message ID database 400.

  When the record including the message ID that is the search key is not stored in the message ID database 400 (No branch of Step B5), the process proceeds to Step B8 shown in FIG. On the other hand, when the record including the message ID that is the search key is stored in the message ID database 400 (Yes branch of step B5), the process proceeds to step B6. The processing after step B6 will be described later.

  In step B8 shown in FIG. 9, the mail header decoding means 300 creates a new record. Specifically, the mail header decoding unit 300 transmits a command for creating a record whose message ID is a search key. For example, assume that the search key is the message ID “20150610123456789@xxx.example.am”. In that case, the mail header decoding means 300 transmits an instruction to create a record including the message ID “20150610123456789@xxx.example.am” to the message ID database 400.

  For example, as shown in FIG. 10, the message ID database 400 may create, as a record, data associating the message ID, the location of the shared mail storage unit 500, and personal mailbox information. The message ID database 400 may register the message ID “20150610123456789@xxx.example.am” in the created data (see FIG. 10). Although FIG. 10, FIG. 11, FIG. 12, and FIG. 13 show table format data, this is not intended to limit the records to the table format. The record may be information in which the message ID, the location of the shared mail storage unit 500, and the personal mailbox information are associated with each other, and the details thereof are not limited.

Then, the mail header decrypting means 300 stores the mail text and the attached file in the shared mail storage unit 500 (Step B9, Step D1). Specifically, the mail header decoding unit 300 extracts a mail text and an attached file from the e-mail based on the e-mail structure (for example, the structure shown in FIG. 2). Then, the mail header decoding unit 300 stores the extracted mail text and attached file in the shared mail storage unit 500. Here, it is assumed that the mail header decoding unit 300 stores the extracted mail text and attached file in the free area of the shared mail storage unit 500.

  In step B <b> 10, the mail header decoding unit 300 writes information specifying the location of the shared mail storage unit 500 in the message ID database 400. Specifically, the mail header decoding unit 300 transmits a command to write information for specifying the location of the shared mail storage unit 500 to the record to the message ID database 400. As described above, the information specifying the location of the shared mail storage unit 500 may be a file path, for example. The information specifying the location of the shared mail storage unit 500 is not particularly limited as long as it is information that can access the stored mail body and attached file after storage.

  In step C4, the message ID database 400 writes information for specifying the location of the shared mail storage unit 500. Specifically, the message ID database 400 receives a command issued by the mail header decoding unit 300 and writes information specifying the location of the shared mail storage unit 500 in the record (see FIG. 11).

  In step B <b> 11, the mail header decoding unit 300 adds information specifying the personal mailbox 600 to the personal mailbox information in the message ID database 400. Specifically, the mail header decoding unit 300 transmits a command for adding information specifying the personal mailbox 600 to the record to the message ID database 400.

  In step C5, the message ID database 400 adds information for specifying the personal mailbox 600. Specifically, the message ID database 400 receives a command issued by the mail header decoding unit 300 and adds information specifying the personal mailbox 600 to the record. For example, as shown in FIG. 12, the message ID database 400 stores the account part of the mail address (in the case of FIG. 12, the account “kobe” of the destination mail address “kobe@example.xxx.jp” shown in FIG. 3). It may be added to personal mailbox information. Note that the personal mailbox information shown in FIG. 12 is an example, and the personal mailbox information is not limited to the account part of the mail address. The personal mailbox information may be any information that identifies the personal mailbox 600, and the details thereof are not limited.

  In step B <b> 12, the mail header decoding unit 300 transmits the header part to the personal mailbox 600. In step E2, the personal mailbox 600 stores the header portion transmitted by the mail header decoding means 300. Specifically, the mail header decrypting unit 300 transmits the header part of the electronic mail shown in FIG. 3 to the personal mailbox 600 of the account “kobe”. The personal mailbox 600 of the account “kobe” stores the transmitted header portion (the header portion of the email shown in FIG. 3).

  Next, the operation of the mail server device 10 will be described in detail with respect to another destination that is different from one registered destination in the header portion corresponding to the message ID. In the following description, it is assumed that one registered destination is “kobe@example.xxx.jp” and the other destination is “kyoto@example.xxx.jp”. Further, in the following description, the mail server device 10 has received the email shown in FIG. 3 (the email with the message ID “20150610123456789@xxx.example.am”) and has created the record shown in FIG. Suppose there is.

  As described above, in step B5 shown in FIG. 8, the mail header decoding unit 300 determines whether or not a record including the message ID as a search key is stored in the message ID database 400.

  Here, it is assumed that the mail header decoding unit 300 determines that a record including the message ID that is the search key is stored in the message ID database 400. In that case, the mail header decoding means 300 adds information specifying the personal mailbox 600 to the personal mailbox information of the message ID database 400 (step B6). Specifically, the mail header decoding means 300 transmits a command for adding information for specifying the personal mailbox 600 to the personal mailbox information corresponding to the message ID in the record to the message ID database 400.

  In step C2, the message ID database 400 adds information that identifies the personal mailbox 600. Specifically, the message ID database 400 receives an instruction issued by the mail header decoding unit 300 and adds information for specifying the personal mailbox 600 to the personal mailbox information corresponding to the message ID. For example, as shown in FIG. 13, the message ID database 400 stores the account part of the mail address (in the case of FIG. 13, the account “kyoto” of the destination mail address “kyoto@example.xxx.jp” shown in FIG. 3). It may be added to personal mailbox information.

  In step B7, the mail header decoding means 300 transmits the header part to the personal mailbox 600 of the transmission destination. In step E1, the personal mailbox 600 stores the header portion transmitted by the mail header decoding means 300. Specifically, the mail header decrypting means 300 transmits the header part of the electronic mail shown in FIG. 3 to the personal mail box 600 of the account “kyoto”. The personal mailbox 600 of the account “kyoto” stores the transmitted header part (the header part of the electronic mail shown in FIG. 3).

<Email request>
Next, the operation when the mail server device 10 receives an e-mail request from the e-mail destination will be described in detail. In the following description, a case where the mail server device 10 receives the email shown in FIG. 3 and receives an email request from the email destination “kobe@example.xxx.jp” is exemplified. explain.

  FIG. 14 is a flowchart illustrating an example of an operation when the mail server device 10 receives an e-mail request from an e-mail destination.

  First, it is assumed that the mail request receiving means 700 receives a mail request from the client terminal (step F1 shown in FIG. 14). Specifically, the mail request accepting unit 700 receives a mail request such as POP3 from the client terminal. For example, the mail request receiving means 700 receives a mail request such as POP3 from the client terminal “kobe@example.xxx.jp”.

  When receiving the mail request from the client terminal, the mail request accepting unit 700 specifies the personal mailbox 600 (Step F2). Specifically, the mail request accepting unit 700 specifies a mail request source based on the mail request. Then, the mail request receiving means 700 identifies the personal mailbox 600 corresponding to the mail request source. For example, when an e-mail request is received from the e-mail destination “kobe@example.xxx.jp”, the e-mail request receiving unit 700 identifies the personal mailbox 600 of the account “kobe”.

  In step F3, the mail request receiving means 700 requests a header part. Specifically, the mail request receiving means 700 requests the specified personal mailbox 600 to transmit the header part of the electronic mail. Here, the mail request accepting means 700 may request the header part of each e-mail for two or more e-mails that have not been received by the mail request source client terminal.

  In step E2, the personal mailbox 600 transmits the header part to the mail request receiving means 700. Specifically, the personal mailbox 600 responds to the request for the header part from the mail request accepting unit 700 and transmits the header part to be stored to the mail request accepting unit 700.

In step F4, the mail request receiving means 700 acquires a header part. In Step F5, mail request receiving unit 700 extracts the message ID. Specifically, the mail request receiving unit 700 extracts the message ID from the acquired header part. For example, the mail request accepting unit 700 acquires the header part of the email with the message ID “20150610123456789@xxx.example.am” from the personal mailbox 600 of the account “kobe” of the mail request source. Then, the mail request receiving unit 700 extracts the message ID “20150610123456789@xxx.example.am” from the acquired header part.

  In step F6, the mail request receiving means 700 searches for the message ID. Specifically, the mail request reception unit 700 transmits a command for searching for a record including the extracted message ID to the message ID database 400.

  In step C6, the message ID database 400 responds with a record. Specifically, the message ID database 400 receives a command issued by the mail request receiving unit 700, searches for a record including the message ID, and returns a search result to the mail request receiving unit 700. For example, the message ID database 400 returns the record shown in FIG. 13 including the message ID “20150610123456789@xxx.example.am” to the mail request receiving means 700.

  In step F <b> 7, the mail request reception unit 700 acquires information for specifying the location of the shared mail storage unit 500. Specifically, the mail request receiving unit 700 acquires information for specifying the location of the shared mail storage unit 500 based on the search result obtained from the message ID database 400.

  In step F8, the mail request receiving means 700 requests a mail text and an attached file. Specifically, the mail request accepting unit 700 requests to transmit the mail text and the attached file stored in the specified shared mail storage unit 500. In step D <b> 2, the shared mail storage unit 500 transmits the mail text and the attached file to the mail request receiving unit 700. For example, it is assumed that the mail body shown in FIG. 3 corresponding to the electronic mail with the message ID “20150610123456789@xxx.example.am” is stored in the shared mail storage unit 500. In that case, the mail request accepting unit 700 acquires the mail text shown in FIG. 3 from the specified shared mail storage unit 500.

  In step F9, the mail request accepting unit 700 combines the header part, the mail text, and the attached file. Specifically, the mail request accepting unit 700 combines the acquired header part, the acquired mail body, and the acquired attached file to restore the e-mail. For example, it is assumed that the message ID database 400 stores the record shown in FIG. Then, it is assumed that the mail server device 10 receives an e-mail request from the client terminal of the account “kobe”. In that case, the mail request accepting unit 700 executes the above-described processing and restores the electronic mail shown in FIG.

  In step F10, the mail request receiving means 700 responds to the mail request. Specifically, the mail request receiving unit 700 transmits the restored electronic mail to the client terminal that is the mail request source. Note that the case where the mail request receiving unit 700 receives a mail request from the client terminal corresponding to “osaka@example.xxx.jp” shown in FIG. To do.

<Delete email>
Next, the operation when the mail server device 10 receives a mail deletion request from the client terminal will be described in detail. In the following description, a case where the mail server device 10 receives the email shown in FIG. 3 and receives an email deletion request from the email destination “kyoto@example.xxx.jp” is exemplified. I will explain.

  FIGS. 15 and 16 are flowcharts showing an example of operations when the mail server device 10 receives an e-mail deletion request from an e-mail destination.

  First, it is assumed that the mail request receiving means 700 receives a mail deletion request from the client terminal (step F11 shown in FIG. 15). Specifically, the mail request receiving unit 700 receives a mail deletion request using POP3 or the like from the client terminal.

  When receiving the mail deletion request, the mail request receiving means 700 identifies the personal mailbox 600 (Step F12). Specifically, the mail request receiving means 700 specifies the personal mailbox 600 based on the mail deletion request. For example, the mail request accepting unit 700 may specify the personal mailbox 600 based on information related to the transmission source of the mail deletion request. When the e-mail deletion request is received from the e-mail destination “kyoto@example.xxx.jp”, the e-mail request receiving unit 700 specifies the personal mailbox 600 corresponding to the account “kyoto”.

  In step F <b> 13, the mail request receiving unit 700 requests a header part from the specified personal mailbox 600. Specifically, the mail request reception means 700 requests the specified personal mailbox 600 to transmit a header part.

  In step E3, the personal mailbox 600 transmits the header part. Specifically, the personal mailbox 600 specified by the mail request accepting unit 700 extracts a header part to be stored in response to a request from the mail request accepting unit 700, and the extracted header part is sent to the mail request accepting unit 700. Send. Note that. The personal mailbox 600 may extract two or more header parts of the e-mail from the storage area of the personal mailbox 600 and transmit the extracted two or more header parts to the mail request receiving means 700.

  In step F14, the mail request receiving means 700 acquires a header part. In step F15, the mail request receiving unit 700 extracts a message ID from the acquired header part.

  In step F16, the mail request receiving means 700 requests the message ID database 400 to delete personal mailbox information. Specifically, the mail request accepting unit 700 transmits an instruction for deleting information for identifying a predetermined personal mailbox 600 from the record including the extracted message ID to the message ID database 400. Here, the predetermined personal mailbox 600 means a personal mailbox 600 corresponding to the mail deletion request source. Note that the command includes the extracted message ID.

  For example, it is assumed that the account of the e-mail deletion request source is “kyoto”. In that case, the mail request accepting means 700 transmits a command for deleting the information specifying the personal mailbox 600 of the account “kyoto” from the message ID database 400.

  In step C7, the message ID database 400 deletes the personal mailbox information requested for deletion from the record. Specifically, the message ID database 400 receives a command issued by the mail request receiving unit 700 and searches for one or more records to be stored using the message ID included in the command as a search key. Then, the message ID database 400 specifies a record including a message ID that is a search key. Then, the message ID database 400 deletes information specifying the personal mailbox 600 corresponding to the mail deletion request source from the specified record.

  For example, it is assumed that the mail server apparatus 10 has received the e-mail shown in FIG. 3 and has received an e-mail deletion request. Here, it is assumed that the account of the e-mail deletion request source is “kyoto”. Assume that the message ID that is the search key is “20150610123456789@xxx.example.am”. In that case, the message ID database 400 specifies the record shown in FIG. 13 using the message ID “20150610123456789@xxx.example.am” as a search key. Then, the message ID database 400 deletes the account “kyoto” from the personal mailbox information of the identified record, and updates the record as shown in FIG.

  In step F <b> 17, the mail request receiving unit 700 requests deletion of the header part stored in the personal mailbox 600. Specifically, the mail request receiving means 700 requests the personal mailbox 600 to delete the header part stored in the specified personal mailbox 600.

  In step E4, the personal mailbox 600 deletes the header part. Specifically, the personal mailbox 600 deletes the stored header part. And it changes to step F18 shown in FIG.

  In step F18 shown in FIG. 16, the mail request accepting means 700 requests the message ID database 400 to search for the message ID. Specifically, the mail request accepting unit 700 transmits a command for searching for the extracted message ID to the message ID database 400.

  In step C8, the message ID database 400 performs a search. Specifically, the message ID database 400 searches for a record including the message ID of the search key, and transmits the search result to the mail request receiving unit 700.

  In step F19, the mail request receiving means 700 determines whether information is registered in the personal mailbox information. Specifically, the mail request receiving means 700 determines whether or not information is registered in the personal mailbox information in the record (that is, the search result) transmitted from the message ID database 400. For example, if the acquired record is in the state shown in FIG. 12, the mail request receiving means 700 determines that information is registered in the personal mailbox information. On the other hand, if the acquired record is in the state shown in FIG. 11, the mail request receiving means 700 determines that no information is registered in the personal mailbox information.

  If the information is registered in the personal mailbox information (Yes branch of step F19), the mail server device 10 ends the process of deleting the electronic mail.

  On the other hand, if the information is not registered in the personal mailbox information (No branch in step F19), the mail request receiving means 700 issues a command to delete the shared mail information corresponding to the acquired record. The data is transmitted to the storage unit 500 (step F20).

  In step D3, the shared mail storage unit 500 deletes the shared mail information. Specifically, the shared mail storage unit 500 deletes the mail text and the attached file corresponding to the acquired record.

  In step F <b> 21, the mail request receiving unit 700 transmits a record deletion command to the message ID database 400. Specifically, the mail request accepting unit 700 transmits a command to delete the acquired record to the message ID database 400.

  In step C9, the message ID database 400 executes deletion. Specifically, the message ID database 400 deletes the record that has received the delete command.

[Modification 1]
As a first modification of the mail server device 10 according to the present embodiment, a mail deletion request including information for specifying an electronic mail to be deleted may be received. For example, the information specifying the e-mail to be deleted may be a message ID, transmission date / time, reception date / time, information on the transmission source (e-mail address, account name, etc.), and the like. Note that the information for specifying the e-mail to be deleted is not particularly limited as long as the e-mail to be deleted can be specified.

  When the mail deletion request includes information for specifying an email to be deleted, it is preferable that the request for transmitting the header portion includes information for specifying the email to be deleted. Alternatively, when the mail deletion request includes information for specifying the e-mail to be deleted, the personal mailbox 600 extracts the header portion based on the information for specifying the e-mail to be deleted, and extracts the extracted header. May be transmitted to the mail request receiving means 700. For example, when the mail deletion request includes a message ID of an electronic mail to be deleted, the personal mailbox 600 extracts a header portion including the message ID.

  As described above, the mail server device 10 according to the present embodiment stores the shared mail information including the mail text in the first storage area (shared mail storage unit 500) that is different for each message ID. Further, the mail server device 10 according to the present embodiment stores the header portion in the second storage area (personal mailbox 600) that is different for each destination. For example, when the mail server device 10 receives e-mails for two or more destinations, the mail server device 10 stores the mail body of the e-mails in the shared mail storage unit 500 and the header part as a personal mailbox 600 corresponding to each destination. To store. Therefore, the mail server device 10 according to the present embodiment avoids managing redundant data (duplicate data). Therefore, the mail server device 10 according to this embodiment suppresses an increase in the data size of the managed email and contributes to efficiently managing email.

[Second Embodiment]
Next, a second embodiment will be described.

  In the present embodiment, the header portion and the shared mail information are stored in the first storage area, and the header portion is stored in the second storage area. In the description of the present embodiment, the description of the same part as the above embodiment is omitted. Further, in the description of the present embodiment, the same components as those of the above-described embodiment are denoted by the same reference numerals, and the description thereof is omitted. In the description of the present embodiment, the description of the same operational effects as those of the above-described embodiment is also omitted.

  FIG. 17 is a block diagram showing an example of the overall configuration of the mail server device 10a according to the present embodiment. In the following description, differences from the mail server device 10 according to the first embodiment will be described in detail.

  The mail header decoding unit 300a according to the present embodiment stores the header part acquired from the received mail and the shared mail information in the first storage area (shared mail storage unit 500) corresponding to the message ID of the received mail. . Further, the mail header decrypting means 300a according to the present embodiment stores the header portion acquired from the received mail in the second storage area (personal mail box 600) for each destination of the received mail.

  The data size of the header part is often smaller than the data size of the mail body. Therefore, even if the header part and the mail text are stored in the shared mail storage unit 500, the influence on the usable capacity of the shared mail storage unit 500 is small. However, by storing the header part and the mail text in the shared mail storage unit 500, the header part and the mail text are combined to contribute to reducing the processing time in the process for restoring the email. . Therefore, the mail server device 10a according to the present embodiment contributes to more efficiently managing emails while suppressing an increase in the data size of emails to be managed.

[Third Embodiment]
Next, a third embodiment will be described.

  In the present embodiment, the header part and the shared mail information are stored in the first storage area, and the message ID of the header part is stored in the second storage area. In the description of the present embodiment, the description of the same part as the above embodiment is omitted. Further, in the description of the present embodiment, the same components as those of the above-described embodiment are denoted by the same reference numerals, and the description thereof is omitted. In the description of the present embodiment, the description of the same operational effects as those of the above-described embodiment is also omitted.

  The configuration of the mail server device 10b according to the present embodiment is as shown in FIG. In the following description, differences from the mail server device 10 according to the first embodiment will be described in detail.

  The mail header decoding unit 300b according to the present embodiment stores the header part acquired from the received mail and the shared mail information in the first storage area (shared mail storage unit 500) corresponding to the message ID of the received mail. . Further, the mail header decrypting means 300b according to the present embodiment stores the message ID 304 of the header part in the second storage area (personal mail box 600) for each destination of the received mail.

  As described above, the data size of the header part is often smaller than the data size of the mail body. Therefore, even if the header part and the mail text are stored in the shared mail storage unit 500, the influence on the usable capacity of the shared mail storage unit 500 is small. Furthermore, by storing the message ID in the personal mailbox 600 instead of the header portion, it is possible to suppress an increase in the data size of the managed email from the second embodiment. Therefore, the mail server device 10b according to the present embodiment contributes to further suppressing an increase in the data size of the managed e-mail while efficiently managing the e-mail.

  Part or all of the above-described embodiments may be described as in the following forms, but is not limited to the following.

  (Mode 1) Same as the mail server device according to the first aspect.

  (Mode 2) Message ID for storing, as a record, information associating the message ID of the received mail, the information specifying the storage location of the shared mail information, and the information specifying the storage location of the header part The mail server device according to attachment 1, further comprising a database.

(Mode 3) The message ID database associates the message ID with information specifying the storage location of the shared mail information and information specifying a personal mailbox as information specifying the storage location of the header part. The mail server device according to attachment 2, wherein the information is stored as the record.

(Mode 4) A mail request receiving unit that receives a mail request is further included, and the mail request receiving unit receives the mail request from the second storage area corresponding to the mail request source, The header part is acquired, the first storage area is specified based on the message ID included in the acquired header part and the message ID database, and the shared information is determined from the specified first storage area. The mail information is acquired, the acquired header part and the acquired shared mail information are combined, an e-mail is created, and the created e-mail is transmitted to the mail request source. The mail server device according to any one of the above.

(Embodiment 5) When the mail request receiving unit receives a mail deletion request, and the mail request receiving unit receives the mail deletion request, the storage location of the header portion to be deleted and the header portion to be deleted The mail server device according to appendix 4, wherein the storage location of the shared mail information is specified based on the message ID included in the header part to be deleted and the message ID database .

  (Mode 6) The mail header decoding means acquires a message ID from the header part of the received mail, determines whether or not the acquired message ID is stored in the message ID database, and acquires the acquired message. If the ID is not stored in the message ID database, the message ID, the information specifying the storage location of the shared mail information, and the header corresponding to the acquired message ID correspond to one destination. The mail server device according to any one of appendices 1 to 5, wherein the record that associates information specifying a second storage area is created, and the created record is registered in the message ID database.

  (Mode 7) When the acquired message ID is stored in the message ID database, the mail header decoding means specifies the record corresponding to the acquired message ID, and the header corresponding to the message ID The mail server device according to appendix 6, wherein information specifying the second storage area corresponding to another destination different from the one destination is added to the specified record.

  (Mode 8) The mail header decoding means stores the header portion acquired from the received mail and the shared mail information in the first storage area corresponding to the message ID of the received mail, and receives the received mail. The mail server device according to any one of appendices 1 to 7, wherein the header section acquired from the received mail is stored in the second storage area for each mail destination.

  (Mode 9) The mail header decoding means stores the header part acquired from the received mail and the shared mail information in the first storage area corresponding to the message ID of the received mail, and receives the received mail. The mail server device according to any one of appendices 1 to 8, wherein a message ID of the received mail is stored in the second storage area for each mail destination.

  (Mode 10) As in the mail management method according to the second aspect.

  (Mode 11) A step of storing, as a record, information associating the message ID of the received mail, information specifying the storage location of the shared mail information, and information specifying the storage location of the header part The mail management method according to appendix 10, including:

  (Mode 12) In the step of storing the record, information associating the message ID, information specifying a storage location of the shared mail information, and information specifying a personal mailbox is stored as the record. The mail management method according to attachment 11.

  (Mode 13) A step of receiving a mail request, and a step of obtaining the header portion from the second storage area corresponding to a mail request source when the mail request is received, and included in the obtained header portion A step of identifying the first storage area based on the message ID, a step of obtaining the shared mail information from the identified first storage area, the obtained header portion, and the obtained share The mail management method according to any one of appendices 10 to 12, further comprising: a step of creating e-mail by combining mail information; and a step of transmitting the created e-mail to the mail request source. .

  (Mode 14) A step of receiving a mail deletion request, a step of specifying a storage location of a header portion to be deleted and a header portion of the deletion target when the mail deletion request is received, and the header portion of the deletion target The mail management method according to attachment 13, wherein a storage location of the shared mail information is specified based on a message ID included in the mail.

  (Mode 15) In the step of separating, the step of acquiring a message ID from the header portion of the received mail, the step of determining whether or not the acquired message ID is stored in the message ID database, If the acquired message ID is not stored in the message ID database, the message ID, the information for specifying the storage location of the shared mail information, and the header corresponding to the acquired message ID Any one of appendices 10 to 14, further comprising: creating the corresponding record associating with the corresponding information specifying the second storage area, and registering the created record in the message ID database. The mail management method described in 1.

  (Mode 16) In the step of separating, when the acquired message ID is stored in the message ID database, the step of identifying the record corresponding to the acquired message ID and the message ID The mail according to claim 15, further comprising a step of adding information specifying the second storage area corresponding to another destination different from the one destination in the header portion to the specified record. Management method.

  (Mode 17) In the separating step, storing the header part acquired from the received mail and the shared mail information in the first storage area corresponding to a message ID of the received mail; The mail management method according to any one of appendices 10 to 16, further comprising: storing the header portion acquired from the received mail in the second storage area for each destination of the received mail.

  (Mode 18) In the separating step, storing the header part acquired from the received mail and the shared mail information in the first storage area corresponding to a message ID of the received mail; The mail management method according to any one of appendices 10 to 17, further comprising: storing the message ID of the received mail in the second storage area for each destination of the received mail.

  (Mode 19) As in the mail management program according to the third aspect.

  The form shown in the form 19 can be expanded to the forms shown in the forms 2 to 9 in the same manner as the form shown in the form 1.

  The disclosure of the above patent document is incorporated herein by reference. Within the scope of the entire disclosure (including claims) of the present invention, the embodiment can be changed and adjusted based on the basic technical concept. Further, various combinations or selections of various disclosed elements (including each element of each claim, each element of each embodiment, each element of each drawing, etc.) are possible within the framework of the entire disclosure of the present invention. is there. That is, the present invention of course includes various variations and modifications that could be made by those skilled in the art according to the entire disclosure including the claims and the technical idea. In particular, with respect to the numerical ranges described in this document, any numerical value or small range included in the range should be construed as being specifically described even if there is no specific description. In the present application, the functional means described as “means” such as “mail receiving means”, “mail header decrypting means”, “mail request accepting means”, etc. are also expressed as the functional unit or the functional part, respectively. be able to.

1, 10, 10a, 10b Mail server device 2, 200 Mail receiving means 3, 300, 300a, 300b Mail header decoding means 4 First storage area 5 Second storage areas 31, 41, 61 Shared mail information 32, 51 62, 301, 701, 4100, 4300 Header part 100 Other mail servers 302, 702, 4101, 4301 Mail text 303, 703, 4102, 4302 Attached file 304 Message ID of header part
400 Message ID database 401 Information in which message ID, header part, and shared mail information are associated 500 Shared mail storage unit 600 Personal mailbox 700 Mail request receiving means 800 Recipient mail software 3100, 3410, 3511-513, 3700 Mail 3200, 3600 Mail software 3300 Mail server 3310 of xxx.example.am Destination mail server determination function 3400 Mail server 3501 of example.xxx.jp Mailbox 3502 of Kobe Mailbox 3503 of kyoto Mailbox 4000 of osaka Mail server 4310 1 @ abc mailbox 4410 2 @ abc mailbox

Claims (9)

A mail receiving means for receiving e-mail;
A mail header decoding means for separating the received mail into shared mail information including a mail body and a header portion when the mail receiving means receives the electronic mail;
A first storage area;
A second storage area that is different for each e-mail destination;
A third storage area different from the first storage area and the second storage area;
Comprising
The header portion includes at least one of the source address of the received mail and the title of the received mail, and the message ID of the received mail,
The mail header decoding means stores the shared mail information of the received mail in the first storage area, and stores the header portion of the received mail in the second storage area for each destination of the received mail. Store and
The third storage area stores, as a record, information associating the message ID, information for specifying the storage location of the shared mail information, and information for specifying the storage location of the header part. Store ID database,
Mail server device. The message ID database includes information associating the message ID, information specifying the storage location of the shared mail information, and information specifying a personal mailbox as information specifying the storage location of the header part , The mail server device according to claim 1, wherein the mail server device is stored as the record. It further includes an email request receiving means for receiving an email request,
The mail request receiving means
When the mail request is received, the header part is acquired from the second storage area corresponding to the mail request source,
Based on the message ID included in the acquired header part and the message ID database , the first storage area is specified, and the shared mail information is acquired from the specified first storage area,
Combining the acquired header part and the acquired shared mail information to create an email,
The created e-mail is transmitted to the mail requesting the mail server apparatus according to claim 1 or 2. The mail request receiving means receives a mail deletion request,
The mail request reception means, when receiving the mail deletion request, specifies a storage location of the header part and a header part to be deleted based on the mail deletion request, and is included in the header part to be deleted The mail server device according to claim 3 , wherein a storage location of the shared mail information is specified based on a message ID and the message ID database . The mail header decoding means includes
Obtaining a message ID from the header of the received mail, determining whether the obtained message ID is stored in the message ID database;
If the acquired message ID is not stored in the message ID database, one of the message ID, the information specifying the storage location of the shared mail information, and the header corresponding to the acquired message ID The record corresponding to the information for specifying the second storage area corresponding to is created,
The mail server device according to any one of claims 1 to 4 , wherein the created record is registered in the message ID database. The mail header decoding means includes
If the acquired message ID is stored in the message ID database, the record corresponding to the acquired message ID is specified,
Wherein within the header part corresponding to the message ID, and corresponding to different other destinations and the one of the destination, the second information specifying a storage area of, adding to record the identified, according to claim 5 Mail server device. The mail header decoding means includes
Storing the header part acquired from the received mail and the shared mail information in the first storage area corresponding to the message ID of the received mail;
The mail server device according to any one of claims 1 to 6 , wherein the header part acquired from the received mail is stored in the second storage area for each destination of the received mail. A first storage area;
A second storage area that is different for each e-mail destination;
A third storage area different from the first storage area and the second storage area;
A mail server device configured to include
Receiving an email; and
Separating the received mail into the shared mail information including the mail body and the header part,
The header portion includes at least one of the source address of the received mail and the title of the received mail, and the message ID of the received mail,
In the separating step, the shared mail information of the received mail is stored in the first storage area corresponding to the message ID, and the reception is stored in the second storage area for each destination of the received mail. Store the header part of the email,
A mail management method for storing, in the third storage area, information in which the message ID, information for specifying the storage location of the shared mail information, and information for specifying the storage location of the header portion are associated with each other. A first storage area;
A second storage area that is different for each e-mail destination;
A third storage area different from the first storage area and the second storage area;
A mail management program to be executed by a computer that controls a mail server device configured to include:
Processing to receive e-mail;
Causing the computer to execute the process of separating the received mail in the shared mail information including the mail text and the header part,
The header portion includes at least one of the source address of the received mail and the title of the received mail and the message ID of the received mail
In the separation process, the shared mail information of the received mail is stored in the first storage area corresponding to the message ID, and the reception is stored in the second storage area for each destination of the received mail. Processing to store the header part of the mail;
A process of storing, in the third storage area, information that associates the message ID, information that specifies the storage location of the shared mail information, and information that specifies the storage location of the header part, A mail management program to be executed by a computer.

Images