Okay so I know I am not the only one getting hit each day on fsxNet with duplicate messages from the past few months, and for some reason my
This was a snafu of mail getting cross pollinated from a botched areafix thing on my end.
Okay so I know I am not the only one getting hit each day on fsxNet with duplicate messages from the past few months, and for some reason my duplicate catcher is not stopping all of them. So for those that are posting to my echo's is there a way or something to delete them out for all users?
My initial thought was to un-subscribe from fsxNet and then resubscribe requesting the past one years worth of message maybe. Dunno, just frustration thinking here.
Please let me know if you find a solution for this.. I've also gotten hit with a lot of duplicate outdated messages again today and am a bit frustrated about it myself as its making the task of "caching up at the end of the day" a bit more daunting..
This type of things happens a lot,
it is the nature of the hobby.
We are all human after all.
This type of things happens a lot,Yep, twice in the last 48 hours.
Yep, twice in the last 48 hours.
Once was because of my board, but the other time? I'm at a loss. I
didn't even see that one.
On 03-04-20 09:51, PalKat wrote to All <=-
Okay so I know I am not the only one getting hit each day on fsxNet
with duplicate messages from the past few months, and for some reason
my duplicate catcher is not stopping all of them. So for those that
are posting to my echo's is there a way or something to delete them out for all users?
My initial thought was to un-subscribe from fsxNet and then resubscribe requesting the past one years worth of message maybe. Dunno, just frustration thinking here.
On 03-04-20 16:54, Netsurge wrote to ryan <=-
This was a snafu of mail getting cross pollinated from a botched areafix thing on my end.
To the salt mines.
Hello ryan,
Once was because of my board, but the other time? I'm at a
loss. I didn't even see that one.
I don't think that was your fault at all. I suspect an SBBS node has
set nodes to be able to connect any area in his areas.bbs.
Hello Netsurge,
This type of things happens a lot,
Yep, twice in the last 48 hours.
it is the nature of the hobby.
No, it's an error, not nature. It can be fixed. Simply.
I don't think that was your fault at all. I suspect an SBBS node
has set nodes to be able to connect any area in his areas.bbs.
Is this a flaw in Synchronet or misconfiguation (or both)?
Nowadays where many nodes don't understand the basics of fidonet
anymore, it would be nice if the software would make it a little bit harder to do stupid things.
I'm a bit bored of the it is a hobby excuse. It is a hobby, so we should be extra careful to not annoy people in their free time with technical problems. Yes shit happens and everything is forgiven when people come back from the salt mines, but there were a time when people were proud
of fidonet systems that ran flawlessly. This in only a general comment.
Synchronet has two methods for dealing with what your linked nodes can access. The first and default method allows links to connect to any
areas listed in the areas.bbs. This is the default and works OK for most nodes either with just one net or are not feeding other nodes. They can run this way forever.. no worries.
Okay so I know I am not the only one getting hit each day on fsxNet with duplicate messages from the past few months, and for someout
reason
my duplicate catcher is not stopping all of them. So for those that are posting to my echo's is there a way or something to delete them
Oli wrote to Al <=-
Is this a flaw in Synchronet or misconfiguation (or both)? Nowadays
where many nodes don't understand the basics of fidonet anymore, it
would be nice if the software would make it a little bit harder to do stupid things.
ryan wrote to Oli <=-
I'm a bit bored of the it is a hobby excuse. It is a hobby, so we should be extra careful to not annoy people in their free time with technical problems. Yes shit happens and everything is forgiven when people come back from the salt mines, but there were a time when people were proud
of fidonet systems that ran flawlessly. This in only a general comment.
Alert! Alert! BBS police! Don't be ridiculous.
Oli wrote to Al <=-
I'm a bit bored of the it is a hobby excuse.
There was a time when giant sysops roamed the earth and users trembled
in their wake...
I'm a bit bored of the it is a hobby excuse.
Prepare to continue to be bored.
Once was because of my board, but the other time? I'm at a loss. I didn't even see that one.
I don't think that was your fault at all. I suspect an SBBS node has set nodes to be able to connect any area in his areas.bbs.
On 03-05-20 11:01, poindexter FORTRAN wrote to ryan <=-
There was a time when giant sysops roamed the earth and users trembled
in their wake...
Oli wrote to Al <=-
Is this a flaw in Synchronet or misconfiguation (or both)?
Nowadays where many nodes don't understand the basics of
fidonet anymore, it would be nice if the software would make it
a little bit harder to do stupid things.
There's a setting in echocfg for each linked node to specify an
echolist key that corresponds to a network-specific area file.
There's also a global setting that says "Ignore the per-node setting
and just allow nodes to subscribe to anything in areas.bbs. It
defaults to Yes.
I've been setting the per-node restriction and missed the global
setting.
My only thought has been so sort by date, which would at least take them out of the current messages. Unfortunately I canna do that Jim, my
My only thought has been so sort by date, which would at
I have looked through the Mystic Config Util and in the mutil *.ini's
| Sysop: | sneaky |
|---|---|
| Location: | Ashburton,NZ |
| Users: | 31 |
| Nodes: | 8 (0 / 8) |
| Uptime: | 56:56:54 |
| Calls: | 2,097 |
| Files: | 11,143 |
| Messages: | 950,216 |