Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[mu4e bug] User-Agent header not set #2750

Closed
3 tasks done
manphiz opened this issue Aug 28, 2024 · 1 comment · Fixed by #2751
Closed
3 tasks done

[mu4e bug] User-Agent header not set #2750

manphiz opened this issue Aug 28, 2024 · 1 comment · Fixed by #2751
Labels
bug mu4e specific for mu4e new

Comments

@manphiz
Copy link
Contributor

manphiz commented Aug 28, 2024

Describe the bug

It looks like mu4e doesn't set User-Agent header anymore. It used to do that when I was using 1.8.x. I stopped using it for a while and started trying it again since 1.12.5 and I can no longer see User-Agent being set. I suspect this may be happening for earlier versions as well.

How to Reproduce

Sending a mail and show all headers, and there is no User-Agent set.

Environment

Debian Linux stable (Bookworm)
Emacs 29.4
mu4e 1.12.6

Checklist

  • you are running either an 1.10.x/1.12.x release or master (otherwise please upgrade)
  • you can reproduce the problem without 3rd party extensions (including Doom/Evil, various extensions etc.)
  • you have read all of the above

Possible Cause

'User-Agent is included in the draft header when message-newsreader is set[1]. However, the only place that it's being set is at [2] where it's let-bounded, so it has no effect on the code at [1].

[1]

,(when message-newsreader 'User-Agent)

[2]
(message-newsreader mu4e-user-agent-string)

@manphiz
Copy link
Contributor Author

manphiz commented Aug 28, 2024

I have a tentative fix at #2751, though I'm not sure whether this is the best way to do this. Please advice. Thanks!

@djcb djcb closed this as completed in 411407f Aug 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug mu4e specific for mu4e new
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant