[MLB-WIRELESS] Fw: Delivery Status Notification (Failure) ( anyone else get this? )

[Jason Clarke]

> On Tue, Jan 14, 2003 at 09:36:58AM +1100, Jason Clarke wrote:
> > It's more along the lines of setting up the MW mailing list to mung
> > the headers so that I / people don't have to reply-to-all to get it
> > back to the list.
>
> ok, you're talking about Reply-To munging, which is a completely
> different and unrelated issue.

It's more the changing of how anything on the list works :-)

> it's also a brain-damaged and broken thing for a mailing list to do.
> for info, see:
>
> http://www.unicom.com/pw/reply-to-harmful.html

Valid points, but I disagree with it :-)

> > It's only out of habit I use reply-to-all and check the addresses
> > listed, but many don't. YOU didn't.
>
> that's because it's a matter of preference.  some people like to be
> CC-ed on list mail, and some people don't like it.  if i know someone
> doesn't like it, and if i remember, then i'll trim their address from
> the CC list.

No problemo. If you remember that is. (Thanks for no CC: :)

> fortunately, there is a way to automatically specify your preference
> without expecting everyone else to have to remember.  just set your mail
> client to add a Mail-Followup-To header when you send messages to a
> list.  this allows you to specify whether you want follow-ups to go to
> you, to the list, or to both.

But then again, you're relying on a 3rd party to honour the Followup header,
and I doubt this will fix the reply-all / CC ickyness.

> > And it utterly SHITS me that I receive two e-mails.
>
> that's not what the Reply-To header is for.  munging the reply-to header
> wouldn't fix this anyway.
>
> use the Mail-Followup-To header to indicate your preference.  that's
> what it's for.
>
> > How ever, I know that my complaints will only start up another war
> > about mail clients
>
> obviously a sore spot, so i'll assume you've been told before that you
> should use a decent mail client.  good advice.
>
> if there's a solution (i.e. using a non-broken mail client) to a problem
> and you choose not to implement that solution then you really have no
> cause to complain.  you can't expect anyone else to care much about your
> problem if you don't care enough to bother to fix it.
>

Tehe. Good advice coming from fanatics (not specifically you). An oxymoron?

Choosing not to implement a non-broken mail client that would result in many
hours of re-training on personal plus the trouble shooting required when
things go wrong seems a little more sensible. I've tried other clients
(Win32 / *nix) and found that most have glaring feature problems (Shared
address books is a primary requirement) or are just suffering from a bad
case of bad gui's.

However, this is going to degenerate into a flame war (I'm guilty of it too)
before much longer and again, will result in no gain in either way. People
advocating other mail clients will continue to do so, people who don't care
will continue not to care, and those who can't deal with the whole issue
will go postal.

J


To unsubscribe: send mail to majordomo at wireless.org.au
with "unsubscribe melbwireless" in the body of the message