- 22 Apr, 2020 1 commit
-
-
rswindell authored
be unpacked into stored messages (.msg). Debug-level log message indicating that one or more attributes were removed (and which ones, in hex). This set of stripped attribute flags could easily be configurable, if that turns out to be desirable.
-
- 07 Apr, 2020 3 commits
-
-
rswindell authored
-
rswindell authored
Track and log the packet-export exceptions (link packets that were *not* exported-to) and detail those exceptions (number of seen-bys, paths, origin address, etc.) which were triggered. This requires latest xpdev/str_list.*
-
rswindell authored
why his messages aren't being exported to packets. Don't increment the per-area-export counter when write_to_pkts() returns false.
-
- 03 Apr, 2020 3 commits
- 24 Mar, 2020 1 commit
-
-
rswindell authored
This makes this file more suitable for import into SCFG->Message Areas (something I'll work on soon), i.e. as an alternative to importing badareas.lst
-
- 11 Mar, 2020 1 commit
-
-
rswindell authored
to before the actual export, so that if an area has no downlinks, you won't actually see this errorneous but harmless log message. Also include the "export-to" address in the message.
-
- 23 Jan, 2020 1 commit
-
-
rswindell authored
Areafix requests to unlink a node from an area would corrupt the list of linked nodes: the *last* listed node would always be removed. If this was not the node that submitted the areafix request, then 2 nodes would be removed from the list of linked-nodes for an echo. To simplify this, we're just going to not write the removed node back to the area file, but leave it in the in-memory list. So technically, the node won't be unlinked until the next run of SBBSecho when the area file is re-parsed. If that's a problem, we can always add run-time removal from the in-memory list later. Reported by Alterego (ALTERANT).
-
- 20 Jan, 2020 1 commit
-
-
rswindell authored
*.msg).
-
- 03 Jan, 2020 1 commit
-
-
rswindell authored
-
- 18 Nov, 2019 2 commits
- 30 Oct, 2019 1 commit
-
-
rswindell authored
If a packed messages contains no PATH or SEEN-BY lines, we can still detect and prevent a message loop by comparing the origin address in the packet header against the downlink's address and if it's a match, skip that downlink. It is still possible that a packed message header contains a different origin address than the packet header, and we're actually over-writing the packed messge header variable with the parsed Origin: line address (if there is one), so perhaps we'll want to compare the (actual) packed message header origin address too at some point in the future, if loops continue to be a problem.
-
- 27 Oct, 2019 1 commit
-
-
rswindell authored
write_to_pkts(): If for some weird reason a downlink's address is in the PATH, but not in the SEEN-BYs, detect as a loop and don't send to (add to an outbound pkt for) the downlink. This is an experimental change to see if it addresses the issue reported by Richard Williamson and Mark Lewis with regards to dupes in the COOKING echo from point nodes off 1:396/45.
-
- 17 Oct, 2019 1 commit
-
-
rswindell authored
in case something (e.g. Argus mailer) deleted it while we were waiting our turn to use it. As reported by Alterego (ALTERANT)
-
- 08 Oct, 2019 1 commit
-
-
rswindell authored
aux/net attributes to FidoNet msg header attributes: - CRASH - FILEREQUEST (FREQ) - RECEIPTREQ (RRREQ) This should fix the FREQ netmail issue reported by Richard Williamson (RICHARDF). Thanks for the bug report!
-
- 05 Oct, 2019 1 commit
-
-
rswindell authored
in-place or by also copying to a new string in the process. Don't string "soft-CRs" (0x8d) from UTF-8 encoded FTN messages, ever. Default strip_soft_cr SBBSecho setting to true/on.
-
- 17 Sep, 2019 1 commit
-
-
rswindell authored
If an incoming message contains no CHRS/CHARSET control line *and* the message text contains valid UTF-8 character encodings, set the FTN charset value to UTF-8 so the message will be displayed/handled accordingly. I did not add checks for header fields (to/from/subject) - we should probably auto-detect UTF-8 in those as well, but for now, I don't see messages coming into FidoNet echoes with UTF-8 in the header fields. Incremented SBBSecho/EchoCfg version to 3.10.
-
- 30 Aug, 2019 1 commit
-
-
rswindell authored
was not a recoverable message header (e.g. the toUserName field was *not* at offset 0x22): xx 02 00 01 00 01 00 6A - 02 FE 01 00 00 00 00 30 : .......j.......0 34 20 46 65 62 20 31 31 - 39 20 20 32 30 3A 32 36 : 4 Feb 119 20:26 3A 33 32 04 00 4B 75 72 - 74 20 57 65 69 73 6B 65 : :32..Kurt Weiske So restore the DateTime field validation: the 20th byte must be null.
-
- 27 Aug, 2019 1 commit
-
-
rswindell authored
messages is a null (0x00) byte. Some broken FidoNet software may include a full 20 usable characters in their DateTime header field, like so: "04 Feb 119 20:26:32" - representing February 4th, 2019. Y2K. <sigh> The DateTime won't be parsed fully correct, but at least the packet won't be rejected outright because it is "Grunged". - for Alterego (ALTERANT)
-
- 22 Aug, 2019 3 commits
-
-
rswindell authored
-
rswindell authored
-
rswindell authored
This requires that the AutoAddSubs=true in sbbsecho.ini (the default) and if you don't want an area file created/updated with new subs, just set new option AutoAddToAreaFile=false. Both of these options default to true which is the same as the previous behavior: if you have a link that configured to hub for a msg group, any subs not already in the area list/file will be considered new and added dynamically. So what's new here is that you can set SBBSecho not to create or update an area file and SBBSecho will run just fine if no area file exists or contains no area definitions. Incremented version to 3.09.
-
- 20 Aug, 2019 1 commit
-
-
rswindell authored
-
- 18 Aug, 2019 1 commit
-
-
rswindell authored
Alterego reported, would cause a crash if the netmail message did *not* have a FLAGS kludge line.
-
- 16 Aug, 2019 1 commit
-
-
rswindell authored
standard time-zone (e.g. -0300 == EST) as this is not accurate when daylight saving time is in effect (-0400 == EDT or AST?).
-
- 06 Aug, 2019 1 commit
-
-
rswindell authored
Always log the "exiting" line when exiting with a non-zero error level.
-
- 04 Aug, 2019 3 commits
-
-
rswindell authored
-
rswindell authored
exit), just log the error and continue processing. Reported by wkitty42.
-
rswindell authored
- Don't ever try to unpack a 0-byte file. - Don't log anything or try delete if the file is < 24 hours old. - Try to delete the file if it's >= 24 hours old (and log a msg, INFO-level).
-
- 03 Aug, 2019 2 commits
- 02 Aug, 2019 2 commits
-
-
rswindell authored
file-attachment deletion in write_flofile() - not the KILLSENT attribute flag. Export the SMB MSG_KILLSENT auxattr from SMB mail to FTN netmail \1FLAGS KFS.
-
rswindell authored
"UTF-8", set the msg's auxattr MSG_HFIELDS_UTF8 flag because FTS-5003 states: "The character set identifier applies to all parts of the message, including the header information and the control lines like origin and tear line."
-
- 30 Jul, 2019 2 commits
-
-
rswindell authored
When writing non-bundle file paths/names to BSO/FLO files, don't use the delete (^) prefix unless the message has the "Kill Sent" attribute set. This seems kind of wrong to me. The KFS "Kill File Sent" flag has been defined in FSC-0053 since 1992, that seems more likely the appropriate flag to determine if a message attachment should be deleted (or not) after being sent. But parsing/using the "Flags" control line flags isn't already in SBBSecho, so I'll just punt for now and do what Mark asked for. <shrug>
-
rswindell authored
-
- 26 Jul, 2019 2 commits
-
-
rswindell authored
the Ctrl-A codes: L (CLS), < (backspace), [ (CR), or ] (LF).
-
rswindell authored
start of a valid control paragraph (kludge line), then convert the Ctrl-A char to an '@'. This handles the situation where someone quotes control paragraphs with Ctrl-A chars, for example, we don't want those Ctrl-A chars being misinterpreted as Ctrl-A codes causing weird colors or pauses or whatever.
-