Subj : Proper dupe prevention
To   : Paul Hayton
From : Tommi Koivula
Date : Sun Jan 31 2016 08:42 pm

Hi Paul.

31 Jan 16 21:52, you wrote to Wilfred van Velzen:

 PH> On 01/30/16, Wilfred van Velzen pondered and said...

 Wv>> Unfortunately it has been determined that fastecho always drops
 Wv>> seen-by's when it imports messages from another zone. This can't
 Wv>> be turned of by a configuration option.
 Wv>>
 Wv>> So for instance the link between Paul Quinn and Tommi Koivula,
 Wv>> who both use fastecho, drops them in both directions. Tommi was
 Wv>> thinking about moving to hpt though, the last time I spoke with
 Wv>> him about this...
 Wv>>

 PH> I'm not sure this is correct so have replied in this echoarea so Paul
 PH> et al. can comment.

 PH> I'm using FE and as far as I can see it does not strip/drop seen-by's
 PH> when messages are imported in via your Z2 feed in to my HUB system.

 PH> In fact you can tell FE to keep seen-bys on a message base by message
 PH> base basis. In my case I have everything set to retain/keep seen-by's
 PH> indefinately.

Sorry Paul, but not true. You just cannot see it happening until you check 
packets that are leaving from your system.

I investigated this, and it is also documented in fastecho.doc:

==== cut ====

    When your system acts  as outbound zonegate you  may need to  strip
all the SEEN-BY information present  in your echomail for all  messages
addressed out-of-zone.  FastEcho  is  capable  to  do  that  simply  by
enabling this feature (which is disabled by default). This can be  done
by using the flag ZONEGATE  in FEOPT. In any  case FastEcho acts as  an
inbound-zone-gate,  which  means   SEEN-BYs  will   be  stripped   when
processing EchoMail coming from another zone.

==== cut ====

Just read the "in any case"...

'Tommi

---
 * Origin: 2001:470:1f15:cb0:f1d0:2:221:6 (2:221/6)

.