*** 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?

Bye, Wilfred.


--- FMail-W32-1.69.7.119-B20150812
* Origin: Native IPv6 connectable node (2:280/464)
þ Synchronet þ Vertrauen þ Home of Synchronet þ telnet://vert.synchro.net

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.

Eric

---
þ Syn

Re: Bad date
By: Wilfred van Velzen to Digital Man on Wed Sep 02 2015 11:15 pm

*** 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?

I think I already fixed the problem, but if it continues feel free to let me know. Thanks,

digital man

Synchronet "Real Fact" #26:
Rob Swindell (digital man) was born approximately 4 hours before the Unix epoch.
Norco, CA WX: 73.6øF, 65.0% humidity, 7 mph SE wind, 0.00 inches rain/24hrs
---
þ Synchro

Re: Bad date
By: Nightfox to Digital Man on Wed Sep 02 2015 03:36 pm

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.

The problem was an inadvertent bug I introduced in the development code (with regards to QWKnet imported messages) and fixed yesterday.

digital man

Synchronet "Real Fact" #25:
The Synchronet Web Server was written predominantly by Stephen Hurd (Deuce). Norco, CA WX: 73.6øF, 65.0% humidity, 7 mph SE wind, 0.00 inches rain/24hrs
---
þ Synchronet

Hi Digital,

On 2015-09-02 19:12:26, you wrote to me:

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,

There are no new messages in my bad area, and I'm reading messages in this area
comming from your system (including your reply), so I think you are right! ;)

Bye, Wilfred.

--- FMail-W32-1.69.7.119-B20