Page 1 of 1
Corrupt messages in error queue
Posted: Wed Mar 07, 2007 3:41 am
by graemef
I am getting messages Corrupt queue. They are always files with attachments. This used to happen occasionally with some PDF's, but seems more common now I have installed a new server last week with the latest software.
OmShowLog shows messeges likes this
ERROR Internet Mail (Outgoing ) 03.07.07 14:24:28
[OM.UX 1168] TNEF gateway: MAPI message attachment SDOC1828.pdf not found in Tra
nsaction File
WARNING Internet Mail (Outgoing ) 03.07.07 14:24:28
[OM.UX 1531] Error in decoding file
<- tf_ReadRecord 44000 67
-> tf_GetINT32
<- tf_GetINT32
-> tf_ReadRecord
-> tf_GetINT32
<- tf_GetINT32
<- tf_ReadRecord 44000 67
-> tf_GetINT32
<- tf_GetINT32
-> tf_ReadRecord
<- tf_ReadRecord:NO
-> tnef_getPastRendData
<- tnef_getPastRendData
-> tnef_getPastRendData
<- tnef_getPastRendData
<- /build/11.0.2/src/lib/tnef/tnef_encode.c:692[102,1531]
WARNING Internet Mail (Outgoing ) 03.07.07 14:24:28
[OM.UX 3001] Failed to convert message to MIME format - moving message to ERROR
queue
The basic message is the same for all messages corrupted.
Any ideas ?
Posted: Wed Mar 07, 2007 5:56 am
by Richard Hall
This is due to a Scalix 11 bug in the TNEF routing of the Internet gateway, see:
http://bugzilla.scalix.com/show_bug.cgi?id=14870
This problem affects messages with attachments that use the TNEF flavour of the Internet gateway (typically Outlook messages to Exchange users). We have a fix for this now, and will be making it available in the near future.
Richard
Posted: Wed Mar 07, 2007 7:42 am
by graemef
Can I test it, this is stopping nearly all outgoing email from our company with attachments, including invoices etc. Also stops emails for people that have background bitmaps
Posted: Wed Mar 07, 2007 8:08 am
by Richard Hall
Hi Graeme,
Are all the recipients affected addressed via the TNEF (Outlook Rich Text) route?
What version of Linux are you running?
Richard
Posted: Wed Mar 07, 2007 12:07 pm
by kanderson
If you need an immediate quick fix, you can delete all of the TNEF routes. This will force them out MIME, which will work fine. HOWEVER, it will mean that things like meeting requests and such are broken when they go to an exchange 5.5 server.
Kev.
Posted: Wed Mar 07, 2007 7:12 pm
by graemef
Richard Hall wrote:Hi Graeme,
Are all the recipients affected addressed via the TNEF (Outlook Rich Text) route?
What version of Linux are you running?
Richard
How do I tell this, yes they would have all been sent using RTF format from outlook. I am running REL4 with all latest patches etc
Posted: Wed Mar 07, 2007 7:13 pm
by graemef
kanderson wrote:If you need an immediate quick fix, you can delete all of the TNEF routes. This will force them out MIME, which will work fine. HOWEVER, it will mean that things like meeting requests and such are broken when they go to an exchange 5.5 server.
Kev.
How can I disable the TNEF routes for the time being, I can live with the calendar thing if it will help me in the short term ?
Cheers
Posted: Thu Mar 08, 2007 5:50 am
by Richard Hall
graemef wrote:kanderson wrote:If you need an immediate quick fix, you can delete all of the TNEF routes. This will force them out MIME, which will work fine. HOWEVER, it will mean that things like meeting requests and such are broken when they go to an exchange 5.5 server.
Kev.
How can I disable the TNEF routes for the time being, I can live with the calendar thing if it will help me in the short term ?
Cheers
Probably the easiest way to do this is to list the Internet gateway details and then unset the TNEF route, and restart the gateway for the changes to take effect:
Code: Select all
> omshowux
MIME Mailnode : internet
TNEF Mailnode : internet,tnef
TNEF Domains :
Dist List Abbreviation Limit : 0
> omconfux -t ''
> omoff -d 0 unix
> omon unixThen when the problem is fixed you can reinstate the TNEF route:
Code: Select all
> omconfux -t internet,tnef
> omoff -d 0 unix
> omon unix
... but remember you will lose some of the Outlook message richness by unsetting the TNEF route.
Posted: Fri Mar 09, 2007 2:46 am
by florian
A fix for this issue is now generally available. Please see
http://www.scalix.com/forums/viewtopic.php?t=6515 for details.
Florian.