| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Re: Is this area alive or dead |
> >> {at}MSGID: 1:249/303 04fcd615 486.fidohusk 04FCD615
>
> JD> So what is the proper way, and why is it a 'major' bug?
>
> I forget which FTSC doc covers this but the above is fine up to, {at}MSGID:
> 1:249/303 04fcd615. What can happen to tossers that follow the specs to the
> letter and use MSGID to scan for dupes is that the extra characters will cau
> them to be tossed to a bad file if it exists. What is the purpose of duping
> the id in caps at the end? I've never seen that happen other then in Syncro
> messages. It is stuff like this that causes me to wonder if the drop in
> messaging in Fido could be due to certain programmers deciding specs on thei
> own and thus one well situated hub that deals with MSGID decides these messa
> will not pass beyond them. I think it is entirely possible.
Hmm, I guess I had not looked carefully enough at that line. Had not
noticed the duplication. I'll ask Rob why that happens.
Thanks.
--- SBBSecho 2.10-Linux
* Origin: The Lions Den BBS, Trenton, On, CDN (1:249/303)SEEN-BY: 633/267 270 @PATH: 249/303 261/38 123/500 106/2000 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™.