draft-crocker-email-arch-03
Folks, I've been working on an email architecture document, prompted by the increased diversity of folk who are trying to enhance the service, to mitigate minor problems like spam. I think the document has reached a stable point, in its attempt to describe the current service. I'd like to get feedback from the ops community. The latest version has substantial changes, but I think they are refinements from the previous version and reflect feedback I've received. Of course, any additional comments are more than welcome, and I have no doubt there can be debate about lots of the details. But the goal is to get this published sooner, rather than later, so I am hoping this is the last major revision. I've submitted the doc to the i-d folks. In the interim, you can access it at: ; <http://bbiw.net/specifications/draft-crocker-email-arch-03.html> ; <http://bbiw.net/specifications/draft-crocker-email-arch-03.txt> -- Dave Crocker Brandenburg InternetWorking +1.408.246.8253 dcrocker a t ... WE'VE MOVED to: www.bbiw.net
Dave Crocker wrote:
Folks,
I've been working on an email architecture document, prompted by the increased diversity of folk who are trying to enhance the service, to mitigate minor problems like spam. I think the document has reached a stable point, in its attempt to describe the current service. I'd like to get feedback from the ops community.
The latest version has substantial changes, but I think they are refinements from the previous version and reflect feedback I've received. Of course, any additional comments are more than welcome, and I have no doubt there can be debate about lots of the details.
But the goal is to get this published sooner, rather than later, so I am hoping this is the last major revision.
I've submitted the doc to the i-d folks. In the interim, you can access it at:
; <http://bbiw.net/specifications/draft-crocker-email-arch-03.html>
; <http://bbiw.net/specifications/draft-crocker-email-arch-03.txt>
-- Dave Crocker Brandenburg InternetWorking +1.408.246.8253 dcrocker a t ... WE'VE MOVED to: www.bbiw.net
Dave I've rename MHS to MTA (mail transport agent) which is the proper technical term. I guess there's a reason why you didn't use MTA? -- Martin Hepworth Snr Systems Administrator Solid State Logic Tel: +44 (0)1865 842300 ********************************************************************** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This footnote confirms that this email message has been swept for the presence of computer viruses and is believed to be clean. **********************************************************************
On Thu, 17 Feb 2005 16:16:37 +0000, Martin Hepworth wrote:
� I've rename MHS to MTA (mail transport agent) which is the proper � technical term. I guess there's a reason why you didn't use MTA?
Needed an additional term:
� Abstract
� ... and the transmission world, in the form of the Mail � Handling Service (MHS) composed of Mail Transfer Agents (MTA).
MTA is a single relay. MHS is the set of mail transfer components that form the entire service. So, it is the set of MSA, MTAs and MDA. I chose the particular term by resurrecting an existing one, from the X.400 world, where UA/MTA terminology was created. As the current document developed, the need for a term that referred to the entire infrastructure service kept appearing. And since I'm citing history, I'll note further x.400 irony: It had Administrative Management Domains (ADMD) but it had it as a core construct in the underlying technical architecture. The current doc uses it as an operations construct. d/ -- Dave Crocker Brandenburg InternetWorking +1.408.246.8253 dcrocker �a t ... WE'VE MOVED to: �www.bbiw.net
participants (2)
-
Dave Crocker
-
Martin Hepworth