JP2001168901A - Community production method, community production system and storage medium with community production program stored therein - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a community production method and a community production system which can prevent unwanted message and annoyance messages from reaching members of a mailing list in the case of community production and to provide a storage medium that stores a community production program. SOLUTION: A mailing list management section, that receives a community production request sent by a community producer, accepts only the community producer as a member taking part in the community and transmits an invitation notice to the community to member candidates. From among the member candidates receiving the notice, people, who intend to take part in the community transmit a communication participation request to the management section to take part in the community.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a community generation method, a community generation system, and a storage medium storing a community generation program, and more particularly, to a member participating in a community from members registered in a mailing list. A community generation method, a community generation system, and a storage medium storing a community generation program, which are dynamically determined according to the following.

[0002]

2. Description of the Related Art Examples of a conventional community generation method, a community generation system, and a storage medium storing a community generation program include methods used in major software, majordomo and fml. The storage medium storing the community generation method, the community generation system, and the community generation program has a mailing list server and a mailing list member storage unit.

[0003] A user can register a mailing list in the mailing list server by sending a mail to the mailing list server or inputting a command on a computer on which the mailing list server operates. When registering the mailing list, the mailing list name, mail address, and member address are registered. When using a registered mailing list, the user sends an e-mail to the e-mail address of the mailing list. The mailing list server forwards the received mail to all members of the mailing list. Thereby, communication between members in the mailing list is realized.

[0004] In addition, a user can perform processing on mailing list data such as deletion of a mailing list, addition and deletion of members, by transmitting a mail in which a command sentence is embedded to a mailing list server. In this case, a dedicated mail address for transmitting such a command statement can be provided separately from the mailing list address.

Further, fml which is free software provides a command for a member to temporarily leave the mailing list. Therefore, the mailing list server manages two lists for one mailing list in order to manage the members who have temporarily left. That is, in addition to the actual mailing list members, a list of all members including those who have temporarily left is managed.
Specifically, members of the mailing list are managed by a file called members, actives, and the initial state is member
s = actives. And the mailing list always sends mail to actives. If a member temporarily leaves, delete the corresponding address from actives, and when rejoining, refer to members to confirm that the user was a member in the past, Add the corresponding address. This allows
Members can temporarily leave the mailing list or join again.

[0006]

In the prior art, there is a problem that an unnecessary message or an annoying message may reach a mailing list member. That is, in temporary communication, the message communicated there is only valuable if read at the time of the communication, and the record of the communication is not important. Nevertheless, in the conventional technology, the message reaches all members unconditionally regardless of whether the member can read the message at that time. Furthermore, according to the conventional technology, even if a certain member is busy at the time and does not want to participate in the communication, the message arrives unconditionally.

[0007] The reason is that, in the prior art, the members participating in the community are not dynamically determined each time communication is performed, and furthermore, regardless of the members' intention at the time of communication. This is because the members participating in the community are determined.

[0008] One method of solving this problem is to consider a method in which a user is sent a command to leave the mailing list when he / she wants to leave the mailing list, and a list of all members including those who have temporarily left the mailing list is managed. Can be
However, in this method, a message is transmitted to all members registered in the mailing list in an initial state. In other words, the message is automatically transmitted until the user leaves the command, regardless of whether the user can read the message.

Therefore, an object of the present invention is to provide a member candidate who wishes to participate in communication each time a community for temporary conversations or the like is generated, taking into account the current situation of member candidates registered in the mailing list. The purpose is to form a community consisting only of members so that unnecessary messages are not accumulated in the candidate members.

[0010]

According to a first community generation system of the present invention, a server receives a community generation request from a user and generates a community.
A community invitation notification is transmitted to the member candidates registered in the mailing list, a community participation request is received from the member candidates who have received the invitation notification, and the member candidates who transmitted the community participation request are caused to join the community. ing. As described above, the object of the present invention is achieved by causing a candidate member who intends to participate in a community to participate in the community.

[0011] In a second community generation system according to the present invention, a web page creation unit receives a community creation request of a user from a community creation request web page through a WWW server. The web page creation unit passes the community generation request to the mailing list registration management unit. The mailing list registration management unit causes a community to be generated, creates a community invitation notification for the candidate members registered in the mailing list, and passes the notification to the Web page creation unit. Web page creation section notifies community invitation W
Create an eb page and present a web page for invitation to the community to potential members. Web page creation department,
A community participation request of the candidate member presented with the community invitation notification web page is received from the community participation request web page via the WWW server. The received Web page creation unit passes the community participation request to the mailing list registration management unit. The mailing list registration management unit causes the candidate member who has made the community participation request to participate in the community. As described above, the object of the present invention is achieved by causing a candidate member who intends to participate in a community to participate in the community.

[0012] A third community generation system according to the present invention provides a process for receiving a community generation request from a user on a recording medium, a process for generating a community, and a process for sending a member candidate registered in a mailing list to a community. In order to cause a computer to execute a process of transmitting an invitation notification, a process of receiving a community participation request of a member candidate who has received an invitation notification to the community, and a process of joining a member candidate having transmitted the community participation request to a community The object of the present invention has been achieved by recording the program described above. As described above, the object of the present invention is achieved by causing a candidate member who intends to participate in a community to participate in the community.

[0013]

Embodiments of the present invention will now be described in detail with reference to the drawings. FIG. 1 is a block diagram showing the configuration of the first embodiment of the present invention.

A first embodiment of the present invention will be described with reference to FIG. In the first embodiment of the present invention, a plurality of user terminals 110, a communication network 100, a server 20
It consists of 0. According to the embodiment of the present invention, the member candidates registered in the mailing list in the server 200 can generate a community on the mailing list, participate in the community, and communicate there. Users registered in the mailing list are called member candidates. The community is a group of candidate members who are willing to participate in message exchange. Here, among the candidate members, those who have joined the community are particularly called members. Further, among the members, those requesting the generation of a community are called community creators.

[0015] Specifically, candidate members are those who have a qualification to participate in the community.

In the embodiment of the present invention, a case where the member candidate is already registered in the server 200 and a case where the member candidate is not registered can be classified. Such differences are:
First, when a community creator requests a community creation, the difference is whether the request is accompanied by a mailing list registration request designating a member candidate or not. The configuration of the embodiment of the present invention will be described below with reference to FIG.

The user terminal 110 transmits to the server 200 a user's community generation request, a community generation request accompanied by a mailing list registration request, a community participation request, a community leave request, a community dissolution request, or a message transmission request. . Here, the community generation request accompanied by the mailing list registration request is transmitted to the mailing list registration request address of the server 200. The community creation request, community participation request, or message transmission request is transmitted as a normal mail to the mailing list address. The request for leaving the community and the request for dissolving the community are transmitted as command mail to the mailing list address. For example, by describing a specific character string in the first line of the mail body, it is possible to specify that the server processes the mail as a command mail. User terminal 1
Numeral 10 is for receiving various notifications or messages from the server 200 to the user. The various notifications include, specifically, an invitation to the community, a notification to notify that a new member has joined the community, a notification to notify that a member has left the community, and the fact that the community has been disbanded. Notification, an error notification, and the like.

