Avast WEBforum
Consumer Products => Avast Mac Security => Topic started by: daz clarke on February 27, 2013, 08:21:08 PM
-
Just updated to version 38397, but had to turn off mail protection as it completely blocked access to my mail server. Apparently there has been a change in the way it handles SSL. I have not modified my system to make it work I used to just put up with the warnings in the previous versions about ssl/tls connections. IMAP accounts on Mac Mail 4.6 (1085), OS X 10.6.8.
-
Latest version is 38403. -> http://forum.avast.com/index.php?topic=107681.0
Please update.
-
Sorry, got that version number from the topic titled, SSL/TLS connection detected!
Just looked and my version is 38403.
-
Sorry, got that version number from the topic titled, SSL/TLS connection detected!
Just looked and my version is 38403.
OK, you've to wait for one of the Mac guys then. ;)
-
SSL handling has indeed changed in 38397 (and later), in fact it is the biggest change in the new version. Some technical info about it can be found here: http://public.avast.com/~tuma/techinfo/ (http://public.avast.com/~tuma/techinfo/)
To find out what's wrong with your mail connection, we need a little bit more info. At least the mailserver and the corresponding system log (/var/log/system.log) messages from com.avast.proxy.
-
ok, but you will have to tell me where the log files are.
my mail server is imap.tools.sky.com and smtp.tools.sky.com
-
is this the log message you need??
Feb 27 19:29:25 Darren-Clarkes-iMac com.avast.proxy[56]: Error connecting to server: direct connection
-
How about this:
Feb 27 08:52:05 kubrick com.avast.proxy[48]: SIGTERM/SIGINT received. Exiting.
Feb 27 08:52:32 kubrick com.avast.proxy[39001]: Starting daemon.
Feb 27 08:52:40 kubrick com.avast.proxy[39001]: Error retreiving KEXT controll socket address: ioctl(): No such file or directory
Feb 27 08:52:40 kubrick com.avast.proxy[39001]: Error connecting KEXT controll socket: connect(): No such file or directory
Feb 27 08:52:40 kubrick com.avast.proxy[39001]: Fatal error. Exiting.
Feb 27 08:52:40 kubrick com.apple.launchd[1] (com.avast.proxy[39001]): Exited with exit code: 1
Feb 27 08:52:40 kubrick com.apple.launchd[1] (com.avast.proxy): Throttling respawn: Will start in 3 seconds
Feb 27 08:52:43 kubrick com.avast.proxy[39096]: Starting daemon.
Feb 27 08:52:43 kubrick com.avast.proxy[39096]: Error retreiving KEXT controll socket address: ioctl(): No such file or directory
Feb 27 08:52:43 kubrick com.avast.proxy[39096]: Error connecting KEXT controll socket: connect(): No such file or directory
Feb 27 08:52:43 kubrick com.avast.proxy[39096]: Fatal error. Exiting.
Feb 27 08:52:43 kubrick com.apple.launchd[1] (com.avast.proxy[39096]): Exited with exit code: 1
Feb 27 08:52:43 kubrick com.apple.launchd[1] (com.avast.proxy): Throttling respawn: Will start in 10 seconds
Feb 27 08:52:57 kubrick com.avast.proxy[48]: Starting daemon.
Feb 27 08:55:20 kubrick com.avast.proxy[48]: AV daemon connection timeout!
Feb 27 08:55:55 kubrick com.avast.proxy[48]: Error connecting to AV daemon: connect(): Connection refused
Feb 27 09:01:21 kubrick com.avast.proxy[48]: SIGTERM/SIGINT received. Exiting.
Feb 27 09:17:52 kubrick com.avast.proxy[47]: Starting daemon.
Feb 27 09:18:55 kubrick com.avast.proxy[47]: SIGTERM/SIGINT received. Exiting.
Feb 27 09:20:15 localhost com.avast.proxy[46]: Starting daemon.
Feb 27 09:20:15 localhost com.avast.proxy[46]: Error connecting to AV daemon: connect(): No such file or directory
Feb 27 09:20:15 localhost com.avast.proxy[46]: client.dropbox.com:https: nodename nor servname provided, or not known
Feb 27 09:20:17 kubrick com.avast.proxy[46]: kextstat -l -b com.avast.PacketForwarder | grep com.avast.PacketForwarder > /dev/null error (1)
Feb 27 09:21:17 kubrick com.avast.proxy[46]: SIGTERM/SIGINT received. Exiting.
Feb 27 09:45:41 kubrick com.avast.proxy[46]: Starting daemon.
Feb 27 09:46:08 kubrick com.avast.proxy[46]: Error connecting to AV daemon: connect(): Connection refused
Feb 27 09:54:57 kubrick com.avast.proxy[46]: SIGTERM/SIGINT received. Exiting.
Feb 27 09:55:12 kubrick com.avast.proxy[1878]: Starting daemon.
Feb 27 09:57:41 kubrick com.avast.proxy[1878]: SIGHUP received. Restarting.
Feb 27 09:58:20 kubrick com.avast.proxy[1878]: SIGTERM/SIGINT received. Exiting.
Feb 27 09:59:08 kubrick com.avast.proxy[48]: Starting daemon.
Feb 27 09:59:36 kubrick com.avast.proxy[48]: Error connecting to AV daemon: connect(): Connection refused
Feb 27 10:06:36 kubrick com.avast.proxy[48]: SIGTERM/SIGINT received. Exiting.
Feb 27 10:09:52 kubrick com.avast.proxy[2432]: Starting daemon.
Feb 27 10:14:45 kubrick com.avast.proxy[2432]: SIGTERM/SIGINT received. Exiting.
Feb 27 10:16:27 kubrick com.avast.proxy[4377]: Starting daemon.
Feb 27 10:20:40 kubrick com.avast.proxy[4377]: SIGTERM/SIGINT received. Exiting.
Feb 27 10:20:53 kubrick com.avast.proxy[5921]: Starting daemon.
Feb 27 10:21:47 kubrick com.avast.proxy[5921]: Error connecting to AV daemon: connect(): Connection refused
Feb 27 10:22:48 kubrick com.avast.proxy[5921]: SIGTERM/SIGINT received. Exiting.
Feb 27 10:23:37 localhost com.avast.proxy[48]: Starting daemon.
Feb 27 10:23:59 kubrick com.avast.proxy[48]: Error connecting to AV daemon: connect(): Connection refused
Feb 27 10:27:21 kubrick com.avast.proxy[48]: SIGHUP received. Restarting.
Feb 27 10:27:51 kubrick com.avast.proxy[48]: Error connecting to AV daemon: connect(): Connection refused
Feb 27 10:28:31 kubrick com.avast.proxy[48]: SSL_read(): EOF
Feb 27 10:30:49 kubrick com.avast.proxy[48]: SIGTERM/SIGINT received. Exiting.
Feb 27 11:01:59 localhost com.avast.proxy[47]: Starting daemon.
Feb 27 11:02:09 kubrick com.avast.proxy[47]: client.dropbox.com:https: nodename nor servname provided, or not known
Feb 27 11:02:10 kubrick com.avast.proxy[47]: kextstat -l -b com.avast.PacketForwarder | grep com.avast.PacketForwarder > /dev/null error (1)
Feb 27 11:05:54 kubrick com.avast.proxy[47]: SIGHUP received. Restarting.
Feb 27 11:07:27 kubrick com.avast.proxy[47]: AV daemon connection timeout!
Feb 27 11:07:44 kubrick com.avast.proxy[47]: Error reading receive buffer: read(): Connection reset by peer
Feb 27 11:07:45 kubrick com.avast.proxy[47]: AV daemon connection timeout!
Feb 27 11:07:52 kubrick com.avast.proxy[47]: SIGHUP received. Restarting.
Feb 27 11:08:22 kubrick com.avast.proxy[47]: AV daemon connection timeout!
Feb 27 11:08:52 kubrick com.avast.proxy[47]: AV daemon connection timeout!
Feb 27 11:08:56 kubrick com.avast.proxy[47]: SIGHUP received. Restarting.
Feb 27 11:09:02 kubrick com.avast.proxy[47]: Error monitoring AV daemon socket: select(): Interrupted system call
Feb 27 11:09:32 kubrick com.avast.proxy[47]: AV daemon connection timeout!
Feb 27 11:09:40 kubrick com.avast.proxy[47]: SIGHUP received. Restarting.
Feb 27 11:10:10 kubrick com.avast.proxy[47]: AV daemon connection timeout!
Feb 27 11:10:40 kubrick com.avast.proxy[47]: AV daemon connection timeout!
Feb 27 11:11:10 kubrick com.avast.proxy[47]: AV daemon connection timeout!
Feb 27 11:11:40 kubrick com.avast.proxy[47]: AV daemon connection timeout!
Feb 27 11:12:10 kubrick com.avast.proxy[47]: AV daemon connection timeout!
Feb 27 11:12:41 kubrick com.avast.proxy[47]: AV daemon connection timeout!
Feb 27 11:12:47 kubrick com.avast.proxy[47]: AV daemon connection timeout!
Feb 27 11:12:53 kubrick com.avast.proxy[47]: AV daemon connection timeout!
Feb 27 11:13:20 kubrick com.avast.proxy[47]: AV daemon connection timeout!
Feb 27 11:13:41 kubrick com.avast.proxy[47]: AV daemon connection timeout!
Feb 27 11:14:09 kubrick com.avast.proxy[47]: AV daemon connection timeout!
Feb 27 11:14:39 kubrick com.avast.proxy[47]: AV daemon connection timeout!
Feb 27 11:16:59 kubrick com.avast.proxy[47]: AV daemon connection timeout!
Feb 27 11:17:05 kubrick com.avast.proxy[47]: AV daemon connection timeout!
Feb 27 11:17:10 kubrick com.avast.proxy[47]: AV daemon connection timeout!
Feb 27 11:18:51 kubrick com.avast.proxy[47]: Error reading receive buffer: read(): Connection reset by peer
Feb 27 11:19:32 kubrick com.avast.proxy[47]: Error reading receive buffer: read(): Connection reset by peer
Feb 27 11:21:05 kubrick com.avast.proxy[47]: Error reading receive buffer: read(): Connection reset by peer
Feb 27 11:31:18 kubrick com.avast.proxy[47]: SIGHUP received. Restarting.
Feb 27 11:37:31 kubrick com.avast.proxy[47]: SIGHUP received. Restarting.
Feb 27 11:50:32 kubrick com.avast.proxy[47]: Error reading receive buffer: read(): Connection reset by peer
Feb 27 11:58:48 kubrick com.avast.proxy[47]: Error connecting to server: direct connection
Feb 27 11:58:49 kubrick com.avast.proxy[47]: Error reading receive buffer: read(): Connection reset by peer
-
and...
Feb 27 12:08:04 kubrick com.avast.proxy[47]: SIGHUP received. Restarting.
Feb 27 12:10:31 kubrick com.avast.proxy[47]: SIGHUP received. Restarting.
Feb 27 12:11:40 kubrick com.avast.proxy[47]: SIGHUP received. Restarting.
Feb 27 12:11:50 kubrick com.avast.proxy[47]: SIGHUP received. Restarting.
Feb 27 12:16:00 kubrick com.avast.proxy[47]: Error reading receive buffer: read(): Connection reset by peer
Feb 27 12:16:50 kubrick com.avast.proxy[47]: Error reading receive buffer: read(): Connection reset by peer
Feb 27 12:30:16 kubrick com.avast.proxy[47]: SIGHUP received. Restarting.
Feb 27 12:31:11 kubrick com.avast.proxy[47]: SIGHUP received. Restarting.
Feb 27 12:34:50 kubrick com.avast.proxy[47]: Error reading receive buffer: read(): Connection reset by peer
Feb 27 14:00:59 kubrick com.avast.proxy[47]: SSL_connect(): Connection reset by peer
Feb 27 14:01:12 kubrick com.avast.proxy[47]: SSL_connect(): EOF
Feb 27 14:01:42 kubrick com.avast.proxy[47]: SSL_connect(): EOF
Feb 27 14:02:06 kubrick com.avast.proxy[47]: SSL_connect(): Connection reset by peer
Feb 27 14:03:30 kubrick com.avast.proxy[47]: SIGHUP received. Restarting.
Feb 27 14:05:15 kubrick com.avast.proxy[47]: SIGHUP received. Restarting.
Feb 27 14:32:41 kubrick com.avast.proxy[47]: Error reading receive buffer: read(): Connection reset by peer
Feb 27 14:35:23 kubrick com.avast.proxy[47]: Error connecting to server: direct connection
Feb 27 14:35:43 kubrick com.avast.proxy[47]: Error reading receive buffer: read(): Connection reset by peer
Feb 27 14:36:23 kubrick com.avast.proxy[47]: Error connecting to server: direct connection
Feb 27 14:36:30 kubrick com.avast.proxy[47]: Error reading receive buffer: read(): Connection reset by peer
Feb 27 14:36:35 kubrick com.avast.proxy[47]: Error connecting to server: direct connection
Feb 27 14:36:37 kubrick com.avast.proxy[47]: Error reading receive buffer: read(): Connection reset by peer
Feb 27 14:36:40 kubrick com.avast.proxy[47]: Error connecting to server: direct connection
Feb 27 14:37:43 kubrick com.avast.proxy[47]: Error connecting to server: direct connection
Feb 27 14:38:14 kubrick com.avast.proxy[47]: Error reading receive buffer: read(): Connection reset by peer
Feb 27 14:38:14 kubrick com.avast.proxy[47]: Error connecting to server: direct connection
Feb 27 14:38:24 kubrick com.avast.proxy[47]: Error reading receive buffer: read(): Connection reset by peer
Feb 27 14:38:30 kubrick com.avast.proxy[47]: Error connecting to server: direct connection
Feb 27 14:38:36 kubrick com.avast.proxy[47]: Error reading receive buffer: read(): Connection reset by peer
Feb 27 16:34:08 kubrick com.avast.proxy[47]: Error reading receive buffer: read(): Connection reset by peer
Feb 27 16:34:54 kubrick com.avast.proxy[47]: Error reading receive buffer: read(): Connection reset by peer
Feb 27 16:35:30 kubrick com.avast.proxy[47]: Error reading receive buffer: read(): Connection reset by peer
Feb 27 16:36:29 kubrick com.avast.proxy[47]: Error reading receive buffer: read(): Connection reset by peer
Feb 27 16:36:59 kubrick com.avast.proxy[47]: Error reading receive buffer: read(): Connection reset by peer
Feb 27 16:38:25 kubrick com.avast.proxy[47]: Error reading receive buffer: read(): Connection reset by peer
Feb 27 16:39:03 kubrick com.avast.proxy[47]: Error reading receive buffer: read(): Connection reset by peer
-
Thanks for the logs. There is definitely some issue with the antivirus engine (daemon) on your system, but even a non working engine should not break the mailshield in a way that it wan't let mail traffic through.
Can you try to disable IPv6 support in the mailshield configuration and see, if that helps? Broken IPv6 in your network could be the reason of the problems (at least of the "direct connection" issues).
-
Thanks tumic,
turned off the ipv6 support and everything seems fine, i have also had to turn it off on the web shield as it made my internet connection remind me of the dial up days.