C the ISO country code (on most services)
ADMD domain code for public system (abbreviation A)
PRMD domain code for connected private system
(abbreviation P)
O organization name
OU organization unit
S surname (last name)
G given name (first name)
I initials (in the name)
DDA domain-defined attributes, keywords defined and
used by the individual systems to specify mailboxes
(user name, list, station, user code, etc.), direct
delivery devices (attention name, telex addresses,
facsimile, etc.)
PN personal name
(a) the character @ cannot be used when routing messages
from X.400 to Internet. Try (a) instead.
(p) the character % cannot be used when routing messages
from X.400 to Internet. Try (p) instead.
(b) the character ! (used in "bang" addresses).
(q) the character " used in email addresses.
RFC-822 this code tells X.400 that an Internet domain address
follows. Does not work on all X.400 systems.
Returned mail ——————- When an email address is incorrect in some way (the system's name is wrong, the domain doesn't exist, whatever), the mail system will bounce the message back to the sender. The returned message will include the reason for the bounce. A common error is addressing mail to an account name that doesn't exist. Let's make an error when sending to LISTSERV@vm1.nodak.edu. Enter "pistserv@vm1.nodak.edu" instead of "LISTSERV@vm1.nodak.edu". This address is wrong. Below, we've printed the complete bounced message. It contains a lot of technical information. Most lines have no interest. Also, the message is much larger than the original message, which contained three lines only. When browsing the bounced message, note that it has three distinct parts: (1) The mail header of the bounced message itself (here, the 13 first lines), (2) The text of the error report (from line 14 until the line "Original message follows:"), and (3) the mailer header and text of your original message (as received by computer reporting the error):
From MAILER@VM1.NoDak.EDU Fri Dec 18 12:54:03 1992
Return-Path: <MAILER@VM1.NoDak.EDU>
Received: from vm1.NoDak.edu by pat.uio.no with SMTP (PP)
id <07610-0@pat.uio.no>; Fri, 18 Dec 1992 12:53:54 +0100
Received: from NDSUVM1.BITNET by VM1.NoDak.EDU (IBM VM SMTP V2R2)
with BSMTP id 9295; Fri, 18 Dec 92 05:53:27 CST
Received: from NDSUVM1.BITNET by NDSUVM1.BITNET (Mailer R2.07)
with BSMTP id 3309; Fri, 18 Dec 92 05:53:26 CST
Date: Fri, 18 Dec 92 05:53:26 CST
From: Network Mailer <MAILER@VM1.NoDak.EDU>
To: opresno@extern.uio.no
Subject: mail delivery error
Status: R
Batch SMTP transaction log follows:
220 NDSUVM1.BITNET Columbia MAILER R2.07 BSMTP service ready.
050 HELO NDSUVM1
250 NDSUVM1.BITNET Hello NDSUVM1
050 MAIL FROM:<opresno@extern.uio.no>
250 <opresno@extern.uio.no>… sender OK.
050 RCPT TO:<pistserv@NDSUVM1>
250 <pistserv@NDSUVM1>… recipient OK.
050 DATA
354 Start mail input. End with <crlf>.<crlf>
554-Mail not delivered to some or all recipients:
554 No such local user: PISTSERV
050 QUIT
221 NDSUVM1.BITNET Columbia MAILER BSMTP service done.
Original message follows:
Received: from NDSUVM1 by NDSUVM1.BITNET (Mailer R2.07) with BSMTP id 3308;
Fri, 18 Dec 92 05:53:25 CST
Received: from pat.uio.no by VM1.NoDak.EDU (IBM VM SMTP V2R2) with TCP;
Fri, 18 Dec 92 05:53:23 CST
Received: from ulrik.uio.no by pat.uio.no with local-SMTP (PP)
id <07590-0@pat.uio.no>; Fri, 18 Dec 1992 12:53:24 +0100
Received: by ulrik.uio.no ; Fri, 18 Dec 1992 12:53:18 +0100
Date: Fri, 18 Dec 1992 12:53:18 +0100
From: opresno@extern.uio.no
Message-Id: <9212181153.AAulrik20516@ulrik.uio.no>
To: pistserv@vm1.nodak.edu
Subject: test
index kidlink
The first part of the bounced message is usually of no interest. Hidden in the second part you'll find the following interesting line:
554 No such local user: PISTSERV