Why developers not want to integrate getmail with imap-idle to mailcow? I really need this. Info from github pages is useless, but some person took about working solution. But without more info.

Why?
I need fast fetching mails from external servers. Ok, in mailcow is solution for this - but when i set check every 1 min then remote server block account because mailcow solution get a lot of data and i exceed free plan. This is not never happen before - now i have fetchmail in iredmail with 1 min checks and works well.
Why 1 mins check is bad? Because now is a lot pages with 1 min valid registration codes - i can handle it with imap-idle - no way to manually fetch in mailcow.

So - any WORKING tutorial to integrate mailcow with getmail or any reason why not?

2 years later

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!

13 days later

Hi. I use getmail from years. Generally works, but when i get a big mail (30MB) then getmail stop fetch mails. No errors in logs, restart not work, ewrything is as usual but not fetching mails. I need to login via web to mail provider, delete big message, restart getmail and all other mails has been synchronized. There is any option to repair this behavior?

So problem found, strange that I have never noticed this myself.
The problem is not caused by the script, but by the docker compose settings “mem_limit: 100m” and “mem_reservation: 20m”.

Please test.

christianbur/getmail62bbc70

docker stats still show memory limit 100MiB with and without memory_limit directive. When i write eg. 500m - still show 100MiB

3afa19210d64 getmail-getmail-1 0.04% 12.61MiB / 100MiB 12.61% 32.7kB / 9.1kB 3.75MB / 0B 5

30MB mail is still not fetched, is only marked as read.

How i test. I send to a Gmail account a mail with 26MB attachement. This is enough to see problem.

It now works for me with 30 MB mails.
The settings are probably not working for you yet, you have to restart the container (build a new one to be sure).

  • change docker-compose.yml
  • docker compose build –no-cache && docker compose up -d && docker compose logs -f

Ahh, You have right! I restart container, without rebuild it. Now works!

No one is typing