Re: Configuring Exim for mail delivery
On Sun, Oct 02, 2016 at 12:52:44PM +0100, Brian wrote:
> [Some snipping. Not too much, I hope].
>
> On Sun 02 Oct 2016 at 01:05:20 +0100, Liam O'Toole wrote:
>
> > On 2016-10-01, Brian <ad44@cityscape.co.uk> wrote:
> > >
> > > Exim's default behaviour, as has been mentioned a couple of times in
> > > this thread, is to use DNS; nsswitch is not involved.
> >
> > Doing an strace on the exim command shows that /etc/nsswitch is
> > consulted first, then /etc/resolv.conf (followed by a DNS lookup of the
> > smarthost).
>
> This is what I cannot get round. I'm prepared to accept that my
> understanding may be defective but when I see "driver = dnslookup" in
> router/200_exim4-config_primary it fits what I observe. Which is why I
> use a hubbed_hosts file to manually route mail to machines on the LAN.
>
> > > This is a default
> > > exim install; no files in conf.d altered. How about you?
> >
> > No alterations I can remember, and 'dpkg --verify' reports no changes to
> > exim4-related files. All customisations have been done via debconf. I am
> > reluctant to divulge those customisations here, but I can tell you that
> > the settings are not particularly exotic. One host on the local network
> > is configured to use my ISP's SMTP server as its smarthost, while the
> > other hosts in turn use the former as their smarthost.
>
> I have the same setup and all customisations (apart from hubbed_hosts)
> have been done via debconf. TBH, I cannot see why /etc/hosts should be
> consulted because I thought there is first a check for an MX record and
> then an attempt to resolve the host *using the DNS* if there was none.
>
> Your instructions are clear so I can continue to try more customising
> via debconf.
>
> mo appears to have had no more success than I have. Don't know about
> Mark.
>
> --
> Brian
>
That's twice you've mentioned conf.d now, bear in mind in a
defaults-accepting Debian installation of exim4, it's not used.
Mark
Reply to: