Users routinely attempt to send large attachments using electronic messages. Many message gateways limit the size of an attachment that may be delivered/received. The message including the attachments is not delivered when the size of an attachment or collection of attachments exceeds these limits. The sender of the message containing the attachment may or may not be notified that the message was not delivered.
This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used as an aid in determining the scope of the claimed subject matter.
The size of attachments to an electronic message are examined before the message is sent to determine if the attachments exceed a size threshold. When the size of the attachments exceed the threshold, one or more of the attachments are uploaded to a shared location that is accessible to the recipients of the message. A link replaces each attachment that was uploaded to the shared location. Permissions are automatically set at the shared location such that each of the recipients of the message are able to access the uploaded attachment.
Referring now to the drawings, in which like numerals represent like elements, various embodiment will be described. In particular,
Generally, program modules include routines, programs, components, data structures, and other types of structures that perform particular tasks or implement particular abstract data types. Other computer system configurations may also be used, including hand-held devices, multiprocessor systems, microprocessor-based or programmable consumer electronics, minicomputers, mainframe computers, and the like. Distributed computing environments may also be used where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote memory storage devices.
Referring now to
A basic input/output system containing the basic routines that help to transfer information between elements within the computer, such as during startup, is stored in the ROM 10. The computer 100 further includes a mass storage device 14 for storing an operating system 16, messaging application(s) 24, Web Browser 25, and attachment manager 26 which will be described in greater detail below.
The mass storage device 14 is connected to the CPU 5 through a mass storage controller (not shown) connected to the bus 12. The mass storage device 14 and its associated computer-readable media provide non-volatile storage for the computer 100. Although the description of computer-readable media contained herein refers to a mass storage device, such as a hard disk or CD-ROM drive, the computer-readable media can be any available media that can be accessed by the computer 100.
By way of example, and not limitation, computer-readable media may comprise computer storage media and communication media. Computer storage media includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storage of information such as computer-readable instructions, data structures, program modules or other data. Computer storage media includes, but is not limited to, RAM, ROM, Erasable Programmable Read Only Memory (“EPROM”), Electrically Erasable Programmable Read Only Memory (“EEPROM”), flash memory or other solid state memory technology, CD-ROM, digital versatile disks (“DVD”), or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by the computer 100.
Computer 100 operates in a networked environment using logical connections to remote computers through a network 18, such as the Internet. The computer 100 may connect to the network 18 through a network interface unit 20 connected to the bus 12. The network connection may be wireless and/or wired. The network interface unit 20 may also be utilized to connect to other types of networks and remote computer systems. The computer 100 may also include an input/output controller 22 for receiving and processing input from a number of other devices, including a keyboard, mouse, or electronic stylus (not shown in
As mentioned briefly above, a number of program modules and data files may be stored in the mass storage device 14 and RAM 9 of the computer 100, including an operating system 16 suitable for controlling the operation of a computer, such as the WINDOWS PHONE 7®, WINDOWS 7®, or WINDOWS SERVER® operating system from MICROSOFT CORPORATION of Redmond, Wash. The mass storage device 14 and RAM 9 may also store one or more program modules. In particular, the mass storage device 14 and the RAM 9 may store one or more application programs, including one or more messaging application(s) 24 and Web browser 25.
A user interface 15 is used by a user to interact with applications and documents. Messaging application(s) 24 may be one or more different messaging applications. For example, computer 100 may include an email application, an Instant Messaging (IM) application, an SMS, MMS application, a real-time information network (e.g. Twitter® interface), a social networking application, and the like. According to an embodiment, messaging application 24 is an email application, such as MICROSOFT OUTLOOK®. The messaging application(s) may be client based and/or web based. For example, a network based message service 17 may be used, such as: MICROSOFT WINDOWS LIVE or some other network based email and messaging service.
Network share 27 is configured to store content (e.g. documents, spreadsheet, Web content, and the like) that are accessible to one or more users through IP network 18. For example, network share 27 may store content that is accessible by users located at one or more locations.
Attachment manager 26 is configured to upload attachments that exceed a size threshold and replace the attachment with a link in the message. The term “link” refers to an address that represents a location of content. For example, a link may be in the form of a Uniform Resource Locator (URL) that specifies a network location of where the attachment/content is stored. Clicking the link generally retrieves the content that is pointed to by the link. Attachment manager 26 may be located externally from an application, e.g. messaging application 24, as shown or may be a part of an application. Further, all/some of the functionality provided by attachment manager 26 may be located internally/externally from a messaging application.
According to an embodiment, attachment manager 26 is configured to present linked content and/or attachments in an attachment area of an electronic message for easier access than having to locate the link within the body of the message. Attachment manager 26 automatically determines the size of attachments to an electronic message before the message is sent. When the size of the attachments exceed the predetermined threshold, one or more of the attachments are uploaded to a shared location that is accessible to the recipients of the message. A link replaces each attachment within the message that was uploaded to the shared location. Attachment manager 26 automatically sets the permissions of the attachment(s) at the shared location such that each of the recipients of the message are able to access the uploaded attachment(s). The attachments may be many different types of content, such as word processing documents, spreadsheets, slides, website content and the like. When the message is delivered to the recipient, the attachment that is addressed by the link may be automatically downloaded and included with the display of the link or in place of the link within the message. More details regarding the attachment manager are disclosed below.
The computing devices may be any type of computing device that is configured to perform the operations relating to sending and receiving electronic messages that include attachments and links to content. For example, some of the computing devices may be: mobile computing devices (e.g. cellular phones, tablets, smart phones, laptops, and the like); desktop computing devices and servers. Some computing devices may be arranged to provide an online service (e.g. messaging service 240 that is configured for sending and receiving electronic messages), some may be arranged as data shares, some may be arranged in local networks, some may be arranged in networks accessible through the Internet, and the like.
The computing devices are coupled through network 18. Network 18 may be many different types of networks. For example, network 18 may be an IP network, a carrier network for cellular communications, and the like. Generally, network 18 is used to transmit data between computing devices, such as computing device 1, computing device 2, network share 230 and messaging service 240.
Computing device 1 includes messaging application 212 and user interface 216. As illustrated, computing device 1 is used by a user to interact with electronic messages, content in a network share (e.g. attachment 232) and the like.
User interface (UI) 216 is used to interact with an application and content, such as messaging application 212 and attachment(s) 232. One or more user interfaces of one or more types may be used to interact with the content. For example, UI 216 may include the use of a context menu, a menu within a menu bar, a menu item selected from a ribbon user interface, a graphical menu, and the like. Generally, UI 216 is configured such that a user may easily interact with content and electronic messages. For example, a user may simply select an option within UI 216 to automatically upload and permission an attachment that exceeds a predetermined size to a shared location. UI 216 may also be used to set permissions for the attachment at the shared location and to access the attachment and/or link to the attachment.
Upon receipt of the message, the recipient of the message may access the uploaded attachment using the link within the received message. According to an embodiment, the attachment is downloaded to the recipient's device automatically. The link to the attachment may/may not be removed from the message when the attachment is downloaded. For example, upon receipt of the message including the link to the attachment, attachment manager 26 may automatically download the attachment, remove the link from the message and attach the downloaded attachment to the message. In this way, the recipient receives the message as if the attachment was delivered with the message.
Messaging application 212 may be a client based application, such as an email application, an Instant Messaging Application, a social media application, and the like. Generally, messaging application 212 is used to send and receive electronic messages of one or more types. A network based messaging service 240 may be used in addition to messaging application 212 or instead of one or more of the different messaging applications. For example, a web interface may be used to access messaging service 240.
Messaging service 240 may be used to process electronic messages between one or more computing devices, such as computing device 1 and computing device 2. Messaging service 240 may be configured to process different message types, such as SMS, MMS, email, messages for social networks and the like. Messaging service 240 may be configured with the functionality of attachment manager 26 and one or more message types may be used to communicate the electronic messages including links to the uploaded attachment(s).
Computing device 2 includes one or more applications, such as a web browser (222) that may be configured to access a messaging service, such as a web based email service and to interact with content. For example, a web browser may be used to access messaging service 240 and create an electronic message including one or more attachments.
One or more network shares (e.g. Network share 230) may be used to store content. The content may be any type of content that is linked/attached within a message, such as word processing documents, spreadsheets, slides, website content and the like Network share 230 is accessible by the computing devices that interact with the content. The network share may be associated with an online service that supports online access/interaction with content. The network share(s) may be associated with one or more online services. For example, different network shares may be associated with different types of attachments (e.g. a network share for a video service, picture service, document service, and the like.)
Attachment manager 26 is configured to detect any attachments to an electronic message and determine when one or more of the attachments is to be uploaded to a network share based on a size of the attachments. The attachments may be to any type of content, such as word processing documents, spreadsheets, slides, pictures, videos, website content and the like. Attachment manager 26 determines if one or more or a combination of attachments exceed a predetermined size threshold. According to an embodiment, the predetermined size threshold is based on a size restriction of a message gateway that sets a maximum size limitation for an electronic message (e.g. 1 MB, 5 MB, 10 MB . . . ). The predetermined size threshold may be configured by an authorized user (e.g. system administrator). When one or more of the attachments exceed the threshold, attachment manager 26 is configured to upload one or more of the attachments. For example, all/portion of the attachments may be uploaded to the shared location and removed from the message such that the size of the message when it is sent is below the threshold. When one attachment or a combination of the attachments exceed the threshold, each attachment to the message is uploaded to the shared location. Each attachment that is uploaded is replaced with a link to the attachment at the shared location within the message. According to an embodiment, the link(s) are placed within an attachment area of the electronic message such that when a user receives the message the links to the uploaded attachments are easily locatable. A single link may also be used to address all of the attachments that were uploaded to the shared location (e.g. the link may point to a folder containing the uploaded attachments). The attachments may be uploaded before the message is sent and/or after the message is sent. According to an embodiment, the attachments are uploaded before a message is sent such that any errors in uploading the attachment to the shared location may be presented to the sender of the electronic message before the message is sent.
According to an embodiment, any attachments that were uploaded due to the size exceeding the threshold are automatically downloaded and included within the attachment area before the user receiving the message views the message. For example, upon receipt of the message, the linked attachment may be automatically downloaded and included with the message. All/some of the linked content may be automatically downloaded. The links to the attachments may/may not be removed from the message after the attachments are downloaded.
The electronic message may be accessed a number of ways. For example, a web browser may access an electronic mail service, an email application on a computing device may be configured to send/receive emails from one or more different services, and the like.
When electronic message is created, attachment 310 is included with the message. The attachments may be to any type of content, such as word processing documents, spreadsheets, slides, websites and the like. Generally, the attachment may be to any type of content that is accessible by a computing device.
When a size of an attachment (or a combination of attachments) exceeds a predetermined size, message 315 may be presented to inform the sender that the size of the attachments are too large to send. Other messages may be displayed to the user indicating that the size of the attachment is too large to send. According to an embodiment, upload option 320 is presented that allows a user to select the upload option before the attachment is uploaded to a shared location. The attachment may be automatically uploaded to a shared location without providing upload option 320. For example, a user may have previously configured an automatic upload option to upload any attachments without user confirmation to a shared location. In this scenario, a message, such as message 330, may be provided along with change option 335 that provides a user with options relating to the attachment (e.g. change permissions for the attachment, move the attachment to a different shared location, remove the attachment from the shared location, and the like.)
When one or more of the attachments are uploaded to a shared location, change option 430 may be used to make changes relating to the attachment. For example, a user may select change option to change the permissions for access to the uploaded attachment at the shared location. For example, some of the recipients may have permissions set that allow them read/write access, other recipients may only have read access. Permissions may also be set to control the forwarding of the attachment/link to the attachment (e.g. prevent an unauthorized user from receiving the attachment and/or a link to the attachment).
According to an embodiment, the link to the uploaded content (410) is located within an attachment area of the message such that the user does not have to search for the linked content within the body of the electronic message.
The attachment area may be located within many different areas of the display. Generally, the attachment area is located such that the display of the attached area remains visible even though the body of the message is scrolled to change the view of the message. A graphical indicator, such as an icon, may be displayed within the attachment area near the link to provide additional information relating to the attachment. The graphical indicator may be selected to indicate a type of the content and/or other characteristics relating to the linked content. For example, a document icon may be used to show the content is a document, a web icon may be used for web content, a spreadsheet icon may be used for spreadsheets, a picture icon may be used for pictures, a message icon may be used for messages, an online service icon may be used to show where the attachment has been uploaded (e.g. a video service icon to indicate that the attachment has been uploaded to video service 1, a picture service icon . . . ) and the like.
After a start block, process 600 moves to operation 610, where the electronic message is accessed. The electronic message may be any electronic message that includes the ability to attach content. According to an embodiment, the electronic messages are email messages. Other messages may also be used attachments, such as SMS, MMS, Instant Messages, social network messages, and the like.
Flowing to operation 620, any attachments that are associated with the electronic message are detected. According to an embodiment, the detection occurs before the message is sent. A size of the attachment(s) is also determined.
Moving to operation 630, a determination is made as to what attachments are to be uploaded based on determining that the size of the attachments exceed a predetermined size threshold. According to an embodiment, the predetermined size threshold is based on a size limitation for delivery of an electronic message (e.g. 1 MB, 5 MB, 10 MB . . . ). The predetermined size threshold may be configured by a user (e.g. system administrator). When one or more of the attachments exceed the threshold, attachment manager 26 is configured to upload one or more of the attachments. For example, all/portion of the attachments may be uploaded to the shared location such that when the uploaded attachments are removed from the message, the size of the message is below the threshold. According to an embodiment, if any one attachment is uploaded, each attachment within the message is uploaded.
Transitioning to operation 640, the determined attachments are uploaded to one or more shared locations. The attachments may be uploaded to shared locations based on different criteria. For example, a shared location may be selected based on a type of the attachment (e.g. video attachments to a shared location that hosts videos, picture attachments to a shared location that hosts pictures, documents to a shared location that hosts documents, and the like.) A shared location may also be selected based on shared locations that are selected by the sender and/or one or more of the recipients. For example, each recipient may have configured preferences indicating a desired shared location. The attachment may be uploaded to more than one shared location (e.g. the attachment is uploaded to each recipient's configured shared location).
Flowing to operation 650, permissions for accessing the uploaded attachments are set such that each recipient is able to access the uploaded attachment. According to an embodiment, the attachment is set to read/write permission for each recipient of the message. A user may change these permissions by accessing a change option within the electronic message and/or by accessing the shared location where the attachment is uploaded.
Moving to operation 660, the attachments within the message are replaced with links that may be used to access each of the uploaded attachments.
Transitioning to operation 670, the electronic message is sent to the recipients.
The process then flows to an end block and returns to processing other actions.
After a start block, process 700 moves to operation 710, where the electronic message is received. The electronic message may be any electronic message that includes a link to an attachment that was uploaded to a shared location. According to an embodiment, the electronic messages are email messages. Other messages may also include links, such as SMS, MMS, Instant Messages, social network messages, and the like. The message may be received by a client based application and/or a Web based application.
Flowing to operation 720, any links to uploaded attachments within the electronic message are detected. A link may be associated with an uploaded attachment using different methods. For example, the link itself may contain information that indicates the content that the link addresses was uploaded due to a size limitation. According to an embodiment, the links are detected before the received message is viewed.
Moving to operation 730, the attachment may be automatically downloaded. According to an embodiment, the content is automatically downloaded and displayed within the attachment area of the electronic message before the user receiving the message views the message.
Transitioning to operation 740, the links to the content that is automatically downloaded are replaced with an attachment of the content.
Flowing to operation 750, the electronic message is displayed with the attachment with the electronic message. When a user views the message, the attachment may be opened.
The process then flows to an end block and returns to processing other actions.
The above specification, examples and data provide a complete description of the manufacture and use of the composition of the invention. Since many embodiments of the invention can be made without departing from the spirit and scope of the invention, the invention resides in the claims hereinafter appended.
Number | Name | Date | Kind |
---|---|---|---|
5355472 | Lewis | Oct 1994 | A |
5787480 | Scales et al. | Jul 1998 | A |
5864870 | Guck | Jan 1999 | A |
5903723 | Beck | May 1999 | A |
6219818 | Freivald et al. | Apr 2001 | B1 |
6275850 | Beyda | Aug 2001 | B1 |
6314425 | Serbinis et al. | Nov 2001 | B1 |
6493758 | McLain | Dec 2002 | B1 |
6533822 | Kupiec | Mar 2003 | B2 |
6687741 | Ramaley et al. | Feb 2004 | B1 |
6718368 | Ayyadurai | Apr 2004 | B1 |
6763496 | Hennings et al. | Jul 2004 | B1 |
6782423 | Nakayama et al. | Aug 2004 | B1 |
6839741 | Tsai | Jan 2005 | B1 |
6883009 | Yoo | Apr 2005 | B2 |
6954934 | Kumar | Oct 2005 | B2 |
6978276 | Demsky et al. | Dec 2005 | B2 |
7003551 | Malik | Feb 2006 | B2 |
7028075 | Morris | Apr 2006 | B2 |
7054905 | Hanna et al. | May 2006 | B1 |
7089287 | Bellotti et al. | Aug 2006 | B2 |
7107518 | Ramaley et al. | Sep 2006 | B2 |
7113948 | Jhingan et al. | Sep 2006 | B2 |
7127670 | Bendik | Oct 2006 | B2 |
7130885 | Chandra et al. | Oct 2006 | B2 |
7143091 | Charnock et al. | Nov 2006 | B2 |
7178099 | Meyer et al. | Feb 2007 | B2 |
7194514 | Yen et al. | Mar 2007 | B1 |
7290034 | Budd et al. | Oct 2007 | B2 |
7353232 | Kalucha et al. | Apr 2008 | B1 |
7392280 | Rohall et al. | Jun 2008 | B2 |
7401291 | Ramaley et al. | Jul 2008 | B2 |
7409394 | Lee | Aug 2008 | B2 |
7409424 | Parker | Aug 2008 | B2 |
7424676 | Carlson et al. | Sep 2008 | B1 |
7444382 | Malik | Oct 2008 | B2 |
7509386 | Miyashita | Mar 2009 | B2 |
7536440 | Budd et al. | May 2009 | B2 |
7546352 | Bhattiprolu et al. | Jun 2009 | B1 |
7565409 | Heilbron et al. | Jul 2009 | B2 |
7580982 | Owen et al. | Aug 2009 | B2 |
7593943 | Clarke et al. | Sep 2009 | B2 |
7650387 | Foo | Jan 2010 | B2 |
7730082 | Sah et al. | Jun 2010 | B2 |
7752269 | Chan et al. | Jul 2010 | B2 |
7783711 | LeVasseur et al. | Aug 2010 | B2 |
7783972 | Camps et al. | Aug 2010 | B2 |
7814425 | O'Shaugnessy et al. | Oct 2010 | B1 |
7840642 | Naick et al. | Nov 2010 | B2 |
7908332 | Malik | Mar 2011 | B2 |
8108464 | Rochelle et al. | Jan 2012 | B1 |
8140975 | Lemay et al. | Mar 2012 | B2 |
8145707 | Thayer et al. | Mar 2012 | B2 |
8176123 | Wang et al. | May 2012 | B1 |
8185591 | Lewis | May 2012 | B1 |
8458269 | Friedman et al. | Jun 2013 | B2 |
8682989 | Meisels et al. | Mar 2014 | B2 |
20010051991 | Beyda et al. | Dec 2001 | A1 |
20010054073 | Ruppert et al. | Dec 2001 | A1 |
20020016818 | Kirani et al. | Feb 2002 | A1 |
20020059384 | Kaars | May 2002 | A1 |
20020062356 | Clarke et al. | May 2002 | A1 |
20020065892 | Malik | May 2002 | A1 |
20020107931 | Singh et al. | Aug 2002 | A1 |
20020129056 | Conant et al. | Sep 2002 | A1 |
20020133633 | Kumar | Sep 2002 | A1 |
20020143691 | Ramaley et al. | Oct 2002 | A1 |
20020174010 | Rice, III | Nov 2002 | A1 |
20030028528 | Christensen et al. | Feb 2003 | A1 |
20030055907 | Stiers | Mar 2003 | A1 |
20040034688 | Dunn | Feb 2004 | A1 |
20040068545 | Daniell et al. | Apr 2004 | A1 |
20040103044 | Vandewater et al. | May 2004 | A1 |
20040158607 | Coppinger et al. | Aug 2004 | A1 |
20040186894 | Jhingan et al. | Sep 2004 | A1 |
20040243672 | Markki et al. | Dec 2004 | A1 |
20050010799 | Kelley et al. | Jan 2005 | A1 |
20050033813 | Bhogal et al. | Feb 2005 | A1 |
20050044492 | Ramaley et al. | Feb 2005 | A1 |
20050060382 | Spector et al. | Mar 2005 | A1 |
20050114672 | Duncan et al. | May 2005 | A1 |
20050122345 | Kirn et al. | Jun 2005 | A1 |
20050166154 | Wilson | Jul 2005 | A1 |
20050188026 | Hilbert et al. | Aug 2005 | A1 |
20050251443 | Chan | Nov 2005 | A1 |
20050289221 | Steele | Dec 2005 | A1 |
20060004819 | Claudatos et al. | Jan 2006 | A1 |
20060020673 | Sorge et al. | Jan 2006 | A1 |
20060031309 | Luoffo et al. | Feb 2006 | A1 |
20060075046 | Yozell-Epstein et al. | Apr 2006 | A1 |
20060095527 | Malik | May 2006 | A1 |
20060195526 | Lederer | Aug 2006 | A1 |
20060206570 | Heidloff et al. | Sep 2006 | A1 |
20060259524 | Horton | Nov 2006 | A1 |
20060282762 | Diamond et al. | Dec 2006 | A1 |
20060294455 | Morris et al. | Dec 2006 | A1 |
20070005717 | LeVasseur et al. | Jan 2007 | A1 |
20070022166 | Bhogal et al. | Jan 2007 | A1 |
20070118794 | Hollander et al. | May 2007 | A1 |
20070130259 | Daniell et al. | Jun 2007 | A1 |
20070136814 | Lee et al. | Jun 2007 | A1 |
20070143419 | Plas | Jun 2007 | A1 |
20070143425 | Kieselbach et al. | Jun 2007 | A1 |
20070168459 | Fujita et al. | Jul 2007 | A1 |
20070192490 | Minhas | Aug 2007 | A1 |
20070198913 | Terao et al. | Aug 2007 | A1 |
20070208782 | Carter et al. | Sep 2007 | A1 |
20070233794 | Singh | Oct 2007 | A1 |
20070271344 | Danasekaran et al. | Nov 2007 | A1 |
20070271502 | Bedi et al. | Nov 2007 | A1 |
20070283267 | Jeffrey et al. | Dec 2007 | A1 |
20080005139 | Hysom et al. | Jan 2008 | A1 |
20080028017 | Garbow et al. | Jan 2008 | A1 |
20080059539 | Chin et al. | Mar 2008 | A1 |
20080120382 | Heidloff et al. | May 2008 | A1 |
20080250474 | Bhogal et al. | Oct 2008 | A1 |
20080281924 | Gadwale | Nov 2008 | A1 |
20080282159 | Vanderwende et al. | Nov 2008 | A1 |
20080288862 | Smetters et al. | Nov 2008 | A1 |
20090006948 | Parker et al. | Jan 2009 | A1 |
20090024931 | Bae | Jan 2009 | A1 |
20090030919 | Brezina et al. | Jan 2009 | A1 |
20090030997 | Malik | Jan 2009 | A1 |
20090063520 | Kimura | Mar 2009 | A1 |
20090094514 | Dargahl et al. | Apr 2009 | A1 |
20090100109 | Turski et al. | Apr 2009 | A1 |
20090157831 | Tian et al. | Jun 2009 | A1 |
20090187852 | Tsurata | Jul 2009 | A1 |
20090210721 | Phillips | Aug 2009 | A1 |
20090248808 | Izumi | Oct 2009 | A1 |
20090313256 | Konduri et al. | Dec 2009 | A1 |
20090319618 | Affronti et al. | Dec 2009 | A1 |
20100011032 | Fukuoka | Jan 2010 | A1 |
20100017701 | Bargeron et al. | Jan 2010 | A1 |
20100023492 | Lucas | Jan 2010 | A1 |
20100057765 | Dispensa et al. | Mar 2010 | A1 |
20100057864 | Laird-McConnell | Mar 2010 | A1 |
20100070448 | Omoigui | Mar 2010 | A1 |
20100070588 | Sinn et al. | Mar 2010 | A1 |
20100082713 | Fird-Nielsen | Apr 2010 | A1 |
20100095198 | Bultrowicz et al. | Apr 2010 | A1 |
20100125640 | Boddington et al. | May 2010 | A1 |
20100169295 | Kanamori | Jul 2010 | A1 |
20100169439 | O'Sullivan et al. | Jul 2010 | A1 |
20100169440 | O'Sullivan | Jul 2010 | A1 |
20100191774 | Mason et al. | Jul 2010 | A1 |
20100198927 | Tonnison et al. | Aug 2010 | A1 |
20100228611 | Shenfield | Sep 2010 | A1 |
20100228989 | Neystadt | Sep 2010 | A1 |
20100235763 | Massand | Sep 2010 | A1 |
20100281224 | Ho et al. | Nov 2010 | A1 |
20100306180 | Johnson et al. | Dec 2010 | A1 |
20100306330 | Friedman | Dec 2010 | A1 |
20110066955 | Olson et al. | Mar 2011 | A1 |
20110113104 | Bhogal et al. | May 2011 | A1 |
20110145363 | Ananthanarayanan | Jun 2011 | A1 |
20110276897 | Crevier et al. | Nov 2011 | A1 |
20120095890 | Santarlas | Apr 2012 | A1 |
20120151379 | Schultz et al. | Jun 2012 | A1 |
20120192064 | Antebi et al. | Jul 2012 | A1 |
20120278281 | Meisels et al. | Nov 2012 | A1 |
20120278401 | Meisels et al. | Nov 2012 | A1 |
20120278402 | Limont et al. | Nov 2012 | A1 |
20120278403 | Costenaro et al. | Nov 2012 | A1 |
20120278404 | Meisels et al. | Nov 2012 | A1 |
20120278407 | Meisels et al. | Nov 2012 | A1 |
20120284344 | Costenaro et al. | Nov 2012 | A1 |
20120284345 | Costenaro et al. | Nov 2012 | A1 |
20140173423 | Meisels et al. | Jun 2014 | A1 |
Number | Date | Country |
---|---|---|
2008-500646 | Jan 2008 | JP |
2007133504 | Nov 2007 | WO |
WO 2007133504 | Nov 2007 | WO |
2009023769 | Feb 2009 | WO |
Entry |
---|
Edholm, Y.; “Email Attachments: The Scourge of the Network”; Jul. 21, 2008; solutions-daily.com; http://www.solutions-daily.com/dsp—getFeaturesDetails.cfm/CID=691; 3 pgs. |
Docstoc; “OneClick: Email Large Documents Without Attaching Files”; retrieved Jan. 7, 2011, from http://www.docstoc.com/oneclick/; 4 pgs. |
Masternewmedia.com; “How to Send Large Files without Email”; Last updated: Jan. 6, 2011; retrieved Jan. 7, 2011, from http://www.masternewmedia.org/how—to—send—large—files—without—email/; 3 pgs. |
MSDN.com; “How to Share Large Files Without Attaching Them”; Aug. 21, 2008; retrieved Jan. 7, 2011, from http://blogs.mdsn.com/b/outlook/archive/2008/08/21/how-to-share-large-files-without-attaching-them.aspx; 3 pgs. |
Sendthisfile.com; “Welcome to SendThisFile”; accessed Jan. 7, 2011, from http://www.sendthisfile.com/; 1 pg. |
Office Action dated Feb. 11, 2013, issued in U.S. Appl. No. 13/096,899. |
U.S. Appl. No. 13/102,431, entitled Changes to Documents are Automatically Summarized in Electronic Messages, filed May 6, 2011. |
U.S. Appl. No. 13/102,875, entitled Setting Permissions for Links Forwarded in Electronic Messages, filed May 6, 2011. |
Decouchant et al.; “Griffon: A Cooperative, Structured, Distributed Document Editor”; 1993; http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.51.759&rep=rep1&type=pdf; 28 pages. |
Devendorf, G.; “Outlook putting attachments in Sharepoint”; Feb. 13, 2008; http://my.advisor.com/blog/garydev.nsf/d6plinks/GDEF-7BSUA2; 5 pages. |
Egnyte.co; “Cloud File Server Features—Complete List”; accessed Dec. 30, 2010, at http://www.egnyte.co.uk/file-server/online-file-server-features.html; 5 pgs. |
Gigaom.com; “How to Use Adobe Acrobat for Online Document Reviews”; Retrieved Date: Jan. 4, 2010; http://gigaom.com/collaboration/how-to-use-adobe-acrobat-for-online-document-reviews/; 8 pgs. |
Harmoni.ie; “harmon.ie for SharePoint”; accessed Apr. 1, 2011 at http://harmon.ie/SharePoint/Product/Features/CollaborateUsingDocuments; 3 pgs. |
Hsieh, H., et al.; “Activity Links: Supporting Communication and Reflection about Action”; Center for the Study of Digital Libraries and Dept. of Computer Science, Texas A&M University, USA; HT '05 Sep. 6-9, 2005, Salzburg, AT; 10 pgs. |
Jatowt, A., et al.; “Change Summarization in Web Collections”; University of Tokyo, Japan; 2004; accessed on or about Jan. 4, 2010 at http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.73.7999&rep=rep1&type-pdf; 10 pgs. |
Lenahan, T.; “5 New Google Docs Features You Might Have Missed”; Apr. 6, 2010; http://www.makeuseof.com/tag/5-google-docs-features-making/; 9 pgs. |
Masternewmedia.org; “Collaborative Document Review Online: PleaseReview”; Retrieved Date: Jan. 4, 2010; http://www.masternewmedia.org/news/2005/06/02/collaborative—document—review—online—pleasereview.htm; 4 pgs. |
McCoy, J., et al.; “SharePoint Workspace and the Office Document Cache”; Mar. 12, 2010-Sep. 29, 2010; retrieved Dec. 30, 2010, at http://blogs.msdn.com/b/sharepoint—workspace—development—team/archive/2010/03/12/sharepoint-workspace-and-the-office-document-cache.aspx; 2 pgs. |
Microsoft Support; “Attachment Manager for Outlook”; accessed Jan. 7, 2011, at http://assistmyteam.com/downloads/manuals/AttachmentManager.pdf; 14 pgs. |
Microsoft Support; “OL2000: Changing from Local Delivery to Server and Offline”; Oct. 8, 2003, rev. 1.0; accessed Jan. 7, 2011 at http://support.microsoft.com/kb/197651; 4 pgs. |
Microsoft Support; “You may receive an ‘Outlook blocked access to the following potentially unsafe attachments’ message in Outlook”; Last Review: May 13, 2010; http://support.microsoft.com/kb/829982; 7 pgs. |
Microsoft; “Going beyond e-mail: Collaborating with Office”; Retrieved Date: Jan. 4, 2010; http://office.microsoft.com/en-us/outlook-help/going-beyond-e-mail-collaborating-with-office-HA001017429.aspx; 10 pgs. |
Office-Addins.com; “Attachments Processor for Microsoft Outlook”; accessed Jan. 6, 2011, at http://www.-office-addins.com/-outlook-addins/attachments-processor.html; 3 pgs. |
phpBB—Free and Open Source Forum Software; “Display last edited time information”; accessed Jan. 6, 2011, at http://www.phpbb.com/community/viewtopic.php?f=46&t=589514; 7 pgs. |
Redline-Software.com; “Outlook Connector for MDaemon”; accessed Jan. 6, 2011, at http://www.redlinesoftware.com/eng/support/docs/mdaemon/c6s4.php; 7 pgs. |
RSBR.de; “Outlook Attachment Sniffer”; accessed Jan. 6, 2011, at http://www.rsbr.de/Software/OASniffer/index.htm; 2 pgs. |
Sharepoint Development; “How to show last modified workflow date in a column on the main list page”; Jul. 31, 2009-Aug. 4, 2009; accessed Jan. 6, 2011, at http://www.sharepointdev.net/sharepoint--design-customization/how-to-show-last-modified-workflow-date--in-a-column-on-the-main-list-page-5094.shtml; 4 pgs. |
Thapa, S.; “Microsoft SharePoint 2010—Features and Benefits”; Dec. 1, 2010; EzineMark.com; 3 pgs. |
The Daily Reviewer; “Outlook Shared Attachment as Hyperlink”; accessed Dec. 30, 2010, at http://thedailyreviewer.com/windowsapps/view/outlook-shared-attachment-as-hyperlink-11367085; 5 pgs. |
PCT Search Report in PCT/US2012/035710 dated Sep. 28, 2012. |
Office Action dated Jun. 20, 2012, issued in U.S. Appl. No. 13/096,899. |
Office Action dated Sep. 7, 2012, issued in U.S. Appl. No. 12/963,0919. |
Office Action dated Oct. 3, 2012, issued in U.S. Appl. No. 12/096,830. |
Office Action dated Nov. 21, 2012, issued in U.S. Appl. No. 13/096,936. |
Office Action dated Nov. 26, 2012, issued in U.S. Appl. No. 13/102,431. |
PCT Search Report in PCT/US2012/035707 dated Nov. 26, 2012. |
PCT Search Report in PCT/US2012/035708 dated Nov. 26, 2012. |
PCT Search Report in PCT/US2012/035709 dated Nov. 26, 2012. |
PCT Search Report in PCT/US2012/036701 dated Nov. 28, 2012. |
PCT Search Report in PCT/US2012/036702 dated Dec. 3, 2012. |
Office Action dated Dec. 11, 2012, issued in U.S. Appl. No. 13/096,854. |
Office Action dated Dec. 14, 2012, issued in U.S. Appl. No. 13/096,869. |
Office Action dated Dec. 26, 2012, issued in U.S. Appl. No. 13/096,880. |
Office Action dated Jan. 2, 2013, issued in U.S. Appl. No. 13/102,875. |
Office Action dated Jan. 9, 2013, issued in U.S. Appl. No. 12/963,091. |
Office Action dated Nov. 22, 2013, issued in U.S. Appl. No. 13/102,875. |
Office Action dated Jan. 15, 2014, issued in U.S. Appl. No. 13/096,854. |
EP Extended Search Report in PCT/US2012/036702 dated Aug. 12, 2014, 6 pgs. |
Office Action dated Jul. 10, 2014, issued in U.S. Appl. No. 13/096,869, 29 pgs. |
Office Action dated Jul. 16, 2014, issued in U.S. Appl. No. 13/102,431, 20 pgs. |
Office Action dated Aug. 14, 2014, issued in U.S. Appl. No. 13/096,854, 32 pgs. |
Wikipedia, Message, http://en.wikipedia.org/wikilMessage retrieved Jan. 9, 2014, p. 1-2. |
Office Action dated Jun. 16, 2014, issued in U.S. Appl. No. 12/963,091, 22 pgs. |
U.S. Appl. No. 14/188,666 entitled Making Document Changes by Replying to Electronic Messages, filed Feb. 24, 2014. |
Office Action dated Jan. 31, 2014, issued in U.S. Appl. No. 13/096,869, 28 pgs. |
Office Action dated Apr. 8, 2014, issued in U.S. Appl. No. 13/102,431, 16 pgs. |
Office Action dated Jun. 4, 2013, issued in U.S. Appl. No. 13/096,936. |
Office Action dated Jun. 10, 2013, issued in U.S. Appl. No. 13/102,431. |
Office Action dated Jun. 20, 2013, issued in U.S. Appl. No. 13/096,854. |
Office Action dated Jun. 21, 2013, issued in U.S. Appl. No. 13/096,830. |
Office Action dated Jun. 21, 2013, issued in U.S. Appl. No. 13/096,869. |
Office Action dated Jul. 16, 2013, issued in U.S. Appl. No. 13/096,880. |
Office Action dated Sep. 24, 2013, issued in U.S. Appl. No. 13/096,899. |
Notice of Allowance dated Oct. 14, 2014 issued in U.S. Appl. No. 13/102,431, 51 pgs. |
Troost et al., Internet Engineering Task Force, RFC 2183 dated Aug. 1997, 12 pgs. available at: www.rfc-editor.org/rfc/rfc2183.txt. |
EP Extended Search Report in PCT/US2012/035708 dated Aug. 29, 2014, 6 pgs. |
EP Extended Search Report in PCT/US2012/035709 dated Sep. 22, 2014, 6 pgs. |
EP Extended Search Report in PCT/US2012/035707 dated Oct. 21, 2014, 6 pgs. |
EP Search Report in PCT/US2012/036701 dated Dec. 4, 2014, 5 pgs. |
Office Action dated Sep. 25, 2014, issued in U.S. Appl. No. 12/963,091, 24 pgs. |
Office Action dated Sep. 26, 2014, issued in U.S. Appl. No. 13/096,936, 29 pgs. |
Office Action dated Oct. 6, 2014, issued in U.S. Appl. No. 13/096,880, 31 pgs. |
Office Action dated Oct. 23, 2014, issued in U.S. Appl. No. 13/096,899, 24 pgs. |
Office Action dated Apr. 9, 2015, issued in U.S. Appl. No. 13/096,936, 23 pgs. |
Office Action dated Apr. 20, 2015, issued in U.S. Appl. No. 13/096,880, 25 pgs. |
Notice of Allowance dated Jun. 15, 2015, issued in U.S. Appl. No. 12/963,091, 28 pgs. |
Office Action dated Jun. 23, 2015, issued in U.S. Appl. No. 13/096,899, 30 pgs. |
Office Action dated Jun. 26, 2015, issued in U.S. Appl. No. 13/096,854, 50 pgs. |
Number | Date | Country | |
---|---|---|---|
20120278405 A1 | Nov 2012 | US |