> Quick question as to what methods you guys are using to "send in
> exceptions" Is there a way of contacting hotmail support that doesn't
> involve an endless loop of "we see no problems" with their tier 1 techs?
I would say the contact with support should be made by the hotmail subscriber.
They can claim they don't receive their important mail and want that situation
rectified. They have a customer relation with hotmail.
My experience is that contacting services where you are not a customer yourself
is usually very difficult and will often not result in any action.
> FYI I do already have SPF, PTR and DMARC records published in DNS which
> has ensured reliable delivery to gmail addresses, but hotmail seems to
> have their own internal scoring system
Another problem is that hotmail uses a cache for SPF and DMARC and it takes
very long to expire. I have seen mail problems in hotmail at least a month
after an SPF record was changed to include more valid addresses, and they were
still considered invalid (resulting in postmaster report via DMARC info).
Rob
We're having some problems with 44net email to and from
hotmail.com. Mail from that domain is getting delayed,
sometimes for hours, and mail going to addresses in that
domain is received by the server but not delivered to the
users mailbox.
I think I've fixed the delay problem by adding more IP addresses
to the greylister 'whitelist', but I don't know of anything
I can do about the delivery problem.
- Brian
Greetings everyone!
I would like to first say that i am new to the Mailing list and this is
my first email on this list.. If you wish to learn more about me and ham
radio you can visit http://kc9zhv.com or http://lorentedford.com
Technology wise i am involved heavily in Gaming Live Streaming and I
rent a Rack Server from SoYouStart out of Canada a derivative of OVH
Data Centers. I am curious if it is possible to route a /27 of ips to
one single static ip from my web and email server that also handles my
routing vpn services and many other things.. I use a specialized distro
called Neth Server I am particularly running on Neth 6.8 for reliability
reasons basically Centos or Red Hat distro..
So i suppose in closing how does everyone else route ip's around? Do you
rent a server like i do and point it at the ip? I know in my Data center
I have 14 dedicated public ipv4 ips to my disposal.
Also will they issue a /24? If so I could use it not only in combination
with my 14 Allstarlink nodes but handle some of my echolink servers and
stuff as well.. Maybe put up some Echolink Proxies for others to use its
not like that takes up any processing power in Linux environment..
Anyway thanks for the time 73 for now
--
Loren Tedford (KC9ZHV)
Phone:618-553-0806
Fax: 1-618-551-2755
Email: lorentedford(a)gmail.com
Email: KC9ZHV(a)KC9ZHV.com
http://www.lorentedford.comhttp://www.kc9zhv.comhttp://forum.kc9zhv.comhttp://hub.kc9zhv.comhttp://Ltcraft.nethttp://voipham.com
***************************************************
CONFIDENTIALITY NOTICE: Confidential information, such as identifiable
patient health information or business information, is subject to
protection under state and federal law. If you are not the intended
recipient of this message, you may not disclose, print, copy or disseminate
this information. If you have received this in error, please reply and
notify the sender (only) and delete the message. Unauthorized interception
of this e-mail is a violation of federal criminal law.
**************************************************
> We're having some problems with 44net email to and from
> hotmail.com. Mail from that domain is getting delayed,
> sometimes for hours, and mail going to addresses in that
> domain is received by the server but not delivered to the
> users mailbox.
I sometimes have similar problems with gmail.com. I send replies to
allocation requests to the user's gmail address and they never receive
it, and become impatient and repeat the request. Sometimes I can fix it
by using a different sender mail address.
It looks like those big guys (who of course get billions of spam messages
a day) use a lot of sender profiling and low-volume senders like @amsat.org and
@*.ampr.org get low in their reputation score. So with a *.ucsd.edu sender
address you had a quite higher reputation score. Mentioning IP addresses in
the mail body does the rest. (often considered an indication of spam)
Rob
All,
The DNS servers that I copied the zones AMPR.ORG and 44.IN-ADDR.ARPA
from, are no longer responding.
My DNS server at 44.60.44.3 (dns-mdc.ampr.org) is still up and available
for client DNS resolution; but the AMPR.ORG and 44.IN-ADDR.ARPA zones
are no longer local copies.
Just an FYI. If anyone else is running DNS, ensure that your AMPR.ORG
and 44.IN-ADDR.ARPA zones are up-to-date.
73,
- Lynwood
KB3VWG
> At the cost of sacificing the independence and survivability of the
> mesh structure that is the current AMPRNet, one or more central v4 to
> v6 gateways could be established. I believe it would be too much to
> expect each of the 600 or so subnet gateways to become "dual-stacked".
I will certainly consider adding IPv4-over-IPv6 tunneling to our gateway for 44.137.0.0/16
when there is demand for it. We are already IPv6-connected but at the moment this is
only used for out-of-band management (to prevent locking myself out of the system when
doing work on the complicated IPv4 routing and firewall)
Of course that would indeed mean it is not meshed over IPv6 but of course it still
participates in the IPv4 mesh.
When there is sufficient uptake in other parts of the world, additional meshing over
IPv6 could be considered. I agree that some method, preferably an internet standard,
should be used to disseminate IPv6 tunnel information. It would decrease the difficulty
of adding a gateway for those that e.g. want to use surplus commercial routers.
Rob
It's been interesting going over historical documents, RFCs, and some
personal correspondence with people who were involved with the AMPRNet
at various times. I think we've now got a pretty good picture of the
history of the AMPRNet up to the current day.
Let me recap the history as I know it:
In 1981, Hank Magnuski, KA6M, got the network with a phone call to Jon
Postel at USC-ISI, later the SRI-NIC.
Around 1983, Hank passed it on to Phil Karn (KA9Q), then at BellCoRe.
Phil managed it until he left to go to work at Qualcomm in San Diego,
and gave it to Wally Linstruth (WA6JPR) [RIP 2010]. Phil is now retired,
and continues to be involved with AMPRNet.
Around 1988, Wally passed the network on to me to manage, and I've been
doing so ever since.
In 2011, it seemed wise to legally formalize the ownership, so we
incorporated our organization, Amateur Radio Digital Communications
(ARDC), as a non-profit 501(c)(3) tax-exempt charitable organization,
and I became its president.
The American Registry of Internet Numbers (ARIN) and Internet Assigned
Numbers Authority (IANA), which are the authority in these matters,
recognizes us (ARDC) as the legal owner of the AMPRNet, 44.0.0.0/8.
If there's any corrections needed in the above brief history, please
let me know.
- Brian
