And behold; the HELO-Message is _NOT_ my.new.helo but some hostname
probably from /etc/hosts.
The point is: This isn't a feature that was present, nor is the use
of a file named /etc/mailhelo standard (only widely used), BUT the
functionality itself is very much necessary, for instance for mailhosts
behind firewalls. And solving the problem by hand excludes of course
the generation of an exim-config by dpkg-reconfigure.
Kind Regards
Peter
--
"Those who give up essential liberties for temporary safety deserve
neither liberty nor safety." -- Benjamin Franklin
"It's also true that those who would give up privacy for security are
likely to end up with neither." -- Bruce Schneier
Hello
* on the Mon, Feb 07, 2011 at 02:02:56PM -0000, Chuck Short wrote:
> 1. Is this reproducible?
Absolutely. The exim-Config in Ubuntu just has no provisions to set
helo_data from /etc/mailhelo (or somewhere else).
See www.exim. org/exim- html-current/ doc/html/ spec_html/ ch30.html
http://
> 2. If so, what specific steps should we take to recreate this bug?
> Be as detailed as possible.
echo "my.new.helo" > /etc/mailhelo
/etc/init.d/exim4 restart
telnet localhost 25
HELO somedomain
And behold; the HELO-Message is _NOT_ my.new.helo but some hostname
probably from /etc/hosts.
The point is: This isn't a feature that was present, nor is the use
of a file named /etc/mailhelo standard (only widely used), BUT the
functionality itself is very much necessary, for instance for mailhosts
behind firewalls. And solving the problem by hand excludes of course
the generation of an exim-config by dpkg-reconfigure.
Kind Regards
Peter
--
"Those who give up essential liberties for temporary safety deserve
neither liberty nor safety." -- Benjamin Franklin
"It's also true that those who would give up privacy for security are
likely to end up with neither." -- Bruce Schneier