>The list membership should consider whether the list server
>should set a Reply-to:<list address> or not.
Agreed. As I understood it, the old server had this as well. I can easily
turn that off if the list membership wants that. I still think its better to
have the "vote" off-line versus on, but do what ever you want. On the
hundred or so lists I run, I've never seen more than 4 or 5 people actually
care one way or another so it usually makes the most sense not to waste
everyone else's time with it.
>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.
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).
>> 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.
>> If the header it is producing violates some RFC, both myself
>> and the developer would be very interested in tracking down the
>> problem and fixing it. Feel free to contact me directly.
>
>The author of Lyris is a personal acquaintance of Chris Lewis,
>and you may wish to coordinate your efforts with him.
He's involved (off-line).
>The present behavior of the list processor is that it appends
>the footer first and substitutes in the message body after.
>This logic is leading to erroneous substitutions in the author's
>message body [serious no-no].
This feature will be able to be turned off in the next version, which I will
take advantage of. It's based on a legacy feature which isn't needed
anymore, so its no problem to remove it.
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 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.
~Josh
-- ---------------------------------------------------------------
Joshua D. Baer SKYLIST.net
<mailto:Josh@SKYLIST.net> Virtual Communities
<phone:412.422.4004> <http://www.SKYLIST.net/>
Now all that was left 'neath the bad-smelling sky was my big empty
factory... the Lorax... and I.
- Dr. Seuss
[
Usenet Hypertext FAQ Archive |
Search Mail Archive |
Authors |
Usenet
]
[
1993 |
1994 |
1995 |
1996 |
1997
]
© Copyright The Internet FAQ Consortium, 1997
All rights reserved