From: Ian Zimmerman <itz@very.loosely.org>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: Bouncing Messages
Date: Thu, 1 Mar 2018 13:04:12 -0800 [thread overview]
Message-ID: <20180301210412.vo2qs7nipmvw23aw@matica.foolinux.mooo.com> (raw)
In-Reply-To: <CAAD4mYgC7dygQ6==7UejXKwjt1Ym9Dgab3bgtt_Ga24Ud0cPpg@mail.gmail.com>
On 2018-03-01 14:42, R0b0t1 wrote:
> I keep getting emails from the mailer daemon about bouncing messages.
> I am worried. Am I missing messages from my internet friends? Please
> send help.
Do you mean the crud from outlook/365? I get that too; it's probably
because my list mail lacks DKIM sigs (intentionally so). But whatever
the reason it's horrifying brain damage on their part to send the
bounces to _me_ rather than the envelope sender which is the bounce
address of the list. Micro$oft may have softened from the 90s but it's
still breaking standard protocols left and right, it seems.
I have just configured my MTA to send bounces from their IP ranges to
/dev/null.
--
Please don't Cc: me privately on mailing lists and Usenet,
if you also post the followup to the list or newsgroup.
To reply privately _only_ on Usenet and on broken lists
which rewrite From, fetch the TXT record for no-use.mooo.com.
next prev parent reply other threads:[~2018-03-01 21:04 UTC|newest]
Thread overview: 54+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-01 20:42 [gentoo-user] Bouncing Messages R0b0t1
2018-03-01 20:45 ` Branko Grubic
2018-03-01 22:38 ` Dale
2018-03-01 22:48 ` Branko Grubic
2018-03-01 23:53 ` [gentoo-user] " Ian Zimmerman
2018-03-02 0:12 ` Dale
2018-03-02 3:23 ` Ian Zimmerman
2018-03-02 4:21 ` Ian Zimmerman
2018-03-02 4:45 ` [gentoo-user] " Floyd Anderson
2018-03-02 5:28 ` Dale
2018-03-02 11:04 ` Floyd Anderson
2018-03-02 16:36 ` [gentoo-user] " Ian Zimmerman
2018-03-02 18:25 ` [gentoo-user] " Floyd Anderson
2018-03-02 22:51 ` [gentoo-user] " Grant Taylor
2018-03-03 0:47 ` Ian Zimmerman
2018-03-03 3:06 ` Grant Taylor
2018-03-03 14:47 ` [gentoo-user] " Stroller
2018-03-03 19:00 ` Grant Taylor
2018-03-03 19:22 ` Grant Taylor
2018-03-04 12:45 ` Stroller
2018-03-04 17:18 ` Grant Taylor
2018-03-02 21:52 ` Dale
2018-03-02 23:08 ` Grant Taylor
2018-03-02 23:59 ` Dale
2018-03-03 0:42 ` Grant Taylor
2018-03-02 0:24 ` Neil Bothwick
2018-03-02 2:00 ` Dale
2018-03-03 15:26 ` J. Roeleveld
2018-03-01 21:04 ` Ian Zimmerman [this message]
2018-03-02 15:26 ` Branko Grubic
2018-03-02 16:28 ` Daniel Frey
-- strict thread matches above, loose matches on Subject: below --
2023-01-13 10:12 [gentoo-user] Bouncing messages Peter Humphrey
2023-01-14 7:00 ` [gentoo-user] " Nuno Silva
2023-01-14 10:25 ` Peter Humphrey
2023-01-16 0:48 ` Jigme Datse
2023-01-16 12:03 ` David Rosenbaum
2023-01-18 8:59 ` Nuno Silva
2023-01-18 11:44 ` Peter Humphrey
2023-01-18 13:51 ` Jack
2023-01-18 15:07 ` Neil Bothwick
2023-01-18 23:02 ` Grant Taylor
2023-01-18 23:19 ` Dale
2023-01-19 0:05 ` David Rosenbaum
2023-01-20 5:59 ` Grant Taylor
2023-01-20 9:07 ` Dale
2023-01-20 14:44 ` Grant Taylor
2023-01-20 16:09 ` Peter Humphrey
2023-01-20 17:18 ` Grant Taylor
2023-01-20 12:20 ` Dr Rainer Woitok
2023-01-28 8:19 ` Nuno Silva
2023-01-19 8:56 ` Nuno Silva
2023-01-19 9:30 ` Peter Humphrey
2023-01-22 22:33 ` Peter Humphrey
2023-01-22 23:04 ` Michael
2023-01-24 13:03 ` Peter Humphrey
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=20180301210412.vo2qs7nipmvw23aw@matica.foolinux.mooo.com \
--to=itz@very.loosely.org \
--cc=gentoo-user@lists.gentoo.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