Right now the test plugin I've built makes a single HTTP request for each email while I evaluate this but I'll be building a DNS query endpoint or a local domain cache to make it more efficient before putting it into production.
Just one more note - I've excluded .email domains from the check as I've
noticed several organizations using that as email only domains.
- Re: Spam rule for HTTP/HTTPS re... Grant Taylor
- Re: Spam rule for HTTP/HTTPS re... Mike Marynowski
- Re: Spam rule for HTTP/HTTPS re... Rupert Gallagher
- Re: Spam rule for HTTP/HTTPS re... Mike Marynowski
- Re: Spam rule for HTTP/HTTPS re... Rupert Gallagher
- Re: Spam rule for HTTP/HTTPS re... RW
- Re: Spam rule for HTTP/HTTPS request to ... Ralph Seichter
- Re: Spam rule for HTTP/HTTPS request to ... Grant Taylor
- Re: Spam rule for HTTP/HTTPS reques... Mike Marynowski
- Re: Spam rule for HTTP/HTTPS request to send... Mike Marynowski
- Re: Spam rule for HTTP/HTTPS request to sender's roo... Mike Marynowski
- Re: Spam rule for HTTP/HTTPS request to sender's... Andrea Venturoli
- Re: Spam rule for HTTP/HTTPS request to sender's root dom... Mike Marynowski
- Re: Spam rule for HTTP/HTTPS request to sender's roo... RW
- Re: Spam rule for HTTP/HTTPS request to sender's... Mike Marynowski
- Re: Spam rule for HTTP/HTTPS request to send... Dominic Raferd
- Re: Spam rule for HTTP/HTTPS request to ... RW
- Re: Spam rule for HTTP/HTTPS reques... Dominic Raferd
- Re: Spam rule for HTTP/HTTPS re... Jari Fredriksson
- Re: Spam rule for HTTP/HTTPS re... Antony Stone
- Re: Spam rule for HTTP/HTTPS re... Jari Fredriksson