| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Hrm. |
> the second situation is that of generating a MSGID for those messages > without a MSGID... nick andre's posts are a perfect example... they do not > have a MSGID because his system doesn't support FTS-0009... synchronet > creating a MSGID and adding it to messages without one is the worst of the > two situations because that message will not have the same MSGID on all > systems... each synchronet system will create its own originaddr field as > well as its own serial number and that blows duplicate detection all to > hell... RS> This problem was addressed on July 22, 2012, and I replied to your RS> message in FIDONEWS telling you so but the message did not appear RS> to make it to your system. yes, it did not make it to my system... i think that was about the time you guys also had to do a bunch of reconfiguration because your RC changed... RS> Here's my local copy of that message: RS> http://vert.synchro.net/msgs/msg.ssjs?msg_sub=fidonews&message=1386 RS> 79 thanks for sending that along... i have actually been watching the CVS reports and had not seen anything related which was kind of surprising to me... i knew that if you had seen my message that something would have been done unless you thought of me as another "phil" which i hope you and others do not ;) )\/(ark ---* Origin: (1:3634/12.42) SEEN-BY: 3/0 633/267 640/954 712/0 101 620 848 953 @PATH: 3634/12 123/500 261/38 712/848 633/267 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.