On 8/28/07, JT Moree <[EMAIL PROTECTED]> wrote: > James W. Abendschan wrote: > > The check_earlytalker plugin ensures at least a one > > second pause in every SMTP session, so time() + peer IP > > + peer port will be far more unique than a random number :-) > > This has been suggested a few times but I'd rather not have to have ids > for the system depend on using a plugin. I'm pushing for adding this id > to core qpsmtpd. > > > This combo would be unique among all hosts attached to the same > > routable networks -- two hosts on two different, unconnected > > networks could possibly get a connection from the same > > private IP + local port at the same time, but this "should > > be impossible" if the networks are connected. > > As in two clients behind a NAT sending to our server at the exact same > time? Might be possible from server farms or distributed mailing list > systems? > > What do you guys think?
that wont be an issue. the nat box will rewrite the outgoing packets to say they are coming from a unique port on it's external interface, and that is all you can see on your end. remoteIP + remotePort + fineGrainedTime is what we use in-house for some high-speed http logging that needs a unique handle. it works just fine with a fair number of concurrent clients behind a nat or proxy. but, my installation is not massive :) allan -- "The truth is an offense, but not a sin"
