This is Plesk 9.0 on SuSE Linux 10.1.
It took me and my co-admin a number of hours to nail down a nearly intractable error we had after upgrading from Plesk 8.6 to 9.0. Users of certain domains could no longer send any email.
It turned out that apparently all users whose domains have no SPF records could no longer send any mail at all.
Our current workaround is to change the SPF checking to the SPF checking mode: Only create Received-SPF headers, never block.
Does Parallels/Plesk have a defect-tracking system that I can use to enter this defect? No black holes, please; I report defects only when I can expect quick feedback indicating that the defect description has been received and understood.
Hans-Georg
It took me and my co-admin a number of hours to nail down a nearly intractable error we had after upgrading from Plesk 8.6 to 9.0. Users of certain domains could no longer send any email.
It turned out that apparently all users whose domains have no SPF records could no longer send any mail at all.
Our current workaround is to change the SPF checking to the SPF checking mode: Only create Received-SPF headers, never block.
Does Parallels/Plesk have a defect-tracking system that I can use to enter this defect? No black holes, please; I report defects only when I can expect quick feedback indicating that the defect description has been received and understood.
Hans-Georg