The communication network 100 includes the user terminal 1
10 and the server 200 via transmission and reception.

The server 200 has a function of receiving a community generation request from a user and generating a community.
A function of receiving a community participation request from a candidate member and joining the member candidate to the community, a function of receiving a community leaving request from a member and leaving the member from the community, and receiving a community dissolution request from the member And a function of receiving a message transmission request from a member and transmitting a message. Further, the server 200
Sends an invitation to the community to the member candidates. The server 200 also notifies the member of a notification that the community participation requester has joined the community, a notification that the member has left the community, and a notification that the community has been dissolved. And an error notification or the like.

The server 200 comprises a mail server 210, a mailing list registration management section 220, and a mailing list member data storage section 230 as shown in FIG.

The mail server 210 sends a community generation request from the user terminal 110, a community generation request accompanied by a mailing list registration request, a community participation request, a community leave request, a community dissolution request, or a message transmission request via the communication network 100. And a mailing list registration unit 221 or a mailing list management unit 22
2 is provided. Specifically, the mail server 210 distributes a mail including a community participation request, a community leaving request, a community dissolution request, and a message transmission request to the mailing list management unit 222.
In addition, the mail server 210 delivers a mail including a community generation request accompanied by a mailing list registration request to the mailing list registration unit 221.

The mailing list registration management section 220 registers the mailing list, creates a community, and dissolves the community into the mailing list member data storage section 230 based on the contents of the mail delivered by the mail server 210. , Withdrawal. Further, the mailing list registration management section 220 refers to the mailing list member data storage section 230 and transmits various notifications or messages such as a notification of invitation to a community. The mailing list registration management section 220 includes a mailing list registration section 221, a mailing list management section 222, and a mail processing / transfer section 223, as shown in FIG.

Upon receiving a community generation request accompanied by a mailing list registration request from the mail server 210, the mailing list registration unit 221 registers a new mailing list in the mailing list member data storage unit 230 according to the contents of the mailing list registration request. Further, the mailing list registration unit 221 registers the mail address of the new mailing list in the mail server 210.

FIG. 2 shows an example of mailing list management information registered in the mailing list member data storage section 230. As shown in FIG. 2, the mailing list management information includes, for each mailing list, the mailing list name, comment information, mailing list address, registrant address, member candidate mail address, member address, mailing list registration date, last use date and time. And other information are managed. Specifically, the state of the mailing list management information can be roughly divided into a state where a community is generated and a state where a community is not generated. FIG. 2A shows mailing list management information in a state where no community has been created. In this case, the member address column is blank,
The addresses of all members are listed in the column of candidate member addresses. On the other hand, FIG. 2B shows mailing list management information in a state where a community has been created. In this case, the person whose address is described in the member address column is a member participating in the community,
A person whose address is described in the member candidate address column is a member candidate who does not participate in the community. Further, the mailing list management information in the state where the community is generated in FIG. 2B includes the last time a community participation request, a message transmission request, or a command mail was received from a member participating in the community. , Last use date and time. Further, in FIG. 2, the member address column and the member candidate address column are divided to distinguish between members participating in the community and candidate members not participating in the community. A method is also conceivable in which a member who participates in the community is distinguished from a candidate member who does not participate, for example, by attaching a tag to the e-mail address of the person.

The mailing list registration unit 221 registers a new mailing list in the mailing list member data storage unit 230, registers a mail address of the new mailing list in the mail server 210, and receives the mail address from the mail server 210. A community generation request is sent to the mailing list management unit 222.

The mailing list management unit 222 receives a community creation request from the mail server 210 or the mailing list registration unit 221 or a community participation request, community leaving request, community dissolution request, or message transmission request from the mail server 210. Execute the process.

When receiving the community generation request, the mailing list management unit 222 generates a community on the mailing list in the mailing list member data storage unit 230, and causes the community creator who transmitted the request to participate in the community. Specifically, the mailing list management unit 222 stores the address of the community creator in the member candidate address column of the mailing list management information stored in the mailing list member data storage unit 230 shown in FIG. Move. As a result, a community including the community creator as a member is generated.

The mailing list management unit 222 generates a community, causes the community creator to participate in the community, and then creates a notification of a community invitation to a member candidate registered in the mailing list, and generates the notification. It requests the mail processing / transfer unit 223 to execute the work of transmitting the invitation notification.

When receiving a community participation request from the mail server 210, the mailing list management unit 222 adds a community participation requester to the community. Specifically, the mailing list management unit 222 replaces the address of the community participation requester in the member candidate address column of the mailing list management information stored in the mailing list member data storage unit 230 shown in FIG. Column to add a community participation requester to the community.

The mailing list management unit 222 creates a notification for notifying the members participating in the community that the requester has participated in the community after the community requester has joined the community. , And a request to the mail processing / transfer unit 223 to execute the transmission work of the notification.

When a message transmission request is received from the mail server 210, the mailing list management unit 222
It requests the mail processing / transfer unit 223 to execute a message transmission operation for members participating in the community.

When a request to leave the community is received from the mail server 210, the mailing list manager 222 leaves the requester from the community. Specifically, the mailing list management unit 222 stores the requester's address in the member address column of the mailing list management information stored in the mailing list member data storage unit 230 shown in FIG. Move.

When a community dissolution request is received from the mail server 210, the mailing list management unit 2
22 disbands the community. Specifically, the mailing list management unit 222 replaces the addresses of all members in the column of member addresses in the mailing list management information stored in the mailing list member data storage unit 230 shown in FIG. Move to

The mailing list management unit 222, after performing a member leaving operation from the community, creates a member leaving notification from the community and transmits the leaving notification to the members participating in the community. It requests the mail processing / transfer unit 223 to execute the work. In addition, the mailing list management unit 222 performs, after performing the community dissolution work, or immediately before the dissolution work,
It requests the mail processing / transfer unit 223 to perform a task of creating a community dissolution notice and transmitting the dissolution notice to members who have joined the community at the time of community dissolution.

The mail processing / forwarding unit 223 creates various notifications in accordance with the contents requested by the mailing list management unit 222, and further refers to the mailing list member data storage unit 230 to send to the member candidate or community. The task of transmitting the notice to the participating members via the mail server 210 is executed, and the mailing list member data storage unit 2
With reference to 30, a message transmission operation is performed on the members participating in the community through the mail server 210. Specifically, the mail processing / transfer unit 22
Reference numeral 3 denotes a mailing list management information stored in the mailing list member data storage unit 230 shown in FIG. 2 in the address of a member participating in the community or the address of a candidate member in the column of the member address. By referring to the address of the member candidate, transmission of various notifications or message transmission to the member or the member candidate is executed through the mail server 210. The various notifications include a notification of an invitation to a community, a notification of a new member joining a community, a notification of a member leaving a community, a notification of a dissolution of a community, and an error notification.

