• Test 2

    From apam@21:1/125.2 to All on Saturday, April 22, 2017 18:10:26
    The Second Mail


    ... MultiMail, the new multi-platform, multi-format offline reader!
    ___ MultiMail/Darwin v0.49

    --- Mystic BBS/QWK v1.12 A32 (Windows)
    * Origin: Blackhole BBS - Mystery Test BBS (21:1/125.2)
  • From apam@21:1/125 to apam on Saturday, April 22, 2017 18:37:55
    The Second Mail

    Well that's interesting. The last 4 chars of the message id are the same,
    but the first four are different.

    So... QWK working 2, QWK not working 1.

    I guess it's a sometimes bug.

    In other news it made me discover a bug in my msgid creation :D

    Andrew

    --- MagickaBBS v0.6alpha (Linux/x86_64)
    * Origin: Cauldron BBS - Magicka Test BBS (21:1/125)
  • From Avon@21:1/101 to apam on Saturday, April 22, 2017 21:41:24
    On 04/22/17, apam pondered and said...

    Well that's interesting. The last 4 chars of the message id are the same, but the first four are different.

    So... QWK working 2, QWK not working 1.

    I'm not sure that's correct.

    [snip]

    From: apam
    To: All
    Subj: Msgid Test
    Date: 04/22/17 18:10
    Base: Mystic BBS Support/Dev

    @TID: Mystic BBS 1.12 A32
    @MSGID: 21:1/125.2 011602d7
    @SEEN-BY: 1/1 100 101 102 103 104 105 107 108 109 111 112 113 114 115 117 118 @SEEN-BY: 119 121 122 123 124 125 126 127 128 129 130 131 133 134 135 136 137 @SEEN-BY: 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 @SEEN-BY: 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 171 172 @SEEN-BY: 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 189 190 @SEEN-BY: 191 192 193 194 195 998 999 2/100
    @PATH: 1/125 100
    Thought I'd also test MSGID generation with QWK seems
    it worked for dan but didn't work for bcw142

    My guess it was just well timed for Dan, but more data
    cant hurt.

    So I'm off to write a second message now, if you don't
    see it, it might have got intercepted as a dupe..

    [snip]

    and message two is as follows

    [snip]

    From: apam
    To: All
    Subj: Test 2
    Date: 04/22/17 18:10
    Base: Mystic BBS Support/Dev

    @TID: Mystic BBS 1.12 A32
    @MSGID: 21:1/125.2 070be3d7
    @SEEN-BY: 1/1 100 101 102 103 104 105 107 108 109 111 112 113 114 115 117 118 @SEEN-BY: 119 121 122 123 124 125 126 127 128 129 130 131 133 134 135 136 137 @SEEN-BY: 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 @SEEN-BY: 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 171 172 @SEEN-BY: 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 189 190 @SEEN-BY: 191 192 193 194 195 998 999 2/100
    @PATH: 1/125 100
    The Second Mail

    [snip]

    Both message ID in this case seem quite different to me.

    So I wonder what is different between you and Brian. Perhaps the tools your using or?

    Best, Paul

    --- Mystic BBS v1.12 A32 (Windows)
    * Origin: Agency BBS | telnet://agency.bbs.geek.nz (21:1/101)
  • From apam@21:1/125 to Avon on Saturday, April 22, 2017 19:59:09
    Avon said....

    On 04/22/17, apam pondered and said...

    Well that's interesting. The last 4 chars of the message id are the
    same,
    but the first four are different.

    So... QWK working 2, QWK not working 1.

    I'm not sure that's correct.

    Yep I meant it worked, so two of us got working packets and one didn't. You're right though I didn't read the message IDs correctly, only the last two digits are the same.

    Both message ID in this case seem quite different to me.

    Yep they are. But why? If our theory that they were based on time was correct, they should be at least very similar if not the same. Either time is a factor in a larger calculation, or time isn't the issue at all and it's something else causing collisions.

    So I wonder what is different between you and Brian. Perhaps the tools your using or?

    No, I'm pretty sure the message ids are generated by mystic, the tools shouldn't play a part in it, also as we've seen dupes in mutil generated messages as well as QWK messages.

    Earlier in a discussion on the WWIV git hub page Alan linked to a very simple message id calculation, it uses the current timestamp and a message serial file - what it does is takes the unix time as serial number if it is greater than the serial file, if not it takes the number from the serial file and pluses one then records the last serial to the serial file. I thought it was very clever way of doing it and implemented it in magicka, perhaps g00r00 could use that?

    Andrew
    --- MagickaBBS v0.6alpha (Linux/x86_64)
    * Origin: Cauldron BBS - Magicka Test BBS (21:1/125)
  • From Richard Menedetter@21:1/104 to Avon on Saturday, April 22, 2017 21:56:04
    Hi Avon!

    22 Apr 2017 21:41, from Avon -> apam:

    So I wonder what is different between you and Brian.
    Perhaps the tools your using or?

    The tools can only make a difference if they are extremely buggy.
    MSGID is created when the message is created.
    No Tool is allowed to change it.
    If they do change it, IMMEDIATELY stop using it!

    But I am very glad that there is a possibility that the QWK/Mutil MSGID bug may
    be solved!

    CU, Ricsi

    --- GoldED+/LNX
    * Origin: One person's <grin> is another's <groan> (21:1/104)