Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Unable to read and write to newsgoup news.free.fr

  • 6 cavab
  • 0 have this problem
  • 13 views
  • Last reply by gp

more options

Good morning, I am subscribed to the news.free.fr news servers and I can access it without any problem when I am at home. But when I want to access it from outside, it is impossible with thunderbird. With seamonkey, I access it without problems from outside my home. I specify that this news server is managed by my ISP which is free.fr So there is a bug in thunderbird since with another newsreader, there are no problems. Best regards,

Good morning, I am subscribed to the news.free.fr news servers and I can access it without any problem when I am at home. But when I want to access it from outside, it is impossible with thunderbird. With seamonkey, I access it without problems from outside my home. I specify that this news server is managed by my ISP which is free.fr So there is a bug in thunderbird since with another newsreader, there are no problems. Best regards,

Chosen solution

Hi, I found the solution here (in french) : https://groups.google.com/g/fr.rec.bricolage/c/Ijk6rP3mXEE You must set the advanced preference “mailnews.nntp.jsmodule” to “false” in the config editor and restart Thunderbird. And now it works! Best regards

Read this answer in context 👍 1

All Replies (6)

more options

You told us nothing that lets us advise. Can you read a group, but not write? Please post a screenshot of the outgoing server and of the incoming server, and maybe some suggestions will surface. Thanks.

more options

Thank you for your interest in this issue. Here's a screenshot showing the last day thunderbird worked somewhere other than my home (on my laptop).

And here is the screenshot of server settings. Ports 587 and 119 do not change the problem. Which remains regardless of the port used.

more options

Hello luciole135

Port 587 don't seem to very useful, I could not connect either from the inside of Free network nor from the outside, so I can't see why you did set it - while port 139 allows for connect from both inside or outside.

Could you try to set the port to 139 and enable debugging ?

Try to set mailnews.smtp.loglevel to 'all' in the config editor (Options / 'general' tab - don't forget to validate by using the checkmark) and see the result of a connection attempt in the Error console (Tools / developer tools).

If what you see is not clear to you, post it here (try to do a copy/paste instead of a screen shot, first it's easier to edit personal information, second you can show more information).

Modified by gp

more options

Hello and thank you for your interest in this issue. I put port 139 and unfortunately it doesn't change anything.

Not without difficulties, I found how to access the configuration editor and I set `mailnews.smtp.loglevel` to 'all' .

Unless I'm mistaken, I activated the debug and here is what I get:

mailnews.nntp: Got an error id=-304 NntpClient.jsm:813:18

   _actionError resource:///modules/NntpClient.jsm:813
   _onData resource:///modules/NntpClient.jsm:207
   openWindowPrompt resource:///actors/PromptParent.jsm:164
   receiveMessage resource:///actors/PromptParent.jsm:108
   openPrompt resource://gre/modules/Prompter.jsm:1182
   openPromptSync resource://gre/modules/Prompter.jsm:1046
   alert resource://gre/modules/Prompter.jsm:1329
   _actionError resource:///modules/NntpClient.jsm:827
   _onData resource:///modules/NntpClient.jsm:207
more options

Seçilmiş Həll

Hi, I found the solution here (in french) : https://groups.google.com/g/fr.rec.bricolage/c/Ijk6rP3mXEE You must set the advanced preference “mailnews.nntp.jsmodule” to “false” in the config editor and restart Thunderbird. And now it works! Best regards

more options

Great for your solution. By the way, it may point to a bug in Thunderbird because as far as I know, JS is the future and if you disable it, you get legacy code (that may disappear at some point).

I add only that I erred totally in my post, sorry. If anyone is reading this thread, the port for newsgroup is 119, NOT 139.