Author Topic: Mailshield problem  (Read 10389 times)

0 Members and 1 Guest are viewing this topic.

Offline pastore.a

  • Newbie
  • *
  • Posts: 6
Mailshield problem
« on: June 02, 2011, 01:37:20 PM »
Hello,

I have a problem with the mail shield. When I turn it on I can't receive the emails anymore.
I use Mail.app and Notify and with both the programs the problem is the same (It seems to be a proxy problem).
I have installed Little Snitch 2 and Glimmer Blocker too (the last one is not activated).

Can someone help me?
Thanks

Andrew
« Last Edit: June 02, 2011, 02:28:19 PM by Milos »

Offline tumic

  • Moderator
  • Advanced Poster
  • *
  • Posts: 724
Re: Mailshield problem
« Reply #1 on: June 02, 2011, 02:31:12 PM »
Please run the following command from terminal and post the output here, or send it to my email

Code: [Select]
cat /var/log/system.log | grep 'proxy\[[0-9]*\]'

Offline pastore.a

  • Newbie
  • *
  • Posts: 6
Re: Mailshield problem
« Reply #2 on: June 02, 2011, 04:28:13 PM »
Jun  2 09:47:23 iMac-20 proxy[1624]: Starting daemon.
Jun  2 09:47:23 iMac-20 proxy[1624]: Error opening hosts file: fopen(): No such file or directory
Jun  2 09:51:35 iMac-20 proxy[1624]: Error connecting to server: connect(): Invalid argument
Jun  2 09:52:10 iMac-20 proxy[1624]: Error connecting to server: connect(): Invalid argument
Jun  2 09:53:07 iMac-20 proxy[1624]: Error connecting to server: connect(): Invalid argument
Jun  2 09:53:41 iMac-20 proxy[1624]: Error connecting to server: connect(): Invalid argument
Jun  2 09:54:07 iMac-20 proxy[1624]: Error connecting to server: connect(): Invalid argument
Jun  2 09:54:56 iMac-20 proxy[1624]: Error connecting to server: connect(): Invalid argument
Jun  2 09:55:07 iMac-20 proxy[1624]: Error connecting to server: connect(): Invalid argument
Jun  2 09:55:31 iMac-20 proxy[1624]: SIGTERM received. Exiting.
Jun  2 09:55:44 iMac-20 proxy[1971]: Starting daemon.
Jun  2 09:55:44 iMac-20 proxy[1971]: Error opening hosts file: fopen(): No such file or directory
Jun  2 09:56:21 iMac-20 proxy[1971]: Error connecting to server: connect(): Invalid argument
Jun  2 09:58:41 iMac-20 proxy[1971]: Error connecting to server: connect(): Invalid argument
Jun  2 09:59:56 iMac-20 proxy[1971]: Error connecting to server: connect(): Invalid argument
Jun  2 10:01:11 iMac-20 proxy[1971]: Error connecting to server: connect(): Invalid argument
Jun  2 10:02:26 iMac-20 proxy[1971]: Error connecting to server: connect(): Invalid argument
Jun  2 10:03:41 iMac-20 proxy[1971]: Error connecting to server: connect(): Invalid argument
Jun  2 10:04:56 iMac-20 proxy[1971]: Error connecting to server: connect(): Invalid argument
Jun  2 10:06:11 iMac-20 proxy[1971]: Error connecting to server: connect(): Invalid argument
Jun  2 10:06:36 iMac-20 proxy[1971]: Error connecting to server: connect(): Invalid argument
Jun  2 10:06:41 iMac-20 proxy[1971]: Error connecting to server: connect(): Invalid argument
Jun  2 10:07:26 iMac-20 proxy[1971]: Error connecting to server: connect(): Invalid argument
Jun  2 10:07:41 iMac-20 proxy[1971]: Error connecting to server: connect(): Invalid argument
Jun  2 10:07:44 iMac-20 proxy[1971]: Error connecting to server: connect(): Invalid argument
Jun  2 10:08:41 iMac-20 proxy[1971]: Error connecting to server: connect(): Invalid argument
Jun  2 10:08:50 iMac-20 proxy[1971]: Error connecting to server: connect(): Invalid argument
Jun  2 10:09:21 iMac-20 proxy[1971]: Error reading receive buffer: read(): Connection reset by peer
Jun  2 10:09:24 iMac-20 proxy[1971]: Error reading receive buffer: read(): Connection reset by peer
Jun  2 10:09:50 iMac-20 proxy[1971]: Error connecting to server: connect(): Invalid argument
Jun  2 10:09:56 iMac-20 proxy[1971]: Error connecting to server: connect(): Invalid argument
Jun  2 10:10:51 iMac-20 proxy[1971]: Error connecting to server: connect(): Invalid argument
Jun  2 10:11:11 iMac-20 proxy[1971]: Error connecting to server: connect(): Invalid argument
Jun  2 10:11:51 iMac-20 proxy[1971]: Error connecting to server: connect(): Invalid argument
Jun  2 10:13:04 iMac-20 proxy[1971]: Error connecting to server: connect(): Invalid argument
Jun  2 10:13:41 iMac-20 proxy[1971]: Error connecting to server: connect(): Invalid argument
Jun  2 10:14:56 iMac-20 proxy[1971]: Error connecting to server: connect(): Invalid argument
Jun  2 10:15:46 iMac-20 proxy[1971]: Error reading receive buffer: read(): Connection reset by peer
Jun  2 10:16:11 iMac-20 proxy[1971]: Error connecting to server: connect(): Invalid argument
Jun  2 10:17:13 iMac-20 proxy[1971]: Error connecting to server: connect(): Invalid argument
Jun  2 10:18:09 iMac-20 proxy[1971]: Error connecting to server: connect(): Invalid argument
Jun  2 10:18:41 iMac-20 proxy[1971]: Error connecting to server: connect(): Invalid argument
Jun  2 10:19:04 iMac-20 proxy[1971]: Error connecting to server: connect(): Invalid argument
Jun  2 10:19:23 iMac-20 proxy[1971]: Error connecting to server: connect(): Invalid argument
Jun  2 10:19:37 iMac-20 proxy[1971]: Error connecting to server: connect(): Invalid argument
Jun  2 10:19:56 iMac-20 proxy[1971]: Error connecting to server: connect(): Invalid argument
Jun  2 10:20:17 iMac-20 proxy[1971]: Error connecting to server: connect(): Invalid argument
Jun  2 10:20:38 iMac-20 proxy[1971]: Error connecting to server: connect(): Invalid argument
Jun  2 10:20:58 iMac-20 proxy[1971]: Error connecting to server: connect(): Invalid argument
Jun  2 10:21:09 iMac-20 proxy[1971]: Error connecting to server: connect(): Invalid argument
Jun  2 10:21:11 iMac-20 proxy[1971]: Error connecting to server: connect(): Invalid argument
Jun  2 10:21:33 iMac-20 proxy[1971]: Error connecting to server: connect(): Invalid argument
Jun  2 10:21:48 iMac-20 proxy[1971]: SIGTERM received. Exiting.
Jun  2 12:48:19 iMac-20 proxy[4035]: Starting daemon.
Jun  2 12:48:19 iMac-20 proxy[4035]: Error opening hosts file: fopen(): No such file or directory
Jun  2 12:48:38 iMac-20 proxy[4035]: Error connecting to server: connect(): Invalid argument
Jun  2 12:49:48 iMac-20 proxy[4035]: Error connecting to server: connect(): Invalid argument
Jun  2 12:50:32 iMac-20 proxy[4035]: Error connecting to server: connect(): Invalid argument
Jun  2 12:50:44 iMac-20 proxy[4035]: Error reading receive buffer: read(): Connection reset by peer
Jun  2 12:53:41 iMac-20 proxy[4035]: Error connecting to server: connect(): Invalid argument
Jun  2 12:54:47 localhost proxy[152]: Starting daemon.
Jun  2 12:54:47 localhost proxy[152]: Error opening hosts file: fopen(): No such file or directory
Jun  2 12:56:14 iMac-20 proxy[152]: Error connecting to server: connect(): Invalid argument
Jun  2 12:56:54 iMac-20 proxy[152]: Error connecting to server: connect(): Invalid argument
Jun  2 12:57:29 iMac-20 proxy[152]: Error connecting to server: connect(): Invalid argument
Jun  2 12:57:55 iMac-20 proxy[152]: Error connecting to server: connect(): Invalid argument
Jun  2 12:58:44 iMac-20 proxy[152]: Error connecting to server: connect(): Invalid argument
Jun  2 12:59:45 iMac-20 proxy[152]: Error connecting to server: connect(): Invalid argument
Jun  2 12:59:59 iMac-20 proxy[152]: Error connecting to server: connect(): Invalid argument
Jun  2 13:00:54 iMac-20 proxy[152]: Error connecting to server: connect(): Invalid argument
Jun  2 13:01:10 iMac-20 proxy[152]: Defective HTTP response!
Jun  2 13:01:14 iMac-20 proxy[152]: Error connecting to server: connect(): Invalid argument
Jun  2 13:01:20 iMac-20 proxy[152]: Defective HTTP response!
Jun  2 13:01:47 iMac-20 proxy[152]: Error connecting to server: connect(): Invalid argument
Jun  2 13:02:30 iMac-20 proxy[152]: Error connecting to server: connect(): Invalid argument
Jun  2 13:03:47 iMac-20 proxy[152]: Error connecting to server: connect(): Invalid argument
Jun  2 13:05:34 iMac-20 proxy[152]: Error connecting to server: connect(): Invalid argument
Jun  2 13:05:45 iMac-20 proxy[152]: Error connecting to server: connect(): Invalid argument
Jun  2 13:06:15 iMac-20 proxy[152]: Error connecting to server: connect(): Invalid argument
Jun  2 13:06:42 iMac-20 proxy[152]: Error connecting to server: connect(): Invalid argument
Jun  2 13:07:16 iMac-20 proxy[152]: Error reading receive buffer: read(): Connection reset by peer
Jun  2 13:07:30 iMac-20 proxy[152]: Error connecting to server: connect(): Invalid argument
Jun  2 13:08:42 iMac-20 proxy[152]: Error connecting to server: connect(): Invalid argument
Jun  2 13:09:42 iMac-20 proxy[152]: Error connecting to server: connect(): Invalid argument
Jun  2 13:11:15 iMac-20 proxy[152]: Error connecting to server: connect(): Invalid argument
Jun  2 13:12:30 iMac-20 proxy[152]: Error connecting to server: connect(): Invalid argument
Jun  2 13:13:34 iMac-20 proxy[152]: Error connecting to server: connect(): Invalid argument
Jun  2 13:14:34 iMac-20 proxy[152]: Error connecting to server: connect(): Invalid argument
Jun  2 13:15:30 iMac-20 proxy[152]: Error reading receive buffer: read(): Connection reset by peer
Jun  2 13:15:53 iMac-20 proxy[152]: SIGTERM received. Exiting.

