I'm sending this out to the mailing list as well as directly to ampr.org subscribers. There's a problem involving linux-hams subscribers who have an ampr.org email address subscribed that I've noticed from my bounce messages. When a message is sent to a vger mailing list, vger sends that message first out to a number of exploder sites, which then attempt direct delivery of the message. This is so that vger doesn't get bogged down trying to do delivery to the list members directly, many of whom may be unreachable at any given point in time. The exploder machine is essentially chosen based on the domain of the subscriber, ie, all aol.com addresses are tried by one machine, all webtv.com addresses by another. The problem is that the machine that handles ampr.org (or more likely, .org, although I'm not sure of that) is set to only attempt delivery for around 3 hours before bouncing the message. That's enough for most systems, but given that ampr.org addresses are often behind radio links which may be slow and/or intermittent, that presents a problem. I've dropped a note on the mailing list for vger mailing list owners, as well as to the postmaster of the exploder site in question, and I'm going to try and have the limit increased, or ampr.org moved to a different exploder with less rigid delivery standards. In the mean time, ampr.org subscribers may miss some email from the list. I would suggest that if you are an ampr.org subscriber, and you don't have a host on the Internet willing to queue email up for you, that you try and find one, and set up an MX record to point to that machine so that if your ampr.org machine is unavailable, it will still get delivered to that Internet host, who will then deliver the messages to you when you are reachable again. I apologize for any inconvience this may have caused, and I'm trying to get it resolved. Bob N2KGO listowner, linux-hams
