[Mailman-Users] Fatal Bounces ONLY on ATT (Bellsouth).NET
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: slund...@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-boun...@lists.deltaforce.net designates 45.33.97.191 as permitted sender) smtp.mailfrom=mailman-boun...@lists.deltaforce.net; dmarc=pass (p=REJECT sp=REJECT dis=NONE) header.from=lists.msinglinks.org Return-Path: 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 ; Fri, 12 Mar 2021 08:50:47 -0800 (PST) Received-SPF: pass (google.com: domain of mailman-boun...@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-boun...@lists.deltaforce.net designates 45.33.97.191 as permitted sender) smtp.mailfrom=mailman-boun...@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 ; 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-ow...@lists.msinglinks.org Delivered-To: msing-ride-ow...@duke.deltaforce.net Received: from duke.deltaforce.net (localhost [IPv6:::1]) by duke.deltaforce.net (Postfix) with ESMTP id 90BDF20082 for ; 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: mail...@lists.msinglinks.org To: msing-ride-ow...@lists.msinglinks.org MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===0332406003479489569==" Message-ID: Date: Fri, 12 Mar 2021 11:50:06 -0500 Precedence: list X-Bee
[Mailman-Users] Re: Fatal Bounces ONLY on ATT (Bellsouth).NET
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_...@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_...@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_...@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 > . > > 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 The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-le...@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/
[Mailman-Users] Re: Fatal Bounces ONLY on ATT (Bellsouth).NET
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 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. -- Brian Carpenter Harmonylists.com Emwd.com -- Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-le...@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/
[Mailman-Users] Re: Fatal Bounces ONLY on ATT (Bellsouth).NET
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. -- Mark Sapiro The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-le...@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/
[Mailman-Users] Re: Fatal Bounces ONLY on ATT (Bellsouth).NET
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... -- Keith Seyffarth mailto:w...@weif.net https://www.weif.net/ - Home of the First Tank Guide! https://www.rpgcalendar.net/ - the Montana Role-Playing Calendar http://www.miscon.org/ - Montana's Longest Running Science Fiction Convention -- Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-le...@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/
[Mailman-Users] Re: Fatal Bounces ONLY on ATT (Bellsouth).NET
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 Sapiro The highway is for gamblers, San Francisco Bay Area, Californiabetter use your sense - B. Dylan -- Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-le...@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/
[Mailman-Users] Re: Fatal Bounces ONLY on ATT (Bellsouth).NET
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 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_...@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_...@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_...@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 > > . > > > > 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 The highway is for gamblers, > San Francisco Bay Area, Californiabetter use your sense - B. Dylan > -- > Mailman-Users mailing list -- mailman-users@python.org > To unsubscribe send an email to mailman-users-le...@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/ > -- Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-le...@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/
[Mailman-Users] Re: Fatal Bounces ONLY on ATT (Bellsouth).NET
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. -- Brian Carpenter Harmonylists.com Emwd.com -- Mailman-Users mailing list -- mailman-users@python.org To unsubscribe send an email to mailman-users-le...@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/
