Can anyone can shed any light on an annoying problem which appears to have started since I installed Avast for Mac a few weeks ago, (although I cannot be sure that it is the root of the problem)? I have recently created a number of IMAP based email accounts on all of my Macs and mobile devices. The Macs were previously set up with POP accounts, but I want all devices to sync, so followed the instructions supplied by my ISP and set up the six or so accounts each with the correct account information, passwords, server setting etc… I use Apple Mail to retrieve, store and send emails. About a week ago I noticed, (by looking at my WebMail account through my ISP), that some emails were ‘stuck’ on the mail server and others, (random selections), had been delivered. I questioned Apple by means of a telephone support call and my ISP and neither can identify a reason why this would be randomly happening.
So yesterday I decided to switch off the Mail Shield part of Avast and have left the email system off all day. When I checked tonight, all emails have been delivered to my Mail Inboxes correctly, including the ones that were ‘stuck’.
Now, although this seems quite conclusive in that it appears that Avast is preventing emails from being picked up at my Mail client end, I had also deactivated all of the email accounts on my mobile devices as I wondered if the devices were in some way affecting the Mac’s abilities to receive the same emails. All of this has confused me, so I intend to try another experiment tomorrow and switch Mail Shield back on and see if mail is again prevented from being picked up.
Mail is being sent from my mail client without any problem and I am using the most current versions of MaxOS, iOS and Avast.
Does anyone else know if this is a ‘common’ or potential reason for the non-delivery of IMAP type email? Is it at all possible that Avast can ‘mark’ an email on the server as unsuitable for retrieval? It seems odd if it can, as I would have thought that it would just deliver it and stick it in the ‘Junk’ folder if it thought it was suspect.
Sorry, but I am a little confused by your question.
Where would I find the system log and what does com.avast.proxy mean and what should I do with it?!
I don’t get any visible error messages through Avast and there are no error messages generated by Mail or my ISP.
Sorry to be dim!
I encountered the same problem as well. i found that Avast’s proxy does NOT work well with ssl under certain circumstances, such as when Apple mail client try to establish connection via ssl.
The simplest solution to resolve that is (only my option) to tell avast mail shield not to scan secured connections.
To do that, open avast preferences, click “advanced…” on the right side of mail shield,
in general page, uncheck “scan secured connections”.
I would rather take risks than miss all incoming mails.
Many thanks for your replies…they are very helpful and I think have narrowed down the issue. I can’t see that it is anything other than an Avast issue. Everything else is a constant; the only thing I’ve changed is installing Avast which has stopped email being delivered to me from the mail server.
zhoupeng: thank you for your post. I think you have identified the issue that is the same as mine. I tried (following advice from Avast technical support) switching off the “Enable IPv6” (they didn’t mention the Scan Secure Connection idea), but this has not completely solved the issue as my “mail@…co.uk” mailbox got stuck this evening. I then left the “Enable IPv6” switched off and in addition turned off the “Scan Secure Connection” and hey presto all of the stuck emails suddenly arrived. Can you tell me if I should leave “Mail Shield” enabled or turn this function off too?
moroni: I have pasted some of the message from the console.app as follows, (I have edited it very slightly to remove a load of repeated lines in today’s report, otherwise it would have gone on for ages!). I can’t make head nor tail of the output, but I am guessing that you can. Any ideas? There doesn’t appear to be any specific reference to a mailbox error, but there are a number of references to “timeouts”, “SSL” and “no such directory”…can you decipher it for me?
Thank you all for your help.
Chris
15/07/2013 22:26:23.000 kernel[0]: com.avast.AvastFileShield: Unmount of /Volumes/Cathy Clone detected: Cleaning cached entries.
16/07/2013 19:07:44.766 com.avast.proxy[112]: Starting daemon.
16/07/2013 19:07:44.774 com.avast.proxy[112]: Error opening log file: /var/log/avast/proxy.log: No such file or directory
16/07/2013 19:07:44.774 com.avast.proxy[112]: Error connecting to scan socket: /Library/Application Support/Avast/socket.mail: No such file or directory
16/07/2013 19:07:44.775 com.avast.proxy[112]: Error connecting to scan socket: /Library/Application Support/Avast/socket.web: No such file or directory
16/07/2013 19:07:45.000 kernel[0]: com.avast.AvastFileShield: Started.
16/07/2013 19:07:45.117 com.apple.launchd[1]: (com.avast.account[117]) Exited with code: 2
16/07/2013 19:07:45.121 com.avast.proxy[112]: client.dropbox.com:https: nodename nor servname provided, or not known
16/07/2013 19:10:55.243 launchctl[297]: launchctl: no plist was returned for: /Users/B??&C??/Library/LaunchAgents/com.avast.install.plist
16/07/2013 19:10:55.243 launchctl[297]: launchctl: no plist was returned for: /Users/B??&C??/Library/LaunchAgents/com.avast.install.plist
16/07/2013 19:11:10.123 com.avast.proxy[112]: Error connecting to server: connection timeout
16/07/2013 19:12:17.482 com.avast.proxy[112]: Error connecting to server: connection timeout
16/07/2013 19:12:28.000 kernel[0]: com.avast.AvastFileShield: Unmount of /private/tmp/UpdateEngine-mount.h7BGocSlD2 detected: Cleaning cached entries.
16/07/2013 19:13:00.000 kernel[0]: com.avast.AvastFileShield: Unmount of /private/tmp/UpdateEngine-mount.4u0KCUMhi3 detected: Cleaning cached entries.
16/07/2013 19:13:03.940 com.avast.helper[422]: Pop socket closed by peer
16/07/2013 19:13:17.609 com.avast.proxy[112]: Error connecting to server: connection timeout
16/07/2013 19:32:08.740 com.avast.proxy[112]: Error reading receive buffer: read(): Connection reset by peer
16/07/2013 19:33:12.668 com.avast.proxy[112]: Error connecting to server: connection timeout
16/07/2013 19:42:08.810 com.avast.proxy[112]: Error reading receive buffer: read(): Connection reset by peer
16/07/2013 19:44:11.627 com.avast.proxy[112]: Error connecting to server: connection timeout
16/07/2013 19:45:11.176 com.avast.proxy[112]: Error reading receive buffer: read(): Connection reset by peer
16/07/2013 19:47:15.082 com.avast.proxy[112]: Error connecting to server: connection timeout
16/07/2013 19:56:08.832 com.avast.proxy[112]: Error reading receive buffer: read(): Connection reset by peer
16/07/2013 19:58:11.605 com.avast.proxy[112]: Error connecting to server: connection timeout
16/07/2013 20:14:08.674 com.avast.proxy[112]: Error reading receive buffer: read(): Connection reset by peer
16/07/2013 20:14:12.684 com.avast.proxy[112]: Error connecting to server: connection timeout
16/07/2013 20:15:06.502 com.avast.proxy[112]: SSL_read(): Connection reset by peer
16/07/2013 21:41:24.877 com.avast.proxy[112]: SSL_read(): Connection reset by peer
16/07/2013 21:41:25.002 com.avast.proxy[112]: SSL_read(): Connection reset by peer
16/07/2013 21:41:27.473 com.avast.proxy[112]: Error reading receive buffer: read(): Connection reset by peer
16/07/2013 21:41:30.759 com.avast.proxy[112]: Error connecting to server: connection timeout
16/07/2013 21:41:31.195 com.avast.proxy[112]: Error reading receive buffer: read(): Connection reset by peer
16/07/2013 21:41:31.195 com.avast.proxy[112]: Error reading receive buffer: read(): Connection reset by peer
16/07/2013 21:41:31.293 com.avast.proxy[112]: Error reading receive buffer: read(): Connection reset by peer
16/07/2013 21:41:34.768 com.avast.proxy[112]: Error connecting to server: connection timeout
16/07/2013 21:41:38.468 com.avast.proxy[112]: Error reading receive buffer: read(): Connection reset by peer
16/07/2013 21:41:38.499 com.avast.proxy[112]: Error reading receive buffer: read(): Connection reset by peer
16/07/2013 21:41:38.541 com.avast.proxy[112]: Error reading receive buffer: read(): Connection reset by peer
16/07/2013 21:41:41.546 com.avast.proxy[112]: Error connecting to server: connection timeout
16/07/2013 21:41:57.673 com.avast.proxy[112]: SSL_read(): Operation timed out
16/07/2013 21:43:32.206 com.avast.proxy[112]: SIGHUP received. Restarting.
16/07/2013 21:43:32.206 com.avast.proxy[112]: Error opening log file: /var/log/avast/proxy.log: No such file or directory
16/07/2013 21:47:05.990 com.avast.proxy[112]: Error reading receive buffer: read(): Connection reset by peer
16/07/2013 21:47:37.126 com.avast.proxy[112]: Error reading receive buffer: read(): Connection reset by peer
16/07/2013 21:47:41.387 com.avast.proxy[112]: Error reading receive buffer: read(): Connection reset by peer
16/07/2013 21:47:48.275 com.avast.proxy[112]: Error reading receive buffer: read(): Connection reset by peer
16/07/2013 21:48:19.714 com.avast.proxy[112]: SSL_read(): EOF
16/07/2013 21:48:19.714 com.avast.proxy[112]: SSL_read(): EOF
16/07/2013 21:48:19.715 com.avast.proxy[112]: SSL_read(): EOF
16/07/2013 21:48:19.715 com.avast.proxy[112]: SSL_read(): EOF
16/07/2013 21:49:01.082 avast![2077]: event_master_disconnected
16/07/2013 21:51:05.957 com.avast.proxy[112]: Error reading receive buffer: read(): Connection reset by peer
16/07/2013 21:52:16.331 com.avast.proxy[112]: SIGHUP received. Restarting.
16/07/2013 21:52:16.331 com.avast.proxy[112]: Error opening log file: /var/log/avast/proxy.log: No such file or directory
Well, if you disable the “Scan Secured Connections” option it is as if you would completely disable
the mailshield in most cases. In other words the mail traffic does not go through the mailshield and is
not scanned when you switch either of them to “off”.
There is nothing interresting in the log, that could help us to understand the reason of your problem. What mailserver
(mail account provider) do you use? What email client (exact version) do you use?
Hi tumic, switching off the scan secure connections has certainly done he trick. My emails are now being delivered to all mail accounts.
I use PlusNet for my ISP and mail accounts via their imap.plus.net server.
I also use Apple Mail to send and receive emails; I don’t use webmail or gmail as a rule. My Apple Mail Version is: 6.5 (1508)
Thanks Chris
I, too am having trouble retrieving mail on my Mac.
I disabled the IPv6 (unchecked the box) feature. Still no luck.
I disabled the Scan Secured Connections (unchecked the box). Still no luck.
It’s only 1 account in my mail program from which I cannot receive mail since installing Avast.
The APOP’s match on it and the other accounts, the incoming servers match, the outgoing servers match. I can’t for the life of me determine why it won’t retrieve mail from my main account.
I’ve posted my CONSOLE (AVAST) search results in the hope that someone can determine what is going on. Thank you!
12/5/13 8:20:44 AM com.avast.helper[239] Can’t open input server /Library/InputManagers/QuicKeysIM
12/5/13 8:25:57 AM com.avast.helper[239] Pop socket closed by peer
12/6/13 8:20:42 AM com.avast.helper[231] Can’t open input server /Library/InputManagers/QuicKeysIM
12/6/13 8:26:14 AM com.avast.helper[231] Pop socket closed by peer
12/6/13 8:34:24 AM com.avast.helper[231] Pop socket closed by peer
12/6/13 8:42:07 AM com.avast.helper[231] Pop socket closed by peer
12/6/13 8:51:13 AM com.avast.helper[231] Pop socket closed by peer
12/6/13 2:59:35 PM com.avast.helper[231] Pop socket closed by peer
12/9/13 8:15:05 AM com.avast.helper[231] Can’t open input server /Library/InputManagers/QuicKeysIM
12/9/13 2:20:45 PM com.avast.helper[231] Pop socket closed by peer
12/9/13 7:33:57 PM com.avast.helper[236] Can’t open input server /Library/InputManagers/QuicKeysIM
12/10/13 8:20:41 AM com.avast.helper[233] Can’t open input server /Library/InputManagers/QuicKeysIM
12/10/13 8:26:08 AM com.avast.helper[233] Pop socket closed by peer
12/10/13 2:32:16 PM com.avast.helper[228] Can’t open input server /Library/InputManagers/QuicKeysIM
12/11/13 8:20:46 AM com.avast.helper[231] Can’t open input server /Library/InputManagers/QuicKeysIM
12/11/13 8:26:06 AM com.avast.helper[231] Pop socket closed by peer
12/11/13 1:43:58 PM com.avast.helper[225] Can’t open input server /Library/InputManagers/QuicKeysIM
12/11/13 1:52:13 PM com.avast.helper[225] Pop socket closed by peer
12/11/13 2:00:41 PM com.avast.helper[225] Pop socket closed by peer
12/11/13 2:09:43 PM com.avast.helper[225] Pop socket closed by peer
12/11/13 2:17:48 PM avast![1422] Can’t open input server /Library/InputManagers/QuicKeysIM
12/11/13 2:19:25 PM avast![1422] event_master_disconnected
12/11/13 2:30:55 PM com.avast.helper[225] Can’t open input server /Library/InputManagers/QuicKeysIM
12/11/13 2:39:53 PM com.avast.helper[225] Pop socket closed by peer
12/11/13 2:53:09 PM avast![1086] Can’t open input server /Library/InputManagers/QuicKeysIM
12/11/13 2:53:50 PM avast![1086] event_master_disconnected
12/8/15 2:22:04.217 PM authexec[696]: executing /Library/Application Support/Avast/components/uninstall/com.avast.uninstall.app/Contents/MacOS/install0
12/8/15 2:22:10.078 PM com.avast.fileshield[275]: Stopping File Shield…
12/8/15 2:22:10.000 PM kernel[0]: com.avast.fileshield: Stopped.
12/8/15 2:22:10.644 PM com.avast.proxy[242]: SIGTERM/SIGINT received. Exiting.
12/8/15 2:22:11.473 PM com.avast.daemon[190]: SIGTERM/SIGINT received. Exiting.
12/8/15 2:26:55.000 PM kernel[0]: hfs: mounted Avast Mac Security on device disk1s1
12/8/15 2:26:55.184 PM mds[58]: (Volume.Normal:2464) volume:0x7fc3ac06c000 ********** Bootstrapped Creating a default store:1 SpotLoc:(null) SpotVerLoc:(null) occlude:0 /Volumes/Avast Mac Security
12/8/15 2:26:55.382 PM fseventsd[44]: Logging disabled completely for device:1: /Volumes/Avast Mac Security
12/8/15 2:27:35.248 PM Installer[1093]: Failed to download http://download.ff.avast.com/mac/vps9/vps915120800.ful:Error Domain=NSURLErrorDomain Code=-1005 “The network connection was lost.” UserInfo={NSUnderlyingError=0x7fee1dab6580 {Error Domain=kCFErrorDomainCFNetwork Code=-1005 “The network connection was lost.” UserInfo={NSErrorFailingURLStringKey=http://download.ff.avast.com/mac/vps9/vps915120800.ful, _kCFStreamErrorDomainKey=1, NSErrorPeerAddressKey=<CFData 0x7fee1d84c7c0 [0x7fff73678390]>{length = 16, capacity = 16, bytes = 0x1002005017c460fe0000000000000000}, _kCFStreamErrorCodeKey=57, NSErrorFailingURLKey=http://download.ff.avast.com/mac/vps9/vps915120800.ful, NSLocalizedDescription=The network connection was lost.}}, NSErrorFailingURLStringKey=http://download.ff.avast.com/mac/vps9/vps915120800.ful, NSErrorFailingURLKey=http://download.ff.avast.com/mac/vps9/vps915120800.ful, _kCFStreamErrorDomainKey=1, _kCFStreamErrorCodeKey=57, NSLocalizedDescription=The network connection was lost.}
12/8/15 2:29:36.742 PM com.apple.xpc.launchd[1]: (com.avast.daemon) This service is defined to be constantly running and is inherently inefficient.
12/8/15 2:29:36.755 PM com.avast.daemon[1550]: Starting daemon.
12/8/15 2:29:36.827 PM sudo[1552]: root : TTY=unknown ; PWD=/Library/Application Support/Avast/tmpInstall ; USER=; COMMAND=/bin/launchctl load -S Aqua /Library/LaunchAgents/com.avast.update-agent.plist
12/8/15 2:29:36.833 PM com.apple.xpc.launchd[1]: (com.avast.update-agent) This service is defined to be constantly running and is inherently inefficient.
12/8/15 2:29:36.911 PM sudo[1563]: root : TTY=unknown ; PWD=/Library/Application Support/Avast/tmpInstall ; USER=; COMMAND=/bin/launchctl load -S Aqua /Library/LaunchAgents/com.avast.userinit.plist
12/8/15 2:29:41.712 PM com.avast.daemon[1550]: Loaded VPS #15120800
12/8/15 2:29:41.803 PM com.apple.xpc.launchd[1]: (com.avast.service) This service is defined to be constantly running and is inherently inefficient.
12/8/15 2:29:42.700 PM com.apple.xpc.launchd[1]: (com.avast.proxy) This service is defined to be constantly running and is inherently inefficient.
12/8/15 2:29:42.727 PM com.avast.proxy[1672]: Starting daemon.
12/8/15 2:29:44.982 PM com.avast.proxy[1672]: swquery.apple.com:https: nodename nor servname provided, or not known
12/8/15 2:29:45.000 PM kernel[0]: com.avast.fileshield: Started.
12/8/15 2:29:45.895 PM com.apple.xpc.launchd[1]: (com.avast.fileshield) This service is defined to be constantly running and is inherently inefficient.
12/8/15 2:29:45.920 PM com.avast.fileshield[1723]: Starting File Shield (build Oct 12 2015 17:04:25)
12/8/15 2:29:45.921 PM com.avast.fileshield[1723]: config_load: ini_read() failed [-1]. Will use defaults.
12/8/15 2:29:52.154 PM com.apple.xpc.launchd[1]: (com.avast.helper) This service is defined to be constantly running and is inherently inefficient.
12/8/15 2:30:16.997 PM com.avast.proxy[1672]: SIGHUP received. Reloading…
12/8/15 2:30:17.375 PM com.avast.proxy[1672]: swquery.apple.com:https: nodename nor servname provided, or not known
12/8/15 2:30:19.028 PM com.avast.proxy[1672]: SIGHUP received. Reloading…
12/8/15 2:30:19.035 PM com.avast.proxy[1672]: swquery.apple.com:https: nodename nor servname provided, or not known
12/8/15 2:30:32.113 PM com.avast.proxy[1672]: SIGHUP received. Reloading…
12/8/15 2:30:32.464 PM com.avast.proxy[1672]: swquery.apple.com:https: nodename nor servname provided, or not known
12/8/15 2:30:32.539 PM com.avast.proxy[1672]: SIGHUP received. Reloading…
12/8/15 2:30:32.587 PM com.avast.proxy[1672]: swquery.apple.com:https: nodename nor servname provided, or not known
12/8/15 2:30:33.319 PM com.avast.proxy[1672]: SIGHUP received. Reloading…
12/8/15 2:30:33.336 PM com.avast.proxy[1672]: swquery.apple.com:https: nodename nor servname provided, or not known
12/8/15 2:30:33.685 PM com.avast.proxy[1672]: SIGHUP received. Reloading…
12/8/15 2:30:33.721 PM com.avast.proxy[1672]: swquery.apple.com:https: nodename nor servname provided, or not known
12/8/15 2:31:01.000 PM kernel[0]: com.avast.fileshield: Unmount of /Volumes/Recovery HD detected: Cleaning cached entries.
12/8/15 2:31:01.933 PM com.avast.fileshield[1723]: Detected unmount of /Volumes/Recovery HD
12/8/15 2:31:31.974 PM com.avast.proxy[1672]: SIGHUP received. Reloading…
12/8/15 2:31:32.747 PM com.avast.proxy[1672]: swquery.apple.com:https: nodename nor servname provided, or not known
12/8/15 2:31:33.026 PM com.avast.proxy[1672]: SIGHUP received. Reloading…
12/8/15 2:31:33.032 PM com.avast.proxy[1672]: swquery.apple.com:https: nodename nor servname provided, or not known