Hello Michiel!

25 Feb 15 17:35, you wrote to me:

 MvdV> Yes, just like it does with anything else in the outbound, exept hold.

 KE>> It may seem irrelevant but in a POTS system it is not.

 MvdV> We are not discussing POTS systems. We are discussing binkd, the IP
 MvdV> mailer.

 You are discussing Binkd and that is your problem. But you are messing with
 the content of a filestructure and conventions in that structure. The use of
that structure is not limited to BINKD.

 There are systems in the fidonet hyrarchy that support more capabilities
 that just BINKD. Those systems often use more than one mailer to support
 opther protocols and POTS. POTS may not be on your radar anymore, but it is
 still used.

 These different mailers can work together, because they all use the same
 file structure and file conventions. If you start messing with one, because
 you think your logic is better, than what has grown over time, then you
 wreck the cooperation with other mailers on systems that are more complex
 than pseudo PVT.

 KE>> "Fixing" a perceived flaw should not break requirements of older
 KE>> systems.

 MvdV> That is why I propose to let this be an addition to binkd.  Something
 MvdV> that has to be configured by setting the autosedreq keyword in the
 MvdV> configuration.

 Currently BINKD is agnostic about the file request system that uses *.req
 files, or any of the other file request methods that has come to life in
 Fidonet.
 You want to add unneeded complextity for one of these methods, that has your
 fancy.

 KE>> The FTSC documents how things work, so others can build
 KE>> compatible software.

 MvdV> That is the general idea...

 Well, then don't change the rules half way the game, retrofitting is not
 an option.

Kees

--- GoldED+/LNX 1.1.5