public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Andreas Eibach" <a.eibach@gmx.net>
To: "David S. Miller" <davem@redhat.com>
Cc: <linux-kernel@vger.kernel.org>, <linux-kernel-owner@vger.kernel.org>
Subject: Re: Automatic Reply from Trash (fwd)
Date: Sat, 30 Mar 2002 22:26:01 +0100	[thread overview]
Message-ID: <02f501c1d831$7e491380$5cedfea9@andreas> (raw)
In-Reply-To: <Pine.LNX.4.44L.0203201832200.2181-100000@imladris.surriel.com> <20020320.140002.116838734.davem@redhat.com>


----- Original Message -----
From: "David S. Miller" <davem@redhat.com>
To: <riel@conectiva.com.br>
Cc: <linux-kernel@vger.kernel.org>; <linux-kernel-owner@vger.kernel.org>
Sent: Wednesday, March 20, 2002 11:00 PM
Subject: Re: Automatic Reply from Trash (fwd)

> I can't, there is no trash@* or *@thux.net subscribed to any
> list.
Common behavior, they use FAKE e-mails, fake headers and fake domain names.
Here in Germany, a lot of serious free-mail providers have complained about
the illegal abuse of their domain names. Thus, this has the effect to
entertain suspicion of the (innocent) free-mail provider.
> If this idiot would put a full received: header trace to his
> bounces we could actually do something.
Haha, just as probable as a burglar leaving his address and phone # for you
on the dining table after burglarizing your home <grin> ;-)

Andreas, quite experienced in handling all kinds of unwanted spam *sigh*


      parent reply	other threads:[~2002-03-30 21:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-20 21:33 Automatic Reply from Trash (fwd) Rik van Riel
2002-03-20 22:00 ` David S. Miller
2002-03-24 21:22   ` Thunder from the hill
2002-03-25  2:49     ` David S. Miller
2002-03-25 19:35       ` Thunder from the hill
2002-03-30 21:26   ` Andreas Eibach [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='02f501c1d831$7e491380$5cedfea9@andreas' \
    --to=a.eibach@gmx.net \
    --cc=davem@redhat.com \
    --cc=linux-kernel-owner@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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