Dr. D

  • Guest
Re: Mailshield problem
« Reply #3 on: June 03, 2011, 07:45:54 AM »
Same problem here, with one additional glitch. Mailshield and WebShield controls are linked. Either they're both on, or they're both off. i.e., Turning off the Mailshield also turns off the web shield (and restores my email functionality). Turning off the Web Shield also turns off the Mailshield. Similarly, both shields turn "on" together.

Tumic, here's the requested output of the terminal command you posted earlier:
[cat /var/log/system.log | grep 'proxy\[[0-9]*\]']

Jun  2 10:50:37 David-Gues-MacBook-Pro proxy[12383]: Starting daemon.
Jun  2 10:50:37 David-Gues-MacBook-Pro proxy[12383]: Error opening hosts file: fopen(): No such file or directory
Jun  2 17:20:22 David-Gues-MacBook-Pro proxy[12383]: Wrong AV daemon statistics pop response code (431)!
Jun  2 17:23:33 David-Gues-MacBook-Pro proxy[12383]: Error reading receive buffer: read(): Connection reset by peer
Jun  2 17:29:34 David-Gues-MacBook-Pro proxy[12383]: Error connecting to server: connect(): Invalid argument
Jun  2 17:30:29 David-Gues-MacBook-Pro proxy[12383]: Error connecting to server: connect(): Host is down
Jun  2 17:30:29 David-Gues-MacBook-Pro proxy[12383]: Error connecting to server: connect(): Host is down
Jun  2 22:21:55 David-Gues-MacBook-Pro proxy[272]: Starting daemon.
Jun  2 22:21:56 David-Gues-MacBook-Pro proxy[272]: Error opening hosts file: fopen(): No such file or directory
Jun  2 22:25:59 David-Gues-MacBook-Pro proxy[272]: Error connecting to server: connect(): Invalid argument
Jun  2 22:26:11 David-Gues-MacBook-Pro proxy[272]: Error connecting to server: connect(): Invalid argument
Jun  2 22:26:17 David-Gues-MacBook-Pro proxy[272]: Error connecting to server: connect(): Invalid argument
Jun  2 22:27:14 David-Gues-MacBook-Pro proxy[272]: Error connecting to server: connect(): Invalid argument
Jun  2 22:27:52 David-Gues-MacBook-Pro proxy[272]: Error connecting to server: connect(): Invalid argument
Jun  2 23:09:06 David-Gues-MacBook-Pro proxy[272]: Error connecting to server: connect(): Invalid argument
Jun  2 23:09:10 David-Gues-MacBook-Pro proxy[272]: Error connecting to server: connect(): Invalid argument
Jun  2 23:09:30 David-Gues-MacBook-Pro proxy[272]: Error connecting to server: connect(): Invalid argument
Jun  2 23:10:44 David-Gues-MacBook-Pro proxy[272]: Error connecting to server: connect(): Invalid argument
Jun  2 23:12:47 David-Gues-MacBook-Pro proxy[281]: Starting daemon.
Jun  2 23:12:47 David-Gues-MacBook-Pro proxy[281]: Error opening hosts file: fopen(): No such file or directory
Jun  2 23:15:50 David-Gues-MacBook-Pro proxy[281]: Error connecting to server: connect(): Invalid argument
Jun  2 23:18:46 David-Gues-MacBook-Pro proxy[281]: Error connecting to server: connect(): Invalid argument
Jun  2 23:18:46 David-Gues-MacBook-Pro proxy[281]: Error connecting to server: connect(): Invalid argument
Jun  2 23:18:59 David-Gues-MacBook-Pro proxy[281]: Error connecting to server: connect(): Invalid argument
Jun  2 23:19:05 David-Gues-MacBook-Pro proxy[281]: Error connecting to server: connect(): Invalid argument
Jun  2 23:19:47 David-Gues-MacBook-Pro proxy[281]: Error connecting to server: connect(): Invalid argument
Jun  2 23:21:50 David-Gues-MacBook-Pro proxy[281]: SIGTERM received. Exiting.
Jun  2 23:22:51 David-Gues-MacBook-Pro proxy[735]: Starting daemon.
Jun  2 23:22:51 David-Gues-MacBook-Pro proxy[735]: Error opening hosts file: fopen(): No such file or directory
Jun  2 23:23:25 David-Gues-MacBook-Pro proxy[735]: SIGTERM received. Exiting.
Jun  2 23:23:34 David-Gues-MacBook-Pro proxy[880]: Starting daemon.
Jun  2 23:23:34 David-Gues-MacBook-Pro proxy[880]: Error opening hosts file: fopen(): No such file or directory
Jun  2 23:23:50 David-Gues-MacBook-Pro proxy[880]: SIGTERM received. Exiting.
Jun  2 23:24:04 David-Gues-MacBook-Pro proxy[1022]: Starting daemon.
Jun  2 23:24:04 David-Gues-MacBook-Pro proxy[1022]: Error opening hosts file: fopen(): No such file or directory
Jun  2 23:24:11 David-Gues-MacBook-Pro proxy[1022]: Error connecting to server: connect(): Invalid argument
Jun  2 23:24:11 David-Gues-MacBook-Pro proxy[1022]: Error connecting to server: connect(): Invalid argument
Jun  2 23:24:27 David-Gues-MacBook-Pro proxy[1022]: SIGTERM received. Exiting.
David-Gues-MacBook-Pro:~ david$

