src/sbbs3 postmsg.cpp 1.109 1.110
Update of /cvsroot/sbbs/src/sbbs3
In directory cvs:/tmp/cvs-serv26448

Modified Files:
postmsg.cpp
Log Message:
Include the vote(s) in the message (telegram) sent to the pollster upon a posted vote msg - the format of the vote(s) is currently hard-coded and not colorized/pretty. This'll require an update to the PollVoteNotice text.dat line.


--- SBBSecho 3.06-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

src/sbbs3 postmsg.cpp 1.127 1.128
Update of /cvsroot/sbbs/src/sbbs3
In directory cvs:/tmp/cvs-serv26458

Modified Files:
postmsg.cpp
Log Message:
Don't create the security-related header fields if the assocated "client" object/struct doesn't have any meaningful data. Prevent this from happening:
SenderTime 19700101000000Z
SenderIpAddr
SenderHostName
SenderPort 0


--- SBBSecho 3.09-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

src/sbbs3 postmsg.cpp 1.128 1.129
Update of /cvsroot/sbbs/src/sbbs3
In directory cvs:/tmp/cvs-serv2344

Modified Files:
postmsg.cpp
Log Message:
Automatic UTF-8 header field detection in savemsg(): if the to, from, or subject header fields are non-ASCII yet valid UTF-8, set the auxattr flag indicating that the msg header is in UTF-8.
This function is used by JS MsgBase.save_msg(), so any scripts/services that use it (e.g. nntpservice, newslink, imapservice, etc.) to save messages with header fields that may be UTF-8 encoded will automatically benefit from this detection. Mixing CP437 (the default) with UTF-8 encoded header fields is not supported, so if one header field is valid UTF-8 (not plain US-ASCII), then they had better all be either plain US-ASCII or UTF-8 or there will be
UTF-8 decoding issues when attempting to display or convert later.


--- SBBSecho 3.09-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

src/sbbs3 postmsg.cpp 1.131 1.132
Update of /cvsroot/sbbs/src/sbbs3
In directory cvs:/tmp/cvs-serv26315

Modified Files:
postmsg.cpp
Log Message:
Don't try to signal an empty semaphore path if the netmail_sem is blank.

--- SBBSecho 3.10-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

src/sbbs3 postmsg.cpp 1.132 1.133
Update of /cvsroot/sbbs/src/sbbs3
In directory cvs:/tmp/cvs-serv27907

Modified Files:
postmsg.cpp
Log Message:
Include a replied-to message's to field to be selected in the post-to history (arrow-up to choose strings from history).

--- SBBSecho 3.11-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

https://gitlab.synchro.net/sbbs/sbbs/-/commit/97bade44ebad5b431485e93c
Modified Files:
src/sbbs3/postmsg.cpp
Log Message:
Notify local recipients of locally-posted messages addressed to them.While SBBSecho would notify local users of imported messages addressed tothem (both EchoMail and NetMail) and QWK-imported messages recently gainedthe ability to notify local recipients of messages addressed to them, othermethods of posting messages (e.g. just using the normal terminal servermethod, e.g. the 'P' command) or using any JavaScript (e.g. web) methods ofposting messages lacked recipient notifications. So that's now fixed.And for JavaScript-saved local email messages too. I don't *think* this willresult in any duplicate notifications of received messages, but let me knowif you see excess/duplicate notifications.Anonymously posted messages are excluded.Messages posted to yourself are excluded (who does that?).
--- SBBSecho 3.11-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

https://gitlab.synchro.net/sbbs/sbbs/-/commit/f4ac7f3920abba7d3c717e3d
Modified Files:
src/sbbs3/postmsg.cpp
Log Message:
Resolve a gcc warning about signedness.
--- SBBSecho 3.11-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

https://gitlab.synchro.net/sbbs/sbbs/-/commit/c8193766c6b75abb18a2c257
Modified Files:
src/sbbs3/postmsg.cpp
Log Message:
Fix savemsg() bug introduced in 97bade44eb (Sep-30), returning false failure'i'
is the return value of savemg(), used to determine success or failure(and what kind of failure) - so we can't use that for the usernumber ofthe recipient.
--- SBBSecho 3.11-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

