|Joined:||Sat, May 14th 2011, 20:53||Total Topics:||0||Roles:||N/A|
|Last Login:||Never||Total Posts:||0||Moderates:||N/A|
|RTTY Procedure Guide||Dec 11th 2012, 23:26||4||584||on 16/1/13|
|Looking for an old QSL Card - K4IBJ||Oct 31st 2012, 17:50||1||479||on 31/10/12|
|Electronic QST problems on Linux||May 23rd 2012, 18:29||10||1,302||on 17/11/12|
|WAS Forum||Mar 30th 2012, 01:35||4||948||on 19/6/12|
|ARRL mail forward problem.||WB7OUT||2 weeks, 4 days ago|
I've seen round trip times as short as 50 seconds when sending test messages to my @arrl.net address. Today I saw a round trip time that was a bit longer; a little over 6 minutes.
The delay occurred because an SMTP delay when my border mail-server tried to deliver to the ARRL mail-server. Here's the relevant extract from my logs (I've altered the hostnames/addresses):
2013-05-07 12:50:07 1UZhGT-000Lkd-3W SMTP timeout while connected to
after initial connection: Operation timed out
2013-05-07 12:50:07 1UZhGT-000Lkd-3W == email@example.com R=dnslookup T=remote_smtp defer (60):
Operation timed out: SMTP timeout while connected to
neeyzk1oe.rqtrav.arg [aaa.bbb.ccc.ddd] after initial connection
2013-05-07 12:52:25 1UZhGT-000Lkd-3W => firstname.lastname@example.org R=dnslookup T=remote_smtp
2013-05-07 12:52:25 1UZhGT-000Lkd-3W Completed
The delivery times and mail servers are also visible in the Received: headers in each message. Most mass market "e-mail clients" make these headers difficult to view, but they are there.
A delay of over 4 hours is not surprising when you understand the SMTP (Simple Mail Transport Protocol) retry mechanism. What usually happens is that a mail-server will schedule a couple of delivery attempts at 15 to 30 minute intervals and then start increasing the delay geometrically each time there is a further delivery failure; the maximum retry interval is typically between 6 and 12 hours.
So if a message is not delivered within the first hour then the next retry will be a 2 hours, then 4 hours, etc., until the message is 96 hours (4 days) old.
|ARRL mail forward problem.||WB7OUT||3 weeks ago|
The only way to know for sure what happened is to see the complete message headers (especially the Received: headers).
Please contact me at email@example.com if you would like me to take a look at that problem message.
|LOTW Complaints||W4RIG||on 24/4/13|
Did you go through the intial postcard process?
Did you run TrustedQSL to generate your certificate request?
Did you manually e-mail the certificate request (TQ5) file as an attachment to firstname.lastname@example.org or upload it at https://p1k.arrl.org/lotw/upload?
Once you complete those steps you will receive an e-mail containing the username and password you need to log-in to LoTW along with the certificate that you need to install in to TrustedQSL.
|LOTW Complaints||W4RIG||on 27/2/13|
https://p1k.arrl.org/lotwuser/default was up for me when I just tried it.
Your LoTW username and password are in the e-mail (from the ARRL) containing your signed certificate.
|My license, printed one is ok?||Bart_KJ6BWB||on 18/2/13|
|Have you tried asking your local license plate issuing authority?
If you need a duplicate license visit http://wireless.fcc.gov/uls and click the "Log In" button next to "Online Filing" to use the License Manager. You will need your FRN and the associated password to log-in. There are links on the License Manager log-in page to help you recover the password associated with your FRN.
Once you're in the License Manager click the "Request Duplicates" link under "My Licenses" in the menu on the left side of the page to request a duplicate copy of your license.