Offline tumic

  • Moderator
  • Advanced Poster
  • *
  • Posts: 724
Re: Mailshield problem
« Reply #4 on: June 03, 2011, 03:14:09 PM »
Turning off the Mailshield also turns off the web shield (and restores my email functionality). Turning off the Web Shield also turns off the Mailshield. Similarly, both shields turn "on" together.

The shield configuration logic is not yet fully implemented in the GUI so you really can only enable/disable all network shields at once from the GUI. However, you can disable/enable particular shields using the configuration file

Code: [Select]
/Library/Application Support/Avast/com.avast.proxyclient.conf
To disable a particular shield, add the following entry to the appropriate module configuration section:

Code: [Select]
ENABLED = 0

The shields must be set to ON in the GUI, otherwise the setting will have no effect. Also note, that the shield state will be shown wrong in the GUI - ON for disabled shields - if you disable it (the change does not propagate to the GUI)

Offline pastore.a

  • Newbie
  • *
  • Posts: 6
Re: Mailshield problem
« Reply #5 on: June 03, 2011, 05:53:03 PM »

The shield configuration logic is not yet fully implemented in the GUI so you really can only enable/disable all network shields at once from the GUI. However, you can disable/enable particular shields using the configuration file

Code: [Select]
/Library/Application Support/Avast/com.avast.proxyclient.conf
To disable a particular shield, add the following entry to the appropriate module configuration section:

