x-scalix-Reason-Code: 143

[RyHD]

Community users are getting this error message when sending meeting invites.
It seems to be isolated to anyone who downgraded from premium to standard.
We are running 10.0 community.


Message could not be delivered to the following recipient:

xxx@xxx.com

because: The message could not be sent as the service level for your mailbox doesn't allow that operation.

Any thoughts?

[ScalixSupport]

As a standard user, it is not possible to schedule meetings with other users. This is one of the features that is available as a premium user. It is only possible to manage your own calendar as a standard user.

Cheers

Dave

[crazy_russian]

Hi,

Could you also check if you have mailbox limits set for the system or the user?

Cheers,
Yuri

[RyHD]

The meeting invites are sent via outlook 2003 ical format, and do not affect any group calendar, plus community to internet invites are working for people who were never premium users to begin with.

I guess what I am saying is, a community user, with their own unshared calendar, creates a meeting invite and sends it to someone else, be it community or internet. If they were once a enterprise uses, it kicks back that error, but not if they have always been a community user.

Also, there are no mailbox limitations set.

[RyHD]

After testing it seems this functionality does NOT work for users who have always been community.

The problem is, we have just lost one of the capabilities of Outlook 2003 because of an upgrade to scalix 10.0.

This was not an issue in 9.4.2.

[ScalixSupport]

So that I'm checking the right thing, is this happening when you send to internal users or external ones ?

Cheers

Dave

[RyHD]

The issue occurs sending to external or internal.
If a meeting invite is sent to a standard user from the outside world, they never receive it and a bounceback message is sent to the person sending the invite.

As i stated before, in 9.4, a standard user in pop3/smtp mode (MS Outlook) could send meeting invites to anyone but premium users, unless they disabled "send in Ical format", then enterprise users would recieve them as well.

[florian]

RyHD,

thanks for pointing this out to us; what you're experiencing is a unplanned-for side-effect of the iCal support we added to Scalix v10; so what actually provides you with more interoperability and functionality in most situations, limits you in this particular situation.

We'll have to look into this from a product and engineering perspective and will provide an update on our position in a while. Stay tuned!

Thanks again,
Florian

[RyHD]

Since this is going to be a wait and see issue, we have already begun to scale back down to 9.4.2. Unfortunately, this means that I am going to have to build a second mail server, as 10.0 and 9.4.2 mail store "/var/opt/scalix/" are incompatible. 700 users is going to take awhile, unless it's possible to do an LDAP synch. Is this possible?

Thanks,
RyHD

[mattc4u]

Hello,
Have you been able to provide a fix or a work around on this issue? I have been able to get it to work by making the sending and receiving user a "Premium User", but this will only work until I reach the available 25 premium users. Thanks for any advice you can give on this.

Matt

[JonathanC]

I too am very interested in this solution. Are there any updates? Thank you.

[florian]

I believe we've reached internal agreement that we want to allow iCal2iCal Scheduling for limited users, i.e. get back to the pre-10 behaviour.

Unfortunately, this requires a code change; we're currently aiming at a Patch update to Scalix 10 as a vehicle for that. This will resolve this and a few other minor issues. As always, our QA team has the final word on it, but I would currently expect this to be released in April.

Hope this helps,
Florian.

[cdclark]

I just got word of a similar error. Same error message:

Code: Select all

Message could not be delivered to the following recipient:

    cchok@mydomain.com

    because: The message could not be delivered to the recipient as the service level for the user's mailbox doesn't allow that operation

Supplementary Information:
    The message could not be delivered to the recipient as the service level for the user's mailbox doesn't allow that operation

Except in this case, there does not appear to be any calendar appointment involved. It was a HTML message sent from Outlook 2003.

The user is and always has been a Premium user on 10.0 CE

[ScalixSupport]

Which user ? The sender or the recipient ?

Cheers

Dave

[cdclark]

Which user ? The sender or the recipient ?

Cheers

Dave

Nevermind, I figured it out. I had the user's quota set lower than the actual mailbox size, but didn't have it set to reject messages when over the limit. So senders were getting this message but not a failure due to over the limit notification.