Posts by f4Nm1Z9k2P
-
-
Piwik ist auch deswegen so mächtig, weil es nicht die Logdateien analysiert sondern normalerweise als Javascript im Browser ausgeführt wird. Deswegen bekommt man u.a. auch mit, auf welche externen Links ein Seitenbesucher so klickt und per Cookie wird bestimmt, welcher Besucher schon mal da war. Dafür fehlen natürlich alle direkten Aufrufe von Dateien in den Statistiken.
Dafür habe ich unter einer Domain Piwik eingerichtet und in alle anderen Seiten habe ich den Code manuell oder per Plugin (Wordpress) eingefügt.
Also das was du willst würde zwar gehen, dafür ist Piwik aber eigentlich nicht wirklich gebaut worden.
-
The wiki also says that your FQHN must resolve the server's IP address. That's what you do when editing /etc/hosts because it is queried before your DNS Resolver.
IMHO the current wiki instrucions seem to be a little misleading. A paragraph that tells how to edit /etc/hosts should be added.
-
-
Try this:
hostname -fYour Hostname should probably be sv01. Change your /etc/hosts according to the following man entry:
Display MoreCode- THE FQDN
- The FQDN (Fully Qualified Domain Name) of the system is the name that the
- resolver(3) returns for the host name, such as, ursula.example.com. It is
- usually the hostname followed by the DNS domain name (the part after the first
- dot). You can check the FQDN using hostname --fqdn or the domain name using
- dnsdomainname.
- You cannot change the FQDN with hostname or dnsdomainname.
- The recommended method of setting the FQDN is to make the hostname be an alias
- for the fully qualified name using /etc/hosts, DNS, or NIS. For example, if
- the hostname was "ursula", one might have a line in /etc/hosts which reads
- 127.0.1.1 ursula.example.com ursula
- Technically: The FQDN is the name getaddrinfo(3) returns for the host name
- returned by gethostname(2). The DNS domain name is the part after the first
- dot.
- Therefore it depends on the configuration of the resolver (usually in
- /etc/host.conf) how you can change it. Usually the hosts file is parsed before
- DNS or NIS, so it is most common to change the FQDN in /etc/hosts.
-
So for me this looks normal. During looking through the files I remembered something which might be the reason. I have added a secondary mx-entry for my domains named "mx30" so there are two mx-entries - the original "mail" and my "mx30". Could that be the reason?
For opendkim, "mail" is a selector that has nothing to with the MX host. As you can have different keys for DKIM it just selects which to use. As I see, opendkim seems to be configured correctly.
Try this: netstat -tulpen | grep opendkim
-
Then it's definitely OpenDKIM. Let's take a look at the following files:
- /etc/opendkim.conf
- /etc/opendkim/SigningTable (should contain entries looking like this: mail._domainkey.DOMAIN.TLD DOMAIN.TLD:mail:/etc/opendkim/keys/DOMAIN.TLD/mail.private)
- /etc/opendkim/KeyTable (should contain entries looking like this: mail._domainkey.DOMAIN.tld DOMAIN.TLD:mail:/etc/opendkim/keys/DOMAIN.TLD/mail.private)
- /etc/opendkim/keys should contain the files mentioned in SigningTable and KeyTable
edit: And also check if opendkim is started.
-
non_smtpd_milters = inet:localhost:12345
smtpd_milters = inet:localhost:12345Is there any difference if you clear these Settings?
-
Your TLS settings can be tested using the Qualys SSLLabs SSL Server Test.If you want to change your settings, edit /etc/apache2/mods-available/ssl.conf. Mozilla has some good recommendations.
-
Yeah, but all this is about customer's lazyness (or stupidity)...
You're totally right, but we are talking about customers that usually aren't tech-savvy. People tend to make bad decisions, so software should become "Secure by Default" and force the user to do the right decision.
