Search results

Exactly the reason I have a password on mine. If they get stolen it might be able to compromise servers. If they now get stolen, they still have to find out the password, which is by the way also not the easiest one. ;)

No you have a different problem. This here is an rDNS/PTR issue because that error is thrown and it's on outgoing mail. You might have an exim issue on incoming mail, it's different and not rDNS/PTR related otherwise you would have seen that error too.

If you created that in Directadmin it won't be seen as a valid PTR record because PTR records need to be set with the ip owner. You need to set that PTR record where you cat the ip address from, mostly your datacenter.

Yep I don't mind, but whatever the solution is, either more personal or more diradmin@hostname, it should be fixed decently. ;)

First of all, thank you for adding the CSF/LFD change to the DA version changelog. It's about LF_INTEGRITY and PT_LIMIT. This sounds a little bit confusing to me: So first line. Configuration in existing servers will be updated with this Directadmin update. Am I correct in the assumption that...

Agreed but it should easy to provide the local to external mail for resellers. Which is probably the reason initially in the past the usage of the contact e-mail address was programmed in there. At the early days that didn't matter. Now it does matter and resellers are used to have this working...

I had the wrong line, but that it has no difference to the solution was not my intend to write it. As sais, this is the reason for my writing that line. Easier/shorter and prevents typo's.

and Normally no need to replace, just use /usr/local/directadmin/scripts/letsencrypt.sh server_cert which is the correct command according to the docs and the script will autodetect the correct hostname which is provided to DA. Will prevent typo's too. grep -Fvx "$(da config-get servername)"...

I didn't mean an external account. But if my reseller account is on the server like [email protected] then I'm normally able to send messages to my customer from that mail address. So in these kind of years, things change but also technologies change and it should be possible (just like with...

Yes why not? Alma 9 will only be EOL in 2032 so time enough to run with it.

Well I disagree a bit here. Because if a reseller, let's say me, creates a new user account, it would be nice if this user will get this mail from my contact e-mail adres and not from diradmin@hostname because that might be confusing to some users. I wonder how CP is doing that, can't remember.

Do I understand correctly that it will replace the [email protected] with diradmin@hostname or am I mistaken? But if this is the case, won't there be an issue anymore on the receiving part like Gmail due to the fact that maybe SPF, DKIM and DMARC of resellerdomain is used? Or will that...

Yes it causes also other issues like this one. It needs to be adressed by DA.

Not exim. But I'm not sure if restarting Dovecot would be enough. You might need to build dovecot and dovecot config, can't harm doing it to be sure.

Did you use the same MySQL or MariaDB database versions on both servers?

Any clue on how?

It's not a problem. DA has always helped us with this in the past, but since a couple of years ago no new licenses keys are made anymore. However in the meantime we already moved servers twice this way, it's not really a fuzz, one just has to keep this in mind. We normally always first take all...

You can forget about that. You can not downgrade licenses. You can use either modern or lifetime. You can go from lifetime to modern (montly) but you can not go from montly to lifetime. So if you want to move, you have to install the new server with the lifetime license (yes that can be done...

I'm even sure of it. But remember we are all people so everybody can make mistakes. This is a bigger one indeed. @zEitEr who of the team is writing the docs these days, do you know? Could you contact them and have this fixed please?

That's very well possible. As said the setting you made in the directadmin.conf does not exist zo you can remove it. There is another setting in the custombuild configuration which is ssl_configuration=intermediate which can be set to old...