|
From: Dieter S. <dsi...@sq...> - 2002-04-11 16:35:17
|
There is an upgrade file available for 1.8.3 which addresses the line length for attachments. Apparently this fixed the problem Outlook was having with decoding the attachments. Dieter Simader http://www.sql-ledger.org (780) 472-8161 DWS Systems Inc. Accounting Software Fax: 478-5281 =========== On a clear disk you can seek forever =========== On Thu, 11 Apr 2002, David Ratte wrote: > This is NOT just an outlook problem, I've been complaining about this since > 1.8.3 came out and have not been able to figure it out myself. > > I don't have any microsoft stuff in the building here and I can't read my own > emails using konqueror, netscape 4.75, or anything else! > > I've checked the CPAN code Dieter used and can't find anything wrong with it. > The only difference is the maximum line length is a little shorter, but > changing it back to match the original does not fix the problem. > > I still believe the CPAN code has an issue though, because if you look at the > raw output of sendmail as compared to other BASE64 documents generated by > other programs, documents from other programs have the code all line up in > neat little rows, where the CPAN code looks like a scrambled mess. > > For the moment, all I was able to do to continue to function with my > customers, was to comment skip the base64 encoding routine (and send the > documents un-encoded) > > But, meanwhile I have bigger fish to fry - currently I have a postgres ut-oh > such that my database is corrupt and after a re-index only contains 3 > records, even though a look at the raw files shows much more... anyone know a > good postgres database recovery service? > > -Dave Ratte > Superior Circuit Technologies, Inc. > dr...@su... |