public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: Gregory Nowak <greg@romuald.net.eu.org>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: Replying to The Speakup List?
Date: Fri, 9 Mar 2007 20:50:06 -0700	[thread overview]
Message-ID: <20070310035006.GA19316@localhost.localdomain> (raw)
In-Reply-To: <20070310081748.GB15922@grml>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Whether you include the original post or not, isn't the issue
here. When replying to some posts, in addition to the address for the
list, you also have the address of the original sender of the message
as well in the reply to field. Personally, I think this is a from
header misconfiguration on the part of whoever posted the message to
which you're replying. Incidently, if you chose to reply to just that
message, and not the entire list in this scenario, you'll get the list
address in the reply to field, instead of the original sender's
address. So, no, in this case, the message isn't just going to
speech.braille.uwo.ca.

The solution here is obvious, remove the original sender's address
from the reply to field, just leaving the list address. I personally
didn't bother doing that, since I don't see a big issue with the
sender getting my message twice, through the list, as well as
directly. However, now that I know this issue exists, I'll be taking
care to check the reply to field when sending a reply to a post from
this list, as well as other mailman lists I guess, since I imagine the
problem isn't unique to this list.

Greg


On Sat, Mar 10, 2007 at 09:17:48AM +0100, Doug Smith wrote:
> Ok, I guess the best solution to all this might be to do what I am
> doing.  I never include the messages back in the post.  I just put in
> my message and let her fly.  I have never had a problem.  
> 
> Why should there be more than one recipient?  The list machine, the
> one at the University of Western Ontario is the only recipient.  This
> machine distributes the messages to all the list members.  Just try
> not including original messages and see if this stops. it.  
> 
> 
> 
> Hope this helps. 
> 
> 
> 
> 
> -- 
> Doug Smith: C.S.F.C.
> Computer Scientist For CHRIST
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup

- -- 
web site: http://www.romuald.net.eu.org
gpg public key: http://www.romuald.net.eu.org/pubkey.asc
skype: gregn1
(authorization required, add me to your contacts list first)

- --
Free domains: http://www.eu.org/ or mail dns-manager@EU.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFF8iru7s9z/XlyUyARAlBKAJsGQhW27mov+dDN53k+DgG/G0IdQgCeMF33
EX7txla7/fGm+o6yYmJvg2w=
=2yuD
-----END PGP SIGNATURE-----


  reply	other threads:[~ UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Gregory Nowak
 ` Adam Myrow
   ` Doug Smith
     ` Gregory Nowak [this message]
       ` Steve Holmes
  -- strict thread matches above, loose matches on Subject: below --
 Hart Larry
 ` Gregory Nowak
   ` David Poehlman
     ` W. Nick Dotson
   ` Albert E. Sten-Clanton

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070310035006.GA19316@localhost.localdomain \
    --to=greg@romuald.net.eu.org \
    --cc=speakup@braille.uwo.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).