The recipient's Inbox is full - but isn't.

Discuss the Scalix Server software

Moderators: ScalixSupport, admin

rogueind

The recipient's Inbox is full - but isn't.

Postby rogueind » Mon Jul 02, 2007 11:08 am

I have an enterprise license user using outlook, that when anyone sends mail to, the message bounces with:

The recipient's Inbox is full - no more messages can be delivered' [OM 9347]


I ran a

Code: Select all

omscan -Avfx -U "User Name"


No errors were reported, and a total mailbox size of 115998KB was reported. I check the user's quota, and that is set to 150MB. (Using AD integration for all users). I tried pushing up the quota and re syncing the directory, but that didn't have any effect on it.

If there are any logs thats would be useful, please let me know.

Any Ideas?

LHD-Tech
Posts: 74
Joined: Tue Feb 20, 2007 1:25 pm
Location: Lompoc, CA
Contact:

Postby LHD-Tech » Mon Jul 02, 2007 1:50 pm

Did you try emptying the waste basket?

pcrock
Posts: 51
Joined: Wed Mar 07, 2007 7:24 am

Postby pcrock » Wed Jul 25, 2007 10:03 am

exactly the same just started for me and I've no idea how to fix it. There is no limit set on the mailbox size but it still rejects. I've set it to not reject but it's still not accepting mail.

What process looks after this and how can I fix it. This is one of the most important mailboxes we have that this is failing on.

Phill

mikethebike
Posts: 566
Joined: Mon Nov 28, 2005 4:16 pm
Location: England

Postby mikethebike » Wed Jul 25, 2007 10:34 am

is there any entries in the fatal log (~openmail/logs/fatal)?
How many mails are there in the user's Inbox? (omtidyu -B -u username -i 0)

Mick

pcrock
Posts: 51
Joined: Wed Mar 07, 2007 7:24 am

Postby pcrock » Wed Jul 25, 2007 11:37 am

doing an /etc/init.d/scalix restart fixed it, but I need to know what kicked it off.

Fatal has one of these for every mail to the box (i've cut our domain off)

ERROR Local Delivery(Local Delivery) Wed Jul 25 15:07:39 2007
[OM 7748] No more items can be added to the Inbox for support/scalix.
Pid of logging process: 18240
Current errno value: 2
Last Msg Id: 12597349.631185372457935.JavaMail.root(a)

Omtidyu gives this

[root@scalix ~]# omtidyu -B -u "support" -i 0
Deletable items for 'support /scalix/CN=support'

InTray: 5 messages

Folder 'Old': 8 items

Folder 'InProgress': 63 items

The entire mailbox is about 200mb and I specifically made sure this box has no limit and does not reject mail as it's that important.
I must admit I'm getting a bit fed up with Scalix now, I seem to be getting too many random errors and the log files give you no idea what's wrong.

mikethebike
Posts: 566
Joined: Mon Nov 28, 2005 4:16 pm
Location: England

Postby mikethebike » Thu Jul 26, 2007 5:47 am

pcrock,

I would normally expect this to occur if there were a large amount of items in the Inbox, and would get "container extension full" errors in the fatal log.
Even after clearing out the Inbox, you would normally have to run an omscan in fix mode on that one mailbox.

Check the size of the 0000001 file in the users "g" directory (omshouw -n support -G)...if its significantly larger than other user's 000001 file, that may be the issue.

I would still be tempted to run "omscan -U support -Avfx" for that user to see if any errors come up.

Mick

pcrock
Posts: 51
Joined: Wed Mar 07, 2007 7:24 am

Postby pcrock » Thu Jul 26, 2007 7:01 am

Mike,

Thanks for that, found it and it's a whole 92k, less that a few other users.
I ran omscan on it yesterday and it came back clean.

Still stumped!

Phill

mikethebike
Posts: 566
Joined: Mon Nov 28, 2005 4:16 pm
Location: England

Postby mikethebike » Thu Jul 26, 2007 10:53 am

Phill,

ok, looks like the container size is not an issue.
I assume there is no help when you do "omsolve -n om 7748" and "omslove -n om 9347" (sorry, don't have a system in front of me)?

If this happens again, I would be tempted to increase the event logging level:

omshowlvl

omconflvl local 11

Wait for the error to occur, then do

omshowlog -p 5 -s local -l 11 > /tmp/phill.txt

look at the man pages for omconflvl and omshowlog for more info

You can look at that file and see if it gives any more useful information.

Mick

rogueind

Postby rogueind » Tue Jul 31, 2007 11:15 am

Shy of restarting "all" the scalix services (not sure which one would have to be singled out) I've found that if i force a logoff of the user, then run omscan -U name -Avfx, and then send a message, the error clears.

Code: Select all

omshowu -n "full name"
System Login : 55279


then

Code: Select all

ps auwx | grep 55279


Get the pid and then run:

Code: Select all

kill <pid>


then

Code: Select all

omscan -U "Full Name" -Avfx


and it seems that works.


Return to “Scalix Server”



Who is online

Users browsing this forum: No registered users and 3 guests