Service Router SERIOUS ERROR

[rudi]

Yes, I did. All scalix server are version 11.0.1

[florian]

so what was the outcome? do you have any xport.hold files? what do they look like, etc.? please provide all information also requested earlier in this thread.

Florian.

[rudi]

Ok, there is one file like the following in /var/opt/scalix/sn/s/xport.hold. But now I found out that the server scalix.mitte.wsd.bmvit.gv.at has an other name. We have changed the hostname. Can I delete this files now?

this post will be deleted:/var/opt/scalix/sn/s/xport.hold # cat 9999.1
Received: from scalix.mitte.wsd.bmvit.gv.at (scalix.mitte.wsd.bmvit.gv.at 192.168.202.5)
by this post will be deleted.scalix.via-donau.org (Scalix SMTP Relay 9.4.0.9)
via ESMTP; Mon, 07 Nov 2005 17:53:14 +0100 (CET)
Received: from localhost (localhost)
by scalix.mitte.wsd.bmvit.gv.at (8.12.10/8.12.10/SuSE Linux 0.7) id jA3C4r2Y019834;
Thu, 3 Nov 2005 13:04:53 +0100
Date: Thu, 3 Nov 2005 13:04:53 +0100
From: Mail Delivery Subsystem <MAILER-DAEMON@scalix.mitte.wsd.bmvit.gv.at>
Message-Id: <200511031204.jA3C4r2Y019834@scalix.mitte.wsd.bmvit.gv.at>
To: <scalix@this post will be deleted.scalix.via-donau.org>
MIME-Version: 1.0
Content-Type: multipart/report; report-type=delivery-status;
boundary="jA3C4r2Y019834.1131019493/scalix.mitte.wsd.bmvit.gv.at"
Subject: Returned mail: see transcript for details
Auto-Submitted: auto-generated (failure)

This is a MIME-encapsulated message

--jA3C4r2Y019834.1131019493/scalix.mitte.wsd.bmvit.gv.at

The original message was received at Thu, 3 Nov 2005 13:04:52 +0100
from localhost [127.0.0.1]

----- The following addresses had permanent fatal errors -----
<scalix@mitte.scalix.via-donau.org>

----- Transcript of session follows -----
554 5.3.0 unknown mailer error 1

--jA3C4r2Y019834.1131019493/scalix.mitte.wsd.bmvit.gv.at
Content-Type: message/delivery-status

Reporting-MTA: dns; scalix.mitte.wsd.bmvit.gv.at
Received-From-MTA: DNS; localhost
Arrival-Date: Thu, 3 Nov 2005 13:04:52 +0100

Final-Recipient: RFC822; scalix@mitte.scalix.via-donau.org
X-Actual-Recipient: rfc822; scalix@scalix.mitte.wsd.bmvit.gv.at
Action: failed
Status: 5.0.0
Last-Attempt-Date: Thu, 3 Nov 2005 13:04:52 +0100

--jA3C4r2Y019834.1131019493/scalix.mitte.wsd.bmvit.gv.at
Content-Type: message/rfc822

Return-Path: <scalix@this post will be deleted.scalix.via-donau.org>
Received: from scalix.mitte.wsd.bmvit.gv.at (localhost [127.0.0.1])
by scalix.mitte.wsd.bmvit.gv.at (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id jA3C4q2Y019830
for <scalix@mitte.scalix.via-donau.org>; Thu, 3 Nov 2005 13:04:52 +0100
Received: from scalix.mitte.wsd.bmvit.gv.at (root@localhost)
by scalix.mitte.wsd.bmvit.gv.at (8.12.10/8.12.10/Submit) with ESMTP id jA3C4qUe019829
for <scalix@mitte.scalix.via-donau.org>; Thu, 3 Nov 2005 13:04:52 +0100
Received: from this post will be deleted.scalix.via-donau.org (this post will be deleted.scalix.via-donau.org 192.168.200.12)
by scalix.mitte.wsd.bmvit.gv.at (Scalix SMTP Relay 9.4.0.8)
via ESMTP; Thu, 03 Nov 2005 13:04:52 +0100 (CET)
Received: from this post will be deleted.scalix.via-donau.org (localhost [127.0.0.1])
by this post will be deleted.scalix.via-donau.org (8.12.10/8.12.10/SuSE Linux 0.7) with ESMTP id jA3C5ujw016251
for <scalix@mitte.scalix.via-donau.org>; Thu, 3 Nov 2005 13:05:56 +0100
Received: (from root@localhost)
by this post will be deleted.scalix.via-donau.org (8.12.10/8.12.10/Submit) id jA3C5u0e016248
for scalix@mitte.scalix.via-donau.org; Thu, 3 Nov 2005 13:05:56 +0100
Date: Thu, 3 Nov 2005 13:05:56 +0100
From: Scalix User <scalix@this post will be deleted.scalix.via-donau.org>
Sender: scalix@this post will be deleted.scalix.via-donau.org
To: undisclosed-recipients:;;;@scalix.mitte.wsd.bmvit.gv.at;
Message-ID: <X00000000001d7d0.1131019492.scalix.mitte.wsd.bmvit.gv.at@MHS>
Subject: Encoded Scalix Transport Message
x-scalix-Hops: 1
MIME-Version: 1.0
Content-Type: text/plain;
charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

scalix-encoded-message

[florian]

well, if you don't need the message, you can certainly delete it. having consistent hostnames is always a good idea with scalix, though i don't think it causes this error.

may i also suggest that you open a case with scalix support if this is really a system down situation? this will give you more consistent response times.

cheers,
Florian.