public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: "Maciej W. Rozycki" <macro@linux-mips.org>
To: Florian Weimer <fw@deneb.enyo.de>
Cc: "Frank Ch. Eigler" <fche@redhat.com>,
	overseers@gcc.gnu.org, gcc mailing list <gcc@gcc.gnu.org>,
	Overseers mailing list <overseers@sourceware.org>,
	Thomas Koenig <tkoenig@netcologne.de>
Subject: Re: Spam, bounces and gcc list removal
Date: Sun, 22 Mar 2020 13:24:03 +0000 (GMT)	[thread overview]
Message-ID: <alpine.LFD.2.21.2003221312000.2689954@eddie.linux-mips.org> (raw)
In-Reply-To: <87k13c4v5m.fsf@mid.deneb.enyo.de>

On Sun, 22 Mar 2020, Florian Weimer wrote:

> >  Spam bouncing is evil and often hits an innocent person whose address has 
> > been faked by the sender of spam, making the source of bounces not better 
> > than the originator.
> 
> I expect this to be an SMTP-level rejection, not a bounce.  sourceware
> generates a bounce from that, and Mailman reacts to that.  But the
> target mail server does not generate a bounce.  So your concern about
> bad ISP behavior does not apply here.

 You mean as with a failure response given to the SMTP DATA command?  
This is actually equally evil as the resulting bounce (i.e. a delivery 
failure notification, or a flood of them, once other MTAs have joined in a 
response to a mass mailing; that is exactly what I suffered from a few 
years ago) will hit whoever's fake envelope sender address has been given 
with the MAIL FROM command.  You don't expect a real one with spam, do 
you?

 As I say, just silently drop it on the floor, this is the least harmful 
way of dealing with spam.  And sometimes indirectly blocking a specific 
e-mail address chosen to look like a source of spam *will be* the actual 
objective of what looks like usual spam.

  Maciej

  reply	other threads:[~2020-03-22 13:24 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-15 12:24 Thomas Koenig
2020-03-21 19:39 ` Thomas Koenig
2020-03-21 20:08   ` H.J. Lu
2020-03-22  2:39     ` Oleg Endo
2020-03-21 20:29   ` Frank Ch. Eigler
2020-03-21 21:22     ` Maciej W. Rozycki
2020-03-22  8:01       ` Winfried Magerl
2020-03-22 16:35         ` Maciej W. Rozycki
2020-03-22  9:05       ` Florian Weimer
2020-03-22 13:24         ` Maciej W. Rozycki [this message]
2020-03-22 13:29           ` Florian Weimer
2020-03-22 16:13             ` Maciej W. Rozycki
2020-03-22  9:54     ` Thomas Koenig

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=alpine.LFD.2.21.2003221312000.2689954@eddie.linux-mips.org \
    --to=macro@linux-mips.org \
    --cc=fche@redhat.com \
    --cc=fw@deneb.enyo.de \
    --cc=gcc@gcc.gnu.org \
    --cc=overseers@gcc.gnu.org \
    --cc=overseers@sourceware.org \
    --cc=tkoenig@netcologne.de \
    /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).