MEPOCS Outbound Queue Item Max Age

[rfwilliams777]

I am getting notifications with what is said in the subject. I have upped the limit in the registry from 1236 to 1368. I know there is an OLD thread about this, but I am experiencing this issue. I do not know if I resolved anything by doing this or if there is something else I should adjust. Below is the error messages I am receiving via email (these are status reports from the server).
MEPOCS Outbound Queue Item Max Age

MEPOCS appears to be having difficulty processing the outbound queue.

Parameters
----------
Violated Threshold: Maximum Value
Violated Threshold Value: 00:20:00
Value: 00:20:27 (20.5m)

I am using ME 8.5 (which this version is in Beta right now).

[rfwilliams777]

I am still having an issue with this. It doesn't seem to affect all accounts and it doesn't seem to be all the time, but I do get the warnings a little too often to just ignore it when I never got them before. Ent 8.5 beta

MEPOCS Outbound Queue Item Max Age

MEPOCS appears to be having difficulty processing the outbound queue.

Parameters
----------
Violated Threshold: Maximum Value
Violated Threshold Value: 00:20:00
Value: 00:47:47 (47.8m)

[kiamori]

This is still a thing, did anyone ever find a way to update this value yet?

Violated Threshold Value: 64

Every day, at least 50 times a day.

[aremdee]

Well I'm now getting this. It has been caused by a customer using IMAP on their mobile phone inadvertently moving the inbox to deleted then back again. They now have 70GB in their inbox and wont let me delete anything.

Wondering if there is an easy solution to clearing the inbox of duplicates etc.

Many thanks
Roger

[aremdee]

Not sure what is happening but I'm now getting this once a day. Can someone give a heads up as to what logs to look in and what to look for to find the culprit please. I know the previous cause but this time it isn't that I don't believe.

[rfwilliams777]

What version of MailEnable are you using? I sent this issue back in 2014 with a much older version of ME. I would recommend upgrading to the newest version and release.

[aremdee]

I know you started this thread. I'm using version 10.45 which I believe is the latest. I'm unsure if this issue is being caused by a customer or something else as it is happening regularly.