james-server-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steve Brewin (JIRA)" <server-...@james.apache.org>
Subject [jira] Commented: (JAMES-344) FetchMail cannot parse particular format of "Received" header
Date Tue, 04 Jan 2005 21:52:12 GMT
     [ http://issues.apache.org/jira/browse/JAMES-344?page=comments#action_57278 ]
     
Steve Brewin commented on JAMES-344:
------------------------------------

Even if on visual examination the IP address appears to be present, the format is invalid
according to my reading of the RFCs.

Unless its a well know defacto divergence from the RFC, personally I am not keen on suppporting
it. Once we start on such a path, where do we stop?

Far from being a moot point, this is the crux of the issue. How do we deal with non-compliant
trace information? The current strategy is to allow the choice of rejection or propogation
with a warning mail attribute attached. If the latter option is chosen, anyone is free to
write a Mailet that interprets and adjust the trace information as they choose after injection
into the James spool.

As noted in JAMES-345 there may be an issue with the implementation, but the intent is in
my view correct.

Out of interest, do you know what breed of mail servers are producing this information?

> FetchMail cannot parse particular format of "Received" header
> -------------------------------------------------------------
>
>          Key: JAMES-344
>          URL: http://issues.apache.org/jira/browse/JAMES-344
>      Project: James
>         Type: Bug
>   Components: FetchMail
>     Versions: 2.2.1
>     Reporter: Jeff Keyser
>     Priority: Minor

>
> The mail server I am pulling e-mail from inserts a "Received" header that looks like
the following:
> Received: from unknown (HELO host.domain.tld) (192.168.255.254) by ...
> BTW - The name "unknown" is always used.  I assume they are purposely saving processing
power by not reverse-looking up the host name.
> I have debugged this problem in the code, and it appears that because the IP address
is not surrounded by square brackets, computeRemoteAddress is unable to find the IP address.
 So the name "unknown" is always used to determine the address instead, which fails.
> FYI - The e-mail I am pulling actually passes through two e-mail servers by different
organizations, and they both use this format.  So I assume this format is common.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org


Mime
View raw message