Mailing list member data storage unit 23
0 stores the mailing list management information shown in FIG. 2 for each mailing list.

Next, the operation of this embodiment will be described in detail with reference to FIG.

FIG. 3 is a diagram showing an example of the processing flow of the present invention when there are four user terminals.

Here, as an example, the user A is the user A,
A case in which a group consisting of B, C, and D attempts to generate a community will be described. First, the user A issues a community generation request to the server 200 via the communication network 100 by the user terminal 110 (FIG. 3).
S1). When the user A requests the community generation together with the registration of the mailing list, the user A makes a community generation request to the mailing list registration request address. Here, the mailing list registration request address is
This is an address for the user to transmit a community generation request accompanied by a mailing list registration request to the server.
This is an address registered in the mail server 210 in advance. When the user makes a community generation request to an existing mailing list, the user transmits a community generation request to the address of the mailing list.

FIG. 4 shows an example of information necessary for a community generation request. Community generation requests can be divided into those with mailing list registration requests and those without. FIG. 4A shows an example of information necessary for a community generation request in which a community generation request is accompanied by a mailing list registration request. In this case, the community generation request includes the information of the community creator, which is the information necessary for authentication to use the service.
ID and password, name of the mailing list to be registered, comment, mailing list address, mail address of the community creator who is the mailing list registrant,
Information such as addresses of candidate members that the community creator wants to communicate with is required. FIG. 4B shows an example of information necessary for a community generation request without a mailing list registration request. In this case, the community generation request requires information such as an ID and password of a community creator, a mailing list name, and a mailing list address, which are information necessary for authentication for using a service. The community creator ID shown in FIGS. 4A and 4B, the mail address of the community creator who is a registrant of the mailing list shown in FIG. 4A, and the mailing list address shown in FIG. Even if it is not directly described in the mail to be executed, it is possible to substitute the sender address and destination address of the mail.

The mail server 210 having received the community generation request checks whether the community generation request is accompanied by a mailing list registration request. This determination can be made, for example, based on whether the mail destination is a mailing list registration request address. If the community generation request involves a mailing list registration request, mail server 210 passes the mail to mailing list registration unit 221. Then, the mailing list registration unit 221 that has received the community generation request sends A, B,
A mailing list with C and D as member candidates is registered in the mailing list member data storage unit (FIG. 2), and then the community generation request is sent to the mailing list management unit 222. On the other hand, if the community generation request does not involve a mailing list registration request, mail server 210 sends a community generation request to mailing list management unit 222.

The mailing list management unit 222 that has received the community generation request generates a community and causes the community creator A to participate in the community (S2 in FIG. 3). As a result, in the mailing list management information (FIG. 2), the mail address of A is described in the column of the member candidate and the mail addresses of B, C, and D are described in the column of the mail address of the candidate (FIG. 2). 3 M1).

The mailing list management unit 222 generates a community and, after making the community creator participate in the community, requests the mail processing / transfer unit 223 to create and transmit an invitation to the community. Upon receiving the request, the mail processing / forwarding unit 223 creates an invitation to the community, refers to the mail address of the candidate member from the mailing list member data storage unit, and sends the invitation to the community to the member via the mail server 210. Send to candidate B, C, D. The invitation notification includes the fact that the candidate member was invited to the community, information on the community generated by the community creator, information on how to join the community, and the like.
The community information includes information such as the name of the mailing list, comments, and candidate members.

When the candidate members B, C, and D, who have received the notification of invitation to the community, intend to participate in the community, they can send an e-mail for a community participation request to the server 200 ( S in FIG.
3). At that time, it is also possible to add a comment or the like when participating in the community. Here, a case where B makes a participation request will be described.

The mail server 210 that has received the community participation request mail from the user terminal B sends the mail to the mailing list management unit 222. The received mailing list management unit 222 causes B, which is the candidate member who transmitted the community participation request, to participate in the community (S4 in FIG. 3). After allowing member candidate B to participate in the community, mailing list management unit 222
It requests the mail processing / transfer unit 223 to create and transmit a community participation notification of the community participation requester B. Upon receiving the request, the mail processing / forwarding unit 223 creates the notification, refers to the address of A as a member participating in the community from the mailing list member data storage unit, and sends the notification through the mail server 210. Sent to A, a member of the community. As a result, the mailing list management information (FIG. 2) is in a state where the mail addresses of A and B are described in the member candidate column, and the mail addresses of C and D are described in the member candidate mail address column. (M in FIG. 3
2).

The same processing is performed also when the member candidate C makes a community participation request (S3, S4 in FIG. 3). As a result, in the mailing list management information (FIG. 2), the mail addresses of A, B, and C are described in the member candidate column, and the mail address of D is described in the member candidate mail address column. (M3 in FIG. 3).

Member who is participating in the community
A, B, and C can make a message transmission request to the server 200 (S5 in FIG. 3). Specifically, members A, B and C participating in the community send mailing list addresses of the mail server 210 to
Send an email containing a message send request.

The mail server 210 that has received the message transmission request transmitted by the member B sends it to the mailing list management unit 222. The received mailing list management unit 222 requests the mail processing / transfer unit 223 to perform a message transmission operation to members A and C participating in the community. Upon receiving the request, the mail processing / forwarding unit 223 refers to the mail addresses of A and C from the mailing list member data storage unit 230, and sends mail to members A and C who are participating in the community at that time. Through server 210,
The message transmission is executed (S6 in FIG. 3). By executing this message transmission request, communication among members A, B, and C participating in the community can be realized. It should be noted that members A and C, which are the members who execute the message transmission, may include B, which is the member who made the mail transmission request. In addition, members A, B, and C participating in this community,
A message transmission request can be made an arbitrary number of times until the user leaves the community or the community is dissolved.

Member who is participating in the community
When A, B, and C want to leave the community, they can transmit a request to leave the community to the server 200 (S7 in FIG. 3). Specifically, a member who wants to leave the community sends a mail including a request to the mailing list address of the mail server 210.

Here, as an example, a case in which B has requested to leave will be described. The mail server 210 that has received the community leaving request from the member B passes the mail to the mailing list management unit 222. The mailing list management unit 222 that has received the request removes the requester B from the community (S8 in FIG. 3). After the withdrawal, the mailing list management unit 222 sends the requester B
Requests the mail processing / transfer unit 223 to create and send a notification that informs that the user has left the community. Upon receiving the request, the mail processing / forwarding unit 223 creates such a notification, refers to the mail addresses of members A and C participating in the community from the mailing list member data storage unit, and sends the notification through the mail server 210. Send notifications to members A and C participating in the community. As a result, in the mailing list management information (FIG. 2), the mail addresses of A and C are described in the member candidate column, and the mail addresses of B and D are described in the member candidate mail address column. (FIG. 3
M4).

When a member participating in the community wants to dissolve the community, the member can transmit a request for dissolution of the community to the server 200 (see FIG. 3).
S9). Specifically, a member who wants to break up the community sends a mail including the request to the mailing list address of the mail server 210.

