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 16:13:39 +0000 (GMT) [thread overview]
Message-ID: <alpine.LFD.2.21.2003221604570.2689954@eddie.linux-mips.org> (raw)
In-Reply-To: <8736a04ixv.fsf@mid.deneb.enyo.de>
On Sun, 22 Mar 2020, Florian Weimer wrote:
> > 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?
>
> No, this is not what happens (unless an open SMTP relay is involved,
> which is a different kind of problem).
>
> The error result from the DATA command is either observed directly by
> the spamming software (which does not generate a bounce message), or
> by some mail relay at an ISP. These relays check the envelope sender
> address before accepting a message for relaying, so if they need to
> generate a bounce, it will not be sent to an unrelated party.
What's the problem setting an own relay (or relay network) that accepts
and/or cooks up anything and then sends stuff to various places according
to the recipients given including say <gcc@gcc.gnu.org>? The ultimate
recipient's MTA is then far down the chain and its reject won't ever reach
the original actual sender's MTA. However it will hurt other people.
Maybe some spammers are so naïve as to (still) send directly, but the
"industry" has now had decades to learn and evolve.
Maciej
next prev parent reply other threads:[~2020-03-22 16:13 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
2020-03-22 13:29 ` Florian Weimer
2020-03-22 16:13 ` Maciej W. Rozycki [this message]
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.2003221604570.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).