[BALUG-Admin] (forw) Bounce action notification
Sat Jul 30 23:13:36 UTC 2022
Rick, thanks for explaining what was happening and apologies to all who
were affected by the way I had things set up for my ewind.com domain. A
little bit of backstory. I had to quickly set up workarounds when I lost
several servers due to hardware failures and had to rebuild on existing
cloud based systems (anybody else using Nephohosting or have heard good or
bad about them?) and where gaps in coverage appeared, tried to cover them
That being said, I'd like to keep my BALUG mailing lists presence based on
my firstname.lastname@example.org address.
Also, any pointers to documentation on current best practices for building
network services (e-mail, Web, DNS)? Especially on cloud hosted platforms?
(e.g. Nephosting (or equivalent), AWS, etc). Most of the "How Tos" that
I've learned from in the past are now outdated.
Speaking of which, I also had to rebuild my collection of GNU Mailman
mailing lists on cloud hosted services since my hardware disasters also
swept those away. I'm guessing that the SPF/DMARC issues may be affecting
these too. Partly due to pricing and what reviews I was able to find at the
time, I ended up going to "Mailmanlists.net". Is the BALUG universe also on
a 3rd party hosted service which everyone is happy with? I'd be curious to
Thanks all for your patience.
- Hoover Chan (email@example.com)
On Sat, Jul 30, 2022 at 2:58 PM Rick Moen <firstname.lastname@example.org> wrote:
> It took me a moment to figure this out, because I was in a security talk
> at SCaLE 19x and was distracted.
> Hoover Chan did something that many people think is a good idea, but is
> not: Hoover subscribed "email@example.com" but set that mailbox to
> forward to his GMail mailbox, firstname.lastname@example.org .
> Hoover, sorry, in 2022 you can no longer do mail forwarding with wild
> abandon, because of increasing deployment of anti-forgery blocking
> technologies (SPF and DMARC).
> In this case, my posting to balug-admin was processed by list.balug.org
> and re-mailed to all subscribers including your email@example.com .
> Host nephoscale.ewind.com (IP 184.108.40.206) tried re-lobbing your
> subscriber copy to GMail, which rejected it because IP 220.127.116.11
> is not a permitted originator for mail from domain balug.org, i.e.,
> that IP as an SMTP source violates balug.org's SPF and DMARC
> I am deleting your subscriptions of firstname.lastname@example.org from
> balug-admin and from any other BALUG mailing list it might be on.
> (I haven't yet checked the other three.) I will also have Mailman
> send an "invitation" to quick-subscribe Hoover Chan <email@example.com>
> if you so wish.
> Please review your subscriptions to any _other_ mailing lists, and stop
> relying on firstname.lastname@example.org -> email@example.com forwarding.
> You really cannot rely on that, any more. TY.
> -- Rick Moen
> for the BALUG sysadmin team
> ----- Forwarded message from firstname.lastname@example.org -----
> Date: Sat, 30 Jul 2022 20:35:00 +0000
> From: email@example.com
> To: firstname.lastname@example.org
> Subject: Bounce action notification
> X-Spam-Status: No, score=-2.6 required=4.0
> NO_REAL_NAME,SPF_PASS,T_TVD_MIME_NO_HEADERS autolearn=ham
> This is a Mailman mailing list bounce action notice:
> List: BALUG-Admin
> Member: email@example.com
> Action: Subscription disabled.
> Reason: Excessive or fatal bounces.
> The triggering bounce notice is attached below.
> Questions? Contact the Mailman site administrator at
> Received: from static-18.104.22.168.nephohosting.com ([22.214.171.124]
> by balug-sf-lug-v2.balug.org with esmtps
> (Exim 4.92)
> id 1oHtAp-00053A-No
> for firstname.lastname@example.org; Sat, 30 Jul 2022
> 20:34:59 +0000
> Received: from localhost (localhost)
> by nephoscale.ewind.com (8.14.4/8.14.4) id 26UKUlVD005544;
> Sat, 30 Jul 2022 13:30:47 -0700
> Date: Sat, 30 Jul 2022 13:30:47 -0700
> From: Mail Delivery Subsystem <MAILER-DAEMON@nephoscale.ewind.com>
> Message-Id: <202207302030.26UKUlVD005544@nephoscale.ewind.com>
> To: <email@example.com>
> MIME-Version: 1.0
> Content-Type: multipart/report; report-type=delivery-status;
> Subject: Returned mail: see transcript for details
> Auto-Submitted: auto-generated (failure)
> Received-SPF: none client-ip=126.96.36.199; helo=nephoscale.ewind.com
> The original message was received at Sat, 30 Jul 2022 13:30:41 -0700
> from balug.org [188.8.131.52]
> ----- The following addresses had permanent fatal errors -----
> (reason: 550-5.7.26 This message does not pass authentication checks
> (SPF and DKIM both)
> (expanded from: <firstname.lastname@example.org>)
> ----- Transcript of session follows -----
> ... while talking to gmail-smtp-in.l.google.com.:
> >>> DATA
> <<< 550-5.7.26 This message does not pass authentication checks (SPF and
> DKIM both
> <<< 550-5.7.26 do not pass). SPF check for [lists.balug.org] does not
> pass with ip:
> <<< 550-5.7.26 [184.108.40.206].To best protect our users from spam, the
> <<< 550-5.7.26 has been blocked. Please visit
> <<< 550-5.7.26
> https://support.google.com/mail/answer/81126#authentication for more
> <<< 550 5.7.26 information.
> f5-20020a62db05000000b0052c708707dbsi7062217pfg.121 - gsmtp
> 554 5.0.0 Service unavailable
> Reporting-MTA: dns; nephoscale.ewind.com
> Received-From-MTA: DNS; balug.org
> Arrival-Date: Sat, 30 Jul 2022 13:30:41 -0700
> Final-Recipient: RFC822; email@example.com
> X-Actual-Recipient: RFC822; firstname.lastname@example.org
> Action: failed
> Status: 5.7.26
> Remote-MTA: DNS; gmail-smtp-in.l.google.com
> Diagnostic-Code: SMTP; 550-5.7.26 This message does not pass
> authentication checks (SPF and DKIM both
> Last-Attempt-Date: Sat, 30 Jul 2022 13:30:42 -0700
> Return-Path: <email@example.com>
> Received: from balug-sf-lug-v2.balug.org (balug.org [220.127.116.11])
> by nephoscale.ewind.com (8.14.4/8.14.4) with ESMTP id
> for <firstname.lastname@example.org>; Sat, 30 Jul 2022 13:30:41 -0700
> Received: from localhost ([127.0.0.1] helo=balug.org)
> by balug-sf-lug-v2.balug.org with esmtp (Exim 4.92)
> (envelope-from <email@example.com>)
> id 1oHtAc-00052G-8o; Sat, 30 Jul 2022 20:34:46 +0000
> Received: from linuxmafia.com ([18.104.22.168])
> by balug-sf-lug-v2.balug.org with esmtps
> (Exim 4.92) (envelope-from <firstname.lastname@example.org>) id 1oHtAZ-000526-W5
> for email@example.com; Sat, 30 Jul 2022 20:34:44 +0000
> Received: from rick by linuxmafia.com with local (Exim 4.72)
> (envelope-from <firstname.lastname@example.org>) id 1oHtAX-0001P2-QB
> for email@example.com; Sat, 30 Jul 2022 13:34:41 -0700
> Date: Sat, 30 Jul 2022 13:34:41 -0700
> From: Rick Moen <firstname.lastname@example.org>
> To: email@example.com
> Message-ID: <20220730203441.GI13985@linuxmafia.com>
> References: <20220726022507.GV13985@linuxmafia.com>
> MIME-Version: 1.0
> Content-Disposition: inline
> In-Reply-To: <20220726022507.GV13985@linuxmafia.com>
> Organization: If you lived here, you'd be $HOME already.
> X-Mas: Bah humbug.
> X-Clacks-Overhead: GNU Terry Pratchett
> User-Agent: Mutt/1.5.20 (2009-06-14)
> X-SA-Exim-Connect-IP: <locally generated>
> X-SA-Exim-Mail-From: firstname.lastname@example.org
> X-SA-Exim-Scanned: No (on linuxmafia.com); SAEximRunCond expanded to false
> Received-SPF: pass client-ip=22.214.171.124; envelope-from=
> Subject: Re: [BALUG-Admin] Spamtraps and
> X-BeenThere: email@example.com
> X-Mailman-Version: 2.1.29
> Precedence: list
> List-Id: Discussion among those who make BALUG work
> List-Unsubscribe: <
> List-Archive: <https://lists.balug.org/pipermail/balug-admin/>
> List-Post: <mailto:firstname.lastname@example.org>
> List-Help: <mailto:email@example.com?subject=help>
> List-Subscribe: <
> Content-Type: text/plain; charset="us-ascii"
> Content-Transfer-Encoding: 7bit
> Errors-To: firstname.lastname@example.org
> Sender: "BALUG-Admin" <email@example.com>
> ----- End forwarded message -----
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the BALUG-Admin