From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Jamal Hadi Salim <jhs@mojatatu.com>,
Linux Kernel Network Developers <netdev@vger.kernel.org>
Cc: Jakub Kicinski <kuba@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Konstantin Ryabitsev <konstantin@linuxfoundation.org>
Subject: Re: netdev email issues?
Date: Sun, 9 Apr 2023 19:45:59 +0700 [thread overview]
Message-ID: <ZDKzhyCAYdAcu6H9@debian.me> (raw)
In-Reply-To: <CAM0EoMkuv=3C_jsn6NEsWoGBBzL2WDSNAOWxTfJ-Oh8xfJs1Fg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1538 bytes --]
On Sat, Apr 08, 2023 at 09:48:12AM -0400, Jamal Hadi Salim wrote:
> ---------- Forwarded message ---------
> From: Postmaster <postmaster@dopamine-today.bounceio.net>
> Date: Sat, Apr 8, 2023 at 3:53 AM
> Subject: Undeliverable: Re: [PATCH v4 net-next 2/9] net/sched: mqprio:
> simplify handling of nlattr portion of TCA_OPTIONS
> To: <jhs@mojatatu.com>
>
>
> MESSAGE NOT DELIVERED
>
> There was an issue delivering your message to got@dopamine.today. This
> is an 5.1.2 Error.
>
> This error typically means: The domain name of the email address is not valid
But dig(1)-ing the domain in question shows no error:
```
; <<>> DiG 9.16.37-Debian <<>> dopamine.today
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 55123
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;dopamine.today. IN A
;; ANSWER SECTION:
dopamine.today. 300 IN A 91.195.240.94
;; Query time: 433 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Sun Apr 09 19:41:03 WIB 2023
;; MSG SIZE rcvd: 59
```
And because of now-frequent this annoying bounce, I have to tell gmail to
block Postmaster of this domain (i.e. the one that send this bounce). Thus,
it is likely that the problem is email routing.
Konstantin, would you like to have a look on this?
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-04-09 12:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <365242745.7238033.1680940391036@mrd-tw.us-east-1.eo.internal>
2023-04-08 13:48 ` netdev email issues? Jamal Hadi Salim
2023-04-09 12:45 ` Bagas Sanjaya [this message]
2023-04-11 18:35 ` Konstantin Ryabitsev
2023-04-12 2:13 ` Bagas Sanjaya
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=ZDKzhyCAYdAcu6H9@debian.me \
--to=bagasdotme@gmail.com \
--cc=davem@davemloft.net \
--cc=jhs@mojatatu.com \
--cc=konstantin@linuxfoundation.org \
--cc=kuba@kernel.org \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).