It appears as if <firstname.lastname@example.org> wrote:
|One problem in terms of tracking this problem down is that our list
|software does not include the mail headers for incoming mail. My mail
|arrives looking like:
|Received: from maxwell.kumo.com (maxwell.kumo.com [22.214.171.124])
| by coyote.rain.org (Postfix) with ESMTP id B08916174F
| for <email@example.com>; Fri, 11 Jun 1999 00:37:18 -0700 (PDT)
|Received: (from majordom@localhost)
| by maxwell.kumo.com (8.9.1/8.9.1) id BAA28888
| for extropians-outgoing; Fri, 11 Jun 1999 01:36:13 -0600
|The very first Received line is the first step in the outgoing mail path
|from the local machine the list runs on. There is no indication of
|where the mail came from before then. Perhaps the list managers might
|be able to manually inspect these incoming messages and determine where
|they are coming from.
Some list members might wish that list software behaviour (e.g. for privacy).
Has the list owners hardwired the code as to make it impossible to upgrade?
If not, any competent software person could easily change the software, so that senders who like routing privacy could enjoy it, while those who feel no such urge could avoid it.
Increased complexity and choice would seem very extropian.