public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Volker Armin Hemmann <volker.armin.hemmann@tu-clausthal.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Randomly dumb questions
Date: Sat, 15 Mar 2008 18:12:48 +0100	[thread overview]
Message-ID: <200803151812.48732.volker.armin.hemmann@tu-clausthal.de> (raw)
In-Reply-To: <200803151650.51347.alan.mckinnon@gmail.com>

On Samstag, 15. März 2008, Alan McKinnon wrote:
> On Saturday 15 March 2008, Etaoin Shrdlu wrote:
> > On Saturday 15 March 2008, Alan McKinnon wrote:
> > > > > The list software doesn't send a copy of a mail back to the
> > > > > same address as what sent it. This is pretty usual behaviour
> > > > > for any list run by a non-idiot (like this one)
> > > >
> > > > Is that so? Then will you, please, explain how do people get
> > > > their original messages back?
> > >
> > > There's a copy already in their outbox? And a sane mailer (like say
> > > kmail) will have put the sent copy there already.
> >
> > What does this have to do with what the list server does?
>
> OK, lets go back to step 1, and try to think it through this time.
>
> - a user sends a mail from account X to list Y
> - same user is also subscribed to list Y from account X
> - if list Y sends a copy of the mail to the user at account X, then the
> user has a duplicate because by definition *he already has the
> original*
> - it is completely reasonable to give the list admin the option to
> enable or disable this behaviour


but you are wrong.

You get your email back from the list.

GMAIL just does not show it.
--
gentoo-user@lists.gentoo.org mailing list



  parent reply	other threads:[~2008-03-15 17:12 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-15  9:33 [gentoo-user] Can't mount NTFS read-write Stroller
2008-03-15  9:48 ` Neil Bothwick
2008-03-15 10:00   ` Stroller
2008-03-15 10:40   ` Florian Philipp
2008-03-15 11:54     ` Neil Bothwick
2008-03-15 12:52 ` Chris Brennan
2008-03-15 12:53 ` [gentoo-user] Randomly dumb questions Chris Brennan
2008-03-15 13:08   ` Dale
2008-03-15 13:15     ` Chris Brennan
2008-03-15 13:24       ` Dale
2008-03-15 13:39         ` Ric de France
2008-03-15 13:35       ` Alan McKinnon
2008-03-15 13:45         ` Chris Brennan
2008-03-15 13:45         ` Gustavo Campos
2008-03-15 14:29         ` Daniel Iliev
2008-03-15 14:31           ` Alan McKinnon
2008-03-15 14:53             ` Florian Philipp
2008-03-15 15:04             ` Etaoin Shrdlu
2008-03-15 14:50               ` Alan McKinnon
2008-03-15 15:03                 ` Chris Brennan
2008-03-15 15:08                 ` Chris Brennan
2008-03-15 15:20                 ` Etaoin Shrdlu
2008-03-15 17:12                 ` Volker Armin Hemmann [this message]
2008-03-15 17:36                   ` Dale
2008-03-15 15:13             ` Daniel Iliev
2008-03-15 21:59             ` Neil Bothwick
2008-03-15 14:53         ` Alan Milnes
2008-03-15 17:14           ` Volker Armin Hemmann
2008-03-15 15:29         ` Markus Schönhaber
2008-03-15 18:49         ` Stroller
2008-03-15 13:27   ` Norberto Bensa
2008-03-15 13:44     ` Chris Brennan
2008-03-15 17:15       ` Volker Armin Hemmann
2008-03-15 18:57     ` Stroller
2008-03-15 14:20   ` Daniel Iliev

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=200803151812.48732.volker.armin.hemmann@tu-clausthal.de \
    --to=volker.armin.hemmann@tu-clausthal.de \
    --cc=gentoo-user@lists.gentoo.org \
    /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