44net

44net@mailman.ampr.org

3194 discussions

Start a nNew thread

201408231824
by Marc, LX1DUC 23 Aug '14

23 Aug '14

lx044-18 add a 212.83.138.143

1 0

Re: [44net] TAPR DCC 2014?
by Bryan Fields 20 Aug '14

20 Aug '14

On 8/20/14, 2:51 AM, Brian Kantor wrote: > Sounds like a plan. I think Friday evening is unscheduled at this > point so maybe we can meet and grab some drinks and food. ok, I'll figure out something. Anyone have any thing they won't eat/keep kosher/etc.? -- Bryan Fields 727-409-1194 - Voice 727-214-2508 - Fax http://bryanfields.net

1 0

Re: [44net] TAPR DCC 2014?
by Bryan Fields 20 Aug '14

20 Aug '14

On 8/20/14, 12:57 AM, Brian Kantor wrote: > I'll be there Thurs evening thru Sunday morning. We should do a 44net get together/dinner/drinks/etc. kinda thing. Anyone up for it? -- Bryan Fields 727-409-1194 - Voice 727-214-2508 - Fax http://bryanfields.net

3 2

Re: [44net] TAPR DCC 2014?
by Bryan Fields 20 Aug '14

20 Aug '14

I just booked Sep 5-7 TPA-AUS for $250 on AA. I'll be there, but staying down the road at a Hilton. I'm landing at 12:40 on the 5th and leaving at 1pm on Sunday, it's all I could fit into my schedule. Anyone else coming? -- Bryan Fields 727-409-1194 - Voice 727-214-2508 - Fax http://bryanfields.net

2 1

Interesting tid-bit
by John D. Hays 13 Aug '14

13 Aug '14

I experienced this yesterday. http://www.zdnet.com/internet-hiccups-today-youre-not-alone-heres-why-70000… ------------------------------ John D. Hays K7VE PO Box 1223, Edmonds, WA 98020-1223 <http://k7ve.org/blog> <http://twitter.com/#!/john_hays> <http://www.facebook.com/john.d.hays>

1 0

Re: [44net] SMTP port 25
by kb9mwr＠gmail.com 13 Aug '14

13 Aug '14

Okay I have my network issues resolved. I had to implement policy based routing to get things work consistently. I was able to receive mail successfully too. Onward and upward!

1 0

Re: [44net] SMTP port 25
by kb9mwr＠gmail.com 13 Aug '14

13 Aug '14

Actually what I said doesn't make any sense. I don't understand where the problem is. I'd still like to hear from anyone running a SMTP server on Linux, not NOS.

4 3

Re: [44net] SMTP port 25
by kb9mwr＠gmail.com 13 Aug '14

13 Aug '14

I was going to run a pipermail email list on a 44 IP. While I am sure I can get it to work fine between other 44 hosts, my guess is that it will see little use if I can't make it work like any other host on the wide internet. The latest problem again is with outside connectivity. There seems to be some sort of TTL issue going on. My network /host isn't always reachable from the internet. And it seems to depend on who you are using for internet. My host: 44.92.21.35 Seems to work fine from a time warner cable connection in Green Bay. But other people report not being able to reach it. Looking at other 44net hosts connected to the internet: pinging 44.88.0.9 - Fine pinging 44.4.92.50 yes but with packet loss So it turns out a lot of my SMTP headaches track back to this bigger problem.

1 0

Re: [44net] SMTP port 25
by lleachii＠aol.com 13 Aug '14

13 Aug '14

- Are you willing to establish an email server and be willing to maintain it? - Who would be responsible for maintaining the accounts? - Do you have a privacy policy in place? - What is your ISP's bandwidth limit? - Do you have the facilities to backup and store emails for all users? - The same DNS entries would be required, and the ampr.org domain (or subdomain) would have to be the only one used. -KB3VWG > At the very least shouldn't AMPRnet folks be able to send and receive > email from other AMPRnet stations? I'd think that would be a good > first step for dealing with EMail. A bit easier and safer than > dealing with the whole Internet. > Bill

4 4

Re: [44net] SMTP port 25
by lleachii＠aol.com 12 Aug '14

12 Aug '14

Steve, I have ran mail servers, but I do not currently run one on AMPRNet; my last attempt was to setup a home server was an IPv6-only server for the purposes of passing a certification exam. There are many reasons for not maintaining it (some of which may be why you're having issues, hope this helps): - The domain you're using for email must have an MX record - That MX record must point to a valid A Record (it doesn't have to be the same domain) - Your mail server must be configured with the hostname name noted in the A Record - The IP noted in the A record must have a PTR record that returns the same hostname in the A Record (this can only be done by one of our friendly Brians, this has to be done in 44.in-addr.arpa) also make sure that - you have configured the SMTP server to receive email for the domain in which you created a global MX record entry - make sure that email account exists on the server - if it is multi-homed, make sure the gateway/default route is over 44NET While mail servers should work with the first two, many ISPs configure their servers only to "talk" with mail servers who also have the PTR record in place. -Lynwood KB3VWG

2 2

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

44net