There are a few options missing in UE that would make it the perfect newsreader for me.
1. An option to automatically save incompete messages. I very frequently download articles that are near the retention limit of my newsserver. Therefore I know that there is no chance of ever downloading the missing articles and would like to always save incompletes rather than have them held in the ? queue.
2. If I close UE while posting a message, the next time I open UE, it does not try to repost the message that was interrupted when UE was closed. Instead, it reports an error and continues with the next segment.
Feature requests
Re: Feature requests
OK, I guess (neutral). I notice the 'sort by date' doesn't always worketag wrote: 1. An option to automatically save incompete messages. I very frequently download articles that are near the retention limit of my newsserver. Therefore I know that there is no chance of ever downloading the missing articles and would like to always save incompletes rather than have them held in the ? queue.
Good, But; how do we know when NO more parts will come up
on the server. I suggest re-saving articles with the arrival of
all additional parts etc.
2. If I close UE while posting a message, the next time I open UE, it does not try to repost the message that was interrupted when UE was closed. Instead, it reports an error and continues with the next segment.
Good, would like it to remember which folders (groups/folder) I have
open and restore the view also.
especially in the TaskManager views. I like the most recent 'thing' at
the top of the display, descending date order.
UE is looking great Alex, keep up the outstanding work for us
it will save incompletes if there is no error, if there is an error you can save them from the error queue or from the header view (invoke 'save attachments'). in principle it could easily put in the save queue along with the error pane, but currently there is no such option (also it is not exactly clear what to do with failed parts if you set delete incomlete bodies since it is not always expired articles).
with posting during the shutdown it may happen that the part is actually posted but the notification that the post is complete doesn't make it since ue shutdowns as soon as you close it not waiting until the completion of current tasks (article body and post tasks are just retried on restart), so just ignore the error message, it will fail reposting the segment but will continue posting other segments (the server error should be like the message-id already exists, just ignore it).
with posting during the shutdown it may happen that the part is actually posted but the notification that the post is complete doesn't make it since ue shutdowns as soon as you close it not waiting until the completion of current tasks (article body and post tasks are just retried on restart), so just ignore the error message, it will fail reposting the segment but will continue posting other segments (the server error should be like the message-id already exists, just ignore it).