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).
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$
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
To disable a particular shield, add the following entry to the appropriate module configuration section:
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)
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.