Patch 4.5.0c - InboundEmail.php

[simple]

Hi

I'm getting warnings when I display the email settings of an Inbound Mailbox.

Warning: Cannot modify header information - headers already sent by (output started at /var/www/.../modules/InboundEmail/InboundEmail.php:1) in /var/www/.../index.php on line 500

Warning: Cannot modify header information - headers already sent by (output started at /var/www/.../modules/InboundEmail/InboundEmail.php:1) in /var/www/.../index.php on line 504

Warning: Cannot modify header information - headers already sent by (output started at /var/www/.../modules/InboundEmail/InboundEmail.php:1) in /var/www/.../index.php on line 508

When I open the file I don't see anything special. But when I diff the new one with the old (4.5.0b) version I get:

1c1
< <?php
---
> <?php
30c30
< * $Id: InboundEmail.php,v 1.126.2.4 2006/09/28 17:38:08 chris Exp $
---
> * $Id: InboundEmail.php,v 1.126.2.1 2006/09/11 23:29:58 awu Exp $



Where is " " coming from? What do I have to do to fix it?

[george_bbch]

Hi,

What's the exact size (in bytes), date and time stamp of your InboundEmail.php corresponding to 4.5.0c?

[simple]

In the zip file:

2006-09-28 10:56 71068 Bytes

CVS Tag:
$Id: InboundEmail.php,v 1.126.2.4 2006/09/28 17:38:08 chris Exp $

It's from the 4.5.0c patch.

[ruchida]

Where is " " coming from? What do I have to do to fix it?

Hi,

Your InboundEmail.php seems to have an extra byte (BOM?) in the 1st byte of the 1st line. Open it with a php editor and remove the byte, and save it.

[simple]

Thanks!

I've tried it with vi on the linux box and didn't see the extra byte. Using Zend Dev Env I was able to delete it.

[george_bbch]

In the zip file:

2006-09-28 10:56 71068 Bytes

CVS Tag:
$Id: InboundEmail.php,v 1.126.2.4 2006/09/28 17:38:08 chris Exp $

It's from the 4.5.0c patch.

Seems OK, but as ruchida already mentioned, the one on the Sugar installation may have been altered.

[mcssoftware]

I had the same issue after upgrade from 4.5.0b -->c - this fix worked. Thanks

[mch423]

Hi folks,

This is filed as bug #9394. We found the culprit and is fixed in D Release coming up shortly.

- Max

[florenceit]

I had ythis issue but did not have the stange byte in the begging ofg the file but in various places throughout. i started going through fixing them until i get to one point where its expecting a different oerator and i see no bad character there. im just waiting on patch D