| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | echomail |
PE> A couple of days ago you sent me a message which contained an PE> origin line. My system rejected it, and the rest of the packet. What was the date on the packet, I cant find it, tho its a tad awkward to search for. PE> As I said in this echo a couple of months ago, I have fixed the problem PE> with PQWK, the onus is on you to use the new PQWK or Tobruk will reject it. The problem is that you barely even test changes, just release and pray. It aint exactly a terrific idea to just use stuff released like that. PE> I am recompiling Tobruk now, with that bit of code commented PE> out, to allow what appears to be "routed echomail". Then I PE> will recompile it back to normal. And then THAT IS IT. NO MORE. That doesnt sound like a terribly practical approach, because its quite feasible for other than PKTs generated by PQWK to have that problem. In other words, even if the latest PQWK is used, you havent allowed for some other point which doesnt even use PQWK at all doing that blemish. And its not as if its a particularly uncommon problem either. @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™.