Difference between revisions of "RFC1211"

From RFC-Wiki
Line 1: Line 1:
 
 
 
 
 
 
 
Network Working Group                                        A. Westine
 
Network Working Group                                        A. Westine
 
Request for Comments:  1211                                    J. Postel
 
Request for Comments:  1211                                    J. Postel
                                                                    ISI
+
                                                                  ISI
                                                              March 1991
+
                                                          March 1991
 
 
  
          Problems with the Maintenance of Large Mailing Lists
+
      Problems with the Maintenance of Large Mailing Lists
  
 
Status of this Memo
 
Status of this Memo
  
  This RFC discusses problems with maintaining large mailing lists,
+
This RFC discusses problems with maintaining large mailing lists,
  especially the processing of error reports.  This memo provides
+
especially the processing of error reports.  This memo provides
  information for the Internet community.  It does not specify an
+
information for the Internet community.  It does not specify an
  Internet standard.  Distribution of this memo is unlimited.
+
Internet standard.  Distribution of this memo is unlimited.
  
 
Table of Contents
 
Table of Contents
  
  1.  Introduction..............................................  1
+
1.  Introduction..............................................  1
  2.  Discussion................................................  1
+
2.  Discussion................................................  1
  3.  Typical Problems..........................................  3
+
3.  Typical Problems..........................................  3
  3.1. Misdirected Error Reports.................................  3
+
3.1. Misdirected Error Reports.................................  3
  3.2. Sublists..................................................  3
+
3.2. Sublists..................................................  3
  3.3. Misdirected Requests......................................  5
+
3.3. Misdirected Requests......................................  5
  3.4. Misdirected Messages......................................  5
+
3.4. Misdirected Messages......................................  5
  4.  Summary...................................................  5
+
4.  Summary...................................................  5
  APPENDIX A - I used to be on the List..........................  6
+
APPENDIX A - I used to be on the List..........................  6
  APPENDIX B - Changing Addresses and Sublists...................  8
+
APPENDIX B - Changing Addresses and Sublists...................  8
  APPENDIX C - Sublists and Other Protocol Worlds................  9
+
APPENDIX C - Sublists and Other Protocol Worlds................  9
  APPENDIX D - Errors from Hidden Hosts..........................  10
+
APPENDIX D - Errors from Hidden Hosts..........................  10
  APPENDIX E - No Postmaster.....................................  12
+
APPENDIX E - No Postmaster.....................................  12
  APPENDIX F - Examples of Error Messages........................  14
+
APPENDIX F - Examples of Error Messages........................  14
  5.  Security Considerations...................................  53
+
5.  Security Considerations...................................  53
  6.  Authors' Addresses........................................  54
+
6.  Authors' Addresses........................................  54
  
1.  Introduction
+
== Introduction ==
  
  Maintaining large mailing lists, especially the processing of error
+
Maintaining large mailing lists, especially the processing of error
  reports, poses many problems.  Most of the examples come from the
+
reports, poses many problems.  Most of the examples come from the
  experience of managing the Internet Engineering Task Force (IETF)
+
experience of managing the Internet Engineering Task Force (IETF)
  mailing list.  Many examples are presented in this memo.  Most of the
+
mailing list.  Many examples are presented in this memo.  Most of the
  specific problems shown have already been corrected.
+
specific problems shown have already been corrected.
  
2. Discussion
+
== Discussion ==
  
  At USC - Information Sciences Institute (ISI) we maintain mailing
+
At USC - Information Sciences Institute (ISI) we maintain mailing
  lists for the Internet Research Groups, the IETF, and other Internet
+
lists for the Internet Research Groups, the IETF, and other Internet
  groups; about 25 lists altogether.  We receive about 400 messages a
+
groups; about 25 lists altogether.  We receive about 400 messages a
  month requesting additions or deletions to these lists.  There are
+
month requesting additions or deletions to these lists.  There are
  
 +
about 20 messages a day requesting changes to the lists.
  
 +
We also receive about 300 error messages a month due to mail delivery
 +
problems.  Many of these are duplicates, but the net result is that
 +
about 10 cases per day need to be investigated.
  
Westine & Postel                                             
+
Many of the error reports are for "soft errors", primarily delayed
 +
delivery notices, such as "not delivered for 2 days, will try for 3
 +
more days".  These just waste the list maintainer's time and are
 +
otherwise ignored.  This is especially wasteful when such messages
 +
are repeated every day.  However, if the same host is a cause of such
 +
messages for many days in a row, the list maintainer may investigate.
  
RFC 1211              Problems with Mailing Lists            March 1991
+
Please note that ignoring the soft errors is not always easy, since
 +
error messages often contain error reports on several mailboxes,
 +
requiring the error message to be read carefully to pick out the hard
 +
errors.
  
 +
The error reports that indicate hard errors, such as "no such user"
 +
require the list maintainer to take action.  In many cases the
 +
appropriate action is to simply delete the user mailbox from the
 +
list.  However, if the mailbox in question is someone known to be
 +
active as a working group chair, or such, further investigation is
 +
necessary.  The more general case of "no such host" may be a
 +
temporary condition, but if it continues for several days it must be
 +
investigated.
  
  about 20 messages a day requesting changes to the lists.
+
Since the error conditions do not have standardized names (for
 +
example, "no such user" vs. "user unknown") it is sometimes difficult
 +
to understand whether a soft or hard error is being reported, and
 +
what one should do about it.  For example, what does "Can't Find Mail
 +
Center!" mean, or what should one do about "mailll:%MAIL-E-OPENOUT,
 +
error opening SYS$USER2:[STGEORGE.LONGMAIL]MAIL$00040093BE236612.MAI;
 +
as outputI)"?
  
  We also receive about 300 error messages a month due to mail delivery
+
The first step in investigating a problem with a user mailbox is to
  problemsMany of these are duplicates, but the net result is that
+
see if it is on the listIf so, the next step is to see if there
  about 10 cases per day need to be investigated.
+
really is a problem with it.  This is done by using the SMTP VRFY and
 +
EXPN features, Finger, or Whois.  This often develops information
 +
suggesting that the user has recently changed his address.  This has
 +
to be confirmed through an exchange of messages (with the postmaster)
 +
and then the mailing list must be updated.
  
  Many of the error reports are for "soft errors", primarily delayed
+
If the user is not on the list, then it is likely the mail is sent
  delivery notices, such as "not delivered for 2 days, will try for 3
+
via an exploder or sublistSo the investigation focuses on finding
  more days"These just waste the list maintainer's time and are
+
which exploder may be involved, usually this is found by looking at
  otherwise ignored.  This is especially wasteful when such messages
+
the path (from the received lines) of the error reportThe exploder
  are repeated every dayHowever, if the same host is a cause of such
+
that is the source of the error can sometimes be checked using the
  messages for many days in a row, the list maintainer may investigate.
 
  
  Please note that ignoring the soft errors is not always easy, since
+
SMTP EXPN feature.  Then the postmaster is notified.
  error messages often contain error reports on several mailboxes,
 
  requiring the error message to be read carefully to pick out the hard
 
  errors.
 
  
  The error reports that indicate hard errors, such as "no such user"
+
If the error report is about a host being unknown, the programs
  require the list maintainer to take action.  In many cases the
+
"whathost", "dig", "ping", and "traceroute" may be used to find the
  appropriate action is to simply delete the user mailbox from the
+
problem.  However, getting the problem fixed may require
  list.  However, if the mailbox in question is someone known to be
+
communication with host and domain administrators.
  active as a working group chair, or such, further investigation is
 
  necessary.  The more general case of "no such host" may be a
 
  temporary condition, but if it continues for several days it must be
 
  investigated.
 
  
  Since the error conditions do not have standardized names (for
+
What to do if problems can't be resolved: Delete the offending entry
  example, "no such user" vs. "user unknown") it is sometimes difficult
+
from the list that may eventually cause the following response: "I
  to understand whether a soft or hard error is being reported, and
+
used to be on the ietf list, how come I am not getting the messages
  what one should do about it.  For example, what does "Can't Find Mail
+
any more?" (See Appendix A.)
  Center!" mean, or what should one do about "mailll:%MAIL-E-OPENOUT,
 
  error opening SYS$USER2:[STGEORGE.LONGMAIL]MAIL$00040093BE236612.MAI;
 
  as outputI)"?
 
  
  The first step in investigating a problem with a user mailbox is to
+
== Typical Problems ==
  see if it is on the list.  If so, the next step is to see if there
 
  really is a problem with it.  This is done by using the SMTP VRFY and
 
  EXPN features, Finger, or Whois.  This often develops information
 
  suggesting that the user has recently changed his address.  This has
 
  to be confirmed through an exchange of messages (with the postmaster)
 
  and then the mailing list must be updated.
 
  
  If the user is not on the list, then it is likely the mail is sent
+
In this section we discuss typical and frequent problems that occur
  via an exploder or sublist.  So the investigation focuses on finding
+
with large mailing lists.
  which exploder may be involved, usually this is found by looking at
 
  the path (from the received lines) of the error report. The exploder
 
  that is the source of the error can sometimes be checked using the
 
  
 +
=== Misdirected Error Reports ===
  
 +
The most frequent problem is that error reports are sent to the
 +
author of the message rather than the list owner.  One way this can
 +
happen is when there is trouble with the author's host not connecting
 +
to another host along the route before it reaches ISI where the
 +
mailing list is.
  
Westine & Postel                                             
+
At ISI the SMTP "from" information is added when the message is
 +
distributed to the list so that hosts following the SMTP protocol
 +
will send their error reports to the list owner.  However, not all
 +
hosts do this properly.
  
RFC 1211              Problems with Mailing Lists            March 1991
+
Another problem is that some machines do not pay attention to the
 +
SMTP information about where to send error reports.
  
 +
=== Sublists ===
  
  SMTP EXPN featureThen the postmaster is notified.
+
What is a sublist?  It is a mailbox with an alias-name that expands
 +
to a mailing-list or group of recipientsThere are many sublists on
 +
our mailing lists.
  
  If the error report is about a host being unknown, the programs
+
When a user requests that a mailbox be added to a list that looks
  "whathost", "dig", "ping", and "traceroute" may be used to find the
+
like an exploder, the following message is sent:
  problem.  However, getting the problem fixed may require
 
  communication with host and domain administrators.
 
  
   What to do if problems can't be resolved: Delete the offending entry
+
   We ask that all list maintainters of exploder mailboxes (an
   from the list that may eventually cause the following response: "I
+
  alias-name that expands to a mailing-list or group of recipients)
   used to be on the ietf list, how come I am not getting the messages
+
  set up some sort of ownership at their site, for their list.  What
   any more?" (See Appendix A.)
+
   this means is, is any mailbox on your list is invalid, the error
 +
   message will go to you (the list owner), and you can delete that
 +
   mailbox from your list.
  
3.  Typical Problems
+
  An example of an entry in your aliases file would be:
  
  In this section we discuss typical and frequent problems that occur
+
      owner-ietf-local:  stev@vax.ftp.com,
  with large mailing lists.
 
  
3.1  Misdirected Error Reports
+
        (or your list maintainer/postmaster)
  
  The most frequent problem is that error reports are sent to the
+
It appears that few people understand the concept of list ownership,
  author of the message rather than the list ownerOne way this can
+
or they do not set it up correctlyThere is ample evidence of
  happen is when there is trouble with the author's host not connecting
+
problems in this area.
  to another host along the route before it reaches ISI where the
 
  mailing list is.
 
  
  At ISI the SMTP "from" information is added when the message is
+
When investigating "user unknown" messages it is often the case that
  distributed to the list so that hosts following the SMTP protocol
+
the user is not individually listed on our list.  The next step is to
  will send their error reports to the list ownerHowever, not all
+
check received lines and hunt for an exploder list with a host
  hosts do this properly.
+
similar to the one that the error came from or points to.  At that
 
+
point we attempt to use SMTP EXPN or VRFY to check that the user is
  Another problem is that some machines do not pay attention to the
+
on a sublistSince many hosts do not implement EXPN or VRFY, the
  SMTP information about where to send error reports.
+
result of our check is inconclusive.  We then contact the list
 
+
maintainer and ask him to delete the invalid mailbox if it is on his
3.2  Sublists
+
sublist.
  
  What is a sublist? It is a mailbox with an alias-name that expands
+
Another problem occurs when someone on a sublist wants to change the
  to a mailing-list or group of recipientsThere are many sublists on
+
name of his mailbox. We look through the main list to make the
  our mailing lists.
+
correction and if that mailbox is not on the list we check the
 +
received lines and look for clues to determine which host this user
 +
may be on.  More than likely it is a sublist(See Appendix B.)
  
  When a user requests that a mailbox be added to a list that looks
+
When the mailbox is in another protocol world (like UUCP or BITNET)
  like an exploder, the following message is sent:
+
there are often problems with the handling and direction of error
 +
reports. (See Appendix C.)
  
      We ask that all list maintainters of exploder mailboxes (an
+
Sometimes we are unable to find the addresses reported in the error
      alias-name that expands to a mailing-list or group of recipients)
+
message on the mailing list in question.  In such a case we check the
      set up some sort of ownership at their site, for their listWhat
+
mailing list for a host name also named in the received lines of a
      this means is, is any mailbox on your list is invalid, the error
+
message in errorIf we find a match then we look for an exploder on
      message will go to you (the list owner), and you can delete that
+
that host and expand the sublist there to see if the mailbox in
      mailbox from your list.
+
question is on that sublist.  (See Appendix D.)
  
 +
At the time a sublist is entered into our list we record the name of
 +
the requestor and consider him the sublist owner.  As people change
 +
roles or companies this contact sometimes fails, in that case we fall
 +
back to contacting the postmaster.  However, not every site has a
 +
"postmaster" mailbox. (See Appendix E.)
  
 +
Most users send their requests and changes to the IETF-Request
 +
mailbox, when they are on, in fact, a sublist, usually at their own
 +
company.  This creates a problem for us trying to determine which
 +
exploder they're on.
  
Westine & Postel                                             
+
In this case, the request message is forwarded to the sublist owner
 +
so he can make changes to his list.  However, sometimes hosts may be
 +
somewhat similar in name (from the same organization, but in a
 +
different department, in a different building, off campus, etc.) and
 +
it's hard to know if this person should really be on that particular
 +
sublist, or listed individually.  Occasionally, we examine the main
 +
file to see if there are individual addresses that could be
 +
incorporated in a sublist.
  
RFC 1211              Problems with Mailing Lists            March 1991
+
=== Misdirected Requests ===
  
 +
Some users don't know that mailing lists usually have a "request"
 +
mailbox, so they mistakenly send their requests to the main list.
 +
When this happens, several people will resend the request to the list
 +
maintainer and then want to know if the request was completed.
  
      An example of an entry in your aliases file would be:
+
=== Misdirected Messages ===
  
        owner-ietf-local: [email protected].com,
+
There are also messages that go to the request mailbox when they are
 +
intended for the main list. These messages get forwarded to the main
 +
list and a message is sent to the user notifying him of the
 +
correction and the proper way to address his message.
  
            (or your list maintainer/postmaster)
+
== Summary ==
  
  It appears that few people understand the concept of list ownership,
+
Running a mailing list should be easy, and with small lists it is.
  or they do not set it up correctlyThere is ample evidence of
+
The number of changes and errors are small and infrequent.  But when
  problems in this area.
+
lists get large and traffic gets heavy, the number of changes and
 +
errors grow to many a dayThe level of effort to manage a mailing
 +
list of substantial size and use becomes significant.
  
  When investigating "user unknown" messages it is often the case that
+
An additional problem is the creativity shown by mail program
  the user is not individually listed on our list.  The next step is to
+
developers in inventing numerous different error reportsWe present
  check received lines and hunt for an exploder list with a host
+
a large sample of such messages in Appendix F.  We hope that these
  similar to the one that the error came from or points toAt that
+
examples will be of help to other mailing list maintainers.
  point we attempt to use SMTP EXPN or VRFY to check that the user is
 
  on a sublist.  Since many hosts do not implement EXPN or VRFY, the
 
  result of our check is inconclusive.  We then contact the list
 
  maintainer and ask him to delete the invalid mailbox if it is on his
 
  sublist.
 
  
  Another problem occurs when someone on a sublist wants to change the
+
Our experience with maintaining large lists suggests the following:
  name of his mailbox.  We look through the main list to make the
 
  correction and if that mailbox is not on the list we check the
 
  received lines and look for clues to determine which host this user
 
  may be on.  More than likely it is a sublist.  (See Appendix B.)
 
  
  When the mailbox is in another protocol world (like UUCP or BITNET)
+
Users:  Please be considerate and try to work problems out locally.
  there are often problems with the handling and direction of error
 
  reports. (See Appendix C.)
 
  
  Sometimes we are unable to find the addresses reported in the error
+
Sublist owners:  Please do everything you can to get the error
  message on the mailing list in questionIn such a case we check the
+
messages related to your sublist to go to youPlease try to get
  mailing list for a host name also named in the received lines of a
+
users on your system to talk to you about additions and deletions.
  message in error.  If we find a match then we look for an exploder on
 
  that host and expand the sublist there to see if the mailbox in
 
  question is on that sublist.  (See Appendix D.)
 
  
  At the time a sublist is entered into our list we record the name of
+
                            APPENDIX A
  the requestor and consider him the sublist owner.  As people change
 
  roles or companies this contact sometimes fails, in that case we fall
 
  back to contacting the postmaster.  However, not every site has a
 
  "postmaster" mailbox. (See Appendix E.)
 
 
 
  Most users send their requests and changes to the IETF-Request
 
  mailbox, when they are on, in fact, a sublist, usually at their own
 
  company.  This creates a problem for us trying to determine which
 
  exploder they're on.
 
 
 
 
 
 
 
 
 
Westine & Postel                                             
 
 
 
RFC 1211              Problems with Mailing Lists            March 1991
 
 
 
 
 
  In this case, the request message is forwarded to the sublist owner
 
  so he can make changes to his list.  However, sometimes hosts may be
 
  somewhat similar in name (from the same organization, but in a
 
  different department, in a different building, off campus, etc.) and
 
  it's hard to know if this person should really be on that particular
 
  sublist, or listed individually.  Occasionally, we examine the main
 
  file to see if there are individual addresses that could be
 
  incorporated in a sublist.
 
 
 
3.3  Misdirected Requests
 
 
 
  Some users don't know that mailing lists usually have a "request"
 
  mailbox, so they mistakenly send their requests to the main list.
 
  When this happens, several people will resend the request to the list
 
  maintainer and then want to know if the request was completed.
 
 
 
3.4  Misdirected Messages
 
 
 
  There are also messages that go to the request mailbox when they are
 
  intended for the main list.  These messages get forwarded to the main
 
  list and a message is sent to the user notifying him of the
 
  correction and the proper way to address his message.
 
 
 
4.  Summary
 
 
 
  Running a mailing list should be easy, and with small lists it is.
 
  The number of changes and errors are small and infrequent.  But when
 
  lists get large and traffic gets heavy, the number of changes and
 
  errors grow to many a day.  The level of effort to manage a mailing
 
  list of substantial size and use becomes significant.
 
 
 
  An additional problem is the creativity shown by mail program
 
  developers in inventing numerous different error reports.  We present
 
  a large sample of such messages in Appendix F.  We hope that these
 
  examples will be of help to other mailing list maintainers.
 
 
 
  Our experience with maintaining large lists suggests the following:
 
 
 
  Users:  Please be considerate and try to work problems out locally.
 
 
 
  Sublist owners:  Please do everything you can to get the error
 
  messages related to your sublist to go to you.  Please try to get
 
  users on your system to talk to you about additions and deletions.
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
Westine & Postel                                             
 
 
 
RFC 1211              Problems with Mailing Lists            March 1991
 
 
 
 
 
                                APPENDIX A
 
  
 
A.1.  Inquiry Message From User Regarding His Mailbox
 
A.1.  Inquiry Message From User Regarding His Mailbox
  
  Date: Tue, 6 Nov 90 03:02:09 PST
+
Date: Tue, 6 Nov 90 03:02:09 PST
  From: "Stewart Bryant, RE02-G/H2, DTN: 830 4682"
+
From: "Stewart Bryant, RE02-G/H2, DTN: 830 4682"
        <[email protected]>
+
+
  Subject: dist list
+
Subject: dist list
  
  Please will you check that I have not been deleted from this
+
Please will you check that I have not been deleted from this
  distribution list.
+
distribution list.
  
  My email address is : [email protected]
+
My email address is : [email protected]
  
  Thanks
+
Thanks
  
  Stewart
+
Stewart
  
23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)~~
+
21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)~~
  
 
A.2.  Message To User - His Mailbox Was Re-added
 
A.2.  Message To User - His Mailbox Was Re-added
  
  To: "Stewart Bryant, RE02-G/H2,
+
To: "Stewart Bryant, RE02-G/H2,
      DTN: 830 4682" <[email protected]>
+
    DTN: 830 4682" <[email protected]>
+
  Reply-To: [email protected]
+
  Subject: Re: dist list
+
Subject: Re: dist list
  In-reply-to: Your message of Tue, 06 Nov 90 03:02:09 -0800.
+
In-reply-to: Your message of Tue, 06 Nov 90 03:02:09 -0800.
                <[email protected]>
+
            <[email protected]>
  Date: Tue, 06 Nov 90 13:54:23 PST
+
Date: Tue, 06 Nov 90 13:54:23 PST
  From: Ann Westine <[email protected]>
+
From: Ann Westine <[email protected]>
  
  Hi Stewart,
+
Hi Stewart,
  
  > Please will you check that I have not been deleted from this
+
> Please will you check that I have not been deleted from this
  > distribution. list.
+
> distribution. list.
  >
+
>
  > My email address is:  [email protected]
+
> My email address is:  [email protected]
  
          I readded you to the list.
+
        I readded you to the list.
  
  --Ann
+
--Ann
 
 
23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)~~
 
 
 
 
 
 
 
 
 
 
 
 
 
Westine & Postel                                             
 
 
 
RFC 1211              Problems with Mailing Lists            March 1991
 
  
 +
21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)~~
  
 
A.3.  User Name Readded and It Bounced
 
A.3.  User Name Readded and It Bounced
  
  Date:    Tue, 06 Nov 90 17:25:15 -0800
+
Date:    Tue, 06 Nov 90 17:25:15 -0800
  From:    [email protected] (Mail Delivery Subsystem)
+
From:    [email protected] (Mail Delivery Subsystem)
  To:      [email protected]
+
To:      [email protected]
  Subject: Returned mail: User unknown
+
Subject: Returned mail: User unknown
  
      ----- Transcript of session follows -----
+
    ----- Transcript of session follows -----
  mail11: Error from DECnet MAIL object on node "janus",
+
mail11: Error from DECnet MAIL object on node "janus",
            during mail delivery to <JANUS::BRYANT>.
+
        during mail delivery to <JANUS::BRYANT>.
            Remote error code is 0x7e81d2, message is:
+
        Remote error code is 0x7e81d2, message is:
  %MAIL-E-ERRACTRNS, error activating transport NM
+
%MAIL-E-ERRACTRNS, error activating transport NM
            (can't decypher error code)
+
        (can't decypher error code)
  550 <[email protected]>... User unknown
+
550 <[email protected]>... User unknown
  
      ----- Recipients of this delivery -----
+
  ----- Recipients of this delivery -----
  <[email protected]> (bounced)
+
<[email protected]> (bounced)
  
      ----- Unsent message follows -----
+
  ----- Unsent message follows -----
  Received: by decpa.pa.dec.com; id AA21747; Tue, 6 Nov 90 13:54:38
+
Received: by decpa.pa.dec.com; id AA21747; Tue, 6 Nov 90 13:54:38
  Received: from LOCALHOST by venera.isi.edu (5.61/5.61+local)
+
Received: from LOCALHOST by venera.isi.edu (5.61/5.61+local)
            id <AA24660>; Tue, 6 Nov 90 13:54:25 -0800
+
        id <AA24660>; Tue, 6 Nov 90 13:54:25 -0800
  To: "Stewart Bryant, RE02-G/H2,
+
To: "Stewart Bryant, RE02-G/H2,
        DTN: 830 4682" <[email protected]>
+
    DTN: 830 4682" <[email protected]>
+
  Reply-To: [email protected]
+
  Subject: Re: dist list
+
Subject: Re: dist list
  In-Reply-To: Your message of Tue, 06 Nov 90 03:02:09 -0800.
+
In-Reply-To: Your message of Tue, 06 Nov 90 03:02:09 -0800.
        <[email protected]>
+
  Date: Tue, 06 Nov 90 13:54:23 PST
+
Date: Tue, 06 Nov 90 13:54:23 PST
  From: Ann Westine <[email protected]>
+
From: Ann Westine <[email protected]>
  
  Hi Stewart,
+
Hi Stewart,
  
  > Please will you check that I have not been deleted from this
+
> Please will you check that I have not been deleted from this
  > distribution list.
+
> distribution list.
  >
+
>
  > My email address is
+
> My email address is
  >
+
>
+
  
  I readded you to the list.
+
I readded you to the list.
  
  --Ann
+
--Ann
  
 
************************************************************************
 
************************************************************************
  
 
+
                            APPENDIX B
 
 
 
 
 
 
Westine & Postel                                             
 
 
 
RFC 1211              Problems with Mailing Lists            March 1991
 
 
 
 
 
                              APPENDIX B
 
  
 
In this example, the old mailbox "[email protected]" was to
 
In this example, the old mailbox "[email protected]" was to
Line 411: Line 344:
 
the mailbox.
 
the mailbox.
  
23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)~~
+
21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)~~
  
 
B.1.  Error Report
 
B.1.  Error Report
  
  Date:    Mon, 22 Oct 90 14:05:38 -0500
+
Date:    Mon, 22 Oct 90 14:05:38 -0500
  From:    [email protected] (Kent Landfield)
+
From:    [email protected] (Kent Landfield)
  To:      [email protected]
+
To:      [email protected]
  Subject: E-mail address change
+
Subject: E-mail address change
  
  Hello,
+
Hello,
  
  I am currently receiving ietf related email at
+
I am currently receiving ietf related email at
  [email protected].  I am moving to sparky.IMD.Sterling.COM
+
[email protected].  I am moving to sparky.IMD.Sterling.COM
  as the ssbell system is going away.  Could you please change my
+
as the ssbell system is going away.  Could you please change my
  address to [email protected] so that I can stay on the
+
address to [email protected] so that I can stay on the
  list ? Thanks.
+
list ? Thanks.
  
23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)~~
+
21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)~~
  
 
B.2.  Message Sent to Postmaster
 
B.2.  Message Sent to Postmaster
  
+
  Subject: Address -  <ssbell!kent>
+
Subject: Address -  <ssbell!kent>
  Date: Thu, 25 Oct 90 13:44:24 PDT
+
Date: Thu, 25 Oct 90 13:44:24 PDT
  From: Ann Westine <[email protected]>
+
From: Ann Westine <[email protected]>
  
  Hi,
+
Hi,
  
  Please delete the mailbox ssbell!kent from the "post-ietf" list.  I
+
Please delete the mailbox ssbell!kent from the "post-ietf" list.  I
  will add his new address "[email protected]" directly to
+
will add his new address "[email protected]" directly to
  the ietf list.  Thanks. Ann
+
the ietf list.  Thanks. Ann
  
 
************************************************************************
 
************************************************************************
  
 
+
                          APPENDIX C
 
 
 
 
Westine & Postel                                             
 
 
 
RFC 1211              Problems with Mailing Lists            March 1991
 
 
 
 
 
                              APPENDIX C
 
  
 
Another problem comes up when a sublist happens to be located in another
 
Another problem comes up when a sublist happens to be located in another
Line 463: Line 388:
 
the mail relay THINK.COM.
 
the mail relay THINK.COM.
  
23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)~~
+
21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)~~
  
 
C.1.  Error Report
 
C.1.  Error Report
  
+
  Date:    Fri, 05 Oct 90 23:45:26 -0400
+
Date:    Fri, 05 Oct 90 23:45:26 -0400
  From:    [email protected]
+
  Subject: Warning From uucp
+
Subject: Warning From uucp
  
  We have been unable to contact machine 'signet' since you
+
We have been unable to contact machine 'signet' since you
  queued your job.
+
queued your job.
  
          mail signet!ietf-interest    (Date 10/04)
+
        mail signet!ietf-interest    (Date 10/04)
  
  Attempts will continue for a few more days.
+
Attempts will continue for a few more days.
  
          Sincerely,
+
        Sincerely,
          early-bird!uucp
+
        early-bird!uucp
  
23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)~~
+
21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)~~
  
 
C.2.  Message Sent to Postmaster
 
C.2.  Message Sent to Postmaster
  
+
  Subject: unable to contact machine 'signet'
+
Subject: unable to contact machine 'signet'
  Reply-To: [email protected]
+
  Date: Mon, 08 Oct 90 09:42:54 PDT
+
Date: Mon, 08 Oct 90 09:42:54 PDT
  From: Ann Westine <[email protected]>
+
From: Ann Westine <[email protected]>
  
  Hi,
+
Hi,
  
  We have a mailbox on the ietf list that gets relayed through your
+
We have a mailbox on the ietf list that gets relayed through your
  host THINK.COM. We will have to delete this mailbox if a connection
+
host THINK.COM. We will have to delete this mailbox if a connection
  cannot be corrected.  Thanks, Ann
+
cannot be corrected.  Thanks, Ann
  
 
************************************************************************
 
************************************************************************
  
 
+
                            APPENDIX D
 
 
 
 
 
 
Westine & Postel                                             
 
 
 
RFC 1211              Problems with Mailing Lists            March 1991
 
 
 
 
 
                              APPENDIX D
 
  
 
Sometimes, the addresses reported in error can't be found on the IETF
 
Sometimes, the addresses reported in error can't be found on the IETF
Line 524: Line 440:
 
sublist.
 
sublist.
  
23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)~~
+
21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)~~
  
 
D.1.  Error Report
 
D.1.  Error Report
  
  Return-Path: [email protected]
+
Return-Path: [email protected]
  Received-Date: Wed, 7 Nov 90 14:34:51 PST
+
Received-Date: Wed, 7 Nov 90 14:34:51 PST
  Received: from venera.isi.edu by zephyr.isi.edu (4.1/4.0.3-4)
+
Received: from venera.isi.edu by zephyr.isi.edu (4.1/4.0.3-4)
          id <AA16502>; Wed, 7 Nov 90 14:34:51 PST
