AREA:SYNCHRONET
@FMAIL BAD: message too old
Hi Rob,
On 2006-02-06 22:28:00,
AREA:SYNCHRONET
@FMAIL BAD: message too old
Since a couple of days, messages from your system end up in my bad area, because of a very old date. Something to fix or set?
*** Answering a msg posted in area BAD_MSGS (Bad messages).
Hi Rob,
On 2006-02-06 22:28:00,
AREA:SYNCHRONET
@FMAIL BAD: message too old
Since a couple of days, messages from your system end up in my bad area, because of a very old date. Something to fix or set?
Hi Rob,
On 2006-02-06 22:28:00,
AREA:SYNCHRONET
@FMAIL BAD: message too old
Since a couple of days, messages from your system end up in my bad area, because of a very old date. Something to fix or set?
Hi DM - I've noticed similar messages on my system as well. I've noticed that in the web interface (I'm still using the old web interface for
message areas), such messages are listed with "Invalid Time". For some of those messages, when I click on it to read the message, I get the message "Error: can't convert 4294967295 to an integer". I get the same error message in my message reader when I try to read some of those messages.
I'm not sure where that error is coming from though. One such problematic message is in the Hardware/Software Help sub-board on Dove-Net, from spacesst to me, with the title "Frontier router vs. Asus RT-N66U router". There are a few other messages with this "Invalid Time" issue that I can read though.
Since a couple of days, messages from your system end up in my bad
area, because of a very old date. Something to fix or set?
I think I already fixed the problem, but if it continues feel free to let me know. Thanks,
Sysop: | MCMLXXIX |
---|---|
Location: | Prospect, CT |
Users: | 325 |
Nodes: | 10 (0 / 10) |
Uptime: | 03:57:54 |
Calls: | 510 |
Messages: | 220570 |