Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Unable to load null status:404 when replying in Verizon webmail

  • 6
  • 10
  • 10 views
  • Nzaghachi ikpeazụ nke guigs

more options

Unable to load null status:404 when replying in Verizon webmail. Error appears in its own window. It seems to be related to MIME-encoded incoming messages. I can open a new message window and copy/paste the reply-message into the new message and then send it without the error. Trying to save-as-draft also gives the same error message. This is recent after update to V.31 of Firefox on Win7(Sp1).

Unable to load null status:404 when replying in Verizon webmail. Error appears in its own window. It seems to be related to MIME-encoded incoming messages. I can open a new message window and copy/paste the reply-message into the new message and then send it without the error. Trying to save-as-draft also gives the same error message. This is recent after update to V.31 of Firefox on Win7(Sp1).

All Replies (6)

more options

Please see this thread about this issue with Verizon.

more options

Yes, I read that thread. I am new to this forum. I do not know why this added report or the problem is in its own thread and not with the others. Nevertheless, the solution seems to be a fix to firefox, and I have seen nothing saying that will happen.

more options

it's a known regression in firefox 31 and mozilla's engineers are working on addressing that at the moment

more options

Yes, I saw that response in the real thread about this issue, where I reposted this note. I am glad this is being addressed, but as a large user community has been plagued with this "regression" bug, I would hope the "developers" fix it soonest.

more options

Same thing here, and I have Windows 7 Ult SP1 32-bit and Windows 8.1 64-bit! I thought it was just on my Win7 machine, but it also is on my Win8.1 machine. Is this just with verizon or it happens with other IPs?

more options

Hey guys, It looks like that the issue has been resolved on the site, can you please try to send and email and confirm this change. There was a bug filed and fixed this week in version 32?

You make have to clear the cache for the site to see the changes. Thank you!