+
        id <AA16502>; Wed, 7 Nov 90 14:34:51 PST
  Posted-Date: Wed, 7 Nov 90 13:54:08 -0800
+
Posted-Date: Wed, 7 Nov 90 13:54:08 -0800
  Received: from UUNET.UU.NET by venera.isi.edu (5.61/5.61+local)
+
Received: from UUNET.UU.NET by venera.isi.edu (5.61/5.61+local)
          id <AA27149>; Wed, 7 Nov 90 14:34:34 -0800
+
        id <AA27149>; Wed, 7 Nov 90 14:34:34 -0800
  Received: from vitam6.UUCP by uunet.uu.net (5.61/1.14) with UUCP
+
Received: from vitam6.UUCP by uunet.uu.net (5.61/1.14) with UUCP
          id AA12926; Wed, 7 Nov 90 17:34:28 -0500
+
        id AA12926; Wed, 7 Nov 90 17:34:28 -0500
  Received: by vitam6.ENG.Vitalink.COM (5.61/1.35)
+
Received: by vitam6.ENG.Vitalink.COM (5.61/1.35)
          id AC03235; Wed, 7 Nov 90 13:54:08 -0800
+
        id AC03235; Wed, 7 Nov 90 13:54:08 -0800
  Date: Wed, 7 Nov 90 13:54:08 -0800
+
Date: Wed, 7 Nov 90 13:54:08 -0800
  From: [email protected] (Mail Delivery Subsystem)
+
From: [email protected] (Mail Delivery Subsystem)
  Subject: Returned mail: Host unknown
+
Subject: Returned mail: Host unknown
+
+
 
 
      ----- Transcript of session follows -----
 
 
 
  550 andrew_greenfield.safari@gatorcorp,
 
      [email protected] unknown
 
 
 
23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)~~
 
 
 
 
 
 
 
 
 
 
 
  
 +
  ----- Transcript of session follows -----
  
 +
550 andrew_greenfield.safari@gatorcorp,
 +
    [email protected] unknown
  
 
+
21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)~~
Westine & Postel                                             
 
 
 
RFC 1211              Problems with Mailing Lists            March 1991
 
 
 
  
 
D.2.  Message Sent to Postmaster
 
D.2.  Message Sent to Postmaster
  
+
+
  Subject: andrew_greenfield.safari@gatorcorp,
+
Subject: andrew_greenfield.safari@gatorcorp,
            melinda_le_baron.safari@gatorcorp... Host unknown
+
        melinda_le_baron.safari@gatorcorp... Host unknown
  Reply-To: [email protected]
+
  Date: Thu, 08 Nov 90 15:30:24 PST
+
Date: Thu, 08 Nov 90 15:30:24 PST
  From: Ann Westine <[email protected]>
+
From: Ann Westine <[email protected]>
  
  Hi,
+
Hi,
  
  We have an exploder mailbox on the IETF list called
+
We have an exploder mailbox on the IETF list called
  "[email protected]".  I'm not sure, but I think the
+
"[email protected]".  I'm not sure, but I think the
  following addresses may be on that list.  Please look into this
+
following addresses may be on that list.  Please look into this
  "host unknown" problem.  If these addresses need to be deleted,
+
"host unknown" problem.  If these addresses need to be deleted,
  please do so.
+
please do so.
  
  Thanks,
+
Thanks,
  Ann
+
Ann
  
 
************************************************************************
 
************************************************************************
  
 
+
                            APPENDIX E
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
Westine & Postel                                             
 
 
 
RFC 1211              Problems with Mailing Lists            March 1991
 
 
 
 
 
                              APPENDIX E
 
  
 
Every host on the Internet that processes mail is required to have a
 
Every host on the Internet that processes mail is required to have a
Line 629: Line 499:
 
E.1.  Message Sent to IETF-Request
 
E.1.  Message Sent to IETF-Request
  
  To:      ([email protected])
+
To:      ([email protected])
  From:    Caralyn Brown (CBROWN@ENR)
+
From:    Caralyn Brown (CBROWN@ENR)
  Date:    10 Jan 91  8:24 AM
+
Date:    10 Jan 91  8:24 AM
  Subject:  please remove me from this list
+
Subject:  please remove me from this list
  
  Please remove me from this list.  I'm changing companies and I'd like
+
Please remove me from this list.  I'm changing companies and I'd like
  to keep the mailbox from getting out of hand.  If it's not too much
+
to keep the mailbox from getting out of hand.  If it's not too much
  trouble, could you just send me a confirmation that I was deleted?
+
trouble, could you just send me a confirmation that I was deleted?
  Thanks.
+
Thanks.
  
  caralyn
+
caralyn
  
23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)~~
+
21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)~~
  
 
E.2.  Message Sent to Postmaster
 
E.2.  Message Sent to Postmaster
  
+
+
  Subject: Please delete from "[email protected]" - Carolyn Brown
+
Subject: Please delete from "[email protected]" - Carolyn Brown
  Reply-To: [email protected]
+
  Date: Thu, 10 Jan 91 09:50:15 PST
+
Date: Thu, 10 Jan 91 09:50:15 PST
  From: Ann Westine <[email protected]>
+
From: Ann Westine <[email protected]>
 
 
  Hi,
 
 
 
  Please delete Carolyn from your sublist.  We do not have her address
 
  listed individually on the main IETF list.
 
 
 
  Thanks, Ann
 
 
 
23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)~~
 
 
 
 
 
 
 
 
 
 
 
  
 +
Hi,
  
 +
Please delete Carolyn from your sublist.  We do not have her address
 +
listed individually on the main IETF list.
  
 +
Thanks, Ann
  
 
+
21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)~~
 
 
 
 
Westine & Postel                                             
 
 
 
RFC 1211              Problems with Mailing Lists            March 1991
 
 
 
  
 
E.3.  Error Report
 
E.3.  Error Report
  
  From: [email protected] (List Service version
+
From: [email protected] (List Service version
        1.0.x463)
+
      1.0.x463)
  Subject: returned mail
+
Subject: returned mail
  Message-Type: Return
+
Message-Type: Return
+
  
  Your mail addressed to "postmaster" could not be processed: There is
+
Your mail addressed to "postmaster" could not be processed: There is
  no mailing list named "postmaster" at this site.
+
no mailing list named "postmaster" at this site.
  
  For help, send to [email protected]; to receive an index of
+
For help, send to [email protected]; to receive an index of
  available lists, send to [email protected]; to reach a List
+
available lists, send to [email protected]; to reach a List
  Administrator, send to [email protected].
+
Administrator, send to [email protected].
  
 
************************************************************************
 
************************************************************************
  
 
+
             APPENDIX F - Examples of Error Messages
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
Westine & Postel                                             
 
 
 
RFC 1211             Problems with Mailing Lists            March 1991
 
 
 
 
 
                APPENDIX F - Examples of Error Messages
 
  
 
F.1. Delayed Delivery Notices
 
F.1. Delayed Delivery Notices
  
  From: [email protected] (Mail Delivery Subsystem)
+
From: [email protected] (Mail Delivery Subsystem)
  Subject: Returned mail: Deferred: Connection timed out during user
+
Subject: Returned mail: Deferred: Connection timed out during user
            open with uiucdcsm-uiuc-dcs-net.cs.uiuc.edu
+
        open with uiucdcsm-uiuc-dcs-net.cs.uiuc.edu
  Posted-Date: Fri, 4 Jan 91 12:46:51 -0800
+
Posted-Date: Fri, 4 Jan 91 12:46:51 -0800
  Received: by venera.isi.edu (5.61/5.61+local)
+
Received: by venera.isi.edu (5.61/5.61+local)
          id <AA08435>; Fri, 4 Jan 91 12:46:51 -0800
+
        id <AA08435>; Fri, 4 Jan 91 12:46:51 -0800
+
 
 
      ----- Transcript of session follows -----
 
  >>> RCPT To:<[email protected]>
 
  <<< 550 (USER) Unknown user name in "[email protected]"
 
  550 [email protected]... User unknown
 
  451 [email protected]... reply: read error
 
  [email protected]... reply: read error
 
  421 dockmaster.ncsc.mil.tcp... Deferred: Connection timed out during
 
      user open with DOCKMASTER.NCSC.MIL
 
  421 va.nkw.ac.uk.tcp... Deferred: Connection timed out during
 
      user open with nsfnet-relay.ac.uk
 
  421 nsl.dec.com.tcp... Deferred: Connection timed out during user
 
      open with jove.pa.dec.com
 
  451 [email protected]... timeout waiting for input
 
      [email protected]... timeout waiting for input
 
  451 [email protected]... reply: read error
 
      [email protected]... reply: read error
 
  421 sccgate.scc.com.tcp... Deferred: Connection timed out during
 
      user open with sccgate.scc.com
 
  421 a.isi.edu.tcp... Deferred: Connection refused by a.ISI.EDU
 
  421 cs.ucl.ac.uk.tcp... Deferred: Connection timed out during user
 
      open with nsfnet-relay.ac.uk
 
  421 oasys.dt.navy.mil.tcp... Deferred: Connection timed out during
 
      user open with oasys.dt.navy.mil
 
  421 peocu1.navy.mil.tcp... Deferred: Connection timed out during user
 
      open with PEOCU1.NAVY.MIL
 
  421 enh.nist.gov.tcp... Deferred: Connection timed out during user
 
      open with enh.nist.gov
 
  421 mickey.imsd.contel.com.tcp... Deferred: Connection refused by
 
      MICKEY.IMSD.CONTEL.COM
 
  421 uv4.eglin.af.mil.tcp..Deferred: Connection timed out during user
 
      open with uv6.eglin.af.mil
 
  421 ima.isc.com.tcp... Deferred: Connection timed out during user
 
      open with ima.ima.isc.com
 
  421 huachuca-emh8.army.mil.tcp... Deferred: Connection refused by
 
      HUACHUCA-EMH8.ARMY.MIL
 
  421 vaxa.nerc-keyworth.ac.uk.tcp... Deferred: Connection timed out
 
  
 +
  ----- Transcript of session follows -----
 +
>>> RCPT To:<[email protected]>
 +
<<< 550 (USER) Unknown user name in "[email protected]"
 +
550 [email protected]... User unknown
 +
451 [email protected]... reply: read error
 +
[email protected]... reply: read error
 +
421 dockmaster.ncsc.mil.tcp... Deferred: Connection timed out during
 +
    user open with DOCKMASTER.NCSC.MIL
 +
421 va.nkw.ac.uk.tcp... Deferred: Connection timed out during
 +
    user open with nsfnet-relay.ac.uk
 +
421 nsl.dec.com.tcp... Deferred: Connection timed out during user
 +
    open with jove.pa.dec.com
 +
451 [email protected]... timeout waiting for input
 +
    [email protected]... timeout waiting for input
 +
451 [email protected]... reply: read error
 +
    [email protected]... reply: read error
 +
421 sccgate.scc.com.tcp... Deferred: Connection timed out during
 +
    user open with sccgate.scc.com
 +
421 a.isi.edu.tcp... Deferred: Connection refused by a.ISI.EDU
 +
421 cs.ucl.ac.uk.tcp... Deferred: Connection timed out during user
 +
    open with nsfnet-relay.ac.uk
 +
421 oasys.dt.navy.mil.tcp... Deferred: Connection timed out during
 +
    user open with oasys.dt.navy.mil
 +
421 peocu1.navy.mil.tcp... Deferred: Connection timed out during user
 +
    open with PEOCU1.NAVY.MIL
 +
421 enh.nist.gov.tcp... Deferred: Connection timed out during user
 +
    open with enh.nist.gov
 +
421 mickey.imsd.contel.com.tcp... Deferred: Connection refused by
 +
    MICKEY.IMSD.CONTEL.COM
 +
421 uv4.eglin.af.mil.tcp..Deferred: Connection timed out during user
 +
    open with uv6.eglin.af.mil
 +
421 ima.isc.com.tcp... Deferred: Connection timed out during user
 +
    open with ima.ima.isc.com
 +
421 huachuca-emh8.army.mil.tcp... Deferred: Connection refused by
 +
    HUACHUCA-EMH8.ARMY.MIL
 +
421 vaxa.nerc-keyworth.ac.uk.tcp... Deferred: Connection timed out
  
 +
    during user open with nsfnet-relay.ac.uk
 +
421 gdr.bath.ac.uk.tcp... Deferred: Connection timed out during user
 +
    open with nsfnet-relay.ac.uk
 +
421 ccint1.rsre.mod.uk.tcp... Deferred: Connection timed out during
 +
    user open with ccint1.rsre.mod.uk
 +
550 [email protected]... Host unknown
 +
421 hqafsc-vax.af.mil.tcp... Deferred: Connection timed out during
 +
    user open with HQAFSC-VAX.AF.MIL
 +
421 nic.nordu.net.tcp... Deferred: Connection timed out during user
 +
    open with nic.nordu.net
 +
421 aedc-vax.af.mil.tcp... Deferred: Connection timed out during user
 +
    open with AEDC-VAX.AF.MIL
 +
421 letterkenn-emh1.army.mil.tcp... Deferred: Connection timed out
 +
    during user open with LETTERKENN-EMH1.ARMY.MIL
 +
421 dumle.kommhuset.se.tcp... Deferred: Connection timed out during
 +
    user open with sunic.sunet.se
 +
421 cis.uab.edu.tcp... Deferred: Connection timed out during user
 +
    open with cisa.CIS.UAB.EDU
 +
421 server.af.mil.tcp... Deferred: Connection timed out during user
 +
    open with server.af.mil
 +
421 issun3.stc.nl.tcp... Deferred: Connection timed out during user
 +
    open with issun3.stc.nl
 +
421 cs.uiuc.edu.tcp... Deferred: Connection timed out during user
 +
    open with uiucdcsm-uiuc-dcs-net.cs.uiuc.edu
  
Westine & Postel                                             
+
          -------------
 
 
RFC 1211              Problems with Mailing Lists            March 1991
 
 
 
 
 
      during user open with nsfnet-relay.ac.uk
 
  421 gdr.bath.ac.uk.tcp... Deferred: Connection timed out during user
 
      open with nsfnet-relay.ac.uk
 
  421 ccint1.rsre.mod.uk.tcp... Deferred: Connection timed out during
 
      user open with ccint1.rsre.mod.uk
 
  550 [email protected]... Host unknown
 
  421 hqafsc-vax.af.mil.tcp... Deferred: Connection timed out during
 
      user open with HQAFSC-VAX.AF.MIL
 
  421 nic.nordu.net.tcp... Deferred: Connection timed out during user
 
      open with nic.nordu.net
 
  421 aedc-vax.af.mil.tcp... Deferred: Connection timed out during user
 
      open with AEDC-VAX.AF.MIL
 
  421 letterkenn-emh1.army.mil.tcp... Deferred: Connection timed out
 
      during user open with LETTERKENN-EMH1.ARMY.MIL
 
  421 dumle.kommhuset.se.tcp... Deferred: Connection timed out during
 
      user open with sunic.sunet.se
 
  421 cis.uab.edu.tcp... Deferred: Connection timed out during user
 
      open with cisa.CIS.UAB.EDU
 
  421 server.af.mil.tcp... Deferred: Connection timed out during user
 
      open with server.af.mil
 
  421 issun3.stc.nl.tcp... Deferred: Connection timed out during user
 
      open with issun3.stc.nl
 
  421 cs.uiuc.edu.tcp... Deferred: Connection timed out during user
 
      open with uiucdcsm-uiuc-dcs-net.cs.uiuc.edu
 
 
 
              -------------
 
 
************************************************************************
 
************************************************************************
  
 
F.2. Failed Mail
 
F.2. Failed Mail
  
  Date:    Tue, 30 Oct 90 5:00:40 EST
+
Date:    Tue, 30 Oct 90 5:00:40 EST
  From: BBN Mail System (MMDF) <[email protected]>
+
From: BBN Mail System (MMDF) <[email protected]>
+
  Subject:  Failed mail  (msg.aa09055)
+
Subject:  Failed mail  (msg.aa09055)
+
  
  After 12 days (276 hours), your message could not be fully delivered.
+
After 12 days (276 hours), your message could not be fully delivered.
  
  It failed to be received by the following address(es):
+
It failed to be received by the following address(es):
  
      [email protected] (host: cc5.bbn.com) (queue: smtp)
+
    [email protected] (host: cc5.bbn.com) (queue: smtp)
  
  Problems usually are due to service interruptions at the receiving
+
Problems usually are due to service interruptions at the receiving
  machine.  Less often, they are caused by the communication system.
+
machine.  Less often, they are caused by the communication system.
  
 
************************************************************************
 
************************************************************************
 
 
 
 
 
Westine & Postel                                             
 
 
RFC 1211              Problems with Mailing Lists            March 1991
 
 
  
 
F.3.  Waiting Mail
 
F.3.  Waiting Mail
  
  To: RELAY Mail System (MMDF) <[email protected]>
+
To: RELAY Mail System (MMDF) <[email protected]>
  Cc: owner-ietf <@RELAY.CS.NET:[email protected]>
+
Cc: owner-ietf <@RELAY.CS.NET:[email protected]>
  Reply-To: [email protected]
+
  Subject: Re: Waiting mail (msg.aa00720)
+
Subject: Re: Waiting mail (msg.aa00720)
  In-Reply-To: Your message of Tue, 02 Oct 90 07:45:14 -0400.
+
In-Reply-To: Your message of Tue, 02 Oct 90 07:45:14 -0400.
                <[email protected]>
+
            <[email protected]>
  Date: Mon, 08 Oct 90 10:11:03 PDT
+
Date: Mon, 08 Oct 90 10:11:03 PDT
  From: Ann Westine <[email protected]>
+
From: Ann Westine <[email protected]>
  
  > After 5 days (105 hours), your message has not yet been
+
> After 5 days (105 hours), your message has not yet been
  > fully delivered.  Attempts to deliver the message will continue
+
> fully delivered.  Attempts to deliver the message will continue
  > for 2 more days.  No further action is required by you.
+
> for 2 more days.  No further action is required by you.
  >
+
>
  > Delivery attempts are still pending for the following address(es):
+
> Delivery attempts are still pending for the following address(es):
  >
+
>
  >      @zix.gmd.dbp.de:[email protected]
+
>      @zix.gmd.dbp.de:[email protected]
  >      (host: zix.gmd.dbp.de)(queue: dfn)
+
>      (host: zix.gmd.dbp.de)(queue: dfn)
  >
+
>
  > Problems usually are due to service interruptions at the receiving
+
> Problems usually are due to service interruptions at the receiving
  > machine.  Less often, they are caused by the communication system.
+
> machine.  Less often, they are caused by the communication system.
  
 
************************************************************************
 
************************************************************************
Line 872: Line 671:
 
F.4.  What Started Out as a Sublist with No Active Users
 
F.4.  What Started Out as a Sublist with No Active Users
  
  a.  Error Report
+
a.  Error Report
 
 
  Date: Tue, 4 Sep 90 22:13:12 +0200
 
  From: [email protected] (Mail Delivery Subsystem)
 
  Subject: Returned mail: User unknown
 
  To: owner-ietf
 
 
 
      ----- Transcript of session follows -----
 
  While talking to mailhost.Gipsi.FR:
 
  >>> RCPT To:<[email protected]>
 
  <<< 550 <[email protected]>... User unknown
 
  550 <[email protected]>... User unknown
 
  
              ----------
+
Date: Tue, 4 Sep 90 22:13:12 +0200
 +
From: MAILER-[email protected] (Mail Delivery Subsystem)
 +
Subject: Returned mail: User unknown
 +
To: owner-ietf
  
23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)~~
+
  ----- Transcript of session follows -----
 +
While talking to mailhost.Gipsi.FR:
 +
>>> RCPT To:<[email protected]>
 +
<<< 550 <[email protected]>... User unknown
 +
550 <[email protected]>... User unknown
  
 +
          ----------
  
 +
21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)~~
  
 +
b.  Message Sent to Postmaster
  
 +
 +
Subject: 550 <[email protected]>... User unknown
 +
 +
Date: Tue, 11 Sep 90 09:56:20 PDT
 +
From: Ann Westine <[email protected]>
  
 +
Hi,
  
 +
I have received numerous error messages like this for over a week.
 +
There appears to be a mailbox on your exploder that is invalid,
 +
please delete it.
  
 +
Thanks, --Ann
  
Westine & Postel                                             
+
21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)~~
  
RFC 1211              Problems with Mailing Lists            March 1991
+
c.  Reply From Postmaster
  
 +
From: [email protected] (Edmonde Duteurtre)
 +
To: westine
 +
In-Reply-To: Ann Westine's message of Tue,
 +
            11 Sep 90 09:56:20 PDT
 +
 +
Subject: 550 <[email protected]>... User unknown
  
  b.  Message Sent to Postmaster
+
Hello
  
  TO:  Postmaster@gisi.gipsi.fr
+
On our site, the bind@gipsi.fr, snmp@gipsi.fr, ietf@gipsi.fr and the
  Subject: 550 <ietf@GIPSI.FR>... User unknown
+
nameddroppers@gipsi.fr mailed only one person: prindevi@gipsi.fr but
  Reply-To: westine@isi.edu
+
this person has leaved our company, and you should cancel this
  Date: Tue, 11 Sep 90 09:56:20 PDT
+
addresses.
  From: Ann Westine <[email protected].edu>
 
  
  Hi,
+
I think we get enough informations through the news.  I think you
 
+
should cancel us ([email protected]) on the mailing list ietf.
  I have received numerous error messages like this for over a week.
 
  There appears to be a mailbox on your exploder that is invalid,
 
  please delete it.
 
 
 
  Thanks, --Ann
 
 
 
23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)~~
 
 
 
  c.  Reply From Postmaster
 
 
 
  From: [email protected] (Edmonde Duteurtre)
 
  To: westine
 
  In-Reply-To: Ann Westine's message of Tue,
 
                11 Sep 90 09:56:20 PDT
 
 
  Subject: 550 <[email protected]>... User unknown
 
 
 
  Hello
 
 
 
 
  [email protected] mailed only one person: [email protected] but
 
  this person has leaved our company, and you should cancel this
 
  addresses.
 
 
 
  I think we get enough informations through the news.  I think you
 
  should cancel us ([email protected]) on the mailing list ietf.
 
  
 
************************************************************************
 
************************************************************************
 
 
 
 
 
 
 
 
 
 
 
 
 
Westine & Postel                                             
 
 
RFC 1211              Problems with Mailing Lists            March 1991
 
 
  
 
F.5.  Sublists without local ownership
 
F.5.  Sublists without local ownership
  
  In this error message there was not much to go on except the
+
In this error message there was not much to go on except the
  words IETF and the name of the host from where the mailer-daemon
+
words IETF and the name of the host from where the mailer-daemon
  sent the error.  Using that clue the mailing list was searched for
+
sent the error.  Using that clue the mailing list was searched for
  that host name (SATURN).  It was a sublist. It appears that there is
+
that host name (SATURN).  It was a sublist. It appears that there is
  something internally wrong with the sublist and this error should
+
something internally wrong with the sublist and this error should
  have gone to the postmaster or owner of the [email protected] list
+
have gone to the postmaster or owner of the [email protected] list
  instead of the IETF owner.  A message was sent to the postmaster.  No
+
instead of the IETF owner.  A message was sent to the postmaster.  No
  reply was received, but the condition was fixed.
+
reply was received, but the condition was fixed.
 
 
23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)~~
 
  
  a.  Error Report
+
21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)~~
  
  Date: Wed, 3 Oct 90 14:42:57 EDT
+
a. Error Report
  From: MAILER-DAEMON%saturn.[email protected] (Mail Delivery
 
                                                    Subsystem)
 
  Subject: Returned mail: unknown mailer error 13
 
 
  
      ----- Transcript of session follows -----
+
Date: Wed, 3 Oct 90 14:42:57 EDT
  /p/news/ietf/21770: Permission denied
+
From: MAILER-DAEMON%saturn.ACC.COM@salt.acc.com (Mail Delivery
  554 "| /usr/local/news -s ietf"... unknown mailer error 13
+
                                                Subsystem)
 +
Subject: Returned mail: unknown mailer error 13
 +
  
 +
  ----- Transcript of session follows -----
 +
/p/news/ietf/21770: Permission denied
 +
554 "| /usr/local/news -s ietf"... unknown mailer error 13
  
23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)~~
+
21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)~~
  
  b. Message Sent to Postmaster
+
b. Message Sent to Postmaster
  
+
  cc: ietf-request
+
cc: ietf-request
  Reply-To: [email protected]
+
  Subject: 554 "| /usr/local/news -s ietf"
+
Subject: 554 "| /usr/local/news -s ietf"
      ... unknown mailer error 13
+
    ... unknown mailer error 13
  In-reply-to: Your message of Wed, 03 Oct 90 14:42:57 -0400.
+
In-reply-to: Your message of Wed, 03 Oct 90 14:42:57 -0400.
        <[email protected]>
+
  Date: Mon, 08 Oct 90 10:53:02 PDT
+
Date: Mon, 08 Oct 90 10:53:02 PDT
  From: Ann Westine <[email protected]>
+
From: Ann Westine <[email protected]>
  
  Hi,
+
Hi,
  
  Please fix the problem with the following mailbox
+
Please fix the problem with the following mailbox
+
  
  Thanks, Ann
+
Thanks, Ann
  
 
************************************************************************
 
************************************************************************
 
 
 
Westine & Postel                                             
 
 
RFC 1211              Problems with Mailing Lists            March 1991
 
 
  
 
F.6.  Repetitive Error Every Couple of Months from Same Host
 
F.6.  Repetitive Error Every Couple of Months from Same Host
  
  a.  Message Dated August 90
+
a.  Message Dated August 90
  
  Date: Tue, 21 Aug 90 09:21:26 -0700
+
Date: Tue, 21 Aug 90 09:21:26 -0700
  From: [email protected] (Mail Delivery Subsystem)
+
From: [email protected] (Mail Delivery Subsystem)
  Subject: Returned mail: Host unknown
+
Subject: Returned mail: Host unknown
  To: <@decpa.pa.dec.com:[email protected]>
+
To: <@decpa.pa.dec.com:[email protected]>
  
      ----- Transcript of session follows -----
+
  ----- Transcript of session follows -----
  mail11: connect: Connect failed, Unrecognized object
+
mail11: connect: Connect failed, Unrecognized object
  (permanent failure)
+
(permanent failure)
  
  554 <netrix::gillin>... 550 Host unknown (Authoritative
+
554 <netrix::gillin>... 550 Host unknown (Authoritative
    answer from name server)
+
  answer from name server)
  
      ----- Recipients of this delivery -----
+
  ----- Recipients of this delivery -----
  <erlang::chiu> (sent)
+
<erlang::chiu> (sent)
  <netrix::gillin> (bounced)
+
<netrix::gillin> (bounced)
  <erlang::rama> (sent)
+
<erlang::rama> (sent)
  
23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)~~
+
21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)~~
  
  b.  Message Dated October 90
+
b.  Message Dated October 90
  
  Date: Mon, 29 Oct 90 05:02:53 -0800
+
Date: Mon, 29 Oct 90 05:02:53 -0800
  From: [email protected] (Mail Delivery Subsystem)
+
From: [email protected] (Mail Delivery Subsystem)
  Subject: Returned mail: Host unknown
+
Subject: Returned mail: Host unknown
  To: <@decpa.pa.dec.com:[email protected]>
+
To: <@decpa.pa.dec.com:[email protected]>
  
      ----- Transcript of session follows -----
+
  ----- Transcript of session follows -----
  mail11: Error from DECnet MAIL object on node "erlang",
+
mail11: Error from DECnet MAIL object on node "erlang",
          during mail delivery to <ERLANG::CHIU>.
+
        during mail delivery to <ERLANG::CHIU>.
          Remote error code is 0x7e803a, message is:
+
        Remote error code is 0x7e803a, message is:
  %MAIL-E-LOGLINK, error creating network link to node CHIU
+
%MAIL-E-LOGLINK, error creating network link to node CHIU
  -SYSTEM-F-NOSUCHNODE, remote node is unknown
+
-SYSTEM-F-NOSUCHNODE, remote node is unknown
  554 <erlang::chiu>... 550 Host unknown (Authoritative
+
554 <erlang::chiu>... 550 Host unknown (Authoritative
    answer from name server)
+
  answer from name server)
 
 
      ----- Recipients of this delivery -----
 
  <erlang::chiu> (bounced)
 
  <netrix::gillin> (sent)
 
  <erlang::rama> (sent)
 
 
 
23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)~~
 
 
 
 
 
 
 
 
 
 
 
 
 
Westine & Postel                                             
 
 
 
RFC 1211              Problems with Mailing Lists            March 1991
 
 
 
 
 
  c.  Message Dated December 90
 
 
 
  Date: Sun, 16 Dec 90 21:40:47 -0800
 
  From: [email protected] (Mail Delivery Subsystem)
 
  Subject: Returned mail: Host unknown
 
 
 
 
 
 
      ----- Transcript of session follows -----
 
  mail11: connect: Connect failed, Unrecognized object
 
  (permanent failure)
 
 
 
  554 <[email protected]>... 550 Host unknown (Authoritative
 
  answer from name server)
 
 
 
      ----- Recipients of this delivery -----
 
  
   <[email protected]> (bounced)
+
   ----- Recipients of this delivery -----
 +
<erlang::chiu> (bounced)
 +
<netrix::gillin> (sent)
 +
<erlang::rama> (sent)
  
23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)~~
+
21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)~~
  
  d.  Message Dated December 90
+
c.  Message Dated December 90
  
  Date: Sun, 16 Dec 90 23:01:21 -0800
+
Date: Sun, 16 Dec 90 21:40:47 -0800
  From: [email protected] (Mail Delivery Subsystem)
+
From: [email protected] (Mail Delivery Subsystem)
  Subject: Returned mail: Host unknown
+
Subject: Returned mail: Host unknown
+
  
      ----- Transcript of session follows -----
+
  ----- Transcript of session follows -----
  mail11: connect: Connect failed, Unrecognized object
+
mail11: connect: Connect failed, Unrecognized object
  (permanent failure)
+
(permanent failure)
  
  554 <gillin%netrix.DEC@DECWRL.DEC.COM>... 550 Host unknown
+
554 <bansal@NETRIX.ENET.DEC.COM>... 550 Host unknown (Authoritative
  (Authoritative answer from name server)
+
answer from name server)
  
      ----- Recipients of this delivery -----
+
  ----- Recipients of this delivery -----
  
  <mogul@DECWRL.DEC.COM> (sent)
