Question on /var/lib/mailman/archives/private/LISTNAME/attachments/
I see files in var/lib/mailman/archives/private/LISTNAME/attachments/. I did some searching and found that :
The stored attachments have been scrubbed from the 'plain' format digest. This happens whether or not anyone actually subscribes to the 'plain' format digest. The only way to avoid it with configuration settings is to set Digest options -> digestable to No (i.e. disable digests).
Otherwise, you could set up a cron to periodically remove them, but then if you actually have 'plain' digest sebscribers, you'll break the links in their digests.
Some of the lists that that files in attachments does not have archived turned on and no users do not have digest set.
So if I under stand this these attachments are kept because under “digest options” “digestible is set to “on”. Is that correct? So even if no user have digest on , the list keeps attachments?
So what is the best way to clear these files, can I just clear out the attachments directory? If no users have digest set , then this will be un notable. But if user have digest on and it is set to PLAIN, then that could be an issue?
On 3/12/21 12:51 PM, Bader, Robert (Bob) wrote:
I see files in var/lib/mailman/archives/private/LISTNAME/attachments/. I did some searching and found that :
You posted this exact message to this list two days ago and it was answered then. See https://mail.python.org/archives/list/mailman-users@python.org/thread/U5AWXTP2TPQKL2TDBMMYUEXQZLPB2HSI/.
Hello,
It appears to be starting again for our list. Fatal bounces but ONLY on ATT.net. Here is what Google says:
DMARC and DKIM passed. However, this may have been the bounce message to me.
Below is the bounce message to me. I see a DKIM Pass and a DKIM Fail. Can anyone shed any other light as to why these ATT addresses are ALL failing?
Thanks, Steve
=====================================================================================================================
Delivered-To: slund348@gmail.com Received: by 2002:a50:379b:0:0:0:0:0 with SMTP id a27csp1420942ecc; Fri, 12 Mar 2021 08:50:47 -0800 (PST) X-Google-Smtp-Source: ABdhPJxug5H8zWZ5WehgGW9Eo2BCkOq6QQzbXrn/8EFInEkMsX0u4V54vXbKmVBEgeBkxHx/pQXm X-Received: by 2002:a25:3b04:: with SMTP id i4mr20275766yba.160.1615567847574; Fri, 12 Mar 2021 08:50:47 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1615567847; cv=none; d=google.com; s=arc-20160816; b=WmCMJ6Dp1O7rScSP4Bssq3+Fucf35qP2E92CDWxOyGylprCDHyG2yby3aL1qBG2YyN vItFfsISDwChuVWeg4ULb27WDDEVyDdYAKPcbEfoSyWxdJLUmPl2R4XpZr/Vw4/1U1eT MiW1Y3HLISbcOHLoVw3S2gFIY1bIrI8knZhUb4HGsXU6VvN/nLNQeRg0vMVJLKKw3m7v elEUTYotNQFApx/JLZzhrkoZgextRdvGaxOKC21yUWeaVoVc0P30pc00JNP/PdNlXQ0M Tyd0gIdrvzZSywS0lW33S/zwNklbBwONgRBC3tr23e2kBTKC8q+KI32JCXk9VHOsrHXH uejw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=sender:errors-to:list-id:precedence:date:message-id:mime-version:to :from:subject:dkim-signature:delivered-to:dkim-signature; bh=+KoYLe/u2BsMykVMJTWEbIVkHJSjKpwBokxJFqNz2Rc=; b=tRtbwMpdiAAHapKX3NhVtKYYQo5jZrWdMYymgFmWmi8XIh9w7Nv3slRD4C1x15xkI8 6OYzFWDkiKiXKC2uqN9zk0C/KGdhGciTAiUocBE9JpQbkUaDXHPb97v31dfSHu6rVVNN wn1o37HJcRqbD9to2sEfMR0izZzTIshSdLLDWeSj3S1Y9MVdZoV92eXNgeLQ9sIpn0Vz WSEPJALVxfxmZ00RGr+XyTbMpfs0Q+gpnfa+/QIltGIqU1WEDs0I23Flotp+LIRPwawG 6TDuAzIaBOJIo6Z4jM0ELWQGcKJSanQp1sq1OkoG+vfnVvy2dTwO/ie2wMN1NAS/iyiq 7vMg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@msinglinks.org header.s=201912 header.b=Opkav72l; dkim=fail header.i=@msinglinks.org header.s=201912 header.b=luOWzzsL; spf=pass (google.com: domain of mailman-bounces@lists.deltaforce.net designates 45.33.97.191 as permitted sender) smtp.mailfrom=mailman-bounces@lists.deltaforce.net; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=lists.msinglinks.org Return-Path: mailman-bounces@lists.deltaforce.net Received: from duke.deltaforce.net (duke.deltaforce.net. [45.33.97.191]) by mx.google.com with ESMTP id z131si5470913yba.182.2021.03.12.08.50.47 for slund348@gmail.com; Fri, 12 Mar 2021 08:50:47 -0800 (PST) Received-SPF: pass (google.com: domain of mailman-bounces@lists.deltaforce.net designates 45.33.97.191 as permitted sender) client-ip=45.33.97.191; Authentication-Results: mx.google.com; dkim=pass header.i=@msinglinks.org header.s=201912 header.b=Opkav72l; dkim=fail header.i=@msinglinks.org header.s=201912 header.b=luOWzzsL; spf=pass (google.com: domain of mailman-bounces@lists.deltaforce.net designates 45.33.97.191 as permitted sender) smtp.mailfrom=mailman-bounces@lists.deltaforce.net; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=lists.msinglinks.org Received: from duke.deltaforce.net (localhost [IPv6:::1]) by duke.deltaforce.net (Postfix) with ESMTP id CDD5B200BF for slund348@gmail.com; Fri, 12 Mar 2021 11:50:09 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=msinglinks.org; s=201912; t=1615567809; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:mime-version:mime-version: content-type:content-type:list-id; bh=+KoYLe/u2BsMykVMJTWEbIVkHJSjKpwBokxJFqNz2Rc=; b=Opkav72lpDlC1h0cnXJ0CHa+SFiP6Vkx2Lhpsq7N1eHULm2tXll7tWnFV5X1durZ+jA8C6 T5cRp+tdVf4VtlRexP1N9Wt3Owj+mGrSogLR1P5TyMqKe6A6d5Ig0L1pM8DLMIGEoSpa/1 NkgQPhsfgDKVtagW0D89jKBwbKL0lvU= X-Original-To: msing-ride-owner@lists.msinglinks.org Delivered-To: msing-ride-owner@duke.deltaforce.net Received: from duke.deltaforce.net (localhost [IPv6:::1]) by duke.deltaforce.net (Postfix) with ESMTP id 90BDF20082 for msing-ride-owner@lists.msinglinks.org; Fri, 12 Mar 2021 11:50:08 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=msinglinks.org; s=201912; t=1615567808; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:mime-version:mime-version: content-type:content-type:list-id; bh=+KoYLe/u2BsMykVMJTWEbIVkHJSjKpwBokxJFqNz2Rc=; b=luOWzzsLIEg5lxOvmSlgeC2wmzOQyuznZo9grRuS9Kduzw8JjY7Fp3VmadXRpWCVnGQzhU rxACCrJ6N7udOrBVG2Fwbu/lUwheDOGYB4J0fq5BPZO0Ti596Fp6o+XNMThfVZGak+LVBZ cCR4DZAfSeU6itv6ZSMb3fG8gV73rRk= Subject: Bounce action notification From: mailman@lists.msinglinks.org To: msing-ride-owner@lists.msinglinks.org MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0332406003479489569==" Message-ID: mailman.3.1615567806.2191127.msing-ride@lists.msinglinks.org Date: Fri, 12 Mar 2021 11:50:06 -0500 Precedence: list X-BeenThere: msing-ride@lists.msinglinks.org X-Mailman-Version: 2.1.34 List-Id: MSing Links Ride Announce / Chat List <msing-ride.lists.msinglinks.org> X-List-Administrivia: yes Errors-To: mailman-bounces@lists.deltaforce.net Sender: MSing-ride mailman-bounces@lists.deltaforce.net
--===============0332406003479489569== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit
This is a Mailman mailing list bounce action notice:
List: MSing-ride
Member: toddholcomb@bellsouth.net
Action: Subscription bounce score incremented.
Reason: Excessive or fatal bounces.
The triggering bounce notice is attached below.
Questions? Contact the Mailman site administrator atmailman@lists.msinglinks.org.
--===============0332406003479489569== Content-Type: message/rfc822 MIME-Version: 1.0
Return-Path: <> X-Original-To: msing-ride-bounces@lists.msinglinks.org Delivered-To: msing-ride-bounces@duke.deltaforce.net Received: by duke.deltaforce.net (Postfix) id D2E7C200B0; Fri, 12 Mar 2021 11:50:05 -0500 (EST) Date: Fri, 12 Mar 2021 11:50:05 -0500 (EST) From: Mail Delivery System MAILER-DAEMON@duke.deltaforce.net Subject: Undelivered Mail Returned to Sender To: msing-ride-bounces@lists.msinglinks.org Auto-Submitted: auto-replied MIME-Version: 1.0 Content-Type: multipart/report; report-type=delivery-status; boundary="DA50A20082.1615567805/duke.deltaforce.net" Content-Transfer-Encoding: 8bit Message-Id: 20210312165005.D2E7C200B0@duke.deltaforce.net
--DA50A20082.1615567805/duke.deltaforce.net Content-Description: Notification Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit
This is the mail system at host duke.deltaforce.net.
I'm sorry to have to inform you that your message could not be delivered to one or more recipients. It's attached below.
For further assistance, please send mail to postmaster.
If you do so, please include this problem report. You can delete your own text from the attached returned message.
The mail system
kurtehlert@att.net: host ff-ip4-mx-vip1.prodigy.net[144.160.159.21] said: 553 5.3.0 flpd599 DNSBL:RBL 521< 45.33.97.191 >_is_blocked.For assistance forward this error to abuse_rbl@abuse-att.net (in reply to MAIL FROM command)
shecht2@att.net: host ff-ip4-mx-vip1.prodigy.net[144.160.159.21] said: 553 5.3.0 flpd599 DNSBL:RBL 521< 45.33.97.191 >_is_blocked.For assistance forward this error to abuse_rbl@abuse-att.net (in reply to MAIL FROM command)
drhillia@bellsouth.net: host al-ip4-mx-vip2.prodigy.net[144.160.235.144] said: 553 5.3.0 alph761 DNSBL:RBL 521< 45.33.97.191 >_is_blocked.For assistance forward this error to abuse_rbl@abuse-att.net (in reply to MAIL FROM command)
toddholcomb@bellsouth.net: host al-ip4-mx-vip2.prodigy.net[144.160.235.144] said: 553 5.3.0 alph761 DNSBL:RBL 521< 45.33.97.191 >_is_blocked.For assistance forward this error to abuse_rbl@abuse-att.net (in reply to MAIL FROM command)
--DA50A20082.1615567805/duke.deltaforce.net Content-Description: Delivery report Content-Type: message/delivery-status
--DA50A20082.1615567805/duke.deltaforce.net Content-Description: Undelivered Message Content-Type: message/rfc822 Content-Transfer-Encoding: 8bit
Return-Path: msing-ride-bounces@lists.msinglinks.org Received: from duke.deltaforce.net (localhost [IPv6:::1]) by duke.deltaforce.net (Postfix) with ESMTP id DA50A20082; Fri, 12 Mar 2021 11:49:57 -0500 (EST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=msinglinks.org; s=201912; t=1615567797; h=from:from:sender:sender:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:list-id:list-help: list-unsubscribe:list-subscribe:list-post; bh=8bK3Fk6sDzStm58/kuHQni6rLCs5pUKkQJlb5ycuOtE=; b=vFrFzKVyw1/DzdbNF1gqyWaMCqgNSBmDzputOyqcYz7lRWrOx8L9hXTP+0qllG3Z7K779w i7WwyvDPVDMx7EUu/eBsN1lDOv0V5uJAwuPtfwlV4G5V1j6dXgp66rW69ZqElYJ1z58xRv L5rYiBWwkmzvnovzAnYCSFE0S80fFHg= X-Original-To: MSing-ride@lists.msinglinks.org Delivered-To: msing-ride@duke.deltaforce.net Received: from mail-ed1-x534.google.com (mail-ed1-x534.google.com [IPv6:2a00:1450:4864:20::534]) by duke.deltaforce.net (Postfix) with ESMTP id D257D20081 for MSing-ride@lists.msinglinks.org; Fri, 12 Mar 2021 11:49:55 -0500 (EST) Received: by mail-ed1-x534.google.com with SMTP id y6so8863508eds.1 for MSing-ride@lists.msinglinks.org; Fri, 12 Mar 2021 08:49:55 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=iRngJPyGcBeYxUV+6uTNF+98a2Gb6VJGB03b1JsT3qo=; b=Ou3pCchODFHIYQcmk2cApXmhBDp1hb0zWIqyK6IC7geUwRK3NnwaPgTN1PBtUmt0Dg mMhm/G3oG9qp96XyZBnnonamYYTz3GPCX30E18b9+0G/GdeEX/o6828vpBK6/eQcG5Et IDErwKwFje3BtYv1c5SZ4EkOb0AmjCxgs1vZQRth6gZ3O6gK9cYz8WDIlt2xUZGd1r3T 8/tDn1Vp+FqB9aDt7XMiMHZT/KAA/RO4UApzRjglq0G+ASYEIgnMVznXP95U9VCGJ+jK SjnK2jEh1mpW8pbvshm/KDx7w2/JXiEy4itEtthH0DS7rOq1nKBGF+2G0npTlSwFq4xZ k4yg== X-Gm-Message-State: AOAM532PHl1qXo8pJl6fHlz2deoxgC1xKFRyFkIsmgpYl0GBJuDsjwbS 2WPotIy+4isBJGeeJZI7TQ+Va13j8aKGYtPQe965goXbgzY= X-Google-Smtp-Source: ABdhPJx/H4xwhKfOvaMhQDSpVXuIaIhF1du4Oo0un05XnFZV3mfbzkP7rvysm1fLiyA9NKJZr3WIG6cRjrmFbJTdAnE= X-Received: by 2002:a05:6402:cb8:: with SMTP id cn24mr15481310edb.105.1615567795132; Fri, 12 Mar 2021 08:49:55 -0800 (PST) MIME-Version: 1.0 References: 80B8BE53-218A-4116-A2EA-183D3BF171E1@yahoo.com F7F6FDF0-D47E-438E-A656-9267312BB797@yahoo.com In-Reply-To: F7F6FDF0-D47E-438E-A656-9267312BB797@yahoo.com Date: Fri, 12 Mar 2021 11:49:44 -0500 Message-ID: CAKPKP=di8_sqhLXvGzetFok+-1Bgy-MPd=fE+szgaPNcgoiAjQ@mail.gmail.com To: Doug Hoffman hoffman_doug@yahoo.com Cc: MSing Links Ride List MSing-ride@lists.msinglinks.org ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=msinglinks.org; s=201912; t=1615567796; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references:dkim-signature; bh=iRngJPyGcBeYxUV+6uTNF+98a2Gb6VJGB03b1JsT3qo=; b=tLfEwXymxrMV/T96uC1TUBGJl3+g/vCY5B1AMJSFsnxK7YcDRjJM+lPo36WRCiXb7y/rnv jhm/xrBRw6jp66g9W+mhivU2xIsUchP61OjraW2VNCJJEM/iSJrfWcGlkhRX68l9TDfjZn 1HBxRjZ+bQnpWrQctqoEljtn3TBThTw= ARC-Seal: i=1; s=201912; d=msinglinks.org; t=1615567796; a=rsa-sha256; cv=none; b=NKhQzQo4tNq9pjt/ydOIzXl3bS1CBlNFw+kydNDDhzWrVR8qatwA89kUow7ihZiqSx1l1n kebHcdUkgN0syLyKcYjiIjgnh8CzJfkwngvV0Uy63S7SXf3f7hyso0Ov5aM+iEJ2TrUshM vE7EMrtXaH3JkJteAYeRMRr1fsG4v9w= ARC-Authentication-Results: i=1; duke.deltaforce.net; dkim=pass header.d=gmail.com header.s=20161025 header.b=YnQikTpv; spf=pass (duke.deltaforce.net: domain of donaldrbelk@gmail.com designates 2a00:1450:4864:20::534 as permitted sender) smtp.mailfrom=donaldrbelk@gmail.com X-Spam-Status: No, score=-3.94 X-Content-Filtered-By: Mailman/MimeDel 2.1.34 Subject: Re: [MSing_Links-Ride] MSLinks X-BeenThere: msing-ride@lists.msinglinks.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: MSing Links Ride Announce / Chat List <msing-ride.lists.msinglinks.org> List-Unsubscribe: https://lists.msinglinks.org/mailman/options/msing-ride, mailto:msing-ride-request@lists.msinglinks.org?subject=unsubscribe List-Archive: https://lists.msinglinks.org/mailman/private/msing-ride/ List-Post: mailto:msing-ride@lists.msinglinks.org List-Help: mailto:msing-ride-request@lists.msinglinks.org?subject=help List-Subscribe: https://lists.msinglinks.org/mailman/listinfo/msing-ride, mailto:msing-ride-request@lists.msinglinks.org?subject=subscribe From: Donald Belk via MSing-ride msing-ride@lists.msinglinks.org Reply-To: Donald Belk donaldrbelk@gmail.com Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: base64 Errors-To: msing-ride-bounces@lists.msinglinks.org Sender: MSing-ride msing-ride-bounces@lists.msinglinks.org
VGhhbmtzIGZvciBwb3N0aW5nLCBEb3VnLiAgVGhlIG1vcmUgcmlkZXMgdGhlIG1lcnJpZXIhICBZ J2FsbCBoYXZlIGEgZ3JlYXQKb25lIC0KCkRvbgoKT24gRnJpLCBNYXIgMTIsIDIwMjEgYXQgMTE6 MDUgQU0gRG91ZyBIb2ZmbWFuIHZpYSBNU2luZy1yaWRlIDwKbXNpbmctcmlkZUBsaXN0cy5tc2lu Z2xpbmtzLm9yZz4gd3JvdGU6Cgo+IEZvciB0aG9zZSBub3QgcGFydGljaXBhdGluZyBpbiB0aGUg IEh1Z2dlciBNdWdnZXIgRGVzdGluYXRpb24gUmlkZSBpbgo+IFNhbmZvcmQgdG9tb3Jyb3cgd2Ug b2ZmZXIgdGhlIGZvbGxvd2luZyBvcHRpb24uCj4KPiBMZXTigJlzIHJpZGUgQ29yaW50aCBMb29w IFNhdHVyZGF5LCBhcHByb3hpbWF0ZWx5IDQyIG1pbGVzLgo+Cj4gU3RhcnQgdGltZSAtIEFwZXgg TmF0dXJlIFBhcmssIDkgYW0KPgo+IEhvcGUgdG8gc2VlIHlvdSB0aGVyZSEKPgo+Cj4KPiBfX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXwo+IE1TaW5nLXJpZGUg bWFpbGluZyBsaXN0Cj4gTVNpbmctcmlkZUBsaXN0cy5tc2luZ2xpbmtzLm9yZwo+IGh0dHBzOi8v bGlzdHMubXNpbmdsaW5rcy5vcmcvbWFpbG1hbi9saXN0aW5mby9tc2luZy1yaWRlCj4KX19fX19f X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KTVNpbmctcmlkZSBtYWls aW5nIGxpc3QKTVNpbmctcmlkZUBsaXN0cy5tc2luZ2xpbmtzLm9yZwpodHRwczovL2xpc3RzLm1z aW5nbGlua3Mub3JnL21haWxtYW4vbGlzdGluZm8vbXNpbmctcmlkZQo=
--DA50A20082.1615567805/duke.deltaforce.net--
--===============0332406003479489569==--
On 3/12/21 1:39 PM, steve lund wrote:
Hello,
It appears to be starting again for our list. Fatal bounces but ONLY on ATT.net. Here is what Google says:
...
...@att.net: host ff-ip4-mx-vip1.prodigy.net[144.160.159.21] said: 553 5.3.0 flpd599 DNSBL:RBL 521< 45.33.97.191 >_is_blocked.For assistance forward this error to abuse_rbl@abuse-att.net (in reply to MAIL FROM command)
It may be a coincidence, but I started seeing the same bounces on one of my servers (thankfully not mail.python.org or lists.mailman3.org) about two days ago.
ATT is blocking your IP.
In my case, I sent this to abuse_rbl@abuse-att.net.
You are blocking all mail from IP 138.68.52.125 per this log message.
Mar 12 09:59:32 grizz postfix/smtp[10965]: D0CAF1F8123: to=<...>, relay=ff-ip4-mx-vip2.prodigy.net[144.160.159.22]:25, delay=0.38, delays=0.1/0/0.27/0.01, dsn=5.3.0, status=bounced (host ff-ip4-mx-vip2.prodigy.net[144.160.159.22] said: 553 5.3.0 flph832 DNSBL:RBL 521< 138.68.52.125 >_is_blocked.For assistance forward this error to abuse_rbl@abuse-att.net (in reply to MAIL FROM command))
This mail is from an opt-in email discussion list or other business related mail from a bicycle club. We do not send spam or unsolicited commercial email. Please remove this block.
I received this reply.
Thank you for contacting the AT&T Postmaster Staff.
We investigate every block report and removal request we receive and take the appropriate action, of which you will be notified. It is never the intention of the AT&T Postmaster staff to block legitimate mail. It is a rare but unfortunate occurrence that legitimate correspondence is blocked as a result of careful yet vigorous anti-spam and abuse countermeasures. We would like to rectify your mail delivery issue as soon as possible with your help. By emailing this address you have already taken the first step in resolving this issue.
When the AT&T Postmaster staff receives a request with the needed information requests are evaluated. If granted, the block will be removed within 24 to 48 hours. There are situations when mail interruptions or blocks are in place outside the AT&T domain. In these cases, we will attempt to make contact with the party initiating the block and seek a resolution. If there is no change after 48 hours please include the current and complete error message that you are receiving in your follow up email to abuse_rbl@abuse-att.net.
For more information about email best practices and mail delivery issues visit:
https://www.att.com/esupport/postmaster/
We reserve the right to deny or turn down a request if our research shows the requested IP(s) being a violator of SPAM or abuse policies currently, or in the past.
We at AT&T thank you for your assistance in reporting this matter and appreciate your patience while we investigate this issue.
AT&T Postmaster Staff
As of 03:30 PST this morning the block had not been removed.
On 3/13/21 11:00 AM, Mark Sapiro wrote:
As of 03:30 PST this morning the block had not been removed.
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
There is definitely an increase in AT&T blocking mail servers recently. I had about 5 out of the blue get blocked. Too date, AT&T has never presented any evidence for their decision to block one our IP addresses. I do know they block new server IPs automatically. The real problem here is how long they are taking to respond to block removal requests. Out of the 5 I had to deal with recently, one of them took 10 DAYS for them to remove the block. I am assuming the reason behind this lengthy delay is a deluge of block removal requests that they are having to deal with.
On 3/13/21 10:33 AM, Brian Carpenter wrote:
Too date, AT&T has never presented any evidence for their decision to block one our IP addresses.
My experience in dealing with blocks by ATT, Microsoft and other ISPs is that they (eventually) remove the blocks, but never once have they provided me with any evidence of the alleged problem email.
On 3/13/21 11:51 AM, Mark Sapiro wrote:
On 3/13/21 10:33 AM, Brian Carpenter wrote:
Too date, AT&T has never presented any evidence for their decision to block one our IP addresses.
My experience in dealing with blocks by ATT, Microsoft and other ISPs is that they (eventually) remove the blocks, but never once have they provided me with any evidence of the alleged problem email.
I have seen that as well, both with mailing lists and other emails. The best I can get from anyone there is, "we wouldn't have blocked it if there weren't an issue," but that doesn't tell me what the issue was (or is) so I can address the issue (assuming there actually was one). And even with my IP addresses set up in their tracking and reporting systems and affiliated with an administrative email address, I have never received any reports or warnings that something was about to happen. Instead I get complaints about bounces or non-delivery from my clients...
On 3/13/21 12:17 PM, Keith Seyffarth wrote:
On 3/13/21 11:51 AM, Mark Sapiro wrote:
My experience in dealing with blocks by ATT, Microsoft and other ISPs is that they (eventually) remove the blocks, but never once have they provided me with any evidence of the alleged problem email.
I have seen that as well, both with mailing lists and other emails. The best I can get from anyone there is, "we wouldn't have blocked it if there weren't an issue," but that doesn't tell me what the issue was (or is) so I can address the issue (assuming there actually was one). And even with my IP addresses set up in their tracking and reporting systems and affiliated with an administrative email address, I have never received any reports or warnings that something was about to happen. Instead I get complaints about bounces or non-delivery from my clients...
That too is completely consistent with my experience.
Mark,
Thanks for your response. So ATT is apparently blocking the email server of our website host.I have notified our web host so hopefully something good will happen eventually.
BTW, so what is this "Registering" an email server with an ISP domain? I assume that it is basically telling them that it is a legitimate email server. Is it worthwhile trying to get our web host to do this or a waste of time? I guess has anyone seen positive results from doing so?
Thanks, Steve
On Sat, Mar 13, 2021 at 11:00 AM Mark Sapiro mark@msapiro.net wrote:
On 3/12/21 1:39 PM, steve lund wrote:
Hello,
It appears to be starting again for our list. Fatal bounces but ONLY on ATT.net. Here is what Google says:
...
...@att.net: host ff-ip4-mx-vip1.prodigy.net[144.160.159.21] said: 553 5.3.0 flpd599 DNSBL:RBL 521< 45.33.97.191 >_is_blocked.For assistance forward this error to abuse_rbl@abuse-att.net (in reply to MAIL FROM command)
It may be a coincidence, but I started seeing the same bounces on one of my servers (thankfully not mail.python.org or lists.mailman3.org) about two days ago.
ATT is blocking your IP.
In my case, I sent this to abuse_rbl@abuse-att.net.
You are blocking all mail from IP 138.68.52.125 per this log message.
Mar 12 09:59:32 grizz postfix/smtp[10965]: D0CAF1F8123: to=<...>, relay=ff-ip4-mx-vip2.prodigy.net[144.160.159.22]:25, delay=0.38, delays=0.1/0/0.27/0.01, dsn=5.3.0, status=bounced (host ff-ip4-mx-vip2.prodigy.net[144.160.159.22] said: 553 5.3.0 flph832 DNSBL:RBL 521< 138.68.52.125 >_is_blocked.For assistance forward this error to abuse_rbl@abuse-att.net (in reply to MAIL FROM command))
This mail is from an opt-in email discussion list or other business related mail from a bicycle club. We do not send spam or unsolicited commercial email. Please remove this block.
I received this reply.
Thank you for contacting the AT&T Postmaster Staff.
We investigate every block report and removal request we receive and take the appropriate action, of which you will be notified. It is never the intention of the AT&T Postmaster staff to block legitimate mail. It is a rare but unfortunate occurrence that legitimate correspondence is blocked as a result of careful yet vigorous anti-spam and abuse countermeasures. We would like to rectify your mail delivery issue as soon as possible with your help. By emailing this address you have already taken the first step in resolving this issue.
When the AT&T Postmaster staff receives a request with the needed information requests are evaluated. If granted, the block will be removed within 24 to 48 hours. There are situations when mail interruptions or blocks are in place outside the AT&T domain. In these cases, we will attempt to make contact with the party initiating the block and seek a resolution. If there is no change after 48 hours please include the current and complete error message that you are receiving in your follow up email to abuse_rbl@abuse-att.net.
For more information about email best practices and mail delivery issues visit:
https://www.att.com/esupport/postmaster/
We reserve the right to deny or turn down a request if our research shows the requested IP(s) being a violator of SPAM or abuse policies currently, or in the past.
We at AT&T thank you for your assistance in reporting this matter and appreciate your patience while we investigate this issue.
AT&T Postmaster Staff
As of 03:30 PST this morning the block had not been removed.
-- Mark Sapiro mark@msapiro.net The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-leave@python.org https://mail.python.org/mailman3/lists/mailman-users.python.org/ Mailman FAQ: http://wiki.list.org/x/AgA3 Security Policy: http://wiki.list.org/x/QIA9 Searchable Archives: https://www.mail-archive.com/mailman-users@python.org/ https://mail.python.org/archives/list/mailman-users@python.org/
On 3/13/21 7:15 PM, steve lund wrote:
Thanks for your response. So ATT is apparently blocking the email server of our website host.I have notified our web host so hopefully something good will happen eventually.
BTW, so what is this "Registering" an email server with an ISP domain? I assume that it is basically telling them that it is a legitimate email server. Is it worthwhile trying to get our web host to do this or a waste of time? I guess has anyone seen positive results from doing so?
AT&T doesn't allow such a process. Microsoft has a great program called SNDS that I recommend having your web host look into, especially if they are hosting mailing lists.
steve lund writes:
BTW, so what is this "Registering" an email server with an ISP domain?
What it says. Other than putting your domain and IP on a list, I know of no policy that's common to most such programs. :-(
Is it worthwhile trying to get our web host to do this
In general, yes. Some ISPs have provided services such as reports on issues related to your domain or IP as a sender, and while history suggests that they think that their users get a lot madder about one spam message than they do about one undelivered mail, users do care about lost mail. I'm sure they genuinely intend these programs to help your mail get through to subscribers at their services. (I don't know if any currently offer such services to registered domains.)
The ones that are reasonably good at this are providers like Gmail, Yahoo!, and O365, whose business model (at least at one time) involved provision of excellent email hosting.
There is some administrative effort required, so you could check what domains your subscribers are using and see if they have registration programs, what information they want, and what benefits they offer when you approach your host. This is the kind of thing that experienced mail hosting services do for you; you may find that they already do this "in general", and haven't registered with ATT only because ATT doesn't have a program. :-(
Steve
Steve,
Thanks for the info. I'll check with out web host / mail provider.
Thanks, Steve
On Sun, Mar 14, 2021 at 10:46 AM Stephen J. Turnbull < turnbull.stephen.fw@u.tsukuba.ac.jp> wrote:
steve lund writes:
BTW, so what is this "Registering" an email server with an ISP domain?
What it says. Other than putting your domain and IP on a list, I know of no policy that's common to most such programs. :-(
Is it worthwhile trying to get our web host to do this
In general, yes. Some ISPs have provided services such as reports on issues related to your domain or IP as a sender, and while history suggests that they think that their users get a lot madder about one spam message than they do about one undelivered mail, users do care about lost mail. I'm sure they genuinely intend these programs to help your mail get through to subscribers at their services. (I don't know if any currently offer such services to registered domains.)
The ones that are reasonably good at this are providers like Gmail, Yahoo!, and O365, whose business model (at least at one time) involved provision of excellent email hosting.
There is some administrative effort required, so you could check what domains your subscribers are using and see if they have registration programs, what information they want, and what benefits they offer when you approach your host. This is the kind of thing that experienced mail hosting services do for you; you may find that they already do this "in general", and haven't registered with ATT only because ATT doesn't have a program. :-(
Steve
participants (6)
-
Bader, Robert (Bob) -
Brian Carpenter -
Keith Seyffarth -
Mark Sapiro -
Stephen J. Turnbull -
steve lund