[Mailman-Users] Re: AT&T Blocking (was AOL list member not receiving list traffic)

2022-09-05 Thread Michael Reeder -- Hygeia MS
AT&T has now started blocking the IP address of the multiple 
auto-forwarding email addresses I set up to get around them blocking the 
IP address of my GNU Mailman list.  So even that labor-intensive 
strategy won't work.  You'd have to be sending from multiple different 
IP addresses.


Dream Host to their credit jumped right on this and also tried to 
resolve the problem with AT&T.  No responses from AT&T. This includes 
sbcglobal.net, att.net, flash.net, bellsouth.net, optonline.net, 
worldnet.att, and ameritech.net .


37 list members at risk unless they change their email addresses. We 
started 20+ years ago with a different list program and hosting 
provider, so we have lots of legacy members suddenly getting cut off.


*Michael Reeder, LCPC
*
*Hygeia Counseling Services : Baltimore / Mt. Washington Village location*
*410-871-TALK / michael(at)hygeiacounseling.com*


On 8/28/2022 4:17 PM, Michael Reeder -- Hygeia MS wrote:
I should mention that for the free att.net account I set up (managed 
by Yahoo) that as the end user I received *NO* notifications of any 
sort.  List emails were not even sent to a Spam folder!


*Michael Reeder, LCPC
*
*Hygeia Counseling Services : Baltimore / Mt. Washington Village 
location*

*410-871-TALK / michael(at)hygeiacounseling.com*

On 8/28/2022 4:08 PM, Michael Reeder -- Hygeia MS wrote:
Dave Nathanson wrote: /"I'm having a similar struggle with 
sbcglobal.net & ATT.net addresses - They are rejecting our list mail 
with a reject notice"/


I can second this.  I believe AT&T has been blocking for months or 
years, but with Dream Host rebuilding their discussion list servers 
in July, it gave AT&T a new opportunity to reblock us anew and a new 
opportunity for list administrators of GNU Mailman lists hosted at 
Dream Host to notice.


I have 36 list users all blocked from AT&T managed accounts at the 
following domains: sbcglobal.net, att.net, flash.net, bellsouth.net, 
optonline.net, worldnet.att, and ameritech.net


Almost all of these flow through email servers at the prodigy.net 
domain, but please notice that this also includes att.net domains 
managed for AT&T by Yahoo (no Prodigy servers involved).


AT&T has ignored my (very polite) screams for months, and this week 
Dream Host support reported back that AT&T is no longer answering 
their inquiries.  According to Dream Host, AT&T recently blocked 8 
additional IP blocks (or just IP addresses?). For one of them, AT&T 
responded saying it was in error (and unblocking it) and saying 
something to the effect that they block any IP block sending too many 
email.  For the other 7, crickets.


I do observe that my IP block is on the UCEPROTECTL3 blacklist, 
although I don't know that AT&T is using it.  UCEPROTECTL3 would, 
however, be happy to "express delist" my particular IP address as its 
doing nothing wrong for the low, low price of only $25 per month.  
Jerks!


I have (temporarily?) fixed this by creating nine or so auto-forward 
email addresses that auto-forward to 5 AT&T accounts each. (Dream 
Host users: you can't just create one auto-forward address to send to 
everyone because Dream Host themselves limit email addresses to about 
30 emails sent per hour.  Also -- with Dream Host auto-forward only 
email addresses you won't see bounce traffic when AT&T starts 
blocking again.)


What a mess.

-- Michael

*Michael Reeder, LCPC
*
*Hygeia Counseling Services : Baltimore / Mt. Washington Village 
location*

*410-871-TALK / michael(at)hygeiacounseling.com*


On 8/27/2022 4:09 PM, Dave Nathanson wrote:
I'm having a similar struggle with sbcglobal.net & ATT.net addresses 
- They are rejecting our list mail with a reject notice, but let 
individual messages through. I have different outgoing server  for 
mailman. My servers are hosted at Dreamhost, who generally has very 
helpful support, but in the past 3 weeks they are not able to 
convince sbcglobal & att to let our mail through because they banned 
our IP block.


I did set Mailman to give me notice for each bounce notification so 
I could see what was going on, and when the bounce counters were 
incremented. That helped me be more aware.


Immensely frustrating, as almost half of our list members have 
sbcglobal or ATT & are losing contact with our group.


  Best,
  Dave Nathanson
  Mac Medix

On Aug 26, 2022, at 10:36 PM, Jayson 
Smith  wrote:


Hi,

Yesterday I received a report from an AOL user that she's not 
receiving traffic from one of my lists. The problem here is that my 
server logs show outgoing mail being accepted by AOL's incoming 
mail servers, and of course after that it's anyone's guess what 
happens to them. She says she's checked her junkmail folder and the 
messages aren't there. Does anyone have any thoughts on this? Is 
AOL known to silently discard mail they think is spam for some 
reason? I replied to her message from the same server and she did 
receive that reply, so they haven't outright blocked my IP or 
something. Even if I could c

[Mailman-Users] Re: AT&T Blocking (was AOL list member not receiving list traffic)

2022-09-05 Thread Stephen J. Turnbull
Michael Reeder -- Hygeia MS writes:

 > AT&T has now started blocking the IP address of the multiple 
 > auto-forwarding email addresses I set up to get around them blocking the 
 > IP address of my GNU Mailman list.

I have to conclude AT&T wants to get rid of their email provision
activity.

Is there possibly something somebody could consider spammy in your
content, such as frequent or repeated announcements of new services or
invitations to events?  Do members ever report the list traffic being
marked as (potential) spam?  Are these discussion lists among the
members, or is it all announcements from your side?

 > 37 list members at risk unless they change their email addresses.

AT&T hates them, so I recommend they get an alternative address for
list mail and eventually get off AT&T altogether.  It's not going to
get better, I imagine.  But most likely they won't change until they
get sued for nonpayment of bills invoiced to their AT&T address. :-/

 > We started 20+ years ago with a different list program and hosting 
 > provider, so we have lots of legacy members suddenly getting cut off.

Do you keep archives?  If so, an RSS feed might be the way to
communicate to them in somewhat less than real time.  Similarly,
moving to Mailman 3 + HyperKitty allows use of the archives in a way
quite similar to dedicated web forum software like Discourse.
Finally (though I hate to recommend it) you could move to forum
software or Google Groups.

I'm sorry to be putting all the work on you, but I don't think there's
anything Mailman can do.  It seems AT&T just doesn't want your list
traffic.

Steve

--
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/