| 
										 Looking for some gentle nudges in the right direction... I'm tinkering with on-mesh, mesh-only email.  I envision a regional or nationwide mesh that will one day have email capability.  Towards this end I built two raspberry pi email servers using information from http://www.samhobbs.co.uk/raspberry-pi-email-server.  I used only the first two tutorials and did not include the SSL/TLS capabilities.  Both Raspberry pi have names (nwf.local.mesh and fwb.local.mesh), they are attached to separate mesh nodes and I can connect to either one of them using the IP or the name without issue.  I can set up a mail client that can receive mail and I can connect to both smtp servers on the mesh to send email.  The problem I'm having is when one mail server attempts to connect to the other.   My Mesh Configuration: (RF)-[N2XU-First]-cat5-[RasPi: fwb.mesh.local] (RF)-[N2XU-Second]-cat5-[RasPi: nwf.local.mesh] If I attempt to log onto fwb as pi@fwb.local.mesh and send mail from pi@fwb.local.mesh to pi@nwf.local.mesh on the other server the log says it can't find a MX for nwf.local.mesh. The email does show in the sent folder but never arrives in the pi@nwf.local.mesh inbox on the other server.  Apparently it's doing a DNS lookup for the MX record of the other server.  Is there a way to include MX records in the DNS records on the mesh nodes that will propagate across the mesh.  I just encountered this a little while ago and did a search here on the forum for MX and didn't get any results. I don't believe that everyone will run an email server, but I do believe that there could and should be at least one somewhat local in each area... maybe by county, or region of a state.  Has anyone else experimented with mesh only email with more than one email server? Thanks. Tom
  									 |