DirectAdmin 1.676

[wila]

Bumped into an issue where a customer reported that one of their subdomains now returned a 404 error instead of the expected application.

The issue turned out to be a wrong pointer under the subdomains setup of their account.

For domain test.example.com it looked like this:
/domains/example.com/public_html/test
whereas it should have been:
/domains/example.com/private_html/test

The public_html folder exists, but only has a single index.html instead of the full application.

Fixing the mapping resolved the issue.
So not a big issue, but figured to report it.
--
Wil

 

[Rolf B]

@wila The default Exim configuration does not log the incoming TCP port. Logging of incoming connection details can be enabled by customizing the /etc/exim.conf file and appending +incoming_interface to the log_selector field:

...
log_selector = \
  +incoming_interface \
...

In main Exim log file /var/log/exim/mainlog the log lines will have I={ip}:{port} section, authenticated connections will have P=esmtpa or P=esmtpsa (if encryption is used). Quick grep over the logs that used 25 port (with or without encryption) would be:

Since we should not modify the config file directly, how is this solved via the custom include file (/etc/exim.variables.conf.custom - there are several lines)?

Does an entry work in this form?:

log_selector = \
+incoming_interface \
+delivery_size \
+sender_on_delivery \
+received_recipients \
+received_sender \
+smtp_confirmation \
+subject \
+smtp_incomplete_transaction \
-dnslist_defer \
-host_lookup_failed \
-queue_run \
-rejected_header \
-retry_defer \
-skip_delivery \
+arguments

what happens if the DA default configuration (for log_selector) is adjusted?

With cpanel the port is written to the logfile by default, I think that would also make sense here.

 

[Ohm J]

@Rolf B
All software logs scanner for Brute force Protection could go wrong, like csf firewall, BFM from Directadmin.

 

[kristian]

The example in @kristian's post could be slightly improved by hardening the socket permissions to be 0660 and making the socket file accessible to the mail group.

Indeed. I have edited my post above with this hardening.