| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | origin line |
PE> Ok, on the origin line question, yes you were right, it was the PE> MSGID, not the origin line, that caused it to get the wrong address. I still cant see how it can do that when it was INSIDE the SOT/EOT which was SPECIFICALLY intended to allow for that problem of stuff that would normally be part of the mail non text body appearing in what is meant to be the body of the text. Maybe I am missing the point utterly on this, but I cant see where. PE> Both problems were fixed in 2.60. Dunno, I still dont see that thats the correct place to fix it. Surely since it was within the SOT/EOT, the problem is in Tobruk which didnt ignore the superfluous MSGID in the message body. Either you are having a brain fart or I am. @EOT: ---* Origin: afswlw rjfilepwq (3:711/934.2) SEEN-BY: 711/934 @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™.