Avast WEBforum

Consumer Products => Avast Mac Security => Topic started by: tumic on January 02, 2013, 04:33:17 PM

Title: Beta
Post by: tumic on January 02, 2013, 04:33:17 PM
As already mentioned here on the avast! forum, we have redesigned the handling
of TLS/SSL connections in the mail/web shield for the next program update. Under the
following link you can find a beta version of avast! for mac with this changes. It will
specially suit those people, who have problems with the current solution.

To use the beta version, simple uninstall the current version using the menu entry in
the avast! GUI and install the beta from the downloaded archive. Note, that this
will not keep any configuration from the old version like a "standard" program
update.

SSL should be NOT disabled in the mail server settings of your mail client anymore,
when using the beta (and any later version). Please check the mail account configuration
and alternatively switch SSL back to "enabled".


Download (Updated 18.2.2013):
http://public.avast.com/~tuma/avast-38330-AAFM.dmg (http://public.avast.com/~tuma/avast-38330-AAFM.dmg)

Technical info:
http://public.avast.com/~tuma/techinfo/ (http://public.avast.com/~tuma/techinfo/)
Title: Re: Beta
Post by: pnoguchi on January 03, 2013, 12:08:22 AM
This beta seems to solve the email conflict, but still causes Chrome to spike its activity when accessing websites with resulting slowness. Looking forward to official release

Title: Re: Beta
Post by: tumic on January 03, 2013, 11:19:43 AM
The "slowness" problem is a fileshield issue (you can "prove" this by disabling the fileshield temporary), not a webshield issue. We are aware of this issue and are working on fileshield speed improvements, but this beta (37943) does not contain any fileshield changes.
Title: Re: Beta
Post by: Muetze on January 03, 2013, 01:16:26 PM
Hi,

after installing Beta Version I have following issue:
Chrome WebRep plug-in Fehlercode: 7013

I cant see that avast scanning outgoing msg email.
Incoming is working very well now and much better than before without any modification.
Title: Re: Beta
Post by: pnoguchi on January 03, 2013, 04:11:01 PM
The "slowness" problem is a fileshield issue (you can "prove" this by disabling the fileshield temporary), not a webshield issue. We are aware of this issue and are working on fileshield speed improvements, but this beta (37943) does not contain any fileshield changes.

I understand that from many other posts. Question is, why are Safari and Firefox not so affected by fileshield? They both run faster, and do not seem to choke on some urls?

-P
Title: Re: Beta
Post by: tumic on January 03, 2013, 04:43:00 PM
Hi,

after installing Beta Version I have following issue:
Chrome WebRep plug-in Fehlercode: 7013

I cant see that avast scanning outgoing msg email.
Incoming is working very well now and much better than before without any modification.

Thanks for the report. The webRep plug-ins are kind of "under construction" in the beta, so there may be some issues with them. However, this will be fixed in the final release.

Regarding the outgoing email scan - avast! for mac has never checked outgoing mail traffic and will not do so, at least not in the nearest future. The purpose of the product is to protect you from the bad world out there, not  the other way, so this should be not a such big issue... ;-)
Title: Re: Beta
Post by: tumic on January 03, 2013, 04:52:40 PM
I understand that from many other posts. Question is, why are Safari and Firefox not so affected by fileshield? They both run faster, and do not seem to choke on some urls?

This is still under examination here, but the most probable explanation is that Chrome simple accesses more/bigger files (cache) than the other browsers.
Title: Re: Beta
Post by: specimen9999 on January 04, 2013, 07:30:51 PM
After reading the technical info, I'm a bit concerned about the security implications. Thru the installation of the SSL CA Certificate in the Keychain the user is giving Avast! and any other program that manages to reverse engineer/hack this process complete control over the encryption trust chain, since technically Avast e resigning the connections with this certificate, if this process is somewhat hacked it could validate any otherwise untrusted connection.
I'm also giving quite a lot of trust to Avast!. The process detailed would be a quite perfect trojan horse and a smart way to circumvent the trust chain of SSL certificates.

We are creating, thru this process, a single point of failure in the trust chain, I would like to know what measures does Avast implement to make sure we aren't in fact being more vulnerable by creating a single point of failure, by exchanging the trust in secure connections and things like prevention of identity theft, for the ability to virus scan the contents of secure connections. Because if I have to pick between the two I rather have my trust chain intact as there are other ways to control viruses (File scan).

Another question is: Is the certificate that is inserted into System Root generated locally and different for every installation or it's the same cert for everyone?
Title: Re: Beta
Post by: pnoguchi on January 04, 2013, 08:10:35 PM
Having briefly commented a few times, with amazingly quick, to the point responses, after more extensive testing the beta I have the following comments:
-regarding the mailshield, the ssl/tls flag does not appear as before with the release version. However my email response was almost totally blocked with access to my mail server timing out, until I set the fileshield to exclude my email client AND its associated support directories. I am guessing that this probably negates the AV scan on my mail. Based on the technical info, my keychain does indeed have the avast! trusted CA inserted, so that part works
-regarding installation, this beta still leaves the avast Application Support directory locked and not accessible from my account (which is an administrative account). Adding and admin r/w permission allows me to see the otherwise nonaccesible directory. I don't know if this is a "bug" or "feature", but it makes avast! free for mac less transparent to me.
-Do appreciate the substantial investment by avast for the Mac platform. I realize that the Mac OSX is by far still a  small blip compared to the various Microsoft OSes.

