/system logging action> print
Flags: * - default
# NAME TARGET REMOTE
0 * memory memory
1 * disk disk
2 * echo echo
3 * remote remote ::
4 1 remote ::
5 2 remote ::
[admin@test] /system logging action> print
Flags: * - default
# NAME TARGET REMOTE
0 * memory memory
1 * disk disk
2 * echo echo
3 * remote remote 0.0.0.0:514
4 email email/system logging
print
set X action=emailNegative:I'm still on V4.16, but I hear rumors that the "/tool e-mail" settings in V5.x has a tls setting.
/tool e-mail set
address from password port userThx for this info (didn't know that). But still... I have this security feature available, it works, why wouldn't I want to use it?ADD: You don't need tls to send email to a gmail account.
You need tls to relay email to a non-gmail account using your gmail account.
You must use port 25 instead of 583 tho.
Tried that but not working for me, I am on 5.4, when setting up I get:Mine works. V4.16 on RB433AH. This is my settings:Then for a testCode: Select all[admin@test] /system logging action> print Flags: * - default # NAME TARGET REMOTE 0 * memory memory 1 * disk disk 2 * echo echo 3 * remote remote 0.0.0.0:514 4 email emailReplace X with the line number of the topic you want emailed.Code: Select all/system logging print set X action=email
I set "topics=critical" as email and then tried to login with a bad password. The email was sent.
/system logging> set 3 action=mail
input does not match any value of action
:local currentBuf [ :toarray [ /log find message~"logged in" || message~"login failure" ] ] ;:local currentBuf [ :toarray [ /log find message~"login failure" ] ] ;