Menu
▾
▴
Re: [Openeeg-list] Re: Vol 1 #4 - mail delivery
|
From: Jim P. <ji...@ua...> - 2002-07-13 18:03:37
|
Andreas Robinson wrote:
> > I vote to not have HTML copies of plain text msgs sent to the list.
>
> Hmm, I guess that HTML is not filtered and cleaned up here which is
> bad because there are a lot of people that send HTML-mails without
> even knowing. We could use a filter that either makes mails
> beginning with <HTML> bounce, or reduces them to plain text. I'll
> send a mail about it to Sourceforge admin - it should not be hard
> for them to implement... if they have time...
I think the problem is that many E-mailers send multipart/alternative
sections by default -- i.e. two sections, plain-text and HTML. My
mail-client (mutt) ignores the HTML alternative, but I guess some
mail-clients don't, and display both. Really it is up to the original
sender to turn off the HTML alternative (or the recipient to use a
client that understands multipart/alternative). I don't think that
Yahoo is any better -- I managed to find several messages on the old
list with exactly the same problem.
Just one thought -- SourceForge now once again lets you turn on
Reply-To headers in the Admin section (I've just turned them back on
for my SBaGen list). This subject generates some (heated) debate, but
I personally prefer the Yahoo-like default of having them turned on
for a closed list.
For lists that are open to non-subscribers and get a lot of
cross-posted discussions, it makes less sense. But perhaps it would
be good to turn them on for this list ? This means that the list adds
a Reply-To field containing the list address to each message, so that
people hitting 'reply' have their reply sent back to the list by
default. (Otherwise they have to always use 'reply-to-all').
Personally, I can live with either option if you want to use
SourceForge's default --
Jim
--
Jim Peters (_)/=\~/_(_) ji...@ua...
(_) /=\ ~/_ (_)
Uazú (_) /=\ ~/_ (_) http://
B'ham, UK (_) ____ /=\ ____ ~/_ ____ (_) uazu.net
|
