I have removed the packet passwords...as I don't see a need for them.
Do you ultimately trust your secure links? Is incoming unsecure mail WVV>automatically processed on your system? Does the same apply to the systems WVV>your links?
I have removed the packet passwords...as I don't see a need for
them.
Do you ultimately trust your secure links? Is incoming unsecure mail
automatically processed on your system? Does the same apply to the
systems your links?
If they are not in my connects, they don't get in...because I've told Internet Rex to DENY connections to those who don't have session passwords, or are not in my connections list.
Do you ultimately trust your secure links? Is incoming unsecure mail
automatically processed on your system? Does the same apply to the
systems your links?
If they are not in my connects, they don't get in...because I've told Internet Rex to DENY connections to those who don't have session passwords, or are not in my connections list.
Do you ultimately trust your secure links? Is incoming unsecure
mail automatically processed on your system? Does the same apply to
the systems your links?
If they are not in my connects, they don't get in...because I've told
Internet Rex to DENY connections to those who don't have session
passwords, or are not in my connections list.
Bad idea! Any fido system should be able to receive crash mail from
any other system, otherwise you are just a Pvt system.
And you can't be Pvt when you are a RIN.
If they are not in my connects, they don't get in...because I've
told Internet Rex to DENY connections to those who don't have session passwords, or are not in my connections list.
that is *not* a GoodIdea<tm>... we're seeing the effects of this in region18 where the *C can connect but cannot drop off netmail for
regional business... chasing and eliminating systems flying invalid domains (NXDOMAIN) in their nodelist entry is one thing because they
can be removed since there's no known way to get netmail to them...
the others that are specifically blocking all other systems except
those with session level passwords or listed in the remote's connections... well... this is especially complicated when the *C hat changes from one person to another and no records are available for transfer as well... i don't like the idea that i may have to remove
viable systems because of this particular configuration... i'm still waiting, after numerous weeks, for information from other sysops on
how to contact several of these NOANSWER systems... i really really
really hate the thought that they may have to be removed...
i don't like the idea that i may have to remove viable systems
because of this particular configuration... i'm still waiting, after
numerous weeks, for information from other sysops on how to contact
several of these NOANSWER systems... i really really really hate the
thought that they may have to be removed...
Remove them, and stop their feed. If they give two shits and actually notice.. they'll figure out a way to contact you or someone that can
pass on the information to you (filegate.net and many others).
If they don't care, they just don't care. That's the way it is these days.
If they are not in my connects, they don't get in...because I've told Internet Rex to DENY connections to those who don't have session passwords, or are not in my connections list.
that is *not* a GoodIdea<tm>... we're seeing the effects of this in region18
Bad idea! Any fido system should be able to receive crash mail from any oth WVV>system, otherwise you are just a Pvt system. And you can't be Pvt when you WVV>a RIN.
You do know that Internet Rex is probably the buggiest software out there rig A>now, right?
Probably not. It has a fancy GUI so you'll continue to use it. :(
ORLY? says who? "Pvt" fits easily on to a RIN's nodelist entry with no ML>problems... the RC, in that case, simply becomes a NC at that point... nothi ML>really any "worse" than a NC with a net that has several "Hubs" with some fo ML>feeding from the NC instead of a "Hub"... "Hub" as in network mail hub... no ML>anything like a backbone hub... in any case, the RC would be where "host ML>routed" netmail would be delivered by default for RINs...
removing their entries is exactly what is being done... how that
affects the systems of those providing the removed ones a feed is unknown... that's up to the folks providing the feed... part of the problem with contacting these folks is not knowing where they get
their feed in the first place :(
in any case, it is a done deal... 30+ days should have been enough for them to see or find out about their "Down" status...
You do know that Internet Rex is probably the buggiest software out
there rig now, right?
It has worked for me in nearly 30 years of being a Sysop.
I paid the full fee to register it...why should I throw away
software that does the job?? I didn't even change the colors for it.
It's like Microsoft bugging me to upgrade to Windows 10?? I am a
firm believer in "If It Ain't Broke...Don't Fix It!!".
You do know that Internet Rex is probably the buggiest software out there right now, right?
It's like Microsoft bugging me to upgrade to Windows 10?? I am a
firm believer in "If It Ain't Broke...Don't Fix It!!".
That happens with just about every software out there. If there's a new version, the author or company that made said new version are going to promote it as much as they can. In the end, it's still your choice what you do with your own system.
Bad idea! Any fido system should be able to receive crash mail from
any oth system, otherwise you are just a Pvt system. And you can't
be Pvt when you a RIN.
They can route FIDONet Netmail to my regional hub, Marc Lewis, who
will send it to me.
I was getting repeated crash connects that weren't leaving any mail or picking anything up.
If there is a need for such, since I'm a Regional Independent (no
other FIDONet BBS's in Arkansas), they can contact me via email. Or
they can telnet into the BBS, and use the Feedback option to leave me
a message, and I'll get back with them.
Or, I'll change it to requiring being a nodelisted system.
According to the docs in Internet Rex, having it "standard" (open to
all) is not considered a good idea.
Bad idea! Any fido system should be able to receive crash mail from
any oth system, otherwise you are just a Pvt system. And you can't
be Pvt when you a RIN.
They can route FIDONet Netmail to my regional hub, Marc Lewis, who
will send it to me.
The point of crash mail is that it's delivered direct!
I was getting repeated crash connects that weren't leaving any mail
or picking anything up.
So deal with those. Ask them to stop doing that, or block their ip's
in your firewall.
If there is a need for such, since I'm a Regional Independent (no
other FIDONet BBS's in Arkansas), they can contact me via email. Or
they can telnet into the BBS, and use the Feedback option to leave me
a message, and I'll get back with them.
Those connection methods are outside of fidonet. And how could they
know your email address?
Or, I'll change it to requiring being a nodelisted system.
If you keep your nodelist up to date?
According to the docs in Internet Rex, having it "standard" (open to
all) is not considered a good idea.
If your other security messures (like using pkt passwords), are in
order, there is nothing wrong it.
That happens with just about every software out there. If there's a
new version, the author or company that made said new version are
going to promote it as much as they can. In the end, it's still
your choice what you do with your own system.
In their defense, the author or company know what they've fixed better than anyone and always want the most-safe/secure/reliable version of
their software to be in use, as much as possible.
Certainly to help their reputation.
But this also reflects the author/company's (probably misplaced) faith that all the new code (features and fixes) didn't introduce some new reliability or security issue that was not there previously.
It's a delicate balance. Sure, you know all the holes you've plugged,
but you don't know how many new holes you've created... until later.
In their defense, the author or company know what they've fixed
better than anyone and always want the most-safe/secure/reliable
version of their software to be in use, as much as possible.
Exactly!
Certainly to help their reputation.
And of course there's a lot of the "to make money" aspect as well.
The point of crash mail is that it's delivered direct!
I was getting repeated crash connects that weren't leaving any mail or picking anything up.
So deal with those. Ask them to stop doing that, or block their ip's in you WVV>firewall.
Those connection methods are outside of fidonet. And how could they know yo WVV>email address?
If you keep your nodelist up to date?
If your other security messures (like using pkt passwords), are in order, t WVV>is nothing wrong it.
in any case, it is a done deal... 30+ days should have been enough for them ML>see or find out about their "Down" status...
| Sysop: | MCMLXXIX |
|---|---|
| Location: | Prospect, CT |
| Users: | 325 |
| Nodes: | 10 (0 / 10) |
| Uptime: | 11:51:32 |
| Calls: | 510 |
| Messages: | 220575 |