3. Minor Changes

The following minor changes have occurred.

• Added code to set newly created files owner, group and permissions (UNIX)
  This is for both FTP 'put's and PBBS 'uploads'. Owner is set to the value of 'security createuid', group is set to the value of 'security creategid', and the file's permissions are set to the value of 'security createperms', *IF* the 'security createsecure' command is set to 'on'.
• Renamed the 'security ftpuid' command to 'security accessuid'
• Renamed the 'security ftpgid' command to 'security accessgid'
• Added code to the PBBS download command to also honor security (UNIX)
  The 'security accessuid' and 'security accessgid' values are used (as with the FTP server) to determine whether or not the user has permission to download the file, based on the UNIX file permissions, as they pertain to the secured user/group
• Removed the 'dump' command from UNIX version
  Easy way to core dump, and anyway, who REALLY would use this with GDB around ;-)
• Added a new flag 'STRICT_HTTPCALL' for enforcing valid calls w/HTTPPBBS
• Added use of security 'amprperms' and 'nonamprperms' w/HTTPPBBS
• Added a PBBS 'motd' command, to redisplay the 'pbbs motd' string
• Added code to the PBBS forwarding to prevent useless outgoing connects
  It the past, if there were messages queued in the forward file for a PBBS, but they were all still being held for sysop review or all of them were deleted messages, then a connection would be made, even though there was no traffic that would be outgoing on that connection. This made it work like a polled connect, but was actually an unwanted outgoing connection. Now these useless outgoing connects are suppressed.

  Also added code in that section to remove the '.fwd' file if all the remaining entries in the queue are for messages already deleted from the system.

• Added code to help prevent crashes when parsing a corrupted domain.txt
  I don't know if this will prevent all of the problems, but many sources of problems when parsing a corrupted domain.txt file have been caught. When these cases are found, a message is logged to the log file, to help find the problem, listing the kind of DNS line it encountered that had the error.
• Several more files LINT'ed
• Added a 'smtp kick' at end of outbound forwarding sessions
• Added code to append 'ampr.org' to abbreviated hostnames in PBBS 'send'
  This applies to email addresses like 'ko4ks@ko4ks'. When seen, the address will properly be changed to 'ko4ks@ko4ks.ampr.org', so that rewrites that treat SMTP addresses differently can act properly. See next entry!
• Added 'pbbs maildomain' command
  Depending on the system, some TNOS machines prefer SMTP connections (if possible) and others PBBS connections. This command allows you to override the default (of PBBS addressing) and lets DNS hostnames be used instead.

  This only comes into play for addresses like 'user@host'. In cases like that, the 'host' portion of the address is looked up in both the white pages and the DNS (as 'host.ampr.org'). If only one gets found, that one will be used. If BOTH are valid destinations, then this command will be used to determine which one is used. If 'pbbs maildomain' is on, then the ampr.org address will be what is used; otherwise the white pages one will be used.

  If a full DNS hostname is given or a complete PBBS haddress is used, then this command is not used. The 'pbbs maildomain' command is only used to complete the address used on addresses like 'user@host'.

• Added code to prevent a useless PBBS connection following a failed one
  If a failed PBBS session results in all remaining messages in the queue being marked as aborted, then the next session would end up skipping those on the first scan of the next connect (as it should), but with XFWD (or FBB if the remote site had nothing to send) this would result in a useless connect, as those messages wouldn't try to get out the door at all on that session. If other messages were in the queue, this would work as planned, but this was a special case.
• MANY more files LINT'ed
• Added NNTP XHDR and XOVER enhancements from JNOS
• Removed all 'C' __ARGS() and __FARGS() macros from the source tree
  While not noticable to the user, this cleans up the source tree a lot. It was a lot of work, but past due.

  This assumes compiling TNOS with an ANSI C-compatible compiler, which is no longer an issue, since all TNOS support is for GCC compilers. In this day and age, it's not really an issue, anyway.

• Added a 'chat' PBBS command, an alias for the 'Operator' command
  I THOUGHT that this had been in there for a long time, but noticed that it wasn't.
• Changed the output of 'nntp active' to two newsgroups per line
• Corrected the NNTP usage of GMT time
  The NNTP RFC (977) specifies that the times given to commands like NEWNEWS are to be in the SERVER's localtime, or should be in GMT time, with 'GMT' appended to the string. The NNTP server could handle incoming clients using 'GMT' strings, but would always use ITS localtime when talking to a remote server. This is fine if both are in the same time zone, but otherwise is wrong. Now TNOS's NNTP server will use GMT strings when acting as a client.
• LINT'ing completed
• All the above items included in beta release 2.20b1
• All the above items included in beta release 2.20b2
• Added DNS patches from JNOS to allow CNAME responses to recurse