No what you are missing is that a gateway and a proxy are separate things that people are interchanging **wrongly** then talking. Using your own defensive "wikipedia".
What a Gateway is: http://en.wikipedia.org/wiki/Gateway_(telecommunications) Now reread what a proxy is: http://en.wikipedia.org/wiki/Proxy_server There is a every clear and decisive difference there. And again while both are generally found on the same hardware and box all the time any more. They are 2 different things. Now for Relay VS Proxy. Shortest answer : Relay blindly transmits data between to or more "thing" , Proxies can "Translate, Interpret, and change (filter)" -- Chris L. Franklin -- Fun with perl : perl -e 'print pack(nnnnnnnnnnnn, 19061,29556,8289,28271,29800,25970,8304,25970,27680,26721,25451,25970), ".\n" ' On Sun, March 15, 2009 12:14 pm, Tom Shaw wrote: > At 11:09 AM -0400 3/15/09, Chris Franklin wrote: >>The rfcs do not talk about proxies, only gateways. And they are too >>different things. That can and usually do coexist with in the same >>box/hardware. > > I think you are missing what a proxy is. A gateway is a proxy; a > relay is a proxy; a proxy server sits between a client application, > and a real server. A proxy intercepts all requests to the real server > to see if it can fulfill or filter the requests itself. If not, it > forwards the request to the real server. > > The definition which I like because it is most clear is, "In computer > networks, a proxy server is a server (a computer system or an > application program) that acts as a go-between for requests from > clients seeking resources from other servers" > > See http://en.wikipedia.org/wiki/Proxy_server , > http://www.answers.com/topic/proxy-server and > http://whatis.techtarget.com/definition/0,,sid9_gci212840,00.html > > Clearly ASSP is not a Transparent proxy in the strict meaning of the > term and maintaining just the sender's "helo" while filtering > tagging, etc. just seems incorrect. > > So given the above definitions a proxy meets the criteria of a relay > in RFC 2821 and its action should follow D.3. > > But most important, and here is a valid argument for "transparency", > is that in a MUA, the email sitting in the inbox is would not appear > compliant with RFC 2821 and its apparent chain of custody would > appear spoofed using a helo/ehlo salutation that does not match the > IP of the ASSP. > > In response to JR's worry about multiple hosts within a domain and > the MTU's responses, I really don't see the issue, but that is for > another email if asked. > > Bottom line, shouldn't the mail headers on the email sitting in your > inbox reflect the chain of custody described in RFC 2821? > > Nevertheless, I bow to the desires of the community, I just wanted to > explain my position clearly. > > Tom > > > > > > ------------------------------------------------------------------------------ > 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 > ------------------------------------------------------------------------------ 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
