public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Erik Mouw <erik@harddisk-recovery.com>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Jesper Juhl <jesper.juhl@gmail.com>,
	Thomas Tuttle <thinkinginbinary@gmail.com>,
	richard.dent@nhs.net, linux-kernel@vger.kernel.org
Subject: Re: [OT] Vacation message heckling (Was: Re: Richard Dent - Annual Leave)
Date: Wed, 19 Jul 2006 11:14:24 +0200	[thread overview]
Message-ID: <20060719091424.GK2131@harddisk-recovery.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0607190001320.9666@yvahk01.tjqt.qr>

On Wed, Jul 19, 2006 at 12:04:26AM +0200, Jan Engelhardt wrote:
> The following note spans every "welcome" mail for some lists I run...
> 
> "Please make sure, should you be away, that *NO* auto-response messages
> (like "I'm out of office until ...") appear on the list. Failure to do
> so will get you removed from the mailing list."

Same on the linux-arm-* mailing lists, see
http://www.arm.linux.org.uk/mailinglists/etiquette.php#e11 .

Silly disclaimers always claim that the email shouldn't be
redistributed and that it is only for the "intended recipient". Because
the lists are publically archived beyond our control, messages are
redistributed. And with mailing lists, the "intended recipient" is very
vague: it apparently is "linux-arm-kernel@lists.arm.linux.org.uk" cause
that's what the "To:" header says, but OTOH it turns up in *my*
mailbox.

I usually protect people with such silly disclaimers against their own
company policy by switching their list subscription to "moderated":
they can still receive all messages from the list, but every message
they send must be OK'ed by the list admins. That turns out to work very
well: either they remove the disclaimer, or they use a webmail account
instead.

BTW: as an interesting side note: silly disclaimers are usually added
by top posting people. How are they ever to notice the disclaimer with
such a ridiculous reply style?


Erik
[linux-arm-*-owner #2]

-- 
+-- Erik Mouw -- www.harddisk-recovery.com -- +31 70 370 12 90 --
| Lab address: Delftechpark 26, 2628 XH, Delft, The Netherlands

      reply	other threads:[~2006-07-19  9:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-18  8:06 Richard Dent - Annual Leave Dent Richard
2006-07-18 13:27 ` [OT] Vacation message heckling (Was: Re: Richard Dent - Annual Leave) Thomas Tuttle
2006-07-18 14:43   ` Valdis.Kletnieks
2006-07-18 20:04     ` Hans-Peter Jansen
2006-07-18 20:30   ` Jesper Juhl
2006-07-18 21:31     ` Valdis.Kletnieks
2006-07-21  3:35       ` Craig Van Tassle
2006-07-21 11:31         ` Valdis.Kletnieks
2006-07-18 22:04     ` Jan Engelhardt
2006-07-19  9:14       ` Erik Mouw [this message]

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=20060719091424.GK2131@harddisk-recovery.com \
    --to=erik@harddisk-recovery.com \
    --cc=jengelh@linux01.gwdg.de \
    --cc=jesper.juhl@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=richard.dent@nhs.net \
    --cc=thinkinginbinary@gmail.com \
    /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