Search results

I will try to set it higher and see what it does, but it should be just unlimited when set to 0. Thank you,.

I have to "up" this as it is still happening. For some reason it's not fixed by nightly tallys. Seems a bug to me. Is there any way to maybe reset this counter? @zEitEr any clue?

Yes, that is what I described:

Yep, got the mail about that already 2 times.;) Being member helped me to get help twice fairly quick when my server was blocked, but it was in fact not my server but a netblock. And since I had not been on their blacklist for a long time probably our server was mitigated and we could mail...

Be aware, if you are a hosting customer, you're on the wrong place too. This forum is only intended for Directadmin license holders, not hosting customers. So if you are not a license holder or reseller, you should contact your host for support.

Yes but in fact the second mailserver will be a smarthost for the ISP mailserver which is eventually really sending the mail outside to the internet, making it's own SPF/DKIM records. Which is causing the issue.

Ah oke sorry, then I misunderstood. I though you ment on premises but with another domain name. What you in fact want is a kind of a double smarthost. I have no clue on how this should work. You might be able to solve the issue by not using a DKIM on your own server, but only using SPF, and...

I think so. Theoretically, if you use DA as smarthost to the Exchange server then it will also send mail generated locally to the Exchange server. It's up to the Exchange server on how to handle these mails. As for receiving mails, it's a question of putting the MX record to the ip of the...

Check this one: https://forum.directadmin.com/threads/changing-default-e-mail-from-address.62363/ that should do the trick normally.

Compare with Windows XP then or other software out there. The lifetime licenses are declared legacy. As you know in software world, it's quite comon to declare lifetime software end of life too (there are examples out there). So be glad it's just legacy, they can still be used and -even- are...

We're using Enhanced skin still for a various customers. Since I get postmaster mail. I got mail from the mailor-daemon of mail which got returned because of "quata full" of a customer. LMTP error after end of data: 552 5.2.2 <[email protected]> Quota exceeded (mailbox for user is full) So Iogged...

If his DA is disabled, there is even risk he's using an illegal version of Directadmin. Then it's easy to put the fault with DA if it's closed down, because he would never admit having a wrongfull license. So that's also an option. He should be able to make backups for you via SSH. I would...

There you got your answer. The hosting provider buys or rents the panel from Directadmin. The issue needs to be solved by the license holder. So that is the hosting provider.

Phoe that's 3 years ago, I probably was talking about the mysql backup timeout. Check this please: https://docs.directadmin.com/directadmin/backup-restore-migration/backups.html#mysqldump-timeout

That's normal. I also have these in the logs, as long as mail is send and receive correctly, it should be no issue. Got them even from a big ISP in the Netherlands. SSL verify error: certificate name mismatch: DN="/CN=spamfilter05.delta.nl" H="mx1.zeelandnet.nl" Nothing to worry about.

Exactly how did you do this? I hope you set it as: port=4060 under the [mysqld] part, right? The 4060 is just an example number, it should read the portnumber you want to use there. Did you also restarted mysql/mariadb afterwards? Be aware that you also have to change that port number in the...

First ipv6, then ipv4 as expected. You mean like this? dig -6 53.176.230.91.bl.spamcop.net txt ; <<>> DiG 9.16.23-RH <<>> -6 53.176.230.91.bl.spamcop.net txt ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 19323 ;; flags: qr rd ra; QUERY: 1, ANSWER...

So the dkim selector is hardcoded for the whole server not for 1 domain, which means one can create multiple DKIM keys, but over the whole server the same DKIM selector is to be used. In that case it's a bug and on a restore the DKIM selector choosen in directadmin.conf should be applied on...

Strange. Maybe RHEL 10 then indeed. I'm running Alma 9 and no issues with this. But also on Alma 9 when sending mail, ipv6 is preferred.

Well then this is a bug, because a DKIM record should work no matter what the dkim_selector in the directadmin.conf says. Because if it restores the dkim selector then it will also restore the DKIM key. The dkim_selector setting in directadmin.conf is only for newly created DKIM keys. So if DA...