Hi Michiel,

On 2015-02-23 14:22:22, you wrote to me:

 MvdV>>>   no-autosendreq

 MvdV>>> makes it behave as it does presently. When ommitted, the *.req
 MvdV>>> file initiates the connnect on its own.

 WV>> To make it fully backwards compatible and not change the default
 WV>> behaviour, with current config files, I would suggest the keyword:

 MvdV> I am looking at it from the perspective of a new user. I have never used
 MvdV> any other BSO mailer, I have only converted my system to BSO last year.
I
 MvdV> am not all that interested how the original binkleyterm behaved.
Arguments
 MvdV> to the effect of "it has always been done that  way" do not impress me
 MvdV> much. I look at how I want it to behave now. And what I see as logical
 MvdV> behaviour is that a *.req file initates a connect all by itself. I do
not
 MvdV> know why the author of the original Binkleyterm did it different. I
think
 MvdV> it is illogical and so my preference is to forget about how it has
always
 MvdV> been done and do it different now and let new users not be bothered with
 MvdV> the old (and IMNSO wrong) way, so make the new behaviour te default.

For new users it could be made a default setting in the example config file...

 WV>>   autosendreq

 WV>> That will make it behave in the new way, when present.

 MvdV> Full backward compatibiltiy has its merits, but it can also be in the
way
 MvdV> of progress.

 MvdV> Allowing an override for the new bahaviour should be enough.

It probably won't break any old setups this way, so I tend to agree with you in
this case.

Bye, Wilfred.

--- FMail-W32-1.69.1.95-B20140716