Я работаю с двух QTH (город и загородный дом), в будни -- в городе, по выходным за городом. Получается, что для каждой смены локации мне нужно создавать новый профиль eQSL с новым Nickname?
Т.е. в результате получится необходимость вручную проверять INBOX на множестве профилей? (то, что нужно в ПО журнала завести соответствующее количество локаций станции с указанием в них соответствующего Nickname профиля QTH -- это уже вторично, хоть и приведёт к дополнительному неудобству)

К примеру может получиться такая структура (Nickname)
2022.06.01-2022.06.02 -- загородный дом
2022.06.03-2022.06.06 -- городской дом
2022.06.07-2022.06.08 -- загородный дом
2022.06.09-2022.06.14 -- городской дом
2022.06.15 -- загородный дом
2022.06.16 -- берег озера
2022.06.17-2022.06.22 -- городской дом
...
И так далее.

---

R1BLH Michael Skolsky

Hi,

? ??????? ????? ?????????? ????? ????????? (Nickname)
2022.06.01-2022.06.02 -- ?????????? ???
2022.06.03-2022.06.06 -- ????????? ???
2022.06.07-2022.06.08 -- ?????????? ???
2022.06.09-2022.06.14 -- ????????? ???
2022.06.15 -- ?????????? ???
2022.06.16 -- ????? ?????
2022.06.17-2022.06.22 -- ????????? ???

That's right

If you cannot name your week-end QTH R1BLH/p for instance, you have to create a new qth/nickname
each time you change QTH...otherwise the system would not know where to put the incoming eqsl

Yes, you will have to check all your inboxes home 1, week-end 1, home 2, week-end 2..........etc
but if you attach all your accounts, you will see in "my other accounts" what accounts have received new eqsl's(blinking icon)

Reason why it's simpler to have another callsign, a variant of your callsign..../p..../m...../a

Sorry, for some reason, cyrillic characters are mistreated by this forum (at least from a non-russian profile)


and to answer your previous questions :


You have corrected your qth/nicknames with a suitable date-range, OK

an incoming eqsl will only land in an account which has a matching date-range

There is no function to transfer qso's between accounts
an incoming eqsl will automatically be confirmed if it matches a record in YOUR OUTBOX

you cannot revert an already confirmed eqsl to a confirm/reject choice, unless you delete the matching qso from your outbox and then reject the eqsl from your inbox/archive...



73 - F6DKQ





Edited by F6DKQ Guy FALCOZ on Jul 6, 2022 at 06:44 AM

Thank you very much for reply.

I'm novice in eQSL. Last time i send paper QSL card was 34 years ago, in my school. :)
Could you clarify one moment: on my QTH R1BLH - 2022.06.19-26_Tekh.2 in the archive there is one eQSL with R3FO. Is that eQSL confirmed by me?

The use of another call sign (with characters after the slash) in Russia is strictly regulated by law.
/p -- transmission from the field (autonomous power supply)
/m -- mobile (on vehicle)
/mm -- on ship
/am -- on the plane
/n -- rookie under the control of an operator
/b -- beacon (temporary use)
/qrp -- output power less than 5W
/qrpp -- power output less than 1W
/[digit] -- region other than home region

Other options are forbidden.

73! Michael
Edited by R1BLH Michael Skolsky on Jul 6, 2022 at 09:19 AM

Hi,

It's more or less the same here in France

but we can also use /a
when for instance I was operating from my parent's home, with a 220V power supply

also the figure in the callsign is not significant for a region in France
/am is forbidden


Yes,

eQSLs between r1blh and R3FO
QSLID...............From To.............Date Time........................Band/Freq.........Mode........Status Added..............................ADIF?
1066690827 R1BLH R3FO 19-Jun-2022 17:40 40M (7.1000) SSB Archived 2022-06-24 08:48:00.0 ADIF
1067374762 R3FO R1BLH 19-Jun-2022 17:40 40M (7.0830) SSB Archived 2022-06-26 09:36:00.0 ADIF

<APP_EQSL_UPLOAD_DATE:8:D>20220624 uploaded on june 24

---

73 - F6DKQ

Edited by F6DKQ Guy FALCOZ on Jul 6, 2022 at 01:57 PM

TNX!!!

73! Michael

---

R1BLH Michael Skolsky