On Mon 20 Oct 2014 at 21:19:05 +0200, lee wrote: > Brian <[email protected]> writes: > > > [I may be misunderstanding how your mail system works but your Date: > > header doesn't look right] > > > > > > On Sun 19 Oct 2014 at 00:53:44 +0200, lee wrote: > > > >> Brian <[email protected]> writes: > >> > >> > On Fri 17 Oct 2014 at 03:15:49 +0200, lee wrote: > >> > > >> >> There is no mentioning of /etc/mailname here. Perhaps that's an > >> >> ideosyncrasy of the automatic configuration. > >> > > >> > No. It's because there is no connection between /etc/mailname and > >> > primary_hostname. > >> > >> Then how does it happen that Debian manages to configure exim in such a > >> way that the contents of /etc/mailname are being used instead of the > >> hostname? Is that another option exim has, and if so, how's it called? > > > > The contents of mailname are not used for the HELO. > > > > If /etc/mailname exists exim will not touch it when it is installed. If > > it does not exist it makes the assumption that canonical_hostname in the > > hosts file is correct and uses that as the mailname. The installation is > > at priority low or medium (I forget which) and no questions are asked. > > > > Suppose the hosts file has > > > > 127.0.1.1 debian.lan debian > > You mean it will rewrite <[email protected]> to <[email protected]> when > /etc/mailname is set to 'example.com'?
No. It will rewrite user to [email protected]. If the envelope To is set to [email protected] it will not be touched. > > primary_hostname is used as the HELO but Debian doesn't set it. > > That's what I said? You may have done. I was trying to say there is nowhere in the Debian configuration where primary_hostname as such could be specified. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected] Archive: https://lists.debian.org/[email protected]
