Sujet : Re: power loss while receiving news
De : jesse.rehmer (at) *nospam* blueworldhosting.com (Jesse Rehmer)
Groupes : news.software.nntpDate : 22. Apr 2024, 00:33:31
Autres entêtes
Organisation : BWH Usenet Archive (https://usenet.blueworldhosting.com)
Message-ID : <v047ob$27o9$1@nnrp.usenet.blueworldhosting.com>
References : 1 2 3 4 5
User-Agent : Usenapp for MacOS
On Apr 21, 2024 at 3:13:42 PM CDT, "Julien ÉLIE"
<
iulius@nom-de-mon-site.com.invalid> wrote:
Hi Wolfgang,
$ grephistory '<q34v5519vru4fco5d14eradn3iksal3ihr@4ax.com>'|sm
sm: could not retrieve @03024359434E475331000F8053BA00000001@
I would then just suggest to run again innxmit on the sending server
for these 675 articles.
As the articles seem to be known in the history file, the target server
will reject them as duplicates, even if they don't exist in the spool.
Oh, yes, you're totally right. These Message-IDs must be removed from
the history file before.
BTW: Is there another way to remove entries from history except manually
deleting them?
What I usually do to achieve that is:
1- setting /remember/ to 0 in expire.ctl;
2- running the expire process ("news.daily notdaily" called with the
same parameters as in crontab);
3- setting /remember/ to its previous value (11 by default).
I'm not aware of another way to totally remove entries from the history
file (it somehow needs rebuilding). If you see another method with the
current programs shipped with INN, I would be glad to hear.
Can you not remove the lines from "history" and then run makedbz?