PHP - MySql - Mass Mail sending problem

We currently run our website on a UNIX virtual private server and are using PHP and Mysql to send out our email blast once a week. The problem we are having is emails to our domain bounce back to our server as well as messages to We checked our IP on various blacklists - and ave not found to be blacklisted. our php.ini file is set to
SMTP = localhost
smtp_port = 25

We also host another website on the same server - ( and it does not have the same problem as our other domain. Let me know what information you may need to assist us with this problem and it is greatly appreciated.
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

with which error-codes are the mails bouncing?

btw those php-settings do not apply to unix there only sendmail_command is used
djvillinAuthor Commented:
below is the message I received in Plesk Mail Que:

Received: (qmail 30183 invoked from network); 31 Jan 2008 16:17:29 -0800
Received: from localhost (HELO (
  by localhost with SMTP; 31 Jan 2008 16:17:29 -0800
MIME-Version: 1.0
From: Edge Insiders <>
Subject: Giving You The Edge
Content-Type: multipart/alternative;

Thats all that I recieved back, and thanks for the explanation on the php.ini variable :-)
djvillinAuthor Commented:
On a similiar note im trying to empty the mail queue but when  run qmhandle -D it gives me this error:

[root@theedge1039 ~]# qmhandle -D
Calling system script to terminate qmail...
Can't exec "/usr/local/bin/svc": No such file or directory at
        /usr/local/bin/qmhandle line 192 (#1)
    (W exec) A system(), exec(), or piped open call could not execute the
    named program for the indicated reason.  Typical reasons include: the
    permissions were wrong on the file, the file wasn't found in
    $ENV{PATH}, the executable in question was compiled for another
    architecture, or the #! line in a script points to an interpreter that
    can't be run for similar reasons.  (Or maybe your system doesn't support
    #! at all.)

What info do you need from me to help me further trouble shoot this prob?

On my original problem to add more info we host our DNS at network solutions and pointed our A records to our VPS and the mail records to our exchane server. We do not host our own DNS/Nameservers on the VPS. But we use our VPS to send out our mass email blast.
djvillinAuthor Commented:
found solution

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Can you please share your solution with us?
I've stumbled upon the same problem with Plesk recently.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Email Servers

From novice to tech pro — start learning today.