Search results
Jump to navigation
Jump to search
Page title matches
- ...] systems on an internal network allowing users within one organization to email each other.17 KB (2,760 words) - 11:50, 2 February 2023
- ...e vulnerabilities according to their locality in Figure 1 of the article [[Email system]], repeated here for convenience. In each category, we summarize th ...r|700px|'''Figure 1 Actors (Users and Agents) and their roles in an ideal email system.'''}}15 KB (2,320 words) - 18:53, 26 December 2010
- 12 bytes (1 word) - 14:13, 26 December 2007
- 5 KB (732 words) - 11:46, 2 February 2023
- 138 bytes (16 words) - 14:30, 13 July 2008
- '''Email abuse''' is the unsolicited sending of [[spam]], third party [[advertisemen ...200508_UltimateGuidetoEmailSecurityUS_822533.pdf Clearswift White Paper on Email Security]</ref>717 bytes (92 words) - 04:28, 1 October 2009
- {{seealso|Email processes and protocols}} ...and should be understood by anyone involved in the design or operation of email systems.11 KB (1,673 words) - 06:07, 29 August 2013
- ...ustrate the use of roles as building blocks in diagrams of various typical email systems.4 KB (524 words) - 04:10, 9 December 2009
- ...ticle is a [[CZ:Related articles|subtopic]] in a group of articles under [[Email system]]. We assume the reader understands the parent article, its termino Solving the problems of bulk [[email abuse]] (spamming, phishing and other bulk mail scams)5 KB (822 words) - 02:42, 3 February 2010
- 846 bytes (129 words) - 05:38, 3 November 2013
- 25 bytes (3 words) - 08:51, 22 April 2024
- 80 bytes (9 words) - 06:06, 1 October 2009
- Brief description of email security problems and solutions.95 bytes (11 words) - 19:08, 23 September 2009
- Description of the features of various programs allowing users to work with email on their own computers, as opposed to [[Webmail]], where everything is done239 bytes (39 words) - 19:55, 23 November 2009
- This article is a subtopic in a group of articles under Email system. We assume the reader understands the parent article, its terminolog514 bytes (66 words) - 21:49, 19 February 2010
- {{r|Email system}} {{r|Email history}}379 bytes (58 words) - 06:45, 23 November 2009
- Roles and responsibilities of organizations handling email.95 bytes (10 words) - 21:07, 27 August 2009
- ...blocked by networks providing Internet access to travelers. The standard email port 25 is frequently blocked due to widespread abuse of these networks. T ...Hutzler, et.al. 2007. Best Current Practices recommended for operators of email submission services.854 bytes (118 words) - 23:50, 30 September 2009
- 559 bytes (48 words) - 17:15, 3 October 2009
- ...nick, ed., http://tools.ietf.org/html/rfc5322. IETF Draft Standard. Basic email message formats, including headers. ...erawy, http://tools.ietf.org/html/rfc5451. IETF Proposed Standard. A new email header field with results of message authentication.2 KB (223 words) - 07:09, 4 November 2009
- The header lines in every email message, defined in RFC-5322.244 bytes (34 words) - 21:06, 30 August 2009
- === BCPs relevant to email security === ...ent, and even controversial. Most of the IETF recommendations relevant to email security are found in a series of documents called Best Current Practices (1 KB (200 words) - 17:37, 9 October 2009
- 102 bytes (13 words) - 14:24, 26 September 2009
- ...ics of [[Email authentication]] and the roles of different agents in the [[Email system]], as illustrated in this diagram:4 KB (610 words) - 17:28, 5 November 2009
- .... Extensions to allow encoding of graphics and other non-ASCII content in email message bodies. ...nick, ed., http://tools.ietf.org/html/rfc5322. IETF Draft Standard. Basic email message formats, including headers.2 KB (245 words) - 21:49, 19 February 2010
- {{slashtitle|Email challenge/response}} '''Challenge/Response (C/R)''' is a method of filtering spam email.1 KB (208 words) - 23:42, 30 September 2009
- 145 bytes (22 words) - 23:47, 30 September 2009
- Brief overview of methods used to authenticate the sender of an email.107 bytes (15 words) - 21:44, 24 November 2008
- 160 bytes (19 words) - 04:30, 1 October 2009
- {{r|Email system}} {{r|Email security}}1 KB (163 words) - 02:30, 3 February 2010
- ...ats and encodings used for text, pictures, and various other objects in an email.126 bytes (18 words) - 13:15, 25 November 2008
- {{r|Email}} {{r|Email system}}573 bytes (87 words) - 14:00, 1 October 2009
- {{r|Email system}}680 bytes (107 words) - 19:11, 23 September 2009
- The header lines in every email message, defined in RFC 532297 bytes (13 words) - 10:52, 8 July 2009
- {{r|Email}} {{r|Email system}}858 bytes (138 words) - 14:06, 1 October 2009
- Email user programs and their features.75 bytes (9 words) - 21:26, 27 August 2009
- 181 bytes (23 words) - 00:04, 3 November 2013
- {{r|Email system}} {{r|Email processes and protocols}}909 bytes (144 words) - 14:38, 1 October 2009
- TCP port reserved for authenticated submission of email messages.101 bytes (12 words) - 11:33, 29 August 2009
- {{seealso|Email processes and protocols}} ...and should be understood by anyone involved in the design or operation of email systems.11 KB (1,671 words) - 06:06, 29 August 2013
- {{r|Email}} {{r|Email processes and protocols}}2 KB (205 words) - 12:38, 5 November 2009
- ...hentication Status", M. Kucherawy. 2009. - IETF Proposed Standard. A new email header field with results of message authentication.399 bytes (51 words) - 10:42, 10 December 2009
- {{r|Email system}} Auto-populated based on [[Special:WhatLinksHere/Email agents]]. Needs checking by a human.448 bytes (59 words) - 16:17, 11 January 2010
- BCP134 - Email Submission Operations: Access and Accountability Requirements [http://iana.org/protocols IANA Protocol Registries] - Registries relevant to email systems776 bytes (100 words) - 20:10, 11 February 2010
- An [[Email authentication|authentication method]] that verifies the purported sender's171 bytes (21 words) - 02:56, 7 December 2009
- The authentication failures that occur in some popular IP-based [[Email authentication]] methods when a forwarder is involved.163 bytes (20 words) - 07:13, 4 November 2009
- ...uce some of the acronyms and jargon needed to understand the literature on email systems. ...them. This is an [[Internet protocol suite|application layer]] view of an email network.17 KB (2,712 words) - 15:14, 26 September 2009
- ...erawy, http://tools.ietf.org/html/rfc5451. IETF Proposed Standard. A new email header field with results of message authentication.884 bytes (118 words) - 07:22, 4 November 2009
- Brief explanation of an email system at the relay level.92 bytes (13 words) - 15:32, 19 September 2009
- {{r|Email system}} {{r|Email authentication}}820 bytes (125 words) - 07:26, 4 November 2009
- 196 bytes (27 words) - 07:36, 4 November 2009
- 792 bytes (105 words) - 12:56, 30 September 2009
- 108 bytes (15 words) - 10:52, 10 December 2009
- {{r|Email system}} {{r|Email authentication}}945 bytes (149 words) - 14:36, 1 October 2009
- {{r|Email}} {{r|Email system}}170 bytes (20 words) - 20:33, 23 November 2009
- {{r|Email system}} {{r|Email authentication}}770 bytes (118 words) - 02:45, 7 December 2009
- {{r|Email system}} {{r|Email processes and protocols}}529 bytes (70 words) - 04:34, 26 January 2021
- Auto-populated based on [[Special:WhatLinksHere/Email message formats]]. Needs checking by a human. {{r|Email system}}439 bytes (57 words) - 16:17, 11 January 2010
- {{r|Email system}} {{r|Email message formats}} (RFC-5322)1 KB (160 words) - 15:15, 26 September 2009
- BCP134 - Email Submission Operations: Access and Accountability Requirements 17 other registries related to email949 bytes (121 words) - 20:10, 11 February 2010
- ...notes and citation-sources (references). Please read this page before you email us an article. ...mat, and also ‘.rtf’ files, which most word processors can generate. Just email your article, as an attachment, to '''[mailto:cz-wikiformat@mail.citizendiu3 KB (543 words) - 03:08, 25 February 2012
- 222 bytes (29 words) - 12:10, 26 February 2008
Page text matches
- == Email Privacy == ...email.com/, and [http://www.sxipper.com/ Sxipper] also offers "disposable" email addresses. ''-- [[User:Tim Chambers|Tim Chambers]] 11:50, 1 October 2008 (C282 bytes (42 words) - 11:50, 1 October 2008
- {{rpl|Email}} {{rpl|Email system}}113 bytes (14 words) - 16:02, 21 January 2023
- ...access to the [[Internet]]. When reading email in the browser, the user's email messages reside on a server rather than being downloaded to the user's desk461 bytes (76 words) - 16:02, 21 January 2023
- '''Email abuse''' is the unsolicited sending of [[spam]], third party [[advertisemen ...200508_UltimateGuidetoEmailSecurityUS_822533.pdf Clearswift White Paper on Email Security]</ref>717 bytes (92 words) - 04:28, 1 October 2009
- {{r|Email system}} {{r|Email security}}216 bytes (30 words) - 18:50, 29 October 2009
- {{r|Email system}} {{r|Email security}}541 bytes (71 words) - 18:46, 29 October 2009
- {{r|Email system}} {{r|Email history}}379 bytes (58 words) - 06:45, 23 November 2009
- {{r|Email system}} {{r|Email processes and protocols}}529 bytes (70 words) - 04:34, 26 January 2021
- {{r|Email system}} {{r|Email greylisting}}337 bytes (41 words) - 09:23, 27 November 2022
- ...blocked by networks providing Internet access to travelers. The standard email port 25 is frequently blocked due to widespread abuse of these networks. T ...Hutzler, et.al. 2007. Best Current Practices recommended for operators of email submission services.854 bytes (118 words) - 23:50, 30 September 2009
- A client-server messaging protocol for [[Email|email]] which requires messages to be downloaded to a client's computer, phone or184 bytes (25 words) - 16:09, 21 January 2023
- {{r|Email system}} {{r|Email security}}193 bytes (22 words) - 18:49, 29 October 2009
- ...ccess Protocol''' (IMAP) is a client-server messaging protocol for [[Email|email]] which allows messages to be stored indefinitely on a server. IMAP is des213 bytes (30 words) - 16:14, 21 January 2023
- {{r|Email system}} {{r|Email security}}274 bytes (33 words) - 18:58, 29 October 2009
- {{r|Email system}} {{r|Email security}}179 bytes (21 words) - 18:47, 29 October 2009
- {{rpl|Email message formats}} {{rpl|Email message headers}}568 bytes (59 words) - 09:03, 22 April 2024
- === BCPs relevant to email security === ...ent, and even controversial. Most of the IETF recommendations relevant to email security are found in a series of documents called Best Current Practices (1 KB (200 words) - 17:37, 9 October 2009
- {{r|Email system}} {{r|Email processes and protocols}}188 bytes (25 words) - 18:55, 8 September 2009
- ...ques that have been developed to protect email users from Unsolicited Bulk Email (UBE or spam). See the [[Anti-spam_techniques/External_Links|External Link315 bytes (46 words) - 09:29, 27 November 2022
- ...Validation (BATV)''' provides a mechanism for assessing the validity of an email's envelope return (bounce) address. It permits the original submitter of a332 bytes (50 words) - 23:36, 30 September 2009
- {{r|Email}} {{r|Email processes and protocols}}2 KB (205 words) - 12:38, 5 November 2009
- {{r|Email system}} Auto-populated based on [[Special:WhatLinksHere/Email agents]]. Needs checking by a human.448 bytes (59 words) - 16:17, 11 January 2010
- '''Post Office Protocol''' is a client-server messaging protocol for [[Email|email]] which requires messages to be downloaded to a client's computer, phone or346 bytes (50 words) - 16:12, 21 January 2023
- #redirect [[email]]19 bytes (2 words) - 09:02, 19 July 2008
- {{r|Email system}} {{r|Email processes and protocols}}226 bytes (27 words) - 13:00, 16 March 2010
- ...col SMTP, for example, is concerned about all the details of conducting an email session over a reliable TCP connection, but not the least concerned about h === The email system ===1 KB (218 words) - 12:34, 28 August 2009
- Email user programs and their features.75 bytes (9 words) - 21:26, 27 August 2009
- {{r|Email system}} {{r|Email processes and protocols}}331 bytes (41 words) - 22:45, 1 October 2009
- {{r|Email}} {{r|Email system}}170 bytes (20 words) - 20:33, 23 November 2009
- Typical email sessions using the SMTP protocol.83 bytes (10 words) - 15:09, 26 September 2009
- ...group promoting [[Sender Policy Framework|SPF]] as a way of avoiding the [[Email forwarding problem|forwarding problem]], but it was never widely deployed.456 bytes (74 words) - 11:55, 5 November 2009
- Roles and responsibilities of organizations handling email.95 bytes (10 words) - 21:07, 27 August 2009
- Brief description of email security problems and solutions.95 bytes (11 words) - 19:08, 23 September 2009
- A typical email session using the SMTP protocol.84 bytes (11 words) - 17:21, 27 August 2009
- Requirements for submission of email using port 587.88 bytes (10 words) - 11:14, 29 August 2009
- Standard TCP port for email transfer using the SMTP protocol.97 bytes (13 words) - 12:28, 29 August 2009
- Standard TCP port for email retrieval using the POP protocol.97 bytes (13 words) - 12:26, 29 August 2009
- Standard TCP port for email retrieval using the IMAP protocol.98 bytes (13 words) - 12:27, 29 August 2009
- * [http://www.emailreplies.com/ email etiquette]200 bytes (28 words) - 22:16, 15 July 2008
- Brief explanation of an email system at the relay level.92 bytes (13 words) - 15:32, 19 September 2009
- TCP port reserved for authenticated submission of email messages.101 bytes (12 words) - 11:33, 29 August 2009
- {{r|Email system}} {{r|Email authentication}}770 bytes (118 words) - 02:45, 7 December 2009
- Techniques used to block or prevent spam, phishing, and other abuses of email.115 bytes (16 words) - 02:42, 7 December 2009
- 2. If the permission is an email, just paste in the email, format it so it makes sense, and click save. This was a Flickr Message (not an email) and it is available at http://www.flickr.com/mail/72157621160869588 :868 bytes (135 words) - 17:51, 9 July 2009
- {{r|Email system}} {{r|Email message formats}} (RFC-5322)1 KB (160 words) - 15:15, 26 September 2009
- ...y servers, clogged tubes, evil gremlins, whatever, but just don't send the email for a decent interval. That'd handle 75% of these throwaway accounts. --493 bytes (69 words) - 13:28, 12 March 2007
- Auto-populated based on [[Special:WhatLinksHere/Email message formats]]. Needs checking by a human. {{r|Email system}}439 bytes (57 words) - 16:17, 11 January 2010
- {{r|Email system}} {{r|Email authentication}}296 bytes (46 words) - 04:55, 26 October 2009
- {{r|Email processes and protocols}} {{r|Email system}}491 bytes (63 words) - 18:43, 11 January 2010
- A moderated email-based discussion group and bulletin board discussing the field of military137 bytes (17 words) - 13:02, 12 June 2008
- Brief overview of methods used to authenticate the sender of an email.107 bytes (15 words) - 21:44, 24 November 2008
- The header lines in every email message, defined in RFC 532297 bytes (13 words) - 10:52, 8 July 2009
- {{r|Email system}} {{r|Email security}}1 KB (163 words) - 02:30, 3 February 2010
- ...encode graphics, binary data, and other non-text items for inclusion in an email message.141 bytes (20 words) - 17:38, 27 August 2009
- BCP134 - Email Submission Operations: Access and Accountability Requirements [http://iana.org/protocols IANA Protocol Registries] - Registries relevant to email systems776 bytes (100 words) - 20:10, 11 February 2010
- {{r|Email}} {{r|Email system}}930 bytes (148 words) - 14:11, 1 October 2009
- ...ats and encodings used for text, pictures, and various other objects in an email.126 bytes (18 words) - 13:15, 25 November 2008
- {{r|Email system}} {{r|Email authentication}}945 bytes (149 words) - 14:36, 1 October 2009
- [[Email authentication]] method that became a basis of [[Sender Policy Framework|SP141 bytes (18 words) - 17:55, 29 October 2009
- [[Email authentication]] method that became a basis of [[Sender Policy Framework|SP141 bytes (18 words) - 17:56, 29 October 2009
- A [[web-based email]] service provided for free by [[Google]] and financed by [[advertising]].130 bytes (16 words) - 10:26, 2 May 2010
- A client-server messaging protocol for [[Email]] which allows messages to be stored indefinitely on the server.147 bytes (19 words) - 16:08, 21 January 2023
- The authentication failures that occur in some popular IP-based [[Email authentication]] methods when a forwarder is involved.163 bytes (20 words) - 07:13, 4 November 2009
- {{r|Email}} {{r|Email system}}573 bytes (87 words) - 14:00, 1 October 2009
- [[Email authentication]] method that verifies the hostname of an [[Simple Mail Tran197 bytes (23 words) - 05:06, 26 October 2009
- {{r|Email system}} {{r|Email}}761 bytes (100 words) - 09:48, 22 October 2010
- ...lies'', are textual context tools for indicating moods or expressions in [[email]], [[irc]], [[instant messenger]], or other [[real-time]] chat communicatio203 bytes (24 words) - 04:56, 6 January 2010
- ...r through the [[Internet Protocol Suite]] and supports applications like [[Email]] and the [[World Wide Web]].213 bytes (26 words) - 06:36, 23 November 2009
- [[Email authentication]] method that verifies a domain name found by a reverse DNS157 bytes (22 words) - 18:22, 28 October 2009
- {{r|Email processes and protocols}} {{r|Email system}}698 bytes (88 words) - 18:27, 11 January 2010
- [[Email authentication]] method that uses a [[Digital signature | digital signature157 bytes (20 words) - 10:59, 12 October 2009
- ...en source implementation of the [[Open PGP]] specification for the [[PGP]] email encryption program.141 bytes (18 words) - 00:58, 30 November 2008
- [[Email authentication]] method that verifies the domain name in a "purported" addr156 bytes (20 words) - 05:01, 26 October 2009
- Email authentication method that seeks to correlate the domain name in a "purport158 bytes (22 words) - 18:43, 29 August 2009
- An [[Email authentication|authentication method]] that verifies the purported sender's171 bytes (21 words) - 02:56, 7 December 2009
- '''Designated Mailers Protocol''' (DMP) is an email authentication method developed by Gordon Fecyk. It became a basis for the221 bytes (32 words) - 10:34, 10 December 2009
- A scheme for email relays to rewrite the Return Address on a forwarded message, allowing the f165 bytes (24 words) - 12:01, 5 November 2009
- [[Email authentication]] method that verifies the domain name in the envelope retur165 bytes (21 words) - 05:00, 26 October 2009
- {{r|Email system}} {{r|Email authentication}}707 bytes (110 words) - 18:33, 29 October 2009
- ...ished in DNS, the [[Domain Name System]].</ref>) are most commonly used by email receivers to screen out spam and other abusive emails flooding the Internet ...ithin hours. Honeypots have addresses that are never used in a legitimate email, but are posted on various websites and other locations where criminals typ832 bytes (126 words) - 12:19, 5 November 2009
- {{r|Email system}} {{r|Email authentication}}820 bytes (125 words) - 07:26, 4 November 2009
- BCP134 - Email Submission Operations: Access and Accountability Requirements 17 other registries related to email949 bytes (121 words) - 20:10, 11 February 2010
- The header lines in every email message, defined in RFC-5322.244 bytes (34 words) - 21:06, 30 August 2009
- .... Extensions to allow encoding of graphics and other non-ASCII content in email message bodies. ...nick, ed., http://tools.ietf.org/html/rfc5322. IETF Draft Standard. Basic email message formats, including headers.2 KB (245 words) - 21:49, 19 February 2010
- {{r|Email}} {{r|Email system}}858 bytes (138 words) - 14:06, 1 October 2009
- Description of the features of various programs allowing users to work with email on their own computers, as opposed to [[Webmail]], where everything is done239 bytes (39 words) - 19:55, 23 November 2009
- {{r|Email system}} {{r|Email processes and protocols}}909 bytes (144 words) - 14:38, 1 October 2009
- {{r|Email system}} {{r|Email processes and protocols}}909 bytes (144 words) - 14:30, 1 October 2009
- {{r|Email system}} {{r|Email processes and protocols}}918 bytes (146 words) - 14:33, 1 October 2009
- {{r|Email system}} {{r|Email processes and protocols}}938 bytes (145 words) - 16:14, 21 January 2023
- {{r|Email system}} {{r|Email processes and protocols}}939 bytes (148 words) - 14:49, 1 October 2009
- {{r|Email}} {{r|Web-based email}}950 bytes (153 words) - 07:33, 16 March 2010
- {{r|Email system}} {{r|Email processes and protocols}}975 bytes (153 words) - 14:46, 1 October 2009
- ...notes and citation-sources (references). Please read this page before you email us an article. ...mat, and also ‘.rtf’ files, which most word processors can generate. Just email your article, as an attachment, to '''[mailto:cz-wikiformat@mail.citizendiu3 KB (543 words) - 03:08, 25 February 2012
- ...oval includes edits made until March 12 which Roger Lohmann okayed through email477 bytes (48 words) - 19:20, 15 March 2009
- ...as sent to a great number of groups, the message was said to be 'spam'. As email became more available and popular, advertisers misused it in a manner simil ...ers use various tactics to avoid this — "throwaway" accounts on free email services, forged headers, "bulletproof" servers that will not disconnect th3 KB (541 words) - 16:24, 24 October 2013
- ...hentication Status", M. Kucherawy. 2009. - IETF Proposed Standard. A new email header field with results of message authentication.399 bytes (51 words) - 10:42, 10 December 2009
- ...y modern mail programs implement Bayesian spam filtering. [[Server-side]] email filters, such as [[SpamAssassin]] and [[Anti-Spam SMTP Proxy|ASSP]], make u ...ny email is spam, divided by the probability of finding those words in any email:7 KB (1,096 words) - 19:12, 27 September 2009
- ...source]] implementation of the [[Open PGP]] specification for the [[PGP]] email encryption program, developed for the [[GNU]] project of the [[Free Softwar340 bytes (50 words) - 05:48, 8 April 2024
- ...ldn't bounce spam and viruses.] - definition of "bounce spam" needed in "Email system" article.312 bytes (42 words) - 15:01, 27 January 2023