FMEncoder sendiong blank results after server move

[arawkins]

Hi, we have a site which we set up fmencoder on awhile back, and it recently was moved to a new server. Our secure form is still working, but the fmencoded file that comes as an attachment is blank. The document root is the same on the new server, and path to fmencoder is set up properly. I don't get any error report at the DEF_ALERT email address either. Everything was running ok last week before the server move so it seems like it must be something that's different with the new server. Is there anything else I can check?

Other maybe-relevant details: it's a multi-page form, and is using an ini file to store the recipient address.

Thanks,
Alan

[russellr]

Hi,

A blank attachment suggests more than one error.

Or, perhaps the email is being damaged by the new email server.

Please view the email source and paste a sample of it here.

[arawkins]

Sure, here is the email source. As this is a public forum, I changed a few values to keep server addresses, email addresses etc. confidential. Hopefully this is still some use. I tried to PM you the full message source but couldn't find a way to do so on the forum, do I need additional permissions for that?

Return-Path: <username@webserver.com>
Delivered-To: recipient@email.com
Received: (removed)
X-Virus-Scanned: OK
X-MessageSniffer-Scan-Result: 0
X-MessageSniffer-Rules: 0-0-0-3648-c
X-CMAE-Scan-Result: 0
X-CNFS-Analysis: v=2.1 cv=UZ1oFsiN c=1 sm=0 tr=0 a=kFBhAeLZhPmG01u23rsugg==:117 a=VUk6f01CMKECDbt4IKjCog==:17 a=D5rYzZNk54MA:10 a=a7DY7DLJ1rUA:10 a=ECgvOV3qTYYA:10 a=NslmJDdM5TEA:10 a=zCf7SY1oAAAA:8 a=pR6JWRFiAAAA:8 a=21-350hwAAAA:8 a=KGjhK52YXX0A:10 a=SV0o6UJL7v4yw-suvS0A:9 a=eAYkqGJDE0IA:10 a=9H4EKLHo9a0A:10 a=WzHNiX6cKY2DZ1D7HSYA:9 a=wPNLvfGTeEIA:10 a=nOZS0LIn0L33imh4XmYA:9 a=eSj2UnRacOQA:10 a=1ARARtbZTC4A:10
Received: from (removed)
X-Spam-Threshold: 95
X-Spam-Score: 0
X-Spam-Flag: NO
X-Virus-Scanned: OK
X-MessageSniffer-Scan-Result: 0
X-MessageSniffer-Rules: 0-0-0-2800-c
X-CMAE-Scan-Result: 0
X-CNFS-Analysis: v=2.1 cv=Id2+Bwaa c=1 sm=0 tr=0 a=VUk6f01CMKECDbt4IKjCog==:117 a=VUk6f01CMKECDbt4IKjCog==:17 a=D5rYzZNk54MA:10 a=ECgvOV3qTYYA:10 a=NslmJDdM5TEA:10 a=zCf7SY1oAAAA:8 a=pR6JWRFiAAAA:8 a=SV0o6UJL7v4yw-suvS0A:9 a=eAYkqGJDE0IA:10 a=9H4EKLHo9a0A:10 a=WzHNiX6cKY2DZ1D7HSYA:9 a=wPNLvfGTeEIA:10 a=nOZS0LIn0L33imh4XmYA:9 a=eSj2UnRacOQA:10 a=1ARARtbZTC4A:10
X-Orig-To: recipient@email.com
X-Originating-Ip: [174.142.46.57]
Received: (removed)
Received: (removed)
To: recipient@email.com
Subject: email subject
MIME-Version: 1.0 (produced by FormMail 8.14 from www.tectite.com)
Content-Type: multipart/mixed; boundary="PARTd41d8cd98f00b204e9800998ecf8427e"
Message-Id: <E1WPh9j-0000D1-KC@webserver.com>
From: username@webserver.com
Date: Mon, 17 Mar 2014 19:41:19 -0400
X-ServerProvider-MailScanner-Information: Please contact the ISP for more information
X-ServerProvider-MailScanner-ID: 1WPh9j-0000D1-KC
X-ServerProvider-MailScanner: Not scanned: please contact your Internet E-Mail Service Provider for details
X-ServerProvider-MailScanner-SpamCheck: 
X-ServerProvider-MailScanner-From: username@webserver.com
X-Spam-Status: No
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - webserver.com
X-AntiAbuse: Original Domain - recipientdomain.com
X-AntiAbuse: Originator/Caller UID/GID - [694 696] / [47 12]
X-AntiAbuse: Sender Address Domain - webserver.com
X-Get-Message-Sender-Via: webserver.com: authenticated_id: username/primary_hostname/system user


(Your mail reader should not show this text.
If it does you may need to upgrade to more modern software.) 


--PARTd41d8cd98f00b204e9800998ecf8427e
Content-Type: text/plain; charset=ISO-8859-1




--PARTd41d8cd98f00b204e9800998ecf8427e
Content-Type: text/plain; name="data.fmencoded"; charset=ISO-8859-1
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="data.fmencoded"




--PARTd41d8cd98f00b204e9800998ecf8427e--




==================================

[russellr]

Hi, OK, so it looks like something (probably 2 things) is going wrong on the server. I recommend you buy a support subscription so we can help resolve it.

[arawkins]

Ok, thank you. I have subscribed for support. Please let me know what the next step is to troubleshoot this.