Skip to Content.
Sympa Menu

internetworkers - Re: [internetworkers] contacts or suggestions for dealing with SPEWS

internetworkers AT lists.ibiblio.org

Subject: Internetworkers: http://www.ibiblio.org/internetworkers/

List archive

Chronological Thread  
  • From: Steven Champeon <schampeo AT hesketh.com>
  • To: "Internetworkers: http://www.ibiblio.org/internetworkers/" <internetworkers AT lists.ibiblio.org>
  • Subject: Re: [internetworkers] contacts or suggestions for dealing with SPEWS
  • Date: Wed, 24 Mar 2004 14:50:44 -0500

on Wed, Mar 24, 2004 at 01:29:01PM -0500, Tanner Lovelace wrote:
> Steven Champeon said the following on 3/24/04 1:16 PM:
>
> > "4. NETWORK OPERATIONS MAILBOX NAMES
> >
> > Operations addresses are intended to provide recourse for customers,
> > providers and others who are experiencing difficulties with the
> > organization's Internet service.
> >
> > MAILBOX AREA USAGE
> > ----------- ---------------- ---------------------------
> > ABUSE Customer Relations Inappropriate public behaviour
> > NOC Network Operations Network infrastructure
> > SECURITY Network Security Security bulletins or queries"
> >
> >Maybe I'll suggest to Derek that he highlight those sections as well.
> >
> >Steve
> >
>
> So, then, it's not just postmaster and abuse that are required?
> Instead, it's postmaster, abuse, noc, and security? It's interesting
> how the story changes to suit the purposes of those who are
> talking about it...

"ABSTRACT

This specification enumerates and describes Internet mail addresses
(mailbox name @ host reference) to be used when contacting personnel
at an organization. Mailbox names are provided for both operations
and business functions. Additional mailbox names and aliases are not
prohibited, but organizations which support email exchanges with the
Internet are encouraged to support AT LEAST each mailbox name for
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
which the associated function exists within the organization.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

[...]

The purpose of this memo is to aggregate and specify the basic set of
mailbox names which organizations need to support. Most
^^^^
organizations do not need to support the full set of mailbox names
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
defined here, since not every organization will implement all of
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
the associated services. However, if a given service is offerred,
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
then the associated mailbox name(es) must be supported, resulting in
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
delivery to a recipient appropriate for the referenced service or
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
role."
^^^^

Tanner, I'm not going to waste any more time on this. Go read the
/whole thing/ - all the words, not just the highlighted ones, starting
with the /top/ of the document and proceeding down to the /end/ - and
if you have more specific questions, let me know. As far as I can
tell, you're just being stubborn because it amuses you, not because
you honestly care.

--
hesketh.com/inc. v: +1(919)834-2552 f: +1(919)834-2554 w: http://hesketh.com
Buy "Cascading Style Sheets: Separating Content from Presentation, 2/e" today!
http://www.amazon.com/exec/obidos/ASIN/159059231X/heskecominc-20/ref=nosim/




Archive powered by MHonArc 2.6.24.

Top of Page