Josh is correct. I just checked the archives on faq.org and the old list
software set
Reply-To: <FAQ-Maintainers@consensus.com>
# >Sorry, but some of these issues affect the health of the community
# >of subscribers. We will decide when we are tired of this topic.
# >When we want guidance from you on the selection of topics, we will
# >ask you.
Time out.... Deep breath... :)
# Hey, I'm just trying to help here. We can do whatever the list wants to. If
# you work with me on this, I'm confident you'll find that the server is quite
# flexible and that we can get it to do whatever we need. The developer has
# already committed to a number of changes based specifically on the comments
# from this list, which we should see in a few weeks (or less).
Great. Thanks. There are some that are required to be corrected before
people will get back to the intended list topics. :)
# >> 1) Header MessageID rewriting
# >
# >> Lyris rewrites the MessageID on messages it sends for two
# >> reasons.
#
# >This violates a very fundamental principle of email. The
# >Message-ID and signature go together. If you put a different
# >Message-ID on a message I signed, you have misappropriated my
# >intellectual property and created an unauthorized copy.
#
# I'm don't agree with the intellectual property connection. However, we are
# currently looking at possible RFC violations. There are two reasons the
# message-id is changed: 1) each person receives a unique message with a
# different body and 2) some mail systems cache message bodies if the
# message-ids are the same, so we must modify them for mail to be delivered
# properly.
Then how about this... This software is violating my system's rights. No
site has the right generating mail that appears to come from my systems
except me. I quote RFC 822.
4.6.1. MESSAGE-ID / RESENT-MESSAGE-ID
This field contains a unique identifier (the local-part
address unit) which refers to THIS version of THIS message.
The uniqueness of the message identifier is guaranteed by the
host which generates it. This identifier is intended to be
machine readable and not necessarily meaningful to humans. A
message identifier pertains to exactly one instantiation of a
particular message; subsequent revisions to the message should
each receive new message identifiers.
Your site sent me the message that I am responding to with a message-id of:
Message-ID: <LYR932-221--kent@landfield.com>
The Lyris software cannot ever generate a message using my host's information
that it and your host guarantees as unique. It cannot be done. I use my
message-id's to index mail sent from my system for archival purposes. This
messes this up greatly. It also makes filtering on Message-ID wothless on
this list (and yes, I do (or did) filter on message-ids).
# I'm not sure if the $subst() tags will be turned off, but I don't see them
# as causing real problems... its the [email address] one which is most likely
# to get a false positive.
The problem is that the list management software is munging the body of
messages it is distributing. This is wrong. It should simply distribute
the message and if need be, append a header or footer to the begining or
end of the message that is clearly not a part of the message.
**ANY** substitution of content of the submitted body is totally unforgivable
software wise. It is just plain broken.
# The Reply-To issue is still open... if people want, I'd be happy to run an
# informal "vote", tally the results, and post them back here.
I say just leave it the way it was until we get the real problems fixed...
Thanks for poking your head up Josh. :) Hope we miss the eyes. ;)
-- Kent Landfield Phone: 1-817-545-2502 Email: kent@landfield.com http://www.landfield.com/ Email: kent@nfr.net http://www.nfr.net/ Please send comp.sources.misc related mail to kent@landfield.com Search the Usenet FAQ Archive at http://www.faqs.org/faqs/
[
Usenet Hypertext FAQ Archive |
Search Mail Archive |
Authors |
Usenet
]
[
1993 |
1994 |
1995 |
1996 |
1997
]
© Copyright The Internet FAQ Consortium, 1997
All rights reserved