* * JNOS 2.0f4 - the 4th beta release of the next official version * * This is a COMPLETE snapshot of my (linux) development system * * That means that MY config.h is included - December 9, 2008 * * Unlike the previous beta version release notes where I only talked * about what had changed for that particular beta alone, this version * of release notes will summarize everything that has changed since I * released the last offical version of JNOS (2.0f) last Dec, 2007. * NOTE : this is NOT a patch - it will replace your previous source ! This document contains several sections. They are as follows : A) What is significantly new since 2.0f of December 21, 2007 B) Fixes to stuff broken over the course of the last year or so C) New commands and configuration files D) How to use the new and enhanced commands and and features E) Get this latest software F) How to compile G) Closing remarks A) What is significantly new since 2.0f of December 21, 2007 ========================================================= 1. Support for the B2F forwarding protocol, including attachments. 2. A B2F exclusion list for stations that can't handle B2F forwarding. 3. Support for the 'Y','N', and 'L' codes in responses to FBB proposals, since JNOS was only supporting the original '+', '-', and '=' codes. 4. Accept telnet (internet access) connections from the Airmail software. 5. Exception list to 'SMTP DENY RELAY' - SDRE functions - very useful ! Added a new 'NoRelay' string for when JNOS sends a 'DENY RELAY' response, which replaces the use of the 'Unknown' string used prior to this, giving a more accurate indication of the situation, instead of confusing users. 6. Hostmode (PACTOR) driver for the PK-232MBX (pakratt 232) AEA modem, including broadcast of FEC (cq cq cq de call call call) text. 7. Direct BAYCOM driver (linux only) - NET2KISS & PSEUDO-TTY not needed ! 8. Two critical fixes to the HFDD code, something that has plagued me ever since I started the HFDD type of interface. This is VERY significant ! a) If you attach any HFDD type interface to JNOS (even if you don't use it - just attaching it), chances are smtp would crash each time it was required. In later betas, the crash would be replaced with a warning to the log, and your smtp queue would simply grow, nothing would ever get delivered, until you restarted JNOS without the HFDD interface. Any code that attaches ANY interface, must use 'setencap()' so that the tcp parameters are properly initialized. Failure to do so causes a crash in the tcpuser.c module. b) Figured out why HF sessions with Airmail on ANY type of HF modem would disconnect a bit too early after forwarding was done, causing Airmail to chirp away for minutes, tying up the frequency. This is a HUGE fix, the final 'FQ' from JNOS now gets sent to Airmail, and it now sees a proper FBB disconnect request, and shuts down PACTOR properly ! 9. Some new designs in the HFDD code for more reliable data exchange with the HF modems. Some of it is just being used with the new PK232 hostmode driver, looks promising - will eventually make it to the other HF modems. 10. New MBX logging - better consistency in logging of MBOX activities. 11. Notification (user customizable shell scripts) for when users connect or disconnect from the BBS, or for when users connect, message, or disconnect from the conference (CONV) bridge. Play a wave file on an event, or send email on an event, or both - or whatever one program into a script file. 12. The 'update Domain.txt' logging is now 'switched off' by default :) 13. Removal of old (unused) code. B) Fixes to stuff broken over the course of the last year or so ============================================================ 1. Bulletin headers messed up due to typo in the AIRMAILGW code, which prevented the 'tofrom' field from being properly setup. 2. Message bleedover when B2F forwarding multiple emails. 3. Double spacing of messages in B2F forwarding with Airmail. 4. The /tmp/fileXXXX files that were not being deleted during forwarding. 5. Pactor sessions between Airmail and JNOS not disconnecting properly, resulting in the channel being tied up for minutes, forcing the Airmail user to have to always manually disconnect - applies to all HF modems. C) New and Enhanced Commands - use the JNOS 2.0 User Manual as base reference ========================================================================== * attach baycom