Child Item

Site Totals

61389 Questions Answered 268 Categories

AOL move and external POP account access not working sending and fixing 553 5.7.1 error

Moved my Verizon.net email over to AOL and now when I check email, using Outlook, my other email address (non Verizon POP3) it will recieve but not send email from that account, now giving an error

Send test e-mail message: Cannot send the message. Verify the e-mail address in your account properties. The server responded: 553 5.7.1 <user@mydomain.com>: Sender address rejected: not owned by user user@verizon.net

I tried talking with Verizon support who said it is an email problem so you have to talk with AOL. AOL said we only deal with Verizon and AOL accounts and they couldnt help.

I have my incoming server as my POP server as the documentation states,

mail.mydomain.com

Outgoing as

smtp.verizon.net

Username and password are for mydomain.com

But I had to change the User Information to My Verizon info and then on the more settings/General put in the reply email address of the POP email account

(I never had to do this until the AOL change)

Comments

tns2

They have stopped offering Mydomain. Assuming you paid for it for this year, then you need to discuss it with Verizon. I doubt AOL has anything set up to help you.

Lots of luck.

SamFrustrated

I am getting the same message and I probably have the same situation. The person that commented about mydomain probably does not understand. In your case, "mydomain" is actually a different domain name, correct?

I also receive email using my domain's POP3 server but I must send email using Verizon's SMTP server. As best as I understand things, that is how email works. Verizon's server woked for me yesterday and has worked for the six years we have had Verizon,. The Verizon suppport person I talked with insisted it is a temporary outage but he does not understand what our situaion is.

Yes, the Verizon help people are no help, they do not understand. We probably need to get the attention of someone that understands.

Hopefully it is a temporary problem and the relevant people in Verizon are working on fixing it.

no6b

Having the same problem here too. I'm worried that this is a new "security feature" to thwart address spoofing. If so, we'll need another SMTP server to use to send our e-mail. Anyone have any leads as to what's available?

tns2

OLD FEATURE for AOL. And i thought for Verizon as well. Your domain has to match, i.e your userid at verizon.com. Verizon was offering a feature called Your Domain that you paid for a year (and of course also offering business accounts). As far as I knew only those with such accounts were allowed to specify non-Verizon domain names.

see info on your domain https://www.verizon.com/support/consumer/email/your-domain

no6b

I never had "Your Domain", yet I was able to send mail using my own domain name for many years until yesterday.

hattrik21

OK So I run a personal domain and have an email address to go along with it. For the last 3+ years I have not had any issues sending emails via verizon's servers when I authenticated with my verizon account. Now after the switch over I can no longer do this. I get an error stating that %USER%@%DOMAIN% is not owend by my @verizon.net address. No kidding, I OWN IT. They state nothing will change and the moment I followed that stupid link and setup things on the AOL side, the issue began.

Before I get any bashing, verizon treated this as a third party email address and it WAS allowed when I logged onto their servers with my verizon email address.

Anyone have any suggestions?

no6b

See my prior message(s).

Still working the issue, almost 1 week later. Chatted with AOL tech.; first said they're still working on it, then regressed to asking for my e-mail client's SSL settings, reset my modem, etc. Opened a trouble ticket at postmaster.aol.com. Will probably call Verizon tomorrow to ask for a reduction in my bill to pay for an outside SMTP service like no-ip.org ($20/year works to $1.67 mo., round up to $2/mo. for all the trouble).

bulls2212

I have the exact same problem:

http://forums.verizon.com/t5/Verizon-net-Email/After-being-forced-to-AOL-Mail-I-can-no-longer-send-mail/m-p/812454/highlight/false#M23710

The good news for verizon is that they will save money from the move to AOL mail.

The bad news for verizon customers is that they are losing email functionality and may never be able to send email again from non-verizon pop3 accounts.

I have already asked Verizon to compensate me for the loss of email services.

Maybe a government agency will help us regain our lost services.

bulls2212

I'm having the same problem.

Why would Verizon do this to its customers?

http://forums.verizon.com/t5/Verizon-net-Email/After-being-forced-to-AOL-Mail-I-can-no-longer-send-mail/td-p/812415

packrat2

I am guessing no one has found a solution? I spent 3 hours on the phone last night being shuffled back and forth between Verizon and AOL and still no solution. Their techs don't have a clue. As much as I hate to have to go back to cable, I have decided to move toTime Warner.

15 years as a Verizon customer and now being forced back to cable. sigh.......

packrat2

I think I just found out why Verizon does not care about solving the issue.

On April 1, Verizon services in California, Texas and Florida will move to the Frontier network.

http://meetfrontier.com/

packrat2

I think I have figured out what is going on here. Verizon/AOL is preventing relaying from any domains except theirs.

Using the Verizon smtp server setting for the outgoing server, if I set my from address to be my @verizon.net email address I can send emails out. Without changing anything on the outgoing server settings and just changing my from address to be my third party email address then I get blocked. Since Verizon blocks outgoing smtp traffic and forces the use of their smtp relay to send emails there appears to be no way to send emails that do not come from their domain.

SamFrustrated

@no6b wrote:
Having the same problem here too. I'm worried that this is a new "security feature" to thwart address spoofing. If so, we'll need another SMTP server to use to send our e-mail. Anyone have any leads as to what's available?

If you can descrive why you can't use the mail server for the site hosting your domain then that will help. I can't remember why I was using Verizon's server instead of the server provided by my hosting server but my point is that it would have helped if Verizon provided a warning that they will no longer provide the service. My hosting service is now GoDaddy and I was able to figure out how to use their mail servder for my domains but it took a couple of hours. I would have preferred to have had more time to schedule when I took care of the issure.

SamFrustrated

@hattrik21 wrote:
OK So I run a personal domain and have an email address to go along with it. For the last 3+ years I have not had any issues sending emails via verizon's servers when I authenticated with my verizon account.

It will help if you can explain why you cannot send messages using the server provided by your personal domain. Is it because there is not such a server?

SamFrustrated

@bulls2212 wrote:
I'm having the same problem.
Why would Verizon do this to its customers?
http://forums.verizon.com/t5/Verizon-net-Email/After-being-forced-to-AOL-Mail-I-can-no-longer-send-mail/td-p/812415

Can you explain why you cannot use the mail server provided by your domain's host? It is very easy for others to say you need to do that but if there is a good reason why you cannot then that would help.

batguano1

A few years ago, before the email move to AOL, Verizon discontinued an authentication service that allowed email user to send email from non-Verizon domains through Verizon SMTP servers. This limitation continued after the move to AOL outbound email servers (smpt.aol.com) at least for those with verizon.net user ids.

Today I tried going back to Square One by attempting to send non-verizon.net email through the non-Verizon (HostMySite) SMTP server. Surprise! It worked.

The outgoing email server setting for HostMySite are mail.mydomain.xxx, Port 50, SSL unchecked, authentication checked, same user id and password as incoming (POP3) email server.

The inability to send email from non-verizon.net domains has been a problem for years and the Verizon tech support people don't understand it. Please let the community know if my solution works for you.

Child Item