Thanks again

Thanks in advance for your help!!

Janusz

  What is it with me and emailing   I tried to send the modified file to contributions@frontaccounting.com

I have used patches for my own stuff, but have never submitted one before.  Other than documenting what I've done and trying to keep the code as fluid as possible with the original style.  Are there any other requirements / guidelines I should / could use?

No, i don't think so. You can send changed files, or patches against selected sources version. We always check the sources before submitting to CVS.

Thanks in advance MPH
Janusz

PS. I also use Suhoshin patch on PHP without any side effects, but I think it can depend on mail content.
J.

  It'll just take me a little longer.  It was late (for me) last night when I got it working.  I've yet to change where the text / html content types go in the header.  I should be able to do that fairly easily tonight. 

  I have used patches for my own stuff, but have never submitted one before.  Other than documenting what I've done and trying to keep the code as fluid as possible with the original style.  Are there any other requirements / guidelines I should / could use?

Regards,

MPH

Janusz

I've got it figured out!!! 

The suhosin security patch for PHP was blocking the emails before the ever got to postfix(My email server).  This would explain why I couldn't find any info in it's log files.  I didn't find it until I increased the debug level in the postfix config file.
from /var/log/messages:

Rather than remove a security measure, I decided to "massage" the code a little.  I removed all of the double "\n"s that I could find in the header and it still was failing.  Once I separated the body from the header, I was getting the emails.  However, for some reason there were extra line feeds in the uuencoded data which rendered the attachment useless.  Adobe said it was corrupt or improperly decoded.  So, I changed the chunking to a length of 72(which really is moot, it just wants a value) and added a "\n" for the EOL, and it everything is working great!!
The \n may not be right since I haven't tested it on a windows box yet.  I would think it's okay because email is email.  Both Windows and Linux read the same email very close to the same.

Thank You for your help and pointing me in the right direction.

Regards,

MPH

Janusz

  After a little more research (Following your instructions) It appears to be a problem with the $this->email header.  I've changed the other 2 variables and it works fine.  Any other combination including the header fails.  I don't have time to dig any further at the moment, hopefully later this evening.

Regards,

MPH
-----------
Janusz,

  Thanks for the info.  Here are the parameters being passed to the mail command.  They all look normal to me.  But I've not programmed anything this involved before.

Some of it may not look quite right as I've removed any personal information, email addresses etc...  I did verify that the original values are correct and the file pointed to does exist.

These are the variables and their values after executing the $ret = mail($mail, $this->subject, "", $this->header); statement.

Thanks,

MPH

  I loaded  FA 2.2.11 a few nights ago.  I'm still poking my way around.

One problem that I can't seem to find my way around is: I can't email invoices.  I keep getting

I did some digging around here and see that AF uses the mail function in PHP.  I can't find any entries let along errors in either the mail log or the PHP log.  I'm using postfix and can send email from the command line.  As a test I got a short PHP mailing script

<?php
# The message
$message = "Line 1\nLine 2\nLine 3";
# Send
mail('my.email@mydomain.com', 'My Subject', $message);
?>

Which works fine.

What can I check next?

Thank You,

MPH