Talk:Email processes and protocols: Difference between revisions

From Citizendium
Jump to navigation Jump to search
imported>David MacQuigg
No edit summary
imported>David MacQuigg
No edit summary
Line 1: Line 1:
{{subpages}}
{{subpages}}
The challenge in this article is to introduce a topic that has a huge amount of detail without overwhelming the non-expert reader. We need to avoid the "written by committee" style, where every contributor gets to squeeze in a few facts that he considers important. Luckily, we have an authoritative reference (RFC-5321) which covers all the details in 94 pages. We will include just those details that are needed for a coherent presentation of the basics, or that are interesting enough to outweigh the burden of including them. The reader needing more facts can also go to the Wikipedia article, which is a lot more verbose than this one.
The challenge in this article is to introduce a subtopic that has a huge amount of detail without overwhelming the non-expert reader. We can do that by keeping the focus narrow, relying on a parent topic to establish a conceptual framework and terminology for the discussion, and subtopics to offload much of the detail. We will include just those details that are needed for a coherent presentation of this topic, or that are interesting enough to outweigh the burden of including them.


Terminology is also a challenge. Should we use the same terms the experts use (MTA, Reverse Path, etc.) or terms that are more meaningful to non-experts (Mail Relay, Return Address, etc.)? We have chosen the latter, because our articles are intended for non-experts. Experts will have no trouble understanding what we mean, as long as we avoid mis-using any of their special terminology. We will capitalize terms that we intend to have a special meaning (e.g. Relay instead of relay).  
Luckily, we have an authoritative reference (RFC-5321) which covers all the details of SMTP in 94 pages. There is also a Wikipedia article on SMTP, which has a lot of facts and might be more readable than the RFC. In this article, we will try to avoid the "written by committee" style, where every contributor gets to squeeze in a few facts that he considers important.


Possible Additional Topics
Terminology is a challenge.  Should we use the same terms the experts use (MTA, Reverse Path, etc.) or terms that are more meaningful to non-experts (Mail Relay, Return Address, etc.)?  We have chosen the latter, because our articles are intended for non-experts.  Experts will have no trouble understanding what we mean, as long as we avoid mis-using any of their special terminology.  We will capitalize terms that we intend to have a special meaning (e.g. Relay instead of relay).


  ESMTP - RFC-5321
=== Possible Additional Subtopics ===
  Port 587 - RFC-4409
  ESMTP - RFC-5321
  Reply Codes
  Port 587 - RFC-4409
    550, 450 - greylisting
  Reply Codes
  Options
    550, 450 - greylisting
    MAIL FROM
  Options
    MAIL FROM

Revision as of 21:10, 24 November 2008

This article is developing and not approved.
Main Article
Discussion
Related Articles  [?]
Bibliography  [?]
External Links  [?]
Citable Version  [?]
 
To learn how to update the categories for this article, see here. To update categories, edit the metadata template.
 Definition Brief explanation of an email system at the relay level. [d] [e]
Checklist and Archives
 Workgroup category computers [Editors asked to check categories]
 Talk Archive none  English language variant American English

The challenge in this article is to introduce a subtopic that has a huge amount of detail without overwhelming the non-expert reader. We can do that by keeping the focus narrow, relying on a parent topic to establish a conceptual framework and terminology for the discussion, and subtopics to offload much of the detail. We will include just those details that are needed for a coherent presentation of this topic, or that are interesting enough to outweigh the burden of including them.

Luckily, we have an authoritative reference (RFC-5321) which covers all the details of SMTP in 94 pages. There is also a Wikipedia article on SMTP, which has a lot of facts and might be more readable than the RFC. In this article, we will try to avoid the "written by committee" style, where every contributor gets to squeeze in a few facts that he considers important.

Terminology is a challenge. Should we use the same terms the experts use (MTA, Reverse Path, etc.) or terms that are more meaningful to non-experts (Mail Relay, Return Address, etc.)? We have chosen the latter, because our articles are intended for non-experts. Experts will have no trouble understanding what we mean, as long as we avoid mis-using any of their special terminology. We will capitalize terms that we intend to have a special meaning (e.g. Relay instead of relay).

Possible Additional Subtopics

  ESMTP - RFC-5321
  Port 587 - RFC-4409
  Reply Codes
    550, 450 - greylisting
  Options
    MAIL FROM