Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Dray]

I just had a resync but DSLstats 6.0.9 failed to send an email alert

15 Sep 2017 13:19:36   DSL connection dropped
15 Sep 2017 13:19:36   No DSL connection
15 Sep 2017 13:20:36   No DSL connection
15 Sep 2017 13:21:38   DSL connection restored. SNRMup = 15.1 dB, SNRMdown = 4.8 dB
15 Sep 2017 13:22:19   Failed to send email alert
15 Sep 2017 13:22:19   Alert: Modem/router re-sync
15 Sep 2017 14:27:40   Email alert sent: "Alert: Downstream SNRM fell to 4.80"
15 Sep 2017 14:27:40   Alert: Downstream SNRM fell to 4.80

DSLstats 6.0.6 also failed to send an alert email

15 Sep 2017 13:19:21   DSL connection dropped
15 Sep 2017 13:19:21   No DSL connection
15 Sep 2017 13:20:21   No DSL connection
15 Sep 2017 13:22:04   Failed to sent email alert - TSendMail: SMTP error: SMTP::MailData
-Other undefined Status503 command out of sequence -- use RSET to resynchronise

15 Sep 2017 13:22:04   Alert: Upstream SNRM fell to 0.00
15 Sep 2017 13:22:04   DSL connection restored. SNRMup = 0.0 dB, SNRMdown = 4.8 dB
15 Sep 2017 13:22:44   Failed to sent email alert - TSendMail: SMTP error: SMTP::MailData
-Other undefined Status503 command out of sequence -- use RSET to resynchronise

15 Sep 2017 13:22:44   Alert: Modem/router re-sync
15 Sep 2017 13:22:51   Email alert sent: "Alert: Downstream SNRM fell to 4.90"
15 Sep 2017 13:22:51   Alert: Downstream SNRM fell to 4.90
15 Sep 2017 13:27:24   Email alert sent: "Alert: Downstream SNRM fell to 4.80"
15 Sep 2017 13:27:24   Alert: Downstream SNRM fell to 4.80

[roseway]

I see, so the email alert function is working, but fails with a resync. I'll have a look at that.

[j0hn]

Just noticed I didn't get a resync email this morning.
Looking further it appears DslStats didn't detect the resync at all. Version 6.0.9
Did it actually detect your resync Dray? It should have counted it on the stats tab, and showed the snrm up/down on the event log if configured to do so

Email alert for resyncs worked fine on 6.0.6 for me.

[Dray]

Yes, I posted the event log; "15 Sep 2017 13:21:38   DSL connection restored. SNRMup = 15.1 dB, SNRMdown = 4.8 dB"

[Dray]

I just noticed a new field in Configuration/Alerts called Email from.

This was blank so I just entered "joe@bloggs.com" which was then auto-populated in Login username which I blanked out.

I wonder if this was stopping the emails?

[roseway]

The "Email From" field is seen by the recipient of the email as the From address. The login username can be blank if that's what your email service accepts, otherwise it must be the SMTP username (which is commonly the same as the From address.

[d2d4j]

Hi

I hope you don't mind, but any email platform which accepts email without login credentials (username and password) is classed as an open relay/system, so credentials should be presented.

The from email address can however, depending upon the provider, be a different email address from the credentials used

Also, on our enterprise clusters, if there is no subject or return email address (i.e. Null), it is either immediately rejected or send straight to spam).

There is only 1 exception to the above, which could only be set by the system admin, and that is if it is whitelisted. So at which it is directly delivered

I stress though, not many people would have this option as to run your own enterprise mail server costs a lot of money, and takes your time up

@roseway sorry I do not use email alerts, but if I did, our connections are whitelisted.

It does sound as though dray had a blank sender though, but it's late and I could be wrong so I apologise in advance

Many thanks

John

[roseway]

Looking at Dray's extracts from the event log, it appears that DSLstats failed to send an email alert after a resync, but succeeded in sending one after the SNRM fell below the trigger threshold. That is why I concluded that the email alert function is working, but it fails when triggered by a resync. At present I'm unsure why this is, but I'll be looking at it today.

I'm still refining the rewritten email function. In particular, in v6.0.9 it didn't fully support StartTLS, and most users would find that only port 465 would work (or unencrypted port 25). I've corrected this now. In view of d2d4j's comments, I'll disallow blank subject lines.

[broadstairs]

Eric I just tested the current 6.0.9 implementation to send and email alert using port 465 and it worked fine for me.

I have just one suggestion to add to this, could you please allow the user to select which alerts to send an email for? I would only want re-sync alerts by email for example, the others would probably cause too much traffic on some occasions. Also if a re-sync is not detected on a boot up, say after a power failure, could we add a boot up alert email option? The re-sync and boot up, for me at least, are the two most significant alerts I would like to see as an email.

Stuart

[roseway]

Thanks Stuart. The problem with port 465, I've recently learned, is that it's unofficial and deprecated. It's still needed with some service providers, but port 587 is preferred for encrypted emails. So I've now modified the email function to allow either port (as well as port 25), with appropriate control of the encryption type.

Regarding your suggestion, I'm trying to reduce the number of options, but in this case it looks fairly straightforward so I'll see what I can do.

[roseway]

Just noticed I didn't get a resync email this morning.
Looking further it appears DslStats didn't detect the resync at all. Version 6.0.9

Resync detection in DSLstats has been a bit haphazard, and I've now stripped it out completely and rewritten it in a much simplified fashion, which should be a lot more reliable. It's now based on the uptime (AS) value - if AS is less that in the previous sample, then a resync is recorded.

[broadstairs]

Eric my email provider explicitly specifies port 465 so that needs to till be allowed. I will contact them to see why they still use it. Do you have a reference for where it is specified as deprecated ? I may need that to try to get them to allow 587 which does not work for me.

As to the other bits fine if you can and have time but its not a show stopper.

Stuart

[roseway]

Stuart, you will still be able to use port 465 if your provider specifies it.

For background information see (for example)  http://blog.mailgun.com/25-465-587-what-port-should-i-use/

[licquorice]

For information, BT still specify port 465

[broadstairs]

Stuart, you will still be able to use port 465 if your provider specifies it.

For background information see (for example)  http://blog.mailgun.com/25-465-587-what-port-should-i-use/

Thanks Eric, I have spoken with my email hosting company and now have port 587 working OK. They say so many devices still only support port 465 which is why it is their default.

Stuart