wolstech

Try it now.

I've removed the offending forwarder from your account and re-enabled mail service again, now waiting for it to unsuspend...

It immediately resuspended you. Argh. Let me try again...

It should work again in a few minutes. Tommy is being slow unsuspending you...

Yeah, forwarding will do it...each time it forwards an email, each recipient it forwards to would be counted as a sent message. Please remove the forwarder and fix the issue quickly. We can also raise the limit instead if you want, but I'd need to ask about that as this scenario is unusual (our usual process for increases is aimed at mitigating spam complaints from bulk email...forwarding between domains on the same account is kind of unusual in itself...). If you'd like me to look into that, let me know. Unsuspended.

The limit is 50/day. You also previously had mail service disabled for sending well over 100 on a prior day, but re-enabled your own mail (mail service removes itself when you exceed the limits, re-enabling it and continuing to send mail without contacting support results in a suspension for limit evasion). Can you explain why you were sending so many emails?

Also, make sure the CF proxy is disabled ("DNS only") for the webmail record.

Did you ever create a DNS record for webmail in Cloudflare? The reason this is looping is because it can't get a certificate. You need to create an A record pointed to the same IP as your domain for the webmail to work. Detail: DNS problem: NXDOMAIN looking up A for webmail.spanyolkonyvelo.es - check that a DNS record exists for this domain; DNS problem: NXDOMAIN looking up AAAA for webmail.spanyolkonyvelo.es - check that a DNS record exists for this domain I have no idea why the regular mail client doesn't work...the settings look correct. Can you try unchecking the option to configure automatically and specify the port?

Post a screen shot of the mail client settings so we can see what you're using. For the webmail, I responded to your other post as well. That's caused by having Cloudflare's SSL settings set to "Full (strict)". Change to "Full" without the strict mode and that should be fixed.

Try using johnny.heliohost.org as the host name when configuring mail clients instead of your domain.

This usually happens because of incorrect Cloudflare SSL settings. The most common cause is selecting "Full (strict)", which is not supported. Changing it to plain "Full" (without the strict) should make it work.

Escalating since I'm not at a PC. Either me or Krydos will get to this for you at some point today.

Gmail does not accept email from us by default because SPF and DKIM are not set up unless you request it (or you can set them up yourself if you're using external DNS). If you send mail from a mailbox in Plesk's webmail, you'll get a message back from Google explaining this. For automated emails such as from mail() it will report a success yet never arrive. There's no mailbox on the sending end, so your email gets sent, Google throws it out, and you can't receive the error back. PHP will report a success since mail() returns true when the send succeeds, not when it delivers, ...PHP doesn't care about, and has no way of knowing, that the receiving end discarded what it sent. The fix for this is usually to set a From address in the mail command (e.g. set the header paramater to "From: noreply@marckeeley.helioho.st"), then request that SPF and DKIM be set up for marckeeley.helioho.st. Do you want me to get SPF and DKIM set up for your domain?

Krydos can do this for you.

When I unsuspend the Johnny account, the tommy account will end up suspended. Do you have everything you need off of the Tommy account?

This is not something that's cleanly supported: We have to fully remove the addon domain, change the main domain, then add the other domain back as an addon. This will cause your document roots to change so your files will need to be moved, and anything else that may have been done to either domain (like setting up mailboxes, or changing PHP versions, etc.) will be undone. My advice would be to leave it as it is. Are you sure you want to do this?

You’re suspended for having more than one account. Users are only allowed to have one account. Which one do you want to keep?

At the moment, Tommy is actually slower than Johnny, though this likely won't be the case once Tommy is rebuilt (we're already in the process of rebuilding it). For right now, accounts don't really move between servers...we just delete your account and send an invite so you can sign up again on the other server, which would involve having to re-request your domains and DKIM and everything else. And yes, Tommy does requires a 30 day inactivity logins. We are working on a server called Morty that won't have these (and no load suspensions either), but there will be a monthly fee attached to it instead that varies based on resource usage.

Unsuspended. It may take a few minutes to work again.

This should be back shortly. We turned it off in an effort to correct another issue but didn't realize it would remove so much functionality. The server is in the process of resyncing and you should see these options again when the process is complete.

Glad to see everything is working now Please let us know if you need anything else.

Incoming email shouldn't be limited, but outgoing email is (to prevent people from using our service to send spam). There's also a 50/day cap on outgoing messages. If you need additional outgoing messages, let us know. There's a few questions you'll need to answer to have the limit raised.

Yes you can change the email address on your accounts. For the hosting account, in Plesk, click your profile in the upper right->edit and you can change the email. It takes a little while for it to sync into the website. For the forum, you can edit your forum profile to change it. Note that you need to change the forum email separately from the hosting account, they do not sync with each other. Domains added. They might take a little while to set up due to other tasks running at the moment, and up to 2 hours to work once they appear in Plesk.

Full is just as secure in that the connection is encrypted, but unlike "strict", it doesn't verify the origin's identity. Using regular Full mode allows CF to make encrypted connections to origins that use self-signed certificates (which Plesk uses by default) or invalid certificates (which yours is, common name doesn't match the domain name). The ability to reach your site when the certificate is invalid or self-signed is a requirement for Plesk to successfully obtain valid certificates, as Lets Encrypt requires Domain Verification, which fails if CF is blocking the site due to strict mode. Strict is not recommended as a result (it may work once you have the initial certificate installed, but renewals may give trouble, and any server maintenance that results in the cert being removed will knock your site offline).

Unsuspended. It may take a few minutes to work again.