Failing to send emails via relay

Ewon Support Ewon Flexy
#1

We are still experiencing issues with two eWons failing to regularly send emails via the relay.

The logs show the some errors as below, would these be related, could you check the relay so if it is causing the time out. We are also getting some alarms saying a buffer is full. Would it be possible to clear this?

1598955355 01/09/2020 10:15:55 smbs-Mbs Gateway target device failed to respond smodbus-Mbs Gateway target device failed to respond mbsio 79305 22331
1598955370 01/09/2020 10:16:10 smbs-Mbs Gateway target device failed to respond smodbus-Mbs Gateway target device failed to respond mbsio 79305 22331
1598955370 01/09/2020 10:16:10 muting (pattern of 1 event) eer-Error Mute Information mbsio 79305 -20205
1598956207 01/09/2020 10:30:07 pattern of 1 event muted 45 times eer-Error Mute Information http 79307 -20205
1598956207 01/09/2020 10:30:07 secu-Authentication failure (From WEB server, ) secu-Authentication failure http 79307 -28611
1598956208 01/09/2020 10:30:08 secu-Authentication failure (From WEB server, ) secu-Authentication failure http 79307 -28611
1598956208 01/09/2020 10:30:08 muting (pattern of 1 event) eer-Error Mute Information http 79307 -20205
1598956238 01/09/2020 10:30:38 smbs-Mbs Gateway target device failed to respond smodbus-Mbs Gateway target device failed to respond mbsio 79305 22331
1598956241 01/09/2020 10:30:41 smbs-Mbs Gateway target device failed to respond smodbus-Mbs Gateway target device failed to respond mbsio 79305 22331
1598956241 01/09/2020 10:30:41 muting (pattern of 1 event) eer-Error Mute Information mbsio 79305 -20205
1598956830 01/09/2020 10:40:30 pattern of 1 event muted 31 times eer-Error Mute Information unact 79301 -20205
1598956830 01/09/2020 10:40:30 ssnd-SMTP server Rx timeout smtpsnd-SMTP server Rx timeout unact 79301 21705
1598956841 01/09/2020 10:40:41 smbs-Mbs Gateway target device failed to respond smodbus-Mbs Gateway target device failed to respond mbsio 79305 22331
1598956844 01/09/2020 10:40:44 exp-Tag name is invalid export-Tag name is invalid unact 79301 23604
1598956856 01/09/2020 10:40:56 smbs-Mbs Gateway target device failed to respond smodbus-Mbs Gateway target device failed to respond mbsio 79305 22331
1598956872 01/09/2020 10:41:12 smbs-Mbs Gateway target device failed to respond smodbus-Mbs Gateway target device failed to respond mbsio 79305 22331
1598956872 01/09/2020 10:41:12 muting (pattern of 1 event) eer-Error Mute Information mbsio 79305 -20205
1598958004 01/09/2020 11:00:04 pattern of 1 event muted 63 times eer-Error Mute Information http 79307 -20205
1598958004 01/09/2020 11:00:04 secu-Authentication failure (From WEB server, ) secu-Authentication failure http 79307 -28611
1598958008 01/09/2020 11:00:08 eppp-The maximum connection time has been exceeded pppitf-The maximum connection time has been exceeded ppp 79311 -22055
1598958009 01/09/2020 11:00:09 secu-Authentication failure (From WEB server, ) secu-Authentication failure http 79307 -28611
1598958013 01/09/2020 11:00:13 smbs-Mbs Gateway target device failed to respond smodbus-Mbs Gateway target device failed to respond mbsio 79305 22331
#2

Hello @TF_MAC,

Can you send me a backup.tar file of the device with support files included? Also are you using relay.talk2m.com or what relay are you using to send these emails out?

-Tim

#4

MOVED TO STAFF NOTE (492 KB) MOVED TO STAFF NOTE (473.5 KB)

#6

Hi @TF_MAC,

What’s are you seeing in the scheduled actions section?

image
image1366×540 30.2 KB

-Tim

#7

I currently don’t have access to this information(screenshots) sorry.
Is there any issue or possible reasons for the issue you can see with the current information.
sorry

#8

Is the device not online over eCatcher? If it is we should be able to grab that information. If it’s not online over eCatcher, then relay.talk2m.com isn’t an available SMTP server

#9

It will also let us know if the issue lies between the flexy and our relay, or the relay and your email if you can get a screenshot of that page

#10

Hi Tim

the ewons are available over ecather as i have been provided logs for such.
i will also try to get the screenshot of the scheduled tasks.

#11

Ok thanks, after that we should be able to find out where the issue is coming from

#12

Hi Time sorry for the delay
these are the images from the Ewons that have been sent hope they help I

image
image903×416 26.8 KB
image (1)
image (1)876×520 32.5 KB
.

#13

Hi @TF_MAC,

Can you get me a picture of this section of the device?

image

#14

here are the screenshots I received.

image (3)
image (3)1148×471 37.1 KB
image (4)
image (4)1139×474 37.7 KB

#15

If it’s showing success there, then it means it’s reaching our SMTP server and that our server should be sending them to the email you provide. Are you using something like Yahoo as your email? Or is it something like a company email? If it’s Yahoo, then unfortunately we don’t have a way for that to go through currently but the dev team is working on this incompatibility. If it’s a company email, you may want to check with your IT and see if the emails are getting blocked or reported as spam

#16

That is the point, the emails from other eWons are showing up fine on the final system, these two ewons’ emails never arrive.

They are all using the same ‘from’ email address and the same destination email address, all being sent via your SMTP relay.

If our system was identifying them as junk or blocking them, wouldn’t it be doing it for all mails coming from your relay (and all eWons)?

#17

Could you make me a temporary user on this account and send me the info in a private message so I can try and test this out? You also shouldn’t need to have anything in the from field of the device if you’re using our server. It should only require the port number 25 and the relay.talk2m.com

#18

Hi Tim
Would you require a temp use for the Talk2M and the Ewon?

#19

Hi @TF_MAC,

Either we’d need temporary login info for the Flexy and eCatcher, or if I could take a look at this over TeamViewer when you’re free that works too

Teamviewer Executable

-Tim

#20

I just tried sending an email and it looks like you’re successfully reaching our server, but I think you might be getting throttled for sending too many emails at once

#21

Is there a possible solution for this >?

#22

When I was looking at it, it looks like you’re sending 10 emails at once pretty frequently. Could you space it out so that you’re not sending these all at once?