From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] no message-id field in header
Date: Tue, 12 Jun 2007 19:11:40 -0700 [thread overview]
Message-ID: <1181700658-sup-8600@south> (raw)
In-Reply-To: <1181694687-sup-7571@doses>
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?
--
William <wmorgan-sup at masanjin.net>
next prev parent reply other threads:[~2007-06-13 2:11 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 [this message]
2007-06-13 2:32 ` Brian
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=1181700658-sup-8600@south \
--to=wmorgan-sup@masanjin.net \
/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