customer is receiving errors after upgrade

[JeremyV]

Ok, this is a bit confusing, but hopefully someone may be able to help. About a day or two after we upgraded to cP6 a user who was using hivemail is now getting a few errors. Basically, hivemail works (if you aren't familiar with it) by having no pop accounts, and you set the catchall address to point to a script. For example, this is what he has setup:

|/usr/bin/php -q /home/username/hivemail_process.php

This was not altered, or changed before or after the upgrade, just showing that when the email comes in, it gets shot to this script. Which then checks the DB to see who it goes to and distributes it accordingly.

Anyway, a few days after we upgraded to cP6 the user also upgraded to the latest hivemail (bad timing for troubleshooting ) Anyway, the email DOES get delivered just like it is supposed to, but the person sending the email gets this:

A message that you sent could not be delivered to one or more of its

recipients. This is a permanent error. The following address(es) failed:

pipe to |/usr/bin/php -q /home/username/hivemail_process.php

generated by [email protected]

pipe to |/usr/bin/php -q /home/username/hivemail_process.php

generated by [email protected]


The following text was generated during the delivery attempts:

------ pipe to |/usr/bin/php -q /home/username/hivemail_process.php

generated by [email protected] ------

That is the jist of it.. it is basically shooting back an email saying the mail couldn't be delivered. But at the same time, the mail IS being delivered

Since we both upgraded at such a close time frame, I had asked him if possible to revert back to the old version of hivemail and see if that cleared up the problem. He informed me no changes in behavior and it is still sending senders that failed delivery message.

I searched the hivemail support forums and have no encountered any similar reports. You would think if this was a problem with cPanel 6 then there would be various reports of this behavior. So I'm not sure it is even a problem since I upgraded, but just running this by everyone to see if it makes sense.

Was Exim or anything else upgraded with this version? Or any other possible items altered to do tihs? Just scoping out all of my options, thanks!

 

[JeremyV]

any ideas here anyone? He verified and said no emails were sent in-between the day cpanel was upgraded and the day he upgraded his script, so it looks as if some configuration setting was changed with the cpanel upgrade.

So it is sending the mail via the pipe, but at the same time a message gets sent to the sender saying underliverable, when in fact it is. Is this just a setting in exim or something that can be disabled?

Thanks for your time.

 

[Annette]

I'd check the valias for the site. By that error, it seems as if the system is not properly terminating addresses that might be sequenced for a single addressee. Something like this, for instance:

[email protected]: [email protected],|/some/pipe/here

This is just one example of a piping and forwarding combination that we've seen fail because the pipe is not in quotes. Another example we've seen:

[email protected]: "|/home/pipe/here",[email protected]

That one was from Perldesk 1.6, where exim would not write to the pipe and send the mail to a POP box. Switching them and forwarding to a mailbox other than [email protected] worked (i.e., to [email protected] instead - this was resolved in PD 1.7).

 

[sfxx]

Hello, I'm just having the same problem.
When you send an email, it is piped and processed, but you also receive a mail delivery failure message.
Of course I'm running php in quiet mode.

Have you solved this problem?

Thank you.