Re: [mailop] AT&T Blocklist

2024-06-18 Thread Jeff Peng via mailop
On 2024-06-19 10:11, Scott Mutter via mailop wrote: On Tue, Jun 18, 2024 at 8:31 PM Jeff Peng via mailop wrote: Mike is right. mx1.amscomputer.com has an A RR 107.181.229.51 which points back its PTR to zephyr.wznoc.com. the two domains are not matched, hence messages sent from this serve

Re: [mailop] AT&T Blocklist

2024-06-18 Thread Scott Mutter via mailop
On Tue, Jun 18, 2024 at 8:31 PM Jeff Peng via mailop wrote: > Mike is right. > > mx1.amscomputer.com has an A RR 107.181.229.51 which points back its > PTR to zephyr.wznoc.com. > > the two domains are not matched, hence messages sent from this server > will be rejected by postfix's such configu

Re: [mailop] AT&T Blocklist

2024-06-18 Thread Jeff Peng via mailop
On 2024-06-19 07:18, Michael Peddemors via mailop wrote: https://wznoc.com/ With a obscure page like that, you are asking for trouble.. Just like the pages many of the bullet proof hosters throw up.. Why not use amscomputer.com in the PTR records, if these are your servers? https://www.amsco

Re: [mailop] AT&T Blocklist

2024-06-18 Thread Scott Mutter via mailop
On Tue, Jun 18, 2024 at 6:18 PM Michael Peddemors via mailop < mailop@mailop.org> wrote: > https://wznoc.com/ > > With a obscure page like that, you are asking for trouble.. > Just like the pages many of the bullet proof hosters throw up.. > > Why not use amscomputer.com in the PTR records, if the

Re: [mailop] AT&T Blocklist

2024-06-18 Thread Michael Peddemors via mailop
https://wznoc.com/ With a obscure page like that, you are asking for trouble.. Just like the pages many of the bullet proof hosters throw up.. Why not use amscomputer.com in the PTR records, if these are your servers? https://www.amscomputer.com/ Inquiring minds would like to know. CIDR:

Re: [mailop] [E] Re: AT&T Blocklist

2024-06-18 Thread Lili Crowley via mailop
Yep thanks! *Lili Crowley* she/her Postmaster On Tue, Jun 18, 2024 at 5:25 PM Faisal Misle via mailop wrote: > In the past few weeks Lili has replied to *various* threads about ATT > blockings. Have you tried reaching out off list to her? > On 6/18/24 9:25 PM, S

Re: [mailop] AT&T Blocklist

2024-06-18 Thread Faisal Misle via mailop
In the past few weeks Lili has replied to *various* threads about ATT blockings. Have you tried reaching out off list to her? On 6/18/24 9:25 PM, Scott Mutter via mailop wrote: What's going on with AT&T? They're blocking our mail servers left and right (IPs aren't on any other blacklist mind

[mailop] AT&T Blocklist

2024-06-18 Thread Scott Mutter via mailop
What's going on with AT&T? They're blocking our mail servers left and right (IPs aren't on any other blacklist mind you) and not hearing a peep from abuse_...@abuse-att.net. What's the point of having your blocked message state to send an email to abuse_...@abuse-att.net if nobody is going to mon

Re: [mailop] t-online.de spam

2024-06-18 Thread Michael Rathbun via mailop
On Tue, 18 Jun 2024 11:33:48 -0700, Michael Peddemors via mailop wrote: >Just an FYI, the list admin's prefer NOT to have the list used for >reporting spam.. It's okay to report generic trends, or >misconfigurations, or visibility into something new.. (And of course, >you are welcome to provid

Re: [mailop] t-online.de spam

2024-06-18 Thread Michael Peddemors via mailop
Hey Benny, Just an FYI, the list admin's prefer NOT to have the list used for reporting spam.. It's okay to report generic trends, or misconfigurations, or visibility into something new.. (And of course, you are welcome to provide evidence of that.. ) but the list can quickly get consumed if

[mailop] t-online.de spam

2024-06-18 Thread Benny Pedersen via mailop
Received: from mailout11.t-online.de (mailout11.t-online.de [194.25.134.85]) by mx.junc.eu (Postfix) with ESMTPS id 22CFA83FCF for ; Tue, 18 Jun 2024 00:45:39 +0200 (CEST) Received: from fwd80.aul.t-online.de (fwd80.aul.t-online.de [10.223.144.106]) by mailout11.t-online

Re: [mailop] Another 'Verified Email' service on AWS EC2

2024-06-18 Thread L. Mark Stone via mailop
FWIW, we use Fail2Ban to block all AWS EC2 IPs that have an "ec2-xxx.compute...amazonaws.com" PTR record, and another Fail2Ban rule to block hosts that HELO with "127.0.0.1". We ourselves host on AWS successfully (for more than six years now) and have filed a number of complaints with their sec

[mailop] Another 'Verified Email' service on AWS EC2

2024-06-18 Thread Michael Peddemors via mailop
Jun 18 09:58:03 be msd[1959712]: CONN: 34.229.185.73 -> 25 GeoIP = [US] PTR = ec2-34-229-185-73.compute-1.amazonaws.com OS = Linux 2.2.x-3.x Jun 18 09:58:04 be msd[1959712]: HELO command received, args: [127.0.0.1] Jun 18 09:58:04 be msd[1959712]: RSET command received, args: Jun 18 09:58:04 be m

Re: [mailop] salesforce phishing emails

2024-06-18 Thread Jarland Donnell via mailop
My experience is similar. My observation has been that Salesforce does not care about abuse, that almost all of the mail coming from their platform is unsolicited marketing email, and that they're a trash spam company worth blocking. On 2024-06-13 12:09, Michael Peddemors via mailop wrote: On

Re: [mailop] Microsoft SNDS website not working

2024-06-18 Thread Bjoern Franke via mailop
Hi, Keep hitting refresh, it will eventually load (at least it does for me).  But I believe this is indicative of some problems on the backend of this website and maybe of the entire Microsoft postmaster/SNDS/JMRPP system.  It's been quite literally months since I've received anything from