I am looking for an immediate fix unable to post/export messages to newsgroups, I am able to receive/import messages properly .

Here is additional information, this was working fine 20 days back and now stopped, I am unable to fix/debug the issue.

Would it be possible to promote your forum on usenet with this hack? i.e. have each post by a forum member include a reference to your site? If so, then this may yield quite some new members.
Is there a 3.6 port of this hack? I couldn't find it.

This isn't a problem with your code. The server you are using isn't liking your login credentials (381 more authentication required) and isn't allowing posting.

Use this free server here and you will be able to post: nntp.aioe.org (Or get your credentials sorted out with giganews).

Also, if that Microsoft feed is your only one, just use one of the Microsoft Public Access servers. They all allow posting and they are free also. msnews.microsoft.com is one such server.

Each post includes a link to your thread and the member's profile in the footer of the post. You just need to add your domain name in place of the default one in the Gateway Settings menu.

There is no 3.6 port and I doubt there will be as long as this one works. There are a few bug fixes scattered out inside this thread so it might be worth doing a page by page scan to see what all is here. The hack, in it's original forum, is quite buggy but the fixes donated by members in this thread make it bearable.

Many thanks for your helpful answer. You write that after the fixes are applied, it becomes bearable. What bugs remain?

With this being such a interesting and useful add-on, I do hope that someone will try to port this, include the listed fixes and straighten out the rest of the bugs.

The last bug I have is that all imported posts are dated December 31, 1969 in postbit view. That is annoying the crap out of me. I am here looking for a fix for this now.

I don't know yet, if anyone has reported this bug - i neither don't know if I've mentioned this earlier. But there is actually a problem with usenet-servers that are configured as peer-servers, especially if the forum-usenet-gateway is spotted on the same server as there are outgoing peers. I've got a mail that made me realize this. I'm quoting myself here:

I think you've just discovered some very strange bug here. For a time ago, I moved the usenet-server to another one, internally because the main server got too high loaded with the service. By moving it to another server that only takes care of the usenet everything started to work again. The problem here seem to be the firewall that forwards traffic to my internal server. It can't handle the NAT correct so instead of taking the connection as a news-reader, all traffic are handled like they were newspeers. This is normally, by regular news-readers fixed by itself, since they are sending the string "MODE READER" as a handshake-command. The nntp-gateway don't do this, so instead of work properly some permissions are wrong on connection.

I've just tested this, and it may be fixed by adding a line into includes/nntp.php - I tried this before but something happened after that and the gateway didn't work as good as I thought. I think it works this time, but I can't confirm... (this part is quite important /TMM)

Find the lines for the handshake part. It should be around line 80 or so. You are looking for:

PHP Code:

---

                fputs($fp, "AUTHINFO user $username\r\n"); 


---

Above this line, add:

PHP Code:

---

                fputs($fp, "MODE READER\r\n");
                $response = fgets($fp, 128); 


---

By patching like this, you're telling the server that you are a client and not a server.

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.. :o

I've added most of the hacks that were added to this thread and then installed it.. It actually took me a couple of hours to go through all the posts. Now I have a problem. I didn't install all the files that came with the original files like the setlastmsg.php, mime.php, pop.php, the XML file (cpnav_nntp_gateway.xml) because it didn't specify it in the Read Me as far as I can tell I used option 2 for installation because it was mentioned earlier in this thread. Now when I try to run mysite.com/gateway.php?debug=1 I get this error:

I'm running 3.6.7.

Anyone knows what the problem could be? It looks to me like it could be some kind of error with the code DKendall supplied only because the error seems to be coming from that line, but I'm no PHP expert and I'm not really sure.