At 6:02 pm +0400 2004/09/02, Peter Savitch wrote:
>Hello,
>
>I don't see any harm using real-world HELO on eth0/eth1, but if you'd
>like to...
>
>To fix your _advertised_ HELO/EHLO string use string-expanded global
>option smtp_banner, but with caution ($interface_address is not always
>set, at least in -bs it's null):
>
what has smtp_banner got to do with the HELO/EHLO string?
This is probably more relevant:
helo_data Type: string* Default: $primary_hostname
The value of this option is expanded, and used as the argument for the
EHLO or HELO command that starts the outgoing SMTP session.
and I believe it could be set in the smtp transport according to the
interface you use.
Giuliano
>-----Original Message-----
>From: exim-users-bounces@??? [mailto:exim-users-bounces@exim.org]
>On Behalf Of leo@???
>Sent: Wednesday, September 01, 2004 9:27 AM
>To: exim-users@???
>Subject: [exim] HELO eth1
>
>I have a serverthat is connected to two different subnet, on two
>different
>domains, on two tifferent ISP [actually the thing is wanted, to have
>more
>"network availability"].
>Usually it uses the official network on eth0.
>If this is not workink however connections are routed throught et1.
>I have noticed seeing some message sent this way that the server on helo
>
>give always is "official" domain name, that is hostname.sub.domain.it
>even if it
>uses eth1 that is mx.domain.net
>(Incidentally: reverse DNS for eth0 address point to hostname.domain.it,
>
>
>...
