TIP: Click on subject to list as thread! ANSI
echo: ic
to: Janis Kracht
from: Philip Lozier
date: 2006-05-20 09:58:46
subject: Immediate Action Require

>> ECHOMAIL?  Note above I said echomail source. Maybe for netmail, but not
>> echomail being distributed?  :>

 JK> Yes, BBBS would balk at a node who was not in the nodelist if I
 JK> tried to send it any type of mail.

If you were to respond to an "echomail" message from a node that
didn't apear in your message, BBBS would balk at it?

>>"funny" thinking about a few months back when somebody
got reuinted with
>>their
>> old net after recieveing, and sending (seen by everybody) echomail on his
>> old
>> node number.  Your system will NOT balk at echomail that is being
>> distributed
>> with the rest of it... what mailer or tosser checks
"echomail" origin lines
>> against the nodelist.

 JK> If that fellow was a downlink of mine, BBBS would balk.  It takes
 JK> in ANYBODY's echomail though ...

If that fellow -wasn't- a downlink of yours though?

Funny thought on that is that somebody could then run a bogus node number
who didn't care about netmail, use it for echomail purposes,
and taunt you... and you wouldn't even be able to respond back to them.

That's scary.

>> What stops it so long as the echo uplink has them configured in?

 JK> Dunno.. BBBS does check the node for a node number I guess.. and a
 JK> dialable point (I mean like a phone number,etc.).

For echomail messages?  I find this hard to believe.

>> result of it) to worry about... and I make no secrets about it?

 JK> Geez, Phil, gimme a break.  All I was saying is exactly what I
 JK> said.. quit reading crap into stuff. :)

Yea, yea... Okay.

Phil

--- FMail/Win32 1.60
Netwo (1:267/169)
* Origin: ==>== part of the NYCap/Adirondack
SEEN-BY: 633/267 270 5030/786
@PATH: 267/169 106/1 2000 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™.