+
<bansal@NETRIX.ENET.DEC.COM> (bounced)
  mogul@acetes (sent)
 
  <gillin%netrix.DEC@DECWRL.DEC.COM> (bounced)
 
  <chiu%[email protected]> (sent)
 
  
23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)~~
+
21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)~~
  
 +
d.  Message Dated December 90
  
 +
Date: Sun, 16 Dec 90 23:01:21 -0800
 +
From: [email protected] (Mail Delivery Subsystem)
 +
Subject: Returned mail: Host unknown
 +
  
 +
  ----- Transcript of session follows -----
 +
mail11: connect: Connect failed, Unrecognized object
 +
(permanent failure)
  
 +
554 <gillin%[email protected]>... 550 Host unknown
 +
(Authoritative answer from name server)
  
 +
  ----- Recipients of this delivery -----
  
 +
 +
mogul@acetes (sent)
 +
<gillin%[email protected]> (bounced)
 +
<chiu%[email protected]> (sent)
  
 +
21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)~~
  
Westine & Postel                                             
+
e.  Message Dated January 91
  
RFC 1211              Problems with Mailing Lists            March 1991
+
Date: Sun, 6 Jan 91 17:05:53 -0800
 
+
From: [email protected] (Mail Delivery Subsystem)
 
+
Subject: Returned mail: User unknown
  e.  Message Dated January 91
+
 
 
  Date: Sun, 6 Jan 91 17:05:53 -0800
 
  From: [email protected] (Mail Delivery Subsystem)
 
  Subject: Returned mail: User unknown
 
 
  
      ----- Transcript of session follows -----
+
  ----- Transcript of session follows -----
  mail11: Error from DECnet MAIL object on node "bigfut",
+
mail11: Error from DECnet MAIL object on node "bigfut",
    during mail delivery to <BIGFUT::CALLON>.
+
  during mail delivery to <BIGFUT::CALLON>.
    Remote error code is 0x7e81fa, message is:(can't decypher error
+
  Remote error code is 0x7e81fa, message is:(can't decypher error
    code)
+
  code)
  550 <[email protected]>... User unknown
+
550 <[email protected]>... User unknown
  
 
************************************************************************
 
************************************************************************
Line 1,143: Line 882:
 
F.7.  Host Unknown or Sublist
 
F.7.  Host Unknown or Sublist
  
  The address "lucb-ml@OPUS" is not an Internet style domain name. The
+
The address "lucb-ml@OPUS" is not an Internet style domain name. The
  exploder [email protected] has this address on its sublist, and
+
exploder [email protected] has this address on its sublist, and
  CSA.McGILL.CA does not recognize this host.  (This error should have
+
CSA.McGILL.CA does not recognize this host.  (This error should have
  gone to the sublist owner at CS.MCGILL.CA).
+
gone to the sublist owner at CS.MCGILL.CA).
  
  Date: Tue, 9 Oct 90 19:45:14 -0400
+
Date: Tue, 9 Oct 90 19:45:14 -0400
  From: Mail Delivery Subsystem  <[email protected]>
+
From: Mail Delivery Subsystem  <[email protected]>
  Subject: Returned mail: Host unknown
+
Subject: Returned mail: Host unknown
+
  
      ----- Transcript of session follows -----
+
  ----- Transcript of session follows -----
  550 "Luc Boulianne"    <lucb-ml@opus>... Host unknown
+
550 "Luc Boulianne"    <lucb-ml@opus>... Host unknown
  
 
************************************************************************
 
************************************************************************
Line 1,160: Line 899:
 
F.8.  "HOST UNKNOWN" and the Host Really Is Known
 
F.8.  "HOST UNKNOWN" and the Host Really Is Known
  
  Usually a "host unknown" report is not acted on unless it is repeated
+
Usually a "host unknown" report is not acted on unless it is repeated
  over a period of several days.  In many cases the hosts really do
+
over a period of several days.  In many cases the hosts really do
  exist, but they're just down for a couple of days, or there are
+
exist, but they're just down for a couple of days, or there are
  network problems reaching it (or it's name serrver).
+
network problems reaching it (or it's name serrver).
 
 
  Date: Fri, 2 Nov 90 08:45:56 -0800
 
  From: [email protected] (Mail Delivery Subsystem)
 
  Subject: Returned mail: Host unknown
 
 
  
          ----- Transcript of session follows -----
+
Date: Fri, 2 Nov 90 08:45:56 -0800
    550 nrc.com.tcp... 550 Host unknown
+
From: MAILER-[email protected] (Mail Delivery Subsystem)
    550 IHM@NRC.COM... Host unknown
+
Subject: Returned mail: Host unknown
 +
To: owner-los-nettos@ISI.EDU
  
 +
        ----- Transcript of session follows -----
 +
  550 nrc.com.tcp... 550 Host unknown
 +
  550 [email protected]... Host unknown
  
 +
21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)~~
  
Westine & Postel                                             
+
WHATHOST CHECK
  
RFC 1211              Problems with Mailing Lists            March 1991
+
        westine 28%  whathost nrc.com
 +
        Host: nrc.com  ==>  129.216.200.51
  
 
+
        westine 82% whathost 129.216.200.51
23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)~~
+
        Host: aztec.NRC.COM  ==>  129.216.200.51
 
 
  WHATHOST CHECK
 
 
 
          westine 28%  whathost nrc.com
 
          Host: nrc.com  ==>  129.216.200.51
 
 
 
          westine 82% whathost 129.216.200.51
 
          Host: aztec.NRC.COM  ==>  129.216.200.51
 
  
 
************************************************************************
 
************************************************************************
Line 1,195: Line 927:
 
F.9.  Host Unknown and MXed to Another Host.
 
F.9.  Host Unknown and MXed to Another Host.
  
  DNS says AMES will forward mail for ADAPT, but mailer at AMES says
+
DNS says AMES will forward mail for ADAPT, but mailer at AMES says
  ADAPT is unknown.  Should ask postmaster at AMES to fix either mailer
+
ADAPT is unknown.  Should ask postmaster at AMES to fix either mailer
  or DNS data.
+
or DNS data.
  
  Date: Wed, 31 Oct 90 09:39:35 PST
+
Date: Wed, 31 Oct 90 09:39:35 PST
+
  Subject: Returned mail: Host unknown
+
Subject: Returned mail: Host unknown
+
  
      ----- Transcript of session follows -----
+
  ----- Transcript of session follows -----
  bad system name: ADAPT
+
bad system name: ADAPT
  uux failed ( 68 )
+
uux failed ( 68 )
  550 [email protected]... Host unknown
+
550 [email protected]... Host unknown
  
23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)~~
+
21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)~~
  
  westine 86% dig adapt.net.com any
+
westine 86% dig adapt.net.com any
  
  ; <<>> DiG <<>> adapt.net.com any
+
; <<>> DiG <<>> adapt.net.com any
  ;; ->>HEADER<<- opcode: QUERY , status: NOERROR, id: 6
+
;; ->>HEADER<<- opcode: QUERY , status: NOERROR, id: 6
  ;; flags: qr aa rd ra  Ques: 1, Ans: 2, Auth: 0, Addit: 2
+
;; flags: qr aa rd ra  Ques: 1, Ans: 2, Auth: 0, Addit: 2
  
  ;; QUESTIONS:
+
;; QUESTIONS:
  ;;      adapt.net.com, type = ANY, class = IN
+
;;      adapt.net.com, type = ANY, class = IN
  
  ;; ANSWERS:
+
;; ANSWERS:
  adapt.net.com  IN  MX  10 ames.arc.nasa.gov  ; 84029
+
adapt.net.com  IN  MX  10 ames.arc.nasa.gov  ; 84029
  adapt.net.com  IN  MX  20 tymix.tymnet.com    ; 84029
+
adapt.net.com  IN  MX  20 tymix.tymnet.com    ; 84029
  
  ;; ADDITIONAL RECORDS:
+
;; ADDITIONAL RECORDS:
  ames.arc.nasa.gov      IN  A  128.102.18.3  ; 158777
+
ames.arc.nasa.gov      IN  A  128.102.18.3  ; 158777
  tymix.tymnet.com        IN  A  131.146.2.1    ; 86400
+
tymix.tymnet.com        IN  A  131.146.2.1    ; 86400
  
 
************************************************************************
 
************************************************************************
 
 
 
Westine & Postel                                             
 
 
RFC 1211              Problems with Mailing Lists            March 1991
 
 
  
 
F.10.  User Unknown
 
F.10.  User Unknown
  
  Most "User Unknown" error messages listed individually on the main
+
Most "User Unknown" error messages listed individually on the main
  list get deleted.  Those on a sublist, require a message to the
+
list get deleted.  Those on a sublist, require a message to the
  postmaster or list maintainer.  They are asked to delete the
+
postmaster or list maintainer.  They are asked to delete the
  invalid user mailbox from their local list.
+
invalid user mailbox from their local list.
  
 
************************************************************************
 
************************************************************************
Line 1,248: Line 973:
 
F.10.1.  Add User but Address Fails
 
F.10.1.  Add User but Address Fails
  
  This is a case where the recipient was checking to see if his mailbox
+
This is a case where the recipient was checking to see if his mailbox
  was already on the list and if not to readd him.  He was readded to
+
was already on the list and if not to readd him.  He was readded to
  the list.  A "user unknown" error message was received on the
+
the list.  A "user unknown" error message was received on the
  confirming message that was sent notifying recipient that he had been
+
confirming message that was sent notifying recipient that he had been
  added.
+
added.
 
 
23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)~~
 
 
 
  a.  Message Sent to User And Postmaster
 
 
 
 
  Cc: westine, [email protected]
 
  Subject: RE: <[email protected]>
 
  Date: Wed, 07 Nov 90 10:15:40 PST
 
  From: Ann Westine <[email protected]>
 
 
 
  Hi Stewart and Postmaster,
 
 
 
  I readded your name to the IETF list but there seems to be problems
 
  with connections to DECnet hosts right now.  I have seen lots of
 
  errors like this lately.  Postmaster, please check into this.  JANUS
 
  is not the only host with an error, there are other hosts like this
 
  in trouble.
 
 
 
  For example.
 
 
 
      From: [email protected] (Mail Delivery Subsystem)
 
      Subject: Returned mail: Host unknown
 
      To: <@decpa.pa.dec.com:[email protected]>
 
 
 
          ----- Transcript of session follows -----
 
      mail11: Error from DECnet MAIL object on node "erlang",
 
                during mail delivery to <ERLANG::CHIU>.
 
                Remote error code is 0x7e803a, message is:
 
      %MAIL-E-LOGLINK, error creating network link to node CHIU
 
      -SYSTEM-F-NOSUCHNODE, remote node is unknown
 
      554 <erlang::chiu>... 550 Host unknown (Authoritative answer
 
 
 
 
 
 
 
Westine & Postel                                             
 
  
RFC 1211              Problems with Mailing Lists            March 1991
+
21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)~~
  
 +
a.  Message Sent to User And Postmaster
  
              from name server)
+
 +
Cc: westine, [email protected]
 +
Subject: RE: <[email protected]>
 +
Date: Wed, 07 Nov 90 10:15:40 PST
 +
From: Ann Westine <[email protected]>
  
          ----- Recipients of this delivery -----
+
Hi Stewart and Postmaster,
        <erlang::chiu> (bounced)
 
        <netrix::gillin> (sent)
 
        <erlang::rama> (sent)
 
                -------
 
      Thank you, Ann
 
  
            To: "Stewart Bryant, RE02-G/H2,
+
I readded your name to the IETF list but there seems to be problems
                DTN: 830 4682" <bryant@janus.enet.dec.com>
+
with connections to DECnet hosts right now. I have seen lots of
            Cc: ietf-request@ISI.EDU
+
errors like this lately. Postmaster, please check into this. JANUS
            Subject: Re: dist list
+
is not the only host with an error, there are other hosts like this
            In-Reply-To: Your message of Tue, 06 Nov 90 03:02:09 0800.
+
in trouble.
                      <[email protected].com>
 
            Date: Tue, 06 Nov 90 13:54:23 PST
 
            From: Ann Westine <westine@ISI.EDU>
 
  
            Hi Stewart,
+
For example.
  
            > Please will you check that I have not been deleted
+
    From: [email protected].com (Mail Delivery Subsystem)
            > from this distribution list.
+
    Subject: Returned mail: Host unknown
            >
+
    To: <@decpa.pa.dec.com:[email protected]>
            > My email address is > bryant@janus.enet.dec.com
 
  
        I readded you to the list. Thanks, Ann
+
        ----- Transcript of session follows -----
 +
    mail11: Error from DECnet MAIL object on node "erlang",
 +
            during mail delivery to <ERLANG::CHIU>.
 +
            Remote error code is 0x7e803a, message is:
 +
    %MAIL-E-LOGLINK, error creating network link to node CHIU
 +
    -SYSTEM-F-NOSUCHNODE, remote node is unknown
 +
    554 <erlang::chiu>... 550 Host unknown (Authoritative answer
  
            ------- Forwarded Message
+
          from name server)
  
            Date:   Tue, 06 Nov 90 17:25:15 -0800
+
        ----- Recipients of this delivery -----
            From:   [email protected]
+
    <erlang::chiu> (bounced)
            To:     [email protected]
+
    <netrix::gillin> (sent)
            Subject: Returned mail: User unknown
+
     <erlang::rama> (sent)
 +
            -------
 +
    Thank you, Ann
  
              ----- Transcript of session follows -----
+
        To: "Stewart Bryant, RE02-G/H2,
 +
            DTN: 830 4682" <[email protected]>
 +
        Cc: ietf-[email protected]
 +
        Subject: Re: dist list
 +
        In-Reply-To: Your message of Tue, 06 Nov 90 03:02:09 0800.
 +
                    <[email protected]>
 +
        Date: Tue, 06 Nov 90 13:54:23 PST
 +
        From: Ann Westine <[email protected]>
  
            mail11: Error from DECnet MAIL object on node "janus",
+
        Hi Stewart,
                    during mail delivery to <JANUS::BRYANT>.
 
                    Remote error code is 0x7e81d2, message is:
 
            %MAIL-E-ERRACTRNS, error activating transport NM
 
                    (can't decypher error code)
 
              550 <[email protected]>... User unknown
 
  
                ----- Recipients of this delivery -----
+
        > Please will you check that I have not been deleted
            <[email protected]> (bounced)
+
        > from this distribution list.
 +
        >
 +
        > My email address is > [email protected]
  
23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)~~
+
      I readded you to the list.  Thanks, Ann
  
 +
        ------- Forwarded Message
  
 +
        Date:    Tue, 06 Nov 90 17:25:15 -0800
 +
        From:    [email protected]
 +
        To:      [email protected]
 +
        Subject: Returned mail: User unknown
  
 +
            ----- Transcript of session follows -----
  
Westine & Postel                                             
+
        mail11: Error from DECnet MAIL object on node "janus",
 +
                during mail delivery to <JANUS::BRYANT>.
 +
                Remote error code is 0x7e81d2, message is:
 +
        %MAIL-E-ERRACTRNS, error activating transport NM
 +
                (can't decypher error code)
 +
            550 <[email protected]>... User unknown
  
RFC 1211             Problems with Mailing Lists            March 1991
+
             ----- Recipients of this delivery -----
 +
        <[email protected]> (bounced)
  
 +
21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)~~
  
 
b.  Message From Postmaster
 
b.  Message From Postmaster
  
  Return-path: [email protected]
+
Return-path: [email protected]
  Date:    Wed, 07 Nov 90 16:24:37 PST
+
Date:    Wed, 07 Nov 90 16:24:37 PST
  To:      [email protected]
+
To:      [email protected]
+
            [email protected]
+
        [email protected]
  Subject: Re: <[email protected]>
+
Subject: Re: <[email protected]>
  From:    Paul A Vixie <[email protected]>
+
From:    Paul A Vixie <[email protected]>
  
  Anne,
+
Anne,
  
  This was a transient.  Please let me know if any other .enet.dec.com
+
This was a transient.  Please let me know if any other .enet.dec.com
  nodes are still unreachable.
+
nodes are still unreachable.
  
  Paul
+
Paul
  
23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)~~
+
21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)~~
  
 
c.  Another Message to Postmaster
 
c.  Another Message to Postmaster
  
  To: Paul A Vixie <[email protected]>
+
To: Paul A Vixie <[email protected]>
+
+
  Reply-To: [email protected]
+
  Subject: Re: <[email protected]>
+
Subject: Re: <[email protected]>
  In-reply-to: Your message of Wed, 07 Nov 90 16:24:37 -0800.
+
In-reply-to: Your message of Wed, 07 Nov 90 16:24:37 -0800.
+
  Date: Thu, 08 Nov 90 11:23:39 PST
+
Date: Thu, 08 Nov 90 11:23:39 PST
  From: Ann Westine <[email protected]>
+
From: Ann Westine <[email protected]>
 
 
  Hi Paul,
 
 
 
  There are a few other error message that I received last week and
 
  they seem to reoccur every couple of months.  Here is an example.
 
  What does this error mean?
 
 
 
  Date: Mon, 29 Oct 90 05:02:53 -0800
 
  From: [email protected] (Mail Delivery Subsystem)
 
  Subject: Returned mail: Host unknown
 
  To: <@decpa.pa.dec.com:[email protected]>
 
 
 
      ----- Transcript of session follows -----
 
  mail11: Error from DECnet MAIL object on node "erlang",
 
          during mail delivery to <ERLANG::CHIU>.
 
          Remote error code is 0x7e803a, message is:
 
  %MAIL-E-LOGLINK, error creating network link to node CHIU
 
  -SYSTEM-F-NOSUCHNODE, remote node is unknown
 
  
 +
Hi Paul,
  
 +
There are a few other error message that I received last week and
 +
they seem to reoccur every couple of months.  Here is an example.
 +
What does this error mean?
  
Westine & Postel                                             
+
Date: Mon, 29 Oct 90 05:02:53 -0800
 +
From: [email protected] (Mail Delivery Subsystem)
 +
Subject: Returned mail: Host unknown
 +
To: <@decpa.pa.dec.com:[email protected]>
  
RFC 1211              Problems with Mailing Lists            March 1991
+
  ----- Transcript of session follows -----
 +
mail11: Error from DECnet MAIL object on node "erlang",
 +
        during mail delivery to <ERLANG::CHIU>.
 +
        Remote error code is 0x7e803a, message is:
 +
%MAIL-E-LOGLINK, error creating network link to node CHIU
 +
-SYSTEM-F-NOSUCHNODE, remote node is unknown
  
 +
554 <erlang::chiu>... 550 Host unknown (Authoritative
 +
  answer from name server)
  
   554 <erlang::chiu>... 550 Host unknown (Authoritative
+
   ----- Recipients of this delivery -----
    answer from name server)
+
<erlang::chiu> (bounced)
 +
<netrix::gillin> (sent)
 +
<erlang::rama> (sent)
 +
<netrix::gillin> (sent)
 +
<erlang::rama> (sent)
  
      ----- Recipients of this delivery -----
+
          ----------
  <erlang::chiu> (bounced)
 
  <netrix::gillin> (sent)
 
  <erlang::rama> (sent)
 
  <netrix::gillin> (sent)
 
  <erlang::rama> (sent)
 
  
              ----------
+
21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)~~
 
 
23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)~~
 
  
 
d.  Message From Postmaster
 
d.  Message From Postmaster
Line 1,429: Line 1,132:
  
 
This error:
 
This error:
          ----- Transcript of session follows -----
+
        ----- Transcript of session follows -----
        mail11: Error from DECnet MAIL object on node "erlang",
+
    mail11: Error from DECnet MAIL object on node "erlang",
                during mail delivery to <ERLANG::CHIU>.
+
            during mail delivery to <ERLANG::CHIU>.
                Remote error code is 0x7e803a, message is:
+
            Remote error code is 0x7e803a, message is:
        %MAIL-E-LOGLINK, error creating network link to node CHIU
+
    %MAIL-E-LOGLINK, error creating network link to node CHIU
        -SYSTEM-F-NOSUCHNODE, remote node is unknown
+
    -SYSTEM-F-NOSUCHNODE, remote node is unknown
        554 <erlang::chiu>... 550 Host unknown (Authoritative
+
    554 <erlang::chiu>... 550 Host unknown (Authoritative
                          answer from name server)
+
                      answer from name server)
  
 
  ...means that the person on ERLANG:: has forwarded their mail to a
 
  ...means that the person on ERLANG:: has forwarded their mail to a
Line 1,449: Line 1,152:
  
 
************************************************************************
 
************************************************************************
 
 
 
 
 
 
 
Westine & Postel                                             
 
 
RFC 1211              Problems with Mailing Lists            March 1991
 
 
  
 
F.10.2.  No Such User
 
F.10.2.  No Such User
  
  Date: Wed, 10 Oct 90 18:05 CDT
+
Date: Wed, 10 Oct 90 18:05 CDT
  From: PMDF Mail Server <[email protected]>
+
From: PMDF Mail Server <[email protected]>
  Subject: Undeliverable mail
+
Subject: Undeliverable mail
+
  
  The message could not be delivered to:
+
The message could not be delivered to:
  
  Addressee: gale
+
Addressee: gale
  Reason:
+
Reason:
    %MAIL-E-NOSUCHUSR, no such user GALE at node CRCVMS
+
  %MAIL-E-NOSUCHUSR, no such user GALE at node CRCVMS
  
 
************************************************************************
 
************************************************************************
Line 1,478: Line 1,170:
 
F.11.  No Transcript
 
F.11.  No Transcript
  
  Date: Wed, 8 Aug 90 13:21:03 -0700
+
Date: Wed, 8 Aug 90 13:21:03 -0700
  From: MAILER-DAEMON (Mail Delivery Subsystem)
+
From: MAILER-DAEMON (Mail Delivery Subsystem)
  Subject: Returned mail: Deferred: Host Name Lookup Failure
+
Subject: Returned mail: Deferred: Host Name Lookup Failure
  To: owner-ietf
+
To: owner-ietf
  To: owner-ietf
+
To: owner-ietf
  To: westine
+
To: westine
  
                          --------------
+
                        --------------
  <text deleted>
+
<text deleted>
  
 
************************************************************************
 
************************************************************************
Line 1,492: Line 1,184:
 
F.12.  Looping - Too Many Hops
 
F.12.  Looping - Too Many Hops
  
  Date: Wed, 7 Nov 90 18:08:59 PDT
+
Date: Wed, 7 Nov 90 18:08:59 PDT
  From: Mail Delivery Subsystem <[email protected]>
+
From: Mail Delivery Subsystem <[email protected]>
  Subject: Returned mail: Unable to deliver mail
+
Subject: Returned mail: Unable to deliver mail
  To:<@jessica.stanford.edu,@jessica.stanford.edu,@jessica.stanford.edu,
+
To:<@jessica.stanford.edu,@jessica.stanford.edu,@jessica.stanford.edu,
    @jessica.stanford.edu,@jessica.stanford.edu,@jessica.stanford.edu,
+
  @jessica.stanford.edu,@jessica.stanford.edu,@jessica.stanford.edu,
    @jessica.stanford.edu:[email protected]>
+
  @jessica.stanford.edu:[email protected]>
 
 
      ----- Transcript of session follows -----
 
  554 sendall: too many hops (17 max)
 
 
 
  Received: from Jessica.Stanford.EDU by Ahwahnee.Stanford.EDU
 
      (5.59/inc-1.0) id AA09128; Wed, 7 Nov 90 18:08:36 PDT
 
  Received: from Ahwahnee.Stanford.EDU by jessica.stanford.edu
 
      (5.59/25-eef) id AA17687; Wed, 7 Nov 90 18:08:31 PDT
 
  Received: from Jessica.Stanford.EDU by Ahwahnee.Stanford.EDU
 
      (5.59/inc-1.0)id AA09124; Wed, 7 Nov 90 18:08:28 PDT
 
  Received: from Ahwahnee.Stanford.EDU by jessica.stanford.edu
 
 
 
 
 
 
 
Westine & Postel                                             
 
  
RFC 1211              Problems with Mailing Lists            March 1991
+
  ----- Transcript of session follows -----
 +
554 sendall: too many hops (17 max)
  
 +
Received: from Jessica.Stanford.EDU by Ahwahnee.Stanford.EDU
 +
  (5.59/inc-1.0) id AA09128; Wed, 7 Nov 90 18:08:36 PDT
 +
Received: from Ahwahnee.Stanford.EDU by jessica.stanford.edu
 +
  (5.59/25-eef) id AA17687; Wed, 7 Nov 90 18:08:31 PDT
 +
Received: from Jessica.Stanford.EDU by Ahwahnee.Stanford.EDU
 +
  (5.59/inc-1.0)id AA09124; Wed, 7 Nov 90 18:08:28 PDT
 +
Received: from Ahwahnee.Stanford.EDU by jessica.stanford.edu
  
      (5.59/25-eef) id AA17674; Wed, 7 Nov 90 18:08:22 PDT
+
  (5.59/25-eef) id AA17674; Wed, 7 Nov 90 18:08:22 PDT
  Received: from Jessica.Stanford.EDU by Ahwahnee.Stanford.EDU
+
Received: from Jessica.Stanford.EDU by Ahwahnee.Stanford.EDU
      (5.59/inc-1.0) id AA09120; Wed, 7 Nov 90 18:08:19 PDT
+
  (5.59/inc-1.0) id AA09120; Wed, 7 Nov 90 18:08:19 PDT
  Received: from Ahwahnee.Stanford.EDU by jessica.stanford.edu
+
Received: from Ahwahnee.Stanford.EDU by jessica.stanford.edu
      (5.59/25-eef) id AA17658; Wed, 7 Nov 90 18:08:13 PDT
+
  (5.59/25-eef) id AA17658; Wed, 7 Nov 90 18:08:13 PDT
  
 +
Received: from Jessica.Stanford.EDU by Ahwahnee.Stanford.EDU
 +
  (5.59/inc-1.0) id AA09116; Wed, 7 Nov 90 18:08:11 PDT
 +
Received: from Ahwahnee.Stanford.EDU by jessica.stanford.edu
 +
  (5.59/25-eef) id AA17645; Wed, 7 Nov 90 18:08:05 PDT
 +
Received: from Jessica.Stanford.EDU by Ahwahnee.Stanford.EDU
 +
  (5.59/inc-1.0) id AA09112; Wed, 7 Nov 90 18:08:03 PDT
 +
Received: from VENERA.ISI.EDU by jessica.stanford.edu
 +
  (5.59/25-eef) id AA17625;
  
  Received: from Jessica.Stanford.EDU by Ahwahnee.Stanford.EDU
+
Wed, 7 Nov 90 18:07:50 PDT
      (5.59/inc-1.0) id AA09116; Wed, 7 Nov 90 18:08:11 PDT
+
Received: by venera.isi.edu (5.61/5.61+local)
  Received: from Ahwahnee.Stanford.EDU by jessica.stanford.edu
+
        id <AA29996>; Wed, 7 Nov 90 15:45:49 -0800
      (5.59/25-eef) id AA17645; Wed, 7 Nov 90 18:08:05 PDT
+
Received-Date: Wed, 7 Nov 90 15:45:45 -0800
  Received: from Jessica.Stanford.EDU by Ahwahnee.Stanford.EDU
+
Received: from NRI.RESTON.VA.US by venera.isi.edu (5.61/5.61+local)
      (5.59/inc-1.0) id AA09112; Wed, 7 Nov 90 18:08:03 PDT
+
        id <AA29992>; Wed, 7 Nov 90 15:45:45 -0800
  Received: from VENERA.ISI.EDU by jessica.stanford.edu
+
Received: from nri by NRI.NRI.Reston.VA.US id aa13139;7 Nov 90 18:26
      (5.59/25-eef) id AA17625;
+
To: Frank Kastenholz <kasten%[email protected]>
 
+
  Wed, 7 Nov 90 18:07:50 PDT
+
Subject: Re: IETF mailing list
  Received: by venera.isi.edu (5.61/5.61+local)
+
Date: Wed, 07 Nov 90 18:26:53 -0500
          id <AA29996>; Wed, 7 Nov 90 15:45:49 -0800
+
  Received-Date: Wed, 7 Nov 90 15:45:45 -0800
 
  Received: from NRI.RESTON.VA.US by venera.isi.edu (5.61/5.61+local)
 
          id <AA29992>; Wed, 7 Nov 90 15:45:45 -0800
 
  Received: from nri by NRI.NRI.Reston.VA.US id aa13139;7 Nov 90 18:26
 
  To: Frank Kastenholz <kasten%[email protected]>
 
 
  Subject: Re: IETF mailing list
 
  Date: Wed, 07 Nov 90 18:26:53 -0500
 
 
  
 
************************************************************************
 
************************************************************************
Line 1,550: Line 1,234:
 
F.13.  No Postmaster
 
F.13.  No Postmaster
  
  a.  Error Message
+
a.  Error Message
  
  Date: Mon, 5 Nov 90 18:40:58 EST
+
Date: Mon, 5 Nov 90 18:40:58 EST
+
  Subject: Returned mail: User unknown
+
Subject: Returned mail: User unknown
+
  
      ----- Transcript of session follows -----
+
  ----- Transcript of session follows -----
  
  421 osi3: Host osi3 is down
+
421 osi3: Host osi3 is down
  550 Postmaster... User unknown
+
550 Postmaster... User unknown
  
23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)~~
+
21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)~~
  
 +
b.  Checking Hostname and Address
  
 +
westine 37% dig osi3.ncsl.nist.gov any
  
 +
;; QUESTIONS:
 +
;;      osi3.ncsl.nist.gov, type = ANY, class = IN
  
 +
;; ANSWERS:
 +
osi3.ncsl.nist.gov      IN      A      129.6.48.108    ; 86400
 +
osi3.ncsl.nist.gov      IN      A      129.6.51.1      ; 86400
  
Westine & Postel                                             
+
21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)~~
  
RFC 1211              Problems with Mailing Lists            March 1991
+
c.  Checking For Users
  
 +
westine 49% mconnect OSI3.NCSL.NIST.GOV
 +
connecting to host OSI3.NCSL.NIST.GOV (0x6c300681), port 0x1900
 +
connection open
 +
220 osi3.ncsl.nist.gov sendmail 4.0/NIST(rbj/dougm) ready at
 +
  Thu, 8 Nov 90 13:58:49 EST
 +
expn ietf
 +
250-Dale Walters <walters>
 +
250-Richard Colella <[email protected]>
 +
250 Doug Montgomery <[email protected]>
  
  b.  Checking Hostname and Address
+
21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)~~
  
  westine 37% dig osi3.ncsl.nist.gov any
