crichardson/enigma-bbs
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

At least for now, use FTN-compliant MSGID for NetMail exports

Browse Source
This commit is contained in:
Bryan Ashby
2018-01-09 19:38:36 -07:00
parent c4c30e0c0d
commit d225d78fa9
1 changed files with 13 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
core/ftn_util.js
View File

@@ -135,9 +135,20 @@ function getMessageSerialNumber(messageId) {
// //
// ENiGMA½: <messageId>.<areaTag>@<5dFtnAddress> <serial> // ENiGMA½: <messageId>.<areaTag>@<5dFtnAddress> <serial>
// //
function getMessageIdentifier(message, address) { // 0.0.8-alpha:
// Made compliant with FTN spec *when exporting NetMail* due to
// Mystic rejecting messages with the true-unique version.
// Strangely, Synchronet uses the unique format and Mystic does
// OK with it. Will need to research further. Note also that
// g00r00 was kind enough to fix Mystic to allow for the Sync/Enig
// format, but that will only help when using newer Mystic versions.
//
function getMessageIdentifier(message, address, isNetMail = false) {
const addrStr = new Address(address).toString('5D'); const addrStr = new Address(address).toString('5D');
return `${message.messageId}.${message.areaTag.toLowerCase()}@${addrStr} ${getMessageSerialNumber(message.messageId)}`; return isNetMail ?
`${addrStr} ${getMessageSerialNumber(message.messageId)}` :
`${message.messageId}.${message.areaTag.toLowerCase()}@${addrStr} ${getMessageSerialNumber(message.messageId)}`
;
} }
// //