-P
Title: Re: Beta
Post by: specimen9999 on January 04, 2013, 10:02:58 PM
I just tried this beta and Mail.app immediately failed to connect to a private mail server, once I changed it back to use SSL, that uses a self signed cert that is already added to the keychain (and was working on the previous version of Avast!). :(
Title: Re: Beta
Post by: GeoffBur on January 06, 2013, 10:55:52 PM
One thing I've noticed, that if "scan secured connections" is set then Dropbox cannot connect to the server.
Title: Re: Beta
Post by: specimen9999 on January 07, 2013, 02:46:38 AM
One thing I've noticed, that if "scan secured connections" is set then Dropbox cannot connect to the server.


I suggest you read the "Technical Info" link in the first post.
Title: Re: Beta
Post by: tumic on January 07, 2013, 11:28:42 AM
Thanks for examining and testing the beta specimen9999.

After reading the technical info, I'm a bit concerned about the security implications. Thru the installation of the SSL CA Certificate in the Keychain the user is giving Avast! and any other program that manages to reverse engineer/hack this process complete control over the encryption trust chain, since technically Avast e resigning the connections with this certificate, if this process is somewhat hacked it could validate any otherwise untrusted connection.
I'm also giving quite a lot of trust to Avast!. The process detailed would be a quite perfect trojan horse and a smart way to circumvent the trust chain of SSL certificates.

We do not deny, that the process we are now using is a significant intervention into the SSL handling on the machine, but if done correct, it should not bring any security issues. After all, it is the mechanism that all antivirus software capable of scanning secured connections is using.

Also note, that to hack the process, you would need root rights. And a malware, that has managed it to run with root rights on your machine has already won and can use a plenty of other ways to affect SSL handling (e.g. install its own certificate into the system keychain).


...there are other ways to control viruses (File scan).

The problem is, that a "traditional" file scan will not protect you from a big group of malware attacking the web browsers/web content. That's why the web shield is there.

Another question is: Is the certificate that is inserted into System Root generated locally and different for every installation or it's the same cert for everyone?

As described in the technical info, the certificate is generated on install/update and is "uniq" for every installation.
Title: Re: Beta
Post by: tumic on January 07, 2013, 11:32:24 AM
One thing I've noticed, that if "scan secured connections" is set then Dropbox cannot connect to the server.


I suggest you read the "Technical Info" link in the first post.

Just a note - there will be predefined exclusions for such software in the final release.
Title: Re: Beta
Post by: tumic on January 07, 2013, 11:44:36 AM
-regarding the mailshield, the ssl/tls flag does not appear as before with the release version. However my email response was almost totally blocked with access to my mail server timing out, until I set the fileshield to exclude my email client AND its associated support directories. I am guessing that this probably negates the AV scan on my mail. Based on the technical info, my keychain does indeed have the avast! trusted CA inserted, so that part works

Poor fileshield performance on some mailbox files is a known issue and we are working on a fix. However I can not guarantee that this will be solved in the next release. The only think you can currently do is to exclude the folders from the fileshield scan as you did.

-regarding installation, this beta still leaves the avast Application Support directory locked and not accessible from my account (which is an administrative account). Adding and admin r/w permission allows me to see the otherwise nonaccesible directory. I don't know if this is a "bug" or "feature", but it makes avast! free for mac less transparent to me.

The Application Support directory is not user readable by design. The reason is, that there are stored some files, that may not be accessible for user processes, e.g. the private keys for the CA certificates.
Title: Re: Beta
Post by: specimen9999 on January 07, 2013, 01:46:38 PM
Thank you for your answers, tumic.

Still one little question remains, the situation with self signed certs:

Mail.app immediately failed to connect to a private mail server using a self signed cert, already on the Keychain, once I changed it back to use SSL (this was working on the previous version of Avast!).
Title: Re: Beta
Post by: tumic on January 07, 2013, 02:44:21 PM
Thank you for your answers, tumic.

Still one little question remains, the situation with self signed certs:

Mail.app immediately failed to connect to a private mail server using a self signed cert, already on the Keychain, once I changed it back to use SSL (this was working on the previous version of Avast!).

This is a bug, thanks for reporting. Connections with self signed certificates were dropped, instead of resigning with the "avast! untrusted CA" certificate. The issue was fixed in build 37968 which is available now under the download link. Please try the new beta and see if it works.
Title: Re: Beta
Post by: specimen9999 on January 07, 2013, 04:51:24 PM
Thank you for your answers, tumic.

Still one little question remains, the situation with self signed certs:

Mail.app immediately failed to connect to a private mail server using a self signed cert, already on the Keychain, once I changed it back to use SSL (this was working on the previous version of Avast!).

This is a bug, thanks for reporting. Connections with self signed certificates were dropped, instead of resigning with the "avast! untrusted CA" certificate. The issue was fixed in build 37968 which is available now under the download link. Please try the new beta and see if it works.

Ok, testing it now.
Mail.app now asked if I wanted to trust this certificate, "avast! untrusted CA", for connecting to this server, I checked "always trust..." and now it works.
One concern thou, this means that ANY self-signed certificate will be accepted for connecting to this particular server? Since I trusted the ""avast! untrusted CA" any untrusted certificate can now be used and not only the certificate I had downloaded to my keychain?

Can't avast sign with the trusted CA if the self-signed certificate is present on the keychain?

I'm wondering about the possibility of a middle man attack going unnoticed if any self-signed certificate is used by the attacker and not the specific one I downloaded from my private mail server.
Title: Re: Beta
Post by: specimen9999 on January 07, 2013, 05:50:56 PM
I have one idea, maybe this is what avast! is already doing but here it goes:

When signing with the avast untrusted CA, generate a new cert for each singular self-signed cert for each specific domain, this way, when connecting to a specific domain that has had its cert changed the user will be prompt again for trusting/untrusting the new avast untrusted CA generated cert.
Title: Re: Beta
Post by: specimen9999 on January 08, 2013, 06:28:01 PM
Another problem, this, the SSL scanning, apparently does not work well with virtual machines running under OS X.
Probably means the same certificate has to be installed in the Guest OS (Windows in this case).
Title: Re: Beta
Post by: tumic on January 08, 2013, 06:40:06 PM
Mail.app now asked if I wanted to trust this certificate, "avast! untrusted CA", for connecting to this server, I checked "always trust..." and now it works.
One concern thou, this means that ANY self-signed certificate will be accepted for connecting to this particular server? Since I trusted the ""avast! untrusted CA" any untrusted certificate can now be used and not only the certificate I had downloaded to my keychain?

Can't avast sign with the trusted CA if the self-signed certificate is present on the keychain?

If you have the certificate in your keychain (either "System Roots" or "System"), than the connection should be resigned with the "avast! trusted CA" certificate that is also in the keychain. so there is something wrong...

I'm wondering about the possibility of a middle man attack going unnoticed if any self-signed certificate is used by the attacker and not the specific one I downloaded from my private mail server.

All the clients I have tested (Safari, Mail, Firefox, Google Chrome) save security exceptions for the concrete host certificate, not the CA certificate that has signed it. And I'm pretty sure that any sane client does it the same way.  This means that if you add an exception for host xxx (signed by the avast! untrusted CA), the client will not accept host yyy (also signed with the untrusted CA).
Title: Re: Beta
Post by: tumic on January 08, 2013, 06:43:01 PM
Another problem, this, the SSL scanning, apparently does not work well with virtual machines running under OS X.
Probably means the same certificate has to be installed in the Guest OS (Windows in this case).

Exactly. The applications in the guest OS must also trust the "avast! trusted CA".
Title: Re: Beta
Post by: specimen9999 on January 08, 2013, 06:44:29 PM
Mail.app now asked if I wanted to trust this certificate, "avast! untrusted CA", for connecting to this server, I checked "always trust..." and now it works.
One concern thou, this means that ANY self-signed certificate will be accepted for connecting to this particular server? Since I trusted the ""avast! untrusted CA" any untrusted certificate can now be used and not only the certificate I had downloaded to my keychain?

Can't avast sign with the trusted CA if the self-signed certificate is present on the keychain?

If you have the certificate in your keychain (either "System Roots" or "System"), than the connection should be resigned with the "avast! trusted CA" certificate that is also in the keychain. so there is something wrong...

I'm wondering about the possibility of a middle man attack going unnoticed if any self-signed certificate is used by the attacker and not the specific one I downloaded from my private mail server.
But I do have the self-signed cert in my keychain, which was working in the non-beta version of avast!.
Title: Re: Beta
Post by: specimen9999 on January 08, 2013, 06:50:14 PM
Another problem, this, the SSL scanning, apparently does not work well with virtual machines running under OS X.
Probably means the same certificate has to be installed in the Guest OS (Windows in this case).

Exactly. The applications in the guest OS must also trust the "avast! trusted CA".
This is not working well at all, I exported the cert from my keychain and installed it as a CA and Microsoft Update fails and a bunch of other apps.

I would love if there was a way not to scan the connections that go into Virtual Machines.
Title: Re: Beta
Post by: tumic on January 08, 2013, 06:59:09 PM
This is not working well at all, I exported the cert from my keychain and installed it as a CA and Microsoft Update fails and a bunch of other apps.
I would love if there was a way not to scan the connections that go into Virtual Machines.

Those apps most probably belong to the same category as Dropbox - they come with hard-coded certificates (do not use the system keychain).
Title: Re: Beta
Post by: specimen9999 on January 08, 2013, 07:03:21 PM
This is not working well at all, I exported the cert from my keychain and installed it as a CA and Microsoft Update fails and a bunch of other apps.
I would love if there was a way not to scan the connections that go into Virtual Machines.

Those apps most probably belong to the same category as Dropbox - they come with hard-coded certificates (do not use the system keychain).

We are talking about Windows here now (the Guest OS), it would be much much more simpler if there was a way to disable scanning SSL connections for Virtual Machines.
Title: Re: Beta
Post by: tumic on January 08, 2013, 07:14:58 PM
We are talking about Windows here now (the Guest OS), it would be much much more simpler if there was a way to disable scanning SSL connections for Virtual Machines.

I'm also talking about Windows. It is likely, that Windows Update does not use the Windows's system certificate storage for security reasons.

Process based exceptions would be a nice feature, but they will sure not be implemented in the near future as the network shield architecture is network layer based (the shield can be used for example on a router/gateway) so there is no info about the process available.
Title: Re: Beta
Post by: specimen9999 on January 08, 2013, 07:31:08 PM
We are talking about Windows here now (the Guest OS), it would be much much more simpler if there was a way to disable scanning SSL connections for Virtual Machines.

I'm also talking about Windows. It is likely, that Windows Update does not use the Windows's system certificate storage for security reasons.

Process based exceptions would be a nice feature, but they will sure not be implemented in the near future as the network shield architecture is network layer based (the shield can be used for example on a router/gateway) so there is no info about the process available.

What about having a set or sets of pre-defined domain scan exclusions?
Title: Re: Beta
Post by: specimen9999 on January 09, 2013, 06:55:09 PM
Mail.app now asked if I wanted to trust this certificate, "avast! untrusted CA", for connecting to this server, I checked "always trust..." and now it works.
One concern thou, this means that ANY self-signed certificate will be accepted for connecting to this particular server? Since I trusted the ""avast! untrusted CA" any untrusted certificate can now be used and not only the certificate I had downloaded to my keychain?

Can't avast sign with the trusted CA if the self-signed certificate is present on the keychain?

If you have the certificate in your keychain (either "System Roots" or "System"), than the connection should be resigned with the "avast! trusted CA" certificate that is also in the keychain. so there is something wrong...

I'm wondering about the possibility of a middle man attack going unnoticed if any self-signed certificate is used by the attacker and not the specific one I downloaded from my private mail server.
But I do have the self-signed cert in my keychain, which was working in the non-beta version of avast!.
As for the self-signed cert problem, I deleted the cert and started over again by getting the cert from the server into my System Keychain, rebooted, but still, Mail.app asks for trusting "avast untrusted CA signed cert". On Safari, strangely, the connection is trusted without prompting but it's signed with self-signed cert on my system keychain and neither with avast trusted or untrusted CA, and yes, I made sure there are no exceptions in vast and that it's scanning web secure connections.
So something's weird going on with self-signed certs.
Title: Re: Beta
Post by: pnoguchi on January 10, 2013, 04:46:59 AM
Using the newest beta (37968), I find I can install WebRep in Firefox 18, Safari 5.1.7, but not in chrome 23 which simply states that the plugin cannot be installed.

-P
Title: Re: Beta
Post by: tumic on January 10, 2013, 04:16:05 PM
Broken WebRep plugins are a known issue, it will be fixed in the final release.
Title: Re: Beta
Post by: specimen9999 on January 11, 2013, 01:37:21 PM
Another problem, this time with signing into a live.com account (hotmail, messenger...) in Firefox, the avast! tusted CA cert is installed in Firefox, and works with other secure connections, but for some reason doesn't work in live.com, the window just stays blank while waiting for something.
In Safari it works fine. The only way to have this working in Firefox was by adding login.live.com to the exclusion list.

BTW, can't we use wildcards like *.live.com in exclusions? It would be so much simpler.

As for the self-certificate problem I'm not sure you considered it a bug or not?
Title: Re: Beta
Post by: specimen9999 on January 13, 2013, 07:58:57 PM
Using build 37988 (what is the changelog of this build?)

I decided to turn off SSL scanning for http connections, the behaviour is just too erratic, specially under firefox, with live.com and facebook.com (some images not appearing).
Title: Re: Beta
Post by: tumic on January 14, 2013, 11:14:30 AM
Using build 37988 (what is the changelog of this build?)

The shield/SSL scan configuration logic in the avast! preferences (Preference Pane) is fixed in build 37988.
Title: Re: Beta
Post by: tumic on January 14, 2013, 07:21:12 PM
Using build 37988 (what is the changelog of this build?)

I decided to turn off SSL scanning for http connections, the behaviour is just too erratic, specially under firefox, with live.com and facebook.com (some images not appearing).

The problems with live.com are caused by their broken server not capable to work with openssl > 1.0.1 that has support for TLS v1.1 and v1.2. (avast uses the latest openssl library - 1.0.1c). We will either search for a workaround for this like disabling TLS 1.1 and 1.2 or simply add the known broken servers (another one is webmail.centrum.cz - the same MSN technology) to the exclusion list.

I can however not see any problems with facebook. Can you provide more info on the issues with facebook?
Title: Re: Beta
Post by: specimen9999 on January 14, 2013, 07:31:23 PM
I can however not see any problems with facebook. Can you provide more info on the issues with facebook?

The issue I had with facebook.com was with images while using Firefox, some images (in news feed) were not appearing (just their placeholder), the images, AFAIK, are hosted on the akamai network in: fbcdn-sphotos-b-a.akamaihd.net, using https also.
Title: Re: Beta
Post by: tumic on January 15, 2013, 03:39:22 PM
There is an updated version (38024) available that fixes the issues with broken HTTPS servers (live.com).
Title: Re: Beta
Post by: specimen9999 on January 16, 2013, 09:16:01 PM
There is an updated version (38024) available that fixes the issues with broken HTTPS servers (live.com).

Using Firefox, works better, I can now open mail.live.com. Unfortunately, Messenger, via web on the live.com page, doesn't work, it just sits there waiting for sign in. Turning off secure connection scanning and it works.
Title: Re: Beta
Post by: Fenikkusu on January 28, 2013, 02:30:09 AM
Version Info
Beta 38024,
10.8.2

GMail Settings:
Server imap.googlemail.com:993,SSL/TSL

Whenever my gmail account attempts to connect to the server, it ends up timing out. Occasionally it will succeed fine, but for the most part it will not connect. Disabling the Mail shield will allow it to work fine, so it's not the connection. I've disabled the compression setting and it still is doing it. My other account works fine.

(Had to use beta due to 'Unable to verify email server' error)
Title: Re: Beta
Post by: specimen9999 on January 28, 2013, 03:06:46 AM
Version Info
Beta 38024,
10.8.2

GMail Settings:
Server imap.googlemail.com:993,SSL/TSL

Whenever my gmail account attempts to connect to the server, it ends up timing out. Occasionally it will succeed fine, but for the most part it will not connect. Disabling the Mail shield will allow it to work fine, so it's not the connection. I've disabled the compression setting and it still is doing it. My other account works fine.

(Had to use beta due to 'Unable to verify email server' error)

Does that also occur if you use imap.gmail.com as the server address (it's the one referenced in google support docs and the one I use, it works fine for me with the beta and before the beta).
Title: Re: Beta
Post by: tumic on January 28, 2013, 10:19:04 AM
GMail Settings:
Server imap.googlemail.com:993,SSL/TSL

Whenever my gmail account attempts to connect to the server, it ends up timing out. Occasionally it will succeed fine, but for the most part it will not connect. Disabling the Mail shield will allow it to work fine, so it's not the connection. I've disabled the compression setting and it still is doing it. My other account works fine.

Are there any interresting messages in the system log file (/var/log/system.log)?
Title: Re: Beta
Post by: Fenikkusu on January 28, 2013, 03:27:07 PM
Version Info
Beta 38024,
10.8.2

GMail Settings:
Server imap.googlemail.com:993,SSL/TSL

Whenever my gmail account attempts to connect to the server, it ends up timing out. Occasionally it will succeed fine, but for the most part it will not connect. Disabling the Mail shield will allow it to work fine, so it's not the connection. I've disabled the compression setting and it still is doing it. My other account works fine.

(Had to use beta due to 'Unable to verify email server' error)

Does that also occur if you use imap.gmail.com as the server address (it's the one referenced in google support docs and the one I use, it works fine for me with the beta and before the beta).

I tried this and everything started working fine. Thank you.

GMail Settings:
Server imap.googlemail.com:993,SSL/TSL

Whenever my gmail account attempts to connect to the server, it ends up timing out. Occasionally it will succeed fine, but for the most part it will not connect. Disabling the Mail shield will allow it to work fine, so it's not the connection. I've disabled the compression setting and it still is doing it. My other account works fine.

Are there any interresting messages in the system log file (/var/log/system.log)?

I took a look at the logs and found this:

Jan 28 09:22:11 mac com.avast.proxy[1540]: Error reading receive buffer: read(): Connection reset by peer
Jan 28 09:22:50 --- last message repeated 1 time ---
Jan 28 09:22:50 mac com.avast.proxy[1540]: Error reading receive buffer: read(): Connection reset by peer
Jan 28 09:23:15 mac com.avast.proxy[1540]: Defective IMAP request!

I don't really understand it myself. Thunderbird auto-used the googlemail.com domain, and this worked correctly when the mail shield is down. Using the gmail.com instead seems to work properly, so I don't really know what is going on.

Edit
======
On a side note, I'm noticing that my college email account doesn't appear to be going through avast at all. I'm not seeing any bars coming in on avast. Is there any way to review this? Other than the server domain and what not, the settings are the same.

Edit 2
======
Sent myself a test email and checked and it is scanning. Apparently it knew it had already scanned the previous emails...Though I'm not sure if this is a good thing or a bad thing because in theory it might be possible to spoof avast into thinking the email is valid when it really isn't...
Title: Re: Beta
Post by: Fenikkusu on February 01, 2013, 07:25:37 AM
After a trial run I've found that the imap.gmail.com setting returns the same senario of timing out. The errors in the log are still the same.
Title: Re: Beta
Post by: joelw135 on February 01, 2013, 07:41:31 PM
Installed the Beta today, no more pop=ups with SSL message, but I can't connect to IMAP server any ideas?  When Mail protection is on Thunderbird connection to IMAP times out or just doesn't connect. If I turn protection off mail on Thunderbird works again.
Title: Re: Beta
Post by: tumic on February 02, 2013, 06:22:36 PM
Installed the Beta today, no more pop=ups with SSL message, but I can't connect to IMAP server any ideas?  When Mail protection is on Thunderbird connection to IMAP times out or just doesn't connect. If I turn protection off mail on Thunderbird works again.

See the techinfo for explanation. However in the final release the required certificate will be added automatically to Thunderbird (as well as Firefox).
Title: Re: Beta
Post by: joelw135 on February 02, 2013, 06:31:51 PM
I have imported the certificate to both Firefox and Thunderbird but I still don't receive mail. I turned off Little Snitch Network monitoring but that didn't help. What next?
Title: Re: Beta
Post by: joelw135 on February 03, 2013, 04:45:49 PM
New problem, with Avast Beta (Latest Version) every-time I try to do anything in Thunderbird I get the spinning ball. If I type an email for every word I type the ball spins and there is a long delay before the word shows on the screen. It happens when even selecting a folder within Thunderbird.  So with Mail protection I can't get mail and even with it turned off I can't type. As soon as I removed the beta everything was back to normal.
Title: Re: Beta
Post by: tumic on February 04, 2013, 06:39:57 PM
I have imported the certificate to both Firefox and Thunderbird but I still don't receive mail. I turned off Little Snitch Network monitoring but that didn't help. What next?

That's strange, it should work, when the certificate is imported. Are there any error messages in the system log file (/var/log/system.log)?
Title: Re: Beta
Post by: joelw135 on February 04, 2013, 07:18:41 PM
No errors show in the system log.
Title: Re: Beta
Post by: Fenikkusu on February 04, 2013, 11:30:41 PM
I've tried as well and continue to get the 'Invalid IMAP Request' error. This occurs only on my GMail account, not my other accounts that also use SSL.
Title: Re: Beta
Post by: specimen9999 on February 04, 2013, 11:38:07 PM
I've tried as well and continue to get the 'Invalid IMAP Request' error. This occurs only on my GMail account, not my other accounts that also use SSL.

Is the port correctly configured on the email client? i.e. 993 SSL
Title: Re: Beta
Post by: joelw135 on February 05, 2013, 12:32:24 AM
Yes incoming set to 993. Is there another Beta coming soon? Mine is also a IMAP Gmail account.
Title: Re: Beta
Post by: specimen9999 on February 05, 2013, 01:09:53 AM
I'm using it with GMail too on Mail.app and it's functioning correctly for me. My problems are different and are related to the SSL Web Shield (which is currently disabled as I think it goes a little too far) with certain specific sites (Messenger on live.com) which haven't been addressed either.
Title: Re: Beta
Post by: joelw135 on February 05, 2013, 04:37:10 PM
More testing: If I turn off Mail Shield Thunderbird becomes un-useable the beach ball shows for every key tap and it could take five minutes to type three words. When Mail Shield is active I can't get mail from either IMAP or POP, but Thunderbird is stable. This beta is really full of bugs.  I expected some bugs but not this many.
Title: Re: Beta
Post by: hansi on February 08, 2013, 03:14:58 PM
Hello,

i am using this program on 2 macs:

1. iMac 2,5 ghz quadcore i5 (2012), 16 GB Ram, MacOS 10.8.2
2. MacBookPro 2,53 ghz IntelCore 2 Duo (MID 2009), 8GB Ram, MacOS 10.8.2

and it is running on both with no bug.

Firefox 19b5 and Thunderbird 17.0.2. Thunderbird with 2 IMAP-Adresses and one POP-Account.

The Scan function with the 3 mailboxes is running good. the scanner recognized in the postboxes 2 trojan!

regards  :)


Update:

have activate in the controlpanel web-schutz ---> erweitert ----> scan secured connections
the broweser dont connect me to the next webside!

have deactivate this one!   :(

regards

Title: Re: Beta
Post by: tumic on February 12, 2013, 12:13:59 PM
have activate in the controlpanel web-schutz ---> erweitert ----> scan secured connections
the broweser dont connect me to the next webside!

What browser do you use? If it is Firefox, then you have to import the proxy CA certificate to Firefox (will be done automatically in the release version), see the techinfo for more details.
Title: Re: Beta
Post by: tumic on February 14, 2013, 06:43:30 PM
There is an updated version available with many bug fixes, improvements and even new features. It should be very close to the final release build, so please give it a try and report issues.
Title: Re: Beta
Post by: specimen9999 on February 14, 2013, 07:39:19 PM
Ok, using the new beta (38320).
When launching Chrome, I got a message from avast! about an "Internal error!" ("An internal error occurred...").

Here's the console log:

Code: [Select]
13/02/14 18:30:42 avast![183] event_master_disconnected
13/02/14 18:31:18 avast![835] event_master_disconnected
13/02/14 18:31:23 com.avast.proxy[465] SSL_accept(): EOF
13/02/14 18:32:48 /System/Library/CoreServices/CCacheServer.app/Contents/MacOS/CCacheServer[139] No valid tickets, timing out
13/02/14 18:33:14 kernel CODE SIGNING: cs_invalid_page(0x1000): p=996[ksadmin] clearing CS_VALID
13/02/14 18:33:14 kernel CODE SIGNING: cs_invalid_page(0x1000): p=998[ksadmin] clearing CS_VALID
13/02/14 18:33:20 com.avast.helper[496] Pop socket closed by peer
13/02/14 18:33:20 com.apple.launchd[1] (com.avast.daemon[445]) Exited with exit code: 1
13/02/14 18:33:20 com.avast.helper[496] Error connecting to master socket: connect(): Connection refused
13/02/14 18:33:33 [0x0-0x2b02b].com.google.Chrome[994] [994:-1213960192:0214/183333:ERROR:rlz.cc(35)] Not implemented reached in bool GoogleUpdateSettings::GetLanguage(string16 *)
13/02/14 18:34:09 avast![1031] event_master_disconnected

Don't know if it's important, but shouldn't be, I uninstalled the avast! Chrome extension after I installed this avast! beta and before launching Chrome.
Title: Re: Beta
Post by: hansi on February 14, 2013, 08:28:46 PM
Thank you tumic,

i'm using firefox 19b6. i wil test the new one.

regards
Title: Re: Beta
Post by: joelw135 on February 15, 2013, 12:57:48 AM
I am using Thunderbird 19 and the new Beta posted today and still can't get my mail. I have imported the certificate into both Firefox 19 B6 and Thunderbird. No problems with Firefox, but no mail in Thunderbird. I have a email account IMAP Gmail and a POP account from Verizon.
Title: Re: Beta
Post by: tumic on February 15, 2013, 12:13:29 PM
Ok, using the new beta (38320).
When launching Chrome, I got a message from avast! about an "Internal error!" ("An internal error occurred...").

Here's the console log:

Code: [Select]
13/02/14 18:30:42 avast![183] event_master_disconnected
13/02/14 18:31:18 avast![835] event_master_disconnected
13/02/14 18:31:23 com.avast.proxy[465] SSL_accept(): EOF
13/02/14 18:32:48 /System/Library/CoreServices/CCacheServer.app/Contents/MacOS/CCacheServer[139] No valid tickets, timing out
13/02/14 18:33:14 kernel CODE SIGNING: cs_invalid_page(0x1000): p=996[ksadmin] clearing CS_VALID
13/02/14 18:33:14 kernel CODE SIGNING: cs_invalid_page(0x1000): p=998[ksadmin] clearing CS_VALID
13/02/14 18:33:20 com.avast.helper[496] Pop socket closed by peer
13/02/14 18:33:20 com.apple.launchd[1] (com.avast.daemon[445]) Exited with exit code: 1
13/02/14 18:33:20 com.avast.helper[496] Error connecting to master socket: connect(): Connection refused
13/02/14 18:33:33 [0x0-0x2b02b].com.google.Chrome[994] [994:-1213960192:0214/183333:ERROR:rlz.cc(35)] Not implemented reached in bool GoogleUpdateSettings::GetLanguage(string16 *)
13/02/14 18:34:09 avast![1031] event_master_disconnected

Don't know if it's important, but shouldn't be, I uninstalled the avast! Chrome extension after I installed this avast! beta and before launching Chrome.

Looks like an engine crash, do you have a corresponding crash report under "System Diegnostic Reports" in Console?
Title: Re: Beta
Post by: tumic on February 15, 2013, 12:26:48 PM
I am using Thunderbird 19 and the new Beta posted today and still can't get my mail. I have imported the certificate into both Firefox 19 B6 and Thunderbird. No problems with Firefox, but no mail in Thunderbird. I have a email account IMAP Gmail and a POP account from Verizon.

First, the certificates are now imported automatically to Thunderbird, sou you do not have to do it manually.

If you have imported the certificate from the previous installation to Thunderbird and did not delete it before installing the new beta, than it will not work because the installer will not overwrite the certificate with the correct (current) one. So first delete the certificate from Thunderbird and then install avast!. If you have avast already installed, it should be sufficient to delete the certificate and do a "log out/log in", the correct certificate should be automatically installed.

If you use the correct certificate, it should work. We test the mailshield with Apple Mail, Thunderbird, Sparrow and Postbox on several mail accounts (iCloud, Gmail, hotmail and some other) and have no known issues. If it still does not work, look into the system log file (/var/log/system.log), the new beta has extended logging, so there may be some useful info for us. Your IMAP account setup in Thunderbird would also be usefull for us, maybe You are using some unusual configuration.
Title: Re: Beta
Post by: specimen9999 on February 15, 2013, 01:14:04 PM
Looks like an engine crash, do you have a corresponding crash report under "System Diegnostic Reports" in Console?

No, I couldn't find any in that location, or anywhere, couldn't find any avast crash report, or any crash report from the corresponding date and time.
In fact if a crash report had been generated it would have popped a window and asked me to send to Apple, which didn't happen.

After the "Internal error!" message the avast icon grayed out and then become black again after a few seconds, I assume it restarted.
Title: Re: Beta
Post by: joelw135 on February 15, 2013, 02:24:14 PM
I am using Thunderbird 19 and the new Beta posted today and still can't get my mail. I have imported the certificate into both Firefox 19 B6 and Thunderbird. No problems with Firefox, but no mail in Thunderbird. I have a email account IMAP Gmail and a POP account from Verizon.

First, the certificates are now imported automatically to Thunderbird, sou you do not have to do it manually.

If you have imported the certificate from the previous installation to Thunderbird and did not delete it before installing the new beta, than it will not work because the installer will not overwrite the certificate with the correct (current) one. So first delete the certificate from Thunderbird and then install avast!. If you have avast already installed, it should be sufficient to delete the certificate and do a "log out/log in", the correct certificate should be automatically installed.

If you use the correct certificate, it should work. We test the mailshield with Apple Mail, Thunderbird, Sparrow and Postbox on several mail accounts (iCloud, Gmail, hotmail and some other) and have no known issues. If it still does not work, look into the system log file (/var/log/system.log), the new beta has extended logging, so there may be some useful info for us. Your IMAP account setup in Thunderbird would also be usefull for us, maybe You are using some unusual configuration.

OK uninstalled the certificates in Thunderbird and Firefox. Removed Avast. Emptied junk rebooted then re-installed Avast. Started Thunderbird still can't receive mail. I can send but not receive. The activity button keeps turning but no connection. It says at the bottom connected to Gmail IMAP but no luck.
Title: Re: Beta
Post by: tumic on February 15, 2013, 02:53:52 PM
Ok, and the system log? Are there any com.avast.proxy entries? And what are your IMAP server settings (connection type, authentication type)?
Title: Re: Beta
Post by: specimen9999 on February 15, 2013, 02:57:31 PM
Ok, and the system log? Are there any com.avast.proxy entries? And what are your IMAP server settings (connection type, authentication type)?

I believe the system log part is related to my post?
If it is, all I could find in the system.log is those lines I posted above.
Title: Re: Beta
Post by: tumic on February 15, 2013, 03:03:51 PM
I believe the system log part is related to my post?

No it was for joelw135, sorry. In your case, the crash report (if any) located in /Library/Logs/DiagnosticReports/ would be helpfull.
Title: Re: Beta
Post by: specimen9999 on February 15, 2013, 03:06:39 PM
Except there isn't any there related to this event, the latest I have there is from the February 9 and relates to an mds crash.
Title: Re: Beta
Post by: tumic on February 15, 2013, 03:12:48 PM
Except there isn't any there related to this event, the latest I have there is from the February 9 and relates to an mds crash.

Ok, so it was more likely a "controlled termination", probably related to VPS update that triggered the error popup. This may (but should not) happen,  for example if the VPS update takes too long.
Title: Re: Beta
Post by: specimen9999 on February 15, 2013, 03:16:23 PM
Except there isn't any there related to this event, the latest I have there is from the February 9 and relates to an mds crash.

Ok, so it was more likely a "controlled termination", probably related to VPS update that triggered the error popup. This may (but should not) happen,  for example if the VPS update takes too long.

Hm, I did try to manually update minutes before, but it said I was already using the latest definitions (probably the ones that came with the download, since I installed on the same day you released it).
Title: Re: Beta
Post by: joelw135 on February 15, 2013, 03:29:23 PM
I believe the system log part is related to my post?

No it was for joelw135, sorry. In your case, the crash report (if any) located in /Library/Logs/DiagnosticReports/ would be helpfull.

There are no crash reports at all.
Title: Re: Beta
Post by: tumic on February 15, 2013, 04:18:55 PM
There are no crash reports at all.

Looks like its getting a little bit tangled up here... ;-) In your case, I'm interested in the system log entries and the mail account configuration. It is very unlikely, that there will be some crash reports in your case.
Title: Re: Beta
Post by: joelw135 on February 15, 2013, 04:24:54 PM
There are no crash reports at all.

Looks like its getting a little bit tangled up here... ;-) In your case, I'm interested in the system log entries and the mail account configuration. It is very unlikely, that there will be some crash reports in your case.
(http://i248.photobucket.com/albums/gg199/joelw135/ScreenShot2013-02-15at64111PM_zps24ecdec9.png)
I can't find any system log entries for Avast.
Title: Re: Beta
Post by: specimen9999 on February 15, 2013, 11:41:10 PM
There are no crash reports at all.

Looks like its getting a little bit tangled up here... ;-) In your case, I'm interested in the system log entries and the mail account configuration. It is very unlikely, that there will be some crash reports in your case.

I can't find any system log entries for Avast.

Sorry to interfere (as my interference before caused some confusion), but 2 things:

1 - Are you connecting via a proxy or are there any proxy settings configured in OS X and/or Thunderbird?
2 - You might want to blur at least part of your email addresses on those screenshots for privacy.
Title: Re: Beta
Post by: joelw135 on February 16, 2013, 12:49:20 AM
There are no crash reports at all.

Looks like its getting a little bit tangled up here... ;-) In your case, I'm interested in the system log entries and the mail account configuration. It is very unlikely, that there will be some crash reports in your case.

