Cannot read message data Help!.

[TRACKS]

I am getting a lot of this but I am not sure what it really means.

# omshowlog -p 60

WARNING Internet Mail (Incoming ) 04.02.07 13:58:50
[OM.UX 1401] Cannot read message data.
<- tf_AppendRecord
<- mp_PutObjectFile
<- ux_InParseMimeFile
<- ux_InParseMimeContent
-> im_UnlinkItem
-> im_ItemRef2FName
<- im_ItemRef2FName
<- im_UnlinkItem
-> im_GetNewItemNum
<- im_GetNewItemNum
-> ux_InParseContentHeader
-> GetMailText
<- /build/11.0.2/src/bin/ux/ux_mimein.c:289[102,1401]
<- /build/11.0.2/src/bin/ux/ux_mimein.c:5080[102,1401]
<- /build/11.0.2/src/bin/ux/ux_in.c:4625[102,1401]
<- /build/11.0.2/src/bin/ux/ux_in.c:2013[102,1401]


WARNING Internet Mail (Incoming ) 04.02.07 14:20:12
[OM.UX 1401] Cannot read message data.
<- tf_AppendRecord
<- mp_PutObjectFile
<- ux_InParseMimeFile
<- ux_InParseMimeContent
-> im_UnlinkItem
-> im_ItemRef2FName
<- im_ItemRef2FName
<- im_UnlinkItem
-> im_GetNewItemNum
<- im_GetNewItemNum
-> ux_InParseContentHeader
-> GetMailText
<- /build/11.0.2/src/bin/ux/ux_mimein.c:289[102,1401]
<- /build/11.0.2/src/bin/ux/ux_mimein.c:5080[102,1401]
<- /build/11.0.2/src/bin/ux/ux_in.c:4625[102,1401]
<- /build/11.0.2/src/bin/ux/ux_in.c:2013[102,1401]


WARNING Internet Mail (Incoming ) 04.02.07 14:34:32
[OM.UX 1401] Cannot read message data.
<- tf_AppendRecord
<- mp_PutObjectFile
<- ux_InParseMimeFile
<- ux_InParseMimeContent
-> im_UnlinkItem
-> im_ItemRef2FName
<- im_ItemRef2FName
<- im_UnlinkItem
-> im_GetNewItemNum
<- im_GetNewItemNum
-> ux_InParseContentHeader
-> GetMailText
<- /build/11.0.2/src/bin/ux/ux_mimein.c:289[102,1401]
<- /build/11.0.2/src/bin/ux/ux_mimein.c:5080[102,1401]
<- /build/11.0.2/src/bin/ux/ux_in.c:4625[102,1401]
<- /build/11.0.2/src/bin/ux/ux_in.c:2013[102,1401]

[ScalixSupport]

Hi!

For the warning OM.UX 1401, this is what I get,

[root@subir-rhel4 ~]# omsolve -n OM.UX 1401
-------------------------------------------------------------------------------
Error Group: OM.UX Error Number: 1401

Cannot read message data.

The Scalix process that talks to Sendmail is out of step with Sendmail.
This could be caused by the Scalix and Sendmail versions being
incompatible. To check on the version of the Internet Mail Gateway
programs, type:

omvers -f /opt/scalix/bin/unix.in

(This may take a few minutes.)
To check the version of Sendmail, type

what /usr/lib/sendmail

Check with your support representative for any known incompatibilities
between Sendmail and Scalix.

Try the commands in the description above and reply to me with result of the same.

Thanks,
Subir

[ScalixSupport]

Hi!

For the OM.UX 1401 warning, we have a bug open http://bugzilla.scalix.com/show_bug.cgi?id=2866

Thanks,
Subir

[TRACKS]

# omvers -f /opt/scalix/bin/unix.in
unix.in 11.0.2.15

sendmail-cf-8.13.1-3.RHEL4.5

[TRACKS]

Why do I get this when trying to access the bug? I don’t even see it listed?

You are not authorized to access bug #2866.

[ScalixSupport]

