Search results

Another option is called Split Domain Routing (SDR). This will allow you to delegate certain email addresses on your domain between two different providers. This article explains it best; Split Domain Routing: Getting Email for Your Domain at Two Providers - LuxSci

Good choice!

Let's skip everything in this thread and just focus on the error; from=<domain@domain.at>, size=4452, nrcpt=1 (queue active) May 7 09:12:41 ip-172-31-15-200 postfix/smtp[13879]: 4F9D540143: host mx01.emig.gmx.net[212.227.17.5] refused to talk to me: 554-gmx.net (mxgmx114) Nemesis ESMTP Service...

Your screenshot literally provides us with ZERO information to assist here.

Ok, so you added the same IP for ns1 and ns2, now you'll need to go to the registrar side and register the nameservers there, and then you'll be able to setup the nameservers. If you're getting an error, we will need to see the error you are getting.

Alibaba Cloud actually blocks outgoing port 25 by default, and also will reblock the port if they detect what they consider spam. This absolutely resembles spam. Contact them; it's your best solutions at this point.

In the resource section, you'll see an old video I created about enabling z-push which is basically an open-source alternative for ActiveSync; from there, you could theoretically incorporate ownCloud, or it's fork Nextcloud.

What is your current cron entry for KAV?

This would depend on the path to PHP; the simplest method to locate this would be to create a phpinfo file and upload it to the domain you were looking to modify,

honest on Plesk website? It's laid out pretty directly; How to get support directly from Plesk?

How to limit CPU and memory usage on Plesk for Linux?

+1 for Best Friends. Be sure to check them out if you're ever in Utah. Great place.

Don't forget to vote; varnish cache

You can use a tool such as IMAP Sync; Imapsync online

^ sounds more like a bandaid then a fix. Using something like https://www.mail-tester.com would help in this case.

Welcome @Monty! Feel free to grab a beer from the imaginary fridge.

I'd give you a bonus point for running 7.1.25, but i'd have to then subtract said point for having the exposed PHP info page.

I'll agree with you on the 70% figure, although it is closer to 60% now I believe. I'm not really buying the "moving to m2" excuse though - M1 works on PHP 7, and most developers would have already updated their modules for PHP 7. The time investment to handle the odd module that may not work...

There ya go. I also like to use this to spot SSL related issues; Why No Padlock?

are you using the same s3 bucket? or at least the same Availability Zone?