The mail server 210 that has received the mail requesting withdrawal from the community sent by the member A.
Passes this mail to the mailing list management unit 222. The received mailing list management unit 222 executes dissolution of the community (S10 in FIG. 3). here,
The mailing list management unit 222 may check whether the requester is a community creator, and dissolve the community only when the requester is a community creator. After executing the dissolution of the community, the mailing list management unit 222 requests the mail processing / transfer unit 223 to create and transmit a notification for notifying the dissolution of the community. Upon receiving the request, the mail processing / forwarding unit 223
Before the community is dissolved from the mailing list member data storage unit, the notification is created, and the notification is sent to the community through the mail server 210 with reference to the email addresses of the members A and C who have joined the community before the community is dissolved. Send to the participating members A and C. As a result, the member candidate column of the mailing list management information (FIG. 2) becomes blank, and the mail addresses of A, B, C, and D are described in the member candidate mail address column (FIG. 3). M5).

Also, in S8 of FIG. 3, as a result of leaving the sender of the request to leave the community from the community,
When the number of members participating in the community becomes one, the dissolution of this community may be executed.

Also, certain conditions such as dissolution after a certain period of time has elapsed since the community was created, or dissolution after a certain period of time since the last e-mail was received from members participating in the community. Is satisfied, the dissolution of this community may be executed. As a result, even if members participating in the community do not request dissolution of the community, it is possible to automatically dissolve a community that is considered to be unnecessary to some extent and generate a newly needed community. become. As a result, it is possible to generate a more dynamic community in consideration of the usage status of the user.

Next, the mail server 210, the mailing list registration section 221, and the mailing list management section 22 will be specifically described. (Specific description of the mail server 210)

Hereinafter, the mail server 210 will be described with reference to FIG.
Will be described in detail. Specifically, the mail server 210 receives a community generation request, a community participation request, a message transmission request, or a command mail from the user terminal 210 via the communication network, and performs the processing.

The mail server 210 has the communication network 1
From 00, a community generation request, a community generation request accompanied by a mailing list registration request, a community participation request, a community leave request, a community dissolution request,
Alternatively, when a mail including a message transmission request is received (S21 in FIG. 5), first, in order to determine the content, it is determined whether the destination of the mail is a mailing list registration request address registered in the mail server 210. Check (S in Fig. 5)
twenty two).

If the destination of the mail is a mailing list registration request address, the mail server 210 determines that the mail is a community generation request accompanied by a mailing list registration request, and determines that the mail is a mailing list registration unit 22.
1 (S25 in FIG. 5), and the process ends.

If the destination of the mail is not the mailing list registration request address, the mail server 210 checks whether or not the destination is a mailing list address registered in the mail server 210 (S23 in FIG. 5). If the destination is a registered mailing list address, the mail server 210 determines that the mail includes a request for the mail mailing list, transmits the mail to the mailing list management unit 222 (S26 in FIG. 5), and ends the processing.

If the destination of the mail is neither the mailing list registration request address nor the mailing list address registered in the mail server 210, the mail server 210 determines that the mail is a mail irrelevant to the mailing list and sends it to the destination. And the process ends. (Specific description of the mailing list registration unit 221)

Hereinafter, the processing of the mailing list registration unit 221 will be described in detail with reference to FIG.

The mailing list registration unit 221 receives a mail including a community generation request accompanied by a mailing list registration request from the mail server 210 (S31 in FIG. 6).
First, it is checked whether or not the requestor, the community creator, is a person who can register the mailing list (FIG. 6).
S 32). At this time, as a method of authenticating the community creator, a method using the sender address, a method using the user's authentication ID and authentication password (FIG. 4A) described in the content of the community generation request, and the like are used. There is.

As a result of examining whether or not the community creator can register the mailing list, if the mailing list cannot be registered, the mailing list registration unit 22
1 creates an error notification and transmits the error notification to the community creator via the mail server 210 (S38 in FIG. 6). The process of S33 of FIG. 6 may be performed after the process of S31 of FIG. 6 without performing the process of S32. In this case, any user can register the mailing list.

As a result of checking whether or not the community creator can be registered in the mailing list, if the mailing list can be registered, the mailing list registration unit 221
Checks the contents of the community generation request accompanied by the mailing list registration request (FIG. 4A), and checks whether information necessary for registering the mailing list has been correctly input (S33 in FIG. 6). If the correct information has not been input, an error notification is created by the mailing list registration unit 221 and transmitted to the community creator via the mail server 210 (S38 in FIG. 6).

When the correct information for registering the mailing list is input in the community generation request accompanying the mailing list registration request, the mailing list registration unit 221 queries the mail server 210 and uses the mailing list address specified by the community creator. It is checked whether it is possible (S34 in FIG. 6). As a result, if the mailing list address is unusable, the mailing list registration unit 221 creates an error notification, and transmits the error notification to the community creator via the mail server 210 (S38 in FIG. 6). In order to reduce the number of times of re-registration due to address duplication, the community creator may input a plurality of addresses from the beginning into the mailing list address column (FIG. 4A) in the community creation request. . In this case, the mailing list registration unit 221 checks addresses in order until a usable address is found (S34 in FIG. 6).

As a result of checking whether the mailing list address is usable or not, if the address is usable,
The mailing list registration unit 221 registers the mailing list name, comment, mailing list address, registrant address, and member candidate address (FIG. 4A) specified by the community creator in the mailing list member data storage unit 230 (FIG. 2A). ) (Step 35).

Next, the mailing list registration unit 221 requests the mail server 210 to register the address specified by the community creator as a mailing list address, and the mail server 210 registers the address as a mailing list address (S36 in FIG. 6). ).

Then, the mailing list registration unit 221
Sends the community creation request to the mailing list
22 and ends the process (S37 in FIG. 6). (Mailing list management unit 222 and mail processing / forwarding unit 223
Specific description)

Hereinafter, the processing of the mailing list management section 222 and the mail processing / transfer section 223 will be described in detail with reference to FIG.

The mailing list management unit 222 includes a mail including a community generation request from the mail server 210 or the mailing list registration unit 221, or a community participation request, community leaving request, community dissolution request, or message transmission request from the mail server 210. And execute the processing.

Upon receiving the mail, mailing list management section 222 first checks the mailing list management information of the mailing list in mailing list member data storage section 230, and checks whether or not the person who sent the mail is a candidate mailing list member (FIG. 7 S41).
As a result, if the person who sent the mail is not a candidate for a mailing list member, the mailing list management unit 222
Sends an error notification to the person (S4 in FIG. 7).
8).

If the person who sent the mail is a mailing list member candidate, the mailing list management unit 222
Checks whether the mail is a community creation request (S42 in FIG. 7). If the community has not been generated, the mailing list management unit 222 determines that the mail is a generation request. Specifically, referring to the mailing list management information in the mailing list member data storage unit 230, if no community participation member exists, it is determined that a community has not been generated, and that the mail is a community generation request.

