![Thunderbird logo](https://assets-prod.sumo.prod.webservices.mozgcp.net/media/uploads/products/2024-02-12-07-36-53-599028_1.png)
Thunderbird RSS subscription not allowing add feed
Thunderbird v 115.6.1.0esr (64-bit) currently using 50+ feed subscriptions with very little problems:
https://audioboom.com/channels/5114286.rss cannot be added. Add under Subscribe results in "The feed URL is not Authorized" error message.
I think this is a problem on the audioboom side but they insist I ask here.
Please see attachment.
所有回复 (8)
Hi, Strange I just added it to my TB and got all the 500 elements loaded :) If this continues, there is a helpful discussion here about a similar problem: https://bugzilla.mozilla.org/show_bug.cgi?id=1803739#c5 and here https://support.mozilla.org/en-US/questions/1166672
由Bogomil Shopov - Бого于
See https://meta.stackexchange.com/questions/382237/valid-rss-feed-url-is-not-authorized-in-thunderbird
You should check your Thunderbird user agent string.
Bogomil Shopov - Бого said
Hi, Strange I just added it to my TB and got all the 500 elements loaded :) If this continues, there is a helpful discussion here about a similar problem: https://bugzilla.mozilla.org/show_bug.cgi?id=1803739#c5 and here https://support.mozilla.org/en-US/questions/1166672
OK: The first link starts with a suggestion: "If you set preference dom.security.secFetch.enabled to false, https://feeds.feedburner.com/uncrate works again. I'm not sure whether that is a good fix or workaround. Mozilla implemented those headers in bug 1508292 and TB also sends them (apparently)." and ends with a message saying the problem as been fixed.
- So, I do not have the experience to know what this means (or how to do it). - If the problem has been patched, it seems to me that this link does not apply.
The second link ends with a suggestion: "This can be circumvented by either disabling the Lightning extension or changing the value of calendar.useragent.extra to blank (Preferences -> Advanced -> Config Editor)."
- So, I thought that Lightning went away quite awhile; long enough that I can't even guess at a date. Whatever the case, I don't have a Lightning extension to disable. - In the case of "(Preferences -> Advanced -> Config Editor)", I don't find this "Preferences" in either TBird or FF. There is: Settings > General that shows "about:preferences" but I am apparently not bright enough to figure out what to do at that point. If I use "Find in Settings", I get no results on "Config editor". - In FF, I type in about:config and assure the code to take the risk associated with user changes > "dom.security.secFetch" > Then WHAT? I see it is set to TRUE but again, I run out of talent before I get the job done; I can toggle to FALSE but don't know if that constitutes "to blank".
christ1 said
See https://meta.stackexchange.com/questions/382237/valid-rss-feed-url-is-not-authorized-in-thunderbird You should check your Thunderbird user agent string.
How? (do I check my Thunderbird user agent string)
How? (do I check my Thunderbird user agent string)
At the top right of the Thunderbird window, click the menu button ≡, then select Help > More Troubleshooting Information. Look for "User Agent".
Thanks for that.
User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:115.0) Gecko/20100101 Thunderbird/115.6.1
So, now that I can see it, what do I do with it?
christ1 said
How? (do I check my Thunderbird user agent string)At the top right of the Thunderbird window, click the menu button ≡, then select Help > More Troubleshooting Information. Look for "User Agent".
So, now that I can see it, what do I do with it?
The user agent looks good, so there's nothing you can or need to do. I have no other suggestions.
As a more general comment, I do create a subfolder for every feed or topic. The feed is then created underneath the subfolder. The benefit is that articles from different feeds are not dumped into a single folder. It's most likely not related to your problem though.
All -
The last update to TB (115.7.0 (64-bit) appears to have fixed this problem. Sorry for the tardy response. I was having a problem with being able to login to the support forum.