I've now configured a dupe area, but the point shouldn't bee seeing dupes as the message bas was started fresh with no messages in it.
Could you also please add pressing enter to quote along with the space key?
I've just done a git clone, and compile.. If this one goes out it's working...
I've now configured a dupe area, but the point shouldn't bee
seeing dupes as the message base was started fresh with no
messages in it.
Ah, I see. Yeah dupe detection needs some work. at present it is
supposed to check a history file with a crc of the msgid. That doesn't
work so well when messages don't have msgids. (That's not the problem
here, I don't know why it would say it found a dupe when it hasn't)
I also noticed that when listing messages with the index reader, there were replies in the list before the message being replied to.
Just wondering if this is a linux m68k thing or a general postie bug?
I think it might be a general postie bug. I've made a new branch of
postie with new dupe checking, branch is called: "newdupechecking"
apam wrote to vorlon <=-
Also, now messages without msgids will be dupe checked, previously they werent.
I just merged this into main. I tested it on m68k and all the messages
i was able to pull from 21:1/999 worked. If it's still not working can
you zip up your packets and send them to me.. if you don't have my
email address, can you upload it to the sysop at
positronicbrain.net:11892 (telnet)
I've just done a git clone, will test and report back latter tonight.
My theory was that many msgids are generated by unix time, some are poorly implemented and may shoot of several different messages in a second, which some other more robust dupe checkers would notice because they work off the whole message not just message id, but postie did not.
Sysop: | Scott Styles |
---|---|
Location: | Oshawa, ON |
Users: | 9 |
Nodes: | 4 (0 / 4) |
Uptime: | 70:36:31 |
Calls: | 75 |
Files: | 371 |
Messages: | 75,932 |