yablacky and Saturn - thanks for Your quick responses! I generally agree with all ideas You both have written, so just some highlights:

Ideal solution IMO. Especially, connected with Saturn's "photo hunting" (making photo after keyboard is opened). BTW, about the latter - would it be possible, to set burst (3-4) auto-photos, triggered on keyboard open, instead of 1? That would made our chances - to get proper face images - close to 100%. I think, that one photo could result in either blurry image (most people mechanically adjust screen angle, just after sliding keyboard open), or one took fraction of second too early (picturing pants or torso). With 4 images burst (considering, that our camera is quite slow at 'bursting', so 4 photos would take 1,5-2 seconds to complete), we're almost sure, to get at least one usable.

You're right, early in the logs, I've clicked "test" twice every time, but then, I had 8 messages total (instead of 2). On later part, I used it only once, and I got 4 messages. Considering, that "isn't loaded during boot" was unneeded, but proper, we can assume that every message was send twice, instead of once (per click). Indeed, I had two "not loaded during boot", and two "test message".

If we add it to my assumption (seems to be confirmed in logs), that program "think" first message sending failed, and immediately try to sending it again, we may have found reason.

In later part of posted log, You can find something, going like "sending message failed" and following it "trying to re-send message after 15 min", but both executed in 1-2 seconds interval. Also, I'm 100% sure, that every click on "test" resulted in message send and received properly, so there should be none indication of "sending message failed", yet there is in logs. It seems, that smscon send message properly, then, for unknown reason, think it failed, and try to re-send it - immediately, instead of 15 minutes later (ignoring 15 min interval, again for reasons unknown). Successful sending of second message is acknowledged by smscon properly, so no other attempts are made.

---

Just notified something - while e-mail account is encrypted in settings file properly, in smscon.log, it's written in plain text (if updating settings, where value of updated thing is also stored). Last time I posted log, I almost published it with my e-mail account data and password inside I think it should be encrypted also, like in settings file (If it is possible), or at least people warned, to delete it from logs, after updating in settings. Let leave posting logs alone - it's just not very wise, to have e-mail account data and password written in plain text file, on '/opt/smscon/smscon.log'

yablacky, thanks for such extensive work on this wonderful program, and Saturn, thanks for implementing controlling new features in Editor so quickly. I'm glad You both weren't scarred by my wall-of-text report

/Estel