Dont like to cross post, but I dont know how this topic can be said any better than what is listed below. With out an independent internet or wireless network to span our coverage needs to support our cause, and this isnt going to happen, these issues are not going to go way.
However, it must be noted that all the on the air systems working now can be used to establish links to get early event communications out for setting up other modes of communications, such as normal voice to voice schedule arrangements. Thus it is important that all groups and individual users that wish to support emergency activities have as many of the options available as possible (or access to them and know how to use them), so those limited in emergency area's have something to start out with before moving on to activities that suit the situation and time. Get good at using what we got the way it currently works, or it is all a big waste. Many are dedicated to making what we have work, work better, and evolve over time. 73 from Bill - WD8ARZ http://hflink.net/qso/ ----- Original Message ----- From: "Rick Muething" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, August 06, 2008 4:33 PM Subject: RE: [wl2kemcomm] Re: Email delivery time Vic confirmed the current code tries 8 times in a 4 hour period once ever 30 minutes. Until and unless there is a general standard used by mail servers trying to chase the latest ad-hoc anti spam technique is a significant burden on our very limited programming resources. Shortening to 5 minute attempts for 4 hours (48 tries) could increase the load on the server's significantly especially when there are so many very sluggish servers (e.g. AOL, Hotmail etc) that often take minutes to respond after accepting the initial start of the mail forwarding sessions. If your ISP is blocking mail waiting for multiple retries as a means of trying to control SPAM that is an issue to take up with the ISP. One thing you learn after being in this effort for long is there are continual changes in techniques for SPAM filtering but often these are met by just more aggressive and sophisticated SPAM bots with little real gain in the end. Rick KN6KB From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of n8gfo Sent: Wednesday, August 06, 2008 3:08 PM To: [EMAIL PROTECTED] Subject: [wl2kemcomm] Re: Email delivery time --- In [EMAIL PROTECTED], "Rick Muething" <[EMAIL PROTECTED]> wrote: > > Vic would have to confirm this.there may have been recent changes but it > used to try hourly for up to 8 hours. Remember that Winlink delivers each > recipients mail (each addressee) independently so a failure or delay with > one address doesn't affect any others in the message. Can this be shortened to maybe 10 minutes or even 5 with enough attempts to make it a 4 or 5 hour total? So many servers are using this transient failure spam "filtering" and it is only going to get worse as time goes on. Having to wait a half an hour to get an email through makes it hard to hold a real-time exercise, much less a real-time emergency. It is also a hinderance to teaching people how to use the system, when they send email to themselves at their ISP address and it goes out but apparently doesn't arrive. I just went through this with someone who was learning packet/airmail from the ground up and it would have helped for him to see success faster. Thanks for your consideration in this.
