From: Morgan Gangwere <0.fractalus@gmail.com>
To: "More reasons we're all going to be laced with cyanide and our
dead bodies used as nuclear fuel." <cygwin-talk@cygwin.com>
Subject: Re: Your setting Return-Path to YOU in your cygwin@cygwin postings
Date: Thu, 05 Mar 2009 18:32:00 -0000 [thread overview]
Message-ID: <4e41f5c20903051032u49097f7fw8c951c47a99c7d45@mail.gmail.com> (raw)
In-Reply-To: <62743174EA5B5317274570F1@orees.hpl.hp.com>
... and why did this not get picked up by my "list-id:*@cygwin.*"
filter? there's no "reasonable" way to tell where the message is
going/coming from. Several MUAs i've seen have done a "Lets Assume On
Behalf Means We Send It To Random Addresses" -- such as Gmail at times
and Mutt.
Apparently, some MUAs take "on-behalf-of" indications as "send it to
the represented person" and not "send it to who sent it to me"
But That Might Just Be Me.
--
Morgan gangwere
"Space does not reflect society, it expresses it." -- Castells, M.,
Space of Flows, Space of Places: Materials for a Theory of Urbanism in
the Information Age, in The Cybercities Reader, S. Graham, Editor.
2004, Routledge: London. p. 82-93.
prev parent reply other threads:[~2009-03-05 18:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <49ADA916.40700@columbus.rr.com>
[not found] ` <49ADBA0D.6040405@gmail.com>
[not found] ` <49ADEF5E.3060804@columbus.rr.com>
[not found] ` <49ADF5B5.5000102@gmail.com>
[not found] ` <49AE0F52.1060006@columbus.rr.com>
2009-03-04 11:59 ` Dave Korn
2009-03-04 12:30 ` Owen Rees
2009-03-04 16:30 ` Dave Korn
2009-03-04 16:45 ` Christopher Faylor
2009-03-04 17:04 ` Owen Rees
2009-03-04 18:16 ` Dave Korn
2009-03-05 10:57 ` Owen Rees
2009-03-05 13:18 ` Dave Korn
2009-03-05 15:56 ` Owen Rees
2009-03-05 18:32 ` Morgan Gangwere [this message]
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=4e41f5c20903051032u49097f7fw8c951c47a99c7d45@mail.gmail.com \
--to=0.fractalus@gmail.com \
--cc=cygwin-talk@cygwin.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).