+
d. Checking For Administrators
  
  ;; QUESTIONS:
+
westine 44% whois osi3.ncsl.nist.gov
  ;;      osi3.ncsl.nist.gov, type = ANY, class = IN
+
National Bureau of Standards (ICST-OSI3)
  
   ;; ANSWERS:
+
   Hostname: OSI3.NCSL.NIST.GOV
   osi3.ncsl.nist.gov      IN      A      129.6.48.108   ; 86400
+
   Nicknames: OSI3.ICST.NBS.GOV,ICST-OSI3.ARPA
   osi3.ncsl.nist.gov      IN      A      129.6.51.1      ; 86400
+
  Address: 129.6.48.108
 +
   System: SUN-3/160 running UNIX
  
23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)~~
+
  Coordinator:
 +
      Montgomery, Douglas C.  (DCM5) [email protected]
 +
      (301) 975-3630
  
   c. Checking For Users
+
   Record last updated on 17-May-89.
  
  westine 49% mconnect OSI3.NCSL.NIST.GOV
+
21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)~~
  connecting to host OSI3.NCSL.NIST.GOV (0x6c300681), port 0x1900
 
  connection open
 
  220 osi3.ncsl.nist.gov sendmail 4.0/NIST(rbj/dougm) ready at
 
    Thu, 8 Nov 90 13:58:49 EST
 
  expn ietf
 
  250-Dale Walters <walters>
 
  250-Richard Colella <[email protected]>
 
  250 Doug Montgomery <[email protected]>
 
  
23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)~~
+
e.  Message Sent to Coordinator
  
  dChecking For Administrators
+
From westine@venera.isi.edu Thu Nov  8 13:58:40 1990
 +
Posted-Date: Thu, 08 Nov 90 10:59:30 PST
 +
 +
 +
Subject: RE: 421 osi3: Host osi3 is down
 +
    550 Postmaster... User unknown
 +
 +
Date: Thu, 08 Nov 90 10:59:30 PST
 +
From: Ann Westine <[email protected]>
  
  westine 44% whois osi3.ncsl.nist.gov
+
Hi Doug,
  National Bureau of Standards (ICST-OSI3)
 
  
      Hostname: OSI3.NCSL.NIST.GOV
+
If the Postmaster is "unknown" please delete him from your exploder
      Nicknames: OSI3.ICST.NBS.GOV,ICST-OSI3.ARPA
+
list "[email protected].nist.gov". I have been receiving error messages
      Address: 129.6.48.108
+
like this one for several days now. If I don't hear from you, I will
      System: SUN-3/160 running UNIX
+
have to delete the above mailbox.
  
      Coordinator:
+
Ann
        Montgomery, Douglas C.  (DCM5)  [email protected]
 
        (301) 975-3630
 
  
      Record last updated on 17-May-89.
+
>    ----- Transcript of session follows -----
 +
> 421 osi3: Host osi3 is down
 +
> 550 Postmaster... User unknown
  
23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)~~
+
21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)~~
  
 +
f.  Message From Coordinator
  
 +
Date: Thu, 8 Nov 90 15:34:02 EST
 +
From: Doug Montgomery <[email protected]>
 +
Organization: National Institute of Standards and Technology (NIST)
 +
Sub-Organization: National Computer Systems Laboratory
 +
 +
Subject: RE:  421 osi3: Host osi3 is down
 +
        550 Postmaster... User unknown
 +
  
 +
I think I have found out what is wrong.  For some reason (we can
 +
discuss this below)  your exploder is sending IETF mail to our
 +
exploder ([email protected]) through the machine
 +
osi.ncsl.nist.gov.  Now due to a recent subnet reconfiguration and
 +
subsequent lack of update to our DNS servers, the DNS was returning
 +
an incorrect address for osi3. Thus IETF mail would be sent to OSI,
 +
which would try to forward it to OSI3 (using the wrong address).
 +
OSI would think that OSI3 was down and dump the message, trying to
 +
send a notice to Postmaster.  OSI doesn't have an aliase for
 +
Postmaster and thus the second error message that you saw.
  
 +
These two problems have been fixed on OSI.  Now the question is what
 +
address you have in your distribution list that would cause this
 +
mail to go through OSI in the first place.  I guess you might have
 +
something like "ietf%[email protected]." The other interesting
 +
point about your list is that we receive IETF mail to our exploder
 +
directly from venera.
  
 +
Thus I suspect that there are two entries for OSI3 on your
 +
distribution list.  One that gets relayed through OSI and one that
 +
points directly to OSI3.  If this is the case  please deleted
 +
everything except the "[email protected]." address.
  
 +
If this is not the case or if there are other problems let me know.
  
Westine & Postel                                             
+
21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)~~
  
RFC 1211              Problems with Mailing Lists            March 1991
+
g.  My Reply Back
  
 +
Here are all the addresses I have on the IETF list under NIST.GOV.
  
  e. Message Sent to Coordinator
+
ietf@OSI3.NCSL.NIST.GOV,
 +
  
  From [email protected] Thu Nov  8 13:58:40 1990
+
I'll deleted "mills@osi.ncsl.nist.gov".
  Posted-Date: Thu, 08 Nov 90 10:59:30 PST
 
  To: dougm@osi.ncsl.nist.gov
 
 
  Subject: RE:  421 osi3: Host osi3 is down
 
      550 Postmaster... User unknown
 
  Reply-To: [email protected]
 
  Date: Thu, 08 Nov 90 10:59:30 PST
 
  From: Ann Westine <[email protected].edu>
 
  
  Hi Doug,
+
Here are two others at NIST
  
  If the Postmaster is "unknown" please delete him from your exploder
+
hunt@ENH.NIST.GOV,
  list "ietf@osi3.ncsl.nist.gov".  I have been receiving error messages
+
sting@CAM.NIST.GOV
  like this one for several days now. If I don't hear from you, I will
 
  have to delete the above mailbox.
 
  
  Ann
+
By the way, on the following message, it looks like the Mailer-Daemon
 +
message went from OSI.ncsl.nist.gov to enh.nist.gov to venera.isi.edu.
  
  >    ----- Transcript of session follows -----
+
--Ann
  > 421 osi3: Host osi3 is down
 
  > 550 Postmaster... User unknown
 
  
23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)~~
+
    Return-Path: [email protected]
 +
    Received-Date: Thu, 8 Nov 90 12:44:11 PST
 +
    Received: from venera.isi.edu by zephyr.isi.edu (4.1/4.0.3-4)
 +
            id <AA19131>; Thu, 8 Nov 90 12:44:11 PST
 +
    Posted-Date: Thu, 8 Nov 90 15:39:54 EST
 +
    Received: from enh.nist.gov by venera.isi.edu (5.61/5.61+local)
 +
            id <AA03448>; Thu, 8 Nov 90 12:44:01 -0800
 +
    Received: from OSI.NCSL.NIST.GOV by ENH.NIST.GOV;
 +
            Thu, 8 Nov 90 15:43 EDT
 +
    Received: by osi.ncsl.nist.gov (4.1/SMI-4.1) id AB14654;
 +
            Thu, 8 Nov 90 15:39:54 EST
 +
    Date: Thu, 8 Nov 90 15:39:54 EST
 +
    From: [email protected]
 +
    Subject: Returned mail: User unknown
 +
 +
    Message-Id: <[email protected]>
 +
    X-Envelope-To: [email protected]
  
  f. Message From Coordinator
+
      ----- Transcript of session follows -----
 +
    421 osi3: Host osi3 is down
 +
    550 Postmaster... User unknown
  
  Date: Thu, 8 Nov 90 15:34:02 EST
+
      ----- Unsent message follows -----
  From: Doug Montgomery <[email protected]>
 
  Organization: National Institute of Standards and Technology (NIST)
 
  Sub-Organization: National Computer Systems Laboratory
 
 
  Subject: RE:  421 osi3: Host osi3 is down
 
            550 Postmaster... User unknown
 
 
  
  I think I have found out what is wrong.  For some reason (we can
+
21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)~~
  discuss this below) your exploder is sending IETF mail to our
 
  exploder ([email protected]) through the machine
 
  osi.ncsl.nist.gov.  Now due to a recent subnet reconfiguration and
 
  subsequent lack of update to our DNS servers, the DNS was returning
 
  an incorrect address for osi3. Thus IETF mail would be sent to OSI,
 
  which would try to forward it to OSI3 (using the wrong address).
 
  OSI would think that OSI3 was down and dump the message, trying to
 
    send a notice to Postmaster.  OSI doesn't have an aliase for
 
  Postmaster and thus the second error message that you saw.
 
  
 +
h. Another Problem  .Forward
  
 +
From: Doug Montgomery <[email protected]>
 +
Organization: National Institute of Standards and Technology (NIST)
 +
 +
Subject: Re: 421 osi3:Host osi3 is down 550 Postmaster.. User unknown
  
Westine & Postel                                             
+
Deleting the [email protected] entry should fix your problems.
 +
Mills has a .forward to osi3, thus explaining why IETF mail was going
 +
---> OSI ---> OSI3.
  
RFC 1211              Problems with Mailing Lists            March 1991
+
I checked OSI's sendmail.cf and it is relaying through enh.  This,
 +
though has nothing to do with the previous problem.
  
 +
I flushed the queue of IETF mail on OSI waiting to go to OSI3.  I
 +
don't think you should see anymore bounced messages.
  
    These two problems have been fixed on OSI.  Now the question is what
+
Sorry that our local problems were causing you grief .... let me know
  address you have in your distribution list that would cause this
+
if it happens again.
  mail to go through OSI in the first place.  I guess you might have
 
  something like "ietf%osi3@osi.ncsl.nist.gov." The other interesting
 
  point about your list is that we receive IETF mail to our exploder
 
    directly from venera.
 
  
    Thus I suspect that there are two entries for OSI3 on your
+
************************************************************************
  distribution list.  One that gets relayed through OSI and one that
 
  points directly to OSI3.  If this is the case  please deleted
 
    everything except the "[email protected]." address.
 
  
    If this is not the case or if there are other problems let me know.
+
F.14File Over Allocation
 
 
23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)~~
 
 
 
  gMy Reply Back
 
 
 
  Here are all the addresses I have on the IETF list under NIST.GOV.
 
 
 
 
 
 
 
  I'll deleted "[email protected]".
 
 
 
  Here are two others at NIST
 
 
 
 
 
 
 
  By the way, on the following message, it looks like the Mailer-Daemon
 
  message went from OSI.ncsl.nist.gov to enh.nist.gov to venera.isi.edu.
 
 
 
  --Ann
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
Westine & Postel                                             
 
  
RFC 1211              Problems with Mailing Lists            March 1991
+
Date: Tue, 4 Sep 90 10:35:49 -0700
 +
From: MAILER-DAEMON (Mail Delivery Subsystem)
 +
Subject: Returned mail: Deferred: Connection timed out during user
 +
        open with ames.arc.nasa.gov
 +
Posted-Date: Tue, 4 Sep 90 10:35:49 -0700
 +
To: owner-ietf
  
 
+
    ----- Transcript of session follows -----
      Return-Path: [email protected]
+
>>> QUIT
      Received-Date: Thu, 8 Nov 90 12:44:11 PST
+
<<< 421 sage.acc.com SMTP Service not available:
      Received: from venera.isi.edu by zephyr.isi.edu (4.1/4.0.3-4)
+
    insufficient disk space.
              id <AA19131>; Thu, 8 Nov 90 12:44:11 PST
+
451 bboard.ietf@SAGE.ACC.COM... reply: read error
      Posted-Date: Thu, 8 Nov 90 15:39:54 EST
+
    bboard.ietf@SAGE.ACC.COM... reply: read error
      Received: from enh.nist.gov by venera.isi.edu (5.61/5.61+local)
 
              id <AA03448>; Thu, 8 Nov 90 12:44:01 -0800
 
      Received: from OSI.NCSL.NIST.GOV by ENH.NIST.GOV;
 
              Thu, 8 Nov 90 15:43 EDT
 
      Received: by osi.ncsl.nist.gov (4.1/SMI-4.1) id AB14654;
 
              Thu, 8 Nov 90 15:39:54 EST
 
      Date: Thu, 8 Nov 90 15:39:54 EST
 
      From: [email protected]
 
      Subject: Returned mail: User unknown
 
      To: [email protected]
 
      Message-Id: <[email protected]>
 
      X-Envelope-To: [email protected]
 
 
 
          ----- Transcript of session follows -----
 
      421 osi3: Host osi3 is down
 
      550 Postmaster... User unknown
 
 
 
          ----- Unsent message follows -----
 
 
 
23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)~~
 
 
 
  h. Another Problem  .Forward
 
 
 
  From: Doug Montgomery <dougm@warthog.ncsl.nist.gov>
 
  Organization: National Institute of Standards and Technology (NIST)
 
  To: westine@ISI.EDU
 
  Subject: Re: 421 osi3:Host osi3 is down 550 Postmaster.. User unknown
 
 
 
  Deleting the mills@osi.ncsl.nist.gov entry should fix your problems.
 
  Mills has a .forward to osi3, thus explaining why IETF mail was going
 
  ---> OSI ---> OSI3.
 
 
 
  I checked OSI's sendmail.cf and it is relaying through enh.  This,
 
  though has nothing to do with the previous problem.
 
 
 
  I flushed the queue of IETF mail on OSI waiting to go to OSI3.  I
 
  don't think you should see anymore bounced messages.
 
 
 
  Sorry that our local problems were causing you grief .... let me know
 
  if it happens again.
 
  
 
************************************************************************
 
************************************************************************
  
 +
F.15.  File Deleted
  
 +
Date: Fri, 10 Aug 90 14:21:57 EDT
 +
From: Daemon <[email protected]>
 +
Subject: Undeliverable mail
 +
To: westine
  
 +
Mail could not be delivered to the following address(es):
  
Westine & Postel                                             
+
/usr/databases/bugs/vaxmail@ccj.bbn.com: No such file
 
+
    or directory
RFC 1211              Problems with Mailing Lists            March 1991
 
 
 
 
 
F.14.  File Over Allocation
 
 
 
  Date: Tue, 4 Sep 90 10:35:49 -0700
 
  From: MAILER-DAEMON (Mail Delivery Subsystem)
 
  Subject: Returned mail: Deferred: Connection timed out during user
 
            open with ames.arc.nasa.gov
 
  Posted-Date: Tue, 4 Sep 90 10:35:49 -0700
 
  To: owner-ietf
 
 
 
      ----- Transcript of session follows -----
 
  >>> QUIT
 
  <<< 421 sage.acc.com SMTP Service not available:
 
      insufficient disk space.
 
  451 [email protected]... reply: read error
 
        [email protected]... reply: read error
 
  
 
************************************************************************
 
************************************************************************
  
F.15File Deleted
+
F.16Strange Postmaster
  
  Date: Fri, 10 Aug 90 14:21:57 EDT
+
a. Message Forwarded to IETF-Request
  From: Daemon <daemon@ccj.bbn.com>
 
  Subject: Undeliverable mail
 
  To: westine
 
  
  Mail could not be delivered to the following address(es):
+
Forwarded: Thu, 21 Feb 91 14:31:09 PST
 +
Forwarded: westine
 +
 +
 +
Return-Path: [email protected]
 +
Received-Date: Sun, 17 Feb 91 17:48:07 PST
 +
Received: from venera.isi.edu by zephyr.isi.edu (4.1/4.0.3-4)
 +
        id <AA03679>; Sun, 17 Feb 91 17:48:07 PST
 +
Posted-Date: Sun, 17 Feb 91 20:48:12 -0500
 +
Received: from TIS.COM by venera.isi.edu (5.61/5.61+local)
 +
        id <AA26292>; Sun, 17 Feb 91 17:48:01 -0800
 +
Received: from TIS.COM by TIS.COM (4.1/SUN-5.64DB)
  
  /usr/databases/bugs/vaxmail@ccj.bbn.com: No such file
+
        id AA04098; Sun, 17 Feb 91 20:48:13 EST
        or directory
+
Reply-To: James M Galvin <galvin@TIS.COM>
 +
To: ietf-request@ISI.EDU
 +
Subject: Failed Mail to IETF
 +
Date: Sun, 17 Feb 91 20:48:12 -0500
 +
From: James M Galvin <[email protected]>
  
************************************************************************
+
------- Forwarded Message
 +
Message-ID: <[email protected]>
 +
 +
To:        [email protected]
 +
Date:      15 Feb 91 21:28:28
 +
Subject:    Can't Find MailCenter!
  
F.16.  Strange Postmaster
+
                <text deleted>
  
  a.  Message Forwarded to IETF-Request
+
21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)~~
  
  Forwarded: Thu, 21 Feb 91 14:31:09 PST
+
b. Problem Reported to MITRE
  Forwarded: westine
 
  Forwarded: postmaster@mbunix.mitre.org
 
  Forwarded: [email protected]
 
  Return-Path: [email protected]
 
  Received-Date: Sun, 17 Feb 91 17:48:07 PST
 
  Received: from venera.isi.edu by zephyr.isi.edu (4.1/4.0.3-4)
 
          id <AA03679>; Sun, 17 Feb 91 17:48:07 PST
 
  Posted-Date: Sun, 17 Feb 91 20:48:12 -0500
 
  Received: from TIS.COM by venera.isi.edu (5.61/5.61+local)
 
          id <AA26292>; Sun, 17 Feb 91 17:48:01 -0800
 
  Received: from TIS.COM by TIS.COM (4.1/SUN-5.64DB)
 
  
 +
 +
Cc: westine, [email protected]
 +
Subject: RE:    Can't Find MailCenter!
 +
 +
Date: Thu, 21 Feb 91 14:31:01 PST
 +
From: Ann Westine <[email protected]>
  
 +
Hi,
  
Westine & Postel                                             
+
We're getting this problem again.  Please fix.
  
RFC 1211              Problems with Mailing Lists            March 1991
+
Thank you.
 +
Ann
  
 +
------- Forwarded Message
  
          id AA04098; Sun, 17 Feb 91 20:48:13 EST
+
Date:    Sun, 17 Feb 91 20:48:12 -0500
   Reply-To: James M Galvin <[email protected]>
+
From:   James M Galvin <[email protected]>
+
  Subject: Failed Mail to IETF
+
Subject: Failed Mail to IETF
  Date: Sun, 17 Feb 91 20:48:12 -0500
 
  From: James M Galvin <[email protected]>
 
  
 
   ------- Forwarded Message
 
   ------- Forwarded Message
 +
 
   Message-ID: <[email protected]>
 
   Message-ID: <[email protected]>
  
Line 1,866: Line 1,522:
 
   Date:      15 Feb 91 21:28:28
 
   Date:      15 Feb 91 21:28:28
 
   Subject:    Can't Find MailCenter!
 
   Subject:    Can't Find MailCenter!
 +
 +
  GatorMail-Q                  Re: 1st PRELIMINARY AGENDA/
 +
  Received: by qmgate; 15 Feb 91 21:28:25
 +
  Received: by mbunix.mitre.org (5.57/4.7)
 +
          id AA25128; Fri, 15 Feb 91 21:26:46 EST
 +
  Received: by venera.isi.edu (5.61/5.61+local)
 +
          id <AA17839>; Fri, 15 Feb 91 08:45:12 -0800
 +
  Posted-Date: Fri, 15 Feb 91 11:45:16 -0500
 +
  Received-Date: Fri, 15 Feb 91 08:45:09 -0800
 +
  Received: from TIS.COM by venera.isi.edu (5.61/5.61+local)
 +
          id <AA17833>; Fri, 15 Feb 91 08:45:09 -0800
 +
  Message-Id: <[email protected]>
 +
  Reply-To: James M Galvin <[email protected]>
 +
  To: Megan Davies <[email protected]>
 +
 +
  Subject: Re: 1st PRELIMINARY AGENDA/ST. LOUIS
 +
  In-Reply-To: Your message of Thu, 14 Feb 91 17:44:13 EST.
 +
                <[email protected]>
 +
  Date: Fri, 15 Feb 91 11:45:16 -0500
 +
  From: James M Galvin <[email protected]>
  
 
                   <text deleted>
 
                   <text deleted>
 
23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)~~
 
 
  b.  Problem Reported to MITRE
 
 
 
  Cc: westine, [email protected]
 
  Subject: RE:    Can't Find MailCenter!
 
  Reply-To: [email protected]
 
  Date: Thu, 21 Feb 91 14:31:01 PST
 
  From: Ann Westine <[email protected]>
 
 
  Hi,
 
 
  We're getting this problem again.  Please fix.
 
 
  Thank you.
 
  Ann
 
 
  ------- Forwarded Message
 
 
  Date:    Sun, 17 Feb 91 20:48:12 -0500
 
  From:    James M Galvin <[email protected]>
 
  To:      [email protected]
 
  Subject: Failed Mail to IETF
 
 
      ------- Forwarded Message
 
 
      Message-ID: <[email protected]>
 
      From:      [email protected] <[email protected]>
 
      To:        [email protected]
 
      Date:      15 Feb 91 21:28:28
 
      Subject:    Can't Find MailCenter!
 
 
 
 
Westine & Postel                                             
 
 
RFC 1211              Problems with Mailing Lists            March 1991
 
 
 
      GatorMail-Q                  Re: 1st PRELIMINARY AGENDA/
 
      Received: by qmgate; 15 Feb 91 21:28:25
 
      Received: by mbunix.mitre.org (5.57/4.7)
 
              id AA25128; Fri, 15 Feb 91 21:26:46 EST
 
      Received: by venera.isi.edu (5.61/5.61+local)
 
              id <AA17839>; Fri, 15 Feb 91 08:45:12 -0800
 
      Posted-Date: Fri, 15 Feb 91 11:45:16 -0500
 
      Received-Date: Fri, 15 Feb 91 08:45:09 -0800
 
      Received: from TIS.COM by venera.isi.edu (5.61/5.61+local)
 
              id <AA17833>; Fri, 15 Feb 91 08:45:09 -0800
 
      Message-Id: <[email protected]>
 
      Reply-To: James M Galvin <[email protected]>
 
      To: Megan Davies <[email protected]>
 
      Cc: [email protected]
 
      Subject: Re: 1st PRELIMINARY AGENDA/ST. LOUIS
 
      In-Reply-To: Your message of Thu, 14 Feb 91 17:44:13 EST.
 
                  <[email protected]>
 
      Date: Fri, 15 Feb 91 11:45:16 -0500
 
      From: James M Galvin <[email protected]>
 
 
                      <text deleted>
 
  
 
************************************************************************
 
************************************************************************
Line 1,935: Line 1,549:
 
F.17.  Message Too Large
 
F.17.  Message Too Large
  
  Date: Wed, 10 Oct 90 17:50:10 MDT
+
Date: Wed, 10 Oct 90 17:50:10 MDT
  From: [email protected] (Mail Delivery Subsystem)
+
From: [email protected] (Mail Delivery Subsystem)
  Subject: Returned mail: Service unavailable
+
Subject: Returned mail: Service unavailable
+
  
      ----- Transcript of session follows ----- 554
+
  ----- Transcript of session follows ----- 554
  [email protected]... Message is too large; 50000 bytes max 554
+
[email protected]... Message is too large; 50000 bytes max 554
  [email protected]... Service unavailable
+
[email protected]... Service unavailable
  
 
************************************************************************
 
************************************************************************
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
Westine & Postel                                             
 
 
RFC 1211              Problems with Mailing Lists            March 1991
 
 
  
 
F.18.  Vacation Messages
 
F.18.  Vacation Messages
  
  a.  Case 1
+
a.  Case 1
  
  Date: Mon, 8 Oct 90 15:28:30 PDT
+
Date: Mon, 8 Oct 90 15:28:30 PDT
  From: David Wasley <[email protected]>
+
From: David Wasley <[email protected]>
  Subject: I am away from e-mail
+
Subject: I am away from e-mail
  This_Message_Brought_To_You_By: the vacation program
+
This_Message_Brought_To_You_By: the vacation program
  Apparently-To: [email protected]
+
Apparently-To: [email protected]
  
  I am away from e-mail until October 13. If your message requires
+
I am away from e-mail until October 13. If your message requires
  immediate attention, please contact one of the people below:
+
immediate attention, please contact one of the people below:
  
  Network problems:    Austin Shelton <[email protected]>
+
Network problems:    Austin Shelton <[email protected]>
  
  Network information:  Bill Wells <[email protected]>
+
Network information:  Bill Wells <[email protected]>
    Network installation: Jim Allison <[email protected]> If
+
  Network installation: Jim Allison <[email protected]> If
  you're really desparate, leave me voice-mail at (415) 642-3478.
+
you're really desparate, leave me voice-mail at (415) 642-3478.
  Thanks for your patience! David Wasley, U C Berkeley
+
Thanks for your patience! David Wasley, U C Berkeley
  
23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)~~
+
21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)~~
  
  b.  Case 2
+
b.  Case 2
  
  Date: Fri, 2 Nov 90 18:17:12 EST
+
Date: Fri, 2 Nov 90 18:17:12 EST
  From: [email protected] (Mail Delivery Subsystem)
+
From: [email protected] (Mail Delivery Subsystem)
  Subject: Returned mail: unknown mailer error 1
+
Subject: Returned mail: unknown mailer error 1
+
  
      ----- Transcript of session follows -----
+
  ----- Transcript of session follows -----
  sh: vacation: not found
+
sh: vacation: not found
  554 "|vacation farber"... unknown mailer error 1
+
554 "|vacation farber"... unknown mailer error 1
  
 
************************************************************************
 
************************************************************************
Line 2,002: Line 1,597:
 
F.19.  LocaL Configuration Errors
 
F.19.  LocaL Configuration Errors
  
  Date: Tue, 14 Aug 90 00:36:51 -0400
+
Date: Tue, 14 Aug 90 00:36:51 -0400
+
  Subject: Returned mail: Local configuration error
+
Subject: Returned mail: Local configuration error
  To: <owner-ietf>
+
To: <owner-ietf>
  
      ----- Transcript of session follows -----
+
  ----- Transcript of session follows -----
+
      Local configuration error
+
    Local configuration error
  
 
************************************************************************
 
************************************************************************
 
 
 
 
Westine & Postel                                             
 
 
RFC 1211              Problems with Mailing Lists            March 1991
 
 
  
 
F.20.  Service Unavailable
 
F.20.  Service Unavailable
  
  Date: Wed, 8 Aug 90 13:00:39 EDT
+
Date: Wed, 8 Aug 90 13:00:39 EDT
+
  Subject: Returned mail: Service unavailable
+
Subject: Returned mail: Service unavailable
  To: <owner-ietf>
+
To: <owner-ietf>
  
      ----- Transcript of session follows -----
+
  ----- Transcript of session follows -----
  Connected to eng.clemson.edu:
+
Connected to eng.clemson.edu:
  >>> HELO omni
+
>>> HELO omni
  <<< 553 omni host name configuration error
+
<<< 553 omni host name configuration error
  554 <[email protected]>... Service unavailable
+
554 <[email protected]>... Service unavailable
  
      ----- Unsent message follows -----
+
  ----- Unsent message follows -----
  
 
************************************************************************
 
************************************************************************
Line 2,040: Line 1,627:
 
F.21.  "Bad File Number"
 
F.21.  "Bad File Number"
  
  To: <owner-ietf>
+
To: <owner-ietf>
  From: The UTCS Post Office <[email protected]>
+
From: The UTCS Post Office <[email protected]>
  Subject: Delivery problems with your mail
+
Subject: Delivery problems with your mail
  
  Your message has been received by the University of Toronto Computing
+
Your message has been received by the University of Toronto Computing
  Services Postal System. A copy of it has been returned to you because
+
Services Postal System. A copy of it has been returned to you because
  of difficulties encountered while attempting to deliver your mail.
+
of difficulties encountered while attempting to deliver your mail.
  
  The following errors occurred while attempting delivery:
+
The following errors occurred while attempting delivery:
  
  <smtp madhaus.utcs.utoronto.ca [email protected] 1609>:
+
<smtp madhaus.utcs.utoronto.ca [email protected] 1609>:
    128.100.102.10: 550 <[email protected]>... User unknown:
+
128.100.102.10: 550 <[email protected]>... User unknown:
    Bad file number
+
Bad file number
  
 
************************************************************************
 
************************************************************************
Line 2,058: Line 1,645:
 
F.22.  Cannot Append
 
F.22.  Cannot Append
  
  Date: Sat, 11 Aug 90 14:51:57 PDT
+
Date: Sat, 11 Aug 90 14:51:57 PDT
  From: [email protected] (Mail Delivery Subsystem)
+
From: [email protected] (Mail Delivery Subsystem)
  Subject: Returned mail: Service unavailable
+
Subject: Returned mail: Service unavailable
+
  
      ----- Transcript of session follows -----
+
  ----- Transcript of session follows -----
  mail: /var/spool/mail/cslater: cannot append
+
mail: /var/spool/mail/cslater: cannot append
  Mail saved in dead.letter
+
Mail saved in dead.letter
  554 cslater... Service unavailable
+
554 cslater... Service unavailable
  
 
************************************************************************
 
************************************************************************
 
 
 
Westine & Postel                                             
 
 
RFC 1211              Problems with Mailing Lists            March 1991
 
 
  
 
F.23.  Error Creating Network Link
 
F.23.  Error Creating Network Link
  
  "erlang::chang... Host unknown"
+
"erlang::chang... Host unknown"
  
  Date: Thu, 1 Nov 90 12:34:20 -0800
+
Date: Thu, 1 Nov 90 12:34:20 -0800
  From: [email protected] (Mail Delivery Subsystem)
+
From: [email protected] (Mail Delivery Subsystem)
  Subject: Returned mail: Deferred
+
Subject: Returned mail: Deferred
  To: <@decpa.pa.dec.com:[email protected]>
+
To: <@decpa.pa.dec.com:[email protected]>
  
      ----- Transcript of session follows -----
+
  ----- Transcript of session follows -----
  mail11: Error from DECnet MAIL object on node "erlang",
+
mail11: Error from DECnet MAIL object on node "erlang",
          during mail delivery to <ERLANG::CHIU>.
+
        during mail delivery to <ERLANG::CHIU>.
          Remote error code is 0x7e803a, message is:
+
        Remote error code is 0x7e803a, message is:
  %MAIL-E-LOGLINK, error creating network link to node CHIU
+
%MAIL-E-LOGLINK, error creating network link to node CHIU
  -SYSTEM-F-NOSUCHNODE, remote node is unknown
