Currently assp writes its received header correctly but establishes communication with the mailserver announcing itself in helo/ehlo using the same helo/ehlo that it received. This results in the headers I copied below.
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 it be possible to fix this? The best way might be on startup to do a reverse lookup of its IP and use myName if the IP is in the unroutable groups? An alternative might be to add a GUI entry to allow users to define the helo/ehlo domain/host used for Client Initiation or maybe just reuse myname for this purpose since, "ASSP will identify itself by this name in the email "Received:" header and in the helo when sending report-replies. Usually the fully qualified domain name of the host." Example received lines: Received: from [88.234.37.94] (206.208.58.52) by oitc.com with ESMTP (EIMS X 3.3.7) for <[email protected]>; Sat, 14 Mar 2009 05:30:36 -0400 Received: from [88.234.37.94] ([88.234.37.94] helo=[88.234.37.94]) with IPv4:25 by assp.oitc.com; 14 Mar 2009 05:30:32 -0400 ------------------------------------------------------------------------------ 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
