Can Someone Please guide me about what to change or how to increase this process_limit?
I have been stuck here for quite some time now. IF anyone could help, that would be extremely relieving for me.
Thanks in Advance

  • You could try to use the extra.conf as described here:

    https://docs.mailcow.email/manual-guides/Dovecot/u_e-dovecot-extra_conf/

    Create the file and add this block (untested):

    service imap {
  executable = imap
  user = vmail
  vsz_limit = 1G
  process_limit = 2048
}

Have something to say?

Join the community by quickly registering to participate in this discussion. We'd like to see you joining our great moo-community!

esackbauer
First of All, I was expecting you to reply to this. Thank you for your time. I respect your valuable time and will try not to waste it.

And yes, I am uploading my email accounts onto a platform which creates a connection to my smtp server and I upload the accounts in bulk, so they create the connection simultaneously. Is there any way i can increase the connection limit?

My server has plenty of resources, it has 64GB Ram and 12 Dedicated cores running at 4.2GHz each.

Currently, I am testing their service so I need to increase this limit as much as I can.

    You could try to use the extra.conf as described here:

    docs.mailcow.email Icon Customize/Expand dovecot.conf - mailcow: dockerized documentation

    docs.mailcow.email Icon docs.mailcow.email
    Customize/Expand dovecot.conf - mailcow: dockerized documentation
    None
    docs.mailcow.email

    Create the file and add this block (untested):

    service imap {
  executable = imap
  user = vmail
  vsz_limit = 1G
  process_limit = 2048
}

      DocFraggle Thanks a lot. It was a huge help. I will continue this if I the issue still persists.

        • e-d-i-t

            Moolevel 0
          • Post #6
          • Edited

          @DocFraggle You probably answered my totaly different question too…
          I’m 6 months hunting and testing for a decent replacement of Zimbra 8 OSE, tried numerous community editions to just find out it either lacks documentation, looks pretty and doesn’t work or does work and unmanageble.

          Then today,.. I saw the demo of Mailcow, knew about it but walked away from anything docker-related.
          Specifically because I have a lot of tuning in either postfix/dovecot/cyrus/httpd configs that are not available thru any webbased menu.

          Knowing that poking directly in containers will end up with back-to-default once restarted.

          Then you come up with this answer to customize/expand a certain config.
          So there is hope!

          Although the admin panel of mailcow seems to give me (almost) ALL I ever wanted, if it is “almost” then there is probably an escape in this way ;-)

          Thanks

          [unknown] I hope btw SOGo will fix my reported bug, because that is still the one withholding me from switching mailserver (Basic HTML-stuff, BODY-tag missing in any message, which renders badly in some clients when a BASE64 image is involved in the message)

          I hope btw SOGo will fix my reported bug, because that is still the one withholding me from switching mailserver (Basic HTML-stuff, BODY-tag missing in any message, which renders badly in some clients when a BASE64 image is involved in the message)

            No one is typing