2025-01

EETNyx · 24 Jan

As I undestand it, if you got Solr enabled before than it’s safe to use new Flatcurve because it use less RAM but more CPU when (re)indexing is running and more HDD when indexing is done.

From what i saw so far i believe you are ok if you leave 1 thread for FTS that is default (I do assume you does not have more than 100 active users,…)

SteffnVo · 25 Jan

The update worked. Later, I set SKIP_FTS=n and indexed a mailbox. Now, I somehow have the problem that when I delete an email (IMAP) in the Mac Mail app, it immediately reappears. However, deleting works via webmail and on my phone (ActiveSync). Do you see this issue too? Switching SKIP_FTS back to y doesn’t solve the problem either.
OK. The solution was to new re-add the mailbox in the Mac Mail App.

EETNyx · 25 Jan

SteffnVo
In your case I would suggest to extend Dovecot logging something like this /opt/mailcow/data/conf/dovecot/extra.conf

plugin {
  mail_log_events = delete undelete expunge save copy mailbox_create mailbox_delete mailbox_rename
  mail_log_fields = uid box msgid size from subject
  mail_log_cached_only = no
}

than search your Dovecot logs if your Mail app send correct commands to Dovecot to manipulate your messages

EETNyx · 26 Jan

ETNyx

Btw I let it run some time and on low memory system (6GB) it’s decent memory usage drop, I would tell now you can make very small 4GB instance for few user just fine :-)

DocFraggle · 27 Jan

Just did the update. I really don’t understand what the Mailcow team did with the SKIP_FTS parameter

So the update script set SKIP_FTS=y which, in my understanding disables FTS per default now? But FTS still works for me in SoGo!?

Why would you disable FTS automatically if the old parameter SKIP_SOLR wasn’t set to ‘y’?

EDIT: OK, just saw this info box in the blog

⚡🐄 Janmooary 2025 Update | The Update which changed the Full-text search (and which kicked out Nextcloud)

mailcow: dockerized - Blog

⚡🐄 Janmooary 2025 Update | The Update which changed the Full-text search (and which kicked out Nextcloud)

Danger This mailcow Update contains critical changes to a few components. Please create a backup and safe your configs before updating. Moohoo everyone We used our holiday break to deliver you a new update right infront of your doorstep. As announced, this update continues a brand new Full-text

Info
After the mailcow update to 2025-01 and the switch to Flatcurve, FTS will be disabled for safety reasons automatically. If you used FTS before or want to try it out, you have to switch the variable SKIP_FTS from y to n and restart mailcow with docker compose up -d afterwards.

DocFraggle · 28 Jan

ETNyx it’s decent memory usage drop

Not that decent for me, but ~ 8% down. Still nice

EETNyx · 28 Jan

DocFraggle
Yes, guess your 100% is >= 12GB RAM?

Did you observe any CPU spikes like blog post mentioned? I’m almost flat 0-2% using 12 CPU threads

DocFraggle · 28 Jan

I’m running a 8-core VM with 16GB RAM. Just had a look, even CPU usage went down since yesterday

Ganzjahresgriller · 31 Jan

I just installed the update. Everything is working as it should. Many thanks to the Mailcow team

esackbauer · 31 Jan

Same here, no problems at all.
Waiting for the LDAP/OIDC authentication to finally arrive

Kkadybee · 6 Feb

Unfortunately for me it didn’t go so well :-(
First thing I noticed that the update downloads were much slower than normal - even down to around 200kb/s;
there were no errors during the update process but Mailcow failed to start all services.
I couldn’t access the web admin page and smtp was failing - yet I could see IMAP/POP was seemingly OK:

UPDATED - I found out the following day that the reason it didn’t go well was because GitHub was having severe network issues that evening as i was running the update! Bad timing on my part :-(
I’ve just run the update again and all went well.
Thanks to the Devs and all involved with Mailcow.