DirectAdmin 1.680

Thanks.
Can you enlighten this one a bit for me as I'm not native English and I'm not sure what is ment by "mail address" here:
Any forwarder email address can be used as a sender address if the forwarding rule is configured to deliver emails to the main address.
Click to expand...
1.) So I have 2 forwarder emails.
One mail going to my ticket system is automatically also forwarded to my normal contact mail address. This keeps working I presume?

2.) Other situation. A customer has [email protected] and has his mail automatically forwarded to [email protected] for example.
Microsoft is often messing with from adresses, but it can also be gmail and this is a forward which is not going to the "main address".

It's not clear to me what happens in these 2 situations or what exactly changes with forwarders, would be nice to have an example for us non-English users.
 
I have a little question about Exim.
Is this still work if the user is owner of the domain, but can set any sender name, "{any_sproof}@user_domain" ?
 
To address lingering questions with additional Exim ACL:
  • User can always send email from address that was used for authentication.
Example: user authenticated as "[email protected]" can send emails from "[email protected]" address.

  • Domain part can be an alias domain that points to the main domain.
Example: if alias domain "alias.example.com" points to "example.com", user authenticated as "[email protected]" can send emails either from "[email protected]" or "[email protected]"

  • Local part can be a forwarder address from the main domain if it forwards to his authenticated email address.
Example: if "[email protected]" is forwarded to "[email protected]", user authenticated as "[email protected]" can send emails either from "[email protected]" or "[email protected]"

  • If catch-all points to his authenticated email address he can send from any local part within the same domain.
Example: if Catch All E-mail forwards mail to "[email protected]", user authenticated as "[email protected]" can send emails from "{anything}@example.com"
 
While this setting can be disabled - which is probably what I will do - it just seems that this "feature" is overstepping the boundaries of SMTP.

In principle I can see where this is beneficial, but it really needs to be part of SMTP and not something that DirectAdmin takes upon itself to implement. I can see this causing a lot of issues for users who have been implementing their own sending policies with a single SMTP Authentication user.

That's just my opinion. But at least this can be disabled.
 
After server update from directadmin including soft i get the following error

Misdirected Request​

The client needs a new connection for this request as the requested host name does not match the Server Name Indication (SNI) in use for this connection.
 

Attachments

  • Scherm­afbeelding 2025-07-18 om 21.34.12.png
    Scherm­afbeelding 2025-07-18 om 21.34.12.png
    21.3 KB · Views: 5
You must log in or register to reply here.
Back
Top