Correct, I am running a Cyrus-imap server.
And correct that this only happens to attachments that are Word.
I think I can even narrow it down to messages that came from Outlook where
Word was used as the editor and where Exchange was the mail server.
I have found the null in the document =00 and if I remove it from the
message on the Cyrus side everything works perfect.
The big question is how can I programmatically remove the null during
None of the current fixes in CVS fix the problem. I think the file where the
current fix is, is called Deliver.class
That fixes the NUL in the compose windows but not in the attachment.
So how do I strip the NUL from the attachment?
From: Per olof Ljungmark [mailto:peo@...]
Sent: Friday, April 29, 2005 5:37 PM
To: Tony Sciortino
Subject: Re: [SM-USERS] Problem with INBOX.Sent in all versions of SM
Tony Sciortino wrote:
> Hello everyone. Has anyone had a chance to look at this issue?
> Even though it seems there was a fix put out it is not working.
> -----Original Message-----
> From: squirrelmail-users-admin@...
> [mailto:squirrelmail-users-admin@...] On Behalf Of Tony
> Sent: Saturday, April 23, 2005 3:59 PM
> To: squirrelmail-users@...
> Subject: [SM-USERS] Problem with INBOX.Sent in all versions of SM
> I had posted yesterday about a problem I am having and someone responded
> saying the issue was fixed in the CVS version.
> I have the issue no matter what version, 1.44 1.45CVS 1.5.1devel
> There are a few messages that have an attachment that looks like this:
> Attachments: untitled- 4.4 k [ text/html ]
> When I try to forward this message to someone I get the error:
> ERROR : Could not append message to INBOX.Sent.
> Server responded: Message contains NUL characters
> Warning: Cannot modify header information - headers already sent by
> started at /opt/mail/functions/page_header.php:42) in
> /opt/mail/src/compose.php on line 444
> Does anyone have insight on this? It is really impacting the users I have.
Most likely your mail server is Cyrus-imap and it does not accept
messages containing the NUL character.
Does i happen to every message, if it does somethings is weird about
your SM installation.
If it happens to a few messages, it is probably attachments that has the
NUL's, I have seen this in MS Office documents and also many spams has them.