Re: Outgoing mail server port 587
Dave AA6YQ
-----Original Message-----AA6YQ comments below From: dxlab@yahoogroups.com [mailto:dxlab@yahoogroups.com] Sent: Saturday, January 07, 2017 2:27 PM To: dxlab@yahoogroups.com Subject: [dxlab] Outgoing mail server port 587 Is it possible to use port 587 for the outgoing mail server? 25 and 465 seem to work correctly but 587 fails. 73,That depends entirely on your internet service provider. Dave, AA6YQ
|
|
Re: Email alarm and SQL expression
Dave AA6YQ
-----Original Message-----AA6YQ comments below From: dxlab@yahoogroups.com [mailto:dxlab@yahoogroups.com] Sent: Saturday, January 07, 2017 1:59 PM To: dxlab@yahoogroups.com Subject: [dxlab] Email alarm and SQL expression I am trying to setup email alarms. All work great but I want to make an email alarm trigger for a specific state in US by using an SQL expression. Forgive my SQL ignorance but if that is possible, what would be the correct SQL expression for this? (DXCCID = '291') and (STATE='MA')Using the state of Massachusetts as an example, The first part means "DXCC entity whose country code is 291", where 291 is the country code for the continental US. <http://www.50states.com/abbreviations.htm>MA is the two-letter abbreviation for Massachusetts. Two-letter abbreviations for US states can be found here: DXCCID='6'Alaska and Hawaii are not part of the continental US; for them, use and DXCCID='110' respectively. (DXCCID = '291') and (STATE in ('MA', 'WY', 'NV'))If you're hunting several states in the continental US, say Massachusetts, Wyoming, and Nevada, you can use this format: X in (A, B, C, D, ...)In SQL, the expression (X=A) or (X=B) or (X=C) or (X=D) or ...means 73, Dave, AA6YQ
|
|
Outgoing mail server port 587
Lefteris Tsintjelis
Is it possible to use port 587 for the outgoing mail server? 25 and 465 seem to work correctly but 587 fails. 73 de Lefteri
|
|
Re: e-QSL and LOTW don't follow callsign
Dave AA6YQ
-----Original Message-----AA6YQ comments below From: dxlab@yahoogroups.com [mailto:dxlab@yahoogroups.com] Sent: Saturday, January 07, 2017 7:52 AM To: dxlab@yahoogroups.com Subject: [dxlab] e-QSL and LOTW don't follow callsign EDR is 90 years this year. And we are a group of amateurs working with special calls. DX keeper is very good to this - make a new log database and then I can change identity very easily. But it seems for me, that e-QSL info and maybe also LOTW info don't follow the callsign.If the QSOs you make with your "special call" don't count towards the awards you are pursuing, then recording them in a separate log file is appropriate. If these QSOs do count towards the awards you are pursuing, you should log them in your OZ6GH log, but with their "Station Callsign" items set to OZ7D (your special callsign, I assume). You can do this by changing the default "Station Callsign" to OZ7D on the Defaults tab of DXKeeper's Configuration window. There is no way to automate the setup of a new callsign with either eQSL or LoTW. <http://www.dxlabsuite.com/dxlabwiki/AdditionalEqslAccounts>I'll defer to Rich W3ZJ on how to configure eQSL to properly handle your special callsign, but take a look at 1. request a "callsign certificate" for your special callsign:For LoTW, you must <https://lotw.arrl.org/lotw-help/addcertreq/> 2. when you receive your "callsign certificate", define a "station location" that references it:Be sure to select the correct "situation" in step 3.b <https://lotw.arrl.org/lotw-help/stnloc/#Define> <http://www.dxlabsuite.com/dxlabwiki/LotWMultipleCallsignsLocations>All QSOs in a batch being submitted to LoTW must be made with the same "Station Callsign" over the air so you can select one "Station Location". See 73, Dave, AA6YQ
|
|
Re: Email alarm and SQL expression
Lefteris Tsintjelis
Worked perfect! Thank you. 73
|
|
Re: Email alarm and SQL expression
On Sat, Jan 7, 2017 at 10:58 AM, Lefteris Tsintjelis sv1hfy@yahoo.com
[dxlab] <dxlab@yahoogroups.com> wrote: DXCCPrefix='K' and Primary='NY' or DXCCPrefix='K' and Primary in ('WA','CA','NY') 73, ~iain / N6ML
|
|
Email alarm and SQL expression
Lefteris Tsintjelis
I am trying to setup email alarms. All work great but I want to make an email alarm trigger for a specific state in US by using an SQL expression. Forgive my SQL ignorance but if that is possible, what would be the correct SQL expression for this?
Thank you
|
|
Spotspy
W0MU
If you are looking for a spotting tool for POTA and WWFF spotspy is
great! Works like a charm and is quite flexible and will do much more than these awards. W0MU
|
|
Re: PU1RTP - Carlos (Error Date in DXKeeper)
Dave AA6YQ
Carlos, your original post began with
toggle quoted messageShow quoted text
TQSL Version 2.0.1 [v2.0.1] There is no need to uninstall anything. As Joe W4TV suggested, just install TQSL 2.3. 73, Dave, AA6YQ
-----Original Message-----
From: dxlab@yahoogroups.com [mailto:dxlab@yahoogroups.com] Sent: Saturday, January 07, 2017 6:58 AM To: dxlab@yahoogroups.com Subject: RES: [dxlab] PU1RTP - Carlos (Error Date in DXKeeper) Please, Firstly should I uninstall Trusteer QSL v2.3 and then install again? Thank you 73 !! PU1RTP – Carlos De: dxlab@yahoogroups.com [mailto:dxlab@yahoogroups.com] Enviada em: sábado, 7 de janeiro de 2017 01:44 Para: dxlab@yahoogroups.com Assunto: RE: [dxlab] PU1RTP - Carlos (Error Date in DXKeeper) -----Original Message-----AA6YQ comments below From: <mailto:dxlab@yahoogroups.com> dxlab@yahoogroups.com [ <mailto:dxlab@yahoogroups.com> mailto:dxlab@yahoogroups.com] Sent: Friday, January 06, 2017 9:56 PM To: <mailto:dxlab@yahoogroups.com> dxlab@yahoogroups.com Subject: RES: [dxlab] PU1RTP - Carlos (Error Date in DXKeeper) Sorry, Dave. But the thing happened was that I had a certificate for a long time, but I made the mistake of asking for another and filled in the wrong date (see image below). Now I do not know how to fix the date to enter the previous QSO's. What should I do? Thank you. 73, PU1RTP. Use these instructions:Request a new "Callsign Certificate", specifying the correct QSO dates. < <https://lotw.arrl.org/lotw-help/certreplace/> https://lotw.arrl.org/lotw-help/certreplace/> Note steps 5.a.3 and 5.a.4. 73,If you upgrade to TQSL 2.3, you'll have the documentation in Portuguese. Dave, AA6YQ --- Este email foi escaneado pelo Avast antivírus. https://www.avast.com/antivirus [Non-text portions of this message have been removed] ------------------------------------ Posted by: "Teixeira" <carlos.teixeira@terra.com.br> ------------------------------------ ------------------------------------ Yahoo Groups Links
|
|
Re: Italian province missing
Dave AA6YQ
-----Original Message-----AA6YQ comments below From: dxlab@yahoogroups.com [mailto:dxlab@yahoogroups.com] Sent: Saturday, January 07, 2017 6:28 AM To: dxlab@yahoogroups.com Subject: [dxlab] Italian province missing In dxkeeper I don't find Cagliari (CA) between the Italian provinces. This is an oversight or something? 73,Cagliari is in Sardinia, which ARRL and CQ award programs consider to be a country that is distinct from Italy. Dave, AA6YQ
|
|
Re: RES: PU1RTP - Carlos (Error Date in DXKeeper)
Joe Subich, W4TV
Firstly should I uninstall Trusteer QSL v2.3 and then install again?No. Simply follow the procedure to renew the bad callsign certificate but specify the *correct* start date. Once you have submitted the "renewal" *do not* attempt to sign and upload any QSOs until you have received the "renewal". 73, ... Joe, W4TV On 1/7/2017 6:57 AM, 'Teixeira' carlos.teixeira@terra.com.br [dxlab] wrote: Please,
|
|
e-QSL and LOTW don't follow callsign
Gorm Helt-Hansen
Hi.
EDR is 90 years this year. And we are a group of amateurs working with special calls. DX keeper is very good to this - make a new log database and then I can change identity very easily. But it seems for me, that e-QSL info and maybe also LOTW info don't follow the callsign. Clublog is, as far I can see, ok. I entered e-QSL info while I was OZ7D. When I changed back to my normal call, OZ6GH, the e-qsl info remained for OZ7D. I then entered my e-QSL data when I was OZ6GH and when I changed to OZ7D, my OZ6GH data showed up under OZ7D. I had not tried LOTW, but it seems the problem is the same here. My OZ6GH data don't change og disappear when I change to OZ7D. Club Log follows the callsign. Have I overlooked something, pse? 73 de Gorm / OZ6GH.
|
|
Re: Commander not talking to other apps, DXLabLauncher not working anymore
Alex OE3JTB
So I found out for myself run PSTROTATOR as administrator and now it works fine 73 Alex
|
|
RES: PU1RTP - Carlos (Error Date in DXKeeper)
Teixeira
Please,
Firstly should I uninstall Trusteer QSL v2.3 and then install again? Thank you 73 !! PU1RTP – Carlos De: dxlab@yahoogroups.com [mailto:dxlab@yahoogroups.com] Enviada em: sábado, 7 de janeiro de 2017 01:44 Para: dxlab@yahoogroups.com Assunto: RE: [dxlab] PU1RTP - Carlos (Error Date in DXKeeper) -----Original Message-----AA6YQ comments below From: <mailto:dxlab@yahoogroups.com> dxlab@yahoogroups.com [ <mailto:dxlab@yahoogroups.com> mailto:dxlab@yahoogroups.com] Sent: Friday, January 06, 2017 9:56 PM To: <mailto:dxlab@yahoogroups.com> dxlab@yahoogroups.com Subject: RES: [dxlab] PU1RTP - Carlos (Error Date in DXKeeper) Sorry, Dave. But the thing happened was that I had a certificate for a long time, but I made the mistake of asking for another and filled in the wrong date (see image below). Now I do not know how to fix the date to enter the previous QSO's. What should I do? Thank you. 73, PU1RTP. Use these instructions:Request a new "Callsign Certificate", specifying the correct QSO dates. < <https://lotw.arrl.org/lotw-help/certreplace/> https://lotw.arrl.org/lotw-help/certreplace/> Note steps 5.a.3 and 5.a.4. 73,If you upgrade to TQSL 2.3, you'll have the documentation in Portuguese. Dave, AA6YQ --- Este email foi escaneado pelo Avast antivírus. https://www.avast.com/antivirus [Non-text portions of this message have been removed]
|
|
Italian province missing
raoul_gi
In dxkeeper I don't find Cagliari (CA) between the Italian provinces. This is an oversight or something?
Thanks. Raoul, ik0rcy
|
|
Re: Commander not talking to other apps, DXLabLauncher not working anymore
Alex OE3JTB
Hi Dave
ok I will try also there tnx 73 Alex
|
|
Re: Commander not talking to other apps, DXLabLauncher not working anymore
Dave AA6YQ
Then you should engage the author of PSTRotator to determine what's going on. That's Codrut YO3DMU, via
toggle quoted messageShow quoted text
codrut.buda (at) rdslink.ro 73, Dave, AA6YQ
-----Original Message-----
From: dxlab@yahoogroups.com [mailto:dxlab@yahoogroups.com] Sent: Saturday, January 07, 2017 2:51 AM To: dxlab@yahoogroups.com Subject: [dxlab] Re: Commander not talking to other apps, DXLabLauncher not working anymore Hello Dave yes no problem between the DXLAB apps, also WSJT-X is give the information to PSTRotator. 73 Alex
|
|
Re: Commander not talking to other apps, DXLabLauncher not working anymore
Alex OE3JTB
And I did exceptions in the firewall for commander, viewer etc..
|
|
Re: Commander not talking to other apps, DXLabLauncher not working anymore
Alex OE3JTB
Hello Dave
yes no problem between the DXLAB apps, also WSJT-X is give the information to PSTRotator. 73 Alex
|
|
Re: Commander not talking to other apps, DXLabLauncher not working anymore
Dave AA6YQ
Alex, are your DXLab applications correctly interoperating?
toggle quoted messageShow quoted text
73, Dave, AA6YQ
-----Original Message-----
From: dxlab@yahoogroups.com [mailto:dxlab@yahoogroups.com] Sent: Saturday, January 07, 2017 2:23 AM To: dxlab@yahoogroups.com Subject: [dxlab] Re: Commander not talking to other apps, DXLabLauncher not working anymore Good morning I have Windows 10 64 Version 1607 (build 14393.576) but I have the same issue. PSTRotator doesnt track. I disabled defender ans the firewall for testing, nothing changed Anything else I can try? tnx for your advice 73 Alex, OE3JTB
|
|