x-scalix-Reason-Code: 5

[ScatterBrain]

I sent an e-mail from home to the office just now. The office is running Scalix 9.2.1, my home is running a Postfix mail server of my own concoction. My server sent the e-mail, Scalix picked it up and then denied delivery. What I got back was this:

Code: Select all

Original-Envelope-ID: 1131067673.12765.6.camel@enterprise.nesbitt.local
Reporting-MTA: smtp; concorde.nesbitt.local
DSN-Gateway: dns; concorde.nesbitt.local
Arrival-Date: Thu, 3 Nov 2005 20:27:59 -0500

Final-Recipient: rfc822;bMcGregor@nesbittengineering.com
Action: failed
Status: 5.3.0
x-scalix-Reason-Code: 5

Now, there is a user, mailbox and address for bmcgregor. In fact, he gets e-mail every day through it. So why wouldn't my e-mail go through to him tonight?

[ScalixSupport]

This appears to be a "transient error"...

Is this repeatable? Have you tried sending the message again? Have you tried other clients?

Let me know,

Matthew
Support

[infohenry]

I also experience this issue. I have a test server with scalix community edition which I am sending to and get the following error response when sending from another account on the scalix server.

Note that the email address sent to was a new email alias created. Once about 30 minutes elapsed then the error cleared up. I beleive the alias/account may need to propagate internal to the scalix server prior to not giving this error. Sending several messages returned the same results in the first few minutes.

Message could not be delivered to the following recipient:

<email address>
because: A mail transport failure occurred
Supplementary Information:

Failed to load any MDB driver

Reporting-MTA: smtp; <smtp server>
DSN-Gateway: dns; <smtp server>

Final-Recipient: rfc822;<email address>
Action: failed
Status: 5.3.0
x-scalix-Reason-Code: 5



Subject:
test
From:
<sender>
Date:
Tue, 3 Jan 2006 11:17:32 -0500
To:
<email address>

[infohenry]

continuation...

but the error occurs consistently when sending from scalix server to external addresses, not sure why, any assistance appreciated

Message could not be delivered to the following recipient:

<external recipient>

because: A mail transport failure occurred


Supplementary Information:



Failed to load any MDB driver




Reporting-MTA: smtp; <scalix smtp server>
DSN-Gateway: dns; <scalix smtp server>

Final-Recipient: rfc822;<external recipient>
Action: failed
Status: 5.3.0
x-scalix-Reason-Code: 5



Subject:
test message from hc
From:
<scalix server email address>
Date:
Tue, 3 Jan 2006 11:58:34 -0500
To:
<external recipient>

test

[florian]

Now, outgoing email uses sendmail on a Scalix server; the errors reported somehow come from the sendmail stack.

Can you post an extract of your /var/log/maillog file at the time of error? This should contain more useful information than the actual Non-delivery-notifcation that we're looking at here.

Thanks,
Florian.

[ScalixSupport]

Failed to load any MDB driver

This error is a different one from the the original post and doesn't look like a Scalix error that is being generated. Unfortunately, the SMTP RFC (2821, section 4.2.1) shows that 5.3.0 is a rather generic reply code.

I have a couple of questions:

1. Is the SMTP server that you obscured, the same name as your Scalix server
2. What client are you reading the non-delivery in ? Is it Outlook ?
3. If you are using Outlook, are you running using offline folder synch ?

The reason I ask about offline folder sync is that we do not use MDB on the server so this, on the face of it, looks to be generated from another server.

Cheers

Dave

[binarynomad]

We have an (internal) user who is no longer recieving email, I am including external and internal attemtps to email the user (the names have been changed to protect..etc)

==================
EXTERNAL ATTEMPT
==================

Message could not be delivered to the following recipient:

asmith@company.com

because: A mail transport failure occurred
Original-Envelope-ID: 90CBE9CE-7D18-4314-8DC2-D2E05BE5A691@ex ... ompany.com
Reporting-MTA: smtp; email-svr.internalnetwork
DSN-Gateway: dns; email-svr.internalnetwork
Arrival-Date: Mon, 23 Jan 2006 13:17:03 -0800

Final-Recipient: rfc822;asmith@company.com
Action: failed
Status: 5.3.0
x-scalix-Reason-Code: 5

From: John Doe <John@externalcompany.com>
Date: January 23, 2006 1:31:02 PM PST
To: "Smith, Alex" <asmith@company.com>
Subject: test from external

