Daryl C. W. O'Shea wrote:
SA knows *nothing* about the connection that isn't in the headers. In your example in this thread you had two headers, one that was added after SA saw it, and one that came in as DATA.
You believe the headers entirely? Okay, so auto detection is even more broken than I thought.
As stated in the documentation, SA *requires* you to at least forge a received header for the local relay before passing the mail to SA. This is the only way that SA can gather data about the connection, the envelope, etc.
Really? Show me the docs. I may have overlooked them.
If you were to be doing what is *required*, SA would see this forged received header, assume that it is the local trusted server (like the docs says it will do). It'll then compare the IP addr info from the first forged received header to the one supplied by the remote host and see that it is not trusted and won't trust it -- just like you're bitching that it's not doing because you're not providing the correct input to SA.
SA should do the intelligent thing, and determine the local network from system calls. It's not like it's written in C -- perl deals with the inconsistencies of system implementations for you.
Without checking the local interface, how do you know what the network is? Are you assuming that my 64.x address is a class-A network? Seriously, auto detection can't possibly work if you're not checking the local interface addresses.
-- Jo Rhett Network/Software Engineer Net Consonance
