From: brian@lorf.org (Brian)
Subject: [sup-talk] no message-id field in header
Date: Tue, 12 Jun 2007 21:32:21 -0500 [thread overview]
Message-ID: <1181701811-sup-4093@doses> (raw)
In-Reply-To: <1181700658-sup-8600@south>
Excerpts from William Morgan's message of Tue Jun 12 21:11:40 -0500 2007:
> Excerpts from brian's message of Tue Jun 12 17:42:12 -0700 2007:
> > Not sure if this is trustworthy, but when I look at this particular
> > message through the uark.edu web interface, it does seem to have a
> > message ID:
> > <".AAA-notification-29733,6108.1181379197"@na-rte-app-1104.vdc.amazon.com>
>
> Do you mind sending me the full headers for this message?
Pasted from pine. Please let me know if I need to do it some other way.
Thank you.
Return-path: <RealTimeEmail+USRT--4ZZAM0N3t2 at bounces.amazon.com>
Received: from mx1.uark.edu (mx1.uark.edu [130.184.5.58])
by mailhost.uark.edu (Sun Java System Messaging Server 6.2-6.01 (built Apr 3
2006)) with ESMTPS id <0JJD00LLQ21BO800 at mailhost.uark.edu> for bsl04 at uark.edu;
Sat, 09 Jun 2007 03:53:35 -0500 (CDT)
Received: from mm-notify-out-1104.amazon.com
(mm-notify-out-1104.amazon.com [207.171.164.46])
by mx1.uark.edu (8.13.8/8.13.8) with ESMTP id l598rUg6012679 for
<bsl04 at uark.edu>; Sat, 09 Jun 2007 03:53:30 -0500
Received: from na-rte-app-1104.vdc.amazon.com ([10.144.96.41])
by mm-notify-out-1104.amazon.com with ESMTP; Sat, 09 Jun 2007 01:53:21 -0700
Received: by na-rte-app-1104.vdc.amazon.com id AAA-notification-29733,
6108; Sat, 09 Jun 2007 01:53:17 -0700
Date: Sat, 09 Jun 2007 01:53:17 -0700
From: "auto-confirm@amazon.com" <auto-confirm at amazon.com>
Subject: Your Order with Amazon.com
To: bsl04 at uark.edu
Message-id:
<".AAA-notification-29733,6108.1181379197"@na-rte-app-1104.vdc.amazon.com>
MIME-version: 1.0
Content-type: Multipart/Alternative; boundary=MuLtIpArT_BoUnDaRy
Bounces-to: RealTimeEmail+USRT--4ZZAM0N3t2 at bounces.amazon.com
X-AMAZON-TRACK: notification
X-AMAZON-MAIL-RELAY-TYPE: notification
X-PMX-Version: 5.3.1.294258, Antispam-Engine: 2.5.1.298604,
Antispam-Data: 2007.6.9.12956
Original-recipient: rfc822;bsl04 at uark.edu
X-Perlmx-Spam: Gauge=IIIIIIIII, Probability=9%, Report='PHISH_SUBJ_LOW 0.5,
__C230066_P5 0, __CP_NAME_BODY 0, __CP_URI_IN_BODY 0, __CT 0,
__CTYPE_HAS_BOUNDARY 0, __CTYPE_MULTIPART 0, __CTYPE_MULTIPART_ALT 0,
__FRAUD_419_REFNUM 0, __HAS_MSGID 0, __MIME_CHARSET_FARAWAY 0, __MIME_HTML 0,
__MIME_VERSION 0, __PHISH_FROM 0, __PHISH_FROM1 0, __PHISH_FROM_A 0,
__PHISH_PHRASE7 0, __PHISH_SUBJ_PHRASE4 0, __SANE_MSGID 0, __STOCK_PHRASE_7 0,
__TAG_EXISTS_HTML 0, __dnsbl.njabl.org_TIMEOUT '
next prev parent reply other threads:[~2007-06-13 2:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-12 18:20 Ian Taylor
2007-06-13 0:07 ` William Morgan
2007-06-13 0:42 ` Brian
2007-06-13 2:08 ` Ian Taylor
2007-06-13 2:11 ` William Morgan
2007-06-13 2:32 ` Brian [this message]
2007-06-13 18:04 ` William Morgan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1181701811-sup-4093@doses \
--to=brian@lorf.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox