Re: [leafnode-list] Problem in leafnode 2.0b8

[Matthias Andree <ma@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>]

krasel@xxxxxxxxxxxxxxxxxxxxxxxxxxxx (Cornelius Krasel) writes:

> I was thinking of removing delposted() altogether and deleting things
> in out.going only on the next run (after having checked that the
> posting has successfully been transferred to the upstream server).
> However, this would probably fail if the posting was canceled or
> superseded upstream before the next run, therefore it is probably
> not a good idea.

I already thought about that, some beta version already had that
removed, but since you refused to accept that, it went back in.

However, I'm suggesting again:

* Servers get a "fetchnews may post here flag". (Overridden to "no"
  upon encountering 201 greeting on connect.)


Some brainstorming, some features orthogonal:

* delete once a POST OK (240) is encountered

* have per-group upstreams

* per-group upstream server (wildmat/regexp?)

-- 
Matthias Andree

-- 
leafnode-list@xxxxxxxxxxxxxxxxxxxxxxxxxxxx -- mailing list for leafnode
To unsubscribe, send mail with "unsubscribe" in the subject to the list