Scalix Forums

hello all,

since yesterday i saw two delivery failures for username@mydom.com. The user exsists, domain is correct, and there are no other problems at the moment. Below find the error report.

Does anyone know what x-scalix-Reason-Code: 100 is..?

Error:

Final-Recipient: rfc822;username@mydom.com
Action: failed
Status: 5.1.1
x-scalix-Reason-Code: 100

Best!
mj

doesn't anybody have any ideas?

I have recreated the person's email address, and restarted the service router (multiple times) but I'm still getting these errors.

Is there an overview somewhere of all the x-scalix-Reason-Codes, their meanings and possible solutions..?

mj

Googling on Action: failed Status: 5.1.1 shows that this indicates the user is unknown.

What happens if you telnet to port 25 on your scalix host as follows:




Do you receive a reject message?

Where are you seeing the error?

Thanks,
Don

dear don and others,

I've tried this conversation, and it works perfectly. The address also exists in sac, there seem to be no problems, but AGAIN today I received a delivery notification like this:

Reporting-MTA: smtp; scalixhost.mydomain.edu
DSN-Gateway: dns; scalixhost.mydomain.edu

Final-Recipient: rfc822;ghazi@mydomain.edu
Action: failed
Status: 5.1.1
x-scalix-Reason-Code: 100

This all started happening after I made changes to the user's display name in sac.

Any ideas where else to look?

Ah, you've changed the user's display name. That's a key bit of information. Again I'll ask, where are you seeing these messages? In the ENU mailbox? Where are these messages originating? Within scalix or from outside?

Thanks,
Don

ok, here's what I found:

in /var/log/mail.info there were lines from sendmail & postfix/smtp for the NEW_DISPLAYNAME@ourdomain.org

That seems wrong, because the emailaddess of the user has not been changed at all. (I changed just the display name)

The errors I noticed came from internal mail messages. I tried the telnet localhost:25 conversation to actually send a mail, and it came through just fine.

So, not yet sure where the NEW_DISPLAYNAME@mydomain.org came from, and where postfix / sendmail have found that..?

What I did now: I have created an email alias for the user for NEW_DISPLAYNAME@mydomain.org, to see if the errors disappear. If they do, we know that that was the problem.

I would of course still like to know where postfix/sendmail would find that (wrong) information...

Thanks for helping so far.
mj

note: in the delivery errors, the correct email address is displayed. (the NEW_DISPLAYNAME@mydomain.org is just in /var/log/mail.info)

Yes, changing the display name has been problematic. Your best solution at this point is to edit /var/opt/scalix/sys/general.cfg and add:

SR_RESOLVE_MASK=8

That tells the service router to resolve on S/G/I/Q/OU1/OU2/OU3/OU4 rather than CN.

After you've made the change restart the service router.

Scalix 11 will handle display name changes better.

Regards,
Don

dear Don,

I have made the appropriate change in general.cfg, restarted the service router in administration console, and today again I received a delivery error for the user, even though the user REALLY exists:

Message could not be delivered to the following recipient:

username@mydomain.edu

because: Recipient name not found at destination

Reporting-MTA: smtp; mailserver.mydomain.edu
DSN-Gateway: dns; mailserver.mydomain.edu

Final-Recipient: rfc822;username@mydomain.edu
Action: failed
Status: 5.1.1
x-scalix-Reason-Code: 100

It appears that most of the messages arrive without problems, just sometimes they generate this failure. If it helps: failures I have seen recently are messages sent by the internal network users to multiple (internal) recipients.

Is there any other place to look, or certain log files to examine?

Are the failures coming from senders that are using outlook? The may need to delete the user with the changed name out of their address cache. This can be achieved by hitting the delete button when their name pops up when addressing.

Thanks,
Don

This would basically mean: send an email out to all our users, requesting them to do delete that address from their cache with a 'complicated' procedure.
(nota bene: all this, even though the email address in fact hasn't even been changed..!)

NOT nice.

really hope that this behaviour is improved in scalix 11.

Is there a time after which the outlook address expires automatically, or will this error stay in our the system eternally??

Since I stumbled across this just today, here's what I did.

Check the users entry in the SYSTEM directory using omsearch -e cn='username'.

Compare the output of that search with omshowu -n 'username'.

If the CN's don't match, you will get an error 100. To make them match, use ommodent to manipulate the SYSTEM directory entry to match what is in the userlist.

Cheers,

Sascha.

dear sascha,

the errors seem to have disappeared 'automagically'. I've checked output of those two commands, and CN's were the same. (when I checked, before they could have been different, who knows..?)

Anyway, all seems to work now, let's hope it stays that way.

Thanks for looking into this.

Mourik Jan