In general, is there a downside to turning on g_imap_status_stored? It defaults, of course, to off. Any ramifications of just turning it on? (We also have some users with large IMAP inboxes...)

Thanks...

Not really, it's fundamentally a problem with imap and pop protocol (which gmail mostly avoids) and how the clients happen to make use of those protocols.   Although make sure you have this setting turned on:

g_imap_status_stored "true"

there is also the setting: g_maildir_netwin to change the mailbox format completely,  but that's a drastic solution which I'm not very keen on to be honest, and only half fixes the problem because the email client is still going to be faced with a huge inbox that it has to keep making requests with.  I think it's much better to use the archiving features so the email client is not having to deal with the large number of messages regardless of the server load.

    ChrisP.



On 23/08/2016 10:34 a.m., surgemail-list@netwinsite.com wrote:

ChrisP,

Server load from large inboxes is a major issue for me. Is this not perhaps an architectural issue with SurgeMail? I never had load issues back in the old days with ComuniGate Pro, with large numbers of messages in users’ inboxes, and that was on much weaker hardware. Also, what about Gmail, where users are encouraged to leave everything in their inbox?

Be that as it may, I intend to start using g_inbox_archive. Is there a way to localize the folder names? E. g. I would prefer to name the Archives folder “Archiv”, Inbox “Eingang”, etc. for my German users.

Best,
Chris

Am 22.08.2016 um 23:04 schrieb surgemail-support <surgemail-support@netwinsite.com>:

You can just delete files, but surgemail will limit the number it shows to the user so as long as the total is still above that number it will keep showing the same number.

You can increase the number using these settings.

There is a pop limit:
    g_maildir_max "30000"
and an imap limit:
    G_IMAP_MAX_MESSAGES "200000"
(those are the defaults)

Rather than increasing those settings which will just make the user experience even worse as their email client has to keep scanning the same messages every day, and your server's load worse...  it's much better to tidy up the accounts with settings like:
    g_inbox_archive "365"
    g_sent_archive "365"
(or smaller, 90 days might be reasonable)
Which will archive messages older than 1 year to sub folders, Archives/YYYY/Inbox etc...

So the messages still exist, but won't be wasting resources every login.


    ChrisP.

On 23/08/2016 5:48 a.m., surgemail-list@netwinsite.com wrote:

i have several customers who use imap and have never deleted anything.

of course, this is my fault fo letting thsi happen, but that's immaterial :-)

i went into the web admin interface and deleted well over 1000 messages for one of these customers, and noticed two things:

1. the number 30001 never changed and

2. going to the customers mdir/new on the server i saw messages with dates (years) that i thought were deleted

what i'm wondering is, if i do deletes from the linux command line, what file(s), if any, would i need to update manually to keep everything in synch?

david camm
advanced web systems
keller, tx