DirectAdmin 1.703

can we open a thread for the (sorry for my bluntness) enshittification in the ssl manager?

i need to replace a CA cert bundle.

before this was;
- open ca field,
- paste new,
- save.

Now it is:
- view,
- copy/download the certicite bundle as it is now,
- copy individual parts in an external ssl certificate decoder to see which part is the ssl to keep,
- create new bundle,
- use replace to upload new.

also what appears to be a false detection of invalid cert; The provided TLS certificate is invalid: x509: certificate signed by unknown authority
while pasting official CA certificates as downloaded from the Cert provider.
but since we now need to paste all parts at once, no clear indication of which part is the problem.

This change is REALLY not helpful at all.
 
Hello,

I wanted to flag an issue introduced by recent exim.conf updates regarding how default system mailboxes are routed.

If a server's parent domain uses external DNS/MX records (or has a wildcard MX record like * IN MX pointing externally), Exim's lookuphost router completely hijacks local system mail.

The Problem:

  1. A default user mailbox receives mail (e.g., [email protected]).
  2. DirectAdmin's aliases file expands this to the bare system username (user), which Exim qualifies into [email protected].
  3. Because lookuphost is at the top of the router stack and relies on a public DNS lookup, it sees the external MX records for the hostname and tries to deliver the mail over the internet via remote_smtp_forward_transport.
  4. The external mail server rejects it with a 550 Mailbox unavailable bounce.
Even if the hostname is explicitly listed in /etc/virtual/domains and /etc/virtual/domainowners, Exim bypasses it because lookuphost matches the external IP routing first.

The Workaround:I had to manually implement a pre-router interceptor in /etc/exim.routers.pre.conf to force local delivery for the primary hostname:

Code:
hostname_local_interceptor:

 driver = accept 

 domains = server.hostname.com 

 check_local_user 

 transport = local_delivery

Could the default exim.conf template be updated so that primary_hostname is explicitly protected or matched as local before lookuphost handles public DNS queries?
 
Back
Top