44net

44net@mailman.ampr.org

1 participants
3194 discussions

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

12 Aug '14

Thanks for the explanation Tim. I haven't messed with running a mail server since 1999 so a lot has apparently changed, and I am a bit concerned about doing it right. Presently I am trying trying exim on a CentOS platform. It seems to send out mail just fine, but when it comes to answering someone else connecting to it from the general internet that is were I apparently don't have something configured right yet. Anyone care to create a nice write up :-)

3 2

Re: [44net] SMTP port 25
by William Lewis 12 Aug '14

12 Aug '14

I found that Comcast only blocks "Residential" subscribers from port 25. The minute I upgraded to a "Commercial" account, all restrictions were removed. The best part was that for a commercial account with one dedicated IP address, it was cheaper than the residential service was. Not sure this approach will work for all though. Bill KG6BAJ At 05:39 PM 08/11/14, you wrote: >(Please trim inclusions from previous messages) >_______________________________________________ >Is anyone running a SMTP server on their gateway? > >Most ISP's block port 25 outgoing, the problem I am seeing.

1 0

Re: [44net] SMTP port 25
by Jason Begley 12 Aug '14

12 Aug '14

What ISP are you using. Most do block outbound 25. ATT will unblock if you get the right person on the phone. KY9J -------- Original message -------- From: kb9mwr(a)gmail.com Date: 08/11/2014 8:50 PM (GMT-05:00) To: 44net(a)hamradio.ucsd.edu Subject: Re: [44net] SMTP port 25 (Please trim inclusions from previous messages) _______________________________________________ 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. _________________________________________ 44Net mailing list 44Net(a)hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net

1 0

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

12 Aug '14

Turns out you have to specify the interface address for sendmail to respond to, 127.0.0.1 is default so that is why that always worked. I never ran into that one before, That explains this weirdness.. Two boxes on my local LAN with no iptables software firewalls or hardware firewalls between them, and selinux off on both: [root@kb9mwr ~]# ifconfig eth0 eth0 Link encap:Ethernet HWaddr 00:21:85:9C:60:42 inet addr:192.168.1.100 Bcast:192.168.255.255 Mask:255.255.0.0 inet6 addr: fe80::221:85ff:fe9c:6042/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:5421757 errors:0 dropped:0 overruns:0 frame:0 TX packets:4042659 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:1012253009 (965.3 MiB) TX bytes:2506193160 (2.3 GiB) Interrupt:58 Base address:0xe000 [root@kb9mwr ~]# telnet localhost 25 Trying 127.0.0.1... Connected to localhost.localdomain (127.0.0.1). Escape character is '^]'. 220 kb9mwr.host.org ESMTP Sendmail 8.13.8/8.13.8; Mon, 11 Aug 2014 19:59:42 -0500 ^] telnet> root@pbx:~ $ telnet 192.168.1.100 25 Trying 192.168.1.100... telnet: connect to address 192.168.1.100: Connection refused telnet: Unable to connect to remote host: Connection refused I was well aware that most ISP's block that port but was really stumped as to why to PC's on the same network could not talk to each other on that port yet could on all other ports. You learn something new every day.

2 1

SMTP port 25
by kb9mwr＠gmail.com 12 Aug '14

12 Aug '14

Is anyone running a SMTP server on their gateway? Most ISP's block port 25 outgoing, the problem I am seeing. I see a email handshake come in and forward over the wireless LAN, But when it comes from a non 44 IP is tries to reply using my assigned ISP provided IP and obviously that doesn't work. So is there some way with IP tables or something else to set and advanced IP rule where is it's a destination on port 25 to route thru amprgw.sysnet.ucsd.edu using my 44 address?

2 1

Re: [44net] 44Net Digest, Vol 3, Issue 131
by Ernest.Tse＠Pacswitch 12 Aug '14

12 Aug '14

An embedded and charset-unspecified text was scrubbed... Name: not available URL: <http://hamradio.ucsd.edu/mailman/private/44net/attachments/20140812/5319c5f…>

1 0

URONode on Summer 2014 issue of TAPR PSR
by Dimitrios Valaris 09 Aug '14

09 Aug '14

Hi all, I just received the "Summer 2014 issue of TAPR PSR" and saw a nice article about UROnode in page 5. Congrats to Brian N1URO. It is the best NODE software I have ever used. --- 73 de Demetre - SV1UY e-mail: demetre.sv1uy(a)gmail.com Radio e-mail: sv1uy(a)winlink.org AMPRnet e-mail: sv1uy(a)sv1uy.ampr.org PACKET mail: SV1UY(a)SV1UY.ATH.GRC.EU WEB: http://www.qsl.net/sv1uy

2 4

testing for source address filtering....
by Eric Fort 08 Aug '14

08 Aug '14

Occasionally I have access to 2 Verizon DSL connections in the same location. the connections while being the same provider are generally a dynamic IP from different /24 subnets and there's about 4 hops between them. (once they reach a common point a couple hops away all other traceroute data is the same. how can I test to see if one connection filters source addresses belonging to the other? (and any guesses as to what the results may be?) Eric

2 1

Re: [44net] 44Net Digest, Vol 3, Issue 128
by Ernest.Tse＠Pacswitch 08 Aug '14

08 Aug '14

An embedded and charset-unspecified text was scrubbed... Name: not available URL: <http://hamradio.ucsd.edu/mailman/private/44net/attachments/20140808/2f26caa…>

1 0

Re: [44net] Performance of DNS
by Rob Janssen 07 Aug '14

07 Aug '14

44net-request(a)hamradio.ucsd.edu wrote: > Subject: > Re: [44net] Performance of DNS > From: > David Ranch <amprgw(a)trinnet.net> > Date: > 08/07/2014 03:04 AM > > To: > AMPRNet working group <44net(a)hamradio.ucsd.edu> > > > > Beyond filtering, are you looking at your named logs too? There are a ton of old / misconfigured DNS servers out there that don't support EDNS: > > success resolving 'blns71.spamcop.net/A' (in 'spamcop.net'?) after disabling EDNS success resolving 'bcwww.enet.cu/A' (in 'enet.cu'?) after reducing the advertised EDNS UDP packet size to 512 octets > > success resolving 'hispructs.com/A' (in 'hispructs.com'?) after reducing the advertised EDNS UDP packet size to 512 octets I recognize that problem but it is not occurring on this server. Probably the ampr.org nameservers are not affected by that, and the machine does not make many other queries. The only recurring error messages are about IPv6 DNS server addresses being unreachable, but only one or two a day. I have now started it with -4 option but it will probably not change much. Also disabled dnssec. Let's see... Rob

1 0

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

44net