Whenever users open their desktop based email application to read messages, it will contact the server for new messages. This seems like a bug with how the Plesk setup is trying to decide whether it is hosting email locally or not?Īny help much appreciated as this is quite a big problem as lots of our clients host their emails on other servers / on an exchange server and this problem is just going to plague me until it is resolved! I am going to scan my postfix configurations on my other servers (where I have never had this problem) and see if there is a setting to resolve this problem.IMAP – Internet Message Access Protocol, as its name suggests enables users to access their IMAP enabled user account email messages from any location at any time, provided they have access to internet connection because the emails residing on servers. The strange thing with my problem is that I can send email from another domain on my server to the problem domain but it's specifically when a website on the problem domain sends enquiry forms through localhost to its own email address (hosted on another server) it is trying to deliver them locally and bouncing even though I have told Plesk that it does not handle email. I am suffering from this exact problem but my /var/qmail/control/virtualdomains file is empty so I cannot even do the hack that is detailed. I believe the following is reported accurately but I do not mean to wrongly point the finger if what I am saying does not make sense! Just to give some background I am not a linux server expert, my role involves some server maintenance because of necessity.
If there is a official solution in plesk, it would be the better way. It's no problem to write a little script to filter the domains with a remote server, but it no nice solution. Is there no "button" in plesk to activate an function like "this domain ist not in my recipient file" or someting else? The other way to delete the domain int the configfile /var/qmail/control/rcpthosts sound more logical. If I configure his remote server to relay the outgoing mails on the plesk-server, the mails would not be blacklisted, but the remote mail server could not relay on the plesk server, because the mail-service is disabled and a smtp-auth would not be able anymore. If it send mail directly without an smarthost, the mails will be blacklisted by all blacklists regarding his dynamic ip. The customer is actually using his remote mail-server as smtp and pop! But the remote mail server has no static ip (dynamic ip by adsl) and has no reverse name for the ip, matching his dyndns hostname! If I disable mail-service for the domains using an external mail-server, the other customers can send them mails without any problems. This would solve the problem, but an open mail relay is not the best solution. If I open relaying for anonymous, I could disable our customers eMail-function in plesk and then using plesk-server as smartrelayhost without auth.
The admin-manuel and the relay-options don't solves the problem, because the relaying works fine (I'm not using an open relay!).
or to disable the email-function for incoming mail, without deactiviating the auth for a relayhost function? Is there any solution? for example how can I tell plesk to look up a mx-record before he look in the local recepients file. But he cannot send mails anymore, because he could not auth with the plesk server to relay his mails. If I deactivate the whole eMail-function in his account, I can send him mail without error, because plesk (qmail) looks for a mx-record. The recepient has only one dummy email-account in his plesk-setup for sending out emails with his own server (relayhost with smtp-auth). The recepient domain has a different mx-record than the plesk-servers mx. The problem occurs because the recepient has his own mail-server. If I send an email to another domain hosted on the same plesk-server as my domain, I receive the following error back: I've got a problem with my plesk 9.2.2 linux-server.
0 kommentar(er)
