CN101764766B - Method and terminal for email attachment information prompt - Google Patents
Method and terminal for email attachment information prompt Download PDFInfo
- Publication number
- CN101764766B CN101764766B CN2010101165802A CN201010116580A CN101764766B CN 101764766 B CN101764766 B CN 101764766B CN 2010101165802 A CN2010101165802 A CN 2010101165802A CN 201010116580 A CN201010116580 A CN 201010116580A CN 101764766 B CN101764766 B CN 101764766B
- Authority
- CN
- China
- Prior art keywords
- attachment
- size
- user
- sending
- 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
Links
- 238000000034 method Methods 0.000 title claims abstract description 47
- 230000005540 biological transmission Effects 0.000 claims description 13
- KDXKERNSBIXSRK-YFKPBYRVSA-N L-lysine Chemical compound NCCCC[C@H](N)C(O)=O KDXKERNSBIXSRK-YFKPBYRVSA-N 0.000 description 7
- 238000010586 diagram Methods 0.000 description 7
- 244000089409 Erythrina poeppigiana Species 0.000 description 5
- 235000009776 Rathbunia alamosensis Nutrition 0.000 description 5
- 101100083446 Danio rerio plekhh1 gene Proteins 0.000 description 4
- 101100129500 Caenorhabditis elegans max-2 gene Proteins 0.000 description 3
- 101001094649 Homo sapiens Popeye domain-containing protein 3 Proteins 0.000 description 3
- 101000608234 Homo sapiens Pyrin domain-containing protein 5 Proteins 0.000 description 3
- 101000578693 Homo sapiens Target of rapamycin complex subunit LST8 Proteins 0.000 description 3
- 102100027802 Target of rapamycin complex subunit LST8 Human genes 0.000 description 3
- 201000004569 Blindness Diseases 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000006870 function Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 230000002452 interceptive effect Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
Images
Landscapes
- Information Transfer Between Computers (AREA)
Abstract
The invention discloses a method and a terminal for email attachment prompt. The method comprises that: a size threshold value of attachments to be prompted is obtained and saved through a sending server; when a user creates an email, the size of the attachment added by the user is obtained; and before the created email is sent, when the size of the attachment added by the user exceeds the threshold value, a prompt indicating that the email cannot be sent is given to the user. The invention has the advantages that the probability of email sending failure is reduced, the email sending efficiency is improved and the usability of the email client terminal is further improved.
Description
Technical Field
The invention relates to the technical field of e-mails, in particular to an e-mail attachment information prompting method and a terminal.
Background
There are many e-mails that people use daily, but there are usually only two ways to implement the e-mails, the first is to use e-mails on websites, that is, what is called web using way, usually people must first log in to Webmail server (web mail server) and check to send and receive e-mails after authentication. However, the user cannot always be in a login state, and cannot send or receive mails every moment, if the Webmail server is not operated for a long time, the user is considered to be logged in overtime, and automatically logs out of the system, and the user needs to log in the mail server again to perform the operation.
The account and the password are logged in and filled out frequently, so that the use of the e-mail by a user is inconvenient, and another e-mail implementation mode, namely e-mail client software, is provided. Moreover, when the client software is used for sending and receiving the mails, the website page content does not need to be downloaded, so that the speed is higher; the mails received by the client software and sent once are stored in the local computer of the client software, and the old mails can be read and managed without surfing the Internet. It has become an essential tool for people to communicate in work and life, due to the advantages of the e-mail client.
In both the web-based method and the e-mail client method, the content that can be sent by the e-mail generally includes text content and attachments (including video, audio, pictures, document files, etc.), wherein the sending server limits the size of the attachments that can be sent according to the user information and the conditions of the sending server. For example, some servers limit attachment sizes to 30M, and when attachments are added beyond 30M, the mail will not be sent successfully.
In the prior art, when an email client is used for sending an email, if the size of an attachment exceeds the limit of a sending server, a user can find that the sending is failed only after the sending is tried, and then the email is edited and sent again, but the complicated process obviously reduces the usability of the email client.
Disclosure of Invention
The invention provides an email attachment information prompting method and a terminal, which can improve the usability of an email client.
The invention provides the following scheme:
an email attachment information prompting method comprises the following steps:
acquiring and storing an attachment size threshold value needing to be prompted through a sending server;
when a user creates a mail, acquiring the size of an attachment added by the user;
and before the created mail is not sent, when the size of the attachment added by the user exceeds the threshold value, prompting the user that the mail cannot be sent.
An email attachment information prompting terminal, comprising:
the threshold value acquisition unit is used for acquiring and storing the accessory size threshold value needing prompting through the sending server;
an attachment size learning unit used for learning the size of the attachment added by the user when the user creates the mail;
and the first information prompting unit is used for prompting the user that the mail cannot be sent when the size of the attachment added by the user exceeds the threshold value before the created mail is not sent.
According to the specific embodiment provided by the invention, the invention discloses the following technical effects:
the invention can judge the size of the added attachment before the mail is sent, and if the attachment is too large, the user can be prompted that the mail can not be successfully sent. Therefore, the user can obtain the information that the mail cannot be successfully sent in time, search the reason in time, modify the current mail and ensure the successful sending of the mail, and does not need to obtain the information after clicking to send, so that the probability of mail sending failure can be reduced, the efficiency of mail sending is improved, and the usability of the electronic mail client is further improved.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings needed to be used in the embodiments will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings without inventive exercise.
FIG. 1 is a schematic diagram of a process for sending mail using an email client program;
FIG. 2 is a flow chart of a method provided by an embodiment of the present invention;
FIG. 3 is a schematic diagram of an extension to a protocol in an embodiment of the invention;
FIG. 4 is a schematic diagram of another pair of protocol extensions in an embodiment of the present invention;
fig. 5 is a schematic diagram of a first terminal according to an embodiment of the present invention;
fig. 6 is a schematic diagram of a second terminal provided in an embodiment of the present invention;
fig. 7 is a schematic diagram of a third terminal provided in an embodiment of the present invention;
fig. 8 is a schematic diagram of a fourth terminal according to an embodiment of the present invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
It should be noted that the method for prompting email attachment information provided in the embodiment of the present invention is mainly applied to the case where a terminal using an email client sends an email, where the terminal mentioned in the embodiment of the present invention includes, but is not limited to, various mobile terminals such as a mobile phone, a personal digital assistant PDA, a smart phone or a handheld portable computer, which have the function of sending and receiving an email, and the terminal may further include a fixed terminal such as a fixed station or a computer.
For ease of understanding, the working principle of the email client is first briefly described below:
assuming that the two mailbox accounts are lisina.com and wangwushu.com, the process of sending and receiving mails between the two mailboxes is shown in fig. 1, wherein a solid arrow represents a process of sending a mail from the lisina.com account to the wangwushu.com account, and a dotted arrow represents a process of sending a mail from the wangwushu.com account to the lisina.com account. Com accounts, the links involved in sending a piece of mail to receiving a piece of mail are specifically explained below by analyzing the process of sending mail from lisina.
Com, the user edits the mail in the interface and clicks the send button, and then the Outlook establishes network connection with the SMTP server of sina, and logs in with lisi's user name and password, and sends the mail to the SMTP server of sina using the SMTP protocol.
Secondly, after receiving the e-mail submitted by lisina.com, the SMTP server of sina judges whether the mail address of the receiver belongs to the administration range of the SMTP server according to the address suffix of the receiver, if so, the mail is directly stored in the mailbox of the receiver, otherwise, the SMTP server of sina inquires the domain name MX record represented by the mail address suffix (sohu.com) of the receiver from the DNS server so as to obtain the SMTP server information of the sohu, and then establishes connection with the SMTP server of the sohu and sends the mail to the SMTP server of the sohu by adopting an SMTP protocol.
After receiving the e-mail sent by sina's SMTP server, the sohu SMTP server also determines whether the e-mail belongs to the jurisdiction of the SMTP server according to the address of the recipient, and if so, directly stores the e-mail in the mailbox of the recipient, otherwise (this will not happen generally), the sohu SMTP server may continue to forward the e-mail, or may discard the e-mail.
And fourthly, a user with the wangwushu.com account establishes network connection with a POP3/IMAP server of the sohu through a mail client program (here, Outlook Express is also assumed), and after logging in with the username and the password of wangwu, whether a new mail exists in the wangwushu.com mailbox can be checked through a POP3 or an IMAP protocol, and if the mail exists in the mailbox, the mail in the mailbox can be read through the POP3 or the IMAP protocol.
The process of sending a mail to the lisina.com account by the wangwushu.com account, which is partially indicated by a dotted line, is similar to the process of sending a mail to the wangwushu.com account by the lisina.com account, and is not described herein again.
It can be seen from the foregoing process of sending email that, when using an email client to send and receive email, the email server is only used to perform background operations, and the foreground user interface is provided by the email client software, that is, what contents are specifically displayed on the user interface is determined by the email client software. This is different from sending and receiving mail directly on a web page, and when sending and receiving mail directly on a web page, the user interface is provided by the mail server, so that what contents are specifically displayed on the user interface is also determined by the mail server.
Referring to fig. 2, the method for prompting email attachment information provided by the embodiment of the present invention includes the following steps:
s201: acquiring and storing an attachment size threshold value needing to be prompted through a sending server;
it should be noted that, in the method provided in the embodiment of the present invention, the execution subjects of each step are all email clients. Since the limitation of the attachment size may be different for different servers and the limitation of the attachment size may also be different for different users by the same server, an attachment size threshold that needs to be prompted needs to be obtained first.
S202: when a user creates a mail, acquiring the size of an attachment added by the user;
the size of the attachment can be known at the same time when the user selects the attachment, and if the user adds a plurality of attachments in the same mail, the sum of the sizes of the attachments is known. The attachment is usually some video, audio, picture or document files stored in the system, and the system stores the attributes of the files when storing the files, wherein the size of the file is used as one basic attribute of the file and is stored in the system, so that the size of the attachment can be conveniently known by reading the attributes of the file as the attachment.
S203: and before the created mail is not sent, when the size of the attachment added by the user exceeds the threshold value, prompting the user that the mail cannot be sent.
Therefore, if the user adds the attachment in the mail, before the user clicks the sending button, the embodiment of the invention can judge whether the sending is failed probably because the attachment is overlarge, and if so, the user can be prompted that the mail cannot be sent. In this way, since the transmission has not been clicked yet, the user can find the problem in time without waiting until the transmission is clicked.
Of course, if only the mail is prompted to be sent, the user may not know the reason for the failure to send, and only needs to search the reason by himself, which requires the user to spend some time for self-thinking and operation. Therefore, while the embodiment of the present invention prompts that the email cannot be sent, the embodiment of the present invention may also prompt the user that the reason why the email cannot be sent is that the attachment is too large, for example, the following prompts may be given: the attachment is too large, the mail cannot be normally sent, and the like. Thus, after obtaining the information, the user can immediately know what means should be used to avoid the failure of sending the mail, for example, if there are a plurality of attachments, the number of attachments can be reduced, and the attachments can be sent for a plurality of times; if there is only one nearby, the file may also be cut into multiple copies using a software tool and then sent in portions, and so on.
Or the attachment size threshold value can be prompted to the user, so that the user can obtain a more intuitive reference when editing the email again, blindness when adding the attachment is avoided, and usability of the email client is further improved.
As described above, in order to determine whether an attachment is oversized before a user clicks a send email and perform a corresponding prompt when the attachment is oversized, a size threshold of the attachment for performing the prompt needs to be known in advance.
Detailed description of the invention
In the first embodiment, the maximum value of the attachment size that can be supported by the delivery server may be used as the attachment size threshold that needs to be presented, and the threshold may be stored. That is, it is necessary to know the maximum value of the attachment size that the delivery server can support, and then to take the maximum value as the attachment size threshold. There may be various implementations of specifically knowing the maximum value of the attachment size that the delivery server can support, which are described below.
In the first mode, because a user uses an email client for the first time and sends an email through an account of the user, the email client needs to perform some information interaction with a sending server according to the SMTP protocol, and therefore, in the first mode, the method can be realized by expanding the SMTP protocol.
For example, when a user sends an email for the first time, information of a sending server corresponding to the account needs to be created, including an IP address and a port of the sending server, and a user name and a password used by the user. After creating the information of the sending server, the e-mail client will actively send an EHLO command to the sending server, and after receiving the EHLO command, the sending server will return some information to the e-mail client, including HELP information returned by the HELP command, etc. According to the feature, the SMTP protocol can be extended, for example, as shown in fig. 3, a "MaxAttSize" command (the name of the command may not be limited thereto) is an extension of the SMTP protocol, and the maximum value of the attachment size that can be supported by the sending server can be sent to the email client through the MaxAttSize command, and the email client records the information and uses the information as the threshold of the attachment size that needs to be prompted. Thus, when a user creates an email by using the account, if the attachment added by the user exceeds the threshold value, the user can be prompted in advance to 'the attachment is too large and cannot be sent', and the like.
In the second mode, since some information also needs to be interacted between the email client and the sending server in the process of sending one email, the sending server can also carry the maximum value of the attachment size which can be supported by the sending server in the interactive information. That is, the maximum attachment size that the sending server can support can be known from the message returned by the sending server in the process of sending the first email.
Obviously, in this way, when sending the first email, if an attachment is also added, it is impossible to give a prompt to the user whether the attachment is oversized, but when sending the first email and then needing to send the email using the account, it is possible to give a relevant prompt to the user by using the acquired attachment size threshold that needs to be prompted.
Detailed description of the invention
In this second embodiment, an estimated value can be used as the attachment size threshold that needs to be prompted, instead of the maximum attachment size that can be supported by the sending server.
For example, the following method can be specifically adopted: when a user sends a mail, if the mail carries an attachment, the electronic mail client can record the size of the attachment; if the sending fails because the attachment is too large, the sending server informs the email client that the sending fails because the attachment is too large. Of course, there is no corresponding command in the existing SMTP protocol, and the implementation may be realized by extending the protocol, for example, an Error Code representing that the sending of the attachment is too large may be defined, and the sending server may notify the e-mail client that a certain mail fails to be sent because the attachment is too large by sending the Error Code, for example, "Error Code (att to large)" as shown in fig. 4 is an extension to the mail protocol. After learning the message, the email client can record the size max1 of the attachment carried by the email, and use the size max1 as the attachment size threshold that needs to be prompted, and when the email is sent later, the attachment cannot exceed the size max 1.
Of course, the size of this max1 may not be the maximum value for the exact sender-server-limited attachment size, and therefore, may be optimized later in the mail delivery process. That is, when the size of the attachment added by the user does not exceed the threshold, if the mail transmission fails and the reason for the failure is that the attachment is too large, the attachment size threshold that needs to be presented is updated to the size of the attachment. For example, if the size of an attachment added to a mail sent again by the user is max2, this max2 is smaller than max1, and therefore, the user is not prompted; however, when the mail is sent, it is found that the size of the attachment still exceeds the server limit, and at this time, the attachment size threshold value to be presented may be updated to max 2. The updating is performed in sequence, and the obtained threshold value is optimized every time the updating is performed, so that the maximum value of the attachment size limited by the attachment server is approached finally.
The method for updating the obtained prompt threshold may be applied to other methods for obtaining the prompt threshold. For example, in the method of the first embodiment, although the maximum value of the attachment sizes that can be supported by the sending server is sent to the mail client, theoretically, the attachment size that can be added by the user can be successfully sent as long as the attachment size does not exceed the maximum value, in practical applications, the attachment size that can be actually added may be slightly lower than the theoretical maximum value. For example, when the size of the attachment added by the user is 19.8M, the mail client does not prompt the user for the information that the attachment is too large according to the method of the first embodiment, where the limitation of the attachment size by a certain sending server is 20M; however, during a particular sending process, the 19.8M attachment may still be too large to send properly. At this time, a method similar to that in the second embodiment may be adopted, that is, when the size of the attachment added by the user does not exceed the pre-acquisition and storage threshold, if the mail transmission fails and the reason for the failure in the mail transmission is that the attachment is too large, the attachment size threshold that needs to be prompted is updated to the size of the attachment. That is, in the above example, the mail client updates the attachment size threshold value that needs to be presented to 19.8M, so that when the user sends a mail later, if the size of the attached file exceeds 19.8M, the user is prompted that the attached file cannot be normally sent.
Corresponding to the method for prompting the information of the email attachment provided by the embodiment of the present invention, the embodiment of the present invention also provides a terminal for prompting the information of the email attachment, and referring to fig. 5, the terminal includes:
a threshold obtaining unit 501, configured to obtain and store, by a sending server, an attachment size threshold that needs to be prompted;
an attachment size learning unit 502, configured to learn the size of an attachment added by a user when the user creates a mail;
a first information prompting unit 503, configured to prompt the user that the email cannot be sent when the size of the attachment added by the user exceeds the threshold before the created email is not sent.
Therefore, if the user adds the attachment in the mail, before the user clicks the sending button, the embodiment of the invention can judge whether the sending is failed probably because the attachment is overlarge, and if so, the user can be prompted that the mail cannot be sent. In this way, since the transmission has not been clicked yet, the user can find the problem in time without waiting until the transmission is clicked.
In order to make the user obtain more information and further improve the usability of the e-mail client, referring to fig. 6, the terminal further includes:
the second information prompting unit 504 is configured to prompt the user that the reason why the mail cannot be sent is that the attachment is too large.
Alternatively, the terminal may further include:
a third information prompting unit 505, configured to prompt the user for the attachment size threshold.
In some embodiments, the threshold obtaining unit 501 may obtain the accessory size threshold that needs to be prompted, where in one embodiment, the maximum value of the accessory size that can be supported by the sending server may be used as the accessory size threshold that needs to be prompted, and accordingly, referring to fig. 7, the threshold obtaining unit 501 may include:
a maximum value learning subunit 5011, configured to learn a maximum value of sizes of attachments that can be supported by the delivery server;
a first threshold determining subunit 5012, configured to determine the maximum value as the accessory size threshold that needs to be prompted.
The maximum value learning subunit 5011 may include:
the first learning subunit is used for receiving a message sent by a sending server after an account is created when a user needs to send an email for the first time, and learning the maximum value of the attachment size which can be supported by the sending server from the message;
or,
and the second learning subunit is used for learning the maximum value of the attachment size which can be supported by the sending server from the message returned by the sending server in the first e-mail sending process.
In another way of acquiring the accessory size threshold that needs to be prompted, an estimated value may be used as the accessory size threshold that needs to be prompted, and in this case, referring to fig. 8, the threshold acquiring unit 501 may include:
an error code receiving subunit 5013 configured to receive an error code returned by the delivery server if the mail delivery fails;
the second threshold determination subunit 5014 is configured to determine, if the reason for the failure of sending the mail is that the attachment is too large, the size of the attachment carried by the mail as the attachment size threshold that needs to be prompted.
In the subsequent process of sending the email, the obtained prompt threshold value may be optimized, and correspondingly, the terminal may further include:
a threshold updating unit 506, configured to update the size threshold of the attachment that needs to be prompted to the size of the attachment if the mail transmission fails and the reason for the failure in the mail transmission is that the attachment is too large when the size of the attachment added by the user does not exceed the threshold.
It will be understood by those skilled in the art that all or part of the steps in the method for implementing the above embodiments may be implemented by hardware related to instructions of a program, where the program may be stored in a computer readable storage medium, and when executed, the program includes the following steps: acquiring and storing an attachment size threshold value needing to be prompted through a sending server; when a user creates a mail, acquiring the size of an attachment added by the user; and before the created mail is not sent, when the size of the attachment added by the user exceeds the threshold value, prompting the user that the mail cannot be sent. The storage medium, such as: ROM/RAM, magnetic disk, optical disk, etc.
The method and the terminal for prompting the email attachment information provided by the invention are described in detail, a specific example is applied in the text to explain the principle and the implementation mode of the invention, and the description of the embodiment is only used for helping to understand the method and the core idea of the invention; meanwhile, for a person skilled in the art, according to the idea of the present invention, the specific embodiments and the application range may be changed. In view of the above, the present disclosure should not be construed as limiting the invention.
Claims (8)
1. An email attachment information prompting method is characterized by comprising the following steps:
the method includes the following steps that an attachment size threshold needing to be prompted is obtained and stored through a sending server, and specifically includes: acquiring the maximum value of the accessory size which can be supported by a sending server, determining the maximum value as the accessory size threshold value needing prompting, and storing the threshold value; or, if the mail fails to be sent, receiving an error code returned by the sending server, and if the reason for the failure of sending the mail is that the attachment is too large, determining the size of the attachment carried by the mail as an attachment size threshold value needing to be prompted;
when a user creates a mail, acquiring the size of an attachment added by the user;
and before the created mail is not sent, when the size of the attachment added by the user exceeds the threshold value, prompting the user that the mail cannot be sent.
2. The method of claim 1, further comprising:
prompting the user that the reason why the mail cannot be sent is that the attachment is too large; or,
prompting a user for the attachment size threshold.
3. The method of claim 1, wherein learning the maximum number of attachment sizes that can be supported by the sender server comprises:
when a user needs to send an email for the first time, after an account is created, receiving a message sent by a sending server, and acquiring the maximum value of the attachment size which can be supported by the sending server from the message;
or,
in the first e-mail sending process, the maximum value of the attachment size which can be supported by the sending server is obtained from the message returned by the sending server.
4. The method according to claim 1 or 2, characterized in that the method further comprises:
and when the size of the attachment added by the user does not exceed the threshold, if the mail transmission fails and the reason of the failure of the mail transmission is that the attachment is too large, updating the attachment size threshold needing to be prompted to the size of the attachment.
5. An email attachment information prompting terminal, characterized by comprising:
the threshold value acquisition unit is used for acquiring and storing the accessory size threshold value needing prompting through the sending server;
an attachment size learning unit used for learning the size of the attachment added by the user when the user creates the mail;
the first information prompting unit is used for prompting the user that the mail cannot be sent when the size of the attachment added by the user exceeds the threshold value before the created mail is not sent;
the threshold value obtaining unit at least comprises any one of the following units:
a maximum value acquiring subunit, configured to acquire a maximum value of the size of the attachment that can be supported by the delivery server;
a first threshold determining subunit, configured to determine the maximum value as the accessory size threshold that needs to be prompted; or,
the error code receiving subunit is used for receiving the error code returned by the sending server if the mail fails to be sent;
and the second threshold determining subunit is configured to determine, if the reason that the sending of the email fails is that the attachment is too large, the size of the attachment carried by the email as the attachment size threshold that needs to be prompted.
6. The terminal according to claim 5, further comprising at least one of the following:
the second information prompting unit is used for prompting the reason that the mail cannot be sent to the user that the attachment is too large;
and the third information prompting unit is used for prompting the attachment size threshold value to a user.
7. The terminal of claim 5, wherein the maximum learning subunit comprises:
the first learning subunit is used for receiving a message sent by a sending server after an account is created when a user needs to send an email for the first time, and learning the maximum value of the attachment size which can be supported by the sending server from the message;
or,
and the second learning subunit is used for learning the maximum value of the attachment size which can be supported by the sending server from the message returned by the sending server in the first e-mail sending process.
8. The terminal according to claim 5 or 6, further comprising:
and the threshold updating unit is used for updating the attachment size threshold value needing to be prompted to the attachment size if the mail transmission fails and the reason of the mail transmission failure is that the attachment is too large when the attachment size added by the user does not exceed the threshold.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2010101165802A CN101764766B (en) | 2010-03-01 | 2010-03-01 | Method and terminal for email attachment information prompt |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN2010101165802A CN101764766B (en) | 2010-03-01 | 2010-03-01 | Method and terminal for email attachment information prompt |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN101764766A CN101764766A (en) | 2010-06-30 |
| CN101764766B true CN101764766B (en) | 2012-01-25 |
Family
ID=42495758
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN2010101165802A Active CN101764766B (en) | 2010-03-01 | 2010-03-01 | Method and terminal for email attachment information prompt |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN101764766B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9887943B2 (en) | 2014-06-01 | 2018-02-06 | Apple Inc. | Dual server system for sending a large email attachment |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8903929B2 (en) * | 2012-07-05 | 2014-12-02 | Microsoft Corporation | Forgotten attachment detection |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP3854618B2 (en) * | 2004-11-10 | 2006-12-06 | 株式会社エヌ・ティ・ティ・ドコモ | Server system and e-mail delivery method |
| CN1983310B (en) * | 2005-12-14 | 2013-07-17 | 腾讯科技（深圳）有限公司 | Method and system for prompting e-mail |
| CA2554991A1 (en) * | 2006-07-28 | 2008-01-28 | Ibm Canada Limited - Ibm Canada Limitee | System and method for distributing email attachments |
| JP2009033262A (en) * | 2007-07-24 | 2009-02-12 | Seiko Epson Corp | Image communication processing unit and divided mail transmission method |
| CN101588382A (en) * | 2008-05-19 | 2009-11-25 | 北京亿企通信息技术有限公司 | Method for submitting attachment in Web pages |
-
2010
- 2010-03-01 CN CN2010101165802A patent/CN101764766B/en active Active
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9887943B2 (en) | 2014-06-01 | 2018-02-06 | Apple Inc. | Dual server system for sending a large email attachment |
Also Published As
| Publication number | Publication date |
|---|---|
| CN101764766A (en) | 2010-06-30 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| JP4890717B2 (en) | Method and system for sending messages across cellular and public data networks | |
| US8078681B2 (en) | System and method for provisioning an email account using mail exchange records | |
| US20090204681A1 (en) | Method, server and client for processing emails | |
| CN102307159B (en) | Method and apparatus for efficient management and resending of transmitted message | |
| US8117267B2 (en) | System and method for provisioning an email account using mail exchange and address records | |
| US7984100B1 (en) | Email system automatically notifying sender status and routing information during delivery | |
| US20120072507A1 (en) | System and method of posting messages to different messaging services | |
| JP2008500665A (en) | Messaging protocol for processing messages with attachments | |
| IL180566A (en) | Electronic messaging system and method | |
| US9014343B1 (en) | Recalling user-generated messages | |
| US20120258742A1 (en) | Techniques for Unified Messaging | |
| JP4521480B1 (en) | Method, system, and computer program for correcting an email message with unsent recipients | |
| US20080256197A1 (en) | Email system including email aggregation server providing security parameter determination features and related methods | |
| KR101650848B1 (en) | Transmitting messages between internationalized email systems and non-internationalized email systems | |
| US9450899B2 (en) | Systems and methods for messaging and presence modification | |
| CN101764766B (en) | Method and terminal for email attachment information prompt | |
| JP2009169866A (en) | Electronic mail client and its control method, and computer program | |
| JP4857246B2 (en) | Approval device, approval method, and program | |
| US8615554B1 (en) | Electronic mail delivery physical delivery backup | |
| US20070078934A1 (en) | System and method for provisioning an email account hosted on an assured email service provider | |
| EP1929726B1 (en) | System and method for provisioning an email account using mail exchange records | |
| US10341274B2 (en) | Systems methods and computer-readable storage media for messaging and presence modification | |
| CN105207884A (en) | Method of acquiring E-mail delivery state and apparatus thereof | |
| US8635292B2 (en) | Method for reduction of disk space usage of electronic messages in a network | |
| CN105634908B (en) | E-mail processing system and method |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| C06 | Publication | ||
| PB01 | Publication | ||
| C10 | Entry into substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| C14 | Grant of patent or utility model | ||
| GR01 | Patent grant | ||
| TR01 | Transfer of patent right | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20171027 Address after: Metro Songshan Lake high tech Industrial Development Zone, Guangdong Province, Dongguan City Road 523808 No. 2 South Factory (1) project B2 -5 production workshop Patentee after: HUAWEI terminal (Dongguan) Co., Ltd. Address before: 518129 Longgang District, Guangdong, Bantian HUAWEI base B District, building 2, building No. Patentee before: Huawei Device Co., Ltd. |
|
| CP01 | Change in the name or title of a patent holder | ||
| CP01 | Change in the name or title of a patent holder |
Address after: 523808 Southern Factory Building (Phase I) Project B2 Production Plant-5, New Town Avenue, Songshan Lake High-tech Industrial Development Zone, Dongguan City, Guangdong Province Patentee after: Huawei Device Co., Ltd. Address before: 523808 Southern Factory Building (Phase I) Project B2 Production Plant-5, New Town Avenue, Songshan Lake High-tech Industrial Development Zone, Dongguan City, Guangdong Province Patentee before: HUAWEI terminal (Dongguan) Co., Ltd. |