Search results

@Danny3445 It can be rather simplified to the following golden rule : mail protocols are NOT intended as file transfer protocols. Stated differently, one should not want to send to large messages, for many reasons. The client-side might not even accept the large messages. The server-side...

@Tjerk Visser I agree with your statement but, at the same time, I have to emphasize that the whole issue is on the side of DrWeb (and not Plesk). DrWeb simply has servers that are really unresponsive - you can ping the servers and then you will see how "slow" they are. As a result...

@Danny3445 An elaborate analysis, thank you. However, first try to establish what the source mail server is ........ since some of the mails originating from or relayed by Microsoft can cause hickups. In addition, try to determine whether Postfix does not have to deal with a lot of...

@Sebahat.hadzhi Could you be so kind as to participate in this topic thread, so we can summarize the issues with the SslIt! extension and file a bug report? Thanks in advance!

@Gjimi I am not sure what you intend to report as a bug. In essence, there is no relation between mail.domain.tld and Apache (and there should not be a relation). The mail.domain.tld is used for other purposes than purposes related to the web server (Apache). The "inclusion" of...

@Tjerk Visser Please try to add 85.10.234.30 update.geo.drweb.com to the /etc/hosts file. In most cases, that you should do the trick. Kind regards....

@Raudpats, One of the problems is that your server is responding very slow. This can be the network, the router, the internet connection, the server etc. It is recommended to check connectivity first, in order to make sure that all things are working properly. Please provide the output...

@JuanCar The answers of @Kaspar and @WebHostingAce should have answered your question(s). Nevertheless, it is still important to note that you are using xbl.spamhaus.org and bl.spamcop.net. It is highly recommended to a) use zen.spamhaus.org : this is a combined DNSBL, see ZEN Blocklist...

@Fede Marsell Red lines are difficult to determine, in the sense that it is difficult to say what it is : a subjective opinion or a red line that cannot be crossed in a legal sense. The discussion about "hosting providers" stopping with using or offering Plesk is a bit off-topic. Let's...

@LRLD To answer your implicit question, being it can simply be stated that the current config is not about "compatibility", but it is related to the ability to switch easily from Qmail to Postfix (and back). Stated differently, not about Qmail playing nicely with Postfix (i.e...

@Raudpats The best question here is to ask what you have changed in the apache config. Did you uncomment (or change) the Mutex entry in apache config? If yes, than that could be or is the likely culprit - you can test this by simply commenting out the Mutex entries : if that works, your...

@David Borrink I think that you should explicitly set the remote storage settings for the "mail domain" under Websites and Domains > Backup and Restore > Settings. Please create a specific (sub-)directory on Dropbox first and use that (sub-)directory in the remote storage settings...

@Manuel Garcia It is correct that, as stated by @Sebahat.hadzhi, Postfix is bouncing messages by default to the original sender - that is, Postfix will at least try. The config line bounce_notice_recipient = postmaster will allow bounce messages to be sent to the postmaster, in addition...

@Fede Marsell Wrong conclusion, I have more interest in this matter than most people. In fact, I have asked a legal team to investigate the matter and to determine the competent court. As opposed to talking about this topic, I am investing serious money to determine which kind of actions...

Excellent, thank you. I will do a test migration soon with the solution of @Kaspar and, if necessary, provide you with some feedback ... Kind regards...

@Hangover2, @Fede Marsell and @AlL, As mentioned in another post, quoted briefly as "[ ... ] The best way is to convince Plesk that Imunify is - factually - determining what is "suspicious". This is also the main problem here : Imunify is that kind of extension that flags (almost)...

@brother4 It is pretty safe to conclude that it is related to the fact that you are on a virtualized host, but I am not sure whether that makes things impossible. I think that you should try "updating" from SSH command line, as opposed to the other methods of updating. Just open two SSH...

@Sebahat.hadzhi If the workaround from @Kaspar is valid, then I do not see why the ETA should be in August. Could you be so kind as to speed up the process and implementation of the update? Kind regards....

@TorbHo and @Kaspar @Kaspar, thanks for the quick testing and suggestion for the workaround! @TorbHo, can you keep everybody posted about your experience with the workaround? It should be working like charm, since that is to be expected - nevertheless, an update from you is always welcome...

@TorbHo Please note that messages with valid DKIM signatures are - often (but not always) - also rejected by GMX and web.de. They are notorious when it comes to bad mail server configuration and also when it comes to bad mail reputation - spammers like it. So, do not worry about those...