WO2005008983A2 - Procede de gestion du courrier electronique de maniere a exclure les messages non demandes de type « pourriel » - Google Patents

Procede de gestion du courrier electronique de maniere a exclure les messages non demandes de type « pourriel » Download PDF

Info

Publication number
WO2005008983A2
WO2005008983A2 PCT/IB2004/050687 IB2004050687W WO2005008983A2 WO 2005008983 A2 WO2005008983 A2 WO 2005008983A2 IB 2004050687 W IB2004050687 W IB 2004050687W WO 2005008983 A2 WO2005008983 A2 WO 2005008983A2
Authority
WO
WIPO (PCT)
Prior art keywords
message
sender
file
iddb
received
Prior art date
Application number
PCT/IB2004/050687
Other languages
English (en)
Other versions
WO2005008983A3 (fr
Inventor
Diego Angelo Tomaselli
Original Assignee
Diego Angelo Tomaselli
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Diego Angelo Tomaselli filed Critical Diego Angelo Tomaselli
Publication of WO2005008983A2 publication Critical patent/WO2005008983A2/fr
Publication of WO2005008983A3 publication Critical patent/WO2005008983A3/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/21—Monitoring or handling of messages
    • H04L51/212—Monitoring or handling of messages using filtering or selective blocking

Definitions

  • the present invention relates to a method and to a corresponding anti-spam computer product to avoid accumulating undesired messages in an electronic mailbox.
  • spam messages will be continued to be referred to, by designating under this term those not requested e-mail messages, sent in a way so that the sender cannot be easily detected, for advertisement purposes or other.
  • sofar limit to filter the incoming messages based upon predetermined rules, for example, by analyzing the words included in the message subject or in the body text thereof and eliminating those messages containing the words which have been previously inserted in a file of "not allowed" words.
  • the system of this most advanced type can be easily sidestepped thanks to a specific utilization of the search engines: in fact, currently the safest way for identifying an advertising mail is to isolate and search for the Internet address thereat the advertisement in question is linked, since the words utilized for the advertisement thereof can be easily created in a random way, whereas the advertisement subject, that is the advertised Internet site, cannot be always different, since this would have a cost; therefore, the most advanced anti-spam systems create lists of internet sites advertised inside the spam and they check if a mail is spam or not through the search for such addresses inside the messages subjected to the check.
  • the spammer in fact, needs only to replace the link to the site to be advertised with a link to a search engine, by re-setting such link so that the opening thereof automatically generates a search for such search engine and the result of such research shows the advisement subject site; in order to reach this aim with the certainty to make result just the wished site among the search's results, the spammer needs only to enter some specific key words inside the advertised site and to utilize such words in the pre-set search: since they are not common words, but specific key words, the spammer can be almost sure that the search will generate the advertisement subject site only as visible result to the user.
  • a possible solution is to create a computer program which browses inside the links existing inside the message subjected to the check (that is, by starting the search set by the spammer), to search for possible links inside the so-opened page (that is among the search results) and to check thereamong the presence of a possible internet site causing spamming, that is already detected previously as end target of not wished advertisement messages.
  • An object of the present invention is to solve the problems mentioned above, by providing a method for the anti-spam management of an e-mail message received in a mailbox, as described in claim 1.
  • An additional object of the present invention is to provide a method for identifying hidden links starting from a first link to a web page included in an e-mail message, as defined in claims 32 or 33.
  • An additional object of the present invention is to provide a computer product for implementing a method according to the present invention, as described in claim 34 or 35.
  • the main advantage of the method according to the present invention is given by the fact that it acts in an extremely effective and automatized way, without requiring any intervention and/or any action by the users (sender and/or recipient).
  • the system according to the present invention intervenes cyclically in an automatic way on the received messages, checking the legitimacy thereof. Such check does not depend upon any action of the message's sender (reply to the request for confirmation), thus the management process of each message is considerably fastest and easiest.
  • the invention does not necessarily requires that the received messages be held in a stand-by state before being able to be checked and/or read, but it checks the messages when they are already in the InBox, without moving anyone thereof and therefore leaving at the user's disposal, in any case, all the messages, thereamong there could be some urgent.
  • This does not exclude the possibility of maintaining separate, or however visually distinct to the user's sight, the surely secure messages from the ones still in the checking step: in fact, in order to distinguish them it is sufficient considering as checked the messages coming from authorized senders.
  • the computer program according to the present invention is executed at predefined intervals. It does not act upon receiving a new message only, but it monitors continuously the content of the user's mailbox.
  • figure 1 is a flow chart schematizing roughly the program's operating principle which implements the method according to the present invention
  • figure 2 is a flow chart related to the program portion which processes and manages the received messages considered with doubtful sender
  • figure 3 is a flow chart illustrating the complete flow of the method according to the present invention.
  • the method according to the present invention exploits a feature common to almost all spammers (under this term the users sending spam messages are designated hereinafter), that is the fact of sending spam by a not-existing e-mail address, or of anonymous and free type, or stolen type.
  • This feature is substantially always checked for obvious reasons, both legal (since in many countries, as in Italy, their activity is illegal) and practical ones. In fact, should they use real addresses it would be simple to filter them, since it would be sufficient to lock the sender, who, being real, could not result always different, as it happens nowadays.
  • the object of the method according to the present invention is to "manage" the messages coming from unknown senders (that is, which previously have not ever written to the sender's address) to understand if it is a valid and functioning e-mail address or if it is an address invented by a spammer and therefore a false or stolen one.
  • the sender of an e-mail message will be continued to be referred to, wishing to designate under this term the sender's e-mail address or the sender's domain or the sender's domain owner of the checked e-mail message.
  • the flow chart of figure 1 roughly schematizes the working principle of the program implementing the method according to the present invention.
  • the program checks the presence of e-mail messages in a user's mailbox. Under the term InBox also possible subfolders are wanted to be included, which, for example, could be useful to maintain the checked messages separated from the ones still to be subjected to the check. If there are no received messages, the program ends (remaining obviously active to check the possible presence of new messages at regular intervals), otherwise it proceeds in analyzing the first message (the messages' sequence is not important, it could be for example the reception order, that it from the oldest to the most recent message). Then, the received message is processed and managed, as it will be explained in details hereinafter. Then, if there are no additional messages, the program ends, otherwise it proceeds in analyzing the subsequent message.
  • the program can be executed cyclically according to pre-established time intervals (even if this does not exclude the activation thereof upon receiving a new message).
  • the regularity and the frequency of such intervals do not change the system effectiveness, but the efficiency thereof only.
  • the following figure 2 is a flow chart related to the program portion which processes and manages each of the received messages, when it is interpreted as a message with doubtful sender.
  • the idea underlying the invention is to analyze all the received messages existing in the InBox, without moving any of them (thus leaving at the user's disposal all messages, thereamong there could be urgent ones, even if this does not exclude the possibility of distinguishing the secure messages from the ones still to be subjected to the check).
  • IDDB codes corresponding to the sent test message.
  • the ID code created in a wholly random way by the system, can be numerical or alphanumerical, since it is unique and biunivocally associated to a test message. Then, the ID code is written in the sent test message (in the message's subject or body text or even inside the e-mail addresses of the involved users) and it will be then extracted by a possible "delivery error” or “denial” message, if received, for the subsequent checks, as it will be explained in more details hereinafter.
  • the sender the sender's e-mail address and the alias thereof
  • the subject of the received message the subject of the received message
  • despatch date and time of the test message will be then utilized to check certain conditions and to perform then pre-established operations for managing the messages.
  • the flow chart of figure 3 illustrates the whole flow, but not limitative, of the method according to the present invention.
  • the program is activated at regular time intervals, for example each minute, but this time it can vary according to the required performances or it can become also irregular (for example if activated upon receiving a new message) without overloading the system, in order to monitor constantly the user's mailbox.
  • the method provides a step of eliminating (or moving) the received message from the user's mailbox, in case the sender is included in the first file of blocked senders or, indeed, is clearly wrong or wholly absent. After the elimination, it is always appropriate to send a notice to the sender. ⁇ Are there ID in the msg?> On the contrary, if the sender's address is not among the locked ones, the program checks if the received message is a delivery error or denial message following a previously sent test message.
  • the extracted ID is not included in the IDDB file, it could be, for example, a test message coming from another user utilizing the same system.
  • the method provides a step of checking if a message was previously sent which, in turn, was subjected to a test by another user utilizing the same system and who thus generated the currently received message.
  • Such check can be carried out automatically if the system can access to a file of sent mail; if this is not possible, the system, however, can translate the test message into the user's language, obviously maintaining unchanged the references to the message subjected to the check.
  • This translation avoids that a spammer tries accessing to the user's mailbox by adding a fictitious ID inside the advertisement thereof, considering that said translation would wholly eliminate what is not pertinent to a correctly formatted test message: in other words, the translation would consist in searching inside the message for the fields related to the subject, to the despatch date and to the recipients of the message subjected to the check, in order then to utilize them to create again a test message corresponding to what is expected by the user, both as far as the language is concerned and as far as the corresponding explanation related to the system operation (that is, basically the instructions useful to deny to have ever sent the message in question) is concerned.
  • the method provides a step of checking if the sender's address is included in a third file of authorized senders. ⁇ Is the sender or domain authorized?> If the sender's address (or the sender's mail domain) results in the file of the senders authorized to send mail to the user, the program continues without intervening and it proceeds in analyzing possible subsequent messages, otherwise additional control and/or check steps are activated.
  • the messages the size thereof exceeds a pre-established threshold can be considered as authorized, since the spammers have to send millions of messages in order to have an economic gain and therefore they cannot allow themselves to send too big messages. Furthermore, it may happen that the user has sent manually a message to a wrong address.
  • a message's content includes references bringing back to a message previously sent by the user (for example, if the message includes the subject or the address of a recipient equal to what has been found in the sent mail) since the delivery service shows these data indeed to communicate that a certain message has not been delivered to a certain address.
  • such message can be considered as coming from an authorized sender, even if only thanks to this particular content thereof (the reference to a message sent manually by the user). In this way, the user is informed about a failed delivery, but a possible spammer cannot utilized this input way since he/she is not able to know what the user has previously sent manually.
  • the method provides a step of generating a new ID (for example, a random number) and of associating such ID to a test message to be sent to the sender of the received message, together with a brief text explaining the function thereof and thus explaining that the test message is used only to check that the sender's address does not generate errors and to confirm that the sender's address has not been falsified.
  • the test message includes references to the message subjected to the check, for example stating the subject, the despatch date and the recipients.
  • the method advantageously provides the elimination of possible ID existing in the original message, which is enclosed to (or simply mentioned in) the test message which, once received, can be then eliminated by the user (if also the sender adopts the same anti-spam system, the test message recognized as such can be deleted automatically) or, in case the user who receives it does not recognize to have ever sent the message in question (enclosed or mentioned by the test message), he/she could also signal to not recognize it (to deny it).
  • the "denial" could occur in a semi-automatic way, for example by pressing a button or a hyperlink included in the test message, so that this does not automatically generate a message replying to the test message, which still includes the sent ID, in order to be able to be recognized by the program.
  • the use of a hyperlink can involve the advantage of distinguishing with greatest certainty the ones which are really denial messages from the ones which could be simple requests for clarification sent as reply to the test message.
  • Another possible technique to try to minimize this kind of risk (the sender asks for clarifications and he/she replies to a test message, but he/she does not wish to deny to have sent a message) is constituted by the proper modification of the alias of the Reply-To field, so that the denials and the possible requests for clarification arrive always at the same address, however allowing the receiving system to distinguish the requests for clarification (that is the simple replies) since the corresponding alias results to be modified as shown in the Reply-To field.
  • the test message includes a hyperlink enabling the sender to deny, that is to send a reply, but this time without modifying the alias as shown by the Reply-To field.
  • the modification of the alias in the Reply-To field can be utilized however to further inform the user who is going to reply to a test message that a reply despatch constitutes a denial and therefore the corresponding message, therefor the test message has been sent, will be deleted, if he/she proceeds in replying to the test message.
  • the program proceeds in storing in the IDDB file the data of the managed message. In particular, as already illustrated, the ID, the sender, the subject (or the message's body text) and the despatch time of the test message.
  • the flow can proceed in analyzing a possible subsequent message, if existing, otherwise ending by waiting for the arrival of new messages.
  • the sender of the received message is the same one stored in the record of the IDDB file corresponding to the ID extracted from the received message, then it means that it is not a real signalling error and the sender has a real address, otherwise the reply containing the ID would have come from a third server and not from the sender directly (typical in case of error).
  • the case can be brought back wherein whoever receives a test message replies thereto (and denies it) in order not to recognize the paternity thereof and in this case it would not be correct blocking the sender by inserting him her in the list of the blocked senders.
  • the method according the invention preferably can be repeated periodically, according to a first pre-established period of time, for example each minute, so as to detect substantially in real time the received new messages and to manage them according to the rules described sofar, but it can also be activated upon receiving a new message.
  • the method according to the present invention can include a step, repeated periodically too, of eliminating from the file all the old registrations carried out before a pre-established period, for example 24 hours.
  • Such step of eliminating all old registrations includes a process which analyzes the IDDB file and it acts on the oldest registrations (for example 24 hour or more old), by deleting them. Practically, it "clears" the file (the error messages usually arrive within 24 hours). Moreover, upon deleting the registrations, advantageously this process can add the corresponding addresses in the file of the authorized addresses, since for these users no error or denial has arrived within 24 hours from the test message despatch. In this way, in future the test message will not ever sent to these senders. Obviously, this step can be subjected to the user's confirmation, who can decide then if authorizing the single sender in question or the whole domain thereof.
  • the method according to the present invention can also include a step of storing the sender's address in the file of the blocked addresses, when the received message is eliminated manually from a user's mailbox without being read. In case, such registering step can be conditioned to a confirmation step by the user.
  • Example 1 A "real" user A (not a spammer) sends an e-mail to the user B (who is currently using a computer program implementing the method according to the present invention), the subject thereof is, for example, "curriculum vitae".
  • the e-mail system of B receives the message of A.
  • the anti-spam program When the anti-spam program is executed, it detects the presence of the message received in the mailbox (InBox) of B. Then, it analyzes the message, in particular it checks the sender' address thereof (for example userA@users.com), which does not exist in the file of blocked addresses. Then, the system proceeds in analyzing the whole content of the message, searching for a ID in the message's subject, in the message's text and in the names of possible enclosures.
  • the program checks if the sender userA@users.com is instead in the file of the authorized addresses, but considering that the sender userA@users.com is unknown, the search result is negative. Before proceeding in sending a test message to the user A, the program checks if in the IDDB file a registration of a test message sent to the same userA@users.com already exists, so as not to enter an endless loop. Considering that it is the first time that userA@users.com writes to B, it does not result any registration.
  • the program proceeds in generating a random ID, which, for example, could be 1234567, then it will proceed in sending a test message to userA@users.com, whose subject could be something like: "Curriculum Nitae -TEST MESSAGE ⁇ ID>1234567 ⁇ /ID>", and the content thereof could be "This mail has been sent by an automatic anti-spam system in order to check the existence and functionality of the userA@users.com address. If one wants to deny to have sent the enclosed message, click the button [DENY] (or reply to the present message)".
  • the test message then, includes as enclosure the message "curriculum vitae" sent originally from A to B (or it shows the data thereof, as the subject).
  • the button [DENY] only generates a message replying to the test message: if a user replies to the test message, this will be then interpreted as a denial. Then, the program stores in the IDDB file the data of the sent test message: to whom it was sent (userA@users.com), with which ID (123467), which was the message to be checked (curriculum vitae) and at what time it was sent (02/07/2003 - 17:03). In the meantime, the message of A can be marked, in case, as not yet checked or it can be moved in a subfolder. Then, the program waits for being re-started again at regular intervals to check the returning of possible error messages.
  • the system proceeds in doing nothing, in case it moves or marks this message too as not yet checked.
  • the message then, remains at disposal of the user B, who then arranges an appointment for the following week.
  • the function "clearing" the IDDB file finds the registration of the message "curriculum vitae" which, as it is not yet present, means that the test message sent to userA@users.com has not yet generated errors, therefore it proceeds in inserting the address of this sender in the file of authorized addresses and it deletes the corresponding registration from the IDDB. If the messages had been moved or marked, it provides in marking them as authorized or in moving them in the same folder of the authorized messages. Once arrived the following week, A sends to B a confirmation message for the appointment.
  • Example 2 A spammer user A sends an advertising email to B, the subject thereof is "Money for you" and the sender thereof results to be spammer@spammers.com. Considering that spamming is illegal and considering that the spammer does not want to be blocked by any kind of filter applied by the sender, the supplied address (spammer@spammers.com) is obviously false, so as to be easily changed and so as to make the real spammer difficult to be traced.
  • the mail system of B receives the mail of A and when the anti-spam program is started, it detects the presence of the message in the InBox of B and it starts to analyze it. This means that first of all it analyzes the sender, which, for example, is spammer@spammers.com, which cannot be found in the file of the blocked senders. Then, the system proceeds in analyzing the whole content of the message, that is it looks for a valid ID in the message's subject, in the message's text and in the names of possible enclosures. If it finds it, it extracts it and searches for the extracted ID inside the IDDB file. In example case the ID is not found, since it is an advertising message.
  • the system checks if the sender spammer@spammers.com is in the file of the authorized addresses, instead. But considering that the sender sparrimer@spammers.com is unknown, the search result is negative. Before proceeding in sending a test message to the user A, the system checks if in the IDDB file a registration of a test message sent to the same spammer@spammers.com already exists, so as not to enter an endless loop. Considering that it is the first time that spammer@spammers.com writes to B, no registration results.
  • the program proceeds in generating a random ID, which for example could be ABC123DEF, then it will proceed in sending a mail to sparnmer@spammers.com, the subject thereof could be for example: "Money for you -TEST MESSAGE ⁇ ID>ABC123DEF ⁇ /ID>", and the content thereof could be "This mail has been sent by an automatic anti-spam system in order to check the existence and functionality of the address spammer@spammers.com. If one wants to deny to have sent the enclosed message, click the button [DENY]".
  • the program stores in the IDDB file the data of the sent test message: to whom it has been sent (spammer@spammers.com), with which ID (ABC123DEF), which was the message to be checked (Money for you) and when it has sent it (02/07/2003 - 17:03).
  • the message of A can be marked, in case, as not yet checked or it can be moved in a subfolder.
  • the program waits for being re-executed at regular intervals to check the return of possible error messages.
  • the last mail server involved in the process (it is not important if it is the server of B or a third server) signals with a mail (for example "Mail Delivery Failure"", sent for example by "postmaster@servers.com") that the user spammer@sparnmers.com cannot receive email, enclosing the message sent thereto ("Money for you -TEST MESSAGE ⁇ ID>ABC123DEF ⁇ /ID>").
  • the mail system of B receives the error signalling mail (Mail Delivery Failure).
  • the program performs again all the checks as already described, but in this case in one of the message's enclosures, the string ⁇ ID> is found, which by convention precedes the univocal identification generated at time of the test message despatch.
  • the program extracts the identification comprised between ⁇ ID> and ⁇ /ID> (that is "ABC123DEF”) and it search for it inside the IDDB file, by finding it, together with the data related to the message. Then, it is checked that the sender of this message (postmaster@servers.com) is not the same registered in the IDDB file (spammer@spammers.com) and therefore, the program proceeds in blocking spammer@spammers.com definitively (as address which has generated an error signalled by a third server, postmaste@servers.com) in case asking for confirmation to the user B to block also all the domain spammers.com and the owner thereof (the firm or the person which results to be the owner of the mail domain), so that in future all messages coming from these individuals are automatically eliminated.
  • spammer@spammers.com definitively (as address which has generated an error signalled by a third server, postmaste@servers.com) in case asking for confirmation to the user B to block also all the domain spammers.com and the owner
  • the original message registered in the IDDB file (Money for you) is eliminated from the InBox of the user B, as well as the corresponding registration is deleted Then, the system eliminates also the error signalling message (Mail Delivery Failure). Then, the system proceeds in analyzing the remaining messages. If the system finds additional messages coming from spammer@spammers.com (or even only by spammers.com if the whole domain has been blocked), it will provide in eliminating them automatically.
  • the present invention has been described sofar according to a preferred embodiment thereof, illustrated by way of example and not for limitative purposes. It is to be meant that other embodiments can exist, all however comprised within the protective scope of the present invention, as defined by the enclosed claims.

Abstract

Procédé de gestion de messages électroniques reçus dans une boîte aux lettres électronique, ledit procédé ayant pour but d'exclure les messages non demandés de type « pourriel ». Ce procédé consiste à déterminer si un message reçu doit être considéré comme étant un message autorisé ou non autorisé, et, lorsque le message reçu n'est pas considéré comme étant un message autorisé, à envoyer un message à l'adresse de courrier électronique de l'expéditeur du message électronique reçu, à détecter la réception éventuelle d'un message de type « introuvable » ou « message refusé » correspondant au message test, à obtenir une information d'erreur, à traiter le message électronique reçu en fonction de l'information d'erreur, et enfin à effacer le message électronique de la boîte aux lettres lorsque l'information d'erreur fait état de la réception du message de type « introuvable » ou « message refusé ».
PCT/IB2004/050687 2003-07-17 2004-05-13 Procede de gestion du courrier electronique de maniere a exclure les messages non demandes de type « pourriel » WO2005008983A2 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
ITRM2003A000353 2003-07-17
IT000353A ITRM20030353A1 (it) 2003-07-17 2003-07-17 Metodo per la gestione anti-spam di messaggi di posta elettronica.

Publications (2)

Publication Number Publication Date
WO2005008983A2 true WO2005008983A2 (fr) 2005-01-27
WO2005008983A3 WO2005008983A3 (fr) 2005-05-12

Family

ID=29765923

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IB2004/050687 WO2005008983A2 (fr) 2003-07-17 2004-05-13 Procede de gestion du courrier electronique de maniere a exclure les messages non demandes de type « pourriel »

Country Status (2)

Country Link
IT (1) ITRM20030353A1 (fr)
WO (1) WO2005008983A2 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7996900B2 (en) * 2008-03-14 2011-08-09 Microsoft Corporation Time travelling email messages after delivery
US8387120B2 (en) 2007-07-25 2013-02-26 Szymon Lukaszyk Method and system of transferring electronic messages
CN110971447A (zh) * 2019-10-22 2020-04-07 视联动力信息技术股份有限公司 一种测试信息管理方法、装置、电子设备及可读存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1999010817A1 (fr) * 1997-08-26 1999-03-04 Christopher Alan Cobb Procede et systeme permettant de filtrer les messages electroniques
US20020198950A1 (en) * 1997-11-25 2002-12-26 Leeds Robert G. Junk electronic mail detector and eliminator
US20030009698A1 (en) * 2001-05-30 2003-01-09 Cascadezone, Inc. Spam avenger
US6546416B1 (en) * 1998-12-09 2003-04-08 Infoseek Corporation Method and system for selectively blocking delivery of bulk electronic mail
WO2003044617A2 (fr) * 2001-10-03 2003-05-30 Reginald Adkins Systeme de controle de courrier electronique autorise

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO1999010817A1 (fr) * 1997-08-26 1999-03-04 Christopher Alan Cobb Procede et systeme permettant de filtrer les messages electroniques
US20020198950A1 (en) * 1997-11-25 2002-12-26 Leeds Robert G. Junk electronic mail detector and eliminator
US6546416B1 (en) * 1998-12-09 2003-04-08 Infoseek Corporation Method and system for selectively blocking delivery of bulk electronic mail
US20030009698A1 (en) * 2001-05-30 2003-01-09 Cascadezone, Inc. Spam avenger
WO2003044617A2 (fr) * 2001-10-03 2003-05-30 Reginald Adkins Systeme de controle de courrier electronique autorise

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8387120B2 (en) 2007-07-25 2013-02-26 Szymon Lukaszyk Method and system of transferring electronic messages
US7996900B2 (en) * 2008-03-14 2011-08-09 Microsoft Corporation Time travelling email messages after delivery
US8327445B2 (en) 2008-03-14 2012-12-04 Microsoft Corporation Time travelling email messages after delivery
CN110971447A (zh) * 2019-10-22 2020-04-07 视联动力信息技术股份有限公司 一种测试信息管理方法、装置、电子设备及可读存储介质

Also Published As

Publication number Publication date
ITRM20030353A0 (it) 2003-07-17
WO2005008983A3 (fr) 2005-05-12
ITRM20030353A1 (it) 2005-01-18

Similar Documents

Publication Publication Date Title
US7596600B2 (en) System for selective delivery of electronic communications
US7412487B2 (en) Method and system for tracking receipt of electronic message
US6779022B1 (en) Server that obtains information from multiple sources, filters using client identities, and dispatches to both hardwired and wireless clients
CA2496313C (fr) Gestion de communication a journal d'instigation d'actions par jeton
US6266692B1 (en) Method for blocking all unwanted e-mail (SPAM) using a header-based password
US8194564B2 (en) Message filtering method
US9715676B2 (en) Method and system for confirming proper receipt of e-mail transmitted via a communications network
US20040093414A1 (en) System for prevention of undesirable Internet content
CN101652967B (zh) 用于减少电子消息的增殖的方法和系统
US20040267886A1 (en) Filtering email messages corresponding to undesirable domains
US20060149823A1 (en) Electronic mail system and method
US20070204043A1 (en) Method, system and apparatus for rejecting unauthorized or SPAM e-mail messages.
US20090044006A1 (en) System for blocking spam mail and method of the same
US20050125667A1 (en) Systems and methods for authorizing delivery of incoming messages
JP2008507005A (ja) オンライン詐欺解決法
CN104010085A (zh) 消息处理方法及装置
US8091118B2 (en) Method and system to optimize efficiency when managing lists of untrusted network sites
US8166113B2 (en) Access limited EMM distribution lists
WO2016156858A1 (fr) Système de commande et de gestion de courrier électronique
US8112482B1 (en) System and method for securing access to electronic mail
WO2005008983A2 (fr) Procede de gestion du courrier electronique de maniere a exclure les messages non demandes de type « pourriel »
CN116055440A (zh) 终端判断并过滤邮件安全内容的方法、装置、设备及介质
KR100528590B1 (ko) 저장된 스팸 메일을 재전송하고 스팸 룰을 변경하는 등의처리를 행하는 스팸 메일 처리 장치 및 방법, 그리고 이방법을 실행하는 프로그램을 기록한 컴퓨터로 읽을 수있는 기록매체
KR0148031B1 (ko) 메일 삭제 기능을 갖는 전자 메일 송수신 방법
US20230308521A1 (en) Management device, management method, and recording medium

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A2

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BW BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE EG ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NA NI NO NZ OM PG PH PL PT RO RU SC SD SE SG SK SL SY TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZM ZW

AL Designated countries for regional patents

Kind code of ref document: A2

Designated state(s): BW GH GM KE LS MW MZ NA SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LU MC NL PL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
122 Ep: pct application non-entry in european phase