I can't find any system log entries for Avast.

Sorry to interfere (as my interference before caused some confusion), but 2 things:

1 - Are you connecting via a proxy or are there any proxy settings configured in OS X and/or Thunderbird?
2 - You might want to blur at least part of your email addresses on those screenshots for privacy.

No proxy in Thunderbird or OSX so I don't know what the problem is. I do use Little Snitch, but I have the network monitor turned off.
(http://i248.photobucket.com/albums/gg199/joelw135/ScreenShot2013-02-15at64111PM_zps24ecdec9.png)
Title: Re: Beta
Post by: joelw135 on February 16, 2013, 04:08:10 PM
I just tried installing on my MacBook Pro with same results, no email with Thunderbird.
Title: Re: Beta
Post by: specimen9999 on February 16, 2013, 04:25:56 PM
I just tried installing on my MacBook Pro with same results, no email with Thunderbird.

I see you have a personalized domain in Gmail.
If you turn off the Mail Shield in Avast it works?
Title: Re: Beta
Post by: joelw135 on February 16, 2013, 04:32:31 PM
I just tried installing on my MacBook Pro with same results, no email with Thunderbird.

I see you have a personalized domain in Gmail.
If you turn off the Mail Shield in Avast it works?

When I turn off Mail Shield Thunderbird becomes unstable. If I type the beach-ball appears and the type does not show on the screen for at least ten seconds. So an email can take an hour to type.
Title: Re: Beta
Post by: specimen9999 on February 16, 2013, 04:36:37 PM
I just tried installing on my MacBook Pro with same results, no email with Thunderbird.

I see you have a personalized domain in Gmail.
If you turn off the Mail Shield in Avast it works?

When I turn off Mail Shield Thunderbird becomes unstable. If I type the beach-ball appears and the type does not show on the screen for at least ten seconds. So an email can take an hour to type.

Seems like a problem with Thunderbird? Avast doesn't mess with the app itself, it just acts a proxy between the app at the web, if you turn off mail shield then avast doesn't intervene with thunderbird in anyway except for the file shield scanning on-access files.

I presume that if you remove avast! reboot, try Thunderbird the problem doesn't disappear?
Title: Re: Beta
Post by: joelw135 on February 16, 2013, 04:39:07 PM
I just tried installing on my MacBook Pro with same results, no email with Thunderbird.

I see you have a personalized domain in Gmail.
If you turn off the Mail Shield in Avast it works?

When I turn off Mail Shield Thunderbird becomes unstable. If I type the beach-ball appears and the type does not show on the screen for at least ten seconds. So an email can take an hour to type.

Seems like a problem with Thunderbird? Avast doesn't mess with the app itself, it just acts a proxy between the app at the web, if you turn off mail shield then avast doesn't intervene with thunderbird in anyway except for the file shield scanning on-access files.

I presume that if you remove avast! reboot, try Thunderbird the problem doesn't disappear?

If Avast is removed Thunderbird works just fine. I am on a Beta Thunderbird 19 so my next thing to do is remove thunderbird and install normal Thunderbird.
Title: Re: Beta
Post by: specimen9999 on February 16, 2013, 04:42:10 PM
I just tried installing on my MacBook Pro with same results, no email with Thunderbird.

I see you have a personalized domain in Gmail.
If you turn off the Mail Shield in Avast it works?

When I turn off Mail Shield Thunderbird becomes unstable. If I type the beach-ball appears and the type does not show on the screen for at least ten seconds. So an email can take an hour to type.

Seems like a problem with Thunderbird? Avast doesn't mess with the app itself, it just acts a proxy between the app at the web, if you turn off mail shield then avast doesn't intervene with thunderbird in anyway except for the file shield scanning on-access files.

I presume that if you remove avast! reboot, try Thunderbird the problem doesn't disappear?

If Avast is removed Thunderbird works just fine. I am on a Beta Thunderbird 19 so my next thing to do is remove thunderbird and install normal Thunderbird.

BTW, I checked your MX records (if they are pointing correctly to gmail), and they seem fine (I saw your domain before you blacked it out), only difference I noted was the 24 hours TTL, but that shouldn't be a problem.
Title: Re: Beta
Post by: specimen9999 on February 16, 2013, 04:46:51 PM
And as for the beachbaling, most likely what's happening, since you are using IMAP, it's that when you type a new message it communicates with the server and it's trying to store the draft on it, the beachballing occurs because it's timming out and can't store the draft.
Title: Re: Beta
Post by: joelw135 on February 16, 2013, 04:50:33 PM
I just tried installing on my MacBook Pro with same results, no email with Thunderbird.
I removed Avasat and Thunderbird, installed Thunderbird non beta. Reinstalled Avast, same problem.
I see you have a personalized domain in Gmail.
If you turn off the Mail Shield in Avast it works?

When I turn off Mail Shield Thunderbird becomes unstable. If I type the beach-ball appears and the type does not show on the screen for at least ten seconds. So an email can take an hour to type.

Seems like a problem with Thunderbird? Avast doesn't mess with the app itself, it just acts a proxy between the app at the web, if you turn off mail shield then avast doesn't intervene with thunderbird in anyway except for the file shield scanning on-access files.

I presume that if you remove avast! reboot, try Thunderbird the problem doesn't disappear?

If Avast is removed Thunderbird works just fine. I am on a Beta Thunderbird 19 so my next thing to do is remove thunderbird and install normal Thunderbird.

BTW, I checked your MX records (if they are pointing correctly to gmail), and they seem fine (I saw your domain before you blacked it out), only difference I noted was the 24 hours TTL, but that shouldn't be a problem.
Title: Re: Beta
Post by: specimen9999 on February 16, 2013, 05:15:23 PM
Actually, no, there's a problem with your MX records.

Check yourself: http://support.google.com/a/bin/answer.py?hl=en&answer=140038
Title: Re: Beta
Post by: joelw135 on February 16, 2013, 05:39:10 PM
Actually, no, there's a problem with your MX records.

Check yourself: http://support.google.com/a/bin/answer.py?hl=en&answer=140038

I can't figure out what the problem is as my settings are as the Google instructions show. The error I get is
Status: ERR
Sanity check failed. Domain name does not pass regexp.
Title: Re: Beta
Post by: specimen9999 on February 16, 2013, 05:45:20 PM
From what I read, briefly, it's something to do with the name servers (NS), not something in google settings, but with your registrar/domain host, apparently the NSs aren't giving out the same names, I don't know if this is a red herring or not, but your symptons, beach balling, time outs, are typical of a network related problem, not getting a connection, might be that the domain avast proxy resolves is not the adequate one and thus it's forwarding the connection to the wrong server.
Title: Re: Beta
Post by: joelw135 on February 16, 2013, 05:54:26 PM
From what I read, briefly, it's something to do with the name servers (NS), not something in google settings, but with your registrar/domain host, apparently the NSs aren't giving out the same names, I don't know if this is a red herring or not, but your symptons, beach balling, time outs, are typical of a network related problem, not getting a connection, might be that the domain avast proxy resolves is not the adequate one and thus it's forwarding the connection to the wrong server.
Well I guess using Avast is out. I have no control over the providers settings. I have no problem getting mail without Avast so I guess I am up the creek.
Title: Re: Beta
Post by: specimen9999 on February 16, 2013, 05:55:52 PM
You have two NS:

ns1.valinor.net  (108.62.78.90)
ns2.valinor.net  (50.116.18.14)

The second one is replying with no/empty values, or not replying at all.
Title: Re: Beta
Post by: joelw135 on February 16, 2013, 05:57:39 PM
You have two NS:

ns1.valinor.net  (108.62.78.90)
ns2.valinor.net  (50.116.18.14)

The second one is replying with no/empty values, or not replying at all.

I don't know what I can do about that, as I don't have any control over the provider, and I can't even talk to them. According to ADMIN the second ns2 is under service at this time.
Title: Re: Beta
Post by: specimen9999 on February 16, 2013, 10:42:46 PM
This does shed a new light for some GMail problems other users are having, I hope tumic reads this, maybe these users are using personalized domains in GMail, and have MX issues.
Title: Re: Beta
Post by: joelw135 on February 17, 2013, 02:08:39 AM
When I put the address for NS1 I get this
"It works!

This is the default web page for this server.

The web server software is running but no content has been added, yet."
When I put the address for NS2 I get:" Error establishing a database connection"

So do you think Avast will work once the second server is back online?
Title: Re: Beta
Post by: joelw135 on February 17, 2013, 04:41:03 PM
I got Avast to work, by turning off "Scan Secure Locations" how will that affect me?
Title: Re: Beta
Post by: tumic on February 18, 2013, 09:50:06 AM
I got Avast to work, by turning off "Scan Secure Locations" how will that affect me?

If You use SSL when connecting to the mailserver (which you most probably do), than switching off "Scan Secured Connection" equals to switching the mailshield off.
Title: Re: Beta
Post by: tumic on February 18, 2013, 09:52:12 AM
I just tried installing on my MacBook Pro with same results, no email with Thunderbird.

Could you please create a Thunderbird debug log file as described here: https://wiki.mozilla.org/MailNews:Logging#Mac_OS_X (https://wiki.mozilla.org/MailNews:Logging#Mac_OS_X) and post it here? Thanks
Title: Re: Beta
Post by: tumic on February 18, 2013, 10:48:16 AM
The today's update (38330) fixes the issue with gmail and Thunderbird >= 17.0. Please try it, if you had issues with Gmail and Thunderbird.
Title: Re: Beta
Post by: joelw135 on February 18, 2013, 02:37:26 PM
The today's update (38330) fixes the issue with gmail and Thunderbird >= 17.0. Please try it, if you had issues with Gmail and Thunderbird.

Installed new Beta ran log and below is the screen shot.
(http://i248.photobucket.com/albums/gg199/joelw135/ScreenShot2013-02-18at84939AM_zps5b71b430.png)
Title: Re: Beta
Post by: tumic on February 18, 2013, 03:16:07 PM
Installed new Beta ran log and below is the screen shot.

And does it work for you now with the latest beta update?
Title: Re: Beta
Post by: joelw135 on February 18, 2013, 03:27:30 PM
Installed new Beta ran log and below is the screen shot.

And does it work for you now with the latest beta update?

No still can't get IMAP gmail.
Title: Re: Beta
Post by: specimen9999 on February 18, 2013, 03:41:13 PM
Tumic, did you read about how his MX settings for his personalized GMail domain are wrong? One of the NS servers isn't responding.
Title: Re: Beta
Post by: joelw135 on February 18, 2013, 03:47:06 PM
Installed new Beta ran log and below is the screen shot.

And does it work for you now with the latest beta update?
Two minutes ago it started working, have no idea why but it is. I will let you know if it continues or not.

No still can't get IMAP gmail.
Title: Re: Beta
Post by: joelw135 on February 18, 2013, 04:54:05 PM
OK Thunderbird had an extension update and I restarted Thunderbird and email stopped again. Now after disabling the scan secure locations mail started. I then enabled it again and mail continues. So there is a break when restarting Thunderbird.
Here is the log.
(http://i248.photobucket.com/albums/gg199/joelw135/ScreenShot2013-02-18at105013AM_zpsdfe46799.png)
Title: Re: Beta
Post by: specimen9999 on February 18, 2013, 04:59:28 PM
Most likely Avast! asked for the MX records to the NS server that is down, again.

https://toolbox.googleapps.com/apps/checkmx/check?from=support.google.com&origin=checkmx-widget&domain=waxman.org
Title: Re: Beta
Post by: joelw135 on February 18, 2013, 05:09:12 PM
Most likely Avast! asked for the MX records to the NS server that is down, again.

https://toolbox.googleapps.com/apps/checkmx/check?from=support.google.com&origin=checkmx-widget&domain=waxman.org

Now that I know if I disable and then enable after restart maybe if I force it to ask for my password on restart it will work on its own every time.
Title: Re: Beta
Post by: joelw135 on February 18, 2013, 05:16:03 PM
Most likely Avast! asked for the MX records to the NS server that is down, again.

https://toolbox.googleapps.com/apps/checkmx/check?from=support.google.com&origin=checkmx-widget&domain=waxman.org

Now that I know if I disable and then enable after restart maybe if I force it to ask for my password on restart it will work on its own every time.

No that didn't work, only turning the scan of secure locations off then back on works. I wonder if this will happen after sleep?
Title: Re: Beta
Post by: joelw135 on February 18, 2013, 05:18:53 PM
Most likely Avast! asked for the MX records to the NS server that is down, again.

https://toolbox.googleapps.com/apps/checkmx/check?from=support.google.com&origin=checkmx-widget&domain=waxman.org

Now that I know if I disable and then enable after restart maybe if I force it to ask for my password on restart it will work on its own every time.

No that didn't work, only turning the scan of secure locations off then back on works. I wonder if this will happen after sleep?
I am correct after sleep the same problem, this is going to be a major problem.
Title: Re: Beta
Post by: specimen9999 on February 18, 2013, 05:28:59 PM
Most likely Avast! asked for the MX records to the NS server that is down, again.

https://toolbox.googleapps.com/apps/checkmx/check?from=support.google.com&origin=checkmx-widget&domain=waxman.org

Now that I know if I disable and then enable after restart maybe if I force it to ask for my password on restart it will work on its own every time.

No that didn't work, only turning the scan of secure locations off then back on works. I wonder if this will happen after sleep?
I am correct after sleep the same problem, this is going to be a major problem.

Personally I'm now convinced, it is going to be a major problem, always, your problem lies elsewhere, even if you uninstall Avast!, even if you set up your email account in another completely different computer, every time any mail program or anti-virus asks for the server address it has a 50% chance of contacting the name server that gives no response, and when that happens you get no connection, the name server probably stopped working around the time you first installed Avast, so it's likely just coincidental.
Title: Re: Beta
Post by: joelw135 on February 18, 2013, 05:31:58 PM
Most likely Avast! asked for the MX records to the NS server that is down, again.

https://toolbox.googleapps.com/apps/checkmx/check?from=support.google.com&origin=checkmx-widget&domain=waxman.org

Now that I know if I disable and then enable after restart maybe if I force it to ask for my password on restart it will work on its own every time.

No that didn't work, only turning the scan of secure locations off then back on works. I wonder if this will happen after sleep?
I am correct after sleep the same problem, this is going to be a major problem.

Personally I'm now convinced, it is going to be a major problem, always, your problem lies elsewhere, even if you uninstall Avast!, even if you set up your email account in another completely different computer, every time any mail program or anti-virus asks for the server address it has a 50% chance of contacting the NS server that gives no response, and when that happens you get no connection, the name server probably stopped working around the time you first installed Avast, so it's likely just coincidental.

I don't have mail problems with any other virus programs. I have BitDefender and Sophos no problems. I also never not get my email unless Avast is loaded.  I would love to keep Avast, so I have to think of a way to keep Thunderbird from sleeping. I don't want the hard drives not sleeping as that is a strain on the system.
Title: Re: Beta
Post by: specimen9999 on February 18, 2013, 05:34:31 PM
Most likely Avast! asked for the MX records to the NS server that is down, again.

https://toolbox.googleapps.com/apps/checkmx/check?from=support.google.com&origin=checkmx-widget&domain=waxman.org

Now that I know if I disable and then enable after restart maybe if I force it to ask for my password on restart it will work on its own every time.

No that didn't work, only turning the scan of secure locations off then back on works. I wonder if this will happen after sleep?
I am correct after sleep the same problem, this is going to be a major problem.

Personally I'm now convinced, it is going to be a major problem, always, your problem lies elsewhere, even if you uninstall Avast!, even if you set up your email account in another completely different computer, every time any mail program or anti-virus asks for the server address it has a 50% chance of contacting the NS server that gives no response, and when that happens you get no connection, the name server probably stopped working around the time you first installed Avast, so it's likely just coincidental.

I don't have mail problems with any other virus programs. I have BitDefender and Sophos no problems. I also never not get my email unless Avast is loaded.  I would love to keep Avast, so I have to think of a way to keep Thunderbird from sleeping. I don't want the hard drives not sleeping as that is a strain on the system.

Are you using more than one AV on the same mac!?
AFAIK Sophos for Mac doesn't scan connections, only access to the file system, so it's like running Avast with Mail and Web shield off. As for Bitdefender I have no idea.
Title: Re: Beta
Post by: joelw135 on February 18, 2013, 05:35:55 PM
No only tried those two, both removed from the iMac.
Title: Re: Beta
Post by: specimen9999 on February 18, 2013, 05:39:50 PM
No only tried those two, both removed from the iMac.

Like I said, your problem is like tossing a coin, it worked before without problems because the NS2 was up, now it isn't, all I'm saying is warning you that with the name server problem you have, independently from Avast! you have 50% chance of your mail not working at this moment.
Title: Re: Beta
Post by: joelw135 on February 18, 2013, 05:41:46 PM
No only tried those two, both removed from the iMac.

Like I said, your problem is like tossing a coin, it worked before without problems because the NS2 was up, now it isn't, all I'm saying is warning you that with the name server problem you have, independently from Avast! you have 50% chance of your mail not working at this moment.

I understand that, but wonder why it works every time I disable then enable the scan of secure locations, it should be that same 50 50 chance, but it works every time.
Title: Re: Beta
Post by: specimen9999 on February 18, 2013, 05:44:55 PM
No only tried those two, both removed from the iMac.

Like I said, your problem is like tossing a coin, it worked before without problems because the NS2 was up, now it isn't, all I'm saying is warning you that with the name server problem you have, independently from Avast! you have 50% chance of your mail not working at this moment.

I understand that, but wonder why it works every time I disable then enable the scan of secure locations, it should be that same 50 50 chance, but it works every time.

Every time you do that you are probably using Thunderbird cached resolution (which is probably the server that is up) instead of Avast cached resolution.
Title: Re: Beta
Post by: joelw135 on February 18, 2013, 05:47:09 PM
No only tried those two, both removed from the iMac.

Like I said, your problem is like tossing a coin, it worked before without problems because the NS2 was up, now it isn't, all I'm saying is warning you that with the name server problem you have, independently from Avast! you have 50% chance of your mail not working at this moment.

I understand that, but wonder why it works every time I disable then enable the scan of secure locations, it should be that same 50 50 chance, but it works every time.

Every time you do that you are probably using Thunderbird cached resolution (which is probably the server that is up) instead of Avast cached resolution.

I just hope the host gets this fixed, as I found out yesterday it needs a new server. This is going to be a problem as the guy is a private entity and not a company. So cash is the problem.
Title: Re: Beta
Post by: specimen9999 on February 18, 2013, 05:51:19 PM
No only tried those two, both removed from the iMac.

Like I said, your problem is like tossing a coin, it worked before without problems because the NS2 was up, now it isn't, all I'm saying is warning you that with the name server problem you have, independently from Avast! you have 50% chance of your mail not working at this moment.

I understand that, but wonder why it works every time I disable then enable the scan of secure locations, it should be that same 50 50 chance, but it works every time.

Every time you do that you are probably using Thunderbird cached resolution (which is probably the server that is up) instead of Avast cached resolution.

I just hope the host gets this fixed, as I found out yesterday it needs a new server. This is going to be a problem as the guy is a private entity and not a company. So cash is the problem.

Look at the SSL thread below this on the forum, a guy edited his host file to force the resolution of imap.gmail.com to a fixed IP, that might be a solution for you. That way you'll be circumventing resolution issues, and if Google ever changes that IP (unlikely) you'll only have to manually update it.
Title: Re: Beta
Post by: joelw135 on February 18, 2013, 05:52:43 PM
No only tried those two, both removed from the iMac.

Like I said, your problem is like tossing a coin, it worked before without problems because the NS2 was up, now it isn't, all I'm saying is warning you that with the name server problem you have, independently from Avast! you have 50% chance of your mail not working at this moment.

I understand that, but wonder why it works every time I disable then enable the scan of secure locations, it should be that same 50 50 chance, but it works every time.

Every time you do that you are probably using Thunderbird cached resolution (which is probably the server that is up) instead of Avast cached resolution.

I just hope the host gets this fixed, as I found out yesterday it needs a new server. This is going to be a problem as the guy is a private entity and not a company. So cash is the problem.

Look at the SSL thread below this on the forum, a guy edited his host file to force the resolution of imap.gmail.com to a fixed IP, that might be a solution for you. That way you'll be circumventing resolution issues, and if Google ever changes that IP (unlikely) you'll only have to manually update it.

Thanks, I will look at that.
Title: Re: Beta
Post by: joelw135 on February 18, 2013, 05:58:47 PM
No only tried those two, both removed from the iMac.

Like I said, your problem is like tossing a coin, it worked before without problems because the NS2 was up, now it isn't, all I'm saying is warning you that with the name server problem you have, independently from Avast! you have 50% chance of your mail not working at this moment.

I understand that, but wonder why it works every time I disable then enable the scan of secure locations, it should be that same 50 50 chance, but it works every time.

Every time you do that you are probably using Thunderbird cached resolution (which is probably the server that is up) instead of Avast cached resolution.

I just hope the host gets this fixed, as I found out yesterday it needs a new server. This is going to be a problem as the guy is a private entity and not a company. So cash is the problem.

Look at the SSL thread below this on the forum, a guy edited his host file to force the resolution of imap.gmail.com to a fixed IP, that might be a solution for you. That way you'll be circumventing resolution issues, and if Google ever changes that IP (unlikely) you'll only have to manually update it.

Thanks, I will look at that.
I looked at that and I am not sure what to do, it is above my ability I think.
Title: Re: Beta
Post by: joelw135 on February 18, 2013, 06:26:16 PM
I renamed the Hosts file created a duplicate then added line 173.194.67.109  imap.gmail.com saved, but the problem still is there. I replaced the original hosts file. Unless I was doing something wrong with the IP I added. Or should I have added the IP to my good NS1
Title: Re: Beta
Post by: specimen9999 on February 18, 2013, 06:50:32 PM
I renamed the Hosts file created a duplicate then added line 173.194.67.109  imap.gmail.com saved, but the problem still is there. I replaced the original hosts file. Unless I was doing something wrong with the IP I added. Or should I have added the IP to my good NS1

You probably need flush your resolution cache, you can do this via terminal.app:

Code: [Select]
sudo dscacheutil -flushcache
Your hosts file should look something like this now(all the entries related to localhost and broadcasthost should be left as they are originally, the values might me slightly different from yours there):
Code: [Select]
##
# Host Database
#
# localhost is used to configure the loopback interface
# when the system is booting.  Do not change this entry.
##
127.0.0.1       localhost
255.255.255.255 broadcasthost
::1     localhost
xxxx::1%lo0     localhost

173.194.66.109  imap.gmail.com
Title: Re: Beta
Post by: joelw135 on February 18, 2013, 07:23:31 PM
I renamed the Hosts file created a duplicate then added line 173.194.67.109  imap.gmail.com saved, but the problem still is there. I replaced the original hosts file. Unless I was doing something wrong with the IP I added. Or should I have added the IP to my good NS1

You probably need flush your resolution cache, you can do this via terminal.app:

Code: [Select]
sudo dscacheutil -flushcache
Your hosts file should look something like this now(all the entries related to localhost and broadcasthost should be left as they are originally, the values might me slightly different from yours there):
Code: [Select]
##
# Host Database
#
# localhost is used to configure the loopback interface
# when the system is booting.  Do not change this entry.
##
127.0.0.1       localhost
255.255.255.255 broadcasthost
::1     localhost
xxxx::1%lo0     localhost

173.194.66.109  imap.gmail.com

I will try that.
Title: Re: Beta
Post by: joelw135 on February 18, 2013, 07:33:34 PM
I renamed the Hosts file created a duplicate then added line 173.194.67.109  imap.gmail.com saved, but the problem still is there. I replaced the original hosts file. Unless I was doing something wrong with the IP I added. Or should I have added the IP to my good NS1

You probably need flush your resolution cache, you can do this via terminal.app:

Code: [Select]
sudo dscacheutil -flushcache
Your hosts file should look something like this now(all the entries related to localhost and broadcasthost should be left as they are originally, the values might me slightly different from yours there):
Code: [Select]
##
# Host Database
#
# localhost is used to configure the loopback interface
# when the system is booting.  Do not change this entry.
##
127.0.0.1       localhost
255.255.255.255 broadcasthost
::1     localhost
xxxx::1%lo0     localhost

173.194.66.109  imap.gmail.com

I will try that.

No luck it didn't work after sleep.
Title: Re: Beta
Post by: specimen9999 on February 18, 2013, 07:36:11 PM
I renamed the Hosts file created a duplicate then added line 173.194.67.109  imap.gmail.com saved, but the problem still is there. I replaced the original hosts file. Unless I was doing something wrong with the IP I added. Or should I have added the IP to my good NS1

You probably need flush your resolution cache, you can do this via terminal.app:

Code: [Select]
sudo dscacheutil -flushcache
Your hosts file should look something like this now(all the entries related to localhost and broadcasthost should be left as they are originally, the values might me slightly different from yours there):
Code: [Select]
##
# Host Database
#
# localhost is used to configure the loopback interface
# when the system is booting.  Do not change this entry.
##
127.0.0.1       localhost
255.255.255.255 broadcasthost
::1     localhost
xxxx::1%lo0     localhost

173.194.66.109  imap.gmail.com

I will try that.

No luck it didn't work after sleep.

*shrug*
Then revert back to the original hosts, there's nothing else I can suggest.
Title: Re: Beta
Post by: joelw135 on February 18, 2013, 07:39:05 PM
I renamed the Hosts file created a duplicate then added line 173.194.67.109  imap.gmail.com saved, but the problem still is there. I replaced the original hosts file. Unless I was doing something wrong with the IP I added. Or should I have added the IP to my good NS1

You probably need flush your resolution cache, you can do this via terminal.app:

Code: [Select]
sudo dscacheutil -flushcache
Your hosts file should look something like this now(all the entries related to localhost and broadcasthost should be left as they are originally, the values might me slightly different from yours there):
Code: [Select]
##
# Host Database
#
# localhost is used to configure the loopback interface
# when the system is booting.  Do not change this entry.
##
127.0.0.1       localhost
255.255.255.255 broadcasthost
::1     localhost
xxxx::1%lo0     localhost

173.194.66.109  imap.gmail.com

I will try that.

No luck it didn't work after sleep.

*shrug*
Then revert back to the original hosts, there's nothing else I can suggest.

What I did for now is set the Sleep to none, but put the hard drive to sleep when able and the monitors. I I could make a script to run after a Thunderbird restart that would be great.
Title: Re: Beta
Post by: joelw135 on February 18, 2013, 08:15:08 PM
I renamed the Hosts file created a duplicate then added line 173.194.67.109  imap.gmail.com saved, but the problem still is there. I replaced the original hosts file. Unless I was doing something wrong with the IP I added. Or should I have added the IP to my good NS1

You probably need flush your resolution cache, you can do this via terminal.app:

Code: [Select]
sudo dscacheutil -flushcache
Your hosts file should look something like this now(all the entries related to localhost and broadcasthost should be left as they are originally, the values might me slightly different from yours there):
Code: [Select]
##
# Host Database
#
# localhost is used to configure the loopback interface
# when the system is booting.  Do not change this entry.
##
127.0.0.1       localhost
255.255.255.255 broadcasthost
::1     localhost
xxxx::1%lo0     localhost

173.194.66.109  imap.gmail.com

I will try that.

No luck it didn't work after sleep.

*shrug*
Then revert back to the original hosts, there's nothing else I can suggest.

What I did for now is set the Sleep to none, but put the hard drive to sleep when able and the monitors. I I could make a script to run after a Thunderbird restart that would be great.

I created a workflow, but it didn't work the same as doing it manually.
Title: Re: Beta
Post by: specimen9999 on February 18, 2013, 09:05:09 PM
I renamed the Hosts file created a duplicate then added line 173.194.67.109  imap.gmail.com saved, but the problem still is there. I replaced the original hosts file. Unless I was doing something wrong with the IP I added. Or should I have added the IP to my good NS1

You probably need flush your resolution cache, you can do this via terminal.app:

Code: [Select]
sudo dscacheutil -flushcache
Your hosts file should look something like this now(all the entries related to localhost and broadcasthost should be left as they are originally, the values might me slightly different from yours there):
Code: [Select]
##
# Host Database
#
# localhost is used to configure the loopback interface
# when the system is booting.  Do not change this entry.
##
127.0.0.1       localhost
255.255.255.255 broadcasthost
::1     localhost
xxxx::1%lo0     localhost

173.194.66.109  imap.gmail.com

I will try that.

No luck it didn't work after sleep.

*shrug*
Then revert back to the original hosts, there's nothing else I can suggest.

What I did for now is set the Sleep to none, but put the hard drive to sleep when able and the monitors. I I could make a script to run after a Thunderbird restart that would be great.

I created a workflow, but it didn't work the same as doing it manually.

I'm sorry to say that eiher manually or automatically won't make any difference, the sleep thing is just a coincidence, I see no reason why sleep would have anything to do with your issue on the long term, the way I see it, it's just coin flipping, nothing more, besides, since the dns cache was cleared you won't be getting the cached results. Don't waste any more time with this until either you have 2 working name servers or tumic has anything to say on the subject, I would like to hear his opinion on the MX thing. I gave a bit more thought to it, and maybe I was wrong, although the name servers problem is an issue, it's an issue that happens when someone tries to send an email to your address as it might not find the gmail server, but when retrieving email via IMAP you are connecting to GMail server directly, so back to square one, I have no idea what's going on over there.
Title: Re: Beta
Post by: joelw135 on February 18, 2013, 09:38:23 PM
I renamed the Hosts file created a duplicate then added line 173.194.67.109  imap.gmail.com saved, but the problem still is there. I replaced the original hosts file. Unless I was doing something wrong with the IP I added. Or should I have added the IP to my good NS1

You probably need flush your resolution cache, you can do this via terminal.app:

Code: [Select]
sudo dscacheutil -flushcache
Your hosts file should look something like this now(all the entries related to localhost and broadcasthost should be left as they are originally, the values might me slightly different from yours there):
Code: [Select]
##
# Host Database
#
# localhost is used to configure the loopback interface
# when the system is booting.  Do not change this entry.
##
127.0.0.1       localhost
255.255.255.255 broadcasthost
::1     localhost
xxxx::1%lo0     localhost

173.194.66.109  imap.gmail.com

I will try that.

No luck it didn't work after sleep.

*shrug*
Then revert back to the original hosts, there's nothing else I can suggest.

What I did for now is set the Sleep to none, but put the hard drive to sleep when able and the monitors. I I could make a script to run after a Thunderbird restart that would be great.

I created a workflow, but it didn't work the same as doing it manually.

I'm sorry to say that eiher manually or automatically won't make any difference, the sleep thing is just a coincidence, I see no reason why sleep would have anything to do with your issue on the long term, the way I see it, it's just coin flipping, nothing more, besides, since the dns cache was cleared you won't be getting the cached results. Don't waste any more time with this until either you have 2 working name servers or tumic has anything to say on the subject, I would like to hear his opinion on the MX thing. I gave a bit more thought to it, and maybe I was wrong, although the name servers problem is an issue, it's an issue that happens when someone tries to send an email to your address as it might not find the gmail server, but when retrieving email via IMAP you are connecting to GMail server directly, so back to square one, I have no idea what's going on over there.

The problem is that Mountain Lion when sleeping drops the Internet connection on both Ethernet and WiFi it is a known documented problem. Most people don't realize it as they don't have GROWL installed and think it is just slow wake up. GROWL shows the loss of IP and network connections, and when awakened it shows reconnection of each.
Title: Re: Beta
Post by: Fenikkusu on February 19, 2013, 06:21:20 AM
Following the first update, I ran the update and found a curious issue. The two accounts that were working no longer were connecting. They both display the error below.

Quote
SSL_accept(): sslv3 alert bad certificate

The worked fine prior to the update and the Scanning of them worked as well. My GMail account however didn't. Following both the first update and the second, all three accounts still fail to connect. If I disable the Shield, all three accounts connect correctly.

It should be worth mentioning that the two non-gmail accounts have certificates I know to be valid. However, they are not registered for the domain under which they are accessed. This could be part of the issue.

Additionally, once I reenabled the shield, my GMail appears to be working correctly know. I will need a refresh to be sure. I do have the hosts fix in place, so this may be playing a role as well.
Title: Re: Beta
Post by: joelw135 on February 19, 2013, 02:12:47 PM
I understand that my NS2 server is down so I only have one NS but there has to be a way for Avast to understand this and ignore it until the server is back up. As it stands I can't get mail unless I disable the mail scan for secure locations. The trick of disabling and enabling the scan is tiresome to say the least.
Title: Re: Beta
Post by: hansi on February 22, 2013, 04:21:05 PM
Hallo,

using the new beta 38330 and i become the following in the Konsole avastfileshield.log:

[4441-note] Fri Feb 22 15:22:55 2013 - Starting File Shield (build Feb 18 2013 10:17:07)
[4441-err] Fri Feb 22 15:22:55 2013 - config_load: ini_read() failed [-1]. Will use defaults.
[4441-err] Fri Feb 22 15:23:37 2013 - SCAN '/private/var/folders/hm/qj1rwy3d313557sxqvm0sghm0000gn/T/tmp.weNQJO' failed: 451 SCAN Engine error 2 No such file or directory
[4441-err] Fri Feb 22 15:24:30 2013 - avscan_handle_read: Lost connection to daemon.
[4441-err] Fri Feb 22 15:24:30 2013 - avscan_handle_read: Lost connection to daemon.
[4441-err] Fri Feb 22 15:28:50 2013 - SCAN '/private/var/folders/hm/qj1rwy3d313557sxqvm0sghm0000gn/T/etilqs_DX4t2tj3fdPLjJc' failed: 451 SCAN Engine error 2 No such file or directory
[4441-err] Fri Feb 22 15:28:50 2013 - SCAN '/private/var/folders/hm/qj1rwy3d313557sxqvm0sghm0000gn/T/etilqs_yMlY7QpcQz0LDmR' failed: 451 SCAN Engine error 2 No such file or directory
[4441-err] Fri Feb 22 15:28:50 2013 - SCAN '/private/var/folders/hm/qj1rwy3d313557sxqvm0sghm0000gn/T/etilqs_QL0tHOU9TsgHH6j' failed: 451 SCAN Engine error 2 No such file or directory
[4441-err] Fri Feb 22 15:29:10 2013 - SCAN '/private/var/folders/hm/qj1rwy3d313557sxqvm0sghm0000gn/T/etilqs_JN2qvl9vkGcerhY' failed: 451 SCAN Engine error 2 No such file or directory
[4441-err] Fri Feb 22 15:29:10 2013 - SCAN '/private/var/folders/hm/qj1rwy3d313557sxqvm0sghm0000gn/T/etilqs_z3BvF7jqeaLOPFg' failed: 451 SCAN Engine error 2 No such file or directory
[4441-note] Fri Feb 22 15:29:14 2013 - Stopping File Shield...
[74-note] Fri Feb 22 15:30:17 2013 - Starting File Shield (build Feb 18 2013 10:17:07)
[74-err] Fri Feb 22 15:30:21 2013 - config_load: ini_read() failed [-1]. Will use defaults.
[74-err] Fri Feb 22 15:30:21 2013 - avmaster_open: connect() failed. No such file or directory [2]
[74-err] Fri Feb 22 15:30:21 2013 - kext_open: The Kext is not loaded.
[74-err] Fri Feb 22 15:30:27 2013 - kext_open: The Kext is not loaded.
[74-err] Fri Feb 22 15:30:27 2013 - avmaster_open: connect() failed. No such file or directory [2]
[74-err] Fri Feb 22 15:30:36 2013 - avmaster_handle_timeout: Timeout avmaster-welcome has occured.
[74-err] Fri Feb 22 15:30:38 2013 - avmaster_handle_timeout: Timeout avmaster-welcome has occured.
[74-err] Fri Feb 22 15:30:40 2013 - avmaster_handle_timeout: Timeout avmaster-welcome has occured.
[74-err] Fri Feb 22 15:30:42 2013 - avmaster_handle_timeout: Timeout avmaster-welcome has occured.
[74-err] Fri Feb 22 15:30:45 2013 - avmaster_handle_timeout: Timeout avmaster-welcome has occured.
[74-err] Fri Feb 22 15:30:47 2013 - avmaster_handle_timeout: Timeout avmaster-welcome has occured.
[74-err] Fri Feb 22 15:30:49 2013 - avmaster_handle_timeout: Timeout avmaster-welcome has occured.
[74-err] Fri Feb 22 15:30:49 2013 - avmaster_open: connect() failed. Connection refused [61]
[74-warn] Fri Feb 22 15:30:49 2013 - av_maybe_stuck: Daemon likely stuck. Restart it.
[74-note] Fri Feb 22 15:33:16 2013 - Starting File Shield (build Feb 18 2013 10:17:07)
[74-err] Fri Feb 22 15:33:16 2013 - config_load: ini_read() failed [-1]. Will use defaults.
[74-err] Fri Feb 22 15:33:16 2013 - avmaster_open: connect() failed. Connection refused [61]
[74-err] Fri Feb 22 15:33:16 2013 - kext_open: The Kext is not loaded.
[74-err] Fri Feb 22 15:33:24 2013 - avmaster_open: connect() failed. Connection refused [61]
[74-err] Fri Feb 22 15:33:30 2013 - avmaster_open: connect() failed. Connection refused [61]
[74-err] Fri Feb 22 15:33:38 2013 - avmaster_handle_timeout: Timeout avmaster-welcome has occured.
[74-err] Fri Feb 22 15:33:40 2013 - avmaster_handle_timeout: Timeout avmaster-welcome has occured.
[74-warn] Fri Feb 22 15:33:40 2013 - av_maybe_stuck: Daemon likely stuck. Restart it.
[74-err] Fri Feb 22 15:33:40 2013 - avmaster_open: connect() failed. Connection refused [61]
[74-err] Fri Feb 22 15:33:49 2013 - avmaster_handle_timeout: Timeout avmaster-welcome has occured.
[74-err] Fri Feb 22 15:33:51 2013 - config_load: ini_read() failed [-1]. Will use defaults.
[74-err] Fri Feb 22 15:33:54 2013 - avmaster_handle_timeout: Timeout avmaster-welcome has occured.
[74-err] Fri Feb 22 15:33:56 2013 - avmaster_handle_timeout: Timeout avmaster-welcome has occured.
[74-err] Fri Feb 22 15:33:58 2013 - avmaster_handle_timeout: Timeout avmaster-welcome has occured.
[74-err] Fri Feb 22 15:34:00 2013 - avmaster_handle_timeout: Timeout avmaster-welcome has occured.
[74-err] Fri Feb 22 15:34:03 2013 - avmaster_handle_timeout: Timeout avmaster-welcome has occured.
[74-err] Fri Feb 22 15:34:03 2013 - avmaster_open: connect() failed. Connection refused [61]
[74-warn] Fri Feb 22 15:34:03 2013 - av_maybe_stuck: Daemon likely stuck. Restart it.
[81-note] Fri Feb 22 15:40:09 2013 - Starting File Shield (build Feb 18 2013 10:17:07)
[81-err] Fri Feb 22 15:40:10 2013 - config_load: ini_read() failed [-1]. Will use defaults.
[81-err] Fri Feb 22 15:40:10 2013 - avmaster_open: connect() failed. Connection refused [61]
[81-err] Fri Feb 22 15:40:10 2013 - kext_open: The Kext is not loaded.
[81-err] Fri Feb 22 15:40:16 2013 - kext_open: The Kext is not loaded.
[81-err] Fri Feb 22 15:40:19 2013 - avmaster_handle_timeout: Timeout avmaster-welcome has occured.
[81-err] Fri Feb 22 15:40:22 2013 - avmaster_handle_timeout: Timeout avmaster-welcome has occured.
[81-err] Fri Feb 22 15:40:24 2013 - avmaster_handle_timeout: Timeout avmaster-welcome has occured.
[81-err] Fri Feb 22 15:40:26 2013 - avmaster_handle_timeout: Timeout avmaster-welcome has occured.
[81-err] Fri Feb 22 15:40:28 2013 - avmaster_handle_timeout: Timeout avmaster-welcome has occured.
[81-err] Fri Feb 22 15:40:30 2013 - avmaster_handle_timeout: Timeout avmaster-welcome has occured.
[81-err] Fri Feb 22 15:40:32 2013 - avmaster_handle_timeout: Timeout avmaster-welcome has occured.
[81-err] Fri Feb 22 15:40:32 2013 - avmaster_open: connect() failed. Connection refused [61]
[81-warn] Fri Feb 22 15:40:32 2013 - av_maybe_stuck: Daemon likely stuck. Restart it.
[81-err] Fri Feb 22 15:40:41 2013 - avmaster_handle_timeout: Timeout avmaster-welcome has occured.
[81-err] Fri Feb 22 15:40:43 2013 - config_load: ini_read() failed [-1]. Will use defaults.
[81-err] Fri Feb 22 15:40:45 2013 - avmaster_handle_timeout: Timeout avmaster-welcome has occured.
[81-err] Fri Feb 22 15:40:47 2013 - avmaster_handle_timeout: Timeout avmaster-welcome has occured.
[81-err] Fri Feb 22 15:40:49 2013 - avmaster_handle_timeout: Timeout avmaster-welcome has occured.
[81-err] Fri Feb 22 15:40:52 2013 - avmaster_handle_timeout: Timeout avmaster-welcome has occured.
[81-err] Fri Feb 22 15:40:54 2013 - avmaster_handle_timeout: Timeout avmaster-welcome has occured.
[81-err] Fri Feb 22 15:40:57 2013 - avmaster_handle_timeout: Timeout avmaster-welcome has occured.
[81-err] Fri Feb 22 15:40:57 2013 - avmaster_open: connect() failed. Connection refused [61]
[81-err] Fri Feb 22 15:41:02 2013 - avmaster_open: connect() failed. Connection refused [61]
[81-warn] Fri Feb 22 15:41:02 2013 - av_maybe_stuck: Daemon likely stuck. Restart it.
[81-err] Fri Feb 22 15:41:08 2013 - config_load: ini_read() failed [-1]. Will use defaults.
[81-err] Fri Feb 22 15:41:42 2013 - SCAN '/private/var/folders/zz/zyxvpxvq6csfxvn_n00000sm00006d/T/etilqs_bxpDHaQYS9jfqa5' failed: 451 SCAN Engine error 2 No such file or directory
[81-err] Fri Feb 22 15:41:43 2013 - SCAN '/private/var/folders/zz/zyxvpxvq6csfxvn_n00000sm00006d/T/etilqs_KclzM66DnwoiOhm' failed: 451 SCAN Engine error 2 No such file or directory
[81-err] Fri Feb 22 15:41:43 2013 - SCAN '/private/var/folders/zz/zyxvpxvq6csfxvn_n00000sm00006d/T/etilqs_gRYHRzUMxftbebN' failed: 451 SCAN Engine error 2 No such file or directory
[81-err] Fri Feb 22 15:41:47 2013 - SCAN '/private/var/folders/zz/zyxvpxvq6csfxvn_n00000sm00006d/T/etilqs_MsOHEQSFWcQWIK8' failed: 451 SCAN Engine error 2 No such file or directory
[81-err] Fri Feb 22 15:41:47 2013 - SCAN '/private/var/folders/hm/qj1rwy3d313557sxqvm0sghm0000gn/T/etilqs_2h3kTVTahwuLDSQ' failed: 451 SCAN Engine error 2 No such file or directory
[81-err] Fri Feb 22 15:41:47 2013 - SCAN '/private/var/folders/zz/zyxvpxvq6csfxvn_n00000sm00006d/T/etilqs_oD1GqYXUQzEYp6s' failed: 451 SCAN Engine error 2 No such file or directory

is this OK?????

Regards
Title: Re: Beta
Post by: specimen9999 on February 22, 2013, 06:20:48 PM
Hallo,

using the new beta 38330 and i become the following in the Konsole avastfileshield.log:
...
is this OK?????

Regards

I wonder if you uninstalled the previous avast version before installing this beta.
Title: Re: Beta
Post by: hansi on February 23, 2013, 01:34:48 PM
Hallo specimen9999,

Yes, I have made ​​the mistake and did not delete the old version and then re-installed. What can I do to correct the mistake?
Title: Re: Beta
Post by: specimen9999 on February 23, 2013, 01:53:23 PM
It's so obvious it's embarrassing. Uninstall (via the avast menu), re-install.
Title: Re: Beta
Post by: specimen9999 on February 25, 2013, 10:22:35 PM
I installed 38330, made sure to uninstall Webrep from all browsersas I REALLY don't want this extension on any of my browsers (is it possible for this to be opt-in and not opt-out?), everything was running fine using Chrome, rebooted, launched Chrome, and there I see the Webrep extension!, at the same time avast complains saying "Internal error!" (no, there were no crash logs in User/System Diagnostic Reports in Console.app), Opened up avast! and there it is, Webrep installed in ALL browsers, I don't want Webrep, leave the browsers alone, one uninstall should be enough.
Title: Re: Beta
Post by: tumic on February 26, 2013, 02:51:21 PM
I installed 38330, made sure to uninstall Webrep from all browsersas I REALLY don't want this extension on any of my browsers (is it possible for this to be opt-in and not opt-out?), everything was running fine using Chrome, rebooted, launched Chrome, and there I see the Webrep extension!, at the same time avast complains saying "Internal error!" (no, there were no crash logs in User/System Diagnostic Reports in Console.app), Opened up avast! and there it is, Webrep installed in ALL browsers, I don't want Webrep, leave the browsers alone, one uninstall should be enough.

If the WebRep plugin was installed even though you have disabled it during install, than it is a bug and it will be fixed, i will check that. The opt-in is a "political" company decision, there is nothing we can do about it.
Title: Re: Beta
Post by: specimen9999 on February 26, 2013, 03:20:32 PM
I installed 38330, made sure to uninstall Webrep from all browsersas I REALLY don't want this extension on any of my browsers (is it possible for this to be opt-in and not opt-out?), everything was running fine using Chrome, rebooted, launched Chrome, and there I see the Webrep extension!, at the same time avast complains saying "Internal error!" (no, there were no crash logs in User/System Diagnostic Reports in Console.app), Opened up avast! and there it is, Webrep installed in ALL browsers, I don't want Webrep, leave the browsers alone, one uninstall should be enough.

If the WebRep plugin was installed even though you have disabled it during install, than it is a bug and it will be fixed, i will check that. The opt-in is a "political" company decision, there is nothing we can do about it.

Thank you. I figured there was no possibility of opt-in, I understand "what's in" for avast! if users use Webrep, I'll just make sure I uninstalll it whenever I reinstall avast!.
Title: Re: Beta
Post by: tumic on February 26, 2013, 04:44:04 PM
Version 38397 is out as the final version, thanks to all who have tested the beta version(s) and reported issues. Although upgrading from a beta version may work, it is highly recommended to uninstall the previous beta version and install 38397 "from  scratch".