thunderbird / thunderbird/thunderbird-android
K9 does not appear to respect system HTTP proxy settings
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 14k
- Forks
- 2.8k
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 57
Description
Checklist
- I have used the search function to see if someone else has already submitted the same bug report.
- I will describe the problem with as much detail as possible.
App version
6.602
Where did you get the app from?
F-Droid
Android version
LineageOS 20.0
Device model
XQ-AS72
Steps to reproduce
- Manage a WiFi connection to add an HTTP proxy
- Attempt to sync with K9
- Message retrieval fails silently (no error message)
- Attempt to compose an email
- Receive the error `GaiException: android_getaddrinfo failed: EAI_NODATA (no address associated with hostname)
Expected behavior
K9 should follow system proxy settings and pass through the set HTTP proxy. Note that this is not related to #980 (as this is a system HTTP proxy, not a proxy set within the app itself), though there may be some overlap in the fix.
Actual behavior
Messages are not retrieved and emails cannot be sent.
Logs
I've snipped a few things from the logs (namely a bunch of account information for my non-gmail accounts), so they may not line up perfectly.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the attached k9mail-logs.txt and reproduce the failure using a WiFi HTTP proxy on LineageOS 20.0. Trace the sync and compose network paths to determine where the system proxy is bypassed; done means messages sync and email can be sent through the configured proxy without the reported address error.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- android, kotlin
- Domain
- mobile, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100