Two Drifters

In Zimbra Release 6.0.6_GA_2324.DEBIAN5_64 UBUNTU8_64 FOSS edition I had the problem, that a zmcontrol status would always show the service stats as stopped, no matter how often you would stop and start all services. After reading a bit on the Zimbra forums, I managed to fix that.

Do (as root):

chown -R zimbra:zimbra /opt/zimbra/zmstat

/opt/zimbra/bin/zmsyslogsetup

These are the two commands you need to run. After that, su zimbra to become the user zimbra and zmcontrol stop and zmcontrol start your server. Voilá, zmcontrol status should now show the stats as running.

Apparently the problem is, that some directories stats tries to access are set up incorrectly with the owner root instead of Zimbra. The error is reported to randomly occur again, so you may need to repeat the chown part.

Also see these websites for further details:

• http://wiki.zimbra.com/wiki/Logger_(ZCS_6.0.x_and_later)
• http://bugzilla.zimbra.com/show_bug.cgi?id=45010

In general, you should follow this guide. Use this article for some extra information.

/usr/sbin/postgrey

my $VERSION = '1.33';
my $DEFAULT_DBDIR = '/var/spool/postfix/postgrey';
my $CONFIG_DIR = '/etc/postfix';

(…)

whitelist_clients_files => $opt{'whitelist-clients'} ||
[ "$CONFIG_DIR/postgrey_whitelist_clients" ,
"$CONFIG_DIR/postgrey_whitelist_clients.local" ],
whitelist_recipients_files => $opt{'whitelist-recipients'} ||
[ "$CONFIG_DIR/postgrey_whitelist_recipients" ],

/etc/default/postgrey

POSTGREY_OPTS="–inet=127.0.0.1:60000"

Postgrey has to be installed, sometimes you have to do it manually. (It's a Perl script, which you can get here: http://postgrey.schweikert.ch/
The excerpt above should help you to set up and locate the proper locations of the files. There is an init.d script for Debian, which I am using.

You might want to get the postgrey package from Debian and try to understand the installation process from it, if you're stuck in a similar situation.

The command which the Debian install script uses to set up the run levels:

update-rc.d postgrey defaults 19 >/dev/null

To start postgrey use:

/etc/init.d/postgrey start

And then as user zimbra:

postfix reload

Postgrey is now set up on your system.

Obwohl Outlook Express bereits auf die maximale Wartezeit eingestellt ist, kommt es trotzdem bei manchen zu Timeout-Problomen.

(Original-Text auf italienisch: "il server ha interrotto la connessione in modo inatteso. …" = "Your server has unexpectedly terminated the connection. Possible causes for this include server problems, network problems, or a long period of inactivity. Account: 'account name', Server:'server', Protocol: POP3, Port 110, Secure (SSL); No, Error Number: 0x800CCC0F"

Eine Recherche bringt folgende Möglichkeiten zustande:

• Outlook Express hat einen Bug, was bei bestimmten e-Mails (mit leerer Message-ID) zu Timeouts führt bzw. dazu, dass eine Mail immer und immer wieder geholt wird. Siehe dazu diesen Artikel.
• Norton AntiVirus scannt einkommende UND abgehende Mails. Norton's Support schlägt vor, den Scan abzuschalten um das Problem zu lösen.
  Hier ist ein weiterer Artikel mit Überblick über Norton, McAffee, Trend-Micro.
• Falls wir einen Exchange Server betreiben würden, hätte Microsoft auch einen Lösungsvorschlag.
• Manchmal ist bei Outlook Express eingestellt, dass es die Internetverbindung automatisch trennen soll. Bell hat dazu eine Seite (auf Englisch).