[TMM-TT]

Originally Posted by KidCharlemane

This fix did not work for me but I emailed you directly about it.

I think that part is just a lastread-issue. Because of the local change of servers the lastread data is probably mismatching with yours. When the gateway connects to the server it reads (I think) the firstpost-lastpost-information from the server (211*) and compares it with the data stored in the database. At least it's something like that. If your value is larger than the lastpost-data sent by server (which it probably is what happened here**), the gateway won't download any new articles, since it thinks that you already have them. Resetting that value in the database might help, with a small risk that there will pop up some dupes.


**) I run a larger server and a smaller, and currently, traffic are forwarded (with a shitty NAT-rule) to the smaller due too high load on the larger. The smaller, unfortunately, have other data stored, that makes the counters differ a bit (and that is bad too)

*) When fetching posts from usenet this command is sent to the server
GROUP news.software.nntp
The server answers with
211 41 63 103 news.software.nntp

Where the data received stands for (from the example):
41 = estimated number of articles in group, 63 = first article number in the group, 103 = last article number in the group

I'm not sure if the gateway does like this, because I didn't find anything about it in the source, but since there is a lastread-field in the admincp, some similar calculations are made, that for the moment prevents new posts to reach you... And yes, that is probably my fault..