| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | RFC type packet format th |
ml>> help stomp out dingle berries and hand holding... DO NOT code ml>> around other people's bugs!!! PE> What does the mailprocessor you use do? that depends greatly on the error itself... in one recent incident, the packed message time/date stamp is missing the last three characters (:xx where xx = seconds). this caused the AREA: line to be out of place and the tosser "properly" put the message in my netmail area. PE> 1. Send out of spec mail to your downlinks (using the rather lame PE> excuse that it was someone else's fault, you're just following PE> orders). if i wasn't running GMD and a couple of others to trap these things, yes, i believe that this is what it does. i'm not it's author... PE> 2. Fix the dates. i'd hope not... i've not seen any evidence of this... PE> 3. Bounce the out-of-spec mail, informing the originator. GMD and others handle this for me. the tosser's job is to toss mail not to inspect it... PE> 4. Delete the out-of-spec mail without informing anyone. again, i'd hope not... i've not seen an evidence of this... BTW: my system saves ALL inbound mail for up to 48hours after it's arrival on system. this is so that i =can= go back and inspect the pkts as they were when they arrived... PE> It's a tough choice to make, with no ruling from the FTSC about PE> what we're meant to be doing. what does the FTSC have to do with this? policy states that mail, if not passed on, must be bounced to the originator... so... bounce the shit or pass it on... your choice as long as one or the other is done... some say the ethical thing to do is to pass it on. others say the opposite. both are correct. )\/(ark* Origin: (1:3634/12) SEEN-BY: 13/13 37/100 50/99 102/735 105/103 119/88 129/11 138/146 153/800 920 SEEN-BY: 157/586 167/90 200/204 201/505 203/512 992 204/200 209/720 7211 SEEN-BY: 239/1 245/6910 260/742 261/1137 270/101 102 103 104 211 272/160 SEEN-BY: 280/1 801 282/1 4073 283/657 292/4 511 876 320/119 321/1 332/1 SEEN-BY: 334/201 341/70 1002 344/3 345/12 348/105 362/37 367/1 385/100 387/31 SEEN-BY: 396/1 402/311 403/150 405/0 406/100 430/105 440/1 600/348 620/243 SEEN-BY: 626/660 632/348 640/206 230 305 820 821 822 823 700/101 711/409 410 SEEN-BY: 711/413 430 808 809 934 712/515 713/317 724/10 800/1 2002/2002 SEEN-BY: 2430/1423 2433/225 2602/100 2604/104 2613/5 2624/306 2630/1001 SEEN-BY: 3401/308 3611/18 3615/7 50 7104/2 @PATH: 3634/12 170/400 396/1 270/101 209/720 640/820 711/409 808 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™.