Now that the obligatory knock knock jokes are out of the way, why is the fidonet.org domain no longer being updated? Is it a technical thing or a lack of resources thing or something else?
Now that the obligatory knock knock jokes are out of the way, why is the FL>> fidonet.org domain no longer being updated? Is it a technical thing or a FL>> lack of resources thing or something else?
Give me something to update it with ... that would be a good start.
So what do you propose?
\%/@rd
--- D'Bridge 3.99
* Origin: Home of the ORG (2:292/854)
Give me something to update it with ... that would be a good start.
So what do you propose?
... but I don't know who is currently looking after fidonet.org or if
they are even using bind.
Feel free to educate me.
I'm just wondering why fidonet.org hasn't been updated using the current nodelist in a while.
I have also been speaking to Nick over on this side of the pond about reactivating the old uucp gate for Zone 1 as I am also doing that for another net including enterprise grade spam and virus protection for it.
That is a good question and something that needs to be worked on. The problem to be avoided there is that there are 4 nodelists every week, probably all named t he same and likewise also 4 diff files. There will
be bright people who are goin g to mix it all up, but let me have a shot at this.
From days gone by I remember tonnes of spam being imported into the net that way .
Is there not already an official fidonet nodelist that is compromised of all 4 zones published every Friday?
Much of that has ebbed away and ever since ZCs started producing daily lists, al so of their zone, we are pretty much in-sync within a 24hr period.
Although anti-spam technology is way better than it was even 5 years ago, fighting spam is a never ending game. There are many options, at least for gated netmail that I currently use to eliminate pretty much all of it like converting any base64, mime and html email to text and parsing it forvalid
content. Denying anything with an attachment as it wouldn't be gatedanyway.
Using RBLs and greylisting.
I'm also running a gateway. I'm allowing only plain text messages to the gateway , it blocks spam very well, as well as rbl's and spamassassin.
Is there not already an official fidonet nodelist that is compromised
of all 4 zones published every Friday?
Although anti-spam technology is way better than it was even 5 years
ago, fighting spam is a never ending game. There are many options, at least for gated netmail that I currently use to eliminate pretty much
all of it like converting any base64, mime and html email to text and parsing it for valid content. Denying anything with an attachment as
it wouldn't be gated anyway. Using RBLs and greylisting.
It's been done that way ever since the International Coordinator
position became vacant.
The ZCs have attempted to combat this with the daily nodelists by naming the files and archives with the zone number; eg. Z1DAILY for Zone 1.
nodelist-issues faded-away in less than 2 weeks
Kind of 'recently' though Nick DID start hatching updates in the NODELIST directory, and that helped my pre-configured scripts. Thanks Nick :)
why is the fidonet.org domain no longer being updated? Is it a
technical thing or a lack of resources thing or something else?
Btw: Are you aware of binkp.net? It does what fidonet.org used to do
with DNS. I t's updated from the current nodelist atleast weekly (maybe even daily)...
Feel free to educate me.
Not sure what you mean but as per the FTSC spec on DNS distributed nodelists a DNS server should be updated using the current nodelist. Like I said, I have a functioning perl script that does that, it works currently on another net that I run under a different domain.
Sysop: | Rempala |
---|---|
Location: | Richlands, NC |
Users: | 106 |
Nodes: | 10 (0 / 10) |
Uptime: | 80:38:51 |
Calls: | 195 |
Files: | 6 |
Messages: | 110,253 |