| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | UUCP!!! |
Hello John, RS> There usually is enough. Normally the first line of the body of RS> the message contains who wrote what is being replied to. RS> It should be feasible to have a reader which has a phantom To: RS> field which doesnt actually from the header at all but has been RS> extracted from the body of the message. RS> There is also normally a full message ID which allows complete RS> threading etc too. JT> Ok, my next question is, if there IS enough information in the JT> public message as to who that message is intended for, the WHY JT> didn't they already write this into the gating software? There isn't... I've been reading scads of messages. Some have To: information and some don't. We need an extra line in the header. The header is just text, and is ended by a blank line. Some messages then have a source which is probably derived from the header in the message to which they are replying... but that may not be the person to whom you are sending the reply! There is only one solution... we need to add a To: line and it has o be in the header. JT> There is more than one gating package out there, ALL of them do JT> the same, address the message to all. As I have since discovered. The UUCP format is flawed. Regards, Bob ___ Blue Wave/QWK v2.12 @EOT: ---* Origin: Precision Nonsense, Sydney (3:711/934.12) SEEN-BY: 711/934 712/610 @PATH: 711/934 |
|
| 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™.