EMAIL SUPPORT

Email messages with valid addresses are rarely undeliverable. However, if this happens it is sometimes difficult to trace a message to its "point of failier". The good news is that the sender often receives notice of the failed email delivery attempt.

To better assist Ariel.Net customers, we sometimes ask that the sender (copy/paste) any error notice information into our "Support" webform and submit it to us. When this is done, we ask that the "body" (error message contents) and "header" (document tracer data) be included.

EMAIL HEADER

The readable text of an email message is referred to as its body.
The header portion of a message tells the Internet what it needs to know for email to be sent to their destination. It also reveals the origin and paths that the messages follow. Whether this information is visible or not, every email contains a header. Generally, the preferences and settings of your email program allow you to display or hide them. The following is an example of what a message header looks like when it is sent from the domain of Cisco.Com to the domain of Ariel.Net.

EMAIL HEADER EXAMPLE

Return-Path: <bingo@cisco.com>
Received: from atlas.cisco.com (atlas-fe0.cisco.com [171.68.225.70]) by iris1.ariel.net (Post.Office MTA v3.1.2 release (PO203-101c) ID# 0-41790U2500L250S0) with ESMTP id AAA1813 for <webmaster@ariel.net>; Mon, 25 Oct 1999 13:04:31 -0700
Received: (bingo@localhost) by atlas.cisco.com (8.8.6 (PHNE_14041)/CISCO.SERVER.1.2) id KAA07455 for webmaster@ariel.net; Mon, 25 Oct 1999 10:21:59 -0700 (PDT)
Date: Mon, 25 Oct 1999 10:21:59 -0700 (PDT)
Message-Id: <199910251721.KAA07455@atlas.cisco.com>
To: webmaster@ariel.net
From: Cisco_CA_Survey <bingo@cisco.com>
Subject: Cisco Survey for Case R1Q377

Return to the Support webpage.
[Home] will return you to our main page.
You may also contact us by emailing support@ariel.net.