From: Amavect <amavect@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] bounce test
Date: Tue, 26 Jul 2022 00:19:55 -0500 [thread overview]
Message-ID: <CAGOW0YPygwK1HWkZfZCm944Lb5ufwQxdUA_tHVnEC1g04Gj5ug@mail.gmail.com> (raw)
In-Reply-To: <CLPB8ZUSHT7P.18667CP1YSCOV@aphrodite.pulpie.local>
Sorry for the noise.
This describes what I'm getting:
https://groups.google.com/g/linux.debian.user/c/2nEZ3tTTJ4k
--Begin bounce message (in HTML)--
© 2017 betterbounces.net, All rights reserved. Privacy
Your email was bounced...
... because something went wrong between you and your recipient. Bummer!
What to do next?
Well, your specific problem was a 5.1.2 error.
The domain you attempted to contact, oboj.net, may have expired. You
can check WHOIS for oboj.net here to determine if this is the case.
If so, contact your recipient another way (e.g., phone or text
message) to confirm their email address.
Get more help on 5.1.2 errors here!
Thanks, have a lovely day.
Yours truly, betterbounces.net
Rate this email: Helpful :) or... Not Helpful :(
--End bounce message--
From what I can gather, some address on the mailing list with domain
oboj.net is dead,
and bounce.io/betterbounces.net is some spam company that hijacks
bounce messages and injects ads.
They then reply to the sender and not the mailing list.
I wonder if this has hit others' spam folders. This got past gmail's.
Thanks,
Amavect
next prev parent reply other threads:[~2022-07-26 5:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-26 4:41 B. Atticus Grobe
2022-07-26 5:19 ` Amavect [this message]
2022-07-26 5:31 ` william
2022-07-26 5:34 ` William Gunnells
2022-07-26 5:40 ` william
2022-07-26 14:17 ` Stanley Lieber
2022-07-26 17:43 ` smj
-- strict thread matches above, loose matches on Subject: below --
2022-07-26 4:33 [9front] Bounce Test Amavect
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=CAGOW0YPygwK1HWkZfZCm944Lb5ufwQxdUA_tHVnEC1g04Gj5ug@mail.gmail.com \
--to=amavect@gmail.com \
--cc=9front@9front.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).