+
-SYSTEM-F-NOSUCHNODE, remote node is unknown
  554 <erlang::chiu>... 550 Host unknown (Authoritative answer from
+
554 <erlang::chiu>... 550 Host unknown (Authoritative answer from
      name server)
+
    name server)
  mail11: connect: Connect failed, Node unreachable
+
mail11: connect: Connect failed, Node unreachable
  (temporary failure)
+
(temporary failure)
  
      ----- Recipients of this delivery -----
+
  ----- Recipients of this delivery -----
  <erlang::chiu> (bounced)
+
<erlang::chiu> (bounced)
  <netrix::gillin> (queued, will retry)
+
<netrix::gillin> (queued, will retry)
  <erlang::rama> (sent)
+
<erlang::rama> (sent)
  
      ----- Unsent message follows -----
+
  ----- Unsent message follows -----
  
 
************************************************************************
 
************************************************************************
Line 2,108: Line 1,688:
 
F.24.  Not a Typewriter
 
F.24.  Not a Typewriter
  
  Date: Wed, 8 Aug 90 19:36:47 -0700
+
Date: Wed, 8 Aug 90 19:36:47 -0700
  From: [email protected] (Mail Delivery Subsystem)
+
From: [email protected] (Mail Delivery Subsystem)
  Subject: Returned mail: Host unknown
+
Subject: Returned mail: Host unknown
  To: owner-ietf
+
To: owner-ietf
 
 
      ----- Transcript of session follows -----
 
  get_status: Not a typewriter
 
  (mail11 operating system error)
 
  
   451 <[email protected]>... Operating system error
+
   ----- Transcript of session follows -----
  mail11: connect: Connect failed, Unrecognized object
+
get_status: Not a typewriter
  (permanent failure)
+
(mail11 operating system error)
  
  554 <bansal@NETRIX.ENET.DEC.COM>... 550 Host unknown
+
451 <gray@netrix.enet.dec.com>... Operating system error
      (Authoritative answer from name server)
+
mail11: connect: Connect failed, Unrecognized object
 +
(permanent failure)
  
 +
554 <[email protected]>... 550 Host unknown
 +
  (Authoritative answer from name server)
  
 +
  ----- Recipients of this delivery -----
 +
<[email protected]> (bounced)
 +
<[email protected]> (bounced)
  
 
+
   ----- Unsent message follows -----
 
 
Westine & Postel                                             
 
 
 
RFC 1211              Problems with Mailing Lists            March 1991
 
 
 
 
 
      ----- Recipients of this delivery -----
 
   <[email protected]> (bounced)
 
  <[email protected]> (bounced)
 
 
 
      ----- Unsent message follows -----
 
  
 
************************************************************************
 
************************************************************************
Line 2,143: Line 1,714:
 
F.25.  "MTA Congestion"
 
F.25.  "MTA Congestion"
  
  Date: Tue, 7 Aug 90 22:37:48 -0700
+
Date: Tue, 7 Aug 90 22:37:48 -0700
  To: ietf-request
+
To: ietf-request
  From: DFN Gateway <postmaster%[email protected]>
+
From: DFN Gateway <postmaster%[email protected]>
  Subject: DFN Mail Network -- failed mail
+
Subject: DFN Mail Network -- failed mail
  
  Mail Failure Diagnostics:
+
Mail Failure Diagnostics:
  
  Message Recipients:
+
Message Recipients:
      [email protected]: MTA congestion
+
  [email protected]: MTA congestion
  
 
************************************************************************
 
************************************************************************
Line 2,157: Line 1,728:
 
F.26.  Local Forwarding Not Working
 
F.26.  Local Forwarding Not Working
  
+
  Subject: [email protected]... User unknown
+
Subject: [email protected]... User unknown
  Date: Thu, 01 Nov 90 13:20:53 PST
+
Date: Thu, 01 Nov 90 13:20:53 PST
  From: Ann Westine <[email protected]>
+
From: Ann Westine <[email protected]>
  
  Hi,
+
Hi,
  
  Would you mind checking into this error message before I delete this
+
Would you mind checking into this error message before I delete this
  person from our list.  I think it may be an internal forwarding
+
person from our list.  I think it may be an internal forwarding
  problem at MIT.  If not let me know if there is a new address or if I
+
problem at MIT.  If not let me know if there is a new address or if I
  should delete this one.
+
should delete this one.
  
  --Ann
+
--Ann
  
      ------- Forwarded Message
+
  ------- Forwarded Message
  
      Date:    Thu, 01 Nov 90 12:34:01 -0800
+
  Date:    Thu, 01 Nov 90 12:34:01 -0800
      From:    [email protected] (Mail Delivery Subsystem)
+
  From:    [email protected] (Mail Delivery Subsystem)
      To:      [email protected]
+
  To:      [email protected]
      Subject: Returned mail: User unknown
+
  Subject: Returned mail: User unknown
  
 +
      ----- Transcript of session follows -----
 +
  >>> RCPT To:<[email protected]>
 +
  <<< 550 /u/dukach/.forward:
 +
      line 0: tabasco.lcs.mit.edu... User unknown
 +
  550 [email protected]... User unknown
  
 +
      ----- Unsent message follows -----
  
 +
 +
 +
  Subject: Re: [email protected]... User unknown
 +
  In-Reply-To: Your message of Thu, 01 Nov 90 13:20:53 -0800.
 +
                <[email protected]>
 +
  Date: Thu, 01 Nov 90 17:16:44 -0500
 +
  
 +
  Ann,
  
 +
  Please don't delete Semyon. I'll get him to fix his
 +
  configuration.
  
 
+
  Thanks,
Westine & Postel                                             
+
  Chuck
 
 
RFC 1211              Problems with Mailing Lists            March 1991
 
 
 
 
 
        ----- Transcript of session follows -----
 
      >>> RCPT To:<[email protected]>
 
      <<< 550 /u/dukach/.forward:
 
          line 0: tabasco.lcs.mit.edu... User unknown
 
      550 [email protected]... User unknown
 
 
 
        ----- Unsent message follows -----
 
 
 
      To: [email protected]
 
      Cc: [email protected]
 
      Subject: Re: [email protected]... User unknown
 
      In-Reply-To: Your message of Thu, 01 Nov 90 13:20:53 -0800.
 
                  <[email protected]>
 
      Date: Thu, 01 Nov 90 17:16:44 -0500
 
      From: [email protected]
 
 
 
      Ann,
 
 
 
      Please don't delete Semyon. I'll get him to fix his
 
      configuration.
 
 
 
      Thanks,
 
      Chuck
 
  
 
************************************************************************
 
************************************************************************
Line 2,217: Line 1,777:
 
F.27. No Such File or Directory
 
F.27. No Such File or Directory
  
  Date: Tue, 11 Dec 90 17:57:08 -0800
+
Date: Tue, 11 Dec 90 17:57:08 -0800
  From: [email protected] (Mail Delivery Subsystem)
+
From: [email protected] (Mail Delivery Subsystem)
  Subject: Returned mail: unknown mailer error 2
+
Subject: Returned mail: unknown mailer error 2
+
  
      ----- Transcript of session follows -----
+
  ----- Transcript of session follows -----
  <<< RCPT To:<[email protected]>
+
<<< RCPT To:<[email protected]>
  <<< RCPT To:<[email protected]>
+
<<< RCPT To:<[email protected]>
  <<< DATA
+
<<< DATA
  mail: Creating /usr/spool/mail/phil -: No such file or directory
+
mail: Creating /usr/spool/mail/phil -: No such file or directory
  mail: Creating /usr/spool/mail/rick -: No such file or directory
+
mail: Creating /usr/spool/mail/rick -: No such file or directory
  Mail saved in dead.letter
+
Mail saved in dead.letter
+
  mailer error
+
mailer error
  
 
************************************************************************
 
************************************************************************
 
 
 
 
 
 
 
Westine & Postel                                             
 
 
RFC 1211              Problems with Mailing Lists            March 1991
 
 
  
 
F.28.  User Account Terminated
 
F.28.  User Account Terminated
  
  Date: Wed, 10 Oct 90 18:21:23 EDT
+
Date: Wed, 10 Oct 90 18:21:23 EDT
+
  Subject: Returned mail: User unknown
+
Subject: Returned mail: User unknown
+
  
      ----- Transcript of session follows -----
+
  ----- Transcript of session follows -----
  Connected to DEVVAX.TN.CORNELL.EDU:
+
Connected to DEVVAX.TN.CORNELL.EDU:
  >>> RCPT To:<[email protected]>
+
>>> RCPT To:<[email protected]>
  <<< 550 <[email protected]>... User unknown
+
<<< 550 <[email protected]>... User unknown
  550 [email protected]... User unknown
+
550 [email protected]... User unknown
  
 
************************************************************************
 
************************************************************************
Line 2,262: Line 1,811:
 
F.29.  Machine Terminated
 
F.29.  Machine Terminated
  
  Date: Wed, 10 Oct 90 19:33:26 EDT
+
Date: Wed, 10 Oct 90 19:33:26 EDT
  From: Mail Delivery Subsystem <[email protected]>
+
From: Mail Delivery Subsystem <[email protected]>
  Subject: Returned mail: Host unknown
+
Subject: Returned mail: Host unknown
+
  
      ----- Transcript of session follows -----
+
  ----- Transcript of session follows -----
  550 edn-unix.dca.mil.tcp... 550 Host unknown
+
550 edn-unix.dca.mil.tcp... 550 Host unknown
  550 [email protected]... Host unknown
+
550 [email protected]... Host unknown
  
      ----- Unsent message follows -----
+
  ----- Unsent message follows -----
  
 
************************************************************************
 
************************************************************************
Line 2,277: Line 1,826:
 
F.30.  Couldn't Make Final Delivery.
 
F.30.  Couldn't Make Final Delivery.
  
  a.  Case 1
+
a.  Case 1
 
 
  Date: 29 Aug 90 13:17:34 EST
 
  From: "SMTP MAILER" <[email protected]>
 
  Subject: Mail Delivery Problem
 
  To: "owner-ietf" <owner-ietf>
 
 
 
    ----Reason for mail failure follows----
 
  Sending mail to recipient(s) Nakassis :
 
    Couldn't make final delivery.
 
 
 
  %MAIL-E-OPENOUT, error opening USER2:[000000]NAKASSIS.DIR as output
 
 
 
23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)~~
 
 
 
  
 +
Date: 29 Aug 90 13:17:34 EST
 +
From: "SMTP MAILER" <[email protected]>
 +
Subject: Mail Delivery Problem
 +
To: "owner-ietf" <owner-ietf>
  
 +
----Reason for mail failure follows----
 +
Sending mail to recipient(s) Nakassis :
 +
  Couldn't make final delivery.
  
 +
%MAIL-E-OPENOUT, error opening USER2:[000000]NAKASSIS.DIR as output
  
Westine & Postel                                             
+
21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)~~
  
RFC 1211              Problems with Mailing Lists            March 1991
+
b.  Case 2
  
 +
Date:  8 Oct 90 20:24:32 EDT
 +
From: "SMTP MAILER" <[email protected]>
 +
Subject: Mail Delivery Problem
 +
To: "owner-ietf" <[email protected]>
  
  b. Case 2
+
----Reason for mail failure follows----
 +
Sending mail to recipient(s) morrisd :
 +
  Couldn't make final delivery.
  
  Date:  8 Oct 90 20:24:32 EDT
+
%MRGATE-E-MRFROMVMS, Error transferring message to Message Router
  From: "SMTP MAILER" <[email protected]>
 
  Subject: Mail Delivery Problem
 
  To: "owner-ietf" <[email protected]>
 
 
 
    ----Reason for mail failure follows----
 
  Sending mail to recipient(s) morrisd :
 
    Couldn't make final delivery.
 
 
 
  %MRGATE-E-MRFROMVMS, Error transferring message to Message Router
 
  
 
************************************************************************
 
************************************************************************
Line 2,318: Line 1,858:
 
F.31.  Unknown ".ARPA" Hosts Without Updated Hostname
 
F.31.  Unknown ".ARPA" Hosts Without Updated Hostname
  
  WHATHOST and DIG show nothing for DCA-EMS.ARPA.  There is no referral
+
WHATHOST and DIG show nothing for DCA-EMS.ARPA.  There is no referral
  to the new hostname.  "WHOIS" DCA-EMS came up with the new hostname.
+
to the new hostname.  "WHOIS" DCA-EMS came up with the new hostname.
 
 
  From: [email protected] (Mail Delivery Subsystem)
 
  Subject: Returned mail: Deferred: Host Name Lookup Failure
 
  Posted-Date: Tue, 13 Nov 90 15:59:34 -0800
 
 
 
 
      ----- Transcript of session follows -----
 
 
    [email protected]... Host unknown
 
 
 
  westine 45% whathost dca-ems.arpa
 
  Unknown Host: dca-ems.arpa, errno 0, h_errno 1 : Unknown host
 
 
 
23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)~~
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
  
 +
From: [email protected] (Mail Delivery Subsystem)
 +
Subject: Returned mail: Deferred: Host Name Lookup Failure
 +
Posted-Date: Tue, 13 Nov 90 15:59:34 -0800
 +
  
 +
  ----- Transcript of session follows -----
 +
 +
  [email protected]... Host unknown
  
Westine & Postel                                             
+
westine 45% whathost dca-ems.arpa
 +
Unknown Host: dca-ems.arpa, errno 0, h_errno 1 : Unknown host
  
RFC 1211              Problems with Mailing Lists            March 1991
+
21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)~~
  
 +
westine 44% whois dca-ems
 +
Defense Communications Agency (DCA) (DCA-EMS)
 +
  Office Automation Division
 +
  Code H610
 +
  Washington, DC 20305-2000
  
   westine 44% whois dca-ems
+
   Hostname: DCA-EMS.DCA.MIL
  Defense Communications Agency (DCA) (DCA-EMS)
+
  Address: 26.1.0.76
      Office Automation Division
+
  System: BBN-C/70 running UNIX
      Code H610
 
      Washington, DC 20305-2000
 
  
      Hostname: DCA-EMS.DCA.MIL
+
  Host Administrator:
       Address: 26.1.0.76
+
       Wilkinson, Avis D. (ADW)  AWilkins@DDN-CONUS.DDN.MIL
       System: BBN-C/70 running UNIX
+
       (703) 848-4867
  
      Host Administrator:
+
  DCA-EMS.DCA.MIL users send E-Mail to AWilkins@DCA-EMS.DCA.MIL
        Wilkinson, Avis D. (ADW)  AWilkins@DDN-CONUS.DDN.MIL
 
        (703) 848-4867
 
  
      DCA-EMS.DCA.MIL users send E-Mail to [email protected]
+
  Record last updated on 10-Sep-90.
 
 
      Record last updated on 10-Sep-90.
 
  
 
************************************************************************
 
************************************************************************
Line 2,379: Line 1,897:
 
F.32.  Messages From an Internet Relay to Commercial Mail Systems
 
F.32.  Messages From an Internet Relay to Commercial Mail Systems
  
  a.  Message Too Large
+
a.  Message Too Large
 
 
  Date: 13 Feb 91 04:15:22 EST
 
  From: Electronic Postmaster <[email protected]>
 
  To: Ann Westine <[email protected]>
 
  Subject: Undeliverable message
 
 
 
 
 
  Re: ? EMDITB - Mail Delivery Failure. Message too large.
 
        >EPX [74360,3202]
 
 
 
  Internet Monthly Report
 
 
 
  Your message could not be delivered as addressed.
 
 
 
  --- Returned message ---
 
 
 
23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)~~
 
 
 
 
 
 
 
  
 +
Date: 13 Feb 91 04:15:22 EST
 +
From: Electronic Postmaster <[email protected]>
 +
To: Ann Westine <[email protected]>
 +
Subject: Undeliverable message
  
 +
Re: ? EMDITB - Mail Delivery Failure. Message too large.
 +
    >EPX [74360,3202]
  
 +
Internet Monthly Report
  
 +
Your message could not be delivered as addressed.
  
 +
--- Returned message ---
  
 +
21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)~~
  
 +
b.  Invalid Parameters
  
Westine & Postel                                             
+
Date: 13 Feb 91 05:34 UT
 +
From: "X.400 Gateway" <[email protected]>
 +
Subject: MHS NonDelivery Report
 +
  
RFC 1211              Problems with Mailing Lists            March 1991
+
Report from domain /PRMD=/ADMD=telemail/C=us/:
  
 
+
FAILED delivery to:
  b.  Invalid Parameters
 
 
 
  Date: 13 Feb 91 05:34 UT
 
  From: "X.400 Gateway" <[email protected]>
 
  Subject: MHS NonDelivery Report
 
 
 
 
  Report from domain /PRMD=/ADMD=telemail/C=us/:
 
 
 
  FAILED delivery to:
 
  
 
   1 Recipient ORName:
 
   1 Recipient ORName:
 
/PN=tony.y.mazraani/DD.TS=SM55/O=SPRINTINTL/ADMD=TELEMAIL/C=US/
 
/PN=tony.y.mazraani/DD.TS=SM55/O=SPRINTINTL/ADMD=TELEMAIL/C=US/
    Translates to:
+
Translates to:
 
/PN=tony.y.mazraani/DD.TS=SM55/O=SPRINTINTL/ADMD=TELEMAIL/C=US
 
/PN=tony.y.mazraani/DD.TS=SM55/O=SPRINTINTL/ADMD=TELEMAIL/C=US
                                                        /@sprint.com
+
                                                      /@sprint.com
    Reason: unable to transfer
+
Reason: unable to transfer
    Diagnostic: invalid parameters
+
Diagnostic: invalid parameters
 
 
23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)~~
 
 
 
  c.  Looping
 
 
 
 
 
  Subject: Delivery Report (failure) for
 
            [email protected]
 
  Message-Type: Delivery Report
 
  Date: Wed, 12 Dec 1990 15:34:41 +0000
 
  Content-Identifier: Why WAN multi...
 
 
 
  This report relates to your message: Why WAN multi...
 
          of Wed, 12 Dec 1990 15:22:56 +0000
 
 
 
  Your message was not delivered to
 
          [email protected] for the following reason:
 
          Message looping detected (please contact local administrator)
 
  
  *** The following information is directed towards the local
+
21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)~~
  *** administrator and is not intended for the end user
 
  *
 
  * DR generated by mta pilot.cs.wisc.edu
 
  *        in /PRMD=xnren/ADMD= /C=us/
 
  *        at Wed, 12 Dec 1990 15:34:35 +0000
 
  *
 
  * Converted to RFC 822 at pilot.cs.wisc.edu
 
  *        at Wed, 12 Dec 1990 15:34:41 +0000
 
  *
 
  
 +
c.  Looping
  
 +
 +
 +
Subject: Delivery Report (failure) for
 +
        [email protected]
 +
Message-Type: Delivery Report
 +
Date: Wed, 12 Dec 1990 15:34:41 +0000
 +
Content-Identifier: Why WAN multi...
  
Westine & Postel                                             
+
This report relates to your message: Why WAN multi...
 +
        of Wed, 12 Dec 1990 15:22:56 +0000
  
RFC 1211              Problems with Mailing Lists            March 1991
+
Your message was not delivered to
 +
        [email protected] for the following reason:
 +
        Message looping detected (please contact local administrator)
  
 +
*** The following information is directed towards the local
 +
*** administrator and is not intended for the end user
 +
*
 +
* DR generated by mta pilot.cs.wisc.edu
 +
*        in /PRMD=xnren/ADMD= /C=us/
 +
*        at Wed, 12 Dec 1990 15:34:35 +0000
 +
*
 +
* Converted to RFC 822 at pilot.cs.wisc.edu
 +
*        at Wed, 12 Dec 1990 15:34:41 +0000
 +
*
  
  * Delivery Report Contents:
+
* Delivery Report Contents:
  *
+
*
  * Subject-Submission-Identifier: [/PRMD=xnren/ADMD=
+
* Subject-Submission-Identifier: [/PRMD=xnren/ADMD=
  /C=us/;<[email protected]]
+
  * Content-Identifier: Why WAN multi...
+
* Content-Identifier: Why WAN multi...
  * Subject-Intermediate-Trace-Information:  /PRMD=xnren/ADMD= /C=us/;
+
* Subject-Intermediate-Trace-Information:  /PRMD=xnren/ADMD= /C=us/;
  *          arrival Wed, 12 Dec 1990 15:22:56 +0000 action Relayed
+
*          arrival Wed, 12 Dec 1990 15:22:56 +0000 action Relayed
  * Subject-Intermediate-Trace-Information:  /PRMD=xnren/ADMD= /C=us/;
+
* Subject-Intermediate-Trace-Information:  /PRMD=xnren/ADMD= /C=us/;
  *          arrival Wed, 12 Dec 1990 15:22:47 +0000 action Relayed
+
*          arrival Wed, 12 Dec 1990 15:22:47 +0000 action Relayed
  * Subject-Intermediate-Trace-Information:  /PRMD=xnren/ADMD= /C=us/;
+
* Subject-Intermediate-Trace-Information:  /PRMD=xnren/ADMD= /C=us/;
  *          arrival Wed, 12 Dec 1990 15:21:48 +0000 action Relayed
+
*          arrival Wed, 12 Dec 1990 15:21:48 +0000 action Relayed
  * Subject-Intermediate-Trace-Information:  /PRMD=xnren/ADMD= /C=us/;
+
* Subject-Intermediate-Trace-Information:  /PRMD=xnren/ADMD= /C=us/;
  *          arrival Wed, 12 Dec 1990 11:05:55 +0000 action Relayed
+
*          arrival Wed, 12 Dec 1990 11:05:55 +0000 action Relayed
  * Subject-Intermediate-Trace-Information:  /PRMD=xnren/ADMD= /C=us/;
+
* Subject-Intermediate-Trace-Information:  /PRMD=xnren/ADMD= /C=us/;
  *          arrival Wed, 12 Dec 1990 11:05:46 +0000 action Relayed
+
*          arrival Wed, 12 Dec 1990 11:05:46 +0000 action Relayed
  * Subject-Intermediate-Trace-Information:  /PRMD=xnren/ADMD= /C=us/;
+
* Subject-Intermediate-Trace-Information:  /PRMD=xnren/ADMD= /C=us/;
  *          arrival Wed, 12 Dec 1990 15:22:57 +0000 action Relayed
+
*          arrival Wed, 12 Dec 1990 15:22:57 +0000 action Relayed
  * Subject-Intermediate-Trace-Information:  /PRMD=xnren/ADMD= /C=us/;
+
* Subject-Intermediate-Trace-Information:  /PRMD=xnren/ADMD= /C=us/;
  *          arrival Wed, 12 Dec 1990 11:04:50 +0000 action Relayed
+
*          arrival Wed, 12 Dec 1990 11:04:50 +0000 action Relayed
  * Recipient-Info: [email protected],
+
* Recipient-Info: [email protected],
  *        /G=Allan/S=Cargille/OU=cs/O=uw-madison/PRMD=xnren/ADMD=
+
*        /G=Allan/S=Cargille/OU=cs/O=uw-madison/PRMD=xnren/ADMD=
  *        /C=us/;
+
*        /C=us/;
  *        FAILURE reason Unable-To-Transfer (1);
+
*        FAILURE reason Unable-To-Transfer (1);
  *        diagnostic Loop-Detected (3);
+
*        diagnostic Loop-Detected (3);
  *        last trace () Wed, 12 Dec 1990 11:04:50 +0000;
+
*        last trace () Wed, 12 Dec 1990 11:04:50 +0000;
  
  ****** End of administration information
+
****** End of administration information
  
 
************************************************************************
 
************************************************************************
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
Westine & Postel                                             
 
 
RFC 1211              Problems with Mailing Lists            March 1991
 
 
  
 
F.33.  Incomplete DNS Data on Host
 
F.33.  Incomplete DNS Data on Host
  
  Date: Fri, 14 Dec 90 19:37:51 -0500
+
Date: Fri, 14 Dec 90 19:37:51 -0500
  From: Mail Delivery Subsystem <[email protected]>
+
From: Mail Delivery Subsystem <[email protected]>
+
  Subject: Returned mail: Host unknown
+
Subject: Returned mail: Host unknown
  
      ----- Transcript of session follows -----
+
  ----- Transcript of session follows -----
  550 megasys.com (TCP)... 550 Host unknown
+
550 megasys.com (TCP)... 550 Host unknown
  550 <[email protected]>... Host unknown (Valid name but no data
+
550 <[email protected]>... Host unknown (Valid name but no data
      [address])
+
    [address])
  
 +
westine 27% dig megasys.com any
  
  westine 27% dig megasys.com any
+
; <<>> DiG <<>> megasys.com any
 +
;; ->>HEADER<<- opcode: QUERY , status: NOERROR, id: 6
 +
;; flags: qr rd ra  Ques: 1, Ans: 2, Auth: 2, Addit: 3
  
  ; <<>> DiG <<>> megasys.com any
+
;; QUESTIONS:
  ;; ->>HEADER<<- opcode: QUERY , status: NOERROR, id: 6
+
;;     megasys.com, type = ANY, class = IN
  ;; flags: qr rd ra  Ques: 1, Ans: 2, Auth: 2, Addit: 3
 
  
  ;; QUESTIONS:
+
;; ANSWERS:
   ;;      megasys.com, type = ANY, class = IN
+
megasys.com    IN      NS      UUNET.UU.NET   ; 172786
 +
megasys.com     IN     NS      seismo.CSS.GOV  ; 172786
  
  ;; ANSWERS:
+
;; AUTHORITY RECORDS:
  megasys.com     IN      NS      UUNET.UU.NET    ; 172786
+
MEGASYS.COM     IN      NS      UUNET.UU.NET    ; 172786
  megasys.com     IN      NS      seismo.CSS.GOV  ; 172786
+
MEGASYS.COM     IN      NS      seismo.CSS.GOV  ; 172786
  
  ;; AUTHORITY RECORDS:
+
;; ADDITIONAL RECORDS:
  MEGASYS.COM    IN      NS      UUNET.UU.NET    ; 172786
+
UUNET.UU.NET    IN      A      192.48.96.2    ; 447968
  MEGASYS.COM    IN      NS      seismo.CSS.GOV  ; 172786
+
UUNET.UU.NET    IN      A      137.39.1.2      ; 170920
 
+
seismo.CSS.GOV  IN      A      192.12.141.25  ; 172786
  ;; ADDITIONAL RECORDS:
 
  UUNET.UU.NET    IN      A      192.48.96.2    ; 447968
 
  UUNET.UU.NET    IN      A      137.39.1.2      ; 170920
 
  seismo.CSS.GOV  IN      A      192.12.141.25  ; 172786
 
  
 
************************************************************************
 
************************************************************************
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
Westine & Postel                                             
 
 
RFC 1211              Problems with Mailing Lists            March 1991
 
 
  
 
F.34.  Sublist Problem
 
F.34.  Sublist Problem
  
+
  Posted-Date: Mon, 17 Dec 90 12:28:23 EST
+
Posted-Date: Mon, 17 Dec 90 12:28:23 EST
  Received: from gimme.math.ufl.edu by venera.isi.edu (5.61/5.61+local)
+
Received: from gimme.math.ufl.edu by venera.isi.edu (5.61/5.61+local)
          id <AA15131>; Mon, 17 Dec 90 09:28:24 -0800
+
        id <AA15131>; Mon, 17 Dec 90 09:28:24 -0800
  Received:  by gimme.math.ufl.edu (4.1/4.03)
+
Received:  by gimme.math.ufl.edu (4.1/4.03)
          id AA05948; Mon, 17 Dec 90 12:28:23 EST
+
        id AA05948; Mon, 17 Dec 90 12:28:23 EST
  Date: Mon, 17 Dec 90 12:28:23 EST
+
Date: Mon, 17 Dec 90 12:28:23 EST
+
  Subject: here we go again: please release me, let me go...
+
Subject: here we go again: please release me, let me go...
  
 +
Fifth time now(?) I try this every couple of months now,
 +
figuring you may be hoplesslly backed up.
  
  Fifth time now(?) I try this every couple of months now,
+
Can you remove me from the ietf list? I may be there as
  figuring you may be hoplesslly backed up.
+
either:
  
  Can you remove me from the ietf list?  I may be there as
+
        [email protected]
  either:
+
or
 +
        [email protected]
  
          [email protected]
+
I would appreciate a confirmation message: I'm ready to use
  or
+
crontab for these mailings.
          [email protected].edu
 
  
  I would appreciate a confirmation message: I'm ready to use
+
Many Thanks,
  crontab for these mailings.
 
  
  Many Thanks,
+
Randy Fischer
  
  Randy Fischer
+
21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)~~
  
23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)~~
+
 +
 +
 +
Subject: Re: here we go again: please release me, let me go...
 +
In-reply-to: Your message of Mon, 17 Dec 90 12:28:23 -0500.
 +
            <[email protected]>
 +
Date: Mon, 17 Dec 90 10:15:36 PST
 +
From: Ann Westine <[email protected]>
  
+
Hi Randy,
 
  Reply-To: [email protected]
 
  Subject: Re: here we go again: please release me, let me go...
 
  In-reply-to: Your message of Mon, 17 Dec 90 12:28:23 -0500.
 
                <[email protected]>
 
  Date: Mon, 17 Dec 90 10:15:36 PST
 
  From: Ann Westine <[email protected]>
 
  
  Hi Randy,
+
I remember your request, and I also remember telling you that you are
 +
not on our list (at least individually).  There is an exploder
 +
"[email protected]" maintained at UFL.EDU.  You need to check with
 +
the postmaster to see if you are on their list.  If this is not the
 +
case, here are the only other addresses I have from UFL.EDU
  
  I remember your request, and I also remember telling you that you are
+
  not on our list (at least individually). There is an exploder
+
esj@UFL.EDU,
  "netadm@MATH.UFL.EDU" maintained at UFL.EDU. You need to check with
+
FCLA@NERVM.NERDC.UFL.EDU,
  the postmaster to see if you are on their list. If this is not the
+
netadm@MATH.UFL.EDU,
  case, here are the only other addresses I have from UFL.EDU
+
POKE@NERVM.NERDC.UFL.EDU,
  
 +
There is another possibility, perhaps you have a pointer to a mailbox
 +
somewhere else?
  
 +
Regards,
 +
Ann
  
Westine & Postel                                             
+
21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)~~
  
RFC 1211              Problems with Mailing Lists            March 1991
+
From: Operator <[email protected]>
 +
 +
Subject: re: done at last: please release me, let me go...
  
 +
Many, many thanks for the reply: I did not, somehow, see your
 +
previous reply -- perhaps you forwarded it to someone at UFL.EDU
 +
