EP1605649B1 - Procédé et dispositif de gestion de courrier électronique - Google Patents

Procédé et dispositif de gestion de courrier électronique Download PDF

Info

Publication number
EP1605649B1
EP1605649B1 EP04013014A EP04013014A EP1605649B1 EP 1605649 B1 EP1605649 B1 EP 1605649B1 EP 04013014 A EP04013014 A EP 04013014A EP 04013014 A EP04013014 A EP 04013014A EP 1605649 B1 EP1605649 B1 EP 1605649B1
Authority
EP
European Patent Office
Prior art keywords
file
message
references
attachments
server
Prior art date
Legal status (The legal status 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 status listed.)
Active
Application number
EP04013014A
Other languages
German (de)
English (en)
Other versions
EP1605649A1 (fr
Inventor
Franz Dr. IXOS Software AG Heiss
Jörg-Stefan IXOS Software AG Sell
Christian Winter
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Open Text Software GmbH
Original Assignee
Ixos Software AG
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 Ixos Software AG filed Critical Ixos Software AG
Priority to EP04013014A priority Critical patent/EP1605649B1/fr
Priority to DE502004001164T priority patent/DE502004001164D1/de
Priority to US11/145,496 priority patent/US8073822B2/en
Publication of EP1605649A1 publication Critical patent/EP1605649A1/fr
Application granted granted Critical
Publication of EP1605649B1 publication Critical patent/EP1605649B1/fr
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/10—Office automation; Time management
    • G06Q10/107—Computer-aided management of electronic mailing [e-mailing]
    • 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/07—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail characterised by the inclusion of specific contents
    • H04L51/08—Annexed information, e.g. attachments
    • 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/42—Mailbox-related aspects, e.g. synchronisation of mailboxes

Definitions

  • the present invention relates to a method and apparatus for managing electronic messages.
  • the invention relates to the memory-efficient archiving of electronic messages containing attachments.
  • Emails or other message formats for sending text, images, sound or other data are known.
  • Electronic messages are thereby sent between data processing systems of different users, which are interconnected, for example, via a computer or a communications network.
  • the sending of messages can be done either only within a local area network, e.g. an intranet of a company or worldwide via the Internet and thus between any user who has a computer connected to the Internet.
  • the standard protocol for exchanging emails according to the RFC822 protocol is described in Crocker, D.H .: "Standard for the Format of ARPA Internet Text Messages", RFC822, 1982.
  • the sending, transmitting and forwarding and distribution of electronic messages is usually carried out by electronic communication systems, which often also take over the storage of messages.
  • electronic communication systems which often also take over the storage of messages.
  • Such message processing systems for sending, receiving and storing emails such as Microsoft Exchange or Lotus Notes, are known and can be installed on a single computer or on a so-called email server for multiple clients in a network.
  • a well-known standard for sending and receiving electronic mail (“e-mail”) between a client and an e-mail server is POP3 ("Post Office Protocol Version 3"), which allows the client to access the e-mail server contact there to query his mailbox and download new emails in the local inbox of the client or to send emails to be sent from the local outbox of the client for further transmission to the email server.
  • POP3 Post Office Protocol Version 3
  • IMAP4rev1 Internet Message Access Protocol Version 4 Revision 1
  • Electronic messages such as emails, typically include a message header that contains information about the recipient, sender, and other information, as well as a message body containing the actual message.
  • the message body can contain files in standard formats as well as other emails, which in turn can contain files, as so-called file attachments or attachments.
  • file attachments or attachments The ability of prior art email processing systems to provide an auto-reply or forwarding function in which a reply message is generated to a received message where the received message is automatically copied into the message body of the reply message creates the problem of cascading messages due to repeated use of the auto-response function in their size continue to grow and thus increasingly represent a memory problem. Because each electronic message is a single file and as such, individually is stored, electronic messages can be outsourced only as a whole from the email processing system and stored externally.
  • mailing lists such as public mailing lists or distribution lists
  • an electronic message is automatically sent to all recipients listed in the list so that an e-mail with identical content e.g. sent to a thousand people and because of the metadata specific to each recipient, e.g. Receiving address, time of reception, etc. is stored individually for the recipient and thus may also be redundant in many cases on the corresponding email server or a corresponding message storage system.
  • European Patent Application EP-A-1 035 690 discloses an e-mail archiving system in which electronic messages are stored in a message archive with a client identifier and an archive token to allow selective and structured access to archived messages.
  • the presented archive system proposes no solution as to how the redundant storage of identical file attachments in a plurality of stored messages can be avoided.
  • US 2002/0065892 A1 discloses a method and apparatus for reducing the memory requirements of shared file attachments in an e-mail communication server.
  • the e-mail communication system thereby reduces the number of duplicated copies of shared attachments of e-mail messages stored on a mail store of an e-mail server. If the e-mail server receives an e-mail attachment that has a size larger than a certain threshold size, the server performs a database search for another copy of the attachment in the mail store. If another copy is located, the attachment is removed from the e-mail message and a link is created between the previously stored attachment in the database.
  • the search for duplicates to a file attachment in the database is time-consuming or resource-intensive, the search for duplicates and further processing takes place only if the previous check has revealed that the file attachment has exceeded a certain file size. Then, if the check for duplicates shows that the file attachment is already stored in the mail memory, if necessary, the file attachment is transferred to a cache section of the mail store, created a record for the e-mail message and a link to the in the Cache section transferred attachment attached. The corresponding links in the records of other e-mail messages, which also refer to this file attachment, are then changed accordingly to reflect the dumping of the attachment to the cache section.
  • a method for the memory-efficient management of electronic messages involves first receiving or reading one of a system such as e.g. an email server to manage message.
  • the message to be managed is analyzed and decomposed into a framework and the file attachments contained in the message.
  • For each file attachment a unique identification value is calculated and the file attachments of the decomposed message are now stored individually, wherein it is first checked whether there is already a file in memory for an identification value. In the event that there is no file with the newly calculated identification value in memory, the new file is saved with its identification value. In the event that a file with the calculated identification value already exists in the memory, the file is not saved again, but only a reference to the already existing identical file created. The remaining skeleton with the message header now contains no more file attachments, but only references to the file attachments stored as separate files and is also stored as such or as the core file of the message.
  • each component such as an attachment
  • the remainder of the message merely references to the file attachments contained in the original message.
  • the unique identification value calculated for each file attachment makes it possible to uniquely identify and manage the file attachments, this identification value being either linked to or separate from the file, e.g. in a mapping table.
  • the invention further provides, in another aspect, a system for the memory efficient management of electronic messages comprising an archive server having a message swap module, an identification value computation module, and a reference counter management module.
  • the message paging module disconnects one on the server received message in the skeleton of the message and the file attachments contained in the message.
  • the skeleton with references to the file attachments contained in the message are then stored separately in a memory.
  • the file attachments are moved to the archive server, and for each file attachment, the identification value calculation module calculates a unique identification value, and if that identification value has not yet been assigned, the file attachment is stored in the memory with the calculated identification value, otherwise if in If a file with the calculated identification value already exists, the file attachment is not saved again, but the reference counter management module increments the reference counter of the existing file.
  • a message client which is connectable to the system for the memory efficient management of electronic messages, comprises a processor, a memory, a screen, at least one input device, and a message client module that informs a user
  • a processor Using the input device in conjunction with a processor allows messages from the message server in a user interface (GUI) of the message client module to be displayed on the screen and save memory-efficient on the archive server.
  • GUI user interface
  • emails are managed as electronic messages by a system, in particular an archive server, whereby incoming emails are read by means of program modules installed on the archive server, analyzed for their components and file attachments are detached.
  • file attachments which in turn are an electronic message or otherwise in turn contain file attachments, are also analyzed and possibly contained file attachments are removed. The analysis and extraction takes place recursively until all components of an electronic message have been removed.
  • the initially present as a file with, for example, the suffix .eml or .msg electronic message is therefore split into a skeleton or a core file containing references to their associated messages or file attachments, and the corresponding previously contained messages and attachments, where contained messages are also split into a skeleton and the respective attachments contained.
  • the liberated ones File attachments are now transferred to a storage system.
  • the file attachments are preferably transferred individually to the storage system, and upon receipt of a file attachment in the storage system, the identification value calculation module calculates a unique identification value for each transferred file attachment and assigns this identification value to the file attachment. The system also checks whether a newly calculated identification value already exists.
  • all identification values of file attachments already stored in the system are stored in an allocation table or an identification value database. After the identification value already exists in the identification value database for a file attachment transferred to the storage or archive system or the archive server, the file attachment is not stored again as a file on the archive server, but only a reference saved to the corresponding, existing file.
  • the subsequent access to an electronic message managed by means of the system takes place by first reading the core file or the skeleton with references from a program module and replacing the contained references to the separately stored files by these files in turn are stored as attachments within the core file, so that the original message is restored.
  • Another aspect of the invention relates to the reconstruction of electronic messages that have been previously managed or archived by decomposition into their components and their separate storage or of messages that are in a suitable format for reconstructing according to the method described here.
  • the reference counter of that file each time a reference in a skeleton is replaced by the corresponding file when reconstructing an electronic message, the reference counter of that file only decrements the reference counter of that file when the message is deleted from the system. If a message is reconstructed only because it is e.g. is to be brought to the display, the corresponding reference counter is not decremented and when the display is then carried out expediently no re-storage of the message in the system. If a file reference count reaches a value less than its initialization value, the file is deleted from the archive server so that file attachments from unmanaged messages are also removed from the archive server.
  • the storage requirements for storing electronic messages is significantly reduced by individual attachments are stored only once after using the identification value is easy to determine whether the file attachment is already stored in the system so that further instances of the file need not be saved again. Instead, reference is made to the already existing instance.
  • the identification value is generated as a hash value with a so-called hash algorithm.
  • a hash algorithm For example, in the programming language Java, the method "hashCode ()" is available, which generates a hash value of the specified file.
  • other algorithms such as checksum formation algorithms (CRC)
  • CRC checksum formation algorithms
  • a further advantage of the present invention relates to the possibility of finely structuring electronic messages or other files, which in turn contain files, by means of the presented methods in that the messages or files can each be recursively decomposed into their individual components.
  • the messages or files can each be recursively decomposed into their individual components.
  • the dissolution and assembly of electronic messages or the detachment of file attachments contained in electronic messages according to the invention are advantageously carried out using program modules which are stored in the server system, e.g. the email server, are integrated and rely on its functionality, so that the functionality provided by the invention can be easily added to existing systems.
  • the invention further ensures that the available individual components of an electronic message are stored only once in the archive system by duplicates are identifiable on the basis of the same identification value and thus a multiple storage is avoided.
  • the text component remaining in the basic structure or the core file is also paged out as a separate file and stored as a uniquely identifiable file on the archive server, so that the basic structure or the core file only from the message header and References, therefore, at least the reference to the file with the body of the message consists.
  • all data of a core file or a skeleton, including the references to the triggered file attachments in an outsourced data structure, eg in an external database or objects in the memory of the archive server can be kept.
  • the provided method or system the administration of an email server is significantly simplified and also designed cheaper.
  • the reference files remaining on a message or email server to the skeletons of the messages are typically only about 0.2 to 1 KB in size, so that even mailboxes with a relatively small storage capacity can manage a large amount of messages. It also makes it possible that significantly more mailboxes can be stored on an email server and thus save hardware and software. Importing backups, restoring data, and migrating to new email servers will be easier and cheaper.
  • the present invention is further advantageous for the secure archival of documents, especially after increasingly legal requirements for retention periods and archiving standards for electronic documents provided, and these are legally equated according to various regulations (SEC rules, GoBSm GDPdU or the Sarbanes-Oxley Act) paper documents ,
  • electronic messages can be made simpler, non-redundant and with statistical information in e.g. put down non-erasable formats.
  • the present invention further provides a computer program and a computer program product.
  • FIG. 1 shows schematically a block diagram of a distributed data processing system 100 suitable for implementing embodiments of the invention.
  • 150 message clients e-mail client 1, e-mail client 2) 110, 120, a message server (e-mail server) 130 and an archive server 140 are connected to each other via an internal network (intranet).
  • the internal network 150 can be embodied as a LAN, WLAN or another communication network, which makes it possible to exchange messages between the servers and clients, for example in the form of data packets.
  • data exchange is also given to remote users connected to the internal network 150 via the Internet 160 via a remote email server 170.
  • FIG. 2 schematically shows a more detailed block diagram 200 of a message client 110, 120 connected to the network 150.
  • the message client 200 is usually a computer, terminal, or even a so-called thin client and has a computer as a computer Processor 230, a screen 210, at least one input device 220, preferably a memory 240 and a random access memory 250.
  • an email client module is executively stored in the memory 250
  • a local inbox / outbox (mailbox) 245 is stored in the memory 240, which is used in particular when a message exchange with the email server 130 takes place according to the POP3 standard.
  • the memory 250 also contains, by way of example, a received and opened e-mail 270 as well as a reconstructed or recovered e-mail 280, which can each be displayed in the GUI 215.
  • FIG. 3 schematically shows a more detailed block diagram 300 of the e-mail server 130 connected to the network 150.
  • the e-mail server 300 has a memory or a database 310 for storing the electronic messages to be managed by the e-mail server in the inbox / outbox (mailbox) 320, as well as a processor 340 and a working memory 350.
  • An e-mail server is located in the main memory Program (email administration program), such as Microsoft Exchange or Lotus Notes, stored at least partially executable that manages the electronic messages using the processor 340.
  • the memory 350 also contains an e-mail notification module 370.
  • FIG. 3 shows, by way of example, a message (e-mail) 390 with file attachments 395 which is currently to be managed.
  • FIG. 4 schematically shows a more detailed block diagram 400 of the archive server 140 connected to the network 150 and also including a processor 430, a memory or database 410 for storing and archiving electronic messages, and a random access memory 450 in which at least Portions of an executable archive server program 460 as well as an identification value calculation module 470, a reference counter management module 480, an e-mail paging module 485, an e-mail reconstruction module 490, and a mapping code calculation module 495, by way of example are stored.
  • the respective modules are preferably loaded into memory only when their functionality is needed.
  • the method 700 for the storage-efficient management of electronic messages runs in principle as explained below.
  • a message 270 to be managed which is opened, for example, in the client 200, should be managed or archived in a memory-efficient manner according to user input via the input device 220.
  • a memory-efficient administration can also be carried out without user input or interaction of a client 200, for example by stored rules and automatic cyclic checking of the server.
  • the email is read by the email server or sent and received for this (step 710) and initially stored in the working memory 350 as email 390.
  • the archive server 400 is informed of the existence of an e-mail to be managed.
  • the Email Swap Module 485 then causes the email to be moved to the archive server and breaks the message into its backbone as well as the file attachments contained in the message (step 720).
  • the basic structure preferably corresponds to the core file of the email with the message header and the immediate text in the message body.
  • the extracted from the email files that were previously included as file attachments 395 in the email are now, preferably individually, moved to a storage system.
  • the memory system is preferably a memory 410 of the archive server or a separate file server.
  • the hash value calculation module 470 calculates for each file attachment a unique hash value as the identification value for that file attachment (step 730).
  • step 740 it is checked whether such an identification value already exists in the memory 410 and thus an identical file has already been stored by the archive server. If this is not the case, a branch is made to step 750, and the file attachment is stored as a file for the first time in the memory of the archive server. If an identical identification value already exists, a branch is made to step 760 in which only the reference counter management module 480 increments the reference count of the file attachment having the identical identification value, but without re-saving the file attachment as a file on the archive server.
  • the memory 410 in this case contains an allocation table 420, in which each stored file is assigned a corresponding reference counter and whose value indicates how often in managed emails the file is referred to as a file attachment. The value of the reference counter can therefore be evaluated statistically, in the simplest case to indicate how often in the managed emails a specific file is included as a file attachment.
  • the archive server program 460 After all file attachments extracted from the email have been processed by the archive server program 460 and its modules, the remaining skeleton of the email becomes the references to the files in the storage system. 410 corresponding to the original file attachments are also stored in the memory of the archive server as the skeleton file 426 with reference 427.
  • no modules of the archive server are installed on the email server 300, since to maintain the stability of the email server on this no additional modules should be present.
  • corresponding functionalities of the e-mail server program 360 are used to report the receipt of new e-mails or to query them regularly.
  • the starting point in step 810 is an email A.msg 510 which contains several file attachments (Word document C.doc and Excel file D.xls) 520, 530 as well as another email (B.msg) 540, which in turn attaches files (Word document E.doc and Text document F.txt) 550, 560 ( Figure 5a).
  • the e-mail notification module 370 has indicated to the archive server program 460 that an e-mail 510 to be managed is located on the e-mail server, this e-mail is replaced by a reference file 380 which initially contains information such as addressee, sender, subject, etc. of the email to be managed.
  • the email is now moved to the archive server 400.
  • e-mail 510 is first separated from e-mail swap module 485 into a skeleton 570, and file attachments C.doc 520, D.xls 530, and escaped e-mail B.msg 540 (FIG. 5b).
  • a next step 830 it is checked whether at least one of the detached file attachments is again an email with possibly further file attachments.
  • such a further email namely the file B.msg 540 is present as a file attachment, so that is branched from step 830 back to step 825 and in re-execution of step 825 and the email B.msg in a skeleton 580 and the File attachments E.doc 550 and F.txt 560 are separated ( Figure 5c).
  • a file identification code 695 is now calculated for the file attachments 520, 530, 550, and 560, each containing a Assignment of the corresponding file attachments to the skeleton allows.
  • the file identification code is preferably a globally unique reference code of the extracted file generated by a file identification code calculation module 475, which is eg generated from parameters such as file name, used network card ID, computer hardware, time of archiving, etc.
  • the mapping code 385 for referring to the skeleton file from the link file is also a globally unique reference code that is generated according to, for example, the file identification code.
  • the hash value calculation module 470 calculates e.g.
  • the archive server program 460 or other module checks whether the file is already in the archive using the calculated hash value Server or its memory 410 is present. If the file is not yet present in the archive server, a branch is made to step 870 and the file is newly stored on the archive server or a suitable memory or file server with its hash value and its file identification code. Further, in step 875, the reference counter management module 480 initializes a reference counter for the newly stored file with a seed value.
  • step 880 in which only the newly calculated file identification code for the already stored file is added and the reference counter of this file is incremented in step 885, the file but not stored again on the archive server or its memory.
  • step 890 the file identification code of the file is returned to the skeleton as a reference to the file.
  • the skeleton 426 with the references 427 is then also on the archive server or a suitable memory 410 is stored.
  • the mapping code 385 of the skeleton reference file 380 on the email server is further supplemented by parameters generated by a mapping code calculation module 495 that refer to the stored skeleton file.
  • the assignment code 385 is also entered for the later assignment as entry 428 in the skeleton.
  • data structures result when the method according to the invention is carried out.
  • a basic structure 610 or 620 of the emails is stored in the memory of the archive server or in a separately stored database.
  • the archive server files are further stored according to the table 650, which lists, for example, in a first column 660 the emails A.msg and B.msg existing file attachments as a file in a second column 670 shows the associated hash value, in one third column 680 indicates the respective value of the reference counter for the files and receives the file identification codes in another column 695.
  • the A.msg basic framework 610 with the references 640 and assignment code as a file or data record is now stored on the archive server, for example in a table 425.
  • the file D.xls referenced in the references via the file identification codes "AD" and "GD” is stored together with the hash value and the reference counter value "2" in an allocation table 420 (data record in column 690).
  • the reference count value "2" indicates that the file D.xls is still referenced by another paged out email (G.msg, via the file identification code "GD”) whose skeleton 630 is shown in FIG.
  • Table 650 also shows a file Z.txt whose reference count value is zero and which is thus cleared the next time the memory or database is updated or by an automatic delete routine. Overall, this ensures that each file is stored only once on the archive server and as soon as a file is no longer referenced by outsourced emails managed in the system will be deleted again from the archive server. Thus, when several messages have been stored with their components or attachments, there is a n: m relationship between the message skeletons and messages and file attachments extracted from the messages.
  • FIG. 9 is a flow chart of a method 900 for reconstructing electronic messages.
  • a user starts e.g. a call to view his email.
  • this call does not differ to the user from the usual call of an email.
  • the user selects by means of the input device 220 at the message client 200 in the user interface (GUI) 215 on the screen 210, a message that he would like to have displayed and selects, for example. by double-clicking on the message or selecting the "Show" button in e.g. a pull-down menu of the GUI of the email client module 260, the function of displaying the email.
  • the client sends a corresponding request to the email server 300 for displaying the selected email.
  • the e-mail server then reads the mapping code 385 from the memory 310 in the e-mail referencing file 380.
  • the mapping code is sent to the archive server.
  • the e-mail corresponding to the mapping code is now reconstructed by the e-mail reconstruction module 490.
  • the skeleton corresponding to the mapping code is read from the memory. In this case, the files referenced in the references belonging to the corresponding skeleton file are then loaded and the references are replaced by the loaded files, so that once again an email file with contained file attachments is formed.
  • the file identification values contained in the references are combined with those in the Mapping table 650 compared to file identification values stored in column 695. If there is a match, the corresponding file specified in column 660 of the table is loaded from memory 410 (step 940). If, therefore, the file identification code "BE" was transferred from the basic structure of the email "B.msg", the email reconstruction module 490 determines the file "E.doc” in line 691 with the identical file identification value "BE".
  • step 960 a check is then made as to whether a loaded file contains further references to likewise triggered and archived files. This affects both other triggered file attachments as well as references to other skeletal files that are stored on the archive server.
  • a loaded file again contains a route, it branches again to step 930 and the link is in turn resolved in accordance with steps 930 and 940 described above by loading the corresponding file.
  • the corresponding references 640 of the A.msg skeleton 610 contain a reference to the B.msg skeletal file 620.
  • this skeleton file is also stored on the archive server.
  • the references of the B.msg skeleton file 620 are then also resolved by loading the files referenced by the file identification codes in the references.
  • step 960 branches to step 970 and the complete reconstruction of the email is done by inserting all the loaded files as file attachments into the skeletal file (s).
  • step 980 the fully reconstructed email is then moved from the archive server to the email server.
  • the reference file corresponding to the email according to the matching allocation code and serving as a wildcard is then replaced by the email.
  • step 990 the email is either stored in the memory of the email server 300, transmitted to the email client 200, or otherwise processed.
  • the user by appropriate inputs, eg via a selection menu, only certain file attachments in an email, for example, for memory reasons, reconstruct wants and selects them in the selection menu.
  • the Email Reconstruction module 490 will then only replace the references with the corresponding files selected by the user. The remaining references are not resolved and appear in the reconstructed email as placeholders for the corresponding file attachments.
  • the user can then also resolve these previously unresolved references and have them replaced by the corresponding file attachments.
  • the fully or partially reconstructed email would then be sent as an email file to the email server e.g. stored in the inbox / outbox (mailbox) 320 and is thus available for the call from the email client 200.
  • the reconstructed e-mail is not first stored in the mailbox 320 of the e-mail server, but transmitted directly to the calling e-mail client 200 and stored there in the local inbox / outbox (mailbox) 245.
  • FIG. 10 shows, by way of example, the section from a graphical user interface 1000 of an email client module 260 according to the invention, which is displayed on the screen 210.
  • the folder list (“Folder List") 1010
  • the inbox opened in window 1020 is, for example, the emails stored on the archive server, such as: the top email of "Peter Roescher" with the subject ("Subject ”)” Some interesting customer documentation .. ".
  • the Inbox 1020 window therefore lists both unarchived and archived emails. Unarchived emails are characterized by the used by the email management program, such as Microsoft Outlook, letter envelope icon, whereas according to the invention archived emails are marked with a CD icon.
  • an additional archive window 1030 the archiving of file attachments is visualized for the user. Furthermore, all function calls for archiving and subsequent reconstruction of emails via the graphical user interface can be controlled by the user.
  • the emails sent by the archive server to the email server in step 980 are preferably first cached in memory 350 as email 390 with file attachments 395.
  • the reconstructed email After transmission of the reconstructed email, it is then preferably transferred from main memory 350 into the memory 250 of the email client as email 280 to later be used e.g. stored in the local inbox / outbox for further processing.
  • an archived email is deleted by inputting a corresponding user input
  • a corresponding command is forwarded to the archive server by the email server via, for example, the email notification module 370 together with the assignment code contained in the reference file corresponding to the email.
  • the skeleton is read with identical assignment code and of all in the skeleton file referenced by a file identification code files, the reference counter is decremented. If a reference counter reaches the value "0", the file and possibly the corresponding data record in the allocation table 650 are deleted. Subsequently, the skeleton file is also deleted and a corresponding message is returned to the email server, after which the reference file is deleted.
  • the separation or dissolution of the email in the skeleton and the contained file attachments is carried out according to an embodiment in that first opens the email file and read the records are contained. When reading, the data records are parsed for the presence of file attachments based on typical file structures or known file suffixes. When recognizing files contained in the e-mail file, they are separated, therefore stored outside the e-mail file, and the file in the e-mail file is replaced by a reference to the paged file.
  • the result is a reference tree, which is all paged out and originally within the Email file as file attachments, possibly with additional attachments, contains existing files as references to the files as nodes or leaves of the tree. Later, after the file identification code has been calculated for each file, the references to this file identification code are supplemented, so that during the reconstruction a clear allocation of the outsourced files is given. The remaining e-mail file with references is also saved as the basic structure of the e-mail.
  • the methods and systems described herein for the memory-efficient management of electronic messages on suitable data processing equipment such as e.g. Computers, e.g. are organized in a client-server environment.

Claims (15)

  1. Procédé (800) de gestion, efficace en terme d'espace mémoire, de messages électroniques sur un serveur d'archivage, comprenant :
    - la décomposition (825) du message en une structure de base et en fichiers attachés contenus dans le message, les fichiers attachés pouvant à leur tour contenir des messages et d'autres fichiers attachés et ceux-ci étant également décomposés (830) selon le procédé ;
    - le calcul (840) d'un code univoque d'identification de fichier pour chaque fichier attaché ;
    - le calcul (850) d'une valeur de hash pour chaque fichier attaché ;
    - la vérification (860) à l'aide de la valeur de hash pour savoir si le fichier attaché est déjà enregistré comme fichier sur le serveur d'archivage ;
    - l'enregistrement (870) du fichier attaché comme fichier avec code respectif d'identification de fichier et valeur de hash, pour lequel aucun fichier avec une valeur de hash identique n'existe sur le serveur d'archivage ;
    - et au cas où un fichier avec une valeur de hash identique existe sur le serveur d'archivage : ajout (880) du code d'identification de fichier du fichier attaché respectif et incrémentation (885) d'un compteur de référence du fichier déjà enregistré ;
    - restitution (890) du code d'identification de fichier des fichiers attachés contenus dans le message à la structure de base ;
    - enregistrement (895) de la structure de base avec les codes d'identification de fichier comme pointeurs vers des fichiers sur le serveur d'archivage, correspondant aux fichiers attachés contenus dans le message.
  2. Procédé (800) selon la revendication 1, dans lequel les fichiers attachés contenus dans le message sont eux-mêmes à leur tour des messages avec des fichiers attachés, le message étant décomposé de manière récursive jusqu'à ce que tous les messages et/ou fichiers attachés soient remplacés par des pointeurs dans la structure de base.
  3. Procédé (800) selon l'une des revendications précédentes, dans lequel les messages électroniques sont des e-mails avec des fichiers attachés, qui sont envoyés et/ou reçus par un serveur d'e-mail et archivés sur le serveur d'archivage, en raison de quoi seuls des fichiers de pointeurs renvoyant respectivement aux e-mails archivés restent sans fichiers attachés sur le serveur d'e-mail.
  4. Procédé selon l'une des revendications précédentes, dans lequel les données contenues dans le message outre les fichiers attachés sont également enregistrées séparément comme fichier avec code d'identification et valeur de hash, la structure de base ne contenant elle-même aucune donnée mais uniquement des pointeurs.
  5. Procédé selon l'une des revendications précédentes, dans lequel sur requête d'un utilisateur pour récupérer un message, les étapes suivantes sont effectuées :
    - lecture (920) de la structure de base du message ;
    - chargement (940) des fichiers à partir de la mémoire à laquelle les pointeurs dans la structure de base renvoient ;
    - remplacement (930) des pointeurs par les fichiers comme fichiers attachés du message à reconstruire.
  6. Procédé (900) selon la revendication 5, dans lequel les pointeurs renvoient à des fichiers qui à leur tour contiennent des pointeurs, les pointeurs étant remplacés de manière récursive par des fichiers correspondants jusqu'à ce que tous les pointeurs soient remplacés par des fichiers (970).
  7. Procédé (900) selon l'une des revendications 5 ou 6, dans lequel la structure de base avec pointeurs est lue (920) par le serveur d'archivage lorsqu'une requête pour récupérer un message est adressée (910) à un serveur de messagerie, les pointeurs comprenant des codes univoques d'identification des fichiers enregistrés, les fichiers étant lus par le serveur d'archivage et les fichiers lus étant insérés (970) comme fichiers attachés dans la structure de base, le message ainsi reconstruit remplaçant (980) le fichier de pointeurs correspondant sur le serveur de messagerie.
  8. Procédé (900) selon la revendication 7, dans lequel, pour lire la structure de base, un code d'attribution est transmis (915) au serveur d'archivage depuis le fichier de pointeurs correspondant au message.
  9. Procédé (900) selon l'une des revendications 5 à 8, dans lequel, lors de la suppression d'un message, les compteurs de référence des fichiers référencés par les pointeurs de la structure de base du message à supprimer sont décrémentés.
  10. Programme informatique contenant un code de programme exécutable qui, lorsqu'il est installé sur un ordinateur en vue d'être exécuté, met en oeuvre un procédé selon l'une des revendications 1 à 9.
  11. Support de programme informatique, contenant un code de programme exécutable qui, lorsqu'il est installé sur un ordinateur en vue d'être exécuté, met en oeuvre un procédé selon l'une des revendications 1 à 9.
  12. Système (100) de gestion de messages électroniques efficace en terme d'espace mémoire, comprenant :
    - un serveur d'archivage (140, 400) avec un premier processeur (430) ;
    - une première mémoire (410) ;
    - un module de transfert des messages (485) ;
    - un module de calcul de valeur de hash (470) ;
    - un module de calcul d'un code d'identification de fichier (475) ; dans lequel
    - un module de gestion de compteur de référence (480) ; dans lequel :
    - le module de transfert des messages décompose un message à gérer en une structure de base et en fichiers attachés contenus dans le message, les fichiers attachés pouvant à leur tour contenir des messages et d'autres fichiers attachés et ceux-ci étant également décomposés par le système ;
    - la structure de base avec pointeurs vers les fichiers attachés contenus dans le message, et les fichiers attachés sont séparément enregistrés dans la première mémoire ;
    - le module de calcul du code d'identification de fichier calcule un code d'identification de fichier (695) pour chaque fichier attaché ;
    - le module de calcul de valeur de hash calcule une valeur de hash (670) pour chaque fichier attaché et, lorsque cette valeur de hash n'a pas encore été attribuée, le fichier attaché est enregistré dans la première mémoire avec le code d'identification de fichier ainsi que la valeur de hash,
    - et dans le cas contraire, lorsqu'un fichier existe déjà dans la première mémoire avec la valeur de hash calculée, le fichier attaché n'est pas enregistré de nouveau comme fichier mais le module de gestion du compteur de référence incrémente le compteur de référence (680) du fichier existant et l'ajoute au code d'identification de fichier, le code d'identification de fichier étant restitué à la structure de base comme pointeur vers le fichier enregistré et étant enregistré avec la structure de base.
  13. Système selon la revendication 12, le serveur d'archivage comprenant encore un module de reconstruction de message (490) lequel à l'aide du premier processeur, sur requête pour récupérer un message archivé, lit à partir d'une première mémoire la structure de base correspondante avec pointeurs ainsi que les fichiers référencés par les pointeurs, remplace dans la structure de base les pointeurs par lesdits fichiers et enregistre le message ainsi reconstruit (280) dans la première mémoire et/ou l'envoie à un serveur de messagerie ou un client de messagerie.
  14. Système selon l'une des revendications 12 ou 13 équipé d'un serveur de messagerie (130, 300), comprenant un second processeur (340) et une seconde mémoire (310), dans lequel le message à gérer est dans un premier temps enregistré dans la seconde mémoire, transféré sur le serveur de messagerie et remplacé dans la première mémoire par un fichier de pointeurs avec un code d'attribution, le code d'attribution renvoyant à la structure de base enregistrée dans la première mémoire.
  15. Système selon l'une des revendications 12 à 14 équipé d'un client de messagerie (110, 120, 200), comprenant un troisième processeur (230), une troisième mémoire (240), un écran (210), au moins une unité d'entrée (220) et un module de client de messagerie (260), permettant à un utilisateur à l'aide de l'unité d'entrée via ledit module de client de messagerie, avec le concours dudit troisième processeur, d'appeler des messages à l'écran depuis le serveur de messagerie sur une interface utilisateur (215) dudit module de client de messagerie, de les afficher à l'écran et de les enregistrer de manière efficace en terme d'espace mémoire sur le serveur d'archivage.
EP04013014A 2004-06-02 2004-06-02 Procédé et dispositif de gestion de courrier électronique Active EP1605649B1 (fr)

Priority Applications (3)

Application Number Priority Date Filing Date Title
EP04013014A EP1605649B1 (fr) 2004-06-02 2004-06-02 Procédé et dispositif de gestion de courrier électronique
DE502004001164T DE502004001164D1 (de) 2004-06-02 2004-06-02 Verfahren und Vorrichtung zum Verwalten von elektronischen Nachrichten
US11/145,496 US8073822B2 (en) 2004-06-02 2005-06-02 Method and apparatus for managing electronic messages

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
EP04013014A EP1605649B1 (fr) 2004-06-02 2004-06-02 Procédé et dispositif de gestion de courrier électronique

Publications (2)

Publication Number Publication Date
EP1605649A1 EP1605649A1 (fr) 2005-12-14
EP1605649B1 true EP1605649B1 (fr) 2006-08-09

Family

ID=34925216

Family Applications (1)

Application Number Title Priority Date Filing Date
EP04013014A Active EP1605649B1 (fr) 2004-06-02 2004-06-02 Procédé et dispositif de gestion de courrier électronique

Country Status (3)

Country Link
US (1) US8073822B2 (fr)
EP (1) EP1605649B1 (fr)
DE (1) DE502004001164D1 (fr)

Families Citing this family (51)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8849919B2 (en) * 2005-02-04 2014-09-30 International Business Machines Corporation Space-efficient mail storing and archiving based on communication structure
US7958120B2 (en) * 2005-05-10 2011-06-07 Netseer, Inc. Method and apparatus for distributed community finding
US9110985B2 (en) 2005-05-10 2015-08-18 Neetseer, Inc. Generating a conceptual association graph from large-scale loosely-grouped content
US7403949B2 (en) * 2005-08-17 2008-07-22 International Business Machines Corporation Elimination of redundant objects in storage systems
US7970743B1 (en) * 2005-09-15 2011-06-28 Emc Corporation Retention and disposition of stored content associated with multiple stored objects
WO2007084778A2 (fr) 2006-01-19 2007-07-26 Llial, Inc. Systèmes et procédés de création, de navigation et de recherche de voisinages d'informations du web
US20070185970A1 (en) * 2006-02-08 2007-08-09 International Business Machines Corporation Method, system, and computer program product for providing messaging services
US8533271B2 (en) * 2006-02-10 2013-09-10 Oracle International Corporation Electronic mail recovery utilizing recorded mapping table
US8843434B2 (en) * 2006-02-28 2014-09-23 Netseer, Inc. Methods and apparatus for visualizing, managing, monetizing, and personalizing knowledge search results on a user interface
US7594082B1 (en) * 2006-03-07 2009-09-22 Emc Corporation Resolving retention policy conflicts
US7814063B1 (en) 2006-03-07 2010-10-12 Emc Corporation Retention and disposition of components of a complex stored object
US7818300B1 (en) 2006-03-07 2010-10-19 Emc Corporation Consistent retention and disposition of managed content and associated metadata
US8903883B2 (en) * 2006-05-24 2014-12-02 International Business Machines Corporation Apparatus, system, and method for pattern-based archiving of business events
US7801862B1 (en) 2006-09-29 2010-09-21 Emc Corporation Retention of complex objects
US9063940B1 (en) 2006-09-29 2015-06-23 Emc Corporation Superseding objects in a retention system
US9817902B2 (en) 2006-10-27 2017-11-14 Netseer Acquisition, Inc. Methods and apparatus for matching relevant content to user intention
DE102006055964A1 (de) * 2006-11-24 2008-05-29 Bdt-Solutions Gmbh Verfahren und Vorrichtung zur Datensicherung
US7840537B2 (en) * 2006-12-22 2010-11-23 Commvault Systems, Inc. System and method for storing redundant information
US8849920B2 (en) * 2007-02-09 2014-09-30 International Business Machines Corporation Management of broadcast-distributed data entities
JP5181504B2 (ja) * 2007-03-22 2013-04-10 富士通株式会社 データ処理方法、プログラム及び情報処理装置
US10387892B2 (en) 2008-05-06 2019-08-20 Netseer, Inc. Discovering relevant concept and context for content node
US20100057765A1 (en) * 2008-08-28 2010-03-04 Jean-Claude Dispensa Email attachment storage method and system
US8949344B2 (en) * 2008-09-15 2015-02-03 Microsoft Corporation Asynchronous queued messaging for web applications
US8527608B2 (en) * 2009-03-27 2013-09-03 Blackberry Limited Method, apparatus and system for reducing download of redundant attachments
US8401996B2 (en) 2009-03-30 2013-03-19 Commvault Systems, Inc. Storing a variable number of instances of data objects
US8578120B2 (en) 2009-05-22 2013-11-05 Commvault Systems, Inc. Block-level single instancing
JP4852638B2 (ja) * 2009-09-28 2012-01-11 株式会社沖データ メール管理装置、複合装置、及び通信方法
EP2550629A4 (fr) 2010-03-23 2017-01-11 Nokia Technologies Oy Procédé et appareil pour la gestion de fichiers dans un compte en ligne
US9111261B2 (en) 2010-04-23 2015-08-18 International Business Machines Corporation Method and system for management of electronic mail communication
JP2012027795A (ja) * 2010-07-26 2012-02-09 Canon Inc 文書データ共有システムおよびユーザ装置
US9785917B2 (en) * 2010-08-17 2017-10-10 Blackberry Limited System and method for obtaining a portion of an archived email message
WO2012045023A2 (fr) 2010-09-30 2012-04-05 Commvault Systems, Inc. Archivage d'objets de données au moyen de copies secondaires
US9123021B2 (en) * 2010-12-08 2015-09-01 Microsoft Technology Licensing, Llc Searching linked content using an external search system
US20140280656A1 (en) * 2011-10-14 2014-09-18 Appbyyou Gmbh Method employing at least one central processing unit (cpu)
US9594760B1 (en) * 2012-02-27 2017-03-14 Veritas Technologies Systems and methods for archiving email messages
US9020890B2 (en) 2012-03-30 2015-04-28 Commvault Systems, Inc. Smart archiving and data previewing for mobile devices
WO2013155066A2 (fr) * 2012-04-09 2013-10-17 Exacttarget, Inc. Système et procédé de distribution sécurisée des communications
US9262429B2 (en) 2012-08-13 2016-02-16 Microsoft Technology Licensing, Llc De-duplicating attachments on message delivery and automated repair of attachments
US10311085B2 (en) 2012-08-31 2019-06-04 Netseer, Inc. Concept-level user intent profile extraction and applications
US9633022B2 (en) 2012-12-28 2017-04-25 Commvault Systems, Inc. Backup and restoration for a deduplicated file system
US10324897B2 (en) 2014-01-27 2019-06-18 Commvault Systems, Inc. Techniques for serving archived electronic mail
JP6331686B2 (ja) * 2014-05-21 2018-05-30 株式会社リコー 情報処理システム、情報処理方法、及びプログラム
US10110522B1 (en) 2014-12-15 2018-10-23 Amazon Technologies, Inc. Setting sharing options for files using a messaging client
US10320727B1 (en) 2014-12-15 2019-06-11 Amazon Technologies, Inc. Managing document feedback on a sharing service using a messaging client
US10324914B2 (en) 2015-05-20 2019-06-18 Commvalut Systems, Inc. Handling user queries against production and archive storage systems, such as for enterprise customers having large and/or numerous files
CN107294834A (zh) * 2016-03-31 2017-10-24 阿里巴巴集团控股有限公司 一种识别垃圾邮件的方法和装置
US10693952B2 (en) 2017-10-23 2020-06-23 Salesforce.Com, Inc. Technologies for low latency messaging
US11252119B2 (en) 2018-06-04 2022-02-15 Salesforce.Com, Inc. Message logging using two-stage message logging mechanisms
US10721193B1 (en) * 2019-04-15 2020-07-21 Microsoft Technology Licensing, Llc Reducing avoidable transmission of an attachment to a message by comparing the fingerprint of the attachment to be sent to that of an attachment that was previously sent or received by the user and indicating to the user when a match occurs that the attachment is redundant
US11641331B2 (en) * 2019-06-04 2023-05-02 Microsoft Technology Licensing, Llc System and method for blocking distribution of non-acceptable attachments
JP2022049958A (ja) * 2020-09-17 2022-03-30 ブラザー工業株式会社 印刷実行部に印刷を実行させるための制御装置とそのためのコンピュータプログラム

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1035690A2 (fr) * 1999-03-08 2000-09-13 Sun Microsystems, Inc. Archivage du courrier électronique

Family Cites Families (30)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US1035690A (en) * 1911-09-05 1912-08-13 Clifton Corley Slub-catcher and tension device.
US6564321B2 (en) * 1995-04-28 2003-05-13 Bobo Ii Charles R Systems and methods for storing, delivering, and managing messages
US7069451B1 (en) * 1995-02-13 2006-06-27 Intertrust Technologies Corp. Systems and methods for secure transaction management and electronic rights protection
US5781901A (en) * 1995-12-21 1998-07-14 Intel Corporation Transmitting electronic mail attachment over a network using a e-mail page
US5903723A (en) * 1995-12-21 1999-05-11 Intel Corporation Method and apparatus for transmitting electronic mail attachments with attachment references
US6076101A (en) * 1996-09-12 2000-06-13 Fujitsu Limited Electronic mail processing system with bonus point tracking
JP2954062B2 (ja) * 1997-02-25 1999-09-27 日本電気通信システム株式会社 電子メールシステム
US6014689A (en) * 1997-06-03 2000-01-11 Smith Micro Software Inc. E-mail system with a video e-mail player
US6009462A (en) * 1997-06-16 1999-12-28 Digital Equipment Corporation Replacing large bit component of electronic mail (e-mail) message with hot-link in distributed computer system
JP2000501540A (ja) * 1997-06-17 2000-02-08 パーデュー ファーマ エルピー 自己破棄文書およびｅメールメッセージシステム
US5999967A (en) * 1997-08-17 1999-12-07 Sundsted; Todd Electronic mail filtering by electronic stamp
US5940823A (en) * 1997-11-10 1999-08-17 International Business Machines Corporation System for the distribution and storage of electronic mail information
US7047248B1 (en) * 1997-11-19 2006-05-16 International Business Machines Corporation Data processing system and method for archiving and accessing electronic messages
US6073133A (en) * 1998-05-15 2000-06-06 Micron Electronics Inc. Electronic mail attachment verifier
US7886008B2 (en) * 1999-07-28 2011-02-08 Rpost International Limited System and method for verifying delivery and integrity of electronic messages
DE10064627B4 (de) * 2000-02-02 2004-02-12 International Business Machines Corp. Verfahren und System für die Verarbeitung von E-Mail-Nachrichten in einem Datenübertragungssystem
US6898622B1 (en) * 2000-05-04 2005-05-24 Bellsouth Intellectual Property Corp. Method for composing packages of electronic mail attachments
US20020059384A1 (en) * 2000-07-13 2002-05-16 Koninklijke Philips Electronics N.V. Substituting URL for attachment in forwarding electronic content
US7039678B1 (en) * 2000-09-07 2006-05-02 Axis Mobile, Ltd. E-mail proxy
US7003551B2 (en) * 2000-11-30 2006-02-21 Bellsouth Intellectual Property Corp. Method and apparatus for minimizing storage of common attachment files in an e-mail communications server
US6820081B1 (en) * 2001-03-19 2004-11-16 Attenex Corporation System and method for evaluating a structured message store for message redundancy
JP2003067306A (ja) * 2001-08-24 2003-03-07 Hitachi Ltd 電子メールの蓄積管理方法
US7231427B1 (en) * 2001-08-30 2007-06-12 Qiang Du E-mail protocol using assumed send and reply address and smart E-mail archiving by addressee and addressor
US7117210B2 (en) * 2001-09-06 2006-10-03 Danger, Inc. System and method of distributing a file by email
US6915333B2 (en) * 2001-12-14 2005-07-05 International Business Machines Corporation Method of managing attached document
US20040064733A1 (en) * 2002-07-05 2004-04-01 Judosoft Inc. System and method for Concurrent Version Control and Information Management of files and documents sent as attachments through e-mail or web-mail
CA2414154A1 (fr) * 2002-12-12 2004-06-12 Mark W. Brooks Systeme et methode de transmission d'un fichier associe a du courrier electronique
US20050005164A1 (en) * 2003-06-20 2005-01-06 Bronwyn Syiek Apparatus and method for precluding e-mail distribution
US20060031340A1 (en) * 2004-07-12 2006-02-09 Boban Mathew Apparatus and method for advanced attachment filtering within an integrated messaging platform
US8805934B2 (en) * 2004-09-02 2014-08-12 Vmware, Inc. System and method for enabling an external-system view of email attachments

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1035690A2 (fr) * 1999-03-08 2000-09-13 Sun Microsystems, Inc. Archivage du courrier électronique

Also Published As

Publication number Publication date
US8073822B2 (en) 2011-12-06
US20050283461A1 (en) 2005-12-22
EP1605649A1 (fr) 2005-12-14
DE502004001164D1 (de) 2006-09-21

Similar Documents

Publication Publication Date Title
EP1605649B1 (fr) Procédé et dispositif de gestion de courrier électronique
DE602005005312T2 (de) Verfahren und System zur Verwaltung elektronischer Nachrichten
DE602006000660T2 (de) Platzsparende Speicherung und Archivierung von elektronischer Post auf Basis einer Kommunikationsstruktur
DE10346897B4 (de) System und Verfahren zum Zuordnen einer Anhangsdatei einer E-Mail zu einer separaten Speicherposition
DE10064627B4 (de) Verfahren und System für die Verarbeitung von E-Mail-Nachrichten in einem Datenübertragungssystem
DE60211489T2 (de) System und Verfahren zur Bearbeitung von in mehreren Nachrichtenspeichern gespeicherten Nachrichten
DE10330282B4 (de) Vorrichtung und Verfahren zum benutzerseitigen Bearbeiten von elektronischen Nachrichten mit Datei-Anlagen
DE60130685T2 (de) System und verfahren zum steuern und organisieren von email
DE69834640T2 (de) System und Verfahren zur Synchronisierung elektronischer Nachrichten über ein Netzwerk
DE69838180T2 (de) Verfahren und rechnerprogrammprodukt zur klassifizierung von in einem netzwerkstack verarbeiteten netzübertragungspaketen
EP1151399B1 (fr) Integration des systèmes de base de données hétérogènes
DE69910952T2 (de) Priorität- und Sicherheit-Kodierungssystem für elektronische Post nachrichten
DE102005058110B4 (de) Verfahren zum Ermitteln möglicher Empfänger
EP1530771B1 (fr) Procede et systeme de transmission de notifications a des utilisateurs d'un systeme de logistique
DE602005004671T2 (de) Verfahren und system zum senden von elektronischer post über ein netzwerk
DE69818549T2 (de) Volltextindizierte Nachrichtenspeicher
DE60004211T2 (de) Entfernung von duplizierten objekten aus einem objektspeicher
DE60306209T2 (de) Verfahren, mobile vorrichtungen und rechnerlesbare media zur datenverwaltung
DE19844013A1 (de) Strukturierter Arbeitsordner
DE10151648B4 (de) Verfahren und Vorrichtung zum Erfassen und Speichern von während einer computerbasierten Sitzung gemachten Notizen
EP1246100A2 (fr) Méthode, appareil et serveur du courrier électronique pour reconnaítre des courriers électroniques indésirés
EP2545464B1 (fr) Procédé de création et de gestion d'une archive longue durée de grand volume
DE602004002777T2 (de) Vorrichtung zur Behandlung von E-Mails in einer Mehrbenutzer-Umgebung
DE10113429B4 (de) E-Mail Gerät, Verfahren zum Erzeugen einer Gruppe von Mail-Adressen, sowie Computerlesbares Medium
DE60221965T2 (de) Verfahren, System und Server zum Senden und Empfangen von E-mails mit verschiedenen Adressen

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20050309

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LI LU MC NL PL PT RO SE SI SK TR

AX Request for extension of the european patent

Extension state: AL HR LT LV MK

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

RIN1 Information on inventor provided before grant (corrected)

Inventor name: WINTER, CHRISTIAN

Inventor name: SELL, JOERG-STEFAN, IXOS SOFTWARE AG

Inventor name: HEISS, FRANZ, DR., IXOS SOFTWARE AG

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): DE FR GB

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

Free format text: NOT ENGLISH

AKX Designation fees paid

Designated state(s): DE FR GB

REF Corresponds to:

Ref document number: 502004001164

Country of ref document: DE

Date of ref document: 20060921

Kind code of ref document: P

GBT Gb: translation of ep patent filed (gb section 77(6)(a)/1977)

Effective date: 20061024

ET Fr: translation filed
PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

26N No opposition filed

Effective date: 20070510

REG Reference to a national code

Ref country code: GB

Ref legal event code: 732E

Free format text: REGISTERED BETWEEN 20100617 AND 20100623

REG Reference to a national code

Ref country code: FR

Ref legal event code: TP

REG Reference to a national code

Ref country code: DE

Ref legal event code: R082

Ref document number: 502004001164

Country of ref document: DE

Representative=s name: PATENTANWAELTE BETTEN & RESCH, DE

REG Reference to a national code

Ref country code: DE

Ref legal event code: R081

Ref document number: 502004001164

Country of ref document: DE

Owner name: OPEN TEXT S.A., LU

Free format text: FORMER OWNER: OPEN TEXT SOFTWARE GMBH, 85630 GRASBRUNN, DE

Effective date: 20141020

Ref country code: DE

Ref legal event code: R082

Ref document number: 502004001164

Country of ref document: DE

Representative=s name: PATENTANWAELTE BETTEN & RESCH, DE

Effective date: 20141020

Ref country code: DE

Ref legal event code: R082

Ref document number: 502004001164

Country of ref document: DE

Representative=s name: BETTEN & RESCH PATENT- UND RECHTSANWAELTE PART, DE

Effective date: 20141020

REG Reference to a national code

Ref country code: GB

Ref legal event code: 732E

Free format text: REGISTERED BETWEEN 20141120 AND 20141126

REG Reference to a national code

Ref country code: FR

Ref legal event code: TP

Owner name: OPEN TEXT S.A., LU

Effective date: 20141203

REG Reference to a national code

Ref country code: FR

Ref legal event code: PLFP

Year of fee payment: 13

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: FR

Payment date: 20160516

Year of fee payment: 13

REG Reference to a national code

Ref country code: FR

Ref legal event code: ST

Effective date: 20180228

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: FR

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20170630

REG Reference to a national code

Ref country code: DE

Ref legal event code: R079

Ref document number: 502004001164

Country of ref document: DE

Free format text: PREVIOUS MAIN CLASS: H04L0012580000

Ipc: H04L0051000000

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: DE

Payment date: 20230502

Year of fee payment: 20

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: GB

Payment date: 20230504

Year of fee payment: 20