Search results

Hi, it will have solved the issue for 99,9% ;) It's one of the most common issues. Regards, Kristian

Hi, no it does not. You will have to solve this in some other way. Regards, Kristian

Hi, in that case I would just configure 2 IPs on the server and configure only one as MX. If one IP ever gets blacklisted, just switch IPs and update your DNS MX Records. Saves IPs and hassle. But you already seem to have a solution, so good luck ;) Regards, Kristian

Hi, the emails you get only update single files via Microupdates. The server components are not updated. Also new Plesk Versions are not updated as of my knowlege. Regards, Kristian

Hi, please open your own thread. Your problem is not related to this one. But please provide more information also. Apache2 RAM and CPU usage is always as high as their demand. CPU depends on how your Scripts are programmed. RAM depends quite alot on how PHP is configured and used. Using...

Danke, das gleiche :) Gruß Kristian

Hi, that would mean you need an IP for each Domain. In times where IPv4 is valuable, this is a waste of resources. With the upcoming Plesk 12 you will be able to rate limit outbound emails. This should help prevent your server being blacklisted. Regards, Kristian

Hi, all I wanted to do is help you solve the problem. I am not a Parallels employee. Please do feel free to report this as a bug to Parallels support. Regards, Kristian

Hi, same procedure though :) Regards, Kristian

Hi, well this is exactly what's in the database. Domain with ID 32 is "catched" All Other Domains are rejected. So the issue is actually limited to alias-Domains right? You could try and find out which Domain ID your Alias-Domains have and update the information in the Database. Then rerun...

Hi again, could you please try the following command and send me it's output? # postalias -q @example.com /var/spool/postfix/plesk/virtual EDIT: Please also try the following and paste the output: # mysql -uadmin -p`cat /etc/psa/.psa.shadow` -Bse "select * from psa.Parameters where parameter...

Hi, ok, cancel that then. Sorry, looks like you'll have to wait for this to get fixed. Did this behavior occur after some Microupdate? Opening a support Ticket should increase the speed of fixing it a little :) Regards, Kristian

Hi, not that I know the answer, but are you talking to PPA API oder Plesk API? Regards, Kristian

Hi, for it to be fixed, you will have to contact Plesk support. I'm guessing they already know about this though. Regards, Kristian

Hi, well is the hostname in "/var/qmail/control/me" actually in your DNS also? Can you resolve this hostname from your local computer? (not from your server) Regards, Kristian

Hi, it's not been deleted. It's here: http://forum.parallels.com/showthread.php?289825-Plesk-Mail-Forward-to-address-(Catchall)-not-working&p=722838&viewfull=1#post722838 Regards, Kristian

Hi, I can't tell you I am afraid. With migrations, I always tell my customers to disabled Mailservices prior to me starting to migrate. So I never end up with split brain :) If they actually do use IMAP you could try and use rsync. (Without delete option). But I highly recommend you to create...

Hi, not that I know of. But you could change the Groups like this: # find /var/www/vhosts -name cgi-bin -gid `cat /etc/group | grep psacln | cut -d ":" -f3` -print0 | xargs chgrp psaserv That should fix the issue for all wrong cgi-bin below /var/www/vhosts Regards, Kristian

Hi, SSL Certificates are not possible for IPs :) But you could get an SSL certificate for your server FQDN and then tell your customers to use that as a Host? Regards, Kristian

Hi, try executing this command: # /usr/local/psa/admin/sbin/mailmng-domain --unset-reject --domain-name example.com Then check what the Panels says. If Catchall is disabled, try: # /usr/local/psa/admin/sbin/mailmng-domain --set-catchall --domain-name example.com --email [email protected]...