From: Stanley Lieber <firstname.lastname@example.org>
Subject: Re: [9front] bounce test
Date: Tue, 26 Jul 2022 10:17:20 -0400 [thread overview]
Message-ID: <78EBAD18-8793-4742-BDBE-26BA5AE6A1DB@stanleylieber.com> (raw)
On July 26, 2022 1:19:55 AM EDT, Amavect <email@example.com> wrote:
>Sorry for the noise.
>This describes what I'm getting:
>--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, I've manually unsubscribed the address.
I hadn't received any of the suspect bounces.
next prev parent reply other threads:[~2022-07-26 14:18 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
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 [this message]
2022-07-26 17:43 ` smj
-- strict thread matches above, loose matches on Subject: below --
2022-07-26 4:33 [9front] Bounce Test Amavect
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).