Jump to content
Sign in to follow this  
mMerlin

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.

Share this post


Link to post
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.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×