Log sending by email does not work on RB433 v.4.16

I set up sending log by email on other models of routerboards without problems.
But con not succed with this one.
In log I can see:
system e-mail error: Error sending e-mail: Abnormal termination (timeout)

also NTP client is somehow not working on this version.


Anyone have an idea?

Can you post “/tool e-mail”, and the script that is supposed to send the email?
You can enable verbose email logging with

/system logging
add topics=e-mail action=memory

Then try sending again and check the log.

Please post “/system ntp client”.

Thank you for your reply.
I am sending the code:


E-mail
server: 77.75.76.43:25
from: "xxx@post.cz"
username: "xxx@post.cz"
password: "xxxxxxxxxx"

add action=mailuj disabled=no prefix=acc topics=system,info,account
add email-to=xxx@post.cz name=mailuj target=email


NTP
enabled: yes
mode: unicast
primary-ntp: 93.185.104.26
secondary-ntp: 0.0.0.0
status: started

err.jpg

/system logging
add topics=e-mail action=memory

Well,

Ive already put it into code.
But there is no more details in log about e-mail.
In the firewall/connections I can see how the router creates conn to email server and gets syn received.
Thats unfortunately all.

RB433AH v4.16
Test email:

[admin@test] /tool e-mail> send to=tim@Xprolectron.com subject=test body=test

Log shows:

16:20:07 e-mail,debug recv: 220 email.Xprolectron.net ESMTP Sendmail 8.13.8/8.13.8; Tue, 18 Jan 2011 16:20:07 -0600
16:20:07 e-mail,debug send EHLO [68.99.58.119]
16:20:07 e-mail,debug recv: 250-email.Xprolectron.net Hello wsip-68-99-58-119.pn.at.Xcox.net [68.99.58.119], pleased to meet you
16:20:07 e-mail,debug recv: 250-ENHANCEDSTATUSCODES
16:20:07 e-mail,debug recv: 250-PIPELINING
16:20:07 e-mail,debug recv: 250-8BITMIME
16:20:07 e-mail,debug recv: 250-SIZE
16:20:07 e-mail,debug recv: 250-DSN
16:20:07 e-mail,debug recv: 250-ETRN
16:20:07 e-mail,debug recv: 250-AUTH DIGEST-MD5
16:20:07 e-mail,debug recv: 250-DELIVERBY
16:20:07 e-mail,debug recv: 250 HELP
16:20:07 e-mail,debug send MAIL FROM: <> test@Xwififoryou.com> >
16:20:07 e-mail,debug recv: 250 2.1.0 <> test@Xwififoryou.com> >… Sender ok
16:20:07 e-mail,debug send RCPT TO: <> tim@Xprolectron.com> >
16:20:07 e-mail,debug recv: 250 2.1.5 <> tim@Xprolectron.com> >… Recipient ok
16:20:07 e-mail,debug send DATA
16:20:07 e-mail,debug recv: 354 Enter mail, end with “.” on a line by itself
16:20:07 e-mail,debug send .
16:20:07 e-mail,debug recv: 250 2.0.0 p0IMK7Ce029203 Message accepted for delivery
16:20:07 e-mail,debug send QUIT
16:20:07 e-mail,debug recv: 221 2.0.0 email.Xprolectron.net closing connection

I just got the email.
I inserted an ‘X’ into each domain name for the spambots.

Thank you for your time SurferTim, I envy you :slight_smile:
I tried the test mail and can not get this from my mikrotik.
The behavior is still the same.

Do you think that firmware could matters?
I have v.2.29

If you entered the “/system logging” info correctly as I suggested, your log would look something like mine, even tho it might not send, it would tell you why.

Please post “/system logging”.

Flags: X - disabled, I - invalid 
 #   TOPICS                          ACTION                          PREFIX    
 0   info                            memory                                    
 1   error                           memory                                    
 2   warning                         memory                                    
 3   critical                        echo                                      
 4   system                          mailuj                          acc       
     info                           
     account                        
 5   info                            disk                                      
 6   e-mail                          memory

Then send a test email to yourself and see what the log shows. If the “from” entry in “/tool e-mail” is not a valid format and domain, most email servers will reject it.

/tool e-mail
send to=me@mydomain.com subject=test body=test

Yeah, it works, unfortunately just on other routers I administer.
Not with this one :frowning:
Actually I have two RB433 v.4.16 having the same troubles.
Can not get it :confused: