[go: up one dir, main page]

WO2006010998A2 - Procede et systeme pour decourager un expediteur de communiquer un message electronique a un utilisateur - Google Patents

Procede et systeme pour decourager un expediteur de communiquer un message electronique a un utilisateur Download PDF

Info

Publication number
WO2006010998A2
WO2006010998A2 PCT/IB2004/003596 IB2004003596W WO2006010998A2 WO 2006010998 A2 WO2006010998 A2 WO 2006010998A2 IB 2004003596 W IB2004003596 W IB 2004003596W WO 2006010998 A2 WO2006010998 A2 WO 2006010998A2
Authority
WO
WIPO (PCT)
Prior art keywords
sender
user
electronic
network address
filter
Prior art date
Application number
PCT/IB2004/003596
Other languages
English (en)
Other versions
WO2006010998A3 (fr
WO2006010998A8 (fr
Inventor
Cédric R. J. HEBERT
Cédric S. P. ULMER
Laurent Y. Gomez
Pascal T. C. Spadone
Maarten E. Rits
Original Assignee
Sap Aktiengesellschaft
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 Sap Aktiengesellschaft filed Critical Sap Aktiengesellschaft
Priority to PCT/IB2004/003596 priority Critical patent/WO2006010998A2/fr
Publication of WO2006010998A2 publication Critical patent/WO2006010998A2/fr
Publication of WO2006010998A3 publication Critical patent/WO2006010998A3/fr
Publication of WO2006010998A8 publication Critical patent/WO2006010998A8/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
    • 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/48—Message addressing, e.g. address format or anonymous messages, aliases
    • 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/23—Reliability checks, e.g. acknowledgments or fault reporting

Definitions

  • An embodiment relates generally to the technical field of communications and, in one exemplary embodiment, to a method and System to discourage a sender from communicating an electronic message to a user.
  • E-mail has become an indispensable method of communication for many people. Indeed, e-mail provides an efficient and convenient way to communicate, receive and process messages.
  • the e-mail System has been exploited by a number of users that use electronic mailing lists to multiply and disseminate a plethora of unwanted material (e.g., SPAM) .
  • SPAM unwanted material
  • a user may send a single e-mail to a server that, in turn, copies and communicates the e-mail to thousands of users on a mailing list. Coping mechanisms have been developed.
  • Some ' users utilize application programs that automatically identify e-mail as SPAM. Other users may attempt to contact the sender and request them to stop sending the e-mail.
  • some sender s may interpret such contact as confirmation of a valid network address and continue to communicate e-mail to the user notwithstanding the expressed desire of the user.
  • a method to update a filter to- discourage a sender from communicating an electronic message to a user includes receiving a first electronic message from a sender, the electronic message including a network address of the sender; determining whether to discourage the sender from communicating a second electronic message to the user; and if so determined, updating the filter by registering the network address of the sender in the filter that is utilized to communicate an electronic response message to the sender, the electronic response message to discourage the sender from communicating the second electronic message to the user.
  • a method to use a filter to discourage a sender from communicating electronic messages to a user includes receiving an electronic message from a sender, the electronic message including a network address of the sender; identifying that the sender is to be discouraged from communicating a second electronic message to the user by using the filter that is updated by registering the network address of the sender to the filter; and communicating an electronic response message to the sender, the electronic response message to discourage the sender from communicating the second electronic message to the user.
  • a method to automatically remove a user from a mailing list includes, at a server machine, electronically communicating a first electronic message to a plurality of users respectively identified in a mailing list; at the server machine, receiving a second electronic message that is associated with a user that is included in the plurality of users, the second electronic message including an error code; at the server machine, automatically removing the user from the mailing list based on the error code.
  • Figure 1 is a network diagram depicting a System, according to one exemplary embodiment of the present invention.
  • Figure 2 is a block diagram illustrating an e-mail and tables utilized by the System, according to an exemplary embodiment of the present invention
  • Figure 3 is a flow chart illustrating a method, according to an exemplary embodiment of the present invention, to update a filter to discourage a sender from communicating an electronic message to a user;
  • Figure 4 is a flow chart illustrating a method, according to an exemplary embodiment of the present invention, to use a filter to discourage a sender from communicating an electronic messages to a user;
  • Figure 5 is a flow chart illustrating a method, according to an exemplary embodiment of the present invention, to automatically remove a user from a mailing list
  • Figure 6 is a flow chart illustrating a method, according to an exemplary embodiment of the present invention, to receive an e-mail header
  • Figures 7-9 illustrate user interface screens, according to an exemplary embodiment of the present invention.
  • Figure 10 illustrates a diagrammatic representation of a machine, in the exemplary form of a computer System, within which a set of instructions, for causing the machine to perform any one or more of the methodologies discussed herein, may be executed.
  • a System receives an e- mail that includes a network address of the user (e.g., e- mail recipient) and a network address of a sender (e.g., mailing list application, author of e-mail, etc.) .
  • the System reads the network address of the user from the e- mail to identify a filter that includes a list of network addresses of senders.
  • the System reads the network address of the sender from the e-mail and compares it with the network addresses in the filter. If a match is identified, the System generates a response message and communicates the response message to the sender.
  • the response message includes an error code that indicates that the network address of the user is an invalid network address. " The error code is intended to discourage the sender from sending additional e-mail to the recipient.
  • a mailing list application may print out, display, or forward error information.
  • the author may receive the error message directly.
  • Another aspect of the above invention includes a System to update a filter that is used to discourage a sender from communicating an e-mail to a user.
  • the System presents a user interface screen to a user (e.g., recipient) for reviewing and identifying unwanted e-mail (e.g., SPAM).
  • a user e.g., recipient
  • the recipient identifies unwanted e- mail by checking a box on the user interface screen that corresponds to the unwanted e-mail.
  • the user e.g., recipient
  • unwanted e-mail e.g., SPAM
  • the System will utilize the filter to discourage the sender from communicating e-mail to the user, as described above.
  • Another aspect of the above invention includes a System that automatically removes a user from a mailing list.
  • the System communicates a copy of an e-mail to each user on a mailing list. If the System receives a message from a user on the mailing list that includes an error code then the user is automatically removed from the mailing list.
  • FIG. 1 is a network diagram depicting a System 10, according to one exemplary embodiment, depicting a client-server architecture and a peer-to-peer architecture.
  • the client-server architecture includes a server machine 12, a server machine 14, a client machine 16 and a client machine 17 connected to and communicating over a network 18 (e.g., Internet, LAN, WAN) .
  • the client and server machines may utilize a number of different protocols including HTTP, Simple Mail Transfer Protocol
  • SMSTP Extended Simple Mail Transfer Protocol
  • ESMTP Extended Simple Mail Transfer Protocol
  • MIME Multipurpose Internet Mail Extensions
  • the peer-peer architecture may include the server machine 12 and the server machine 14.
  • the server machine 12 includes a mailing list application 22 and a web services application 23 and is connected to a mail storage component 24.
  • the mailing list application 22 e.g., LISTSERV, MAJORDOMO, LISTPROC, MAILBASE, etc.
  • the mailing module 22 receives an e-mail from a user and responds by copying and communicating the e-mail to each user that appears on a mailing list.
  • the mailing module 22 is utilized to administer mailing lists by processing control messages (e.g., add user to mailing list, remove user from mailing list, etc.) and error messages (e.g., invalid network address) .
  • the removing module 28 is utilized by the mailing module 22 to remove a user from a mailing list.
  • the mail storage component 24 includes a mailing list table 32 that stores the mailing lists.
  • the web services application 23 provides web interfaces to applications running on the server machine 12 including the mailing list application 22.
  • the server machine 14 includes a filtering engine 34 and is connected to a filter storage component 36.
  • the filtering engine 34 includes a communicating module 38 and an identifying module 40.
  • the communicating module 38 is utilized to communicate with the server machine 12 and the client machines 16 and 17.
  • the identifying module 40 utilizes a filter to identify an incoming e-mail as unwanted (e.g., SPAM) .
  • the filter storage component 36 is utilized to store filters in a user filter table 42 and a spam rule set table 44.
  • the user filter table 42 stores filters that identify the network addresses of e-mail senders that should be discouraged from sending e-mail.
  • the spam rule set table 44 stores rules that the filtering engine 34 applies to an incoming e-mail to identify and mark as incoming e-mail as unwanted.
  • the client machines 16 and 17 include a client application program 46.
  • the client machine 17 is connected to a client storage component 48.
  • the client application program 46 is utilized to author, communicate, and receive e-mail over the network 18.
  • the client application program 46 may be a mail client such .as the MICROSOFT OUTLOOK mail client developed by Microsoft Corporation of Redmond, Washington State or an Internet browser such as the INTERNET EXPLORER browser also developed by Microsoft Corporation.
  • the client application program 46 includes a filtering module 50 and an updating module 52.
  • the filtering module 50 is utilized to communicate with server machines 12 and 14 and to add, delete and update filters.
  • the filtering module 50 utilizes the updating module 52 to update a filter by registering a receiver network address in the filter.
  • the client storage component 48 is utilized to store a filter in the form of an exemplary personal filter table 54.
  • Figure 2 is a block diagram illustrating an e- mail and - various tables, according to an exemplary embodiment, including an exemplary electronic message in the form of an e-mail 60, a personal filter table 54, a user filter table 42, a spam rule set table 44, and a mailing list table 32.
  • the e-mail 60 includes a header 62 and a body 64.
  • the body 64 may include text and/or an optional file attachment.
  • the header 62 includes network addresses 65 that include sender network addresses 67 and receiver network addresses 69.
  • the sender network addresses 67 include an e-mail sender network address 66.
  • the receiver network addresses 69 include a blind receiver network address 68, a secondary receiver network address 70 and a primary receiver network address 72 (e.g., domain name System (DNS) addresses) .
  • DNS domain name System
  • the personal filter table 54 is utilized to store one or more e-mail sender network addresses 66.
  • the personal filter table 54 is updated by the client application program 46 and utilized by the filtering engine 34 to identify and respond to a sender that communicates an e-mail 60 that is unwanted.
  • the user filter table 42 is stored on the server machine 14 and is utilized by the filtering engine 34 to store multiple personal filter tables 54.
  • the spam rule set table 44 is utilized to store one or more ⁇ spam rules 75 that are utilized by the filtering engine 34 to automatically identify and mark incoming e-mail as spam.
  • the mailing list table 32 stores mailing lists 74.
  • Each mailing list 74 includes a mailing list identifier 76 and one or more receiver network addresses 69.
  • FIG. 3 is a flowchart illustrating a method 80, according to an exemplary embodiment, to update a filter.
  • a server machine 14 e.g., transfer server
  • a client machine 17 e.g., operated by an e-mail recipient
  • a user 18 e.g., recipient
  • a client application program 46 e.g., MICROSOFT OUTLOOK
  • the filtering engine 34 at the server machine 14 receives the request for e-mail 60 from the user 18 and communicates, at box 98, the e-mail 60 to the client machine 17.
  • the filtering module 50 on the client machine 17, receives and stores the e-mail 60 including a first electronic message in the form of an exemplary e-mail 60 on the client storage component
  • the user 18 reviews the e-mail 60 by utilizing a user interface 104 as illustrated on Figure 8, according to an exemplary embodiment.
  • the user interface 104 illustrates a summary line 105 and a notify sender checkbox 108 for each e-mail 60 retrieved by the client application program 46.
  • the user 18 reviews the e-mail 60 by selecting the first summary line 105
  • the filtering module 50 responds by displaying a full view of the selected e-mail 60, as illustrated in user interface 110 on Figure 9, according to an exemplary embodiment.
  • the user interface 110 illustrates the full view of the e-mail
  • the filtering engine 34 at the sever machine 14 has utilized the spam rule set table to identify the e- mail 60 with the string "** SPAM **"' .
  • the user 18 further wants to discourage the sender at the sender network address 66 (e.g., PRESCRIPTION@SERVER_MACHINE_12. com) from sending additional e-mail and consequently, returning to user interface 104, as illustrated on Figure 8, the user 18 selects the corresponding notify sender checkbox 108. Finally, the user 18 selects a submit user interface element 109.
  • the filtering module 50 enters a loop to update the personal filter table 54 and gets the next e-mail 60.
  • the filtering module 50 determines if the notify sender check box 108 is set for the e-mail 60. If the notify sender check box 108 is set, then the user has manually identified that the sender of the e-mail 60 should be discouraged from sending additional e-mail 60 and a branch is made to box 126. Otherwise, a branch is made to decision box
  • the updating module 52 registers the e-mail sender network address 66 (e.g., PRESRIPTION@SERVER_MACHINE_12.com) in the personal filter table 54.
  • the e-mail sender network address 66 e.g., PRESRIPTION@SERVER_MACHINE_12.com
  • the filtering module 50 synchronizes the personal filter table 54 at the client machine 14 with the corresponding personal filter table that is stored in the user filter table 42 at the server machine 14 by communicating the personal filter table 54 to the server machine 14.
  • the filtering module 50 determines if there is more e-mail 60 to process. If there is more e-mail 60 to process, a branch is made to box 122. Otherwise, processing ends on the client mach ine 17 .
  • the filtering module 50 in the filtering engine 34, on the server machine 14, receives and registers the personal filter table 54 in the appropriate entry in the user filter table 42 and processing ends.
  • FIG. 4 is a flowchart illustrating a method 93, according to an exemplary embodiment, to use a filter.
  • a client machine 16 e.g., operated by an e- mail author
  • a server machine 12 e.g., mailing list server
  • a server machine 14 e.g., transfer server
  • a client machine 17 e.g., operated by a recipient
  • a user 15 e.g., e-mail author
  • client machine 16 utilizes a client application program 46 (e.g., MICROSOFT OUTLOOK) to author an e- mail 60 that is addressed to a mailing list 74 that is stored at server machine 12 as illustrated in user interface 84 on Figure 7.
  • client application program 46 e.g., MICROSOFT OUTLOOK
  • the user interface 84 illustrates the e— mail 60 that includes a header 62 and body 64.
  • the header 62 includes a primary receiver network address 72 and a subject line 78.
  • the primary receiver network address 72 includes a mailing list identifier 76, "PRESCRIPTIONS", and a domain name System address 88, // @SERVER_MACHINE_12.com 77 , for the server machine 12.
  • the body 64 includes an advertisement for an online ordering of prescription drugs.
  • the mailing list application 22 receives the e-mail 60 from the client machine 16.
  • the mailing list application 22 ex tracts the mailing list identifier 76 from the header 62 of the e- mail 60 and utilizes the mailing list identifier 76 to find the corresponding set of receiver network addresses
  • the communicating module 38 in the filtering engine 34 at the server machine 14 receives an e-mail header 62 from the server machine 12.
  • Figure 6 illustrates the box 92, according to an exemplary embodiment.
  • the server machine 12 e.g., mailing list server
  • the server machine 14 e.g., transfer machine
  • the server machine 12 operating as a client, establishes a TCP connection to port 25 of the server machine 14 and communicates an EHELLO message (e.g., Extended simple Mail transfer Protocol as defined by RFC 142) to the server machine 14. It will be appreciate that other protocols may be utilized in other embodiments .
  • EHELLO message e.g., Extended simple Mail transfer Protocol as defined by RFC 142
  • the server machine 12 receives the acknowledgment and communicates a sender network address 66 to the server machine 14.
  • the communicating module 38 at the server machine 14 receives the sender network address 66 and communicates an acknowledgment to the server machine 12.
  • the server machine 12 receives the acknowledgment and communicates a receiver network address 69 to the server machine 14.
  • the communicating module 38 at server machine 14 receives the receiver network address 66 and processing ends.
  • the identifying module 40 is passed the receiver network address 69 (e.g., a primary receiver network address 72, a secondary receiver network address 70, a blind receiver network address 68, etc.) from the communicating module 38.
  • the identifying module 40 utilizes the receiver network address 60 to get the corresponding filter in the form of an exemplary personal filter table 54 from the user filter table 42.
  • the identifying module may request the personal filter table 54 from the client application program 46.
  • the filtering engine 34 and the client application program may be able to communicate as peers, thus the filtering engine 34 may initiate communication.
  • the client application program 46 may execute on the server machine 14.
  • the identifying module 40 searches the personal filter table 54 to identify a sender network address 66 that matches the sender network address 66 in the e-mail 60. If the identifying module 40 identifies a match, a branch is made to box 149. Otherwise, a branch is made to box 153.
  • the communicating module 38 stores an invalid network address error code in an electronic response message.
  • Other embodiments may utilize other error codes.
  • the communication module 38 stores an acknowledgement response in the electronic response message.
  • the communication module 38 communicates the electronic response message to the server machine 12.
  • the error code indicates that the receiver network address 69 is an invalid network address.
  • Other embodiments may utilize other error codes to discourage the sender from communicating additional e-mail 60.
  • the electronic response message includes an error code indicating that the previously communicated receiver network address 69 is an invalid network address.
  • the mailing module 26 may store, display, or print error information (e.g., the error code, the sender network address 67, and the receiver network address 69, etc.) at the server machine 12 to notify an administrator that the mailing list 74 includes a receiver network address 69 that is invalid.
  • the mailing module 26 may forward the error information to the user 15 (e.g., the author) .
  • Yet other embodiments may include other mechanisms (e.g., notification) that may be utilized to publish, communicate or disseminate the error information and thereby discourage the sender from sending additional e- mails 60 to the user 18 at the receiver network address 69.
  • the mailing module 26 communicates the body 64 of the e-mail 60 to the server machine 14.
  • the communicating module 38 At box 159 the communicating module 38, at the server machine 14, receives the body 64 of the e- mail 60 and processing ends.
  • Figure 5 is a flowchart illustrating a method 160, according to an exemplary embodiment, to automatically remove a user from a mailing list.
  • the server machine 12 receives an e-mail 60 from a user 15 and the mailing module 26 communicates the e-mail 60 to recipients on a mailing list as previously described in box 90 on Figure 4.
  • the server machine 14 receives and processes a header 62 of an e-mail 60 as previously described in boxes 92,146,148,149, and 153 on Figure 4.
  • the server machine 14 communicates an electronic response message to the server machine 12 as previously described in box 150 on Figure 4.
  • the mailing module 26, on the server machine 12 receives an electronic response message as previously described in box 152 on Figure 4.
  • the mailing module 26, on the server machine 12 determines if the error code in the electronic response message indicates an invalid network address. If the mailing module 26 determines there is an invalid network address error code, a branch is made to box 182. Otherwise, a branch is made to box 179.
  • the removing module 28 automatically removes the receiver network address 69 from the mailing list 74 that is currently being processed.
  • the server machine 12 communicates the body 64 of the e-mail 60 to the server machine 14 as described in box 157 on Figure 4.
  • the server machine 14 receives and processes the body 64 of the e-mail 60 as previously described in box 159 on Figure 4.
  • Figure 10 shows a diagrammatic representation of a machine in the exemplary form of a computer System 300 within which a set of instructions, for causing the machine to perform any one or more of the methodologies discussed herein, may be executed.
  • the machine operates as a standalone device or may be connected (e.g., networked) to other machines.
  • the machine may operate in the capacity of a server or a client machine in server-client network environment, or as a peer machine in a peer- to-peer (or distributed) network environment.
  • the machine may be a server computer, a client computer, a personal computer (PC) , a tablet PC, a set-top box
  • STB Personal Digital Assistant
  • PDA Personal Digital Assistant
  • STB Personal Digital Assistant
  • web appliance a web appliance
  • network router a network router
  • switch or bridge any machine capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by that machine.
  • machine shall also be taken to include any collection of machines that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein.
  • the exemplary computer System 300 includes a processor 302 (e.g., a central processing unit (CPU) a graphics processing unit (GPU) or both) , a main memory 304 and a static memory 306, which communicate with each other via a bus 308.
  • the computer System 300 may further include a video display unit 310 (e.g., a liquid crystal display (LCD) or a cathode ray tube (CRT) ) .
  • the computer System 300 also includes an alphanumeric input device 312 (e.g., a keyboard) , a cursor control device 314 (e.g. , a mouse) , a disk drive unit 316, a signal generation device 318 (e.g., a speaker) and a network interface device 320.
  • the disk drive unit 316 includes a machine- readable medium 322 on which is stored one or more sets of instructions (e.g., software 324) embodying any one or more of the methodologies or functions described herein.
  • the software 324 may also reside, completely or at least partially, within the main memory 304 and/or within the processor 302 during execution thereof by the computer System 300, the main memory 304 and the processor 302 also constituting machine-readable media.
  • the software 324 may further be transmitted or received over a network 326 via the network interface device 320.
  • machine-readable medium 392 is shown in an exemplary embodiment to be a single medium, the term “machine-readable medium” should be taken to include a single medium or multiple media
  • machine-readable medium shall also be taken to include any medium that is capable of storing, encoding or carrying a set of instructions for execution by the machine and that cause the machine to perform any one or more of the methodologies of the present invention.
  • machine-readable medium shall accordingly be taken to include, but not be limited to, solid-state memories, optical and magnetic media, and carrier wave signals.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

L'invention concerne un système pour actualiser un filtre pour décourager un expéditeur de communiquer un message électronique à un utilisateur. Selon l'invention, le système reçoit un message d'un expéditeur, ce message contenant une adresse réseau de l'expéditeur, et il détermine si l'expéditeur doit être découragé de communiquer un deuxième message à un utilisateur, sur la base d'une entrée de l'utilisateur. Si l'utilisateur indique que l'expéditeur devrait être découragé, le système actualise le filtre en enregistrant l'adresse réseau de l'expéditeur dans le filtre subséquemment utilisé pour communiquer un message de réponse à l'expéditeur avec un code d'erreur indiquant que l'adresse réseau de l'utilisateur est une adresse réseau non valable. La présente invention porte également sur un système pour utiliser un filtre pour décourager un expéditeur de communiquer un deuxième message à un utilisateur, ainsi que sur un système pour effacer automatiquement un utilisateur d'une liste de diffusion.
PCT/IB2004/003596 2004-07-13 2004-07-13 Procede et systeme pour decourager un expediteur de communiquer un message electronique a un utilisateur WO2006010998A2 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/IB2004/003596 WO2006010998A2 (fr) 2004-07-13 2004-07-13 Procede et systeme pour decourager un expediteur de communiquer un message electronique a un utilisateur

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/IB2004/003596 WO2006010998A2 (fr) 2004-07-13 2004-07-13 Procede et systeme pour decourager un expediteur de communiquer un message electronique a un utilisateur

Publications (3)

Publication Number Publication Date
WO2006010998A2 true WO2006010998A2 (fr) 2006-02-02
WO2006010998A3 WO2006010998A3 (fr) 2006-04-13
WO2006010998A8 WO2006010998A8 (fr) 2006-06-15

Family

ID=35786565

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IB2004/003596 WO2006010998A2 (fr) 2004-07-13 2004-07-13 Procede et systeme pour decourager un expediteur de communiquer un message electronique a un utilisateur

Country Status (1)

Country Link
WO (1) WO2006010998A2 (fr)

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030182383A1 (en) * 2002-02-12 2003-09-25 Xiaopeng He Enterprise electronic mail filtering and notification system
US20030229672A1 (en) * 2002-06-05 2003-12-11 Kohn Daniel Mark Enforceable spam identification and reduction system, and method thereof
US7200636B2 (en) * 2002-11-01 2007-04-03 Sun Microsystems, Inc. Method and apparatus for applying personalized rules to e-mail messages at an e-mail server

Also Published As

Publication number Publication date
WO2006010998A3 (fr) 2006-04-13
WO2006010998A8 (fr) 2006-06-15

Similar Documents

Publication Publication Date Title
US6993561B2 (en) Method and apparatus for maintaining a unified view of multiple mailboxes
EP1447765B1 (fr) Méthode, appareil, et interface utilisateur pour contrôler le courrier électronique et les messages d'alerte
CA2567315C (fr) Protocole de messagerie pour traiter des messages avec des pieces jointes
EP1676387B1 (fr) Hierarchie de schemas pour messages electroniques
KR101251862B1 (ko) 전자 메일 대화를 조작하고 표시하는 방법
US20060036698A1 (en) Method and system to discourage a sender from communicating an electronic message to a user
US7689654B2 (en) Email address verification
US9015252B2 (en) Method and system for forcing e-mail addresses into blind carbon copy (“Bcc”) to enforce privacy
CN1217514C (zh) 统一信息中的联机集聚方法和装置
US20150169202A1 (en) Declassifying of suspicious messages
EP1883042A1 (fr) Système et procédé de transmission de données électroniques
US20020091772A1 (en) Method for correlating an electronic mail message with related messages
WO2007081646A2 (fr) Procédé et appareil permettant de générer des données d'abonnement personnalisées
CN1304608A (zh) 从主机系统向移动数据通讯装置发布信息的装置和方法
KR20060050342A (ko) 팩스 메시지를 나타내기 위해 메시지 스키마를 확장하는시스템 및 방법
JP2007249310A (ja) 情報管理サーバ
JP2000215127A (ja) ハイパ―テキストリファレンス間の関係を確立するシステムおよび方法と該システムを含む電子メ―ルプログラム
US20060086798A1 (en) Deferred email message system and service
WO2006010998A2 (fr) Procede et systeme pour decourager un expediteur de communiquer un message electronique a un utilisateur
JP4121171B2 (ja) メッセージ管理方法及びシステム及びメッセージ管理プログラムを格納した記憶媒体
JP4640620B2 (ja) 電子メール管理システム、メールサーバ、電子メール管理方法、及びプログラム
JP2005072672A (ja) 電子メール分類配信装置のフィードバック学習システム及びそのフィードバック学習プログラム
JP2003303159A (ja) 情報処理装置及びメッセージの処理方法並びにプログラム
JP3366892B2 (ja) サーバ装置および情報の共有方法
JP2003256623A (ja) スケジュール転送システム、スケジュール登録装置及びプログラム

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): 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

CFP Corrected version of a pamphlet front page
CR1 Correction of entry in section i

Free format text: IN GAZETTE 05/2006 UNDER (72, 75) REPLACE "RITS, MAARTEN, E. [BE/FR]; ROUTES DES COLLES ESSI,BP 145, F-06903 SOPHIA ANTIPOLIS (FR)" BY "RITS,MAARTEN, E. [BE/FR]; 930, ROUTE DES COLLES ESSI, BP 145, F-06903 SOPHIA ANTIPOLIS (FR)."

NENP Non-entry into the national phase

Ref country code: DE

WWW Wipo information: withdrawn in national office

Country of ref document: DE

122 Ep: pct application non-entry in european phase