instead of MATH.UFL.EDU?  Or I missed it in the flow of mail I am
 +
trying to abate.
 +
No matter.
  
  ceben@NERVM.NERDC.UFL.EDU,
+
At any rate "netadm@math.ufl.edu" is indeed a local exploder, aliased
  esj@UFL.EDU,
+
at the moment to myself and one of my assistants. It is local to the
  FCLA@NERVM.NERDC.UFL.EDU,
+
"math.ufl.edu" subdomain, and not to "ufl.edu" as your records
  netadm@MATH.UFL.EDU,
+
indicate. I am the postmaster of the "math.ufl.edu", and you should
  POKE@NERVM.NERDC.UFL.EDU,
+
be able to verify "math.ufl.edu" has an MX record pointing to
 +
"mathlab.math.ufl.edu". I am therefore mailing to you as root from
 +
that machine.
  
  There is another possibility, perhaps you have a pointer to a mailbox
+
Please remove "[email protected]" from your list.  I have quite
  somewhere else?
+
enjoyed the discussions,  but the volume been overwhelming.
  
  Regards,
+
Thanks very much for your prompt reply,
  Ann
+
Appreciatively,
  
23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)~~
+
 
 
  From: Operator <[email protected]>
 
 
  Subject: re: done at last: please release me, let me go...
 
 
 
  Many, many thanks for the reply: I did not, somehow, see your
 
  previous reply -- perhaps you forwarded it to someone at UFL.EDU
 
  instead of MATH.UFL.EDU?  Or I missed it in the flow of mail I am
 
  trying to abate.
 
  No matter.
 
 
 
  At any rate "[email protected]" is indeed a local exploder, aliased
 
  at the moment to myself and one of my assistants.  It is local to the
 
  "math.ufl.edu" subdomain, and not to "ufl.edu" as your records
 
  indicate.  I am the postmaster of the "math.ufl.edu", and you should
 
  be able to verify "math.ufl.edu" has an MX record pointing to
 
  "mathlab.math.ufl.edu".  I am therefore mailing to you as root from
 
  that machine.
 
 
 
  Please remove "[email protected]" from your list.  I have quite
 
  enjoyed the discussions,  but the volume been overwhelming.
 
 
 
  Thanks very much for your prompt reply,
 
  Appreciatively,
 
 
 
 
  
 
************************************************************************
 
************************************************************************
  
 +
F.35.  File Protection Problem
  
 +
From: "Raj Jain, LKG1-2/A19, DTN: 226-7642, 508-486-7642
 +
      09-Feb-1991 0904"
 +
 +
 +
Subject: Request to add to IETF
  
 +
I seem to have suddenly dropped off the IETF distribution list. I
 +
have not received any IETF mail since 9-Jan-91. Could you please
 +
ensure that I am still in the distribution list.
  
 +
-Raj Jain
  
 +
21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)~~
  
 +
To: "Raj Jain, LKG1-2/A19, DTN: 226-7642,
 +
    508-486-7642 09-Feb-1991 0904" <[email protected]>
 +
cc: [email protected], ietf-request
 +
 +
Subject: Re: Request to add to IETF
 +
In-reply-to: Your message of Sat, 09 Feb 91 06:07:15 -0800.
 +
            <[email protected]>
 +
Date: Tue, 12 Feb 91 11:17:41 PST
 +
From: Ann Westine <[email protected]>
  
 +
Hi Raj,
  
 +
I will readd you to the IETF list.  However, if I receive more error
 +
messages like this, then I must take your name off the list again.
 +
I've sent messages to the postmaster at DEC but the problem isn't
 +
corrected.  Your address isn't the only one, there's CALLON and a few
 +
others.
  
 +
Maybe you can check into this.  Here's the header from one of the
 +
many error messages I received.
  
Westine & Postel                                             
+
Regards, --Ann
  
RFC 1211              Problems with Mailing Lists            March 1991
+
   Date: Wed, 9 Jan 91 17:04:41 -0800
 
+
  From: MAILER-DAEMON@decwrl.dec.com (Mail Delivery Subsystem)
 
+
  Subject: Returned mail: User unknown
F.35.  File Protection Problem
 
 
 
   From: "Raj Jain, LKG1-2/A19, DTN: 226-7642, 508-486-7642
 
          09-Feb-1991 0904"
 
  <jain@erlang.enet.dec.com>
 
  
  Subject: Request to add to IETF
 
  
  I seem to have suddenly dropped off the IETF distribution list. I
+
      ----- Transcript of session follows -----
  have not received any IETF mail since 9-Jan-91. Could you please
+
   mail11: Error from DECnet MAIL object on node "erlang",
  ensure that I am still in the distribution list.
+
          during mail delivery to <ERLANG::JAIN>.
 
+
          Remote error code is 0x7e81fa, message is:
  -Raj Jain
+
   %MAIL-E-OPENOUT, error opening !AS as output
 
+
   -RMS-E-PRV, insufficient privilege or file protection violation
23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)~~
+
          (can't decypher error code)
 
+
   550 <jain@ERLANG.DEC.COM>... User unknown
  To: "Raj Jain, LKG1-2/A19, DTN: 226-7642,
 
      508-486-7642 09-Feb-1991 0904" <[email protected]>
 
   cc: [email protected], ietf-request
 
  Reply-To: [email protected]
 
  Subject: Re: Request to add to IETF
 
  In-reply-to: Your message of Sat, 09 Feb 91 06:07:15 -0800.
 
                <[email protected]>
 
  Date: Tue, 12 Feb 91 11:17:41 PST
 
   From: Ann Westine <[email protected]>
 
 
 
  Hi Raj,
 
 
 
  I will readd you to the IETF list.  However, if I receive more error
 
   messages like this, then I must take your name off the list again.
 
  I've sent messages to the postmaster at DEC but the problem isn't
 
   corrected. Your address isn't the only one, there's CALLON and a few
 
  others.
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
Westine & Postel                                             
 
 
 
RFC 1211              Problems with Mailing Lists            March 1991
 
 
 
 
 
  Maybe you can check into this. Here's the header from one of the
 
  many error messages I received.
 
 
 
  Regards, --Ann
 
 
 
      Date: Wed, 9 Jan 91 17:04:41 -0800
 
      From: MAILER-DAEMON@decwrl.dec.com (Mail Delivery Subsystem)
 
      Subject: Returned mail: User unknown
 
      To: [email protected]
 
  
 +
      ----- Recipients of this delivery -----
 +
  <[email protected]> (bounced)
  
        ----- Transcript of session follows -----
+
21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)~~
      mail11: Error from DECnet MAIL object on node "erlang",
 
              during mail delivery to <ERLANG::JAIN>.
 
              Remote error code is 0x7e81fa, message is:
 
      %MAIL-E-OPENOUT, error opening !AS as output
 
      -RMS-E-PRV, insufficient privilege or file protection violation
 
              (can't decypher error code)
 
      550 <[email protected]>... User unknown
 
  
        ----- Recipients of this delivery -----
+
Date: Tue, 12 Feb 91 17:54:20 EST
      <jain@ERLANG.DEC.COM> (bounced)
+
From: "Raj Jain, LKG1-2/A19, DTN: 226-7642, 508-486-7642
 +
      12-Feb-1991 1751"
 +
<jain@erlang.enet.dec.com>
 +
 +
Subject: Re: Request to add to IETF
  
23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)~~
+
The error message that you sent is unfortunately my mistake and has
 
+
nothing to do with DECWRL. One day I reset protection on all my files
  Date: Tue, 12 Feb 91 17:54:20 EST
+
and directories and didn't realize that even the system did not have
  From: "Raj Jain, LKG1-2/A19, DTN: 226-7642, 508-486-7642
+
the privilege to write mail messages on my disk. I discovered it only
          12-Feb-1991 1751"
+
after several people sent phone messages to me. Thanks for adding my
+
name again. I will try to be careful.  -Raj
 
  Subject: Re: Request to add to IETF
 
 
 
  The error message that you sent is unfortunately my mistake and has
 
  nothing to do with DECWRL. One day I reset protection on all my files
 
  and directories and didn't realize that even the system did not have
 
  the privilege to write mail messages on my disk. I discovered it only
 
  after several people sent phone messages to me. Thanks for adding my
 
  name again. I will try to be careful.  -Raj
 
  
 
************************************************************************
 
************************************************************************
 
 
 
 
 
 
 
 
 
 
 
Westine & Postel                                             
 
 
RFC 1211              Problems with Mailing Lists            March 1991
 
 
  
 
F.36.  User Unknown
 
F.36.  User Unknown
  
  a.  Request to be Readded to IETF List
+
a.  Request to be Readded to IETF List
  
  Date: Mon, 11 Feb 91 10:03:54 PST
+
Date: Mon, 11 Feb 91 10:03:54 PST
  From: "Paul Ciarfella DTN 227-3548 Outside 508 952-3548
+
From: "Paul Ciarfella DTN 227-3548 Outside 508 952-3548
        11-Feb-1991 1301"
+
      11-Feb-1991 1301"
+
+
  Subject: add me to the ietf list (again)
+
Subject: add me to the ietf list (again)
  
  Hi -
+
Hi -
  
  Could I be added to the ietf distribution list (again). I must have
+
Could I be added to the ietf distribution list (again). I must have
  been dropped from the list somehow.  This happened to me before the
+
been dropped from the list somehow.  This happened to me before the
  last ietf - I had to get my name reregistered then, too.
+
last ietf - I had to get my name reregistered then, too.
  
  Thanks,
+
Thanks,
  
  Paul Ciarfella [email protected]
+
Paul Ciarfella [email protected]
 
 
23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)~~
 
 
 
  b.  Message to User Regarding Readd and Previous Problems
 
 
 
  To: "Paul Ciarfella DTN 227-3548 Outside 508 952-3548  11-Feb-1991
 
      1301" <[email protected]>
 
 
  Reply-To: [email protected]
 
  Subject: Re: add me to the ietf list (again)
 
  In-Reply-To: Your message of Mon, 11 Feb 91 10:03:54 -0800.
 
                <[email protected]>
 
  Date: Wed, 13 Feb 91 11:05:46 PST
 
  From: Ann Westine <[email protected]>
 
 
 
  Hi Paul,
 
 
 
  Every couple of months I have lots of error messags from several
 
  individual mailboxes on ENET.DEC.COM.  Here is a typical one.  Since
 
  I cannot reach you I am forced to delete your mailbox.
 
 
 
  I have sent several messages to the postmaster at DEC but nothing has
 
  been corrected.  Perhaps you can look into this.
 
 
 
  --Ann
 
 
 
 
 
 
 
 
 
 
 
 
 
Westine & Postel                                             
 
 
 
RFC 1211              Problems with Mailing Lists            March 1991
 
 
 
 
 
      Return-Path: [email protected]
 
      Received-Date: Tue, 11 Dec 90 19:53:19 PST
 
      Received: from venera.isi.edu by zephyr.isi.edu (4.1/4.0.3-4)
 
              id <AA11360>; Tue, 11 Dec 90 19:53:19 PST
 
      Posted-Date: Tue, 11 Dec 90 19:42:03 -0800
 
      Received: from decpa.pa.dec.com by venera.isi.edu
 
              (5.61/5.61+local)
 
              id <AA08309>; Tue, 11 Dec 90 19:53:17 -0800
 
      Received: by decpa.pa.dec.com; id AA12106; Tue, 11 Dec 90 19:42:03
 
      Date: Tue, 11 Dec 90 19:42:03 -0800
 
      From: [email protected] (Mail Delivery Subsystem)
 
      Subject: Returned mail: User unknown
 
      Message-Id: <[email protected]>
 
      To: [email protected]
 
 
 
        ----- Transcript of session follows -----
 
      mail11: input timeout reading remote object
 
      get_status: Connection timed out
 
      (temporary failure)
 
 
 
      mail11: Error from DECnet MAIL object on node "levers",
 
              during mail delivery to <LEVERS::CIARFELLA>.
 
              Remote error code is 0x7e81fa, message is:
 
      %MAIL-E-OPENOUT, error opening !AS as output
 
      -RMS-E-CRE, ACP file create failed
 
      -SYSTEM-W-DIRALLOC, allocation failure on directory file
 
              (can't decypher error code)
 
      550 <[email protected]>... User unknown
 
 
 
        ----- Recipients of this delivery -----
 
      <[email protected]> (queued, will retry)
 
      <[email protected]> (bounced)
 
      <[email protected]> (sent)
 
 
 
23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)23:47, 22 September 2020 (UTC)~~
 
  
 +
21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)~~
  
 +
b.  Message to User Regarding Readd and Previous Problems
  
 +
To: "Paul Ciarfella DTN 227-3548 Outside 508 952-3548  11-Feb-1991
 +
    1301" <[email protected]>
 +
 +
 +
Subject: Re: add me to the ietf list (again)
 +
In-Reply-To: Your message of Mon, 11 Feb 91 10:03:54 -0800.
 +
            <[email protected]>
 +
Date: Wed, 13 Feb 91 11:05:46 PST
 +
From: Ann Westine <[email protected]>
  
 +
Hi Paul,
  
 +
Every couple of months I have lots of error messags from several
 +
individual mailboxes on ENET.DEC.COM.  Here is a typical one.  Since
 +
I cannot reach you I am forced to delete your mailbox.
  
 +
I have sent several messages to the postmaster at DEC but nothing has
 +
been corrected.  Perhaps you can look into this.
  
 +
--Ann
  
 +
  Return-Path: [email protected]
 +
  Received-Date: Tue, 11 Dec 90 19:53:19 PST
 +
  Received: from venera.isi.edu by zephyr.isi.edu (4.1/4.0.3-4)
 +
          id <AA11360>; Tue, 11 Dec 90 19:53:19 PST
 +
  Posted-Date: Tue, 11 Dec 90 19:42:03 -0800
 +
  Received: from decpa.pa.dec.com by venera.isi.edu
 +
          (5.61/5.61+local)
 +
          id <AA08309>; Tue, 11 Dec 90 19:53:17 -0800
 +
  Received: by decpa.pa.dec.com; id AA12106; Tue, 11 Dec 90 19:42:03
 +
  Date: Tue, 11 Dec 90 19:42:03 -0800
 +
  From: [email protected] (Mail Delivery Subsystem)
 +
  Subject: Returned mail: User unknown
 +
  Message-Id: <[email protected]>
 +
  
 +
      ----- Transcript of session follows -----
 +
  mail11: input timeout reading remote object
 +
  get_status: Connection timed out
 +
  (temporary failure)
  
 +
  mail11: Error from DECnet MAIL object on node "levers",
 +
          during mail delivery to <LEVERS::CIARFELLA>.
 +
          Remote error code is 0x7e81fa, message is:
 +
  %MAIL-E-OPENOUT, error opening !AS as output
 +
  -RMS-E-CRE, ACP file create failed
 +
  -SYSTEM-W-DIRALLOC, allocation failure on directory file
 +
          (can't decypher error code)
 +
  550 <[email protected]>... User unknown
  
 +
      ----- Recipients of this delivery -----
 +
  <[email protected]> (queued, will retry)
 +
  <[email protected]> (bounced)
 +
  <[email protected]> (sent)
  
 +
21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)~~
  
 +
c.  Response from User Regarding Problem
  
 +
Return-Path: [email protected]
 +
Received-Date: Wed, 13 Feb 91 13:51:25 PST
 +
Received: from venera.isi.edu by zephyr.isi.edu (4.1/4.0.3-4)
 +
        id <AA26215>; Wed, 13 Feb 91 13:51:25 PST
 +
Posted-Date: Wed, 13 Feb 91 13:51:02 PST
 +
Received: from decpa.pa.dec.com by venera.isi.edu (5.61/5.61+local)
 +
        id <AA04585>; Wed, 13 Feb 91 13:51:22 -0800
 +
Received: by decpa.pa.dec.com; id AA14420; Wed, 13
 +
          Feb 91 13:51:00 -0800
 +
Received: from levers.enet; by decwrl.enet; Wed, 13 Feb 91 13:51:02 PST
 +
Date: Wed, 13 Feb 91 13:51:02 PST
 +
From: "I'll die for my country but I won't kill for Texaco
 +
13-Feb-1991 1641"
 +
 +
 +
Subject: re: add me to the ietf list (again)
  
 +
Hi Ann,
  
Westine & Postel                                             
+
Could we try another address for me?  The old address has been
 
+
plagued by disk problems which might explain why the mail is not
RFC 1211              Problems with Mailing Lists            March 1991
+
getting delivered.
 
 
 
 
  c.  Response from User Regarding Problem
 
 
 
  Return-Path: [email protected]
 
  Received-Date: Wed, 13 Feb 91 13:51:25 PST
 
  Received: from venera.isi.edu by zephyr.isi.edu (4.1/4.0.3-4)
 
          id <AA26215>; Wed, 13 Feb 91 13:51:25 PST
 
  Posted-Date: Wed, 13 Feb 91 13:51:02 PST
 
  Received: from decpa.pa.dec.com by venera.isi.edu (5.61/5.61+local)
 
          id <AA04585>; Wed, 13 Feb 91 13:51:22 -0800
 
  Received: by decpa.pa.dec.com; id AA14420; Wed, 13
 
            Feb 91 13:51:00 -0800
 
  Received: from levers.enet; by decwrl.enet; Wed, 13 Feb 91 13:51:02 PST
 
  Date: Wed, 13 Feb 91 13:51:02 PST
 
  From: "I'll die for my country but I won't kill for Texaco
 
  13-Feb-1991 1641"
 
 
 
  Subject: re: add me to the ietf list (again)
 
 
 
  Hi Ann,
 
 
 
  Could we try another address for me?  The old address has been
 
  plagued by disk problems which might explain why the mail is not
 
  getting delivered.
 
  
  The new address to register is:
+
The new address to register is:
  
+
  
  I will check into the problem on this end.  Sorry about the tone of
+
I will check into the problem on this end.  Sorry about the tone of
  my first message but this has been a never-ending problem for over 8
+
my first message but this has been a never-ending problem for over 8
  months.
+
months.
  
  Thank you,
+
Thank you,
  
  Paul C
+
Paul C
  
 
************************************************************************
 
************************************************************************
  
5.  Security Considerations
+
== Security Considerations ==
 
 
  Security issues are not discussed in this memo.
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
Westine & Postel                                             
 
 
 
RFC 1211              Problems with Mailing Lists            March 1991
 
 
 
 
 
6.  Authors' Addresses
 
 
 
  Ann Westine
 
  USC - Information Sciences Institute
 
  4676 Admiralty Way
 
  Marina del Rey, CA 90292-6695
 
 
 
  Phone: 213-822-1511
 
 
 
 
 
 
 
 
  Jon Postel
 
  USC - Information Sciences Institute
 
  4676 Admiralty Way
 
  Marina del Rey, CA 90292-6695
 
 
 
  Phone: 213-822-1511
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
  
 +
Security issues are not discussed in this memo.
  
 +
== Authors' Addresses ==
  
 +
Ann Westine
 +
USC - Information Sciences Institute
 +
4676 Admiralty Way
 +
Marina del Rey, CA 90292-6695
  
 +
Phone: 213-822-1511
  
 +
  
 +
Jon Postel
 +
USC - Information Sciences Institute
 +
4676 Admiralty Way
 +
Marina del Rey, CA 90292-6695
  
 +
Phone: 213-822-1511
  
Westine & Postel
+
EMail: Postel@ISI.EDU

Revision as of 21:26, 29 September 2020

Network Working Group A. Westine Request for Comments: 1211 J. Postel

                                                                 ISI
                                                          March 1991
      Problems with the Maintenance of Large Mailing Lists

Status of this Memo

This RFC discusses problems with maintaining large mailing lists, especially the processing of error reports. This memo provides information for the Internet community. It does not specify an Internet standard. Distribution of this memo is unlimited.

Table of Contents

1. Introduction.............................................. 1 2. Discussion................................................ 1 3. Typical Problems.......................................... 3 3.1. Misdirected Error Reports................................. 3 3.2. Sublists.................................................. 3 3.3. Misdirected Requests...................................... 5 3.4. Misdirected Messages...................................... 5 4. Summary................................................... 5 APPENDIX A - I used to be on the List.......................... 6 APPENDIX B - Changing Addresses and Sublists................... 8 APPENDIX C - Sublists and Other Protocol Worlds................ 9 APPENDIX D - Errors from Hidden Hosts.......................... 10 APPENDIX E - No Postmaster..................................... 12 APPENDIX F - Examples of Error Messages........................ 14 5. Security Considerations................................... 53 6. Authors' Addresses........................................ 54

Introduction

Maintaining large mailing lists, especially the processing of error reports, poses many problems. Most of the examples come from the experience of managing the Internet Engineering Task Force (IETF) mailing list. Many examples are presented in this memo. Most of the specific problems shown have already been corrected.

Discussion

At USC - Information Sciences Institute (ISI) we maintain mailing lists for the Internet Research Groups, the IETF, and other Internet groups; about 25 lists altogether. We receive about 400 messages a month requesting additions or deletions to these lists. There are

about 20 messages a day requesting changes to the lists.

We also receive about 300 error messages a month due to mail delivery problems. Many of these are duplicates, but the net result is that about 10 cases per day need to be investigated.

Many of the error reports are for "soft errors", primarily delayed delivery notices, such as "not delivered for 2 days, will try for 3 more days". These just waste the list maintainer's time and are otherwise ignored. This is especially wasteful when such messages are repeated every day. However, if the same host is a cause of such messages for many days in a row, the list maintainer may investigate.

Please note that ignoring the soft errors is not always easy, since error messages often contain error reports on several mailboxes, requiring the error message to be read carefully to pick out the hard errors.

The error reports that indicate hard errors, such as "no such user" require the list maintainer to take action. In many cases the appropriate action is to simply delete the user mailbox from the list. However, if the mailbox in question is someone known to be active as a working group chair, or such, further investigation is necessary. The more general case of "no such host" may be a temporary condition, but if it continues for several days it must be investigated.

Since the error conditions do not have standardized names (for example, "no such user" vs. "user unknown") it is sometimes difficult to understand whether a soft or hard error is being reported, and what one should do about it. For example, what does "Can't Find Mail Center!" mean, or what should one do about "mailll:%MAIL-E-OPENOUT, error opening SYS$USER2:[STGEORGE.LONGMAIL]MAIL$00040093BE236612.MAI; as outputI)"?

The first step in investigating a problem with a user mailbox is to see if it is on the list. If so, the next step is to see if there really is a problem with it. This is done by using the SMTP VRFY and EXPN features, Finger, or Whois. This often develops information suggesting that the user has recently changed his address. This has to be confirmed through an exchange of messages (with the postmaster) and then the mailing list must be updated.

If the user is not on the list, then it is likely the mail is sent via an exploder or sublist. So the investigation focuses on finding which exploder may be involved, usually this is found by looking at the path (from the received lines) of the error report. The exploder that is the source of the error can sometimes be checked using the

SMTP EXPN feature. Then the postmaster is notified.

If the error report is about a host being unknown, the programs "whathost", "dig", "ping", and "traceroute" may be used to find the problem. However, getting the problem fixed may require communication with host and domain administrators.

What to do if problems can't be resolved: Delete the offending entry from the list that may eventually cause the following response: "I used to be on the ietf list, how come I am not getting the messages any more?" (See Appendix A.)

Typical Problems

In this section we discuss typical and frequent problems that occur with large mailing lists.

Misdirected Error Reports

The most frequent problem is that error reports are sent to the author of the message rather than the list owner. One way this can happen is when there is trouble with the author's host not connecting to another host along the route before it reaches ISI where the mailing list is.

At ISI the SMTP "from" information is added when the message is distributed to the list so that hosts following the SMTP protocol will send their error reports to the list owner. However, not all hosts do this properly.

Another problem is that some machines do not pay attention to the SMTP information about where to send error reports.

Sublists

What is a sublist? It is a mailbox with an alias-name that expands to a mailing-list or group of recipients. There are many sublists on our mailing lists.

When a user requests that a mailbox be added to a list that looks like an exploder, the following message is sent:

  We ask that all list maintainters of exploder mailboxes (an
  alias-name that expands to a mailing-list or group of recipients)
  set up some sort of ownership at their site, for their list.  What
  this means is, is any mailbox on your list is invalid, the error
  message will go to you (the list owner), and you can delete that
  mailbox from your list.
  An example of an entry in your aliases file would be:
     owner-ietf-local:  [email protected],
        (or your list maintainer/postmaster)

It appears that few people understand the concept of list ownership, or they do not set it up correctly. There is ample evidence of problems in this area.

When investigating "user unknown" messages it is often the case that the user is not individually listed on our list. The next step is to check received lines and hunt for an exploder list with a host similar to the one that the error came from or points to. At that point we attempt to use SMTP EXPN or VRFY to check that the user is on a sublist. Since many hosts do not implement EXPN or VRFY, the result of our check is inconclusive. We then contact the list maintainer and ask him to delete the invalid mailbox if it is on his sublist.

Another problem occurs when someone on a sublist wants to change the name of his mailbox. We look through the main list to make the correction and if that mailbox is not on the list we check the received lines and look for clues to determine which host this user may be on. More than likely it is a sublist. (See Appendix B.)

When the mailbox is in another protocol world (like UUCP or BITNET) there are often problems with the handling and direction of error reports. (See Appendix C.)

Sometimes we are unable to find the addresses reported in the error message on the mailing list in question. In such a case we check the mailing list for a host name also named in the received lines of a message in error. If we find a match then we look for an exploder on that host and expand the sublist there to see if the mailbox in question is on that sublist. (See Appendix D.)

At the time a sublist is entered into our list we record the name of the requestor and consider him the sublist owner. As people change roles or companies this contact sometimes fails, in that case we fall back to contacting the postmaster. However, not every site has a "postmaster" mailbox. (See Appendix E.)

Most users send their requests and changes to the IETF-Request mailbox, when they are on, in fact, a sublist, usually at their own company. This creates a problem for us trying to determine which exploder they're on.

In this case, the request message is forwarded to the sublist owner so he can make changes to his list. However, sometimes hosts may be somewhat similar in name (from the same organization, but in a different department, in a different building, off campus, etc.) and it's hard to know if this person should really be on that particular sublist, or listed individually. Occasionally, we examine the main file to see if there are individual addresses that could be incorporated in a sublist.

Misdirected Requests

Some users don't know that mailing lists usually have a "request" mailbox, so they mistakenly send their requests to the main list. When this happens, several people will resend the request to the list maintainer and then want to know if the request was completed.

Misdirected Messages

There are also messages that go to the request mailbox when they are intended for the main list. These messages get forwarded to the main list and a message is sent to the user notifying him of the correction and the proper way to address his message.

Summary

Running a mailing list should be easy, and with small lists it is. The number of changes and errors are small and infrequent. But when lists get large and traffic gets heavy, the number of changes and errors grow to many a day. The level of effort to manage a mailing list of substantial size and use becomes significant.

An additional problem is the creativity shown by mail program developers in inventing numerous different error reports. We present a large sample of such messages in Appendix F. We hope that these examples will be of help to other mailing list maintainers.

Our experience with maintaining large lists suggests the following:

Users: Please be considerate and try to work problems out locally.

Sublist owners: Please do everything you can to get the error messages related to your sublist to go to you. Please try to get users on your system to talk to you about additions and deletions.

                            APPENDIX A

A.1. Inquiry Message From User Regarding His Mailbox

Date: Tue, 6 Nov 90 03:02:09 PST From: "Stewart Bryant, RE02-G/H2, DTN: 830 4682"

     <[email protected]>

To: [email protected] Subject: dist list

Please will you check that I have not been deleted from this distribution list.

My email address is : [email protected]

Thanks

Stewart

21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)~~

A.2. Message To User - His Mailbox Was Re-added

To: "Stewart Bryant, RE02-G/H2,

   DTN: 830 4682" <[email protected]>

cc: [email protected] Reply-To: [email protected] Subject: Re: dist list In-reply-to: Your message of Tue, 06 Nov 90 03:02:09 -0800.

            <[email protected]>

Date: Tue, 06 Nov 90 13:54:23 PST From: Ann Westine <[email protected]>

Hi Stewart,

> Please will you check that I have not been deleted from this > distribution. list. > > My email address is: [email protected]

       I readded you to the list.

--Ann

21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)~~

A.3. User Name Readded and It Bounced

Date: Tue, 06 Nov 90 17:25:15 -0800 From: [email protected] (Mail Delivery Subsystem) To: [email protected] Subject: Returned mail: User unknown

   ----- Transcript of session follows -----

mail11: Error from DECnet MAIL object on node "janus",

        during mail delivery to <JANUS::BRYANT>.
        Remote error code is 0x7e81d2, message is:

%MAIL-E-ERRACTRNS, error activating transport NM

        (can't decypher error code)

550 <[email protected]>... User unknown

  ----- Recipients of this delivery -----

<[email protected]> (bounced)

  ----- Unsent message follows -----

Received: by decpa.pa.dec.com; id AA21747; Tue, 6 Nov 90 13:54:38 Received: from LOCALHOST by venera.isi.edu (5.61/5.61+local)

        id <AA24660>; Tue, 6 Nov 90 13:54:25 -0800

To: "Stewart Bryant, RE02-G/H2,

    DTN: 830 4682" <[email protected]>

Cc: [email protected] Reply-To: [email protected] Subject: Re: dist list In-Reply-To: Your message of Tue, 06 Nov 90 03:02:09 -0800.

     <[email protected]>

Date: Tue, 06 Nov 90 13:54:23 PST From: Ann Westine <[email protected]>

Hi Stewart,

> Please will you check that I have not been deleted from this > distribution list. > > My email address is > > [email protected]

I readded you to the list.

--Ann

                           APPENDIX B

In this example, the old mailbox "[email protected]" was to be deleted and the new mailbox "[email protected]" was to be added. However, when checking the mailing list the old address was not found. Further checking for anything that resembled the hostname still did not turn up anything. Then checking the full header information of the sender's message showed that the message came through UUNET.UU.NET. There is a sublist on UUNET called "[email protected]". By using the SMTP feature EXPN on the sublist the mailbox was found in the form "ssbell!kent". Finally, a message was sent to the postmaster at UUNET and asked him to delete the mailbox.

21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)~~

B.1. Error Report

Date: Mon, 22 Oct 90 14:05:38 -0500 From: [email protected] (Kent Landfield) To: [email protected] Subject: E-mail address change

Hello,

I am currently receiving ietf related email at [email protected]. I am moving to sparky.IMD.Sterling.COM as the ssbell system is going away. Could you please change my address to [email protected] so that I can stay on the list ? Thanks.

