> The problem is that 1) headers are supposed to provide a "chain of > custody" per the RFC's and 2) RFC 821/2821 para 3.6 requires the > domain name given with the helo/ehlo must be the primary host name > (or a domain literal only if the host has no name) and assp fulfills > neither critera as shown below.
Would an "X-ASSP-Received-From:" header carrying the original IP and HELO solve such an issue ? In such a case, ASSP may just present itself using its own name instead of the sending host HELO so you'll have your "chain"... although, I don't see such a thing as a really big issue, a minor annoyance maybe, but not an issue at all, and btw, if such a change would require overhead to ASSP, then my opinion would be to leave things as they are :) at least until someone won't demonstrate that the current behaviour is causing some nasty problem or letting spam through ------------------------------------------------------------------------------ Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are powering Web 2.0 with engaging, cross-platform capabilities. Quickly and easily build your RIAs with Flex Builder, the Eclipse(TM)based development software that enables intelligent coding and step-through debugging. Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com _______________________________________________ Assp-test mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-test