Code: [Select]
ENABLED = 0

The shields must be set to ON in the GUI, otherwise the setting will have no effect. Also note, that the shield state will be shown wrong in the GUI - ON for disabled shields - if you disable it (the change does not propagate to the GUI)


I opened the file
Code: [Select]
/Library/Application Support/Avast/com.avast.proxyclient.conf
Then after added the
Code: [Select]
ENABLED = 0 in all mail module configuration sections, I rebooted my mac.
Everything was ok.

But... When I opened the GUI the problem came back and every
Code: [Select]
ENABLED = 0 was disappeared from the configuration file.

I didn't switched off/on the mail shield in the GUI, I only opened the GUI!

Andrew

Uli

  • Guest
Re: Mailshield problem
« Reply #6 on: June 05, 2011, 11:33:59 PM »
you can out comment the socket like

;SOCKET = "Lib...

not sure if it is the right way, but it works

Offline tumic

  • Moderator
  • Advanced Poster
  • *
  • Posts: 724
Re: Mailshield problem
« Reply #7 on: June 06, 2011, 10:16:54 AM »
But... When I opened the GUI the problem came back and every
Code: [Select]
ENABLED = 0 was disappeared from the configuration file.

Did you really put in ENABLED = 0 ?! There is a "bug" in the configuration file comments that states the keyword to be ENABLE not ENABLED. Puting in ENABLE will lead to configuration file parse error that will force a restart with a default configuration file.

