On 01/10/16 12:39, mo wrote:
Am 01.10.2016 um 13:22 schrieb Brian:On Sat 01 Oct 2016 at 12:36:10 +0200, mo wrote:I just figured out how to get this working myself a week or two back, soit's fresh in my mind. The key trick is the use of "hubbed hosts".Did you follow a specific book or guide?The manual for exim4-config_files is the first place to look.I will look into the manual.I also found a book about exim from O'Reilly, it's quite old (2001) but i guess i can get some info out of it.Exim configuration has the concept of "routers" and "transports". Routers basically decide what to do with a message, and transports do it. One of the routers configured by default in the Debian exim configuration is for "hubbed hosts". What this means, is machinescapable of sending and receiving email ("hosts" in exim speak) that areon the same LAN as this machine (connected by a "hub"). Note that this "hub" could be your local home network router, and for these purposesmachines on WiFi and machines on a wired LAN would be considered on thesame hub, even though that isn't strictly true. The point is that network packets can be addressed directly between the machines, they don't require a router in between.As far as i do understand this is that only machines which are defined as hubbed hosts can be send mail in the local LAN? Or am i misunderstandingsomething here? :)hubbed_hosts can send mail wherever you want. For example: example.com: smtp.example.com would send mail to someone at example.com through smtp.example.com (which could be a smarthost).Got it, thanks ;)In Debian, this is achieved with Avahi. This is what allows you, if youhave MachineA and MachineB on your network, to do for example "ping MachineA.local" from MachineB and expect MachineA.local to be resolved into an IP address.I'm not a friend of avahi to be honest, i much rather ignore it :DLet's hope your IP addresses do not change.No changes here, static network configuration, so that should not pose problems. (My network only has 4 machines, so DHCP is not needed, at least atm i don't need it :) )In /etc/exim4, create a file owned by root called hubbed_hosts. In the file, each line maps a "domain" (the part after the @ sign in an email address) to a "host" (the name of a machine on your network, as it can be reached from this machine). Put the domain first, then a tab character (spaces may also be OK) and then the host. So for example Ihave a machine on my network called affinity, and so in the hubbed_hosts file on the machine I am sitting in front of now, I have two lines, onesaying "affinity.local<TAB>affinity.local", and the other saying "affinity<TAB>affinity.local" (no quotes in the file). This tells the local exim installation that any email address with @affinity.local as the domain should be forwarded on to a machine called affinity.local, and any mail with @affinity as the domain should be forwarded on to a machine called affinity.local. Exim4 will then say "Connect to affinity.local!" with no attempt to translate that into an IP address,and Avahi daemon will answer "that is IP address WW.XX.YY.ZZ!" to whichexim will say "very well, connect to WW.XX.YY.ZZ!" and the exim4 on affinity will wake up and co-operate to deliver the mail.I just did that and now mailing works flawlessly :DJust one questions: Why do i need hubbed_host entries? Should it not be fine alone to make a entry in /etc/hosts for the machines i want to send mail to(I do not operate a dedicated DNS server). This is something i dont really understand...I'd suggest you try it and look at the logs.I will try that out, exim has a pretty nice logging format i think ;)
Hi MoI tried to send this with a .pdf yesterday d'oh! Anyway, we've just reinstalled our servers with mail and automated backup and updated our notes. They're not finalised and hence not on the web yet but you can access them here:
https://dl.dropboxusercontent.com/u/63603283/InstallationNotes2016.9.24.pdf Bit's of it may help. Regards Clive -- Clive Menzies http://freecriticalthinking.org