21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)~~

B.2. Message Sent to Postmaster

To: [email protected] Subject: Address - <ssbell!kent> Date: Thu, 25 Oct 90 13:44:24 PDT From: Ann Westine <[email protected]>

Hi,

Please delete the mailbox ssbell!kent from the "post-ietf" list. I will add his new address "[email protected]" directly to the ietf list. Thanks. Ann

                          APPENDIX C

Another problem comes up when a sublist happens to be located in another protocol world such as BITNET or UUCP and that mail is forwarded through a mail relay. Experience shows that proper implementation of the list ownership concept is even less likely.

SIGNET is a host in the UUCP world receiving mail forwarded through the mail relay THINK.COM.

21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)~~

C.1. Error Report

To: [email protected] Date: Fri, 05 Oct 90 23:45:26 -0400 From: [email protected] Subject: Warning From uucp

We have been unable to contact machine 'signet' since you queued your job.

       mail signet!ietf-interest    (Date 10/04)

Attempts will continue for a few more days.

       Sincerely,
       early-bird!uucp

21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)~~

C.2. Message Sent to Postmaster

To: [email protected] Subject: unable to contact machine 'signet' Reply-To: [email protected] Date: Mon, 08 Oct 90 09:42:54 PDT From: Ann Westine <[email protected]>

Hi,

We have a mailbox on the ietf list that gets relayed through your host THINK.COM. We will have to delete this mailbox if a connection cannot be corrected. Thanks, Ann

                           APPENDIX D

Sometimes, the addresses reported in error can't be found on the IETF list. In this example, "GATORCORP" is not on the IETF list. In checking the received lines there is a host called VITALINK.COM. We have an exploder on our list at VITALINK called "ietf- [email protected]". The program DIG shows that VITALINK.COM MXs to UUNET.UU.NET. Since VITALINK is not directly on the Internet the EXPN and VRFY features of SMTP don't apply, the sublist on VITALINK can't be checked. However, there are enough clues to make an educated guess that the mailboxes on the host GATORCORP are on the exploder sublist at VITALINK. In this situation a message was sent to the Postmaster of VITALINK.COM to ask him to delete the invalid addresses from his sublist.

21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)~~

D.1. Error Report

Return-Path: [email protected] Received-Date: Wed, 7 Nov 90 14:34:51 PST Received: from venera.isi.edu by zephyr.isi.edu (4.1/4.0.3-4)

       id <AA16502>; Wed, 7 Nov 90 14:34:51 PST

Posted-Date: Wed, 7 Nov 90 13:54:08 -0800 Received: from UUNET.UU.NET by venera.isi.edu (5.61/5.61+local)

       id <AA27149>; Wed, 7 Nov 90 14:34:34 -0800

Received: from vitam6.UUCP by uunet.uu.net (5.61/1.14) with UUCP

       id AA12926; Wed, 7 Nov 90 17:34:28 -0500

Received: by vitam6.ENG.Vitalink.COM (5.61/1.35)

       id AC03235; Wed, 7 Nov 90 13:54:08 -0800

Date: Wed, 7 Nov 90 13:54:08 -0800 From: [email protected] (Mail Delivery Subsystem) Subject: Returned mail: Host unknown To: [email protected] To: [email protected]

  ----- Transcript of session follows -----

550 andrew_greenfield.safari@gatorcorp,

   [email protected] unknown

21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)~~

D.2. Message Sent to Postmaster

To: [email protected] Cc: [email protected] Subject: andrew_greenfield.safari@gatorcorp,

        melinda_le_baron.safari@gatorcorp... Host unknown

Reply-To: [email protected] Date: Thu, 08 Nov 90 15:30:24 PST From: Ann Westine <[email protected]>

Hi,

We have an exploder mailbox on the IETF list called "[email protected]". I'm not sure, but I think the following addresses may be on that list. Please look into this "host unknown" problem. If these addresses need to be deleted, please do so.

Thanks, Ann

                           APPENDIX E

Every host on the Internet that processes mail is required to have a "postmaster" mailbox to receive error reports and trouble inquiries. In this case, the "postmaster" mailbox was not recognized.

E.1. Message Sent to IETF-Request

To: ([email protected]) From: Caralyn Brown (CBROWN@ENR) Date: 10 Jan 91 8:24 AM Subject: please remove me from this list

Please remove me from this list. I'm changing companies and I'd like to keep the mailbox from getting out of hand. If it's not too much trouble, could you just send me a confirmation that I was deleted? Thanks.

caralyn

21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)~~

E.2. Message Sent to Postmaster

To: [email protected] Cc: [email protected], [email protected] Subject: Please delete from "[email protected]" - Carolyn Brown Reply-To: [email protected] Date: Thu, 10 Jan 91 09:50:15 PST From: Ann Westine <[email protected]>

Hi,

Please delete Carolyn from your sublist. We do not have her address listed individually on the main IETF list.

Thanks, Ann

21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)~~

E.3. Error Report

From: [email protected] (List Service version

     1.0.x463)

Subject: returned mail Message-Type: Return To: <[email protected]>

Your mail addressed to "postmaster" could not be processed: There is no mailing list named "postmaster" at this site.

For help, send to [email protected]; to receive an index of available lists, send to [email protected]; to reach a List Administrator, send to [email protected].

            APPENDIX F - Examples of Error Messages

F.1. Delayed Delivery Notices

From: [email protected] (Mail Delivery Subsystem) Subject: Returned mail: Deferred: Connection timed out during user

        open with uiucdcsm-uiuc-dcs-net.cs.uiuc.edu

Posted-Date: Fri, 4 Jan 91 12:46:51 -0800 Received: by venera.isi.edu (5.61/5.61+local)

       id <AA08435>; Fri, 4 Jan 91 12:46:51 -0800

To: [email protected]

  ----- Transcript of session follows -----

>>> RCPT To:<[email protected]> <<< 550 (USER) Unknown user name in "[email protected]" 550 [email protected]... User unknown 451 [email protected]... reply: read error [email protected]... reply: read error 421 dockmaster.ncsc.mil.tcp... Deferred: Connection timed out during

   user open with DOCKMASTER.NCSC.MIL

421 va.nkw.ac.uk.tcp... Deferred: Connection timed out during

   user open with nsfnet-relay.ac.uk

421 nsl.dec.com.tcp... Deferred: Connection timed out during user

   open with jove.pa.dec.com

451 [email protected]... timeout waiting for input

   [email protected]... timeout waiting for input

451 [email protected]... reply: read error

   [email protected]... reply: read error

421 sccgate.scc.com.tcp... Deferred: Connection timed out during

   user open with sccgate.scc.com

421 a.isi.edu.tcp... Deferred: Connection refused by a.ISI.EDU 421 cs.ucl.ac.uk.tcp... Deferred: Connection timed out during user

   open with nsfnet-relay.ac.uk

421 oasys.dt.navy.mil.tcp... Deferred: Connection timed out during

   user open with oasys.dt.navy.mil

421 peocu1.navy.mil.tcp... Deferred: Connection timed out during user

   open with PEOCU1.NAVY.MIL

421 enh.nist.gov.tcp... Deferred: Connection timed out during user

   open with enh.nist.gov

421 mickey.imsd.contel.com.tcp... Deferred: Connection refused by

   MICKEY.IMSD.CONTEL.COM

421 uv4.eglin.af.mil.tcp..Deferred: Connection timed out during user

   open with uv6.eglin.af.mil

421 ima.isc.com.tcp... Deferred: Connection timed out during user

   open with ima.ima.isc.com

421 huachuca-emh8.army.mil.tcp... Deferred: Connection refused by

   HUACHUCA-EMH8.ARMY.MIL

421 vaxa.nerc-keyworth.ac.uk.tcp... Deferred: Connection timed out

   during user open with nsfnet-relay.ac.uk

421 gdr.bath.ac.uk.tcp... Deferred: Connection timed out during user

   open with nsfnet-relay.ac.uk

421 ccint1.rsre.mod.uk.tcp... Deferred: Connection timed out during

   user open with ccint1.rsre.mod.uk

550 [email protected]... Host unknown 421 hqafsc-vax.af.mil.tcp... Deferred: Connection timed out during

   user open with HQAFSC-VAX.AF.MIL

421 nic.nordu.net.tcp... Deferred: Connection timed out during user

   open with nic.nordu.net

421 aedc-vax.af.mil.tcp... Deferred: Connection timed out during user

   open with AEDC-VAX.AF.MIL

421 letterkenn-emh1.army.mil.tcp... Deferred: Connection timed out

   during user open with LETTERKENN-EMH1.ARMY.MIL

421 dumle.kommhuset.se.tcp... Deferred: Connection timed out during

   user open with sunic.sunet.se

421 cis.uab.edu.tcp... Deferred: Connection timed out during user

   open with cisa.CIS.UAB.EDU

421 server.af.mil.tcp... Deferred: Connection timed out during user

   open with server.af.mil

421 issun3.stc.nl.tcp... Deferred: Connection timed out during user

   open with issun3.stc.nl

421 cs.uiuc.edu.tcp... Deferred: Connection timed out during user

   open with uiucdcsm-uiuc-dcs-net.cs.uiuc.edu
          -------------

F.2. Failed Mail

Date: Tue, 30 Oct 90 5:00:40 EST From: BBN Mail System (MMDF) <[email protected]> Sender: [email protected] Subject: Failed mail (msg.aa09055) To: [email protected]

After 12 days (276 hours), your message could not be fully delivered.

It failed to be received by the following address(es):

   [email protected] (host: cc5.bbn.com) (queue: smtp)

Problems usually are due to service interruptions at the receiving machine. Less often, they are caused by the communication system.

F.3. Waiting Mail

To: RELAY Mail System (MMDF) <[email protected]> Cc: owner-ietf <@RELAY.CS.NET:[email protected]> Reply-To: [email protected] Subject: Re: Waiting mail (msg.aa00720) In-Reply-To: Your message of Tue, 02 Oct 90 07:45:14 -0400.

            <[email protected]>

Date: Mon, 08 Oct 90 10:11:03 PDT From: Ann Westine <[email protected]>

> After 5 days (105 hours), your message has not yet been > fully delivered. Attempts to deliver the message will continue > for 2 more days. No further action is required by you. > > Delivery attempts are still pending for the following address(es): > > @zix.gmd.dbp.de:[email protected] > (host: zix.gmd.dbp.de)(queue: dfn) > > Problems usually are due to service interruptions at the receiving > machine. Less often, they are caused by the communication system.

F.4. What Started Out as a Sublist with No Active Users

a. Error Report

Date: Tue, 4 Sep 90 22:13:12 +0200 From: [email protected] (Mail Delivery Subsystem) Subject: Returned mail: User unknown To: owner-ietf

  ----- Transcript of session follows -----

While talking to mailhost.Gipsi.FR: >>> RCPT To:<[email protected]> <<< 550 <[email protected]>... User unknown 550 <[email protected]>... User unknown

          ----------

21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)~~

b. Message Sent to Postmaster

TO: [email protected] Subject: 550 <[email protected]>... User unknown Reply-To: [email protected] Date: Tue, 11 Sep 90 09:56:20 PDT From: Ann Westine <[email protected]>

Hi,

I have received numerous error messages like this for over a week. There appears to be a mailbox on your exploder that is invalid, please delete it.

Thanks, --Ann

21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)~~

c. Reply From Postmaster

From: [email protected] (Edmonde Duteurtre) To: westine In-Reply-To: Ann Westine's message of Tue,

            11 Sep 90 09:56:20 PDT

<[email protected]> Subject: 550 <[email protected]>... User unknown

Hello

On our site, the [email protected], [email protected], [email protected] and the [email protected] mailed only one person: [email protected] but this person has leaved our company, and you should cancel this addresses.

I think we get enough informations through the news. I think you should cancel us ([email protected]) on the mailing list ietf.

F.5. Sublists without local ownership

In this error message there was not much to go on except the words IETF and the name of the host from where the mailer-daemon sent the error. Using that clue the mailing list was searched for that host name (SATURN). It was a sublist. It appears that there is something internally wrong with the sublist and this error should have gone to the postmaster or owner of the [email protected] list instead of the IETF owner. A message was sent to the postmaster. No reply was received, but the condition was fixed.

21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)~~

a. Error Report

Date: Wed, 3 Oct 90 14:42:57 EDT From: MAILER-DAEMON%[email protected] (Mail Delivery

                                                Subsystem)

Subject: Returned mail: unknown mailer error 13 To: <[email protected]>

  ----- Transcript of session follows -----

/p/news/ietf/21770: Permission denied 554 "| /usr/local/news -s ietf"... unknown mailer error 13

21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)~~

b. Message Sent to Postmaster

To: [email protected] cc: ietf-request Reply-To: [email protected] Subject: 554 "| /usr/local/news -s ietf"

   ... unknown mailer error 13

In-reply-to: Your message of Wed, 03 Oct 90 14:42:57 -0400.

     <[email protected]>

Date: Mon, 08 Oct 90 10:53:02 PDT From: Ann Westine <[email protected]>

Hi,

Please fix the problem with the following mailbox "[email protected]".

Thanks, Ann

F.6. Repetitive Error Every Couple of Months from Same Host

a. Message Dated August 90

Date: Tue, 21 Aug 90 09:21:26 -0700 From: [email protected] (Mail Delivery Subsystem) Subject: Returned mail: Host unknown To: <@decpa.pa.dec.com:[email protected]>

  ----- Transcript of session follows -----

mail11: connect: Connect failed, Unrecognized object (permanent failure)

554 <netrix::gillin>... 550 Host unknown (Authoritative

 answer from name server)
  ----- Recipients of this delivery -----

<erlang::chiu> (sent) <netrix::gillin> (bounced) <erlang::rama> (sent)

21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)~~

b. Message Dated October 90

Date: Mon, 29 Oct 90 05:02:53 -0800 From: [email protected] (Mail Delivery Subsystem) Subject: Returned mail: Host unknown To: <@decpa.pa.dec.com:[email protected]>

  ----- Transcript of session follows -----

mail11: Error from DECnet MAIL object on node "erlang",

       during mail delivery to <ERLANG::CHIU>.
       Remote error code is 0x7e803a, message is:

%MAIL-E-LOGLINK, error creating network link to node CHIU -SYSTEM-F-NOSUCHNODE, remote node is unknown 554 <erlang::chiu>... 550 Host unknown (Authoritative

 answer from name server)
  ----- Recipients of this delivery -----

<erlang::chiu> (bounced) <netrix::gillin> (sent) <erlang::rama> (sent)

21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)~~

c. Message Dated December 90

Date: Sun, 16 Dec 90 21:40:47 -0800 From: [email protected] (Mail Delivery Subsystem) Subject: Returned mail: Host unknown To: [email protected]

  ----- Transcript of session follows -----

mail11: connect: Connect failed, Unrecognized object (permanent failure)

554 <[email protected]>... 550 Host unknown (Authoritative answer from name server)

  ----- Recipients of this delivery -----

<[email protected]> (bounced)

21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)~~

d. Message Dated December 90

Date: Sun, 16 Dec 90 23:01:21 -0800 From: [email protected] (Mail Delivery Subsystem) Subject: Returned mail: Host unknown To: [email protected]

  ----- Transcript of session follows -----

mail11: connect: Connect failed, Unrecognized object (permanent failure)

554 <gillin%[email protected]>... 550 Host unknown (Authoritative answer from name server)

  ----- Recipients of this delivery -----

<[email protected]> (sent) mogul@acetes (sent) <gillin%[email protected]> (bounced) <chiu%[email protected]> (sent)

21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)~~

e. Message Dated January 91

Date: Sun, 6 Jan 91 17:05:53 -0800 From: [email protected] (Mail Delivery Subsystem) Subject: Returned mail: User unknown To: [email protected]

  ----- Transcript of session follows -----

mail11: Error from DECnet MAIL object on node "bigfut",

 during mail delivery to <BIGFUT::CALLON>.
 Remote error code is 0x7e81fa, message is:(can't decypher error
 code)

550 <[email protected]>... User unknown

F.7. Host Unknown or Sublist

The address "lucb-ml@OPUS" is not an Internet style domain name. The exploder [email protected] has this address on its sublist, and CSA.McGILL.CA does not recognize this host. (This error should have gone to the sublist owner at CS.MCGILL.CA).

Date: Tue, 9 Oct 90 19:45:14 -0400 From: Mail Delivery Subsystem <[email protected]> Subject: Returned mail: Host unknown To: <[email protected]>

  ----- Transcript of session follows -----

550 "Luc Boulianne" <lucb-ml@opus>... Host unknown

F.8. "HOST UNKNOWN" and the Host Really Is Known

Usually a "host unknown" report is not acted on unless it is repeated over a period of several days. In many cases the hosts really do exist, but they're just down for a couple of days, or there are network problems reaching it (or it's name serrver).

Date: Fri, 2 Nov 90 08:45:56 -0800 From: [email protected] (Mail Delivery Subsystem) Subject: Returned mail: Host unknown To: [email protected]

       ----- Transcript of session follows -----
 550 nrc.com.tcp... 550 Host unknown
 550 [email protected]... Host unknown

21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)~~

WHATHOST CHECK

       westine 28%  whathost nrc.com
       Host: nrc.com  ==>  129.216.200.51
       westine 82% whathost 129.216.200.51
       Host: aztec.NRC.COM  ==>  129.216.200.51

F.9. Host Unknown and MXed to Another Host.

DNS says AMES will forward mail for ADAPT, but mailer at AMES says ADAPT is unknown. Should ask postmaster at AMES to fix either mailer or DNS data.

Date: Wed, 31 Oct 90 09:39:35 PST From: [email protected] Subject: Returned mail: Host unknown To: [email protected]

  ----- Transcript of session follows -----

bad system name: ADAPT uux failed ( 68 ) 550 [email protected]... Host unknown

21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)~~

westine 86% dig adapt.net.com any

<<>> DiG <<>> adapt.net.com any
->>HEADER<<- opcode
QUERY , status
NOERROR, id: 6
flags
qr aa rd ra Ques: 1, Ans: 2, Auth: 0, Addit: 2
QUESTIONS
adapt.net.com, type = ANY, class = IN
ANSWERS

adapt.net.com IN MX 10 ames.arc.nasa.gov ; 84029 adapt.net.com IN MX 20 tymix.tymnet.com ; 84029

ADDITIONAL RECORDS

ames.arc.nasa.gov IN A 128.102.18.3 ; 158777 tymix.tymnet.com IN A 131.146.2.1 ; 86400

F.10. User Unknown

Most "User Unknown" error messages listed individually on the main list get deleted. Those on a sublist, require a message to the postmaster or list maintainer. They are asked to delete the invalid user mailbox from their local list.

F.10.1. Add User but Address Fails

This is a case where the recipient was checking to see if his mailbox was already on the list and if not to readd him. He was readded to the list. A "user unknown" error message was received on the confirming message that was sent notifying recipient that he had been added.

21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)~~

a. Message Sent to User And Postmaster

To: [email protected], [email protected] Cc: westine, [email protected] Subject: RE: <[email protected]> Date: Wed, 07 Nov 90 10:15:40 PST From: Ann Westine <[email protected]>

Hi Stewart and Postmaster,

I readded your name to the IETF list but there seems to be problems with connections to DECnet hosts right now. I have seen lots of errors like this lately. Postmaster, please check into this. JANUS is not the only host with an error, there are other hosts like this in trouble.

For example.

   From: [email protected] (Mail Delivery Subsystem)
   Subject: Returned mail: Host unknown
   To: <@decpa.pa.dec.com:[email protected]>
       ----- Transcript of session follows -----
   mail11: Error from DECnet MAIL object on node "erlang",
            during mail delivery to <ERLANG::CHIU>.
            Remote error code is 0x7e803a, message is:
   %MAIL-E-LOGLINK, error creating network link to node CHIU
   -SYSTEM-F-NOSUCHNODE, remote node is unknown
   554 <erlang::chiu>... 550 Host unknown (Authoritative answer
          from name server)
       ----- Recipients of this delivery -----
    <erlang::chiu> (bounced)
    <netrix::gillin> (sent)
    <erlang::rama> (sent)
            -------
   Thank you, Ann
        To: "Stewart Bryant, RE02-G/H2,
            DTN: 830 4682" <[email protected]>
        Cc: [email protected]
        Subject: Re: dist list
        In-Reply-To: Your message of Tue, 06 Nov 90 03:02:09 0800.
                   <[email protected]>
        Date: Tue, 06 Nov 90 13:54:23 PST
        From: Ann Westine <[email protected]>
        Hi Stewart,
        > Please will you check that I have not been deleted
        > from this distribution list.
        >
        > My email address is > [email protected]
     I readded you to the list.  Thanks, Ann
        ------- Forwarded Message
        Date:    Tue, 06 Nov 90 17:25:15 -0800
        From:    [email protected]
        To:      [email protected]
        Subject: Returned mail: User unknown
           ----- Transcript of session follows -----
        mail11: Error from DECnet MAIL object on node "janus",
                during mail delivery to <JANUS::BRYANT>.
                Remote error code is 0x7e81d2, message is:
        %MAIL-E-ERRACTRNS, error activating transport NM
                (can't decypher error code)
           550 <[email protected]>... User unknown
            ----- Recipients of this delivery -----
        <[email protected]> (bounced)

21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)~~

b. Message From Postmaster

Return-path: [email protected] Date: Wed, 07 Nov 90 16:24:37 PST To: [email protected] cc: [email protected], [email protected],

        [email protected]

Subject: Re: <[email protected]> From: Paul A Vixie <[email protected]>

Anne,

This was a transient. Please let me know if any other .enet.dec.com nodes are still unreachable.

Paul

21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)~~

c. Another Message to Postmaster

To: Paul A Vixie <[email protected]> cc: [email protected], [email protected],

   [email protected]

Reply-To: [email protected] Subject: Re: <[email protected]> In-reply-to: Your message of Wed, 07 Nov 90 16:24:37 -0800.

   <[email protected]>

Date: Thu, 08 Nov 90 11:23:39 PST From: Ann Westine <[email protected]>

Hi Paul,

There are a few other error message that I received last week and they seem to reoccur every couple of months. Here is an example. What does this error mean?

Date: Mon, 29 Oct 90 05:02:53 -0800 From: [email protected] (Mail Delivery Subsystem) Subject: Returned mail: Host unknown To: <@decpa.pa.dec.com:[email protected]>

  ----- Transcript of session follows -----

mail11: Error from DECnet MAIL object on node "erlang",

       during mail delivery to <ERLANG::CHIU>.
       Remote error code is 0x7e803a, message is:

%MAIL-E-LOGLINK, error creating network link to node CHIU -SYSTEM-F-NOSUCHNODE, remote node is unknown

554 <erlang::chiu>... 550 Host unknown (Authoritative

 answer from name server)
  ----- Recipients of this delivery -----

<erlang::chiu> (bounced) <netrix::gillin> (sent) <erlang::rama> (sent) <netrix::gillin> (sent) <erlang::rama> (sent)

          ----------

21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)~~

d. Message From Postmaster

Date: Thu, 08 Nov 90 17:10:02 PST To: [email protected] Subject: Re: <[email protected]> From: Paul A Vixie <[email protected]>

Anne,

This error:

       ----- Transcript of session follows -----
    mail11: Error from DECnet MAIL object on node "erlang",
            during mail delivery to <ERLANG::CHIU>.
            Remote error code is 0x7e803a, message is:
    %MAIL-E-LOGLINK, error creating network link to node CHIU
    -SYSTEM-F-NOSUCHNODE, remote node is unknown
    554 <erlang::chiu>... 550 Host unknown (Authoritative
                      answer from name server)
...means that the person on ERLANG:: has forwarded their mail to a

system that ERLANG does not know about. Decnet mail is not store-and- forward, so decwrl (as smtp-to-decnet gateway) sees the end-system error. Trying to be helpful, it sends it back to you.

My advice is to delete any addresses you have trouble with, if they are in the .enet.dec.com subdomain.

paul

F.10.2. No Such User

Date: Wed, 10 Oct 90 18:05 CDT From: PMDF Mail Server <[email protected]> Subject: Undeliverable mail To: [email protected]

The message could not be delivered to:

Addressee: gale Reason:

 %MAIL-E-NOSUCHUSR, no such user GALE at node CRCVMS

F.11. No Transcript

Date: Wed, 8 Aug 90 13:21:03 -0700 From: MAILER-DAEMON (Mail Delivery Subsystem) Subject: Returned mail: Deferred: Host Name Lookup Failure To: owner-ietf To: owner-ietf To: westine

                       --------------

<text deleted>

F.12. Looping - Too Many Hops

Date: Wed, 7 Nov 90 18:08:59 PDT From: Mail Delivery Subsystem <[email protected]> Subject: Returned mail: Unable to deliver mail To:<@jessica.stanford.edu,@jessica.stanford.edu,@jessica.stanford.edu,

 @jessica.stanford.edu,@jessica.stanford.edu,@jessica.stanford.edu,
 @jessica.stanford.edu:[email protected]>
  ----- Transcript of session follows -----

554 sendall: too many hops (17 max)

Received: from Jessica.Stanford.EDU by Ahwahnee.Stanford.EDU

  (5.59/inc-1.0) id AA09128; Wed, 7 Nov 90 18:08:36 PDT

Received: from Ahwahnee.Stanford.EDU by jessica.stanford.edu

  (5.59/25-eef) id AA17687; Wed, 7 Nov 90 18:08:31 PDT

Received: from Jessica.Stanford.EDU by Ahwahnee.Stanford.EDU

  (5.59/inc-1.0)id AA09124; Wed, 7 Nov 90 18:08:28 PDT

Received: from Ahwahnee.Stanford.EDU by jessica.stanford.edu

  (5.59/25-eef) id AA17674; Wed, 7 Nov 90 18:08:22 PDT

Received: from Jessica.Stanford.EDU by Ahwahnee.Stanford.EDU

  (5.59/inc-1.0) id AA09120; Wed, 7 Nov 90 18:08:19 PDT

Received: from Ahwahnee.Stanford.EDU by jessica.stanford.edu

  (5.59/25-eef) id AA17658; Wed, 7 Nov 90 18:08:13 PDT

Received: from Jessica.Stanford.EDU by Ahwahnee.Stanford.EDU

  (5.59/inc-1.0) id AA09116; Wed, 7 Nov 90 18:08:11 PDT

Received: from Ahwahnee.Stanford.EDU by jessica.stanford.edu

  (5.59/25-eef) id AA17645; Wed, 7 Nov 90 18:08:05 PDT

Received: from Jessica.Stanford.EDU by Ahwahnee.Stanford.EDU

  (5.59/inc-1.0) id AA09112; Wed, 7 Nov 90 18:08:03 PDT

Received: from VENERA.ISI.EDU by jessica.stanford.edu

  (5.59/25-eef) id AA17625;

Wed, 7 Nov 90 18:07:50 PDT Received: by venera.isi.edu (5.61/5.61+local)

       id <AA29996>; Wed, 7 Nov 90 15:45:49 -0800

Received-Date: Wed, 7 Nov 90 15:45:45 -0800 Received: from NRI.RESTON.VA.US by venera.isi.edu (5.61/5.61+local)

       id <AA29992>; Wed, 7 Nov 90 15:45:45 -0800

Received: from nri by NRI.NRI.Reston.VA.US id aa13139;7 Nov 90 18:26 To: Frank Kastenholz <kasten%[email protected]> Cc: [email protected] Subject: Re: IETF mailing list Date: Wed, 07 Nov 90 18:26:53 -0500 From: [email protected]

F.13. No Postmaster

a. Error Message

Date: Mon, 5 Nov 90 18:40:58 EST From: [email protected] Subject: Returned mail: User unknown To: [email protected]

  ----- Transcript of session follows -----

421 osi3: Host osi3 is down 550 Postmaster... User unknown

21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)~~

b. Checking Hostname and Address

westine 37% dig osi3.ncsl.nist.gov any

QUESTIONS
osi3.ncsl.nist.gov, type = ANY, class = IN
ANSWERS

osi3.ncsl.nist.gov IN A 129.6.48.108 ; 86400 osi3.ncsl.nist.gov IN A 129.6.51.1 ; 86400

21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)~~

c. Checking For Users

westine 49% mconnect OSI3.NCSL.NIST.GOV connecting to host OSI3.NCSL.NIST.GOV (0x6c300681), port 0x1900 connection open 220 osi3.ncsl.nist.gov sendmail 4.0/NIST(rbj/dougm) ready at

 Thu, 8 Nov 90 13:58:49 EST

expn ietf 250-Dale Walters <walters> 250-Richard Colella <[email protected]> 250 Doug Montgomery <[email protected]>

21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)~~

d. Checking For Administrators

westine 44% whois osi3.ncsl.nist.gov National Bureau of Standards (ICST-OSI3)

  Hostname: OSI3.NCSL.NIST.GOV
  Nicknames: OSI3.ICST.NBS.GOV,ICST-OSI3.ARPA
  Address: 129.6.48.108
  System: SUN-3/160 running UNIX
  Coordinator:
     Montgomery, Douglas C.  (DCM5)  [email protected]
     (301) 975-3630
  Record last updated on 17-May-89.

21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)~~

e. Message Sent to Coordinator

From [email protected] Thu Nov 8 13:58:40 1990 Posted-Date: Thu, 08 Nov 90 10:59:30 PST To: [email protected] Cc: [email protected] Subject: RE: 421 osi3: Host osi3 is down

   550 Postmaster... User unknown

Reply-To: [email protected] Date: Thu, 08 Nov 90 10:59:30 PST From: Ann Westine <[email protected]>

Hi Doug,

If the Postmaster is "unknown" please delete him from your exploder list "[email protected]". I have been receiving error messages like this one for several days now. If I don't hear from you, I will have to delete the above mailbox.

Ann

> ----- Transcript of session follows ----- > 421 osi3: Host osi3 is down > 550 Postmaster... User unknown

21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)~~

f. Message From Coordinator

Date: Thu, 8 Nov 90 15:34:02 EST From: Doug Montgomery <[email protected]> Organization: National Institute of Standards and Technology (NIST) Sub-Organization: National Computer Systems Laboratory To: [email protected] Subject: RE: 421 osi3: Host osi3 is down

        550 Postmaster... User unknown

Cc: [email protected]

I think I have found out what is wrong. For some reason (we can discuss this below) your exploder is sending IETF mail to our exploder ([email protected]) through the machine osi.ncsl.nist.gov. Now due to a recent subnet reconfiguration and subsequent lack of update to our DNS servers, the DNS was returning an incorrect address for osi3. Thus IETF mail would be sent to OSI, which would try to forward it to OSI3 (using the wrong address). OSI would think that OSI3 was down and dump the message, trying to

