Odd autoreply problem with separate email + webserver.

[scabpicker]

I have a customer who was setup with the separate email+webserver setup described here. IspCP 1.0.0, debian lenny.

It does seem to work properly, with the exception of autoreply messages. When they set an autoreply, persons who send to it get the following in a bounced message:

Reporting-MTA: dns; ******mail.********.net
X-Postfix-Queue-ID: 2E0BE842FC
X-Postfix-Sender: rfc822; donotreply@*******.com
Arrival-Date: Fri, 5 Jun 2009 21:12:23 -0500 (CDT)

Final-Recipient: rfc822; donotreply@ispcp-arpl.********.com
Original-Recipient: rfc822;donotreply@*******.com
Action: failed
Status: 4.3.0
Diagnostic-Code: X-Postfix; mail transport unavailable


This is the mail system at host *****mail.******.net.

I'm sorry to have to inform you that your message could not be delivered to one or more recipients. It's attached below.

For further assistance, please send mail to postmaster.

If you do so, please include this problem report. You can delete your own text from the attached returned message.

The mail system

(expanded from ):
mail transport unavailable


The only lines that reference ispcp-arpl in the web machine's logs are:

Jun 5 13:22:01 *******web postfix/pipe[26110]: 94F82894987: to=<donotreply@ispcp-arpl.****.com>, orig_to=<donotreply@****.com>, relay=ispcp-arpl, delay=0.98, delays=0.19/0.03/0/0.76, dsn=2.0.0, status=sent (delivered via ispcp-arpl service)
Jun 5 13:22:01 *******web postfix/pipe[26110]: 6AD9C894B46: to=<donotreply@ispcp-arpl.****.com>, orig_to=<donotreply@****.com>, relay=ispcp-arpl, delay=0.84, delays=0.51/0/0/0.32, dsn=2.0.0, status=sent (delivered via ispcp-arpl service)
Jun 5 16:02:50 *******web postfix/pipe[17856]: 0A7C7894A67: to=<donotreply@ispcp-arpl.****.com>, orig_to=<donotreply@****.com>, relay=ispcp-arpl, delay=1.2, delays=0.69/0.01/0/0.48, dsn=2.0.0, status=sent (delivered via ispcp-arpl service)
Jun 5 16:02:50 *******web postfix/pipe[17856]: 32308894B59: to=<donotreply@ispcp-arpl.****.com>, orig_to=<donotreply@****.com>, relay=ispcp-arpl, delay=0.4, delays=0.12/0/0/0.27, dsn=2.0.0, status=sent (delivered via ispcp-arpl service)


The mail server's logs paint a different picture:

Jun 6 15:59:21 *******mail postfix/qmgr[2111]: 2E0BE842FC: to=<donotreply@ispcp-arpl.****.com>, orig_to=<donotreply@****.com>, relay=none, delay=67618, delays=67617/1/0/0, dsn=4.3.0, status=deferred (mail transport unavailable)
Jun 6 16:24:21 *******mail postfix/qmgr[2111]: warning: private/ispcp-arpl socket: malformed response
Jun 6 16:24:21 *******mail postfix/qmgr[2111]: warning: transport ispcp-arpl failure -- see a previous warning/fatal/panic logfile record for the problem description
Jun 6 16:24:21 *******mail postfix/qmgr[2111]: 6E7CB842F8: to=<donotreply@ispcp-arpl.****.com>, orig_to=<donotreply@****.com>, relay=none, delay=101331, delays=101330/1/0/0, dsn=4.3.0, status=deferred (mail transport unavailable)
Jun 6 16:34:21 *******mail postfix/qmgr[2111]: warning: private/ispcp-arpl socket: malformed response
Jun 6 16:34:21 *******mail postfix/qmgr[2111]: warning: transport ispcp-arpl failure -- see a previous warning/fatal/panic logfile record for the problem description

I'm kind of suspecting that the issue is that /var/www/ispcp/engine/messager/ispcp-arpl-msgr isn't on the mail box. Does anyone know if that is the case? If so, would an nfs mount of same fix the problem?