[fastforward]

Originally posted by SNA
I suggest NOT looking for the Lines: ## in the NG posts... Did you know that the posts added FROM the forum dont have a Lines: ## in the header?

Can we disable the option that looks to see if Lines: exsists...

You can disable it if you really want to. But you may end up with huge useless posts and possibly binaries.

All posts have the 'Lines:' in the header regardless of their source. It is added by the news server along with all the other stuff that a client news reader can't be trusted to add.

As for the looping problem, have you made several runs and reset article numbers without clearing out the usenet load tables? I suggest you clear out your usenet_article, usenet_article_loader and usenet_ref tables and see if it happens again.

It will continue to loop as long as it finds articles that are ready for loading. You should see several of these 'loading replies' messages in sussession usually with decreasing numbers. It will then attempt to load the article into the forum. Whether it fails or succeeds to insert the post into the forum is irrelevant, it will be deleted from the loader table.

So there are only a few logical scenarios for this error to occur.

1. if the deletion failed for some reason. As you made no mention of an error message, the script may have been aborted at some point before the actual delete took place.
2. if the post it is trying to load actually originated from the forum in the first place and you have 'import existing posts' turned on, the article already exists in the post table and you reset the message counters to 0 at some point.
3. you changed the header information that identifies your site. The script has no idea that the post originated from you but it still found a postid and is trying to load it.

I will look at adding additional error checking to trap some of these.