On 09/19/18, A. Dumas pondered and said...
 
 AD> > A gateway that posts a message to a NNTP server in a specific timezone t
 AD> > it resides in, is not posting the message incorrectly.
 AD> 
 AD> If it doesn't specify the timezone, or it attaches a wrong timezone, then
 AD> yes, it posts incorrectly. You use defective (obsolete) software in the
 AD> sense that it does not adhere to the usenet message interchange standard
 AD> as described by RFC 1036, from which I quote below. If you can't fix it,
 AD> the solution would be to take your shitty software offline. Nobody has

The gateway software is operating as intended. It's attaching the correct
timezone stamp to a message being posted by it. I think this is key point we
differ on. The software is not defective because it doesn't run the way you
think it should. It runs as intended. I do agree it's legacy software but
it was being used quite happily back in the late 1990s and *nothing* has
changed to it since. Turns out there may be source code for it (when I did a
quick look thanks to Google) so if you know C and feel so inclined why not
download the code and modify it to a way you think it should work.

 AD> the solution would be to take your shitty software offline. Nobody has
 AD> bbs access but not internet access, have they? So the gateway is not
 AD> needed.

Those who choose to run a BBS system, of which there are many, are quite
happy to use a gateway service to enjoy bi directional content between a BBS
using BBS technology and Usenet. The system is well used and carries hundreds
of messages between the two ecosystems each day. A blanket statement that
something is not required seems pretty ignorant to me when you're not engaged
in the scene. 

--- Mystic BBS v1.12 A39 2018/04/21 (Windows/32)