Is it it just me or is anyone else having problems scan-to-emailing over Verizon. I have at least two 2232's that now matter how I configure them they always error out. I have tried:
My personal ISP with smtp auth
Our business web host with smtp auth
A Verizon account that works on most other machines with smtp auth
I have tried ports 25, a "secret" port 26 on our mail host and the new and "improved" 587 port.
Is it possible Verizon is blocking specific IPs?
I tried setting up argosoft on one of the computers to see what was happening .The argosoft log said it was flat out rejected, I don't know if Verizon was just not going to let an smtp server live on their network. So that wasn't much help.
On strange thing tho. When I setup the email with our business host, I can send email to myself and anyone else within our domain, but not to any other domains.
Any ideas?
TIA
My personal ISP with smtp auth
Our business web host with smtp auth
A Verizon account that works on most other machines with smtp auth
I have tried ports 25, a "secret" port 26 on our mail host and the new and "improved" 587 port.
Is it possible Verizon is blocking specific IPs?
I tried setting up argosoft on one of the computers to see what was happening .The argosoft log said it was flat out rejected, I don't know if Verizon was just not going to let an smtp server live on their network. So that wasn't much help.
On strange thing tho. When I setup the email with our business host, I can send email to myself and anyone else within our domain, but not to any other domains.
Any ideas?
TIA
Comment