As a result, the mailing list management section 222
Determines that the mail is a community creation request, the mailing list management unit 222 creates a community and causes the community creator who sent the community creation request to participate in the community (FIG. 7).
S43 in FIG. 3 and S2 in FIG. Then, the mailing list management unit 222 registers the date and time when the community was created in the mailing list member data storage unit 230 (such as the registration date and time in FIG. 2), and creates and transmits an invitation to the community by the mail processing / forwarding unit 223. Request to. Upon receiving the request, the mail processing / forwarding unit 223 creates a notification of invitation to the community and sends the mailing list member data storage unit 23
With reference to the mail address of the member candidate from 0, the invitation notification is transmitted to the member candidate through the mail server, and the process is terminated (S44 in FIG. 7).

Further, the mailing list management unit 222
If it is determined that the received mail is not a community generation request, the mailing list management unit 222 refers to the mailing list management information in the mailing list member data storage unit 230, and the person who transmitted the mail is a member participating in the community. Check whether or not (Fig. 7
S47). As a result, if the person who sent the mail is not a member participating in the community, the mailing list management unit 222 determines that the mail is a community participation request. And the mailing list management unit 2
22 updates the mailing list management information stored in the mailing list member data storage unit 230,
The community join requester who has transmitted the community join request is added to the community (S49 in FIG. 7, S2 in FIG. 3).
4). As a method of adding this community participation requester to the community, the mail address of the community participation requester in the member candidate column (FIG. 2) of the mailing list management information stored in the mailing list member data storage unit 230 is set to the member address. (FIG. 2) and a method of setting a flag at the mail address of the community participation requester in the member candidate column of the mailing list management information (FIG. 2).

Next, the mailing list management unit 222
The mail processing / forwarding unit 223 extracts a comment to the community of the community participation requester from the received community participation request, and creates and transmits a notification including the comment to notify that the community participation requester has joined the community. And terminates the process. The mail processing / forwarding unit 223 creates a notification for notifying that the community participation requester has joined the community,
Referring to the mailing list member data storage unit 230,
The mail address of the member participating in the community is checked, and the notification is transmitted to the member participating in the community through the mail server 210 (S50 in FIG. 7).

If the person who sent the mail is a member participating in the community in S45 of FIG. 7, the mailing list management unit 222 checks whether the mail is a command mail (FIG. 7). S43).
This determination method depends on the definition of the command mail of the system. For example, when the user describes a specific character string in the first line of the mail body and specifies that the server processes the mail as a command mail, the determination is made by reading the first line of the mail body.

As a result of checking whether or not the mail is a command mail, if the mail is not a command mail, the mailing list management unit 222 determines that the mail is a message transmission request. Then, the mailing list management unit 222 requests the mail processing / transfer unit 223 to transfer the message transmission request. Upon receiving the request, the mail processing / forwarding unit 223 changes the subject and destination of the message transmission request to those suitable for performing communication in the community, and the mailing list member data storage unit 230 stores the members participating in the community. Look up the mail address of the mail server 2
The message of the message transmission request is transmitted to the members participating in the community through 10.
(S47 in FIG. 7, S6 in FIG. 3).

In S46 of FIG. 7, if the mail is a command mail, the mailing list management unit 222
The contents of the command mail are checked to see if it is a request to leave the community (S51 in FIG. 7).
As a result, when the content of the command mail is a request to withdraw from the community, the mailing list management unit 222
Updates the mailing list member data storage unit 230 to leave the sender of the command mail from the community (S54 in FIG. 7, S8 in FIG. 3). Also, S in FIG.
At 51, if the content of the command mail is a request to leave the community and the mail sender is a community creator, the process of S54 in FIG.
The community dissolution processing of S57 and S58 in FIG. 7 may be performed. Thus, if the community creator leaves the community, the community will be dissolved.

After the sender of the command mail is removed from the community (S54 in FIG. 7), the mailing list management section 222 stores the mailing list member data storage section 23.
Referring to 0, it is checked whether the number of members participating in the community is one (S55 in FIG. 7). As a result, if the number of members participating in the community is not one, the mailing list management unit 222 performs mail processing to create and transmit a notification for notifying that the member who is the sender of the command mail has left the community. Request the transfer unit 223 to end the processing. The mail processing / forwarding unit 223 creates a notification for notifying that the member has left the community, checks the mailing list member data storage unit 230 for the mail addresses of the members participating in the community, This notification is transmitted to the members participating in (1) (S56 in FIG. 7).

Further, as a result of examining whether or not the number of members participating in the community is one, if the number of members participating in the community is one, the mailing list management unit 222 stores the mailing list member data. The mailing list management information stored in the storage unit 230 is updated, the community is dissolved, and the mail processing / transfer unit 223 is requested to create and transmit a notification for notifying that the community has been dissolved (FIG. 7). S57,
S10 in FIG. 3). The mail processing / forwarding unit 223 creates a notification for notifying that the community has been dissolved, checks the mailing list member data storage unit 230 for the mail addresses of members participating in the community,
This notification is transmitted to the members participating in the community through the mail server 210 (S58 in FIG. 7). Here, even if the number of members participating in the community is one, the community may not be dissolved.

In S51 of FIG. 7, as a result of the mailing list management unit 222 examining whether the content of the command mail is a request for withdrawal, if the content of the command mail is not a request for withdrawal from the community, the mailing list management unit 222 Checks whether the content of the command mail is a request for dissolution of the community (S5 in FIG. 7).
2). As a result, if the content of the command mail is not a request for dissolution of the community, the mailing list management unit 222
Creates and sends an error notification to the mail processing / forwarding unit 223
Request to. The mail processing / transfer unit 223 creates an error notification, and transmits the error notification to the sender of the command mail via the mail server 210 (S53 in FIG. 7).

On the other hand, when the content of the command mail is a request for dissolution of the community, the mailing list management unit 22
2 requests the mail processing / transfer unit 223 to create and send a community dissolution notice. Email processing / forwarding unit 22
3 creates a notice of community dissolution, checks the mail address of the member participating in the community by the mailing list member data storage unit 230, and transmits this notification to the member participating in the community via the mail server 210 ( Step 57 in FIG. 7). Thereafter, the mailing list management unit 222 updates the mailing list management information stored in the mailing list member data storage unit 230 and disbands the community (S58 in FIG. 7). Specifically, the mailing list management unit 222 stores the mailing list member data storage unit 2
A method of transmitting all mail addresses in the member address column of the mailing list management information stored in the mailing list management information 30 to the member candidate address column, and a method of transferring the tag of the tagged mail address in the member candidate address column of the mailing list management information. Execute the method of taking.

In addition, on the mail server 210, a mailing list address and a community management address are prepared for each mailing list, and a request for creating a community, a request for joining a community, a request for leaving from a community, or a request for dissolving a community are provided as contents. A method is also considered in which all or any of the command mails to be received is received at a community management address on the mail server 210, and a message transmission request is received at a mailing list address on the mail server 210. By using a method of preparing a mailing list address and a community management address for each mailing list,
The mailing list management unit can determine whether or not it is a command mail in S46 of FIG. 7 based on the destination of the sent mail. Even in such a case, if the community generation request is accompanied by a mailing list registration request, the community generation request is sent to the mail server 2.
10 will be received at the mailing list registration request address.

