Search results

Those googleusercontent ip's are also spam mails. So I would suggest to add port 25 for those who want.

I think there is even already a "convert" option present in your license account if I'm not mistaken.

Then it would be unusable if one blocks all google ip's then gMail posts not not be able to be received either. In post #5 it's only Google cloud if I'm not mistaken.

No to my opinion, since the SPF and DKIM record still exist for the hostname, so where should spoofing take place? It's not the best fix, agree to that, but this is something DA should fix for resellers and not the resellers themselves. Exactly this, so DA needs to change this behaviour for...

But those also are only the googleusercontent ip's? Or all google ip's? Because we wouldn't want to blok google mail itself for example and notices from adsense.

Yep, DA should also fix the updates so csf -u can be used and not reinstall everytime whitelisting the current ip doing the update.

I think you missed his first line is his first topic as reason for the loss of files. ;)

It's not an issue, it's a feature that mail to root is not send. Easily to solve by setting root email in /etc/aliases and restart Exim. How?

If I'm correct it's just send by Google. I know Google can pickup mail from other domains. I thought maybe it's picking up mail from other domains and then sending it, because the sender domain address is not from Google, only the MTA address. We also report all of these mails via Spamcop to...

You might be right, but that opting out would be for that Google account only not for messages send to your server and other customers.

Those are the skin options, so I presume like floyd said you want to go back to the Enhanced skin. Since you were able to change it to Evo, you must be reseller or admin. Just use reseller level and then you can change to Enhanced again.

Is there an easy way to implement this in CSF? Or Spamassassin?

Just type "skin" in one of the search bars and Evo will give you the correc page if all is well.

I never said it was a good solution. To me the best solution is still the dyndns (no-ip.org) solution for such cases, or a VPN.

The symlink is made by Directadmin, seems they forgot to add a symlink for the logfile, although my /logs directory (in the correct place) does not contain any logs, does yours? We do have a /var/log/roundcube/errors.log so it seems they moved it to there and the csf.conf just needs adjusting to...

Lately getting again more spam via Google and Outlook, will post headers if it happens again this week.

You might want to have a look at this thread. It's set as solved but was a bit ongoing. I also experiencing again spam via Google and Outlook. https://forum.directadmin.com/threads/how-can-i-block-this-spam-coming-via-google.82079/

If you are talking about whitelisting Starlink ip's, then yes ofcourse it's open to all Starlink ip's. Just CIDR so like: 179.65.148.0/24

Sorry, could be me but I don't get it. I don't see the fun about the dyndns option related to that.

Why? That is good for admins with a more dynamic ip, right?