I switched from a Windows system (using fmail) to a linux system
(using husky), and kept all my message bases. This might cause a
problem for dupe checking, since husky starts with an empty dupe
history file. Is there a way to generate this dupe history from the existing messagebases?
I switched from a Windows system (using fmail) to a linux system
(using husky), and kept all my message bases. This might cause a
problem for dupe checking, since husky starts with an empty dupe
history file. Is there a way to generate this dupe history from
the existing messagebases?
Most dupes happen within a couple of hours, so I wouldn't worry about it... ;-)
Sometimes a bunch of old dupes arrive, when somebody does a rescan
without taking precautions, but that is not your problem! ;-) And
maybe husky has a setting for disregarding old arriving mail?
Sometimes a bunch of old dupes arrive, when somebody does a rescan
without taking precautions, but that is not your problem! ;-) And
maybe husky has a setting for disregarding old arriving mail?
Yes: the -tooOld option for a message area definition!
Most dupes happen within a couple of hours, so I wouldn't worry about it... ;-)
Sometimes a bunch of old dupes arrive, when somebody does a rescan
without taking precautions, but that is not your problem! ;-)
Yes: the -tooOld option for a message area definition!Thanks for the hint! What value would you recommend? I think a few days should be enough?
Yes: the -tooOld option for a message area definition!
Thanks for the hint! What value would you recommend? I think a few
days should be enough?
Yes: the -tooOld option for a message area definition!
Thanks for the hint! What value would you recommend? I think a few
days should be enough?
You sometimes see some days/week old legit mails, when mail gets stuck somewhere. Shit happens. So a value of a month (or 2) is probably better...
I also use -sbkeepAll on my EchoAreaDefaults line so seen-bys are not stripped when linking with nodes outside of my own zone.
problem for dupe checking, since husky starts with an empty dupe
history file. Is there a way to generate this dupe history from the existing messagebases?
Yes: the -tooOld option for a message area definition!Thanks for the hint! What value would you recommend? I think a few
days should be enough?
Yes: the -tooOld option for a message area definition!Thanks for the hint! What value would you recommend? I think a few
days should be enough?
Yes, I use -tooOld 60 in my EchoAreaDefaults line.That's what I added as well a few days ago!
I also use -sbkeepAll on my EchoAreaDefaults line so seen-bys are not stripped when linking with nodes outside of my own zone.Makes sense. Added that one now...
The magic word for system migration is PKT.Wow, thanks, that is a nice procedure! Wish I knew about about that one before I made the switch...
For todays low traffic condition in fidonet no mail should be dropped because of age. Fidonet is a _store_ and forward network. The tooOld switch was built to protect against amok running systems where the
usual dupe detection fails (eg. msgid modification).
My hub system has the -tooold set at 60. Most dupes come in fromI have it at 60 now too :-)
systems that have some type of failure, or configuration issue.
Sysop: | Eric Oulashin |
---|---|
Location: | Beaverton, Oregon, USA |
Users: | 101 |
Nodes: | 16 (0 / 16) |
Uptime: | 10:45:46 |
Calls: | 3,515 |
Calls today: | 3 |
Files: | 8,462 |
Messages: | 337,500 |