Next, a second embodiment of the present invention will be described in detail with reference to the drawings.

FIG. 8 is a block diagram showing the configuration of the second embodiment of the present invention. Referring to FIG. 8, the second embodiment is different from the first embodiment in that a WWW server 240 and a WWW page creation unit 250 are provided in addition to the components of the first embodiment.

The server 200 according to the second embodiment has the first
In addition to the embodiment, a request for community generation, a request for community participation, a request for leaving a community, a request for community dissolution, or a request for message transmission from a community creator, a member, or a candidate member from the information input Web page can be made via the WWW server 240. And receive. The information input Web pages are respectively created by the Web page creation unit 250 and provided to the community creator and the like via the WWW server 240. The web page for inputting information
Community creation request web page, community participation request web page, community leave request web page,
Includes a web page for requesting community dissolution and a web page for requesting message transmission.

Mail server 210 of the second embodiment
Performs the same processing as the mail server 210 of the first embodiment.

The mailing list management unit 220 according to the second embodiment performs, in addition to the processing performed by the mailing list management unit 220 according to the first embodiment, the contents of a request or a command distributed by the Web page creation unit 250. Based on this, the mailing list is registered in the mailing list member data storage unit 230, a community is created and disbanded, and members join and leave the community. Further, the mailing list management unit 220 of the second embodiment
Makes various notifications with reference to the mailing list member data storage unit 230. Here, the various notifications are the same as the notifications of the first embodiment.

The mailing list registration unit 221 of the second embodiment receives a community generation request accompanied by a mailing list registration request from the Web page creation unit 250 in addition to the processing performed by the mailing list registration unit 221 of the first embodiment. Then, the processing performed by the mailing list registration unit 221 of the first embodiment is performed.

The mailing list management unit 222 according to the second embodiment receives a request from the mail server 210 and performs the mailing list management unit 222 according to the first embodiment.
In addition to the above processing, the same type of request is received from the Web page creation unit 250 and the corresponding processing is performed. Further, the mailing list management unit 222 according to the second embodiment performs a process of transmitting various notifications or messages transmitted by the mail processing / transfer unit 223 to the Web page creation unit 250.

Mail processing / transfer unit 2 of the second embodiment
23, the mailing list member data storage unit 230
The same processing as that of the mailing list member data storage unit 230 of the first embodiment is performed.

The WWW server 240 receives the request transmitted by the user terminal 110 using the information input Web page via the communication network 100, and sends the request to the Web page creation unit 250. Perform distribution processing.

The Web page creation section 250 is a server for the WWW server 24.
0, a request is received from the mailing list registration unit 221.
Alternatively, a process of distributing to the mailing list management unit 222 and a process of the WWW server 240 creating a notification Web page for providing various notifications and messages to the user terminal 110 and a message Web page are performed.

More specifically, the Web page creation unit 250 distributes a community creation request, a community participation request, a community leave request, a community dissolution request, and a message transmission request to the mailing list management unit 222, and generates a community with a mailing list registration request. The request is distributed to the mailing list registration unit 220.

The web page creation unit 250 creates a notification web page for disclosing various notifications received from the mailing list management unit 222.
An operation of creating a message Web page that discloses the contents of the message of the message transmission request received from the mailing list management unit 222 is executed. Further, the web page creation unit 250 sends the created web page to the WWW server 24.
Through 0, an operation of disclosing to a community creator, a member, or a candidate member is performed. Various notifications include a community invitation notification, a notification that the requester of the community has joined the community, a notification that a member has left the community, and a notification that the community has been disbanded. Notification, error notification, and the like.

Next, the operation of the second embodiment of the present invention will be described in detail with reference to the drawings.

[0097] The WWW server 240 is a web page creation unit 25.
0 always provides the information input Web page.
Therefore, a community creator, a member candidate, or a member inputs a
The page is always available via the communication network 100.

Therefore, in the second embodiment of the present invention,
Community creation request (S1 in FIG. 3), community participation request (S3 in FIG. 3), message transmission request (S3 in FIG. 3)
5) A request for leaving information from the community (S7 in FIG. 3) and a request for dissolution of the community (S9 in FIG. 3) are used for inputting information provided by the WWW server 240 in addition to the transmission according to the first embodiment. It can be sent using a web page. In this case, these community generation requests and the like are transmitted to the Web page creation unit 250 via the WWW server 240.

In the second embodiment of the present invention, the server 200 generates a community (S2 in FIG. 3), adds a candidate member to the community (S4 in FIG. 3), and delivers a message (S4 in FIG. 3). The processing of S6 in FIG. 3 and the withdrawal of the member from the community (S8 in FIG. 3) are executed by receiving a community participation request or the like by the mail server 210, or by using a Web page for inputting information. It can also be executed by receiving the transmitted community participation request and the like by the WWW server 240.

Next, the WWW server 240, the Web page creation unit 250, the mailing list registration unit 221, and the mailing list management unit 222 will be specifically described. (Specific description of the WWW server 240)

The WWW server 240 is connected to the communication network 1
Via 00, a request is received from a web page for inputting information. Then, the WWW server 240 transmits the request to the Web page creation unit 250. (Web page creation unit 25
Specific description of 0)

[0102] Web page creation section 250 receives a request from communication network 100. Web page creation part 2
50 checks whether the received request is a community generation request accompanied by a mailing list registration request.

If the received request is a community generation request accompanied by a mailing list registration request, the request is transmitted to the mailing list registration unit 221. On the other hand, if the received request is another request, the Web page creation unit 250 transmits the received request to the mailing list management unit 222.

Further, when receiving a request from the mailing list registration unit 221 or the mailing list management unit 222 to create a web page for error notification, the web page creation unit 250 creates a web page for error notification,
For community creators, members or potential members
It is presented via the WWW server 240. Further, the web page creation unit 250 sends the mailing list management unit 222
Upon receiving a request to create a notification web page or a message web page, create a notification web page that discloses various notifications or a message web that discloses the contents of the message in the message transmission request. A page is created and presented to the community creator, member or candidate member via the WWW server 240. (Specific description of the mailing list registration unit 221)

The mailing list registration unit 221 receives a community generation request accompanied by a mailing list registration request transmitted from the web page creation unit 250 or the mail server 210, and performs processing. The processing content is the same as the processing performed by the mailing list registration unit 221 according to the first embodiment of this invention. The transmission of the error notification to the community creator in S38 in FIG. 6 is performed by the mailing list registration unit 221 requesting the Web page creation unit 250 to create an error notification Web page. (Specific description of the mailing list management unit 222)

