Easiest thing to do is turn off the declude service. Run the script. Then get the source from the declude folder. This file will be exactly what is received from smarter mail.
Then turn declude back on to process the mail waiting. You can then post the source here. I would zip the source and attach it so we can look at the source without having to worry about the email munging it. I have done this process a few times and it has worked wonderfully in tracking down bad header issues with scripts and web site forms. And yes it seems the hay day of the declude mail list is over. Kevin Bilbee > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Michael > Jaworski > Sent: Friday, February 15, 2008 3:20 PM > To: declude.junkmail@declude.com > Subject: [Declude.JunkMail] Header Munged in Body > > Boy this list is so quiet compared to the old days. > > I have not seen this lately but we have a new customer who uses a script to > send a status message to our SmarterMail/Declude setup which is forwarded to > a Postfix server mailbox for final delivery. Only when it is forwarded do > they see the XIN Added headers at the top of the body. As usual the case we > need to prove we(Declude/SM) are not the source of the problem by finding > the real source. Our past experience moves us to point the source of the > problem is the script e-mail structure itself. Does anyone know of a test > site to point their script e-mail to validate the structure of that e-mail? > > Thanks, > > Mike J > > > > > --- > This E-mail came from the Declude.JunkMail mailing list. To > unsubscribe, just send an E-mail to [EMAIL PROTECTED], and > type "unsubscribe Declude.JunkMail". The archives can be found > at http://www.mail-archive.com. --- This E-mail came from the Declude.JunkMail mailing list. To unsubscribe, just send an E-mail to [EMAIL PROTECTED], and type "unsubscribe Declude.JunkMail". The archives can be found at http://www.mail-archive.com.
