| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Unpacking insecure arcmail |
On Sun, 15 Mar 2015, Kai Richter wrote to mark lewis: KR>> I'll always like to learn, which common tossers did/do so? ml> fastecho has done so over here for years... there are others which ml> also followed but i don't know their names any more... KR> Doesn't sound like other common tossers if you can't remember their KR> names. ;) old age has its benefits... sorry to hear about the trouble but yes, that's what can easily happen when the software being used is not configured for or even offering what used to be commonly offered... too many "new kids" develop "new stuff" and just don't have the knowledge of the past... in some cases, when old-timers point these things out, they are blown off with "we don't need that any more" and then you get what you ran into... granted, it started as an accident by that person who enabled that setting but that should be OK if the software processed /netmail/ in the insecure inbound... imagine how many paths are truly broken for this one simple process that should be enabled by default... no wonder folks can get routed netmail working properly :smh: )\/(ark* Origin: (1:3634/12) SEEN-BY: 11/201 34/999 90/1 116/18 120/331 123/500 1406 128/187 135/364 140/1 SEEN-BY: 218/700 222/2 226/0 160 230/150 240/1120 249/303 250/1 261/38 100 SEEN-BY: 266/404 1413 267/155 280/464 1027 282/1031 1056 292/907 908 311/2 SEEN-BY: 320/119 340/400 393/68 396/45 633/267 280 640/384 712/101 550 848 SEEN-BY: 770/1 801/161 @PATH: 3634/12 123/500 261/38 712/848 633/267 |
|
| 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™.