Offline pastore.a

  • Newbie
  • *
  • Posts: 6
Re: Mailshield problem
« Reply #8 on: June 11, 2011, 03:42:02 PM »
Did you really put in ENABLED = 0 ?! There is a "bug" in the configuration file comments that states the keyword to be ENABLE not ENABLED. Puting in ENABLE will lead to configuration file parse error that will force a restart with a default configuration file.

Maybe you are right, now it's working correctly with ENABLED = 0  ;)

Thanks
Andrew

Offline tumic

  • Moderator
  • Advanced Poster
  • *
  • Posts: 724
Re: Mailshield problem
« Reply #9 on: June 22, 2011, 02:57:24 PM »
Please try the latest update, all the mailshield problems should be fixed there.

Offline pastore.a

  • Newbie
  • *
  • Posts: 6
Re: Mailshield problem
« Reply #10 on: June 26, 2011, 10:33:24 AM »
Please try the latest update, all the mailshield problems should be fixed there.

The problem is still there...  :'(

Andrew

Offline tumic

  • Moderator
  • Advanced Poster
  • *
  • Posts: 724
Re: Mailshield problem
« Reply #11 on: June 27, 2011, 04:54:45 PM »
Do you still get the same "invalid argument" error messages?

Code: [Select]
Jun  2 23:09:30 David-Gues-MacBook-Pro proxy[272]: Error connecting to server: connect(): Invalid argument

