> The subject line of this message is clearly wrong.
> 255 of the 821 subscribers to this mailing list use @gmail.com
> mailboxes.
> If there were a problem with gmail, it would have shown up long
> ago.
I have a bit mixed feelings about it. As a coordinator I get regular mail
from gmail users and often experience that my replies do not arrive or get
marked as SPAM. I get reminders about requests that I have already processed,
and sometimes a message "oh sorry I found your reply in the SPAM folder".
At first I blamed my use of an @amsat.org address, and also using that address
as a From: address in my replies. Due to the SPF record on amsat.org it can be
expected that such use leads to marking of mail as suspicious.
So I switched to using another alias service (@vrza.nl being offered by one of
our amateur radio societies), but the situation did not improve. I still get
reports of my mail ending up in the SPAM folder at gmail. But the vrza.nl
domain has no SPF record.
Apparently there is some relation to the user receiving the mail. Some users
receive all my mail without problem, no matter if sent from @amsat.org @vrza.nl
or another source. Others report that it is treated as SPAM for each of those.
Not being a gmail.com user myself, I do not exactly know what features it offers
for whitelisting or other special treatment of mail, or maybe what it learns
automatically. It could be that sending back and forth several mails eventually
leads to an address getting on the whitelist automatically. The same could be
true for mail server IP addresses (like a mailinglist server), and it could be
that knowledge built in the past also affects the results of new SPAM criteria
added later.
It is all a bit opaque, and when you want reliable and predictable mail service,
using those mailservices certainly is not the best choice... or at the least
check the SPAM folder regularly. (but I have also received reports of mail
being dropped and not placed there)
Rob
TL;DR:
In never ending battle against SPAM and phishing attacks, some email
providers are now using DMARC, rejecting or marking as SPAM email if the
originating mail server doesn't match the authorized ones for the
provider's service.
For example:
- Yahoo! is flat out rejecting e-mail from yahoo! mail users if it comes
from non-authorized servers.
- Google is marking e-mail from gmail users as SPAM if it comes from
non-authorized servers.
Unfortunately this breaks mailing list software like mailman (used for this
list) which tries to make e-mail from the list appear as if it is coming
from the original sender.
The changes that are required to fix the issue change the functionality of
the list software in ways users may not like.
I found this out while applying DMARC for my my own domains.
More info can be found at these sites:
https://wiki.list.org/DEV/DMARChttps://dmarc.org/
Fun.
-Neil
--
Neil Johnson
https://news.ycombinator.com/item?id=18407173
Note: I'm NOT advocating anything like that for 44.0.0.0/8.
It's just going to be fun to watch the market for IPv4 address space boom
and then bust when IPv6 adoption finally reaches critical mass.
-Neil, N0SFH
--
Neil Johnson
Hello group,
what can cause ampr-ripd to stay at " waiting for RIPV2 Broadcast".I
opened
the DMZ port of my main routerwhere my raspbery PI is connected. I know the
DMZ work. I tested if from outside.
Any tought?
73 de Jean
--
Sysop de: VE2PKT (BBS), VE2PKT-13 (URONode)
: VE2RCN-1, VE2RGM-1, VE2RGC-1, VE2RVA-1, (The-Net)
: VE2PKT-9 (DXCluster), VE2PKT-10 (Winlink Gateway)
RF:
147.435 Mhz (1200 Bps),
Internet:
Telnet://nodes-ve2pkt.dyndns.org <http://xrouter-ve2pkt.dyndns.org> port 23
(Network Node)
Telnet://fbb-ve2pkt.dyndns.org port 6300 (FBB BBS)
Telnet://ve2pkt.dyndns.org port 9000 (DXCluster)
E-Mail:
packet: ve2pkt(a)ve2pkt.#qbc.qc.can.noam
ampr net: ve2pkt(a)ve2pkt.ampr.org
Inet: ve2pkt(a)gmail.com
Hi! I am kind of new to all this ampr thing. Been following this mailing list and trying to have my setup in a way that will be stable.
I have a vps running openvpn server.
I have an edge router
I want to take my 44 IP address range and distribute them to a port on my edge router but I want to keep my wan/lan configuration as it is and transparent to the 44 range
In what way should I do it?
I am totaly lost.
Hi there
Has someone tried doing A gateway with cellular modem ?
I understand that cellular modems (at least in our country) do few times NAT (carrier-grade nat) and therefore the IP it get is not an IP accessible from the outside world so probably cant do any IPIP to the 44 net router
Is that true ? or is there any solution ?
We dont have IPV6 systems here yet which might overcome this problem only IPV4
any Info on the subject is appreciated
Regards
Ronen -4Z4ZQ
http://www.ronen.org
[http://www.ronen.org/My-QSl.jpg]<http://www.ronen.org/>
Ronen Pinchooks (4Z4ZQ) WebSite<http://www.ronen.org/>
ronen.org (Ronen Pinchooks (4Z4ZQ) WebSite) is hosted by domainavenue.comwww.ronen.org
> Possibly a router not having updated the script to 3.2 after upgrade to
> ROS 6.41 and later.
Yes, that would be the reason for sending MNDP broadcasts.
Actually I don't mind that those are sent, it can be useful as it provides the info
I gave in the first post. But of course it would be nice when system->identity is
changed e.g. to the callsign so it is easier to contact people when something is wrong.
However, the main issue is that it is using a public IP that is not in the gateway list
so these packets cause a log message and are dropped here.
Likely the public IP has changed without the owner noticing it or without him realizing
that he needs to update the portal entry.
(of course this can be avoided when using a DNS name in the portal and some dynamic DNS
update script, or even simply "IP Cloud" when this MikroTik is directly in the public IP)
Rob
Who is running an unregistered gateway at public IP address 72.192.178.228 ? (Cox communications)
It is a MikroTik RB750Gr3 router running 6.42.6 firmware with default identity "MikroTik" broadcasting
MNDP packets to all other gateways, apparently running Marius' ampr-rip script, but the address is not
appearing in the portal. Maybe its address has changed but not updated in the portal?
Rob
This caught my attention on the wetnet list:
https://www.enhancedradio.com/products/hamshield-lora-edition-high-power
For those seeking new ways to move data and ones that exceed what you
can do connected to conventional analog rigs, this is worth looking
into.
Circuit Cellar magazine had a pretty decent multi-part LoRA overview last year.
And if you look on github, Travis, KK4VCZ has some code adapted as a
starting place for ham radio:
https://github.com/travisgoodspeed/loraham
Figured I'd point it out there as it's what we do.
Network Working Group V. Cerf
Request for Comments: 2468 MCI
Category: Informational October 1998
I REMEMBER IANA
October 17, 1998
Status of this Memo
This memo provides information for the Internet community. It does
not specify an Internet standard of any kind. Distribution of this
memo is unlimited.
Copyright Notice
Copyright (C) The Internet Society (1998). All Rights Reserved.
Remembrance
A long time ago, in a network, far far away, a great adventure took
place!
Out of the chaos of new ideas for communication, the experiments, the
tentative designs, and crucible of testing, there emerged a
cornucopia of networks. Beginning with the ARPANET, an endless
stream of networks evolved, and ultimately were interlinked to become
the Internet. Someone had to keep track of all the protocols, the
identifiers, networks and addresses and ultimately the names of all
the things in the networked universe. And someone had to keep track
of all the information that erupted with volcanic force from the
intensity of the debates and discussions and endless invention that
has continued unabated for 30 years. That someone was Jonathan B.
Postel, our Internet Assigned Numbers Authority, friend, engineer,
confidant, leader, icon, and now, first of the giants to depart from
our midst.
Jon, our beloved IANA, is gone. Even as I write these words I cannot
quite grasp this stark fact. We had almost lost him once before in
1991. Surely we knew he was at risk as are we all. But he had been
our rock, the foundation on which our every web search and email was
built, always there to mediate the random dispute, to remind us when
our documentation did not do justice to its subject, to make
difficult decisions with apparent ease, and to consult when careful
consideration was needed. We will survive our loss and we will
remember. He has left a monumental legacy for all Internauts to
Cerf Informational [Page 1]
RFC 2468 I REMEMBER IANA October 1998
contemplate. Steadfast service for decades, moving when others
seemed paralyzed, always finding the right course in a complex
minefield of technical and sometimes political obstacles.
Jon and I went to the same high school, Van Nuys High, in the San
Fernando Valley north of Los Angeles. But we were in different
classes and I really didn't know him then. Our real meeting came at
UCLA when we became a part of a group of graduate students working
for Professor Leonard Kleinrock on the ARPANET project. Steve
Crocker was another of the Van Nuys crowd who was part of the team
and led the development of the first host-host protocols for the
ARPANET. When Steve invented the idea of the Request for Comments
series, Jon became the instant editor. When we needed to keep track
of all the hosts and protocol identifiers, Jon volunteered to be the
Numbers Czar and later the IANA once the Internet was in place.
Jon was a founding member of the Internet Architecture Board and
served continuously from its founding to the present. He was the
FIRST individual member of the Internet Society I know, because he
and Steve Wolff raced to see who could fill out the application forms
and make payment first and Jon won. He served as a trustee of the
Internet Society. He was the custodian of the .US domain, a founder
of the Los Nettos Internet service, and, by the way, managed the
networking research division of USC Information Sciences Institute.
Jon loved the outdoors. I know he used to enjoy backpacking in the
high Sierras around Yosemite. Bearded and sandaled, Jon was our
resident hippie-patriarch at UCLA. He was a private person but fully
capable of engaging photon torpedoes and going to battle stations in
a good engineering argument. And he could be stubborn beyond all
expectation. He could have outwaited the Sphinx in a staring
contest, I think.
Jon inspired loyalty and steadfast devotion among his friends and his
colleagues. For me, he personified the words "selfless service".
For nearly 30 years, Jon has served us all, taken little in return,
indeed sometimes receiving abuse when he should have received our
deepest appreciation. It was particularly gratifying at the last
Internet Society meeting in Geneva to see Jon receive the Silver
Medal of the International Telecommunications Union. It is an award
generally reserved for Heads of State, but I can think of no one more
deserving of global recognition for his contributions.
While it seems almost impossible to avoid feeling an enormous sense
of loss, as if a yawning gap in our networked universe had opened up
and swallowed our friend, I must tell you that I am comforted as I
contemplate what Jon has wrought. He leaves a legacy of edited
documents that tell our collective Internet story, including not only
Cerf Informational [Page 2]
RFC 2468 I REMEMBER IANA October 1998
the technical but also the poetic and whimsical as well. He
completed the incorporation of a successor to his service as IANA and
leaves a lasting legacy of service to the community in that role.
His memory is rich and vibrant and will not fade from our collective
consciousness. "What would Jon have done?", we will think, as we
wrestle in the days ahead with the problems Jon kept so well tamed
for so many years.
There will almost surely be many memorials to Jon's monumental
service to the Internet Community. As current chairman of the
Internet Society, I pledge to establish an award in Jon's name to
recognize long-standing service to the community, the Jonathan B.
Postel Service Award, which will be awarded to Jon posthumously as
its first recipient.
If Jon were here, I am sure he would urge us not to mourn his passing
but to celebrate his life and his contributions. He would remind us
that there is still much work to be done and that we now have the
responsibility and the opportunity to do our part. I doubt that
anyone could possibly duplicate his record, but it stands as a
measure of one man's astonishing contribution to a community he knew
and loved.
Security Considerations
Security issues are not relevant to this Remembrance.
Author's Address
Vinton G. Cerf
MCI
EMail: vcerf(a)mci.net
Cerf Informational [Page 3]
RFC 2468 I REMEMBER IANA October 1998
Full Copyright Statement
Copyright (C) The Internet Society (1998). All Rights Reserved.
This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than
English.
The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Cerf Informational [Page 4]