| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | bad netmail |
BL> I only look for "To:" before ">" so it doesn't look in quotes. BL> I ignore all spaces, fail it on any number over 999, or any BL> sequence of numbers less than 3 or more than 4. It would accept BL> 3:54/54; not 3:54. BG> What about 3:640/6666 or 3:640/305.6666 ? As these contain BG> numerals which are greater than 999, would it then fail ? It would fail on 3:640/6666 but 3:640/305.6666 would just ignore the point and return 3:640/305 as the address because it already has three numbers. I look for "To:" and then I ignore all spaces and look for numbers with delimiters between. Anything but a space counts as a delimiter, in case the old pensioner uses ";" instead of ":", and to make sure I've got a real address I set a limit of 999. I could make it 9999 just as easily, because I still need 3 numbers and less than 4. BG> I ask this because Alex is trying for a node address which is BG> the same as his current point address (and the last four digits BG> of his telephone number), and I've seen several Zone 1 BG> addresses with 4 or more digits too. Alex is a dickhead! I won't send the bastards any mail, so there! BL> At present, I have two ways to send netmail: use the netmail BL> area (address optional), BG> That's OK if the recipient is calling the same board, but BG> without an address, how would it be routed through other nodes BG> ? ROFL!! It wouldn't. If you try to send netmail without an address, then it looks up the name list and if it finds the name then it uses that address. If it doesn't find the name in the list, it sends the netmail to yourself so you know it didn't go anywhere. I'm still trying to decide what to do if the address is different than that listed under the name. If it were a reader, I'd just give a warning, but this happens after the message is packed, so I'll probably send the message to myself. BL> Both QWK and PKT have message headers, but *both* of them send BL> the Netmail information in the message itself. Bloody crazy! BG> Que? I just checked my message base, and neither netmail nor BG> echomail has any address info in the message body itself. In BG> fact, they appear identical in format. It's the tosser (no BG> offence!) and the editor which determine how a netmail is sent, BG> not the manner in which it's addressed (using PKT format of BG> course, dunno about QWK). PKT format puts the netmail address information in the message, following the SUBJECT null terminator but before the actual text. It is identified by Hex 01 (@) followed by INTL then TOPT and FMPT as the point destination and origin. It does the same thing in ordinary mail to identify the conference name... @AREA:LOCUSER QWK identifies Netmail with its "To: 3:711/034.12"... also in the message. Regards, Bob ___ Blue Wave/QWK v2.12 @EOT: ---* Origin: Precision Nonsense, Sydney (3:711/934.12) 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™.