No proxy usage when caching mail content
Is your feature request related to a problem? Please describe.
I have a proxy configuration in config/config.php. This is needed for internet access. The mail apps try to fetch content to cache (I believe it's the 'proxy' public function). It's not using the global proxy settings It seems to work nethertheless but it generates alarms in the system.
Describe the solution you'd like
mail apps should be using the global proxy settings and never try direct internet access if configured
Describe alternatives you've considered
mail apps could have its own proxy settings or an option to disable caching.
Additional context
No response
Hello,
sorry for the late response. Do you still have this issue? I checked and the proxy feature does use the default Nextcloud HTTP client. This client does use the proxy settings of Nextcloud. This has been the case for many years, so I'm not sure where we don't respect the proxy settings.
Hello,
Better late than never :)
It seems a bit better but I'm still seeing some stuff.
So first my setup. I have a nextcloud on apache on a linux system (Rocky 9) with nft rules that blocks almost everything. Apache is not allowed to access the outside world. So I have setup a proxy configuration on nextcloud and a squid. I also have a bind DNS server (and it helps with the debug). Nextcloud is 29.0.7 and mail is 3.7.8
Now an example (it happens to all mails) So I have an email received from a domain When launching the mail app, I see a DNS request for that domain I also see right after the DNS log entry, an attempt from apache uid to open a connection to the IP address of that domain on port 443. When I select the email, by default the image are blocked. When I unblock everything is fine, requests go through the proxy as expected.
So the only thing that bother me is the https request to the domain that is made by apache directly without using the proxy. It seems to be done only once by email at the opening of the app. Even if I disconnect and reconnect, no new attempt is done.
It could be the feature that fetches favicons for the sender domain to show it as avatar
Hi there! It looks like this issue hasn’t seen much activity for a while and might need a bit more information to move forward. If we don’t hear back soon, we may close it to keep things organized. Thanks again for your contributions – we really appreciate it!