Why doesn spamdykes graylist filter use the IP address of the remote server?
At first glance, it seems more effective to use three criteria for graylisting: the sender’s email address, the recipient’s email address and the remote server’s IP address. Many graylist filters do this. Whether it actually stops more spam is questionable. However, using the remote server’s IP address often causes more problems than it solves. To understand why, consider a large mail service like GMail, Yahoo! or AOL. Such providers handle so many messages that they must use dozens of outbound servers to keep up with the load. Imagine this scenario: • A user on a large provider sends a message. • Server 1 attempts to deliver it. The graylist filter creates a graylist entry and rejects the connection. • Server 1 puts the message back in the queue to retry later. • Some time later, server 2 grabs the message and attempts to deliver it. Server 2’s IP address is different from server 1’s, so the graylist filter creates a new entry and rejects the connection. • Server 2 puts the message ba
Related Questions
- Why doesn spamdyke filter using Sender Policy Framework (SPF), Sender ID, Certified Server Validation (CSV), DomainKeys or DomainKeys Identified Mail (DKIM)?
- Do I need a static IP address from my Internet provider to use the Proliphix Remote Server?
- Does the remote server address need to be an IP address?
