my incoming email from my business is blocked Verizon Security is unresponsive
mearley1
Newbie

The email that is sent from my business is being blocked, I have sent in numerous requests to have the problem resolved, but never receive , other that a form reply from verizon security that they will look into it. This has been going on for months, I did reccive aresponse that one of the  reasons was that my server was on a shared IP. I have switched servers and now have a dedicated IP, I submitted another form, but no responsive from Verizon seurity other than the form reply.

You cannot contact Verizon via phone, there is no customer service number, my only recourse will be to drop Verizon Fios and go with another company

has anyone had this problem? and how did  it get fixed.

0 Likes
Re: my incoming email from my business is blocked Verizon Security is unresponsive
JDoe5
Specialist - Level 1

Yeah, that happens all too often with Verizon email.  You get email reguarly from a legitimate source.  One day the email just stops.  The sender does NOT get any failed mail messages and from the POV of the sender they sent email succesfully to you.  The email is lost in the Verizon Ether.

Go to the Verizon email account holder WhiteList form and complete it.

http://my.verizon.com/micro/whitelist/RequestForm.aspx?id=member

Send the below URL to QVC and have QVC fill out the ISP WhiteList form

http://my.verizon.com/micro/whitelist/RequestForm.aspx?id=isp

Additionally, you can add your comapany's email Domain to the the "Safe Sender" category.

Log into Webmail

Settings --> email settings --> blocking

Scroll all the way down .

Click on Safe Senders

 

Enter the business' email address or domain in the field and choose "Add"

Re: my incoming email from my business is blocked Verizon Security is unresponsive
JDoe5
Specialist - Level 1

ADDENDUM:

That should have read...

"Send the below URL to your business and have a network administrator of your business fill out the ISP WhiteList form"

Sorry for any confusion the previous line may have caused.

0 Likes