[Exim] Missing helo/ehlo entry in headers when reverse entry…

Página superior
Eliminar este mensaje
Responder a este mensaje
Autor: Andre van der Walt
Fecha:  
A: exim-users
Asunto: [Exim] Missing helo/ehlo entry in headers when reverse entry is the same
Hi List,

Recently I have noticed that when the reverse entry of a hosts is exactly
the same as the "helo/ehlo" entry it will leave out the "helo" entry, after
the ip, in the headers out Anyone know why this is happening or how to fix
this?? Had a look on Google but did not find anything.

Running on Red Hat Linux, Exim 4.24 & Exiscan

Example of reverse entry being the same as "helo/ehlo":
Received: from flash.dmz.advtech.co.za ([192.168.254.98])
by bushtiger.bugssolutions.co.za with smtp (Exim 4.22 #1)
id 1AMpyl-0000iL-Um
for <andre@???>; Thu, 20 Nov 2003 16:40:39 +0200

Example of reverse entry not being the same as "helo/ehlo":
Received: from gw.dmz.advtech.co.za ([192.168.254.97]
helo=bushtiger.bugssolutions.co.za)
by mail.advtech.co.za with esmtp (Exim 4.24 #1)
id 1AMq1B-0008J4-TK
for <andre@???>; Thu, 20 Nov 2003 16:42:49 +0200

And I have these entries in the configure file to do the mails headers:
received_header_text = "Received: \
         ${if def:sender_rcvhost {from ${sender_rcvhost}\n\t}\
         {${if def:sender_ident {from ${sender_ident} }}\
         ${if def:sender_helo_name {(helo=${sender_helo_name})\n\t}}}}\
         by ${primary_hostname} \
         ${if def:received_protocol {with ${received_protocol}}} \
         ${if def:tls_cipher {\n\t(Cipher ${tls_cipher}) }}\
         ${if def:tls_peerdn {(PeerDN ${tls_peerdn}) }}\
         (Exim ${version_number} #${compile_number})\n\t\
         id ${message_id}\
         ${if def:authenticated_id { by authid <$authenticated_id>}}\
         ${if def:sender_host_authenticated { with
$sender_host_authenticated}}\
         ${if def:received_for {\n\tfor <$received_for>}}"



Cheers,

Andre