Skip to content

Commit edb6205

Browse files
committed
Update 401 troubleshooting information
1 parent 019e7d6 commit edb6205

File tree

1 file changed

+29
-3
lines changed

1 file changed

+29
-3
lines changed

README.md

Lines changed: 29 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -168,9 +168,35 @@ mujmap cannot and will never be able to:
168168

169169
## Troubleshooting
170170
### Status Code 401 (Unauthorized)
171-
- [ ] Ensure that your mail server supports HTTP Basic Auth. *Fastmail does.* See #5.
172-
- [ ] Verify that you are using the correct username and password. Fastmail
173-
requires a special third-party password *specifically for JMAP access*.
171+
172+
If you're using Fastmail (which, let's be honest, is practically a certainty at
173+
the time of writing), you may have recently encountered errors with
174+
username/password authentication (HTTP Basic Auth). This may be caused by
175+
Fastmail phasing out username/password-based authentication methods, as
176+
described in [this blog
177+
post](https://jmap.topicbox.com/groups/fastmail-dev-beta/Tc47db6ee4fbb5451).
178+
179+
While this is objectively a good thing, and while it seems the intention was to
180+
roll this change out slowly, the API endpoint advertised by Fastmail DNS SRV
181+
records has almost immediately changed following the publication of this blog
182+
post, causing 401 errors in existing mujmap configurations. You have two
183+
options:
184+
185+
- Switch to bearer tokens by following the guide in the blog post. mujmap
186+
supports bearer tokens via the `password_command` config option in the latest
187+
`main` branch revision but not yet in a versioned release.
188+
- Remove `fqdn` from your config if it's set, and add or change `session_url` to
189+
explicitly point to the old JMAP endpoint, located at
190+
`https://jmap.fastmail.com/.well-known/jmap`.
191+
192+
If your 401 errors are unrelated to the above situation, try the following
193+
steps:
194+
195+
- [ ] Ensure that your mail server supports either HTTP Basic Auth or Bearer
196+
token auth.
197+
- [ ] Verify that you are using the correct username and password/bearer token.
198+
If you are using HTTP Basic Auth, Fastmail requires a special third-party
199+
password *specifically for JMAP access*.
174200
- [ ] Verify that you are using a `password_command` which prints the correct
175201
password to stdout. If the password command fails, mujmap logs its stderr.
176202
- [ ] If using Fastmail, check your login logs on the website for additional

0 commit comments

Comments
 (0)