All of lore.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk@arm.linux.org.uk>
To: aeriksson@fastmail.fm
Cc: cpufreq@www.linux.org.uk
Subject: Re: Spam coming from the list
Date: Mon, 27 Sep 2004 21:50:23 +0100	[thread overview]
Message-ID: <20040927215023.D26680@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20040927203501.AD5E63F03@latitude.mynet.no-ip.org>; from aeriksson@fastmail.fm on Mon, Sep 27, 2004 at 10:35:01PM +0200

On Mon, Sep 27, 2004 at 10:35:01PM +0200, aeriksson@fastmail.fm wrote:
> On Sun, 26 Sep 2004 21:51:57 BST Russell King wrote:
> >On Sun, Sep 26, 2004 at 06:24:46PM +0200, aeriksson@fastmail.fm wrote:
> >> I hate spam as much as the next guy, but filtering in at the mail list
> >> server it just not the Right Thing to do. It's an end2end problem and
> >> needs to have and end2end solution. All of us have private filers
> >> anyway, and we only run the risk of dropping legitimate mail.
> >
> >Disagree - peoples email systems actively reject spam, which causes
> >bounces.  The list interprets bounces as a failure of your address,
> >and with enough of them will disable and then unsubscribe you.
> >
> >Obviously bad news for the subscribers.
> >
> 
> Well that's pretty much the same man-in-the-middle attack on the feed
> as the maillist would do. My mail provider does that and I've asked
> them not to, but they refuse. They do it for all recipients on the
> smtp inlet, and  claim they have to send a bounce for leagal resons.
> Anyone know of a mailservice with a clean, untampered with, feed? (My 
> cable provider blocks 25).

This is off-topic for this list, and I guess interested parties should
continue in private mail... please?  If enough people want to discuss
this issue, I can setup an off-topic discussion list at www.linux.org.uk.
8)

There are three options to dealing with spam and viruses:
1. silently drop the message on the floor.
2. generate a bounce to the possibly forged return path address.
3. scan the messag at SMTP time and reject before accepting the
   message.

Any well behaved system uses solution (3) - chances are the incoming
SMTP connection is either directly from a virus or spam engine, in
which case rejecting the attempt does not create a bounce.

Obviously ISPs and companies certainly can not justify (1) as
acceptable behaviour on their part.  Maybe their setup doesn't allow
for (2), in which case they are just contributing to the spam and
virus problem.

Now, again, since this is an off-topic discussion for this list, can
we move it elsewhere please?

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:  2.6 PCMCIA      - http://pcmcia.arm.linux.org.uk/
                 2.6 Serial core

      reply	other threads:[~2004-09-27 20:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-26 14:45 Spam coming from the list Julio De Gregorio
2004-09-26 15:29 ` Russell King
2004-09-26 16:24 ` aeriksson
2004-09-26 20:51   ` Russell King
2004-09-27 11:51     ` Frank Mehnert
2004-09-27 12:16       ` David Pottage
2004-09-27 14:24     ` Harald Milz
2004-09-27 14:39       ` Dave Jones
2004-09-27 15:04         ` Harald Milz
2004-09-27 21:39           ` Francesco Poli
2004-09-27 20:35     ` aeriksson
2004-09-27 20:50       ` Russell King [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=20040927215023.D26680@flint.arm.linux.org.uk \
    --to=rmk@arm.linux.org.uk \
    --cc=aeriksson@fastmail.fm \
    --cc=cpufreq@www.linux.org.uk \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.