Hi!

Done! now the bug should be visible, apart from this, I would request you to add a line
DEBUG_LOG=TRUE at the beginning of the file /var/opt/scalix/??/s/sys/smtpd.cfg and restart
smtpd using the commands below:

Code: Select all

omoff -wd 0 smtpd
omon smtpd

replicate the steps for incoming mails and see if you find any trouble in the logs generated
at /var/opt/scalix/??/s/tmp/smtpd-SMTP.log.

Thanks,
Subir

[sbyrne]

I'm seeing this same problem right now on my machine that runs FC5 with scalix version (11.1.0.10849-1.fc5).

My issue is that a message with an attachment larger than some arbitrary value (10 MB or so) will not get delivered and I see multiple warnings in my Internet Mail Gateway log that are like the following:

Code: Select all

WARNING Internet Mail (Incoming ) 09.25.07 14:10:24
[OM.UX 1401] Cannot read message data.
<- tf_AppendRecord
<- mp_PutObjectFile
<- ux_InParseMimeFile
<- ux_InParseMimeContent
-> im_UnlinkItem
-> im_ItemRef2FName
<- im_ItemRef2FName
<- im_UnlinkItem
-> im_GetNewItemNum
<- im_GetNewItemNum
-> ux_InParseContentHeader
-> GetMailText
<- /build/11.1.0/src/bin/ux/ux_mimein.c:289[102,1401]
<- /build/11.1.0/src/bin/ux/ux_mimein.c:5080[102,1401]
<- /build/11.1.0/src/bin/ux/ux_in.c:4625[102,1401]
<- /build/11.1.0/src/bin/ux/ux_in.c:2013[102,1401]

and the message is never delivered.

In my mind, that's not a warning, that's a severe error.

So, the question is: how do I fix this? Back when I was using Postfix for my mail relay, I *never* had these problems.

Please shed some light on this as it's a serious problem in our office (scanning a large document to an email address doesn't work).

-Sam

[sbyrne]

please...this is driving me nuts.

Does no one have these same issues? I find it difficult to believe...

The attachment is a pdf and it just happened *again*.

I need a work around for this or (better option) a way to solve it.

The problem is that a document that I scan into a pdf and email to my address never gets delivered. This is *bad* and it makes me despise scalix.

Help. please.

[Valerion]

I myself have not seen this (and I do send around large emails, including PDFs). For this I would suggest you contact Scalix Support and have them look at the issue. If it is a bug, they would try to fix it, or to give you a workaround. Scalix does charge for support, but not if the support call is due to a (verified) bug on their side.

[sbyrne]

I myself have not seen this (and I do send around large emails, including PDFs). For this I would suggest you contact Scalix Support and have them look at the issue. If it is a bug, they would try to fix it, or to give you a workaround. Scalix does charge for support, but not if the support call is due to a (verified) bug on their side.

I'm not sure what the deal is then. I just recently upgraded to FC7 and installed the latest release of Scalix to try to see if it's been resolved and am still having sendmail give me errors like unexpected EOM.

I tried to piggy back onto an older bug, but was told that we shouldn't open it up since it was old.

[sbyrne]

Since I'm too cheap to pay a thousand bucks or more to get help on this, I'm working around it for now (deliver the message to another email account running postfix only which accepts the message just fine and then use fetchmail to deliver it to the local scalix account). I don't have the patience or the time or (in this case) the money to try to wait around for an acknowledgement that this is indeed a problem. If Scalix is trying to provide a functional SMTP solution, then they damn well can't overlook a problem that's reported in which messages are not being delivered.

I know I should look at the code myself to see where the issue is, but I'm not really a developer (excuses excuses). I just need a little help from someone to say, yes, that is a bug and it seems to be located in module x or no, that is not a bug based upon your provided data. Unfortunately, I just don't have months to start wading through the source to try and locate the problem. I need to be able to scan documents to my scalix accounts *today* and count on the mail server not dropping the message.

