Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #172999 > unrolled thread
| Started by | mo <mo777@gmx.net> |
|---|---|
| First post | 2016-09-30 22:30 +0200 |
| Last post | 2016-10-01 22:50 +0200 |
| Articles | 11 on this page of 51 — 8 participants |
Back to article view | Back to linux.debian.user
Configuring Exim for mail delivery mo <mo777@gmx.net> - 2016-09-30 22:30 +0200
Re: Configuring Exim for mail delivery Liam O'Toole <liam.p.otoole@gmail.com> - 2016-10-01 00:50 +0200
Re: Configuring Exim for mail delivery Mark Fletcher <mark27q1@gmail.com> - 2016-10-01 04:00 +0200
Re: Configuring Exim for mail delivery mo <mo777@gmx.net> - 2016-10-01 12:40 +0200
Re: Configuring Exim for mail delivery Brian <ad44@cityscape.co.uk> - 2016-10-01 13:30 +0200
Re: Configuring Exim for mail delivery mo <mo777@gmx.net> - 2016-10-01 13:50 +0200
Re: Configuring Exim for mail delivery Clive Menzies <clive@clivemenzies.co.uk> - 2016-10-01 14:00 +0200
Re: Configuring Exim for mail delivery mo <mo777@gmx.net> - 2016-10-01 14:10 +0200
Re: Configuring Exim for mail delivery mo <mo777@gmx.net> - 2016-10-01 14:10 +0200
Re: Configuring Exim for mail delivery Mark Fletcher <mark27q1@gmail.com> - 2016-10-01 14:10 +0200
Re: Configuring Exim for mail delivery Mark Fletcher <mark27q1@gmail.com> - 2016-10-01 14:30 +0200
Re: Configuring Exim for mail delivery mo <mo777@gmx.net> - 2016-10-01 14:40 +0200
Re: Configuring Exim for mail delivery Mark Fletcher <mark27q1@gmail.com> - 2016-10-01 15:00 +0200
Re: Configuring Exim for mail delivery mo <mo777@gmx.net> - 2016-10-01 15:00 +0200
Re: Configuring Exim for mail delivery Brian <ad44@cityscape.co.uk> - 2016-10-01 15:00 +0200
Re: Configuring Exim for mail delivery mo <mo777@gmx.net> - 2016-10-01 15:10 +0200
Re: Configuring Exim for mail delivery Mark Fletcher <mark27q1@gmail.com> - 2016-10-01 15:40 +0200
Re: Configuring Exim for mail delivery mo <mo777@gmx.net> - 2016-10-01 16:20 +0200
Re: Configuring Exim for mail delivery Brian <ad44@cityscape.co.uk> - 2016-10-01 16:40 +0200
Re: Configuring Exim for mail delivery Teemu Likonen <tlikonen@iki.fi> - 2016-10-01 16:00 +0200
Re: Configuring Exim for mail delivery mo <mo777@gmx.net> - 2016-10-01 16:20 +0200
Re: Configuring Exim for mail delivery mo <mo777@gmx.net> - 2016-10-01 11:10 +0200
Re: Configuring Exim for mail delivery Brian <ad44@cityscape.co.uk> - 2016-10-01 12:10 +0200
Re: Configuring Exim for mail delivery mo <mo777@gmx.net> - 2016-10-01 12:40 +0200
Re: Configuring Exim for mail delivery mo <mo777@gmx.net> - 2016-10-01 14:10 +0200
Re: Configuring Exim for mail delivery Brian <ad44@cityscape.co.uk> - 2016-10-01 14:30 +0200
Re: Configuring Exim for mail delivery mo <mo777@gmx.net> - 2016-10-01 14:30 +0200
Re: Configuring Exim for mail delivery Mark Fletcher <mark27q1@gmail.com> - 2016-10-01 15:00 +0200
Re: Configuring Exim for mail delivery mo <mo777@gmx.net> - 2016-10-01 15:10 +0200
Re: Configuring Exim for mail delivery Mark Fletcher <mark27q1@gmail.com> - 2016-10-01 14:10 +0200
Re: Configuring Exim for mail delivery Mark Fletcher <mark27q1@gmail.com> - 2016-10-01 13:40 +0200
Re: Configuring Exim for mail delivery mo <mo777@gmx.net> - 2016-10-01 14:10 +0200
Re: Configuring Exim for mail delivery rhkramer@gmail.com - 2016-10-01 14:20 +0200
Re: Configuring Exim for mail delivery mo <mo777@gmx.net> - 2016-10-01 16:30 +0200
Re: Configuring Exim for mail delivery Liam O'Toole <liam.p.otoole@gmail.com> - 2016-10-01 18:30 +0200
Re: Configuring Exim for mail delivery Brian <ad44@cityscape.co.uk> - 2016-10-01 20:20 +0200
Re: Configuring Exim for mail delivery mo <mo777@gmx.net> - 2016-10-01 22:50 +0200
Re: Configuring Exim for mail delivery Brian <ad44@cityscape.co.uk> - 2016-10-02 00:30 +0200
Re: Configuring Exim for mail delivery Mark Fletcher <mark27q1@gmail.com> - 2016-10-02 02:30 +0200
Re: Configuring Exim for mail delivery Liam O'Toole <liam.p.otoole@gmail.com> - 2016-10-02 13:10 +0200
Re: Configuring Exim for mail delivery mo <mo777@gmx.net> - 2016-10-02 10:50 +0200
Re: Configuring Exim for mail delivery Liam O'Toole <liam.p.otoole@gmail.com> - 2016-10-01 23:10 +0200
Re: Configuring Exim for mail delivery Brian <ad44@cityscape.co.uk> - 2016-10-02 00:40 +0200
Re: Configuring Exim for mail delivery Liam O'Toole <liam.p.otoole@gmail.com> - 2016-10-02 02:10 +0200
Re: Configuring Exim for mail delivery Brian <ad44@cityscape.co.uk> - 2016-10-02 14:00 +0200
Re: Configuring Exim for mail delivery Mark Fletcher <mark27q1@gmail.com> - 2016-10-02 14:50 +0200
Re: Configuring Exim for mail delivery Gene Heskett <gheskett@shentel.net> - 2016-10-02 15:20 +0200
Re: Configuring Exim for mail delivery Mark Fletcher <mark27q1@gmail.com> - 2016-10-02 15:50 +0200
Re: Configuring Exim for mail delivery Brian <ad44@cityscape.co.uk> - 2016-10-02 15:40 +0200
Re: Configuring Exim for mail delivery Liam O'Toole <liam.p.otoole@gmail.com> - 2016-10-02 17:30 +0200
Re: Configuring Exim for mail delivery mo <mo777@gmx.net> - 2016-10-01 22:50 +0200
Page 3 of 3 — ← Prev page 1 2 [3]
| From | mo <mo777@gmx.net> |
|---|---|
| Date | 2016-10-02 10:50 +0200 |
| Message-ID | <snKD7-4va-3@gated-at.bofh.it> |
| In reply to | #173088 |
Am 02.10.2016 um 00:22 schrieb Brian: > On Sat 01 Oct 2016 at 22:47:27 +0200, mo wrote: > >> Am 01.10.2016 um 20:17 schrieb Brian: >>> On Sat 01 Oct 2016 at 17:25:46 +0100, Liam O'Toole wrote: >>> >>>> On 2016-10-01, mo <mo777@gmx.net> wrote: >>>>> First of all: >>>>> Thank you Liam for your help! :) >>>>> Thanks for the very nice and long explanation Mark! :) >>>>> >>>>> I think i should elaborate a little more on my setup.. i guess i did not >>>>> make that very clear in the first place, sorry about that. >>>>> >>>>> My network is consisting of the following systems: >>>>> >>>>> Main PC - 192.168.23.11 (Running Debian Jessie) >>>>> Server - 192.168.23.200 (Running Debian Jessie) >>>>> >>>>> The server is always online, the PC is only half of the day on. >>>>> >>>>> What i want to do now is the following: >>>>> >>>>> Sending mail from my Main PC to my Server and also the other way around, >>>> >from the Server to my Main PC. >>>>> The Server should also be able to send mail to the "outside" (Meaning to >>>>> other SMTP servers). >>>>> The second requirement is optional since i dont own a domain and all >>>>> this is sitting locally at my home. The most important thing for me is >>>>> to send and receive mail from both systems in my home network. >>>>> I hope this made my problem a little clearer :) >>>>> >>>>> I'm a little ashamed to say that, but i could not totally follow your >>>>> explanations Mark... I'm quite a newbie when it comes to SMTP.. sorry :( >>>>> >>>>> Thanks again for all your help ;) >>>>> >>>>> Greets >>>>> >>>>> mo >>>>> >>>>> >>>> >>>> I should have been a little clearer myself. You don't need to register a >>>> domain name. Just invent your own domain name for local purposes. Let's >>>> say you choose the domain name "monet", and that you have already given >>>> the hostnames "desktop" and "server" to your two machines. Then you >>>> would edit the file /etc/hosts on both machines to contain the following >>>> lines: >>>> >>>> 192.168.23.11 desktop.monet desktop >>>> 192.168.23.200 server.monet server >>> >>> I did that on gnome and desktop with appropriate changes: >>> >>> 192.168.7.20 desktop.monet desktop >>> 192.168.7.67 gnome.monet gnome >>> >>>> Now you only need to tell exim4 on the server that it is the final >>>> destination for emails to *.monet, again using the debconf wizard. You >>>> will then be able to send emails to local addresses, while emails to all >>>> other domains will go through your ISP's smarthost. >>> >>> I did that on gnome and desktop. >>> >>>> Incidently, you can also tell exim4 on the desktop to use the server as >>>> its smarthost. >>>> >>>> I realise that you're getting lots of (sometimes contradictory) >>>> information from various sources. The barebones configuration I have >>>> described above has served me well for several years. >>> >>> All commands are issued from gnome. >>> >>> brian@gnome:~# ping -c3 desktop >>> PING desktop.monet (192.168.7.20) 56(84) bytes of data. >>> 64 bytes from desktop.monet (192.168.7.20): icmp_seq=1 ttl=64 time=0.267 ms >>> 64 bytes from desktop.monet (192.168.7.20): icmp_seq=2 ttl=64 time=0.255 ms >>> 64 bytes from desktop.monet (192.168.7.20): icmp_seq=3 ttl=64 time=0.269 ms >>> >>> --- desktop.monet ping statistics --- >>> 3 packets transmitted, 3 received, 0% packet loss, time 2001ms >>> rtt min/avg/max/mdev = 0.255/0.263/0.269/0.019 ms >>> >>> brian@gnome:~# ping -c3 desktop.monet >>> PING desktop.monet (192.168.7.20) 56(84) bytes of data. >>> 64 bytes from desktop.monet (192.168.7.20): icmp_seq=1 ttl=64 time=0.264 ms >>> 64 bytes from desktop.monet (192.168.7.20): icmp_seq=2 ttl=64 time=0.255 ms >>> 64 bytes from desktop.monet (192.168.7.20): icmp_seq=3 ttl=64 time=0.255 ms >>> >>> --- desktop.monet ping statistics --- >>> 3 packets transmitted, 3 received, 0% packet loss, time 2002ms >>> rtt min/avg/max/mdev = 0.255/0.258/0.264/0.004 ms >>> >>> We expect that result because ping uses files in /etc/nsswitch. >>> >>> root@gnome:~# exim -bt brian@desktop >>> R: dnslookup for brian@desktop >>> brian@desktop is undeliverable: Unrouteable address >>> >>> root@gnome:~# exim -bt brian@desktop.monet >>> R: dnslookup for brian@desktop.monet >>> brian@desktop.monet is undeliverable: Unrouteable address >>> >>> Am I the only one who gets this? No capability to deliver mail to >>> desktop. What am I doing wrong? >>> >> >> I think this is the problem with exim calling DNS on the given hostname... >> which is doomed to fail. To get it working you need to create the >> hubbed_hosts file and set your aliases in there, for example: >> 192.168.7.20: desktop >> >> Then it should work fine, at least for me it did. >> >> Hope this helps :) > > Not really, I'm afraid. > > We all know a hubbed_hosts file works. Mark Fletcher has written > extensively about it and I have said a thing or too also. What I want to > know is why following the advice from Liam O'Toole doesn't work for me, > even though I have followed the instructions exactly. > > BTW: It would be 'desktop: 192.168.7.20' and 'desktop.monet:192.168.7.20' > in hubbed_hosts. Ah yeah, right, i mixed the syntax up, sorry about that.
[toc] | [prev] | [next] | [standalone]
| From | Liam O'Toole <liam.p.otoole@gmail.com> |
|---|---|
| Date | 2016-10-01 23:10 +0200 |
| Message-ID | <snzHI-5Dd-13@gated-at.bofh.it> |
| In reply to | #173071 |
On 2016-10-01, Brian <ad44@cityscape.co.uk> wrote: > On Sat 01 Oct 2016 at 17:25:46 +0100, Liam O'Toole wrote: > >> On 2016-10-01, mo <mo777@gmx.net> wrote: >> > First of all: >> > Thank you Liam for your help! :) >> > Thanks for the very nice and long explanation Mark! :) >> > >> > I think i should elaborate a little more on my setup.. i guess i did not >> > make that very clear in the first place, sorry about that. >> > >> > My network is consisting of the following systems: >> > >> > Main PC - 192.168.23.11 (Running Debian Jessie) >> > Server - 192.168.23.200 (Running Debian Jessie) >> > >> > The server is always online, the PC is only half of the day on. >> > >> > What i want to do now is the following: >> > >> > Sending mail from my Main PC to my Server and also the other way around, >> > from the Server to my Main PC. >> > The Server should also be able to send mail to the "outside" (Meaning to >> > other SMTP servers). >> > The second requirement is optional since i dont own a domain and all >> > this is sitting locally at my home. The most important thing for me is >> > to send and receive mail from both systems in my home network. >> > I hope this made my problem a little clearer :) >> > >> > I'm a little ashamed to say that, but i could not totally follow your >> > explanations Mark... I'm quite a newbie when it comes to SMTP.. sorry :( >> > >> > Thanks again for all your help ;) >> > >> > Greets >> > >> > mo >> > >> > >> >> I should have been a little clearer myself. You don't need to register a >> domain name. Just invent your own domain name for local purposes. Let's >> say you choose the domain name "monet", and that you have already given >> the hostnames "desktop" and "server" to your two machines. Then you >> would edit the file /etc/hosts on both machines to contain the following >> lines: >> >> 192.168.23.11 desktop.monet desktop >> 192.168.23.200 server.monet server > > I did that on gnome and desktop with appropriate changes: > > 192.168.7.20 desktop.monet desktop > 192.168.7.67 gnome.monet gnome > >> Now you only need to tell exim4 on the server that it is the final >> destination for emails to *.monet, again using the debconf wizard. You >> will then be able to send emails to local addresses, while emails to all >> other domains will go through your ISP's smarthost. > > I did that on gnome and desktop. > >> Incidently, you can also tell exim4 on the desktop to use the server as >> its smarthost. >> >> I realise that you're getting lots of (sometimes contradictory) >> information from various sources. The barebones configuration I have >> described above has served me well for several years. > > All commands are issued from gnome. > > brian@gnome:~# ping -c3 desktop > PING desktop.monet (192.168.7.20) 56(84) bytes of data. > 64 bytes from desktop.monet (192.168.7.20): icmp_seq=1 ttl=64 time=0.267 ms > 64 bytes from desktop.monet (192.168.7.20): icmp_seq=2 ttl=64 time=0.255 ms > 64 bytes from desktop.monet (192.168.7.20): icmp_seq=3 ttl=64 time=0.269 ms > > --- desktop.monet ping statistics --- > 3 packets transmitted, 3 received, 0% packet loss, time 2001ms > rtt min/avg/max/mdev = 0.255/0.263/0.269/0.019 ms > > brian@gnome:~# ping -c3 desktop.monet > PING desktop.monet (192.168.7.20) 56(84) bytes of data. > 64 bytes from desktop.monet (192.168.7.20): icmp_seq=1 ttl=64 time=0.264 ms > 64 bytes from desktop.monet (192.168.7.20): icmp_seq=2 ttl=64 time=0.255 ms > 64 bytes from desktop.monet (192.168.7.20): icmp_seq=3 ttl=64 time=0.255 ms > > --- desktop.monet ping statistics --- > 3 packets transmitted, 3 received, 0% packet loss, time 2002ms > rtt min/avg/max/mdev = 0.255/0.258/0.264/0.004 ms > > We expect that result because ping uses files in /etc/nsswitch. > > root@gnome:~# exim -bt brian@desktop > R: dnslookup for brian@desktop > brian@desktop is undeliverable: Unrouteable address > > root@gnome:~# exim -bt brian@desktop.monet > R: dnslookup for brian@desktop.monet > brian@desktop.monet is undeliverable: Unrouteable address > > Am I the only one who gets this? No capability to deliver mail to > desktop. What am I doing wrong? > exim seems to be trying to resolve desktop.monet via DNS, thus ignoring /etc/nsswitch. (I have no idea whether that is the default behaviour.) Do you have a local DNS capable of resolving the address? You might try the mail command from the mailutils or bsd-mailx packages for comparison. -- Liam
[toc] | [prev] | [next] | [standalone]
| From | Brian <ad44@cityscape.co.uk> |
|---|---|
| Date | 2016-10-02 00:40 +0200 |
| Message-ID | <snB6O-6tF-29@gated-at.bofh.it> |
| In reply to | #173086 |
On Sat 01 Oct 2016 at 21:52:53 +0100, Liam O'Toole wrote: > On 2016-10-01, Brian <ad44@cityscape.co.uk> wrote: > > On Sat 01 Oct 2016 at 17:25:46 +0100, Liam O'Toole wrote: > > > >> On 2016-10-01, mo <mo777@gmx.net> wrote: > >> > First of all: > >> > Thank you Liam for your help! :) > >> > Thanks for the very nice and long explanation Mark! :) > >> > > >> > I think i should elaborate a little more on my setup.. i guess i did not > >> > make that very clear in the first place, sorry about that. > >> > > >> > My network is consisting of the following systems: > >> > > >> > Main PC - 192.168.23.11 (Running Debian Jessie) > >> > Server - 192.168.23.200 (Running Debian Jessie) > >> > > >> > The server is always online, the PC is only half of the day on. > >> > > >> > What i want to do now is the following: > >> > > >> > Sending mail from my Main PC to my Server and also the other way around, > >> > from the Server to my Main PC. > >> > The Server should also be able to send mail to the "outside" (Meaning to > >> > other SMTP servers). > >> > The second requirement is optional since i dont own a domain and all > >> > this is sitting locally at my home. The most important thing for me is > >> > to send and receive mail from both systems in my home network. > >> > I hope this made my problem a little clearer :) > >> > > >> > I'm a little ashamed to say that, but i could not totally follow your > >> > explanations Mark... I'm quite a newbie when it comes to SMTP.. sorry :( > >> > > >> > Thanks again for all your help ;) > >> > > >> > Greets > >> > > >> > mo > >> > > >> > > >> > >> I should have been a little clearer myself. You don't need to register a > >> domain name. Just invent your own domain name for local purposes. Let's > >> say you choose the domain name "monet", and that you have already given > >> the hostnames "desktop" and "server" to your two machines. Then you > >> would edit the file /etc/hosts on both machines to contain the following > >> lines: > >> > >> 192.168.23.11 desktop.monet desktop > >> 192.168.23.200 server.monet server > > > > I did that on gnome and desktop with appropriate changes: > > > > 192.168.7.20 desktop.monet desktop > > 192.168.7.67 gnome.monet gnome > > > >> Now you only need to tell exim4 on the server that it is the final > >> destination for emails to *.monet, again using the debconf wizard. You > >> will then be able to send emails to local addresses, while emails to all > >> other domains will go through your ISP's smarthost. > > > > I did that on gnome and desktop. > > > >> Incidently, you can also tell exim4 on the desktop to use the server as > >> its smarthost. > >> > >> I realise that you're getting lots of (sometimes contradictory) > >> information from various sources. The barebones configuration I have > >> described above has served me well for several years. > > > > All commands are issued from gnome. > > > > brian@gnome:~# ping -c3 desktop > > PING desktop.monet (192.168.7.20) 56(84) bytes of data. > > 64 bytes from desktop.monet (192.168.7.20): icmp_seq=1 ttl=64 time=0.267 ms > > 64 bytes from desktop.monet (192.168.7.20): icmp_seq=2 ttl=64 time=0.255 ms > > 64 bytes from desktop.monet (192.168.7.20): icmp_seq=3 ttl=64 time=0.269 ms > > > > --- desktop.monet ping statistics --- > > 3 packets transmitted, 3 received, 0% packet loss, time 2001ms > > rtt min/avg/max/mdev = 0.255/0.263/0.269/0.019 ms > > > > brian@gnome:~# ping -c3 desktop.monet > > PING desktop.monet (192.168.7.20) 56(84) bytes of data. > > 64 bytes from desktop.monet (192.168.7.20): icmp_seq=1 ttl=64 time=0.264 ms > > 64 bytes from desktop.monet (192.168.7.20): icmp_seq=2 ttl=64 time=0.255 ms > > 64 bytes from desktop.monet (192.168.7.20): icmp_seq=3 ttl=64 time=0.255 ms > > > > --- desktop.monet ping statistics --- > > 3 packets transmitted, 3 received, 0% packet loss, time 2002ms > > rtt min/avg/max/mdev = 0.255/0.258/0.264/0.004 ms > > > > We expect that result because ping uses files in /etc/nsswitch. > > > > root@gnome:~# exim -bt brian@desktop > > R: dnslookup for brian@desktop > > brian@desktop is undeliverable: Unrouteable address > > > > root@gnome:~# exim -bt brian@desktop.monet > > R: dnslookup for brian@desktop.monet > > brian@desktop.monet is undeliverable: Unrouteable address > > > > Am I the only one who gets this? No capability to deliver mail to > > desktop. What am I doing wrong? > > > > exim seems to be trying to resolve desktop.monet via DNS, thus ignoring > /etc/nsswitch. (I have no idea whether that is the default behaviour.) Do > you have a local DNS capable of resolving the address? Exim's default behaviour, as has been mentioned a couple of times in this thread, is to use DNS; nsswitch is not involved. This is a default exim install; no files in conf.d altered. How about you? > You might try the mail command from the mailutils or bsd-mailx packages > for comparison. mail uses exim as the MTA. It is hardly likely to work. -- Brian.
[toc] | [prev] | [next] | [standalone]
| From | Liam O'Toole <liam.p.otoole@gmail.com> |
|---|---|
| Date | 2016-10-02 02:10 +0200 |
| Message-ID | <snCvT-7vS-9@gated-at.bofh.it> |
| In reply to | #173089 |
On 2016-10-01, Brian <ad44@cityscape.co.uk> wrote: > On Sat 01 Oct 2016 at 21:52:53 +0100, Liam O'Toole wrote: > >> On 2016-10-01, Brian <ad44@cityscape.co.uk> wrote: >> > On Sat 01 Oct 2016 at 17:25:46 +0100, Liam O'Toole wrote: >> > >> >> On 2016-10-01, mo <mo777@gmx.net> wrote: >> >> > First of all: >> >> > Thank you Liam for your help! :) >> >> > Thanks for the very nice and long explanation Mark! :) >> >> > >> >> > I think i should elaborate a little more on my setup.. i guess i did not >> >> > make that very clear in the first place, sorry about that. >> >> > >> >> > My network is consisting of the following systems: >> >> > >> >> > Main PC - 192.168.23.11 (Running Debian Jessie) >> >> > Server - 192.168.23.200 (Running Debian Jessie) >> >> > >> >> > The server is always online, the PC is only half of the day on. >> >> > >> >> > What i want to do now is the following: >> >> > >> >> > Sending mail from my Main PC to my Server and also the other way around, >> >> > from the Server to my Main PC. >> >> > The Server should also be able to send mail to the "outside" (Meaning to >> >> > other SMTP servers). >> >> > The second requirement is optional since i dont own a domain and all >> >> > this is sitting locally at my home. The most important thing for me is >> >> > to send and receive mail from both systems in my home network. >> >> > I hope this made my problem a little clearer :) >> >> > >> >> > I'm a little ashamed to say that, but i could not totally follow your >> >> > explanations Mark... I'm quite a newbie when it comes to SMTP.. sorry :( >> >> > >> >> > Thanks again for all your help ;) >> >> > >> >> > Greets >> >> > >> >> > mo >> >> > >> >> > >> >> >> >> I should have been a little clearer myself. You don't need to register a >> >> domain name. Just invent your own domain name for local purposes. Let's >> >> say you choose the domain name "monet", and that you have already given >> >> the hostnames "desktop" and "server" to your two machines. Then you >> >> would edit the file /etc/hosts on both machines to contain the following >> >> lines: >> >> >> >> 192.168.23.11 desktop.monet desktop >> >> 192.168.23.200 server.monet server >> > >> > I did that on gnome and desktop with appropriate changes: >> > >> > 192.168.7.20 desktop.monet desktop >> > 192.168.7.67 gnome.monet gnome >> > >> >> Now you only need to tell exim4 on the server that it is the final >> >> destination for emails to *.monet, again using the debconf wizard. You >> >> will then be able to send emails to local addresses, while emails to all >> >> other domains will go through your ISP's smarthost. >> > >> > I did that on gnome and desktop. >> > >> >> Incidently, you can also tell exim4 on the desktop to use the server as >> >> its smarthost. >> >> >> >> I realise that you're getting lots of (sometimes contradictory) >> >> information from various sources. The barebones configuration I have >> >> described above has served me well for several years. >> > >> > All commands are issued from gnome. >> > >> > brian@gnome:~# ping -c3 desktop >> > PING desktop.monet (192.168.7.20) 56(84) bytes of data. >> > 64 bytes from desktop.monet (192.168.7.20): icmp_seq=1 ttl=64 time=0.267 ms >> > 64 bytes from desktop.monet (192.168.7.20): icmp_seq=2 ttl=64 time=0.255 ms >> > 64 bytes from desktop.monet (192.168.7.20): icmp_seq=3 ttl=64 time=0.269 ms >> > >> > --- desktop.monet ping statistics --- >> > 3 packets transmitted, 3 received, 0% packet loss, time 2001ms >> > rtt min/avg/max/mdev = 0.255/0.263/0.269/0.019 ms >> > >> > brian@gnome:~# ping -c3 desktop.monet >> > PING desktop.monet (192.168.7.20) 56(84) bytes of data. >> > 64 bytes from desktop.monet (192.168.7.20): icmp_seq=1 ttl=64 time=0.264 ms >> > 64 bytes from desktop.monet (192.168.7.20): icmp_seq=2 ttl=64 time=0.255 ms >> > 64 bytes from desktop.monet (192.168.7.20): icmp_seq=3 ttl=64 time=0.255 ms >> > >> > --- desktop.monet ping statistics --- >> > 3 packets transmitted, 3 received, 0% packet loss, time 2002ms >> > rtt min/avg/max/mdev = 0.255/0.258/0.264/0.004 ms >> > >> > We expect that result because ping uses files in /etc/nsswitch. >> > >> > root@gnome:~# exim -bt brian@desktop >> > R: dnslookup for brian@desktop >> > brian@desktop is undeliverable: Unrouteable address >> > >> > root@gnome:~# exim -bt brian@desktop.monet >> > R: dnslookup for brian@desktop.monet >> > brian@desktop.monet is undeliverable: Unrouteable address >> > >> > Am I the only one who gets this? No capability to deliver mail to >> > desktop. What am I doing wrong? >> > >> >> exim seems to be trying to resolve desktop.monet via DNS, thus ignoring >> /etc/nsswitch. (I have no idea whether that is the default behaviour.) Do >> you have a local DNS capable of resolving the address? > > 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 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. >> You might try the mail command from the mailutils or bsd-mailx packages >> for comparison. > > mail uses exim as the MTA. It is hardly likely to work. > Indeed. Please strike my suggestion from the record, m'lud. I misunderstood the meaning of the '-bt' switch you quoted above. -- Liam
[toc] | [prev] | [next] | [standalone]
| From | Brian <ad44@cityscape.co.uk> |
|---|---|
| Date | 2016-10-02 14:00 +0200 |
| Message-ID | <snNB0-6oj-17@gated-at.bofh.it> |
| In reply to | #173093 |
[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
[toc] | [prev] | [next] | [standalone]
| From | Mark Fletcher <mark27q1@gmail.com> |
|---|---|
| Date | 2016-10-02 14:50 +0200 |
| Message-ID | <snOnn-6Za-1@gated-at.bofh.it> |
| In reply to | #173114 |
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
[toc] | [prev] | [next] | [standalone]
| From | Gene Heskett <gheskett@shentel.net> |
|---|---|
| Date | 2016-10-02 15:20 +0200 |
| Message-ID | <snOQp-7p0-7@gated-at.bofh.it> |
| In reply to | #173118 |
On Sunday 02 October 2016 08:41:50 Mark Fletcher wrote: > 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 Uuh, Mark, here on an up to date wheezy install, with exim4's default config untouched, it does indeed exist, as /etc/exim4/conf.d, and its populated with quite a few subdirs. ========= gene@coyote:~$ ls -l /etc/exim4/conf.d total 28 drwxr-xr-x 2 root root 4096 Apr 4 21:35 acl drwxr-xr-x 2 root root 4096 Apr 4 21:35 auth drwxr-xr-x 2 root root 4096 Apr 4 21:35 main drwxr-xr-x 2 root root 4096 Apr 4 21:35 retry drwxr-xr-x 2 root root 4096 Apr 4 21:35 rewrite drwxr-xr-x 2 root root 4096 Apr 4 21:35 router drwxr-xr-x 2 root root 4096 Apr 4 21:35 transport ========== Based on the dates, I have to assume exim4 was pulled in as a dependency of something else I installed recently since this wheezy install is around 2 years old now. It's installation did not effect how my machine runs that I am aware of. According to htop, no daemon of that name is currently running. Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene>
[toc] | [prev] | [next] | [standalone]
| From | Mark Fletcher <mark27q1@gmail.com> |
|---|---|
| Date | 2016-10-02 15:50 +0200 |
| Message-ID | <snPjs-7yu-5@gated-at.bofh.it> |
| In reply to | #173121 |
On Sun, Oct 02, 2016 at 09:17:58AM -0400, Gene Heskett wrote: > On Sunday 02 October 2016 08:41:50 Mark Fletcher wrote: > > > 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 > > Uuh, Mark, here on an up to date wheezy install, with exim4's default > config untouched, it does indeed exist, as /etc/exim4/conf.d, and its > populated with quite a few subdirs. > ========= Yup, here too. But it is not being used. Mark
[toc] | [prev] | [next] | [standalone]
| From | Brian <ad44@cityscape.co.uk> |
|---|---|
| Date | 2016-10-02 15:40 +0200 |
| Message-ID | <snP9L-7va-1@gated-at.bofh.it> |
| In reply to | #173118 |
On Sun 02 Oct 2016 at 21:41:50 +0900, Mark Fletcher wrote: > On Sun, Oct 02, 2016 at 12:52:44PM +0100, Brian wrote: > > > > 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. It shouldn't make any difference whether the split configuration is used or not for what we are doing. A defaults-accepting installation would use "local delivery only; not on a network". Obviously this would not suit testing mail delivery to other machines on the LAN. It was at this first page I made my mistake! I chose "Internet site......" because that is the way I always send mail. No wonder I got "Unrouteable address". Was it clear that I should have used "mail sent by smarthost......" (Liam?)?. Mystery solved. I've not tested extensively but I can get mail to go to a user on another machine. I'm not enamoured of this technique because it does not suit my mail setup. So I will stick with the more versatile hubbed_hosts. Thanks for all the clues. -- Brian.
[toc] | [prev] | [next] | [standalone]
| From | Liam O'Toole <liam.p.otoole@gmail.com> |
|---|---|
| Date | 2016-10-02 17:30 +0200 |
| Message-ID | <snQSd-c2-1@gated-at.bofh.it> |
| In reply to | #173122 |
On 2016-10-02, Brian <ad44@cityscape.co.uk> wrote: > On Sun 02 Oct 2016 at 21:41:50 +0900, Mark Fletcher wrote: > >> On Sun, Oct 02, 2016 at 12:52:44PM +0100, Brian wrote: >> > >> > 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. > > It shouldn't make any difference whether the split configuration is used > or not for what we are doing. > > A defaults-accepting installation would use "local delivery only; not on > a network". Obviously this would not suit testing mail delivery to other > machines on the LAN. It was at this first page I made my mistake! > > I chose "Internet site......" because that is the way I always send > mail. No wonder I got "Unrouteable address". Was it clear that I should > have used "mail sent by smarthost......" (Liam?)?. Mystery solved. I've > not tested extensively but I can get mail to go to a user on another > machine. ยง2.1 of /usr/share/doc/exim4-base/README.Debian.html (from exim4-base) provides some assistance. > > I'm not enamoured of this technique because it does not suit my mail > setup. So I will stick with the more versatile hubbed_hosts. > > Thanks for all the clues. > At least your curiosity has been satisfied. :) -- Liam
[toc] | [prev] | [next] | [standalone]
| From | mo <mo777@gmx.net> |
|---|---|
| Date | 2016-10-01 22:50 +0200 |
| Message-ID | <snzol-5go-5@gated-at.bofh.it> |
| In reply to | #173063 |
Am 01.10.2016 um 18:25 schrieb Liam O'Toole: > On 2016-10-01, mo <mo777@gmx.net> wrote: >> First of all: >> Thank you Liam for your help! :) >> Thanks for the very nice and long explanation Mark! :) >> >> I think i should elaborate a little more on my setup.. i guess i did not >> make that very clear in the first place, sorry about that. >> >> My network is consisting of the following systems: >> >> Main PC - 192.168.23.11 (Running Debian Jessie) >> Server - 192.168.23.200 (Running Debian Jessie) >> >> The server is always online, the PC is only half of the day on. >> >> What i want to do now is the following: >> >> Sending mail from my Main PC to my Server and also the other way around, >> from the Server to my Main PC. >> The Server should also be able to send mail to the "outside" (Meaning to >> other SMTP servers). >> The second requirement is optional since i dont own a domain and all >> this is sitting locally at my home. The most important thing for me is >> to send and receive mail from both systems in my home network. >> I hope this made my problem a little clearer :) >> >> I'm a little ashamed to say that, but i could not totally follow your >> explanations Mark... I'm quite a newbie when it comes to SMTP.. sorry :( >> >> Thanks again for all your help ;) >> >> Greets >> >> mo >> >> > > I should have been a little clearer myself. You don't need to register a > domain name. Just invent your own domain name for local purposes. Let's > say you choose the domain name "monet", and that you have already given > the hostnames "desktop" and "server" to your two machines. Then you > would edit the file /etc/hosts on both machines to contain the following > lines: > > 192.168.23.11 desktop.monet desktop > 192.168.23.200 server.monet server > > Now you only need to tell exim4 on the server that it is the final > destination for emails to *.monet, again using the debconf wizard. You > will then be able to send emails to local addresses, while emails to all > other domains will go through your ISP's smarthost. > > Incidently, you can also tell exim4 on the desktop to use the server as > its smarthost. > > I realise that you're getting lots of (sometimes contradictory) > information from various sources. The barebones configuration I have > described above has served me well for several years. Thanks for the clarification Liam :) > If you add more machines to your network later on you should consider > setting up local DHCP and DNS instead of manually updating /etc/hosts > files. But we'll leave that for another day. :) I think that day will soon come for me :) (I cant live without some playing and fuzzing around :^) )
[toc] | [prev] | [standalone]
Page 3 of 3 — ← Prev page 1 2 [3]
Back to top | Article view | linux.debian.user
csiph-web