The mailing list management section 222 receives a community creation request, a community participation request, a message transmission request, or a command from the web page creation section 250 and performs processing. The processing content is the same as the processing performed by the mailing list management unit 222 of the first embodiment. The transmission of the error notification in S48 and S53 in FIG. 7 is performed by the mailing list management unit 222 requesting the Web page creation unit 250 to create a Web page for error notification. Further, S4 in FIG.
4, a notification for notifying that the community participation requester of S50 in FIG. 7 has joined the community, a notification for notifying that the member of S56 in FIG. 7 has left the community, a notification of FIG. S58
Is notified by the mailing list management unit 222 requesting the Web page creation unit 250 to create a notification Web page.

The transmission of the message in S47 of FIG. 7 is performed by the mailing list management unit 222 requesting the Web page creation unit 250 to create a message Web page.

Note that the WWW server 240 sends a community creation request (S1 in FIG. 3), a community participation request (S3 in FIG. 3), a message transmission request (S5 in FIG. 3), and a withdrawal request from the community. (S7 in FIG. 3), it is also possible to receive the contents of the community dissolution request (S9 in FIG. 3) sequentially instead of receiving them at once. For example,
When making a community generation request, the community creator first inputs only his / her own mailing address (FIG. 2A). Then, after the authentication process (S32 in FIG. 6) for the mailing list registration unit is completed, the mailing list registration unit requests the community creator for contents necessary for the mailing list registration request such as the mailing list address (FIG. 2 (a)). I do. Then, the community creator who has received the request inputs a content necessary for the mailing list registration request. In this method, a community creator, a member, or a candidate member can execute a process interactively with the WWW server 240.

When the mailing list management unit issues a notification, the mail server 210 may request the mail server 210 instead of the web page creation unit 250 to execute all or a part of the notification. For example, only the invitation notice may be sent by e-mail as in the first embodiment.

Next, a third embodiment of the present invention will be described in detail with reference to the drawings.

Referring to FIG. 9, the third embodiment of the present invention includes a user terminal 110, a communication network 100, a server 200 and a community as in the first embodiment of the present invention. A recording medium 300 on which a generation program is recorded is provided. The recording medium 300 may be a magnetic disk, a semiconductor memory, a CD-ROM, or another recording medium. The server 200 includes a data processing unit 400
And a storage unit 500.

The community generation program is stored in the recording medium 3
00 to the server 200 and the data processing unit 40
0, and generates a mailing list member data storage unit 230 in the storage unit 500. Data processing unit 40
No. 0 executes the same processing as the processing by the mail server 210, the mailing list registration unit 221, the mailing list management unit 222, and the mail processing / transfer unit 223 in the first embodiment under the control of the community generation program.

Next, a fourth embodiment of the present invention will be described in detail with reference to the drawings.

Referring to FIG. 9, a fourth embodiment of the present invention comprises a user terminal 110, a communication network 100,
The server includes a server 200, and further includes a recording medium 300 that records a community generation program. This recording medium 3
00 may be a magnetic disk, semiconductor memory, CD-ROM, or other recording medium. The server 200 includes a data processing unit 400 and a storage unit 500.

The community generating program is stored in the recording medium 3
00 to the server 200 and the data processing unit 40
0, and generates a mailing list member data storage unit 230 in the storage unit 500. Data processing unit 40
0 indicates the mail server 210 and the WWW server 2 in the second embodiment under the control of the community generation program.
40, the same processing as the processing by the Web page creation unit 250, the mailing list registration unit 221, the mailing list management unit 222, and the mail processing / transfer unit 223 is executed.

[0116]

The effect of the present invention is to dynamically generate a community consisting only of users who intend to participate in communication in consideration of the situation of the user at the time of creating the community. Will be possible. As a result, it is possible to prevent an unnecessary or annoying message from reaching the mailing list member candidates.

The reason is that at the start of the mailing list communication, an invitation notification is transmitted to the candidate members, and a message is transmitted only between those who have expressed their intention to participate. This is because only the invitation notification is transmitted to the user.

[Brief description of the drawings]

FIG. 1 is a block diagram showing a configuration of a first embodiment of the present invention.

FIG. 2 is a diagram showing a specific example of mailing list management information according to the first embodiment of the present invention.

FIG. 3 is a flowchart showing the operation of the first embodiment of the present invention.

FIG. 4 is a diagram showing a specific example of a community generation request according to the first embodiment of this invention.

FIG. 5 is a flowchart showing the operation of the mail server according to the first embodiment of the present invention.

FIG. 6 is a flowchart showing the operation of the mailing list registration unit according to the first embodiment of the present invention.

FIG. 7 is a flowchart showing the operation of the mailing list management unit according to the first embodiment of the present invention.

FIG. 8 is a block diagram showing a configuration of a second exemplary embodiment of the present invention.

FIG. 9 is a block diagram showing the configuration of the third and fourth embodiments of the present invention.

[Explanation of symbols]

 REFERENCE SIGNS LIST 100 communication network 110 user terminal 200 server 210 mail server 220 mailing list registration management section 221 mailing list registration section 222 mailing list management section 223 mail processing / transfer section 230 mailing list member data storage section 240 WWW server 250 web page creation section 300 recording medium 400 data Processing unit 500 Storage unit

Claims (29)

