-=> Wilfred van Velzen wrote to August Abolins <=-

 WvV> TID: FMail-lnx64 2.1.0.18-B20170815
 WvV> PID: GED+LNX 1.1.5-b20161221
 WvV> REPLY: 2:221/360 EF6B28DC
 WvV> MSGID: 2:280/464 779086FC
 WvV> Hi August,

 WvV> On 2019-05-09 23:57:00, you wrote to me:

 AA>>> Just a test upload with SemPoint + BW -> dangerbay bbs
 AA>>> (pcboard) and bluewave door.

 WvV>> At least the MSGID kludge is in your message on arrival here...

 AA> The MSGID originating from SemPoint is being replaced with a new one
 AA> by the PCBWave door.

 AA> Infact, it looks like every host system is replacing the original MSGID
 WvV> and
 AA> PID that SemPoint puts in.  I thought that if those were present upon
 AA> upload, they would remain untouched.

 WvV> If it's from a bluewave package I can see the logic in that. Because
 WvV> bluewave packages basically are equal in status to messages written
 WvV> online by a bbs user. And those messages get the MSGID from the bbs.

 AA> Not a major issue.  But the lack of ANY kludges in the downloaded
 AA> packets from DangerBay's PCBWave door, is a bit disconcerting.

 WvV> I don't see a reason why they should be removed unless the bluewave
 WvV> standard requires so?

 WvV> Bye, Wilfred.

 WvV> --- FMail-lnx64 2.1.0.18-B20170815
 WvV>  * Origin: FMail development HQ (2:280/464)

Just a test reply by Multimail/BW/Concord.

This combination seems to be able to show the kludges...

'Tommi

... MultiMail, the new multi-platform, multi-format offline reader!

--- Concord/2/BW 001B30d (Reg.)
 * Origin: - rbb - telnet://rbb.homeip.net - (2:221/360)