Plesk 8.1 and Email Piping Issues

[easyhud]

Hi,

I'm having an issue with email piping with Plesk 8.1. I've setup email piping exactly like the manual stated. I chmod'd the cli directory and index.php, and I tried adding "php -q" but I get the same result. Notice how qmail is appending my domain to the piping command that I entered into the ".qmail-support" file (the email address is going to be support, so it just happens to be the same as in the manual). Here's a copy of my logs below with my domain information replaced for security reasons:

Jul  5 13:35:10 qmail: 1183667710.624676 starting delivery 17: msg 11665532 to local 1-"|/var/www/vhosts/myreceivedomain.com/support/cli/index.php"@myreceivedomain.com
Jul  5 13:35:10 qmail: 1183667710.624989 status: local 2/10 remote 0/20
Jul  5 13:35:10 qmail: 1183667710.625059 delivery 16: success: did_0+1+0/qp_7875/
Jul  5 13:35:10 qmail: 1183667710.625125 status: local 1/10 remote 0/20
Jul  5 13:35:10 qmail: 1183667710.625184 end msg 11663790
Jul  5 13:35:10 qmail: 1183667710.628764 delivery 17: failure: This_address_no_longer_accepts_mail./
Jul  5 13:35:10 qmail: 1183667710.628956 status: local 0/10 remote 0/20
Jul  5 13:35:10 qmail: 1183667710.703040 bounce msg 11665532 qp 7878
Jul  5 13:35:10 qmail: 1183667710.703157 end msg 11665532
Jul  5 13:35:10 qmail: 1183667710.703427 new msg 11665534
Jul  5 13:35:10 qmail: 1183667710.703490 info msg 11665534: bytes 2837 from <> qp 7878 uid 2522
Jul  5 13:35:10 qmail: 1183667710.760091 starting delivery 18: msg 11665534 to remote npregean@mysenddomain.com
Jul  5 13:35:10 qmail: 1183667710.760166 status: local 0/10 remote 1/20
Jul  5 13:35:12 qmail: 1183667712.310399 delivery 18: success: 64.202.189.86_accepted_message./Remote_host_said:_250_Accepted_message_qp_6393_bytes_3017/
Jul  5 13:35:12 qmail: 1183667712.310549 status: local 0/10 remote 0/20
Jul  5 13:35:12 qmail: 1183667712.310586 end msg 11665534

Anyone know why the domain name is getting appended to the command or any issue or setting that might be causing this?

Thanks and any help would be greatly appreciated.

[akamaka]

I have same problem with Plesk 8.2. How can i fix this?

Thanks

[easyhud]

Unfortunately we were unable to find a solution to this anywhere. We ended up using a cPanel server because absolutely needed piping working and didn't have time to figure out a solution.

[akamaka]

After chmod-ed httpdocs directory to 755 this works. But in this way i open a big security hole

[craigbrass]

After chmod-ed httpdocs directory to 755 this works. But in this way i open a big security hole

Its only a security hole if there is some unsecure software around that directory tbh.

[akamaka]

Originally Posted by craigbrass

Its only a security hole if there is some unsecure software around that directory tbh.

All ssh users (from any another domain on that server) can access a 755 chmoded httpdocs folder and its contents. I think, this is a big security problem...

[craigbrass]

Really? That sounds like a server misconfiguration. The user should only have access to their own user directory.

[supportskins]

Originally Posted by akamaka

All ssh users (from any another domain on that server) can access a 755 chmoded httpdocs folder and its contents. I think, this is a big security problem...

Its as if you are inviting trouble! Should be fixed ASAP!!

[akamaka]

In Plesk htpdocs need to be chmod 750. This is the normal server configuration on Plesk servers. In this way ssh users can not access domains of another users. As you see, chmoding httpdocs to 755 will break the Plesk security schema.

[craigbrass]

Well if this is the way Plesk works, I am glad I do not use it. How stupid is working SSH access like!