also sprach dman <dsh8290@rit.edu> [2002.01.11.1700 +0100]: > Nex the system web30.achilles.net received the message vis ESMTP from > a host who said it was 'seal' in the EHLO command, but whose IP is > 209.151.2.114 which resolves to mail@port-15.ottawa4.achilles.net (I > didn't think the "@" was legal in a hostname though, perhaps that is > just something the MTA sticks in the header). it's an ident lookup in addition to a hostname lookup. > | Received: (qmail 21575 invoked from network); 11 Jan 2002 04:30:36 > | -0000 > > qmail got the message next. Pretty sparse data here. I guess one > would need to be familiar with qmail's operation to know what "invoked > from network" means. Still, it doesn't say what machine or anything. SMTP. simple as that. DJB... oh well... > | Or is the next Received header (Received: from unknown...) trying > | to tell me something about my exim.conf? > > Nope, it is telling you that your ISP is (partially) messed up :-). any isp with 'doze machines is messed up! > The purpose of the Received: headers are just to allow admins to track > down what happened to a message so that configs can be debugged. Each > system can be configured to put whatever it wants as a Received: > header, or nothing at all. It is recommended to include the info, > though, in case something goes wrong somewhere. a very nice feature of exim and sendmail btw. i wish postfix could rewrite the received headers. then i could put my crappy humour in there. -- martin; (greetings from the heart of the sun.) \____ echo mailto: !#^."<*>"|tr "<*> mailto:"; net@madduck echo '[dO%O+38%O+PO/d0<0]Fi22os0CC4BA64E418CE7l0xAP'|dc
Attachment:
pgpCo3gWbyrLV.pgp
Description: PGP signature