Search results

The SpamAssassin spam filter works with a scoring system. If the mail still gets into inbox, you should consider modifying the scores for each part. A very good tutorial on how to modify SpamAssassin for better protection can be found here (german, but maybe you can translate it with Chrome)...

@m3lezZ thank you for your idea with a cron job. I found another idea and will test it: Denying comment spam bots | DjaoDjin The idea is to change spamd to show the ip-address of the spamming server in the maillog. With that you can now make a fail2ban filter.

Most spam on our servers is blocked by different spamassasin and combined fail2ban rules, but this time the Spam was forwarded to external mail-addresses, because our clients love to use their private mail-addresses and have set a forwarding-rule. How can we use fail2ban to block Servers...

T-Online blocks mostly all new/unknown mail-servers. But usually you get a quick response, if you contact them via the mentioned mail address. You should also sign up for Microsoft's SNDS Service Sign in to your Microsoft account or you maybe get blacklisted for hotmail and outlook addresses, too.

Do you use Outlook? Those are most likely from deleted messages. Outlook deletes it and generates the 'deleted not read' responses. If that is for spam-mails, then every spam sender gets such messages.

Now I tried to run script as PHP script via cron-style * * * * * /usr/bin/php -f /var/www/vhosts/html/script.php &> /dev/null Same error.

No, it is configured to "call a URL". No need to run it as php.

The cron just runs a php script via https:// url. If I run the script from another server it works, but the same server where the script is located gives the error message.

Hello, when I start a specific cron job via Plesk, I get the following error: The cron runs under the user www-data and should just load a web-url with a php script. Thank you for your help!

Today we had the same problem again with one of our servers Ubuntu 16.04.6 LTS‬, Plesk Onyx Version 17.8.11 Update #70. After the following commands, the problem was resolved: service apparmor stop service apparmor teardown postqueue -f Could the bug be back again after updating?

Hello, I had a similar problem and I found out that the problem are the bounce mails from MAILER-DAEMON. So, spam was sent to not existing mail boxes and the MAILER-DAEMON tries to return a bounce message. As the sending mail address is forged, this bounce can't be sent, so the mail stays in...

I don't know why, but after I changed settings->server settings->preferred domains for website from "www.domain.tld" to "none" it worked The old server was set to "www.domain.tld", too. Does this make any sense to you?

Update: some mod_rewrite rules don't work anymore, too. Could there be some kind of connection?

Plesk 17.8.11 Update #54 ‪Ubuntu 18.04.2 LTS‬ After migrating a Plesk server to a new Plesk server, the websites with custom DirectoryIndex in htaccess do not work anymore. They show a "403 Forbidden" error. The sites without custom DirectoryIndex work as expected. Anything in the...

The problem is not solved yet. But, I use a cron-job to flush the messages and so the symptoms don't bother me anymore. But I still would like to know, why the messages appear in 17.8, when they didn't appear in 17.0. The cron looks like this: #mailq |awk...

Remarked as unresolved. Now, after the weekend, again we have a lot of these bounce messages. What can we do?

We use spamhaus. Maybe the domain was not in the list as the mail arrived. Although i don't like SPF protection that much, I activated it now. As far as I know, Plesk now supports SRS for forwarded mails, so I gave it a try. Up to now: no more error mails in the queue for some hours. Maybe...

No, these mails are no outgoing spam. I checked the mail body via ssh. A mail doesn't need a valid mx record to be sent. The "from" address can of course be spoofed. For example: the message from [email protected] is sent to our client [email protected]. This mailadress is forwarded to...

The same today. A lot of MAILER-DAEMON@ messages. None of them are outgoing spam, but error messages to the sender which can not be reached of course. Why didn't we have these messages with Plesk 17.0? Is there anything different in the mail configuration?

Next time, try to disable apparmor and than flush mailqueue (postqueue -f): How to disable AppArmor on Plesk 12.x That solved the problem for me. Please keep in mind, that apparmor is part of Plesk Onyx since 17.0 and should not be uninstalled completely.