What the hell does this mean? For me, it meant: Eclipse 64bit and Java 32bit installed.
I solved this by downloading and installing the 64bit java version instead.
Hope this helps somebody 😉
30. July 2015
Recommendation
Try my Open Source PHP visitor analytics script CrazyStat.14. July 2015
Ubuntu Gnome 15.04: Hide Hidden files in Nautilus
To hide hidden files and folders in Nautilus in Ubuntu Gnome 15.05, type this in a terminal:
gsettings set org.gtk.Settings.FileChooser show-hidden false
If you want to see hidden files from time to time, press CTRL + H in a nautilus window.
Ubuntu Gnome: Sort folders first in Nautilus
If you prefer to have the folders at the beginning in Nautilus, just type this command in a terminal:
gsettings set org.gnome.nautilus.preferences sort-directories-first true
Works in Ubuntu Gnome 15.04
Ubuntu Gnome: Find file starting with the letter you type in Nautilus
New nautilus versions start searching for what you start typing inside a folder. If you instead prefer to jump to the files starting with what you type, just like Windows Explorer behaves, type this in a terminal:
gsettings set org.gnome.nautilus.preferences enable-interactive-search true
Works on Ubuntu Gnome 15.04
4. July 2015
phpLiteAdmin is now hosted on bitbucket
As Google code is shutting down, the open source project phpLiteAdmin which was hosted on google code all the time needed a new home. The team decided to use bitbucket. There were several reasons why we did not go for the most obvious one – github. Mainly, github does not offer some features we need.
I moved all the issues from the issue tracker to bitbucket and also imported the wiki pages and converted them into markdown syntax so everything is nice again. Downloads are also hosted on bitbucket now.
The git source repository is available on bitbucket as well as github. So if you want to fork phpLiteAdmin and send us pull requests, you can do so on any of the two plattforms.
This is phpLiteAdmin’s new home: https://bitbucket.org/phpliteadmin/public
And don’t tell us, you don’t want to create a bitbucket account – you don’t need to! You can log into bitbucket with your existing google, facebook, twitter or even github account!
The discussion group is still a google group.
23. June 2015
Bind9 on Debian Wheezy: journal rollforward failed: journal out of sync with zone
Getting this error when restarting bind9?
journal rollforward failed: journal out of sync with zone
You probably changed the zonefile while bind was running without freezing it.
To fix this, first stop bind:
service bind9 stop
Then remove the journal file for the zone. On Debian Wheezy, it is in the same folder as the zone:
rm /etc/bind/zones/example.com.jnl
Then start bind again:
service bind9 start
To avoid the problem next time, before changing a zonefile, freeze the zone:
rndc freeze example.com
Then edit your zonefile and finally thaw it:
rndc thaw example.com
5. June 2015
Zimbra: Redirect http to https
Zimbra without Proxy (pre 8.5)
That’s the easy way how you can enforce https encrpytion by redirecting http to https:
su – zimbra zmtlsctl redirect zmcontrol stop zmcontrol start
Works at least on Zimbra 8.0 and I think should also work on 7
Zimbra with Proxy (required from 8.5+)
With Zimbra 8.5+, a Proxy is required. This makes the configuration a little different. To configure the proxy to redirect http to https, run:
su zimbra ~/libexec/zmproxyconfig -e -w -o -a 8080:80:8443:443 -x both -H `zmhostname` # if your proxy is local: zmprov ms `zmhostname` zimbraReverseProxyMailMode redirect # if your proxy is proxy.server.name zmprov ms proxy.server.name zimbraReverseProxyMailMode redirect zmcontrol restart
With the latest Zimbra versions, the restart is not even necessary, it automatically detects the change within 2 minutes.
Hope this helps somebody!
2. June 2015
Zimbra: Using zmpostfixpolicyd to stop backscatter
Your Zimbra is backscattering? This is what may help you:
Update 2018-08-21:
Before doing anything else, make sure you don’t have a CatchAll defined for your domain. To do so:
su - zimbra zmprov gd example.com | grep zimbraMailCatchAllAddress # should be empty. NOT @example.com zmprov gd example.com | grep zimbraMailCatchAllForwardingAddress # should be empty. NOT @example.com zmprov gd example.com | grep zimbraMailTransport # should be lmtp:zimbra.example.com:7025 . NOT e.g. smtp:relayhost.com:587
If any of this is not as should be, then change it:
zmprov md domain.com zimbraMailCatchAllAddress "" zmprov md domain.com zimbraMailCatchAllForwardingAddress "" zmprov md domain.com zimbraMailTransport lmtp:zimbra.example.com:7025
Note that in the last line, you need to give the FQDN of your Zimbra server, instead of zimbra.example.com.
You may also read the Zimbra wiki about catchalls.
Original article:
A Zimbra 8.0 Server (on Ubuntu) was backscattering. Unfortunately Zimbra servers cannot use the postfix setting
smtpd_reject_unlisted_sender=yes
when an alias domain is setup. Everybody says it is easy, just install the policyd as a recipient_restriction and that’s it. All you need to do is:
su - zimbra zmlocalconfig -e postfix_enable_smtpd_policyd=yes zmprov mcf +zimbraMtaRestriction "check_policy_service unix:private/policy" zmmtactl stop zmmtactl start
Unfortunately, this did not work for me with Zimbra 8.0. The server was still backscattering.
First, I enabled verbose output for the policyd. To do so, open /opt/zimbra/postfix/conf/master.cf.in (the .in is important) in a texteditor and search for this part:
%%uncomment LOCAL:postfix_enable_smtpd_policyd%%policy unix - n n - - spawn %%uncomment LOCAL:postfix_enable_smtpd_policyd%% user=zimbra argv=/usr/bin/perl /opt/zimbra/libexec/zmpostfixpolicyd
Add a -v ad the end of the command:
%%uncomment LOCAL:postfix_enable_smtpd_policyd%%policy unix - n n - - spawn %%uncomment LOCAL:postfix_enable_smtpd_policyd%% user=zimbra argv=/usr/bin/perl /opt/zimbra/libexec/zmpostfixpolicyd -v
Then (as zimbra user), recreate the master.cf and restart postfix with these commands:
zmmtactl stop zmmtactl start
Now when a mail is received (from an external sender), you will see output like this in your mail log (on Debian/Ubuntu: /var/log/mail.log):
/opt/zimbra/libexec/zmpostfixpolicyd[29326]: Attribute: ccert_fingerprint= /opt/zimbra/libexec/zmpostfixpolicyd[29326]: Attribute: sasl_method= /opt/zimbra/libexec/zmpostfixpolicyd[29326]: Attribute: sasl_sender= /opt/zimbra/libexec/zmpostfixpolicyd[29326]: Attribute: size=3428 /opt/zimbra/libexec/zmpostfixpolicyd[29326]: Attribute: helo_name=[...] /opt/zimbra/libexec/zmpostfixpolicyd[29326]: Attribute: reverse_client_name=[...] /opt/zimbra/libexec/zmpostfixpolicyd[29326]: Attribute: queue_id= /opt/zimbra/libexec/zmpostfixpolicyd[29326]: Attribute: encryption_cipher=AECDH-AES256-SHA /opt/zimbra/libexec/zmpostfixpolicyd[29326]: Attribute: encryption_protocol=TLSv1.2 /opt/zimbra/libexec/zmpostfixpolicyd[29326]: Attribute: etrn_domain= /opt/zimbra/libexec/zmpostfixpolicyd[29326]: Attribute: ccert_subject= /opt/zimbra/libexec/zmpostfixpolicyd[29326]: Attribute: request=smtpd_access_policy /opt/zimbra/libexec/zmpostfixpolicyd[29326]: Attribute: protocol_state=RCPT /opt/zimbra/libexec/zmpostfixpolicyd[29326]: Attribute: stress= /opt/zimbra/libexec/zmpostfixpolicyd[29326]: Attribute: recipient=does-not-exist@example.com /opt/zimbra/libexec/zmpostfixpolicyd[29326]: Attribute: sasl_username= /opt/zimbra/libexec/zmpostfixpolicyd[29326]: Attribute: ccert_pubkey_fingerprint= /opt/zimbra/libexec/zmpostfixpolicyd[29326]: Attribute: instance=7289.556db23f.b6b7d.0 /opt/zimbra/libexec/zmpostfixpolicyd[29326]: Attribute: protocol_name=ESMTP /opt/zimbra/libexec/zmpostfixpolicyd[29326]: Attribute: encryption_keysize=256 /opt/zimbra/libexec/zmpostfixpolicyd[29326]: Attribute: recipient_count=0 /opt/zimbra/libexec/zmpostfixpolicyd[29326]: Attribute: ccert_issuer= /opt/zimbra/libexec/zmpostfixpolicyd[29326]: Attribute: sender=[...] /opt/zimbra/libexec/zmpostfixpolicyd[29326]: Attribute: client_name=[...] /opt/zimbra/libexec/zmpostfixpolicyd[29326]: Attribute: client_address=[...] /opt/zimbra/libexec/zmpostfixpolicyd[29326]: Recipient Domain: example.com /opt/zimbra/libexec/zmpostfixpolicyd[29326]: Recipient userid: does-not-exist /opt/zimbra/libexec/zmpostfixpolicyd[29326]: Action: dunno
If you see these logs, then zmpostfixpolicyd is set up correctly in postfix. If you don’t, check the postfix configuration.
But the policy daemon always returned “dunno”, even if the recipient did not exist. Therefore, I looked into the perl code of the policy daemon (/opt/zimbra/libexec/zmpostfixpolicyd):
The original code includes this part:
if (lc(($ldap->get_values("zimbraDomainType"))[0]) eq "alias") {
my $robject = ($ldap->get_values("zimbraMailCatchAllForwardingAddress"))[0];
syslog $syslog_priority, "Real Domain: %s", $robject if $verbose;
@attrs=('1.1');
$mesg = $ldap->search_s(
"",
LDAP_SCOPE_SUBTREE,
"(&(|(zimbraMailDeliveryAddress=$user"."$robject)(zimbraMailDeliveryAddress=$daddr)(zimbraMailAlias=$user".
"$robject)(zimbraMailAlias=$daddr)(zimbraMailCatchAllAddress=$user"."$robject)(zimbraMailCatchAllAddress=$robject)".
"(zimbraMailCatchAllAddress=$daddr))(zimbraMailStatus=enabled))",
\@attrs,
0,
$result
);
$ent = $ldap->first_entry();
$ldap->unbind;
if ($ent != 0) {
return "dunno";
} else {
return "reject 5.1.1 Mailbox unavailable";
}
} else {
     $ldap->unbind;
     return "dunno";
   }