[Claims] 1. A community generation request is received from a member candidate registered in a mailing list, a community composed of members performing communication among the member candidates is generated, and the member candidate is invited to the community. Transmitting a notification, receiving a community participation request for joining the community from the member candidates that have received the invitation invitation to the community, and causing the candidate members that have transmitted the community participation request to join the community. And a community generation system. 2. A community generation request accompanied by a mailing list registration request is received from a user, a mailing list is created, and among the member candidates registered in the mailing list,
A community composed of members performing communication is generated, an invitation notification to the community is transmitted to the candidate members registered in the mailing list, and the community participation is performed from the candidate members receiving the invitation notification to the community. A community participation request for receiving the community participation request, and causing the candidate member who transmitted the community participation request to participate in the community. 3. When the community including the community generation request or the community participation request is received and the community is not generated, it is determined that the mail includes the community generation request and the community is generated. 4. The method according to claim 1, wherein if the user who transmitted the mail is not included in the members of the community, it is determined that the mail includes the community participation request. Community generation system. 4. When a candidate member who has transmitted a request to participate in the community is caused to participate in the community, the candidate member who transmitted the request to participate in the community participated in the community with respect to a member participating in the community. 4. The community generation system according to claim 1, wherein a notification for notifying the user is issued. 5. The system according to claim 1, wherein upon receiving a request for leaving a member of the community from the community, a member who is a sender of the request for leaving the community is left from the community. 5. The community generation system according to 2, 3, or 4. 6. As a result of leaving a member who is a sender of a request for leaving from the community from the community,
The community generation system according to claim 4, wherein when the number of people participating in the community becomes one, the community is dissolved. 7. The community according to claim 1, wherein the community is dissolved upon receiving a request for dissolution of the community from a member participating in the community.
7. The community generation system according to 4, 5, or 6. 8. The system according to claim 6, wherein when the community is dissolved, a notice for notifying that the community has been dissolved is transmitted to members participating in the community. The described community generation system. 9. A mailing list member data storage unit for storing information relating to a mailing list; receiving a community generation request from a registered member candidate of the mailing list; generating the community; and sending an invitation notification to the member candidate to the community. Requesting transmission, and receiving a community participation request from the member candidate, a mailing list managing unit for causing the member candidate having transmitted the community participation request to participate in the community; and transmitting an invitation notification from the mailing list managing unit to the community. In response to the request, create a notification of invitation to the community, and refer to the mailing list member data storage unit to send a notification of invitation to the community to a candidate member registered in the mailing list. Community generation system characterized in that it comprises a processing and transfer unit. 10. A mailing list registration unit that receives a community generation request accompanied by a mailing list registration request from a user, outputs information on the mailing list to a mailing list member data storage unit, and outputs the community generation request to a mailing list management unit. A mailing list member data storage unit for storing information about the mailing list received from the mailing list registration unit; and receiving the community generation request, generating the community, and sending an invitation notification to the community to a candidate member registered in the mailing list. Request transmission,
When a community participation request is received from the member candidate, a mailing list management unit that causes the member candidate that has transmitted the community participation request to participate in the community, and a transmission request for an invitation notification to the community from the mailing list management unit, A mail processing / forwarding unit that creates the community invitation notification, refers to the mailing list member data storage unit, and transmits the community invitation notification to the candidate members registered in the mailing list. And a community generation system. 11. When the mailing list management unit receives the mail including the community generation request or the community participation request, the mailing list management unit considers the mailing list member data storage unit, and if the community is not generated, It is determined that the mail includes the community generation request, and if the community has been generated and the person who sent the mail is not included in the members of the community, the mail includes the community participation request. The community generation system according to claim 9, wherein a determination is made. 12. A notification for notifying that the candidate member having transmitted the community participation request has joined the community when the mailing list management unit causes the candidate member having transmitted the community participation request to participate in the community. Requesting the mail processing / forwarding unit to send the mail, the mail processing / forwarding unit receives the request, creates the notification, refers to the mailing list member data storage unit, and registers the member registered in the mailing list. The community generation system according to claim 9, 10 or 11, wherein the notification is transmitted to a candidate. 13. The mailing list management unit, upon receiving a withdrawal request from a community of a member participating in the community and leaving the member who is the sender of the withdrawal request from the community, from the community, The mailing list management unit requests a mail processing / forwarding unit to transmit a notification for notifying that the member has left the community, and the mail processing / forwarding unit creates the notification in response to the request. 13. The community generation system according to claim 9, 10, 11 or 12, wherein the notification is transmitted to a member candidate registered in the mailing list with reference to the mailing list member data storage unit. 14. The method according to claim 1, wherein the mailing list management unit leaves the member who is the sender of the request to leave the community from the community, and if the number of members participating in the community becomes one, 14. The community generation system according to claim 13, wherein the community is dissolved. 15. The community according to claim 9, wherein the mailing list management unit receives the request for dissolution of the community from a member participating in the community and dissolves the community. Or 1
5. The community generation system according to 4. 16. The mailing list management unit requests the mail processing / transfer unit to create a notification for notifying that the community has been dissolved when the community is dissolved, and the mail processing / forwarding unit Receiving the request, creating the notification, referring to the mailing list member data storage unit, and transmitting the notification to a candidate member registered in the mailing list. The community generation system according to 1. 17. The system according to claim 1, wherein at least the community creation request and the community participation request are received at a community management address.
4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 1
The community generation system according to 4, 15, or 16. 18. A community creation request web page for the community creation request, and a community participation request web for the community participation request.
A Web page creation unit for providing a page or the like is provided.
The community generation system according to 5, 16, or 17. 19. A process for receiving a community generation request from a member candidate registered in a mailing list, a process for generating a community, a process for transmitting a community invitation notification to the member candidate, and a process for transmitting to the community A program for causing a computer to execute a process of receiving a community participation request for participating in the community from a member candidate that has received the invitation notification of the above, and a process of causing the candidate member having transmitted the community participation request to participate in the community A recording medium on which is recorded. 20. A process for receiving a community generation request accompanied by a mailing list registration request from a community creator; a process for creating the mailing list; a process for generating a community; A process of transmitting an invitation notification to a community; a process of receiving a community participation request for participating in the community from the member candidates that have received the invitation notification; and joining the candidate member that has transmitted the community participation request to the community A recording medium characterized by recording a program for causing a computer to execute a process for causing the program to execute. 21. A process for judging that the mail includes the community generation request when the community is not generated when the mail including the community generation request or the community participation request is received; Is generated, and when the user who sent the mail is not included in the members of the community, a program for causing a computer to execute a process of determining that the mail includes the community participation request is recorded. 21. The recording medium according to claim 19, wherein: 22. When a candidate member who has transmitted the community participation request participates in the community, the candidate member who transmitted the community participation request has participated in the community for members participating in the community. 22. The recording medium according to claim 19, wherein a program for causing a computer to execute a process of giving a notification for notifying the user is recorded. 23. A program for causing a computer to execute a process of receiving a leaving request of a member participating in the community from the community and a process of leaving a member who is a sender of the leaving request from the community. 23. The recording medium according to claim 19, wherein the program is recorded. 24. If the number of members participating in the community becomes one as a result of performing a process of leaving a member who is a sender of a request to leave the community from the community, the community is dissolved. The recording medium according to claim 23, wherein a program for causing a computer to execute a process is recorded. 25. A program for causing a computer to execute a process of receiving a request for dissolution of the community from members participating in the community and a process of dissolving the community. 25. The recording medium according to 20, 21, 22, 23 or 24. 26. A method for causing a computer to execute a process of transmitting a notification for notifying that the community has been dissolved to members participating in the community when performing the process of breaking up the community. 26. The recording medium according to claim 24, wherein the program is recorded. 27. A program for causing a computer to execute a process for creating a community creation request web page for the community creation request and a community creation request web page for the community participation request. Claims 19, 20, 21, 2
27. The recording medium according to 2, 23, 24, 25 or 26. 28. A user terminal sends a community creation request for a member candidate registered in a mailing list to a server, wherein the server receives the community creation request, creates a community, and The invitation notification to the community is transmitted to the user terminal.The user terminal receives the invitation notification to the community, and receives the invitation notification to the community from among the candidate members who wish to participate in the community. A community generation method, comprising transmitting a community participation request to the server, wherein the server receives the community participation request, and causes a candidate member having transmitted the community participation request to participate in the community. 29. A user terminal sends a community creation request accompanied by a community creator's mailing list registration request to a server, and the server receives the community creation request, creates a mailing list, and creates a community. Transmitting, to a user terminal, an invitation notification to a community for a member candidate registered in the mailing list, wherein the user terminal receives the invitation notification to the community; Transmitting a community participation request from the member candidate who wishes to participate in the community to the server, wherein the server receives the community participation request, and causes the member candidate having transmitted the community participation request to participate in the community. Community generation method.