send a notice to Postmaster.  OSI doesn't have an aliase for

Postmaster and thus the second error message that you saw.

These two problems have been fixed on OSI.  Now the question is what

address you have in your distribution list that would cause this mail to go through OSI in the first place. I guess you might have something like "ietf%[email protected]." The other interesting point about your list is that we receive IETF mail to our exploder

directly from venera.
Thus I suspect that there are two entries for OSI3 on your

distribution list. One that gets relayed through OSI and one that points directly to OSI3. If this is the case please deleted

everything except the "[email protected]." address.
If this is not the case or if there are other problems let me know.

21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)~~

g. My Reply Back

Here are all the addresses I have on the IETF list under NIST.GOV.

[email protected], [email protected]

I'll deleted "[email protected]".

Here are two others at NIST

[email protected], [email protected]

By the way, on the following message, it looks like the Mailer-Daemon message went from OSI.ncsl.nist.gov to enh.nist.gov to venera.isi.edu.

--Ann

   Return-Path: [email protected]
   Received-Date: Thu, 8 Nov 90 12:44:11 PST
   Received: from venera.isi.edu by zephyr.isi.edu (4.1/4.0.3-4)
           id <AA19131>; Thu, 8 Nov 90 12:44:11 PST
   Posted-Date: Thu, 8 Nov 90 15:39:54 EST
   Received: from enh.nist.gov by venera.isi.edu (5.61/5.61+local)
           id <AA03448>; Thu, 8 Nov 90 12:44:01 -0800
   Received: from OSI.NCSL.NIST.GOV by ENH.NIST.GOV;
           Thu, 8 Nov 90 15:43 EDT
   Received: by osi.ncsl.nist.gov (4.1/SMI-4.1) id AB14654;
           Thu, 8 Nov 90 15:39:54 EST
   Date: Thu, 8 Nov 90 15:39:54 EST
   From: [email protected]
   Subject: Returned mail: User unknown
   To: [email protected]
   Message-Id: <[email protected]>
   X-Envelope-To: [email protected]
      ----- Transcript of session follows -----
   421 osi3: Host osi3 is down
   550 Postmaster... User unknown
      ----- Unsent message follows -----

21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)~~

h. Another Problem .Forward

From: Doug Montgomery <[email protected]> Organization: National Institute of Standards and Technology (NIST) To: [email protected] Subject: Re: 421 osi3:Host osi3 is down 550 Postmaster.. User unknown

Deleting the [email protected] entry should fix your problems. Mills has a .forward to osi3, thus explaining why IETF mail was going ---> OSI ---> OSI3.

I checked OSI's sendmail.cf and it is relaying through enh. This, though has nothing to do with the previous problem.

I flushed the queue of IETF mail on OSI waiting to go to OSI3. I don't think you should see anymore bounced messages.

Sorry that our local problems were causing you grief .... let me know if it happens again.

F.14. File Over Allocation

Date: Tue, 4 Sep 90 10:35:49 -0700 From: MAILER-DAEMON (Mail Delivery Subsystem) Subject: Returned mail: Deferred: Connection timed out during user

        open with ames.arc.nasa.gov

Posted-Date: Tue, 4 Sep 90 10:35:49 -0700 To: owner-ietf

   ----- Transcript of session follows -----

>>> QUIT <<< 421 sage.acc.com SMTP Service not available:

   insufficient disk space.

451 [email protected]... reply: read error

    [email protected]... reply: read error

F.15. File Deleted

Date: Fri, 10 Aug 90 14:21:57 EDT From: Daemon <[email protected]> Subject: Undeliverable mail To: westine

Mail could not be delivered to the following address(es):

/usr/databases/bugs/[email protected]: No such file

    or directory

F.16. Strange Postmaster

a. Message Forwarded to IETF-Request

Forwarded: Thu, 21 Feb 91 14:31:09 PST Forwarded: westine Forwarded: [email protected] Forwarded: [email protected] Return-Path: [email protected] Received-Date: Sun, 17 Feb 91 17:48:07 PST Received: from venera.isi.edu by zephyr.isi.edu (4.1/4.0.3-4)

       id <AA03679>; Sun, 17 Feb 91 17:48:07 PST

Posted-Date: Sun, 17 Feb 91 20:48:12 -0500 Received: from TIS.COM by venera.isi.edu (5.61/5.61+local)

       id <AA26292>; Sun, 17 Feb 91 17:48:01 -0800

Received: from TIS.COM by TIS.COM (4.1/SUN-5.64DB)

       id AA04098; Sun, 17 Feb 91 20:48:13 EST

Reply-To: James M Galvin <[email protected]> To: [email protected] Subject: Failed Mail to IETF Date: Sun, 17 Feb 91 20:48:12 -0500 From: James M Galvin <[email protected]>


Forwarded Message

Message-ID: <[email protected]> From: [email protected] <[email protected]> To: [email protected] Date: 15 Feb 91 21:28:28 Subject: Can't Find MailCenter!

               <text deleted>

21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)~~

b. Problem Reported to MITRE

To: [email protected] Cc: westine, [email protected] Subject: RE: Can't Find MailCenter! Reply-To: [email protected] Date: Thu, 21 Feb 91 14:31:01 PST From: Ann Westine <[email protected]>

Hi,

We're getting this problem again. Please fix.

Thank you. Ann


Forwarded Message

Date: Sun, 17 Feb 91 20:48:12 -0500 From: James M Galvin <[email protected]> To: [email protected] Subject: Failed Mail to IETF

  ------- Forwarded Message
  Message-ID: <[email protected]>
  From:       [email protected] <[email protected]>
  To:         [email protected]
  Date:       15 Feb 91 21:28:28
  Subject:    Can't Find MailCenter!
  GatorMail-Q                   Re: 1st PRELIMINARY AGENDA/
  Received: by qmgate; 15 Feb 91 21:28:25
  Received: by mbunix.mitre.org (5.57/4.7)
          id AA25128; Fri, 15 Feb 91 21:26:46 EST
  Received: by venera.isi.edu (5.61/5.61+local)
          id <AA17839>; Fri, 15 Feb 91 08:45:12 -0800
  Posted-Date: Fri, 15 Feb 91 11:45:16 -0500
  Received-Date: Fri, 15 Feb 91 08:45:09 -0800
  Received: from TIS.COM by venera.isi.edu (5.61/5.61+local)
          id <AA17833>; Fri, 15 Feb 91 08:45:09 -0800
  Message-Id: <[email protected]>
  Reply-To: James M Galvin <[email protected]>
  To: Megan Davies <[email protected]>
  Cc: [email protected]
  Subject: Re: 1st PRELIMINARY AGENDA/ST. LOUIS
  In-Reply-To: Your message of Thu, 14 Feb 91 17:44:13 EST.
               <[email protected]>
  Date: Fri, 15 Feb 91 11:45:16 -0500
  From: James M Galvin <[email protected]>
                  <text deleted>

F.17. Message Too Large

Date: Wed, 10 Oct 90 17:50:10 MDT From: [email protected] (Mail Delivery Subsystem) Subject: Returned mail: Service unavailable To: <[email protected]>

  ----- Transcript of session follows ----- 554

[email protected]... Message is too large; 50000 bytes max 554 [email protected]... Service unavailable

F.18. Vacation Messages

a. Case 1

Date: Mon, 8 Oct 90 15:28:30 PDT From: David Wasley <[email protected]> Subject: I am away from e-mail This_Message_Brought_To_You_By: the vacation program Apparently-To: [email protected]

I am away from e-mail until October 13. If your message requires immediate attention, please contact one of the people below:

Network problems: Austin Shelton <[email protected]>

Network information: Bill Wells <[email protected]>

 Network installation: Jim Allison <[email protected]> If

you're really desparate, leave me voice-mail at (415) 642-3478. Thanks for your patience! David Wasley, U C Berkeley

21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)~~

b. Case 2

Date: Fri, 2 Nov 90 18:17:12 EST From: [email protected] (Mail Delivery Subsystem) Subject: Returned mail: unknown mailer error 1 To: <[email protected]>

  ----- Transcript of session follows -----

sh: vacation: not found 554 "|vacation farber"... unknown mailer error 1

F.19. LocaL Configuration Errors

Date: Tue, 14 Aug 90 00:36:51 -0400 From: [email protected] Subject: Returned mail: Local configuration error To: <owner-ietf>

  ----- Transcript of session follows -----

554 <[email protected]>,<[email protected]>...

   Local configuration error

F.20. Service Unavailable

Date: Wed, 8 Aug 90 13:00:39 EDT From: [email protected] Subject: Returned mail: Service unavailable To: <owner-ietf>

  ----- Transcript of session follows -----

Connected to eng.clemson.edu: >>> HELO omni <<< 553 omni host name configuration error 554 <[email protected]>... Service unavailable

  ----- Unsent message follows -----

F.21. "Bad File Number"

To: <owner-ietf> From: The UTCS Post Office <[email protected]> Subject: Delivery problems with your mail

Your message has been received by the University of Toronto Computing Services Postal System. A copy of it has been returned to you because of difficulties encountered while attempting to deliver your mail.

The following errors occurred while attempting delivery:

<smtp madhaus.utcs.utoronto.ca [email protected] 1609>:

128.100.102.10: 550 <[email protected]>... User unknown:
Bad file number

F.22. Cannot Append

Date: Sat, 11 Aug 90 14:51:57 PDT From: [email protected] (Mail Delivery Subsystem) Subject: Returned mail: Service unavailable To: [email protected]

  ----- Transcript of session follows -----

mail: /var/spool/mail/cslater: cannot append Mail saved in dead.letter 554 cslater... Service unavailable

F.23. Error Creating Network Link

"erlang::chang... Host unknown"

Date: Thu, 1 Nov 90 12:34:20 -0800 From: [email protected] (Mail Delivery Subsystem) Subject: Returned mail: Deferred To: <@decpa.pa.dec.com:[email protected]>

  ----- Transcript of session follows -----

mail11: Error from DECnet MAIL object on node "erlang",

       during mail delivery to <ERLANG::CHIU>.
       Remote error code is 0x7e803a, message is:

%MAIL-E-LOGLINK, error creating network link to node CHIU -SYSTEM-F-NOSUCHNODE, remote node is unknown 554 <erlang::chiu>... 550 Host unknown (Authoritative answer from

   name server)

mail11: connect: Connect failed, Node unreachable (temporary failure)

  ----- Recipients of this delivery -----

<erlang::chiu> (bounced) <netrix::gillin> (queued, will retry) <erlang::rama> (sent)

  ----- Unsent message follows -----

F.24. Not a Typewriter

Date: Wed, 8 Aug 90 19:36:47 -0700 From: [email protected] (Mail Delivery Subsystem) Subject: Returned mail: Host unknown To: owner-ietf

  ----- Transcript of session follows -----

get_status: Not a typewriter (mail11 operating system error)

451 <[email protected]>... Operating system error mail11: connect: Connect failed, Unrecognized object (permanent failure)

554 <[email protected]>... 550 Host unknown

  (Authoritative answer from name server)
  ----- Recipients of this delivery -----

<[email protected]> (bounced) <[email protected]> (bounced)

  ----- Unsent message follows -----

F.25. "MTA Congestion"

Date: Tue, 7 Aug 90 22:37:48 -0700 To: ietf-request From: DFN Gateway <postmaster%[email protected]> Subject: DFN Mail Network -- failed mail

Mail Failure Diagnostics:

Message Recipients:

  [email protected]: MTA congestion

F.26. Local Forwarding Not Working

To: [email protected] Subject: [email protected]... User unknown Date: Thu, 01 Nov 90 13:20:53 PST From: Ann Westine <[email protected]>

Hi,

Would you mind checking into this error message before I delete this person from our list. I think it may be an internal forwarding problem at MIT. If not let me know if there is a new address or if I should delete this one.

--Ann

  ------- Forwarded Message
  Date:    Thu, 01 Nov 90 12:34:01 -0800
  From:    [email protected] (Mail Delivery Subsystem)
  To:      [email protected]
  Subject: Returned mail: User unknown
     ----- Transcript of session follows -----
  >>> RCPT To:<[email protected]>
  <<< 550 /u/dukach/.forward:
      line 0: tabasco.lcs.mit.edu... User unknown
  550 [email protected]... User unknown
     ----- Unsent message follows -----
  To: [email protected]
  Cc: [email protected]
  Subject: Re: [email protected]... User unknown
  In-Reply-To: Your message of Thu, 01 Nov 90 13:20:53 -0800.
               <[email protected]>
  Date: Thu, 01 Nov 90 17:16:44 -0500
  From: [email protected]
  Ann,
  Please don't delete Semyon. I'll get him to fix his
  configuration.
  Thanks,
  Chuck

F.27. No Such File or Directory

Date: Tue, 11 Dec 90 17:57:08 -0800 From: [email protected] (Mail Delivery Subsystem) Subject: Returned mail: unknown mailer error 2 To: <[email protected]>

  ----- Transcript of session follows -----

<<< RCPT To:<[email protected]> <<< RCPT To:<[email protected]> <<< DATA mail: Creating /usr/spool/mail/phil -: No such file or directory mail: Creating /usr/spool/mail/rick -: No such file or directory Mail saved in dead.letter 554 <[email protected]>,<[email protected]>... unknown mailer error

F.28. User Account Terminated

Date: Wed, 10 Oct 90 18:21:23 EDT From: [email protected] Subject: Returned mail: User unknown To: <[email protected]>

  ----- Transcript of session follows -----

Connected to DEVVAX.TN.CORNELL.EDU: >>> RCPT To:<[email protected]> <<< 550 <[email protected]>... User unknown 550 [email protected]... User unknown

F.29. Machine Terminated

Date: Wed, 10 Oct 90 19:33:26 EDT From: Mail Delivery Subsystem <[email protected]> Subject: Returned mail: Host unknown To: <[email protected]>

  ----- Transcript of session follows -----

550 edn-unix.dca.mil.tcp... 550 Host unknown 550 [email protected]... Host unknown

  ----- Unsent message follows -----

F.30. Couldn't Make Final Delivery.

a. Case 1

Date: 29 Aug 90 13:17:34 EST From: "SMTP MAILER" <[email protected]> Subject: Mail Delivery Problem To: "owner-ietf" <owner-ietf>

----Reason for mail failure follows----

Sending mail to recipient(s) Nakassis :

 Couldn't make final delivery.

%MAIL-E-OPENOUT, error opening USER2:[000000]NAKASSIS.DIR as output

21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)~~

b. Case 2

Date: 8 Oct 90 20:24:32 EDT From: "SMTP MAILER" <[email protected]> Subject: Mail Delivery Problem To: "owner-ietf" <[email protected]>

----Reason for mail failure follows----

Sending mail to recipient(s) morrisd :

 Couldn't make final delivery.

%MRGATE-E-MRFROMVMS, Error transferring message to Message Router

F.31. Unknown ".ARPA" Hosts Without Updated Hostname

WHATHOST and DIG show nothing for DCA-EMS.ARPA. There is no referral to the new hostname. "WHOIS" DCA-EMS came up with the new hostname.

From: [email protected] (Mail Delivery Subsystem) Subject: Returned mail: Deferred: Host Name Lookup Failure Posted-Date: Tue, 13 Nov 90 15:59:34 -0800 To: [email protected]

  ----- Transcript of session follows -----

[email protected],[email protected],

 [email protected]... Host unknown

westine 45% whathost dca-ems.arpa Unknown Host: dca-ems.arpa, errno 0, h_errno 1 : Unknown host

21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)~~

westine 44% whois dca-ems Defense Communications Agency (DCA) (DCA-EMS)

  Office Automation Division
  Code H610
  Washington, DC 20305-2000
  Hostname: DCA-EMS.DCA.MIL
  Address: 26.1.0.76
  System: BBN-C/70 running UNIX
  Host Administrator:
     Wilkinson, Avis D.  (ADW)  [email protected]
     (703) 848-4867
  DCA-EMS.DCA.MIL users send E-Mail to [email protected]
  Record last updated on 10-Sep-90.

F.32. Messages From an Internet Relay to Commercial Mail Systems

a. Message Too Large

Date: 13 Feb 91 04:15:22 EST From: Electronic Postmaster <[email protected]> To: Ann Westine <[email protected]> Subject: Undeliverable message

Re: ? EMDITB - Mail Delivery Failure. Message too large.

    >EPX [74360,3202]

Internet Monthly Report

Your message could not be delivered as addressed.

--- Returned message ---

21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)~~

b. Invalid Parameters

Date: 13 Feb 91 05:34 UT From: "X.400 Gateway" <[email protected]> Subject: MHS NonDelivery Report To: [email protected]

Report from domain /PRMD=/ADMD=telemail/C=us/:

FAILED delivery to:

 1 Recipient ORName:

/PN=tony.y.mazraani/DD.TS=SM55/O=SPRINTINTL/ADMD=TELEMAIL/C=US/

Translates to:

/PN=tony.y.mazraani/DD.TS=SM55/O=SPRINTINTL/ADMD=TELEMAIL/C=US

                                                     /@sprint.com
Reason: unable to transfer
Diagnostic: invalid parameters

21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)~~

c. Looping

From: [email protected] To: [email protected] Subject: Delivery Report (failure) for

        [email protected]

Message-Type: Delivery Report Date: Wed, 12 Dec 1990 15:34:41 +0000 Content-Identifier: Why WAN multi...

This report relates to your message: Why WAN multi...

       of Wed, 12 Dec 1990 15:22:56 +0000

Your message was not delivered to

       [email protected] for the following reason:
       Message looping detected (please contact local administrator)
      • The following information is directed towards the local
      • administrator and is not intended for the end user
  • DR generated by mta pilot.cs.wisc.edu
  • in /PRMD=xnren/ADMD= /C=us/
  • at Wed, 12 Dec 1990 15:34:35 +0000
  • Converted to RFC 822 at pilot.cs.wisc.edu
  • at Wed, 12 Dec 1990 15:34:41 +0000
  • Delivery Report Contents:
  • Subject-Submission-Identifier: [/PRMD=xnren/ADMD=

/C=us/;<[email protected]]

  • Content-Identifier: Why WAN multi...
  • Subject-Intermediate-Trace-Information: /PRMD=xnren/ADMD= /C=us/;
  • arrival Wed, 12 Dec 1990 15:22:56 +0000 action Relayed
  • Subject-Intermediate-Trace-Information: /PRMD=xnren/ADMD= /C=us/;
  • arrival Wed, 12 Dec 1990 15:22:47 +0000 action Relayed
  • Subject-Intermediate-Trace-Information: /PRMD=xnren/ADMD= /C=us/;
  • arrival Wed, 12 Dec 1990 15:21:48 +0000 action Relayed
  • Subject-Intermediate-Trace-Information: /PRMD=xnren/ADMD= /C=us/;
  • arrival Wed, 12 Dec 1990 11:05:55 +0000 action Relayed
  • Subject-Intermediate-Trace-Information: /PRMD=xnren/ADMD= /C=us/;
  • arrival Wed, 12 Dec 1990 11:05:46 +0000 action Relayed
  • Subject-Intermediate-Trace-Information: /PRMD=xnren/ADMD= /C=us/;
  • arrival Wed, 12 Dec 1990 15:22:57 +0000 action Relayed
  • Subject-Intermediate-Trace-Information: /PRMD=xnren/ADMD= /C=us/;
  • arrival Wed, 12 Dec 1990 11:04:50 +0000 action Relayed
  • Recipient-Info: [email protected],
  • /G=Allan/S=Cargille/OU=cs/O=uw-madison/PRMD=xnren/ADMD=
  • /C=us/;
  • FAILURE reason Unable-To-Transfer (1);
  • diagnostic Loop-Detected (3);
  • last trace () Wed, 12 Dec 1990 11:04:50 +0000;
            • End of administration information

F.33. Incomplete DNS Data on Host

Date: Fri, 14 Dec 90 19:37:51 -0500 From: Mail Delivery Subsystem <[email protected]> To: [email protected] Subject: Returned mail: Host unknown

  ----- Transcript of session follows -----

550 megasys.com (TCP)... 550 Host unknown 550 <[email protected]>... Host unknown (Valid name but no data

   [address])

westine 27% dig megasys.com any

<<>> DiG <<>> megasys.com any
->>HEADER<<- opcode
QUERY , status
NOERROR, id: 6
flags
qr rd ra Ques: 1, Ans: 2, Auth: 2, Addit: 3
QUESTIONS
megasys.com, type = ANY, class = IN
ANSWERS

megasys.com IN NS UUNET.UU.NET ; 172786 megasys.com IN NS seismo.CSS.GOV ; 172786

AUTHORITY RECORDS

MEGASYS.COM IN NS UUNET.UU.NET ; 172786 MEGASYS.COM IN NS seismo.CSS.GOV ; 172786

ADDITIONAL RECORDS

UUNET.UU.NET IN A 192.48.96.2 ; 447968 UUNET.UU.NET IN A 137.39.1.2 ; 170920 seismo.CSS.GOV IN A 192.12.141.25 ; 172786

F.34. Sublist Problem

From: [email protected] Posted-Date: Mon, 17 Dec 90 12:28:23 EST Received: from gimme.math.ufl.edu by venera.isi.edu (5.61/5.61+local)

       id <AA15131>; Mon, 17 Dec 90 09:28:24 -0800

Received: by gimme.math.ufl.edu (4.1/4.03)

       id AA05948; Mon, 17 Dec 90 12:28:23 EST

Date: Mon, 17 Dec 90 12:28:23 EST To: [email protected], [email protected] Subject: here we go again: please release me, let me go...

Fifth time now(?) I try this every couple of months now, figuring you may be hoplesslly backed up.

Can you remove me from the ietf list? I may be there as either:

       [email protected]

or

       [email protected]

I would appreciate a confirmation message: I'm ready to use crontab for these mailings.

Many Thanks,

Randy Fischer

21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)~~

To: [email protected] cc: [email protected], [email protected] Reply-To: [email protected] Subject: Re: here we go again: please release me, let me go... In-reply-to: Your message of Mon, 17 Dec 90 12:28:23 -0500.

            <[email protected]>

Date: Mon, 17 Dec 90 10:15:36 PST From: Ann Westine <[email protected]>

Hi Randy,

I remember your request, and I also remember telling you that you are not on our list (at least individually). There is an exploder "[email protected]" maintained at UFL.EDU. You need to check with the postmaster to see if you are on their list. If this is not the case, here are the only other addresses I have from UFL.EDU

[email protected], [email protected], [email protected], [email protected], [email protected],

There is another possibility, perhaps you have a pointer to a mailbox somewhere else?

Regards, Ann

21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)~~

From: Operator <[email protected]> To: [email protected], [email protected] Subject: re: done at last: please release me, let me go...

Many, many thanks for the reply: I did not, somehow, see your previous reply -- perhaps you forwarded it to someone at UFL.EDU instead of MATH.UFL.EDU? Or I missed it in the flow of mail I am trying to abate. No matter.

At any rate "[email protected]" is indeed a local exploder, aliased at the moment to myself and one of my assistants. It is local to the "math.ufl.edu" subdomain, and not to "ufl.edu" as your records indicate. I am the postmaster of the "math.ufl.edu", and you should be able to verify "math.ufl.edu" has an MX record pointing to "mathlab.math.ufl.edu". I am therefore mailing to you as root from that machine.

Please remove "[email protected]" from your list. I have quite enjoyed the discussions, but the volume been overwhelming.

Thanks very much for your prompt reply, Appreciatively,

-Randy Fischer <[email protected]> <[email protected]>

F.35. File Protection Problem

From: "Raj Jain, LKG1-2/A19, DTN: 226-7642, 508-486-7642

      09-Feb-1991 0904"

<[email protected]> To: [email protected] Subject: Request to add to IETF

I seem to have suddenly dropped off the IETF distribution list. I have not received any IETF mail since 9-Jan-91. Could you please ensure that I am still in the distribution list.

-Raj Jain

21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)~~

To: "Raj Jain, LKG1-2/A19, DTN: 226-7642,

   508-486-7642 09-Feb-1991 0904" <[email protected]>

cc: [email protected], ietf-request Reply-To: [email protected] Subject: Re: Request to add to IETF In-reply-to: Your message of Sat, 09 Feb 91 06:07:15 -0800.

            <[email protected]>

Date: Tue, 12 Feb 91 11:17:41 PST From: Ann Westine <[email protected]>

Hi Raj,

I will readd you to the IETF list. However, if I receive more error messages like this, then I must take your name off the list again. I've sent messages to the postmaster at DEC but the problem isn't corrected. Your address isn't the only one, there's CALLON and a few others.

Maybe you can check into this. Here's the header from one of the many error messages I received.

Regards, --Ann

  Date: Wed, 9 Jan 91 17:04:41 -0800
  From: [email protected] (Mail Delivery Subsystem)
  Subject: Returned mail: User unknown
  To: [email protected]
     ----- Transcript of session follows -----
  mail11: Error from DECnet MAIL object on node "erlang",
          during mail delivery to <ERLANG::JAIN>.
          Remote error code is 0x7e81fa, message is:
  %MAIL-E-OPENOUT, error opening !AS as output
  -RMS-E-PRV, insufficient privilege or file protection violation
          (can't decypher error code)
  550 <[email protected]>... User unknown
     ----- Recipients of this delivery -----
  <[email protected]> (bounced)

21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)~~

Date: Tue, 12 Feb 91 17:54:20 EST From: "Raj Jain, LKG1-2/A19, DTN: 226-7642, 508-486-7642

      12-Feb-1991 1751"

<[email protected]> To: [email protected] Subject: Re: Request to add to IETF

The error message that you sent is unfortunately my mistake and has nothing to do with DECWRL. One day I reset protection on all my files and directories and didn't realize that even the system did not have the privilege to write mail messages on my disk. I discovered it only after several people sent phone messages to me. Thanks for adding my name again. I will try to be careful. -Raj

F.36. User Unknown

a. Request to be Readded to IETF List

Date: Mon, 11 Feb 91 10:03:54 PST From: "Paul Ciarfella DTN 227-3548 Outside 508 952-3548

     11-Feb-1991 1301"

<[email protected]> To: [email protected] Subject: add me to the ietf list (again)

Hi -

Could I be added to the ietf distribution list (again). I must have been dropped from the list somehow. This happened to me before the last ietf - I had to get my name reregistered then, too.

Thanks,

Paul Ciarfella [email protected]

21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)~~

b. Message to User Regarding Readd and Previous Problems

To: "Paul Ciarfella DTN 227-3548 Outside 508 952-3548 11-Feb-1991

   1301" <[email protected]>

Cc: [email protected] Reply-To: [email protected] Subject: Re: add me to the ietf list (again) In-Reply-To: Your message of Mon, 11 Feb 91 10:03:54 -0800.

            <[email protected]>

Date: Wed, 13 Feb 91 11:05:46 PST From: Ann Westine <[email protected]>

Hi Paul,

Every couple of months I have lots of error messags from several individual mailboxes on ENET.DEC.COM. Here is a typical one. Since I cannot reach you I am forced to delete your mailbox.

I have sent several messages to the postmaster at DEC but nothing has been corrected. Perhaps you can look into this.

--Ann

  Return-Path: [email protected]
  Received-Date: Tue, 11 Dec 90 19:53:19 PST
  Received: from venera.isi.edu by zephyr.isi.edu (4.1/4.0.3-4)
          id <AA11360>; Tue, 11 Dec 90 19:53:19 PST
  Posted-Date: Tue, 11 Dec 90 19:42:03 -0800
  Received: from decpa.pa.dec.com by venera.isi.edu
          (5.61/5.61+local)
          id <AA08309>; Tue, 11 Dec 90 19:53:17 -0800
  Received: by decpa.pa.dec.com; id AA12106; Tue, 11 Dec 90 19:42:03
  Date: Tue, 11 Dec 90 19:42:03 -0800
  From: [email protected] (Mail Delivery Subsystem)
  Subject: Returned mail: User unknown
  Message-Id: <[email protected]>
  To: [email protected]
     ----- Transcript of session follows -----
  mail11: input timeout reading remote object
  get_status: Connection timed out
  (temporary failure)
  mail11: Error from DECnet MAIL object on node "levers",
          during mail delivery to <LEVERS::CIARFELLA>.
          Remote error code is 0x7e81fa, message is:
  %MAIL-E-OPENOUT, error opening !AS as output
  -RMS-E-CRE, ACP file create failed
  -SYSTEM-W-DIRALLOC, allocation failure on directory file
          (can't decypher error code)
  550 <[email protected]>... User unknown
     ----- Recipients of this delivery -----
  <[email protected]> (queued, will retry)
  <[email protected]> (bounced)
  <[email protected]> (sent)

21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)21:26, 29 September 2020 (UTC)~~

c. Response from User Regarding Problem

Return-Path: [email protected] Received-Date: Wed, 13 Feb 91 13:51:25 PST Received: from venera.isi.edu by zephyr.isi.edu (4.1/4.0.3-4)

       id <AA26215>; Wed, 13 Feb 91 13:51:25 PST

Posted-Date: Wed, 13 Feb 91 13:51:02 PST Received: from decpa.pa.dec.com by venera.isi.edu (5.61/5.61+local)

       id <AA04585>; Wed, 13 Feb 91 13:51:22 -0800

Received: by decpa.pa.dec.com; id AA14420; Wed, 13

         Feb 91 13:51:00 -0800

Received: from levers.enet; by decwrl.enet; Wed, 13 Feb 91 13:51:02 PST Date: Wed, 13 Feb 91 13:51:02 PST From: "I'll die for my country but I won't kill for Texaco 13-Feb-1991 1641" <[email protected]> To: [email protected] Subject: re: add me to the ietf list (again)

Hi Ann,

Could we try another address for me? The old address has been plagued by disk problems which might explain why the mail is not getting delivered.

The new address to register is:

  [email protected]

I will check into the problem on this end. Sorry about the tone of my first message but this has been a never-ending problem for over 8 months.

Thank you,

Paul C

Security Considerations

Security issues are not discussed in this memo.

Authors' Addresses

Ann Westine USC - Information Sciences Institute 4676 Admiralty Way Marina del Rey, CA 90292-6695

Phone: 213-822-1511

EMail: [email protected]

Jon Postel USC - Information Sciences Institute 4676 Admiralty Way Marina del Rey, CA 90292-6695

Phone: 213-822-1511

EMail: [email protected]