-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Sam,
What I would love to see is a filter interface running at the DATA stage, rather than a specific implementation of greylisting. At this point, we have the information that is required for conventional greylisting: to, from, remote address. Other folks have stated they'd like to have the MD5 of the message body, but they can do that with the existing courierfilter interface. - From earlier postings in this thread, the method that I would choose is different from the method others would choose. In the mean time, I am patching courier to do it via an exec() call. Exit code maps to smtp response code. I'd obviously rather see an official method to achieve this goal so as not to maintain my own patch set. Josh Sam Varshavchik wrote: > Sander Holthaus writes: > >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> Sam Varshavchik wrote: >>> Alexander Lazic writes: >>> >>>> How about to add -greylist to couriertcpd such as -block. >>>> >>>> My opinion is that this is the right point, isn't it? >>> >>> No. couriertcpd's job is to only accept network connections. >>> couriertcpd is protocol-independent, and has no idea if the >>> connection will be an SMTP, IMAP, or a POP3 connection. >>> >> Sam, >> >> what is your opinion on greylisting? Any specific reason why it is not >> included in Courier? > > Because I have a job, and not enough free time to do it right. Busy > mail servers may receive hundreds of connection attempts per second. > Assuming a baseline of 100 connections a second, and a greylisting > expiration interval of two hours -- you can't really have an effective > greylisting system with a shorter expiration, because it's quite > reasonable for legitimate senders to wait at least an hour to try again > -- simple math will show you that your greylisting database is going to > grow to the 700,000 record range. > > Before I could even think of writing a single line of code, I have to > figure out how to scale to a database that may potentially hold several > million records, and do it in a way that allows for parallel queries -- > and updates -- with negligible overhead. > > And that's just for starters. Then, you need to figure out how you're > going to hold whitelisted addresses. > > Greylisting sounds wonderful, but only if you're a small fish that > occasionally gets any mail, at all. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEa0Lplrx3tV7BDaERAsP6AJ4z00Yy+zH7aPMou+y8B/73T2q9YwCgi2AV WmmQaxOIicOefgmIhRjzk24= =waqT -----END PGP SIGNATURE----- ------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
