Search results

Barry, you may also need to look at IPs whitelist ('Server' -> 'Mail' -> 'Whitelist') -- these IPs are allowed to send mail through server w/o authorization. Also, SMTP authorization does not mean that spammers cannot send mail TO your server -- they just cannot relay the mail THROUGH your...

postman, Plesk has wonderful feature -- Autoupdater -- which is available from control panel and it is possible to install all Plesk-related components from there (and Autoupdater will install all dependencies).

In apache configuration, webmail vhost is defined with "ServerAlias webmail.*" so it will be only called by it. Also, webmail uses hostname from URL to define full mailname to log into webmail, so without it login would not be possible (even if 'short mailnames' are allowed).

qmail restarts to re-read configs about virtualhosts where new domain is added. As to the error itself: I can only suggest you to change all occurences of 'start-stop-daemon' in /etc/init.d/qmail to '/sbin/start-stop-daemon'. Hope it helps.

to check if you are running Plesk inside VE, check if /proc/vz/veinfo exists. If it does not, then you are running physical server. In this case try to run 'depmod -a' command to rebuild modules table. However, kernel version ('2.6.9-023stab043.1-smp') indicates that it is Virtuozzo VE. If...

It really looks like the issue with modules allowed for VE. Did you try KB article's recommendations?

qmail-scanner is not a part of Plesk AFAIK... never had any expirience with it... maybe someone in thirdparty forum had... try asking there.

what's on line 3672 of /workdir/restore/dump-plesk.xml?

looks like network connection to source host is broken. Also, check that PMM is not corrupted by using 'rpm -V psa-migration-manager | grep ^..5' command.

No, Plesk Migration Manager can be used only by admin himself. Clients cannot use it.

check that physical hosting has been set up on the same IP which is specified in DNS settings. If they mismatch, then Plesk default page will pop out even if those two IPs on the same server.

Updating the system will not help, because system usually has nothing to do with Plesk upgrade problems. What kind of problems/errors do you have with both statistics/phpmyadmin?

Stopping cron daemon will not terminate forked processes. To kill the scheduled backup you need to find whole tree of forked processes with 'ps axwwf' command. at the root of this tree is '/usr/local/psa/admin/sbin/backupmng' process. To stop backup completely you need to pass IPs of all members...

try to check if there are any errors in /var/log/httpd/error_log. Also, if there are any custom configuration for this domain in vhost.conf file, try to disable it, restart apache and check how it works without it.

was there any errors on spamassassin start?: /etc/init.d/psa-spamassassin start Also, try to check maillog (/usr/local/psa/var/log/maillog) for any messages from spamd.

it seems that PATH variable which is used by PHP has no '/sbin' directory, since 'start-stop-daemon' command is in /sbin. Try to set PATH environment correctly at the start of PHP script to have '/sbin'.

Is there any errors on activation? When you activate firewall through interface, try to log into the server by SSH and check iptables rules with 'iptables -L -n' There are also some technical fine points about firewall on virtual environment running by Virtuozzo: they are described in KB

It doesn't look like headers which spamassassin puts into headers. If you are using 4PSA antivirus/antispam products, then I think you better check this with them.

There is a section in manual about vhost.conf files where you can find more information. Also, KB has a lot of articles about vhost.conf with examples.

the feature works this way: in qmail configs, for e.g. [email protected]'s mailbox (usually /var/qmail/mailnames/domain.tld/user/) another record is created -- [email protected] (which points to the same mailbox path). So, after enabling mail domain alias you do not need to do anything else -- Plesk...