Jump to content

failing defaulted postmaster contact for garrisonnetwork.com


Recommended Posts

Reporting spam from 104.192.100.140 got the usual statisical tracking address due to bounces at the calculated address. Refresh/Show for the the message source tracking got:

Removing old cache entries.

Tracking details

Display data:
"whois 104.192.100.140[at]whois.arin.net" (Getting contact from whois.arin.net )
checking NET-104-192-100-0-2
Display data:
"whois NET-104-192-100-0-2[at]whois.arin.net" (Getting contact from whois.arin.net )
Found AbuseEmail in whois noc[at]garrisonnetwork.com
104.192.100.0 - 104.192.101.255:noc[at]garrisonnetwork.com
checking NET-104-192-100-0-1
Display data:
"whois NET-104-192-100-0-1[at]whois.arin.net" (Getting contact from whois.arin.net )
Found AbuseEmail in whois abuse[at]garrisonnetwork.com
104.192.100.0 - 104.192.103.255:abuse[at]garrisonnetwork.com
Routing details for 104.192.100.140
Using abuse net on noc[at]garrisonnetwork.com
No abuse net record for garrisonnetwork.com
Using default postmaster contacts postmaster[at]garrisonnetwork.com
postmaster[at]garrisonnetwork.com bounces (10 sent : 6 bounces)


Using postmaster#garrisonnetwork.com[at]devnull.spamcop.net for statistical tracking.
The explicit abuse address found for NET-104-192-100-0-1 looks like a better place to try.
Link to comment
Share on other sites

I have mitigated this problem by adding an appropriate record for garrisonnetwork.com at abuse.net. Ignoring an obvious abuse address and unnecessarily relying on abuse.net's incomplete database is still far from a good algorithm.

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...