So basically, this code only rejects mail to recipients for alias-domains, but accepts all mail to domains that are not alias-domains. I adjusted the code as follows:
if (lc(($ldap->get_values("zimbraDomainType"))[0]) eq "alias") {
my $robject = ($ldap->get_values("zimbraMailCatchAllForwardingAddress"))[0];
syslog $syslog_priority, "Real Domain: %s", $robject if $verbose;
@attrs=('1.1');
$mesg = $ldap->search_s(
"",
LDAP_SCOPE_SUBTREE,
"(&(|(zimbraMailDeliveryAddress=$user"."$robject)(zimbraMailDeliveryAddress=$daddr)(zimbraMailAlias=$user".
"$robject)(zimbraMailAlias=$daddr)(zimbraMailCatchAllAddress=$user"."$robject)(zimbraMailCatchAllAddress=$robject)".
"(zimbraMailCatchAllAddress=$daddr))(zimbraMailStatus=enabled))",
\@attrs,
0,
$result
);
$ent = $ldap->first_entry();
$ldap->unbind;
if ($ent != 0) {
syslog $syslog_priority, "Existing Alias-Recipient";
return "dunno";
} else {
syslog $syslog_priority, "Non-Existing Alias-Recipient";
return "reject 5.1.1 Mailbox unavailable";
}
} else {
@attrs=('1.1');
$mesg = $ldap->search_s(
"",
LDAP_SCOPE_SUBTREE,
"(&(|(zimbraMailDeliveryAddress=$user"."$domain)(zimbraMailDeliveryAddress=$daddr)(zimbraMailAlias=$user".
"$domain)(zimbraMailAlias=$daddr)(zimbraMailCatchAllAddress=$user"."$domain)(zimbraMailCatchAllAddress=$domain)".
"(zimbraMailCatchAllAddress=$daddr))(zimbraMailStatus=enabled))",
\@attrs,
0,
$result
);
$ent = $ldap->first_entry();
$ldap->unbind;
if ($ent != 0) {
syslog $syslog_priority, "Existing Recipient";
return "dunno";
} else {
syslog $syslog_priority, "Non-Existing Recipient";
return "reject 5.1.1 Mailbox unavailable";
}
}
Then I restarted postfix as a zimbra user with:
zmmtactl stop zmmtactl start
And finally, the policy daemon rejected mails to unexisting recipients 🙂
/opt/zimbra/libexec/zmpostfixpolicyd[5799]: Recipient Domain: example.com /opt/zimbra/libexec/zmpostfixpolicyd[5799]: Recipient userid: does-not-exist /opt/zimbra/libexec/zmpostfixpolicyd[5799]: Non-Existing Recipient /opt/zimbra/libexec/zmpostfixpolicyd[5799]: Action: reject 5.1.1 Mailbox unavailable postfix/smtpd[5791]: NOQUEUE: reject: RCPT from [...]: 554 5.1.1 <does-not-exist@example.com>: Recipient address rejected: Mailbox unavailable; [...]
Please use the described solution with care. It is my workaround, it is working on the system in question. It might not work with another setup. If you use it, test thoroughly if only the correct mails get rejected.
A Zimbra update will overwrite the zmpostfixpolicyd code and thus revert the change, so you might need to readjust the code after an update.
This drove me nuts and I hope this information is of help for somebody. Please comment if you have a better solution or find the described solution useful.
21. May 2015
wp-cli: syntax error, unexpected ‘?’, error connecting to the database
Running wp-cli on a website that was set up by somebody else resulted in a strange error:
PHP Parse error: syntax error, unexpected '?' in phar:///usr/local/wp-cli.phar/php/wp-cli.php(23) : eval()'d code on line 1 Error: <h1>Fehler beim Aufbau der Datenbank-Verbindung</h1> ...
The database settings in wp-config.php were all correct and WordPress was also working, so this did not seem to be the problem. In the end, I found out the reason was a byte order mark at the beginning of wp-config.php that had been inserted probably by Windows Editor. To solve the issue, the easiest way is to open the file in a good editor, for Windows I recommend PSPad, copy everything into the clipboard (CTRL +A, CTRL + C), create a new empty file (CTRL + N), paste everything (CTRL + V), save it (CTRL + S) as wp-config.php and upload the file.