Links in email will not open from my secondary email account.



Mail Window Front End
9 years ago
9 years ago


(Reporter: safira, Unassigned)


Firefox Tracking Flags

(Not tracked)





9 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv: Gecko/2009042316 Firefox/3.0.10 (.NET CLR 3.5.30729)
Build Identifier: version (20090302)

I have 2 email accounts configured. On my secondary (military) account, any emails that I receive with any type of internet link, I cannot open it. On the very bottom of the screen, I can see that the path for links on that account is "blockedhttp://inserturlhere", but I can't find anything in Mozilla that will allow me to change it so that all links are not blocked.

Reproducible: Always

Steps to Reproduce:
1.Open my Army inbox
2.Click on an email containing an external link
3. Click on the external link
Actual Results:  
Link doesn't open.

Expected Results:  
The link should open into an internet browser.
(In reply to comment #0)

> "blockedhttp://inserturlhere", but I can't find anything in Mozilla that will
> allow me to change it so that all links are not blocked.

Something server side is changing the emails so the links or not valid html links anymore. I'm temped to close this as invalid.
THe other option is having an extension changing your blocked link to normal links - ain't sure if it's doable.
Component: Account Manager → Mail Window Front End
QA Contact: account-manager → front-end

Comment 2

9 years ago
I was able to open links fine when I was using Windows mail. I created the account in Thunderbird for the sake of simplicity.
It would help if you do a view source and copy the line with a link (you can XXX the part after the http:// )

Comment 4

9 years ago
It's likely Exchange/Outlook that adds the "blocked::" to so some links!AFCCA5892B178862!751.entry

Comment 5

9 years ago
Did some more research, its the Army's fault.
Last Resolved: 9 years ago
Resolution: --- → FIXED
Resolution: FIXED → INVALID
in that case no bug for us, thanks for the response.
You need to log in before you can comment on or make changes to this bug.