Offline pastore.a

  • Newbie
  • *
  • Posts: 6
Re: Mailshield problem
« Reply #12 on: June 27, 2011, 08:12:25 PM »
Jun 26 10:12:18 iMac-20 proxy[1316]: Starting daemon.
Jun 26 10:12:18 iMac-20 proxy[1316]: Error opening hosts file: fopen(): No such file or directory
Jun 26 10:12:23 iMac-20 proxy[1316]: AV daemon connection timeout!
Jun 26 10:12:54 iMac-20 proxy[1316]: Error connecting to server: connect(): Invalid argument
Jun 26 10:13:47 iMac-20 proxy[1316]: Error connecting to server: connect(): Invalid argument
Jun 26 10:14:46 iMac-20 proxy[1316]: Error connecting to server: connect(): Invalid argument
Jun 26 10:18:03 iMac-20 proxy[1316]: Error connecting to server: connect(): Invalid argument
Jun 26 10:18:16 iMac-20 proxy[1316]: Error connecting to server: connect(): Invalid argument
Jun 26 10:19:11 iMac-20 proxy[1316]: Error connecting to server: connect(): Invalid argument
Jun 26 10:20:14 iMac-20 proxy[167]: Starting daemon.
Jun 26 10:20:14 iMac-20 proxy[167]: Error opening hosts file: fopen(): No such file or directory
Jun 26 10:31:02 iMac-20 proxy[167]: Error reading receive buffer: read(): Connection reset by peer
Jun 26 10:34:12 iMac-20 proxy[167]: Error reading receive buffer: read(): Connection reset by peer
Jun 26 11:34:17 iMac-20 proxy[167]: Error reading receive buffer: read(): Connection reset by peer
Jun 26 11:34:49 iMac-20 proxy[167]: Error reading receive buffer: read(): Connection reset by peer
Jun 26 11:37:55 iMac-20 proxy[167]: Error reading receive buffer: read(): Connection reset by peer
Jun 26 11:43:41 iMac-20 proxy[167]: Error reading receive buffer: read(): Connection reset by peer
Jun 26 11:49:31 iMac-20 proxy[167]: Error connecting to server: connect(): Connection refused
Jun 26 11:49:34 iMac-20 proxy[167]: Error reading receive buffer: read(): Connection reset by peer
Jun 26 11:52:39 iMac-20 proxy[167]: Error reading receive buffer: read(): Connection reset by peer
Jun 26 12:00:06 iMac-20 proxy[167]: Error connecting to AV daemon: connect(): Connection refused
Jun 26 12:00:11 iMac-20 proxy[167]: Error connecting to server: connect(): Connection refused
Jun 26 12:12:49 iMac-20 proxy[155]: Starting daemon.
Jun 26 12:12:49 iMac-20 proxy[155]: Error opening hosts file: fopen(): No such file or directory
Jun 26 14:13:05 iMac-20 proxy[155]: Error reading receive buffer: read(): Connection reset by peer
Jun 26 14:17:13 iMac-20 proxy[155]: Error reading receive buffer: read(): Connection reset by peer
Jun 26 14:49:12 iMac-20 proxy[155]: Error reading receive buffer: read(): Connection reset by peer
Jun 26 18:56:28 iMac-20 proxy[155]: Error writing send buffer: write(): Broken pipe