KR20050042546A - System and method for managing spam mail - Google Patents

Abstract

The present invention includes a terminal such as a PC connected to the Internet; A sender mail server connected to the Internet; A mail server for recipients connected to the Internet; A member DB of the mail server for the recipient; Mail DB; Preliminary Spam DB; Main Spam DB; And it relates to a spam mail management system and a spam mail management method comprising a management program.

Description

Spam management system and spam management system {System and Method for Managing Spam Mail}

In order to explain the existing mail system, a widely used webmail system is described as an example.

1 is a structural diagram of a general webmail program. It is a structural diagram of a program 18 installed to implement a webmail service. As shown in FIG. 1, for a webmail service, an operating system (OS) 11 for operating a server system is first installed, and a DNS 12 for installing a domain on the operating system 11 and a mail is exchanged. MAIL Daemon program 13 can be installed, and other POP3 (14), IMAP (15), DATABASE (16), WEB SERVER (17), etc. are installed. These programs operate in interconnected operations and continue to evolve as the Internet evolves. Here, the program shown in FIG. 1 is only a part of it, and a program for other services may also be installed.

2 is a configuration diagram of a server device used for a conventional webmail service. As shown in FIG. 2, the server device 20 for the web mail service used in the related art includes a CPU 22 and a main memory 23 on the server board 21, and a main disk (for example, FIG. For example, a hard disk; 24 and a power supply device 25 are configured, and the Ethernet port 26 is formed so that the server device 20 provides Internet service. Figure 2 shows an example of the relevant components for the webmail service, other devices are omitted. Referring to FIG. 2, the operations of the programs for the conventional webmail service are described. The programs 12 to 17 for providing the webmail service described with reference to FIG. 1 are stored in the main disk 24, and these are all described above. It is operated from the main disk 24. The main disk 24 also stores user information and various data for webmail services. For example, it builds a variety of databases and stores a variety of data, including sent letters, inboxes, mail addresses and user-related information.

Based on the existing mail system, a technique for filtering spam mail based on the current sender is that when a user registers a sender's mail address of a received mail, the user can later refuse to receive mail from the same sender.

The existing spam filtering technology has a disadvantage in that an individual user creates a spam list using existing data, and thus does not effectively prevent new spammers.

Accordingly, an object of the present invention is to share a list of spammers by sharing a list of spammers among several members to increase the effectiveness of spam blocking, and to block malicious registrants among members, The same sender address cannot be registered in the spare Spam DB more than once, and the sender address registered more than a certain number of times in the Spam DB can be registered in the main Spam DB to improve the reliability of the spam list of the registered main Spam DB. Tag is attached to the mail sent from the sender's address registered in the preliminary Spam DB to notify the member that the mail is highly likely to be spam, and the user logs out without opening the tagged spam mail. Deletes the tagged spam mails in bulk and registers the sender's address in the preliminary spam DB to increase convenience. By opening the spam is not granted automatically deleted to remove or change the Tag, you, and delete a user opened a spam mail that Tag is given to the registered address of the sender to the preliminary spam DB.

Hereinafter, an embodiment of the present invention will be described in detail with reference to the accompanying drawings.

3 is a schematic diagram of a spam mail management system according to the present invention.

As shown in FIG. 3, the spam mail management system includes a terminal 100 such as a PC connected to the Internet 200; A sender mail server 300 connected to the Internet 200; A mail server 400 for a receiver connected to the Internet 200; A member DB 410 of the mail server 400; Mail DB 420; It consists of a spare Spam DB 430 and a main Spam DB 440.

In addition, the mail server 400 manages the member DB 410, the mail DB 420, the preliminary Spam DB 430 and the main Spam DB 440, and the management program 450 for controlling the spam mail management method described later It includes.

4 and 5 are partial flow charts showing a spam mail management method according to the present invention.

Recipient mail server 400,

When the member's mail is received, (step S210).

Search the main Spam DB 440 to see if the sender's address is in the main Spam DB 440, and if there is no sender's address in the main Spam DB 440,

Search the preliminary Spam DB 430 to see if the sender's address is in the preliminary Spam DB 430, and if there is no sender's address in the preliminary Spam DB 430,

Check if the mail has been deleted by the member, and if the mail has been deleted by the member (step S240),

Register the caller's address in the member DB 410 and the preliminary Spam DB 430, and operate the registration counter (step S250) to record the registration count (i) 1, and (step S260 and step S270).

In step S220, if there is an address of the sender in the main Spam DB 440, the mail is deleted,

If there is an address of the sender in the preliminary Spam DB 430 in step S230, a tag is assigned to the corresponding mail (step S300).

Check whether the member opens the mail to which the tag is attached (step S310), and when the member opens the mail to which the tag is attached,

Remove or change the tag of the mail, and (step S320)

Check if the member deletes the mail, and if the member deletes the mail (step S330),

Check the member DB 410 to see if the member has registered the sender address (step S340). If the member has not registered the sender address, operate the registration counter to accumulate the number of registrations (i). And (step S270)

Check whether the registered number (i) accumulated by the registration counter exceeds a predetermined number (K), and (step S280) If the registered number exceeds the predetermined number (i> K)

Register the caller address in the main Spam DB 440, and (step S290).

If the member does not open the mail to which the tag is assigned in step S310, check whether the member logs out, and if the member logs out (step S350),

Delete the message, (step S360)

The member DB 410 is searched to see if the member has registered the sender address. (Step S340)

In order to check whether the member has registered the caller address in step S340, the member DB 410 includes a list of caller addresses that each member has deleted and has passed through step S270.

The registration counters of step S260 and step S270, by the management program 450, records the first 1 through step S250 (i = 0; i = i + 1) or 1 to the accumulated number of registrations through step S340. A simple counter that adds up. (i = i + 1)

As a method of tagging the mail in step S300, a method of attaching a specific code to the header of the mail may be used.

According to the present invention, the sender address registered in common by multiple users is registered in the main spam DB, and the same member cannot be registered more than once, thereby increasing the reliability of the main spam DB and registering the sender address registered in the preliminary spam DB. By assigning a tag to an e-mail sent from, it is possible to notify the member in advance that the e-mail is likely to be spam.

1 is a structural diagram of a general webmail program,

2 is a configuration diagram of a server device used for a conventional webmail service;

3 is a schematic diagram of a spam management system according to the present invention;

4 is a partial flow chart showing a spam mail management method according to the present invention;

5 is a partial flowchart illustrating a spam mail management method according to the present invention.

<Description of the code | symbol about the principal part of drawing>

100: terminal 200: Internet

300: mail server (for sender) 400: mail server (for receiver)

410: member DB 420: mail DB

430: Spare Spam DB 440: Primary Spam DB

450: management program

Claims (4)

A terminal such as a PC connected to the Internet; A sender mail server connected to the Internet; A mail server for recipients connected to the Internet; A member DB of the mail server for the recipient; Mail DB; Preliminary Spam DB; Main Spam DB; And a management program comprising: a spam mail management system. The method of claim 1, The member DB is a spam mail management system, characterized in that it comprises a sender address list of the mail deleted by each member. The method of claim 1, The management program controls the spam mail management method of claim 4, characterized in that it comprises a registration counter spam mail management system. In the spam mail management system having the configuration of claim 1, claim 2 and claim 3, The recipient mail server is Receiving the member's mail, searching the main Spam DB to determine whether the sender's address is in the main Spam DB; Retrieving the preliminary Spam DB to determine whether the sender's address is in the preliminary Spam DB; Checking whether the mail has been deleted by the member; Registering the caller's address in the member DB and the spare Spam DB; Deleting the mail; Tagging the mail; Confirming whether the member opens the mail to which the tag is assigned; Removing or changing a tag of the mail; Confirming whether the member deletes the mail; Checking whether the member has registered the sender address by searching the member DB; Operating the registration counter to accumulate and record the number of registrations; Checking whether the number of registrations accumulated by the registration counter exceeds a predetermined number of times; Registering the caller address with the main Spam DB; Spam management method comprising the step of confirming that the member is logged out.