https://gitlab.synchro.net/sbbs/sbbs/-/commit/a852cced25cbf1285825942f
Modified Files:
src/sbbs3/postmsg.cpp
Log Message:
Reduce unnecessary posted-to username searches. Auto-UTF8 in savemsg().When posting to "All" or replying to a message that was posted by networked (not local) user, don't attempt to search for that username in the local user base to inform them of the posted message to them.savemsg() is the underlying C function for saving a new message (mail or post) to a message base from several
places, including JS modules. If there was no "charset" specified in the passed
message header, check to see if the message body text is non-ASCII but valid UTF-8, and if it is, set the FIDO_CHARSET header field to the appropriate UTF-8
charset identifier string. This would *also* address Issue #177 reported by Michael J. Ryan. It's possible, but unlikely, that a message text would contain
valid CP437 that *also* happened to be valid UTF-8. If that does happen to occur (e.g. in posted ANSI art?), we might want to revert this enhancement to savemsg() and leave to the caller's to detect/specify the charset, always.
--- SBBSecho 3.11-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

https://gitlab.synchro.net/main/sbbs/-/commit/54c935707ff58e948fb0df2b
Modified Files:
src/sbbs3/postmsg.cpp
Log Message:
Move the tags prompt to *before* the locking of the message baseThanks Mr. Executive Chicken esq. for the telephone call and bug report.
--- SBBSecho 3.14-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

https://gitlab.synchro.net/main/sbbs/-/commit/489267ade424d4f40cf8b752
Modified Files:
src/sbbs3/postmsg.cpp
Log Message:
mod_ar is no longer a pointer, it's an arrayCID 319077
--- SBBSecho 3.14-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

https://gitlab.synchro.net/main/sbbs/-/commit/908618c85f29a300acc7a500
Modified Files:
src/sbbs3/postmsg.cpp
Log Message:
Debug the "thread_back field missing" errorSome QWKnet vote messages are failing:evnt unpackREP <ENSEMBLE> !ERROR 2 (No such file or directory) in qwk.cpp line 1146 (qwk_vote) writing "/sbbs/data/subs/dove-gen" access=-105 info=smb_addvote thread_back field missingCatch this problem a little higher up
(in votemsg()) and log the message's reply-IDs to help determine what's the root-cause here. Don't bother calling smb_addvote() if thread_back is 0.
--- SBBSecho 3.14-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

https://gitlab.synchro.net/main/sbbs/-/commit/33a8b69cfbbd8194e3519608
Modified Files:
src/sbbs3/postmsg.cpp
Log Message:
Strip control chars/ctrl-A sequences from msg subject in notify()We may want Ctrl-A sequences in the telegram subject, but not in the messagesubject
--- SBBSecho 3.15-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

https://gitlab.synchro.net/main/sbbs/-/commit/4a86ab8768e486a58d22d55e
Modified Files:
src/sbbs3/postmsg.cpp
Log Message:
Bounds-check subnum in savemsg()It's possible to use savemsg() (from JS MsgBase.save_msg()) to add a messageto a message base that's not a sub-board (not configured in SCFG->MessageAreas and not the "mail" base), but in that case, savemsg() would dereferencean invalid sub in the scfg->sub array and crash. So use is_valid_subum()to insure the subnum is a valid sub before using as an index.
--- SBBSecho 3.20-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

https://gitlab.synchro.net/main/sbbs/-/commit/69111a8f420d212de3c0d638
Modified Files:
src/sbbs3/postmsg.cpp
Log Message:
If user doesn't modify the replied-to-msg subject, use the original subject

(which might be UTF-8 encoded). This works-around the problem that Accession reported in #synchronet with my reply to a UTF-8 encoded message using a CP437 terminal which resulted in a message body that was UTF-8 encoded but a message subject that was CP437 encoded. This mix of encodings is not supported by FTN standards.

This is just a work-around since if the user modifies the subject the result could still have the CP437 unside-down question marks (indicating non-translatable UNICODE chars) and those should be converted to UTF-8
chars when going out on FTN or being stored in the message base. So there's still a bug here somewhere that I need to look into more.
--- SBBSecho 3.23-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

https://gitlab.synchro.net/main/sbbs/-/commit/1dde501fe8ea8dc8bea5e3d4
Modified Files:
src/sbbs3/postmsg.cpp
Log Message:
Call add_msg_id() *after* opening the message base to send notification email

notify() was creating wrongly-formated auto-generated Message-IDs:
e.g. Message-ID: <677B3F17.0.notices@vert.synchro.net>
--- SBBSecho 3.23-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)