==================
INTERNAL ATTEMPT
==================

Message could not be delivered to the following recipient:

asmith@company.com

because: A mail transport failure occurred
Reporting-MTA: smtp; mail-svr.internalnetwork
DSN-Gateway: dns; mail-svr.internalnetwork

Final-Recipient: rfc822;asmith@company.com
Action: failed
Status: 5.3.0
x-scalix-Reason-Code: 5

From: "Doe, John" <bDoe@company.com>
Date: January 23, 2006 1:22:49 PM PST
To: "Smith, Alex" <asmith@company.com>
Subject: test

[ScalixSupport]

Hi. Since this is actually a sendmail error, either you have the SMTP Relay configured with SMTPFILTER=TRUE or Scalix can't find the address "asmith@company.com" in it's directory. Assuming it's the former, can you open a shell window and type:

Code: Select all

sendmail -bt
> 3,0 asmith@company.com

if the last line it returns is something like this:

Code: Select all

parse            returns: $# scalix $@ company $: asmith < @ company . com . >

then the name is in the Scalix directory. However, if it returns something more like this:

Code: Select all

parse            returns: $# local $: asmith

or

Code: Select all

parse            returns: $# relay $@ smarthost . company . come $: asmith < @ company. com . >


then the problem is the address asmith@company.com isn't defined in Scalix. Trying typing:

omsearch -e cn=*|grep -i asmith@company.com

and see what is returned.

Thanks,
Rachel

[josephhammerman]

Thanks for you r prompt reply Rachel. Here is the ouput generated by Sendmail in terst mode:

sudo /usr/lib/sendmail -bt
ADDRESS TEST MODE (ruleset 3 NOT automatically invoked)
Enter <ruleset> <address>
> 3,0 mfong@mobitv.com
canonify input: mfong @ mobitv . com
Canonify2 input: mfong < @ mobitv . com >
Canonify2 returns: mfong < @ mobitv . com . >
canonify returns: mfong < @ mobitv . com . >
parse input: mfong < @ mobitv . com . >
Parse0 input: mfong < @ mobitv . com . >
Parse0 returns: mfong < @ mobitv . com . >
ParseLocal input: mfong < @ mobitv . com . >
ParseLocal returns: mfong < @ mobitv . com . >
Parse1 input: mfong < @ mobitv . com . >
Parse1 returns: $# scalix $@ any $: mfong < @ mobitv . com . >
parse returns: $# scalix $@ any $: mfong < @ mobitv . com . >

Here is the output of omsearch -e cn=*|grep <username>@<companydomain>:

S=Fong/G=Malina/OU1=eme-mail01/OU2=corp/CN=Fong, Malina/INTERNET-ADDR="Fong, Mal ina" <mFong@mobitv.com>="Fong, Malina" <Malina.Fong@mobitv.com>="Fong, Malina" < mFong@idetic.com>/ENTRY-TYPE=1/UL-AUTHID=mfong/UL-CAPS=6/UL-CLASS=Full/PARENT-DL =8672=8832=9216=10112=7936

so according to these two tests, if I understand your test criteria, everything appears to be correctly configured. This users mail was working fine until approximately four days ago (counting the weekend).

[ScalixSupport]

Hi Joseph,

Hmm... that looks correct. Try stopping and restart local delivery and see if that fixes it:

Code: Select all

omoff -d0 ld
omon ld

Thanks,
Rachel

[josephhammerman]

Again, thank you for you prompt reply Rachel.

I followed your steps, and it briefly returned the users mail queue to a functional state. Less then half an hour later, the queue is once again broken. Furthermore all the mail that is directed to this user while the queue is in the current state is dissappearing, as far as I can tell. I am going to HUP the local delivery deamon again. In the meantime, could you please advise us with additional troubleshooting steps? Thank you!

[ScalixSupport]

Hi Joseph,

You actually have an open incident with Support that may be related to this. I'm going to send a reply to the case holder on your end (Brian) and see if we can get ssh access to your server to take a look around.

Thanks,
Rachel

[ScalixSupport]

Hi Joseph,

Just a follow-up to close this thread. It turned out that the user had a rule that was filtering mail to a specific folder. There was actually a duplicate folder, which appeared to be the problem, but after further testing, it appears that one of the two folders had some type of corruption that was causing Local Delivery to hang.

The solution was to remove the folder.

Thanks,
Rachel