When the MAX BR1 Mini sends out an email for auto reboot or loss of connection, it has a date in the text of 2017. Yahoo is rejecting the email saying the date is too far in the past or future and must be spam. The time is correct on the router. Not sure I checked if the date was correct but since it is syncing I would assume the date is correct on the router. Is there a way to edit the canned message that is send from Watchdog or whatever is generating those emails?
Brian
@Brian_Wall could you share that “canned message” (with private details being masked) with us for a better understanding?
BTW, which BR1 Mini (HW1/2 or HW3) and the firmware is running?
Or, you can submit a ticket for our team to check?
WeiMing
This one happens to be from from an HW3, running 8.4 Another is a HW1 running 8.3.
This is an automated message generated from MAX_BR1_XXXX (Peplink MAX BR1 Mini: XXXX-XXXX-XXXX running 8.4.0 build 5075).
Sun Dec 31 19:02:30 EST 2017
Current health status for all WAN:
Cellular: Connected (IP: XXX.XXX.182.143)
Peplink | http://www.peplink.com
Dec 31, 2017
@Brian_Wall thanks for the feedback and the details, we will look at it and come back to you.
BTW, I have masked (edited) your device S/N as this is a public post.
@Brian_Wall Based on our checking, it could possibly be the email notification was sent right after the device was rebooted and before the time sync was completed.
Sample of Notification before the time sync is successful.
If your devices are not the case, please submit a ticket to let us investigate. Do quote this forum thread so the support team is aware of the background.
I checked several of the emails and that does appear to be the case. The disconnect and reconnect emails have the correct time/date but the weekly reboot connect messages have the unsynced time/date.
Now we know the root cause, is there a fix? A way to delay the status emails upon rebooting until the system time is updated.
This is still happening… And… it is not always the case. I had a few notifications lately where the date was correct, followed by an incorrect date. The 2 messages below came in 10 minutes apart, and the first message date was correct, but the second is wrong.
I am a retired programmer of 40 years, started back in the days of CP/M computers, before the IBM PC was released. If you need some more help or info, let me know.
***This message came in at 8.03pm and is CORRECT (corresponds to a log entry below):
This is an automated message generated from MAX_BR1_blur (Peplink MAX BR1 Mini: blur-blur-blur running 8.5.1 build 5203).
Tue Mar 11 20:03:51 CDT 2025
Current health status for all WAN:
WAN: Disconnected (Link down)
Verizon 1: Connected (IP: 100.86.blur.blur)
Peplink | http://www.peplink.com
Mar 11, 2025
***10 minutes later, at 8:13pm, this one came in and is WRONG:
This is an automated message generated from MAX_BR1_blur (Peplink MAX BR1 Mini: blur-blur-blur running 8.5.1 build 5203).
Sun Dec 31 18:18:25 CST 2017
Current health status for all WAN:
WAN: Disconnected (Link down)
Verizon 1: Connected (IP: 100.113.blur.blur)
Peplink | http://www.peplink.com
Dec 31, 2017
***Here is the log for around the above events:
| Mar 12 11:15:13 | System: Time synchronization successful (0.peplink.pool.ntp.org) |
|---|---|
| Dec 31 18:18:33 | WAN: Verizon 1 (Priority 1) connected to VzW (100.64.blur.blur) in SIM slot B |
| Dec 31 18:13:52 | WAN: Verizon 1 Peplink eSIM cannot connect, switching to SIM B |
| Dec 31 18:03:34 | System: Time synchronization fail |
| Dec 31 18:02:48 | System: Wi-Fi AP Normal Mode, Turn ON SSIDs |
| Dec 31 18:01:35 | System: Started up (8.5.1 build 5203) |
| Mar 12 05:09:18 | System: Time synchronization successful |
| Mar 12 05:03:56 | System: Time synchronization fail |
| Mar 11 20:03:51 | WAN: Verizon 1 (Priority 1) connected to VzW (100.86.blur.blur) in SIM slot B |
| Mar 11 20:03:13 | WAN: Verizon 1 (Priority 1) disconnected in SIM slot B |
| Mar 11 17:30:58 | System: Time synchronization successful |
As you can see, the log shows a time sync at 8:03pm. No event coincides with the 8:13 notification. It was the next day before the next time synchronization failure message. We get a few of these failure messages, due to the Verizon tower in our home area. While traveling, I rarely, if ever, see these entries.
Hopefully, you Peplink guys can fix this… let me know if I can help.
Paul Maia
