| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | bad netmail |
BG> Better to send the occasional netmail to nul than have
BG> legitimate messages bounced IMO.
I don't think so. If netmail is trashed, you never know until you
notice that there has been no reply. If you send it to yourself, you
can see that you did wrong, and fix it, and resend it.
BG> And what about netmail messages which are to be gated via UUCP,
BG> where the current format is to send the message to UUCP{at}3:50/40
BG> (entered in the To: field of the message header), while the
BG> message body itself is addressed much the same as QWK netmail
BG> is now, but with characters instead of numerals (e.g To:
BG> diamondTS{at}aol.com)?
I didn't even know about this, but my rep2pkt would simply ignore
all that shit as part of the message, and when rep2pkt checks the
address in the DAT file it would find UUCP{at}3:50/40 in the name, and
take appropriate action... ie, send it anyway. All I would need to do
is add a blank in the address so it would send anything.
I don't know, but my guess is that PKT format treats it the same,
otherwise it would not be compatible. The thing about these add-ons to
an existing standard is that they have to be easy to handle.
At present, I have a .dat file that configures the rep2pkt converter.
In a proper Windows version, this would come up on the screen in an
editor when you wanted to revise it. This sort of thing is shit-easy to
do in VB.
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™.