NNTP real-time scan causing problems

I’ve had to turn the NNTP real-time scan feature off as it was causing strange behaviour when reading Usenet postings. The body of the post would be the same for every post I read - the same as the first post, that is. I reported this to NewsDemon and they told me that there is a problem with the latest version of Avast! which is causing this.

I’d like to think that all NNTP traffic is being scanned , like everything else, so is there any chance that this will be resolved before I remove Avast! and switch to an alternative A/V product?

Avast! version 6.0.1367 on Vista Home Premium SP2.

I’ll throw here an idea, but I have no clue if it is going to solve anythig for you.

Try web shield → expert settings → “well known browsers only”.

Then delete your firewall rules related to avast and/or to the program(s) having some problem. Save and reboot.

Please report back.

Except it’s the Mail Shield which applies to NNTP traffic, so I don’t see why this change would have any effect.

The reason I suggested web shield settings as a (remote) possibility to look into is because the latest stable web shield version (6.0.1xxx) was blocking more internet traffic than just web browsers, and some reports were somehow strange.

Changing the setting and testing it is so simple and fast that it was worth mentioning.

Deleting the firewall rules would take longer than the web shield change :), but it is still relatively easy to test.

Besides those, you could try temporarily disabling shields one at a time (including mail shield specifically) and see if the behavior changes.

Do all these settings change on the fly? I seem to recall that as soon as I unchecked the NNTP box it started working correctly.

I just now try every combination of ‘Web Shield well-known browsers’ and ‘NNTP scanning’ and Thunderbird worked fine every which way. I have to say that the original problem sometimes went away for a short while without me having to do anything. So I’m still not really sure what the problem is - except that Avast! is the problem. NewsDemon told me that it’s the NNTP setting, and I presume they know what they’re talking about.

I take that back. The only way to get consistently correct results is to turn off NNTP scanning.

Bummer.

I’ve reported this thread to a Moderator hopefully someone from Avast will reply. :slight_smile: