Search results

Jump to navigation Jump to search
Results 1 – 42 of 376
Advanced search

Search in namespaces:

Page title matches

  • ...] systems on an internal network allowing users within one organization to email each other.
    17 KB (2,764 words) - 17:00, 11 August 2024
  • ...ustrate the use of roles as building blocks in diagrams of various typical email systems.
    4 KB (528 words) - 17:00, 11 August 2024
  • ...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)
    6 KB (826 words) - 17:00, 11 August 2024
  • 25 bytes (3 words) - 08:51, 22 April 2024
  • 877 bytes (133 words) - 17:00, 11 August 2024
  • 12 bytes (1 word) - 14:13, 26 December 2007
  • ...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,324 words) - 17:01, 11 August 2024
  • 138 bytes (16 words) - 14:30, 13 July 2008
  • 5 KB (736 words) - 17:00, 11 August 2024
  • '''Email abuse''' is the unsolicited sending of [[spam]], third party [[advertisemen ...200508_UltimateGuidetoEmailSecurityUS_822533.pdf Clearswift White Paper on Email Security]</ref>
    748 bytes (96 words) - 17:00, 11 August 2024
  • {{seealso|Email processes and protocols}} ...and should be understood by anyone involved in the design or operation of email systems.
    11 KB (1,677 words) - 17:01, 11 August 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
  • 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 (614 words) - 17:00, 11 August 2024
  • .... 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 (212 words) - 17:00, 11 August 2024
  • 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
  • 80 bytes (9 words) - 06:06, 1 October 2009

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 (C
    282 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 desk
    461 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>
    748 bytes (96 words) - 17:00, 11 August 2024
  • {{r|Email system}} {{r|Email greylisting}}
    421 bytes (52 words) - 07:01, 11 July 2024
  • A client-server messaging protocol for [[Email|email]] which requires messages to be downloaded to a client's computer, phone or
    184 bytes (25 words) - 16:09, 21 January 2023
  • {{r|Email system}} {{r|Email security}}
    193 bytes (22 words) - 18:49, 29 October 2009
  • {{r|Email system}} {{r|Email security}}
    179 bytes (21 words) - 18:47, 29 October 2009
  • {{r|Email system}} {{r|Email security}}
    708 bytes (90 words) - 07:01, 8 August 2024
  • ...ccess Protocol''' (IMAP) is a client-server messaging protocol for [[Email|email]] which allows messages to be stored indefinitely on a server. IMAP is des
    244 bytes (34 words) - 12:00, 2 September 2024
  • {{rpl|Email message formats}} {{rpl|Email message headers}}
    568 bytes (59 words) - 09:03, 22 April 2024
  • ...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.
    1 KB (139 words) - 14:48, 13 August 2024
  • {{r|Email system}} {{r|Email history}}
    463 bytes (69 words) - 17:00, 11 August 2024
  • {{r|Email system}} {{r|Email processes and protocols}}
    611 bytes (79 words) - 17:00, 11 August 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 Link
    346 bytes (50 words) - 07:01, 11 July 2024
  • {{r|Email system}} Auto-populated based on [[Special:WhatLinksHere/Email agents]]. Needs checking by a human.
    594 bytes (78 words) - 17:00, 11 August 2024
  • {{r|Email system}} {{r|Email security}}
    363 bytes (43 words) - 12:01, 26 July 2024
  • ...Validation (BATV)''' provides a mechanism for assessing the validity of an email's envelope return (bounce) address. It permits the original submitter of a
    363 bytes (54 words) - 17:00, 20 July 2024
View (previous 20 | ) (20 | 50 | 100 | 250 | 500)