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

[sworcester]

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)

[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.

[SamFrustrated]

Me too, no6b. The article that was posted about "Verizon Your Domain" is too vague (I am sure it makes sense to people that understands it). I cannot be sure it applies to us. If it applies to us then Verizon should have warned us and given us enough time to figure out what we need to do. It is my understanding that I must use my ISP's SMTP server to send email. Verizon also needs to educate their support people so they understand the problem and solution(s). You can read in my first post how the Verizon customer service person reacted to the problem when I tried to get help.

[tns2]

NO you do not need to send your email thru verizon SMTP server.  Normally you send it to the server that owns or supports your domain name.

However verizon does block port 25 the default, unsecured well known port.  Some of the popular other ports are not blocked (587,465 etc)

[SamFrustrated]

Unless you have been hacking my system, you do not know how I normally send email. Note that there are three customers that have been sending email for a non-Verizon account thru the Verizon server  That is a fact, you seen to want to argue. It is a service that Verizon has been providing for years. If they are not offering it now then it is a huge inconvenience to not provide us time to prepare. Please do not ignore that.

The following all provide some kind of explanartion of customers sending email that the account is external to the ISP thru their ISP.

Why can’t I Send Domain Email through my email client?

How to send emails through your ISP | Flo Web Design Ltd

CST: Email settings for sending mail via ISP SMTP server

&%$*@# - WHY CAN'T I SEND MAIL???

Sending email from an ISP that blocks port 25 at Simplehost Web Hosting

Trouble sending mail? Can't send email? SMTP errors? - Saratoga Hosting Helpdesk

Cannot Send but can Receive Email

Verizon Email using your own using personal domain - Verizon FiOS | DSLReports Forums

FiOS and external SMTP server - Verizon FiOS | DSLReports Forums

I found one more page thaty is so important that I will make a separate post for it.

[InFoman1]

Faced the same situation last night when I could still receive emails using my POP ix.netcom account (Earthlink) but could not send them using my SMTP verizon server now switched to AOL. Long and short of it - You're not going to get any help from either Verizon or AOL. Their support hasn't a clue.  Turns out AOL will not allow you to use a 3'red party POP address with their SMTP servers - Something to do with Spam.

My Netcom/Earthlink solutions turned out to be quite simple - It has nothing to do with Verizon/AOL. The POP setting remains unchanged. but you MUST now use Earthlinks SMTP server with the correct settings for it to work. Following are the instructions I used in Windows 10 running Microsoft Outlook: (This should work with anyone's SMTP server as long as you use the correct settings from you email provider.)

1. While in Outlook, start by choosings "Tools", "Account Settings", and double-click on the email account you are trying to configure.
2. Change the address of the SMTP server From: SMTP.VERIZON.NET  To: SMTPAUTH.EARTHLINK.NET (Check your email provider for their SMTP server address.)
3. Click on "More Settings" in the lower right-hand side of the box.
4. Click on the "Outgoing Server" Tab
5. Check the box that says "My outgoing server (SMTP) requires authentication" under internet email settings.
6. Check the box below that says "Log on using" then put user name and password. Your password should be fine but, r username, by itself is not. You MUST put your entire earthlink email address not just your username. (Check your email provider for their requirements.)
7. Click on the "Advanced Tab."
8. Change the 25 in the "Outgoing server" box to 587. (Check your email provider for their requirements.)
9. Return to the settings screen and click the box "Test Account Settings."

If no typos were made, you should be back in businees.

Hope this helps.

[packrat2]

Unfortunately that does not do me any good. I am my own smtp relay. I have been since 2002.

[no6b]

Spent one last hour on the phone with Verizon, & my takeaway is they aren't going to do anything about it because AOL runs the SMTP servers now.  Bottom line is that Verizon is getting out of the e-mail business altogether: I was told that new Verizon customers aren't being offered e-mail service of any kind, & are expected to either use a free service like GMail, or pay someone else for separate service.

My stance was that since I was offered e-mail service at the time I renewed my contract, Verizon must either provide it or reimburse me for my costs of replacement SMTP service.  There are providers of straight SMTP service - the one I found is only $20/year.  So I asked Verizon to give me a discount to cover the cost of that service.  They agreed to do so for one year.  My Verizon contract expires shortly after that, & by then I expect Verizon FiOS in this area to be sold off to Frontier anyway, so we'll see what things are like by then.

[Lucid123]

I found a free third party relay: sparkpost.com. so far it's been working (1 day). Note: you have to use STARTTLS to get encrypted connection...I had to change my mail server from "SSL/TLS" to "STARTTLS (Required)" (hMailServer).

[#14]

I was having the same problem and talked to AOL for an hour. They even logged into my comoputer and didn't fix it. It is really a simple fix.

Previously Verizon allowed you to send email through their server in the name of an external account. AOL doesn't. So for outgoing mail server (SMTP), you had something like outgoing.verizon.net, then with the aol change you had smtp.aol.com. That works if you're sending from your verizon/aol account. But when sending from an account from "yourwebsite".com or gmail.com you have to use the SMTP settings from those servers. Example: if it's a gmail account your smtp setting will be "smtp.gmail.com". Then under more settings in the Outgoing Server tab you'll select Use same settings as my incoming mail server (instead of what you may have previously had, ie: log on using "yourusername@verizon.net"). then under the advanced tab you'll select the incoming server (995 for secure - and check the box) and outgoing server (for instance for gmail it is 465 with SSL encryption..

You may have to play a little with the number for your outgoing server. For my website the outgoing server is 587 and no encryption.

Click ok. Test your account settings. This worked for me, and I'm now able to send via Gmail and my personally owned website. Good luck!

[SamFrustrated]

Please see Your Attention Needed: Re-configure Your Email Settings to Send Email | FiOS Internet | Residential ... It seems to describe our situaiton quite clearly. I see no indication it has been discontinued and all indication is that it should work. I followed the link near the bottom for step-by-step instructions then how to Configure Thunderbird to use port 465 for sending email | High Speed Internet | Residential Support .... It does not provide a server name but assuming that smtp.verizon.net is the same as before, it does not work.

[tns2]

I am surprised to hear it was working before.

The intention was to make sure you existed on the SMTP server by the name you logged on with.  This was to reduce spamming message coming from Verizon Network.  It was never meant to allow you to use another network name.  It was always possible to provide another name for responding to email.  Allowing you to say you were another userid and network name WHICH THEY COULDN't Authenticate, would allow you to spam people anonymously.

Whether you like it or not you are NOW an AOL customer even if you haven't been told to switch your Webmail access.  And it certainly looks like AOL IS enforcing this.

[no6b]

Actually it would be quite easy for AOL to verify that I own a particular e-mail address: just send a verification code to it.  If I receive the code, that means it's my e-mail address, & if I can receive e-mail with it why can't I send too?

[SamFrustrated]

---

@no6b wrote:

if I can receive e-mail with it why can't I send too?

---

Email is not logical. Email is sent using SMTP servers that are totally different from the POP3 servers used to receive email.

[no6b]

Update: I called Verizon to complain about the problem.  Rep transferred me to AOL.  Explained the problem to AOL rep.  They said "your domain isn't in our system so we can't help".  Transferred me back to Verizon.  Told the next rep. I got that I was already transferred back to Verizon from AOL so please fix the problem!  From this point I was on the phone for at least another hour while the poor rep. did everything he could to research the problem.  Finally put someone on the line from AOL again!  But this time she asked for my full name & phone number plus the domain that I wanted to be able to send e-mail from.  She said wait 48 hours & then it should work!!!  We'll see...

[SamFrustrated]

TNS_2, please understand that this is an area that you are not familiar with. I have no doubt that you have been very helpful for many people but this is an area you are not sufficiently familiar with. It does not work the way you assume it does.

There are a few things I have said that you are ignoring.

[tns2]

---

@SamFrustrated wrote:

TNS_2, please understand that this is an area that you are not familiar with. I have no doubt that you have been very helpful for many people but this is an area you are not sufficiently familiar with. It does not work the way you assume it does.

There are a few things I have said that you are ignoring.

---

Actually one of the things I did before I retired was run an Email server for my company.(18000 users).  I retired 10 years ago.  Even then spam was a problem and it was recommended that you NOT allow email to be introduced by your system if the Original User name was not carried in the headers.  You don't have the info to authenticate a user and his password on another system

Which thing do you think I am ignoring.  THe fact that you think AOL(a Verizon company) should still allow you to use a different userid and domain name?  Something else.