On Tue, 14 May 2013, Paul Quinn wrote to Rj Clay:

 ml>> that depends on the tosser's method of dupe detection...

 RC>    True but in this case none of the messages would be in any other
 RC> echo...

 PQ> Smack me if I'm wrong...  I think this aspect is weak point for
 PQ> MBSE: the handling of dupes/bad mail.  IIRC there ain't no option
 PQ> to 'toss from bad', after configuring new areas.  So, you are at
 PQ> the mercy of any dupes in the dupe database.

exactly and this isn't the only system aflicted with this problem...

synchronet (actually the sbbsecho tosser) is another one... it deletes what
it considers to be duplicates with no facility for saving them to a special
area for human perusal... the only real solution to this is to use a script
that deletes the dupe databases before each round of tossing performs the
toss and then deletes the dupe bases again after the toss... this second
deletion so that other methods of message importing (QWK, news) don't get
caught with possibly false dupes... it barely has the ability to save
messages for areas not defined and no good way to move them into the proper
area once it is defined... i'm ever hopefuly that this will be remedied...
i'd contribute if i were a C coder but since i'm not, i can't... all i can
do is point out what is desired and how it would be done...

i'm sure there are other tossers with similar aflictions, as well... 

)\/(ark

--- FMail/Win32 1.60