Unfortunately it has been determined that fastecho always drops
seen-by's when it imports messages from another zone. This can't be
turned of by a configuration option.
So for instance the link between Paul Quinn and Tommi Koivula, who both use fastecho, drops them in both directions. Tommi was thinking about moving to hpt though, the last time I spoke with him about this...
I'm using FE and as far as I can see it does not strip/drop seen-by's when messages are imported in via your Z2 feed in to my HUB system.
In fact you can tell FE to keep seen-bys on a message base by message base basis. In my case I have everything set to retain/keep seen-by's indefinately.
@MSGID: 3:640/1384 56add09e
@REPLY: 3:770/100 483fae9b
@PID: JamNNTPd/Linux 1
@CHRS: UTF-8 2
@TZUTC: 1000
@TID: CrashMail II/Linux 0.71
Hi! Paul,
On 01/31/2016 06:52 PM, you wrote to Wilfred van Velzen:
I'm using FE and as far as I can see it does not strip/drop seen-by's
when messages are imported in via your Z2 feed in to my HUB system.
In fact you can tell FE to keep seen-bys on a message base by message
base basis. In my case I have everything set to retain/keep seen-by's
indefinately.
Wilfred is correct, as he stated about their being stripped. We can't
see it in our local bases. But when messages are exported or tossed during incoming, the seen-by are stripped. I've seen the effect on
-this- system.
I intend to re-work my mail moving, basing inter-zone exchanges via
this node. However I'm enjoying a bit of 'real life' and haven't yet
made any config changes. I need motivation. :)
Cheers,
Paul.
--- Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Thunderbird/31.4.0
* Origin: Paul's other Linux vBox - Maryborough, Qld, OZ (3:640/1384) SEEN-BY: 109/500 116/116 123/5 52 140 400 500 789 124/5013 5014 135/300 SEEN-BY: 140/1 154/10 203/0 226/600 229/426 261/38 320/101 119 219 322/759 SEEN-BY: 342/11 806 3634/12 24 27 50
@PATH: 640/1384 384 203/0 320/119 123/500 3634/12
On 01/30/16, Wilfred van Velzen pondered and said...
Unfortunately it has been determined that fastecho always drops
seen-by's when it imports messages from another zone. This can't
be turned of by a configuration option.
So for instance the link between Paul Quinn and Tommi Koivula,
who both use fastecho, drops them in both directions. Tommi was
thinking about moving to hpt though, the last time I spoke with
him about this...
I'm not sure this is correct so have replied in this echoarea so Paul
et al. can comment.
I'm using FE and as far as I can see it does not strip/drop seen-by's
when messages are imported in via your Z2 feed in to my HUB system.
In fact you can tell FE to keep seen-bys on a message base by message
base basis. In my case I have everything set to retain/keep seen-by's indefinately.
i've been thinking about adjusting my stuff, too... just trying to work out the best way to go about it and what the final result will look like...
i've been thinking about adjusting my stuff, too... just trying to
work out the best way to go about it and what the final result will
look like...
I've been thinking about that too. I ran FD/FE/RA years ago in dos and os/2 so I know why you all are reluctant to be done with it.
I wonder if Tobias Burchhardt still has the source and would be
interested in updating it, or releasing the source under the gpl
licence?
In my case I would run fidoconfig and friends, HPT and HTICK. I have
them setup here but not running them ATM but find them to be very well behaved.
* Origin: Paul's other Linux vBox - Maryborough, Qld, OZ
(3:640/1384)
SEEN-BY: 109/500 116/116 123/5 52 140 400 500 789 124/5013 5014
135/300
SEEN-BY: 140/1 154/10 203/0 226/600 229/426 261/38 320/101 119
219 322/759
SEEN-BY: 342/11 806 3634/12 24 27 50
@PATH: 640/1384 384 203/0 320/119 123/500 3634/12
640/384 or 320/119 are stripping as there is no 640/* entries in the seenbys... 203/0 is left because that's the direct uplink...
In fact you can tell FE to keep seen-bys on a message base by message basis. In my case I have everything set to retain/keep seen-by's indefinately.
Just read the "in any case"...
Sigh, thanks for this.
640/384 or 320/119 are stripping as there is no 640/* entries in the
seenbys... 203/0 is left because that's the direct uplink...
Yep. ~640/384 will be the culprit. Björn was very particular about seen-by stripping from day #1;
I was unaware of FE's shortcomings then.
SEEN-BY: 109/500 116/116 123/5 52 140 400 500 789 124/5013 5014
135/300
SEEN-BY: 140/1 154/10 203/0 226/600 229/426 261/38 320/101 119
219 322/759
SEEN-BY: 342/11 806 3634/12 24 27 50
@PATH: 640/1384 384 203/0 320/119 123/500 3634/12
640/384 or 320/119 are stripping as there is no 640/* entries in the seenbys... 203/0 is left because that's the direct uplink...
I know how you feel. I only found out at the end of last year, and felt that I'd been kicked in the 'family jewels'.
Well, as I recall suggesting once before... there's always FMail.
Though it cannot read the FE config directly, it can use a FE-generated Areas.Bbs file. Section 2.1 (FSetup) refers.
640/384 or 320/119 are stripping as there is no 640/* entries in
the seenbys... 203/0 is left because that's the direct uplink...
320/119 runs FastEcho 1.46.1 under OS/2, so it would appear the
stripping is happening there. When I have time, I will have to look
into another tosser for this node.
FE is actually working as it was designed and documented. Tobias
didn't have any clue that one day something like the FidoWeb would
exist.
I need to get my head around what other options there are for tossers
out there. Ideally something that runs under windows.
head around what other options there are for tossers out there. Ideally something that runs under windows.
.and I'm picking this is not the echo to chat about that :)
FMail should perform well. It has something up its sleeve that FE
lacked: a modern, currently-maintained, Windows version.
Look for its support echo called 'FMAIL_HELP'. Keep in mind that
Wilfred is the current maintainer of FMail. Plenty of support there if you choose it.
For Windows I would suggest FMail or Hpt. They both are still in development. Hpt can import FE setup, however there's still manual work
to do. And it won't support Hudson Message Base.
Unfortunately it has been determined that fastecho always drops
seen-by's when it imports messages from another zone. This can't
be turned of by a configuration option.
I've been thinking about that too. I ran FD/FE/RA years ago in dos and os/2 so I know why you all are reluctant to be done with it. I wonder if Tobias Burchhardt still has the source and would be interested in updating it, or releasing the source under the gpl licence?
Re: Proper dupe prevention
By: Tommi Koivula to Paul Hayton on Sun Jan 31 2016 03:42 pm
Unfortunately it has been determined that fastecho always drops
seen-by's when it imports messages from another zone. This can't
be turned of by a configuration option.
Isn't this the correct treatment ? There shouldn't be any zones on seen-by's.
Re: Proper dupe prevention
By: Alan Ianson to mark lewis on Sun Jan 31 2016 06:20 am
I've been thinking about that too. I ran FD/FE/RA years ago in dos and
os/2 so I know why you all are reluctant to be done with it. I wonder if
Tobias Burchhardt still has the source and would be interested in updating
it, or releasing the source under the gpl licence?
Nice try, but the guy still demands a properly completed registration form before issuing a key.
Unfortunately it has been determined that fastecho always drops
seen-by's when it imports messages from another zone. This can't be
turned of by a configuration option.
Isn't this the correct treatment ? There shouldn't be any zones on seen-by's.
I've been thinking about that too. I ran FD/FE/RA years ago in dos
and os/2 so I know why you all are reluctant to be done with it. I
wonder if Tobias Burchhardt still has the source and would be
interested in updating it, or releasing the source under the gpl
licence?
Nice try, but the guy still demands a properly completed registration
form before issuing a key.
AI> I've been thinking about that too. I ran FD/FE/RA years ago in dos andif
AI> os/2 so I know why you all are reluctant to be done with it. I wonder
AI> Tobias Burchhardt still has the source and would be interested inupdating
AI> it, or releasing the source under the gpl licence?
Nice try, but the guy still demands a properly completed registration form before issuing a key.
Nice try, but the guy still demands a properly completed registration
form before issuing a key.
Sysop: | digital man |
---|---|
Location: | Riverside County, California |
Users: | 1,017 |
Nodes: | 17 (0 / 17) |
Uptime: | 112:50:59 |
Calls: | 503,081 |
Calls today: | 16 |
Files: | 212,935 |
U/L today: |
1 files (4K bytes) |
D/L today: |
4,275 files (756M bytes) |
Messages: | 440,554 |