This is rather disappointing for me as I really like Scalix; but I feel very uncomfortable about Scalix now that I've been ignored this long about this problem.

[kanderson]

A single support incident with Scalix is $300. It's not overly expensive. Scalix support is awesome. They will provide fast and accurate answers, and address problems base on priority. Having a server that won't process mail would be an extremely high priority.

The Forums, on the other hand, are a best effort machine. There are knowledgeable and experienced people here who will help as best as they can, but lets face it. I get paid for supporting clients. I can't spend all day on the forums, or I'd be bankrupt almost immediately. Scalix is the same way. Support that someone is paying for is understandably given a higher priority than the forums. Otherwise, People wouldn't pay for support every. Forum support is intentionally best effort and that's the norm for any software. If something is urgent, open a support case. If it isn't, then use the forum.

A server that's down is a support incident, in my view...

Kev.

[sbyrne]

A single support incident with Scalix is $300. It's not overly expensive. Scalix support is awesome. They will provide fast and accurate answers, and address problems base on priority. Having a server that won't process mail would be an extremely high priority.

The Forums, on the other hand, are a best effort machine. There are knowledgeable and experienced people here who will help as best as they can, but lets face it. I get paid for supporting clients. I can't spend all day on the forums, or I'd be bankrupt almost immediately. Scalix is the same way. Support that someone is paying for is understandably given a higher priority than the forums. Otherwise, People wouldn't pay for support every. Forum support is intentionally best effort and that's the norm for any software. If something is urgent, open a support case. If it isn't, then use the forum.

A server that's down is a support incident, in my view...

Kev.

Gotcha.

The problem is that the server is not actually "down". It simply is unable to finish delivery of certain messages that have large attachments (not all large attachments just some).

I'm completely aware that the forum is what it is, but when I found (what appeared to me) to be the same exact problem on bugzilla (http://bugzilla.scalix.com/show_bug.cgi?id=2866), I tried to bring attention back to the issue and was shot down. I'd be happy to pay 300 for an issue that appears to be unknown and is a possible feature request, but I'm still uncomfortable paying 300 for an issue that appears to not have been completely resolved from the first time it was raised.

Don't misunderstand, I appreciate Scalix for a lot of the neat features that it offers, but gee, sometimes I wish that simple stuff like this would *just work*.

[kanderson]

If nothing else, note in the bug that you're also experiencing the issue. That does two things.

First, it adds you to the list so you'll see when progress is made against it.

Second, it helps Scalix see that more than just one person is seeing the issue, which helps them gauge a priority for it.

Kev.

[sbyrne]

If nothing else, note in the bug that you're also experiencing the issue. That does two things.

First, it adds you to the list so you'll see when progress is made against it.

Second, it helps Scalix see that more than just one person is seeing the issue, which helps them gauge a priority for it.

Kev.

Dude. I don't mean to be a jerk, but did you actually look at that bug? If you did, then you'd have noticed that I did everything you suggested.

I really don't want to vent on you (especially considering I'm using Scalix for free), but here we go.

My experience with Scalix has been kind of strange. I've been using it since before build 10 (I don't remember the first build) and when build 10 rolled around, I installed it thought it was much improved over the old versions and thought I'd like to support the folks that are doing the work on it. I dug around in the site looking for a way that I could contribute money to the cause (buy a license, etc.) and couldn't find anything other than paying *large* amounts of money for enterprise licensing. I posted a message on the forum just kind of seeing if there might be a way for someone that has 5-10 users to contribute without ponying up for extravagant enterprise licenses. I never really got anywhere and even emailed back and forth with Scalix sales trying to get some more answers. Ultimately, I was told to just use the community version since I really didn't have enough users to make the license worth it.

Fast forward to now, where I'm being told that I now have to pay 300 bucks to re-open an issue that (IMO) matches the problems that I've been having.

You'll have to forgive me if I'm just a little bit peeved. When I want to pay I can't (or can't afford to pay enough) and when I think it's inappropriate, I'm being forced to pay...

I guess I'll just continue to work around it.