Hi all,

in my mail queue I sometimes find a series of DMARC reports which cannot be
delivered to the spammer who caused them:

 

43EC952E6A     2035 Fri Oct  2 00:37:58  postmas...@mydomain.de

               (connect to ecijoven.com[31.220.44.130]:25: Connection
refused)

                                         ad...@ecijoven.com

 

47A1947827     2017 Fri Oct  2 04:04:28  postmas...@mydomain.de

               (connect to ppobbris.com[31.220.44.130]:25: Connection
refused)

                                         ad...@ppobbris.com

 

1D8F1468DB     2041 Fri Oct  2 03:04:02  postmas...@mydomain.de

              (connect to iberagree.com[31.220.44.130]:25: Connection
refused)

                                         ad...@iberagree.com

 

2CCDE46166     2045 Fri Oct  2 02:18:49  postmas...@mydomain.de

              (connect to shchinoff.com[31.220.44.130]:25: Connection
refused)

                                         ad...@shchinoff.com

 

3F7DC454B1     2007 Fri Oct  2 01:53:39  postmas...@mydomain.de

              (connect to ecomtyoon.com[31.220.44.130]:25: Connection
refused)

                                         ad...@ecomtyoon.com

 

3DCFE52E87     2013 Fri Oct  2 13:34:57  postmas...@mydomain.de

               (connect to iphstore.com[31.220.44.130]:25: Connection
refused)

                                         ad...@iphstore.com
<mailto:ad...@iphstore.com> 

 

I realize, that while the domain names are random, the destination IP for
these is the same for each message. 

That brings me to the question: would something like "noDMARCReportIP" be
useful, so that the list for noDMARCReportDomain does not grow too long?

(I admit in my case that list has less than 100 entries.)

 

 

Best regards & thank you for your good work

 

Dirk

 

 

 

_______________________________________________
Assp-test mailing list
Assp-test@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/assp-test

Reply via email to