Search results

Have you tried http://kb.odin.com/9296 ? (try it even if you didn't change your hostname) I'm not sure if this will help, but you can try to upgrade to plesk panel 10.1.1. Perhaps this error is going to be fixed if plesk is updated.

IgorG, I tried this too, but every backup fails now

The sso database retains the old Service Provider ID's of past sso registrations, (this could be either a bug or a feature), so I guess it's considered normal to see multiple Service Provider ID's. Have you tried the update-hostname command (http://kb.odin.com/en/9296)? I'm afraid I don't know...

Hello EduardoG, The SSO system is using an sqlite database to store data (/var/lib/sso/sso.db). Each Service Provider ID is stored inside that database, in a table named sp. No such SP specified as target, probably means that your Service Provider IDs were not stored, when you reattached...

I had this problem on a server in the past, and I decided to run /usr/local/psa/bootstrapper/pp10.9.0-bootstrapper/bootstrapper.sh repair (before Mr.Yes posted the method he/she used) and the issue stopped occurring, apparently the repair fixed it.

IgorG, I went to http://kb.odin.com/en/9329 and downloaded the send-report file, but then I noticed I had to change the line #!/opt/psa/bin/sw-engine-pleskrun to #!/usr/local/psa/bin/sw-engine-pleskrun since I'm using an rpm based linux (plesk is installed in /usr/local/psa). I tried to edit...

You mean you deleted the xml files of the backup? Now that the xml files are removed, does the backup work?

I think the sso feature is a bit problematic in my opinion. I wish it would not brake so easily. I had a 403 error, I couldn't detach & reattach plesk billing to sso but I managed to solve it by editing the billing database. If you are planning to try what I'm suggesting, try it at your own...

Is spam protection enabled in the e-mail accounts settings? I had the same problem, so I tried the following: Removed spamassassin & psa-spamassain and deleted the directory /var/lib/spamassassin Installed spamassassin and psa-spamassassin using the autoinstaller...

When a customer backups his/her site using Backup Manager, the size of the backup will be included on mail size statistics, on next calculation. How to reproduce: Let's suppose there is a client with the following statistics on Statistics tab (https://www.domain.com:8443/smb/statistics)...

If your subscriber backed up his site using the Backup Manager, the size of the backup is added on the mail size statistics. It's one of Plesk Panel 10 bugs. Otherwise you could try recalculating statistics for that domain: /usr/local/psa/admin/sbin/statistics --calculate-one...

I have the same issue too on a CentOS server with Plesk Panel 10. It's one more of Plesk Panel 10 bugs. Ever since Plesk Panel 10 was installed, I have seen 4 - 5 bugs so far. I never had serious issues (except one with Postfix) with Plesk Panel 8.x and 9.x. Apparently Plesk Panel 10 was...

I have the same issue too, must be one of the Plesk Panel 10 bugs. I hope it's going to be fixed soon.

I just noticed this issue too, on my server. I hope a fix will be released soon

Glad to know the switch completed successfully. Actually I think QMail is the default MTA when installing plesk panel for the first time (at least I think it is when installing Plesk Panel on an rpm based linux).

Yes, technically switching to QMail, means just avoiding the problem, this can't be considered a true solution. However the users on a server usually don't care much about what an MTA is, they just want to send their e-mails successfully, so I did what I thought it was necessary to keep my users...

Yes, I switched back to QMail in December 20th 2008 (4 days after I started this thread) and still using QMail ever since (currently still using it on Plesk Panel 10.0.1), this problem doesn't appear when using QMail.

Wow, 14 thread pages so far, this thread has become really big since I started it back in December 2008. IgorG, If I understood correctly you suggest that this error is basically the e-mail client's fault (if it's indeed sending a malformed message). However, this error happens when using...

Postfix still doesn't work correctly. Just tried Plesk 9.2.3 with Postfix on a CentOS 5 testing server. Even on Plesk 9.2.3, Postfix still raises queue file write errors on messages with large attachments (above 5MB), and when Postfix is used, DomainKeys protection is not working.

I have installed Plesk 9.2.1 on a test server, postfix now works, but not domainkeys.