Is Tommy down?

[infantex]

What I ended up doing is adding a DNS zone for infantex.com.mx (althoug it won't be used), deactivating DKIM for the domain and activating it again so that a DKIM record was created, and copied it's contents to Cloudflare. It seems to have worked.

I used mailgenius to check it. DKIM turned out to be OK, but I was surprised to learn that both my domain (infantex.com.mx) and the VPS's IP (65.19.141.197) were blacklisted! Mailgenius report: https://app.mailgenius.com/spam-test/979562

However, upon checking https://check.spamhaus.org/, neither one appears to be listed. Should I research more on this subject?

By the way, the v-list-mail-domain-dkim-dns command still gives me an error.

[herrerapoch]

I can not access to my plesk dashboard and to my website. Is there any forecast of when it could be fixed. Thank u so much

[infantex]

59 minutes ago, herrerapoch said:

I can not access to my plesk dashboard and to my website. Is there any forecast of when it could be fixed. Thank u so much

I don't think there's a forecast. Krydos is working on this issue.

 

[Kairion]

16 hours ago, infantex said:

Since my DNS is hosted by Cloudflare, there's nothing under DNS. So no mail._domainkey record to copy from.

DNS page in HestiaCP image: https://screencast-o-matic.com/i/c0nifCVxC9n

My bad. You will find your DKIM on "Mail", hover your domain and click on DNS Records, it is this icon:

Make sure no other records are missing by comparing those with the ones on your Cloudflare dashboard.

16 hours ago, infantex said:

I found (https://forum.hestiacp.com/t/solved-invalid-signature-of-dkim/3028) that when using an external DNS service, you can use the `v-list-mail-domain-dkim-dns` command to query the correct records. However, it didn't work for me. I get an error:

infantex@vps40:~$ v-list-mail-domain-dkim-dns infantx infantex.com.mx
/usr/local/hestia/func/main.sh: line 1548: /usr/local/hestia/conf/hestia.conf: Permission denied
Error: user infantx doesn't exist
/usr/local/hestia/func/main.sh: line 100: /usr/local/hestia/log/error.log: Permission denied
infantex@vps40:

I have three users in HestiaCP: admin, infantx and zaldivar. The infantex.com.mx domain belongs to the infantx user, but I get the same error no matter which user I enter. I even tried with user infantex (the user I to log into my VPS with) to no avail.

The command is right but you have to run it with administrator permissions on your VPS, so you either log in as root on your VPS (usually it's disabled by default due to security concerns) or you need to run it with sudo. It should be like that:

sudo v-list-mail-domain-dkim-dns infantx infantex.com.mx

This command is the terminal version of the web steps I mentioned above.

16 hours ago, infantex said:

I used mailgenius to check it. DKIM turned out to be OK, but I was surprised to learn that both my domain (infantex.com.mx) and the VPS's IP (65.19.141.197) were blacklisted! Mailgenius report: https://app.mailgenius.com/spam-test/979562

However, upon checking https://check.spamhaus.org/, neither one appears to be listed. Should I research more on this subject?

I wouldn't worry about that "Mail Genius". They don't even have the current blacklist's name/site address. Probably they have outdated data and are still using it instead of checking directly on the source.

I checked with MX Toolbox (https://mxtoolbox.com/emailhealth/infantex.com.mx/), and everything seems fine with your domain (it isn't in any blacklists or have any other problems).

  

16 hours ago, infantex said:

By the way, the v-list-mail-domain-dkim-dns command still gives me an error.

Let me know if running with sudo worked.

[infantex]

On 2/7/2023 at 4:00 PM, Kairion said:

Let me know if running with sudo worked.

It didn't work.

infantex@vps40:~$ sudo v-list-mail-domain-dkim-dns infantx infantex.com.mx
[sudo] password for infantex: 
sudo: v-list-mail-domain-dkim-dns: command not found

 

[Kairion]

22 hours ago, infantex said:

It didn't work.

infantex@vps40:~$ sudo v-list-mail-domain-dkim-dns infantx infantex.com.mx
[sudo] password for infantex: 
sudo: v-list-mail-domain-dkim-dns: command not found

It looks like your HestiaCP bin directory isn't in your secure_path variable. You need to edit the /etc/sudoers file and add this path to it (can break your sudo command if you make any mistakes, so proceed with caution):

/usr/local/hestia/bin

Alternatively, you can simply run the following command:

sudo /usr/local/hestia/bin/v-list-mail-domain-dkim-dns infantx infantex.com.mx

In this way, sudo will know where to find HestiaCP's command v-list-mail-domain-dkim-dns to run it with root permissions.

 

Let me know if that works.

[infantex]

8 hours ago, Kairion said:

Alternatively, you can simply run the following command:

sudo /usr/local/hestia/bin/v-list-mail-domain-dkim-dns infantx infantex.com.mx

This time, it worked.

However, I had already solved the problem adding a DNS zone for infantex.com.mx and copying the DKIM record from there. As I mentioned in a previous post:

I don't know whether I would have gotten the necessary records if I had run that command before creating (?) the records the way I did.

Also, I could never get the mail and webmail.infantex.com.mx addresses to work.

Anyways, I'm now back on Tommy.

Regards,

[Kairion]

On 2/10/2023 at 5:34 AM, infantex said:

I don't know whether I would have gotten the necessary records if I had run that command before creating (?) the records the way I did.

Also, I could never get the mail and webmail.infantex.com.mx addresses to work.

Unfortunately, mail hosting without having HestiaCP managing your domain DNS records demands some additional settings like I mentioned:

On 2/6/2023 at 2:15 PM, Kairion said:

Per HestiaCP default, your webmail should be accessible from the address webmail.infantex.com.mx, but you need to make sure your DNS hosting has an A record (named webmail) pointing towards your VPS' IP address (the same with MAIL, IMAP, SMTP, and POP)

 

HestiaCP could be more intuitive and user-friendly to show which records were needed to get everything working but as far as I could see on their forum they aren't exactly aiming to achieve that.

Anyway, I'm glad you're back on Tommy and everything is working now.