TIP: Click on subject to list as thread! ANSI
echo: fidosoft.husky
to: KAI RICHTER
from: ZHENJA KALIUTA
date: 2020-01-11 09:52:00
subject: Re: hpt long subjects and

Hi, Kai!

On Sat, 11 Jan 2020 07:23:10 +0200 Kai Richter writes:

 ZK>>>> In case of subject longer then allowed 71 + NUL bytes HPT send
 ZK>>>> the whole PKT with the incorrect message to bads.

 ZK>>>> Would it be more practical to be more error tolerant and just
 ZK>>>> cut it to the allowed limit, or it's considered as modification
 ZK>>>> of messages and forbidden by some document?

 KR> No. If you work around the bugs of others you will build a pile of
 KR> shards.

Well, in general in the world there are other opinions:

https://tools.ietf.org/html/rfc1122

```
1.2.2  Robustness Principle

[...]

                "Be liberal in what you accept, and
                 conservative in what you send"
```

https://tools.ietf.org/html/rfc7103

```Advice for Safe Handling of Malformed Messages```

 MD>>> 2.1.5  No Alteration of Routed Mail
 MD>>> You may not modify, other than as required for routing or other
 MD>>> technical purposes, any message, netmail or echomail, passing

 ZK>> Isn't it an "other technical purpose"? ;)

 KR> Work around a "standard violation" should never become a technical
 KR> purpose.

Valid point, thanks.

 KR> Fix the source of the problem. If it can't be fixed don't allow the
 KR> broken to enter. That's straight, clear and simple.


--- Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux)
* Origin: Somewhere in the North (2:4500/1.59)

SOURCE: echomail via QWK@docsplace.org

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™.