1 Topic by dittman

  • dittman
  • Member
  • Offline
  • Registered: 2015-08-15
  • Posts: 55

Topic: Spamcop filtering

==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
- iRedMail version (check /etc/iredmail-release): 0.9.5-1
- Deployed with iRedMail Easy or the downloadable installer? No
- Linux/BSD distribution name and version: CentOS 7.2.1511 (Core)
- Store mail accounts in which backend (LDAP/MySQL/PGSQL):  MySQL
- Web server (Apache or Nginx): Apache
- Manage mail accounts with iRedAdmin-Pro? No
- [IMPORTANT] Related original log or error message is required if you're experiencing an issue.
====

After having all my email rejected for a time yesterday due to the spamcop.net domain expiration I started investigating how to prevent this in the future.  The recommendation was to verify the IP returned from bl.spamcop.net was 127.0.0.2 and not just any valid IP.

How would I best implement this?

----

Spider Email Archiver: On-Premises, lightweight email archiving software developed by iRedMail team. Supports Amazon S3 compatible storage and custom branding.

2 Reply by dittman

  • dittman
  • Member
  • Offline
  • Registered: 2015-08-15
  • Posts: 55

Re: Spamcop filtering

This didn't turn up when I searched but did when I just browsed the documents:

https://docs.iredmail.org/enable.dnsbl.html

adding =127.0.0.2 to bl.spamcop.net works.