Hi, mark!

On Sat, 11 Jan 2020 08:16:43 +0200 mark lewis writes:

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

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

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

 ml> keeping in mind my previous message on this, i also highly agree
 ml> with this and still look to the caveat i listed in that previous
 ml> message...

Thanks for the detailed reply.

 ml> ew (TINW) really need to know the name of this defective software
 ml> creating pkts with too long subject lines... it is possible there's
 ml> a newer/older version that doesn't have this defect and the
 ml> originating system can be pointed to this version to replace their
 ml> defective one...

There is no problem there (anymore). It was some newly written software
and the author is aware of it and has fixed it AFAIU.



--- Gnus/5.13 (Gnus v5.13) Emacs/24.5 (gnu/linux)