My first thought was it was a Frontier issue since they have a long history of changing things with no customer notification and just causing things to break. Since I can receive email, but not send, things seemed only broken on the outbound side. I decided to see if I could access my accounts directly from Yahoo and bypass any forwarding that Frontier may be providing. I created new accounts on Yahoo using my iPad email client and that seemed to work from home using Viasat.
I had a board meeting yesterday so I tried email from our cooperative who uses a different ISP. Interestingly, my original Frontier accounts were able to send email at the cooperative location, but the new Yahoo accounts were unable to send. Just the opposite of at home.
When I got back home I tested and found now that neither the original Frontier accounts nor the new Yahoo accounts would send. So, I am somewhat perplexed now as to the root cause. As it seems to be an interaction between Viasat and the email provide. To test as this, I tried a Google account I created some time ago, but never use and it is able to send just fine both at home and away.
So, has Frontier and/or Yahoo been put on a blacklist at Viasat? Is Frontier and/or Yahoo having problems?. Anyone else here having similar problems or have a guess at what my problem might be?
I am not a big Google fan, but if I can’t resolve this in another day or two, I will have to close my existing accounts and move to gmail and that is a pain as I get email from a lot of people and organizations.
I am a frontier customer for 20+ years, I started with Frontier DSL, but in my area the bandwidth was just no longer good for anything, so I moved to Spectrum.
I am having the exact same issue...
I too, went through all of the settings over and over, I went back and forth from port 110/25 and 995/465 with SSL and get the same result.
I also tried smtp.frontier.com and smtp.frontiernet.net on both sets of ports.
In all cases - I can get mail - but cannot send SMTP mail
So I thought it was something with my Spectrum internet
I also have the mail configured on my android phone, a tablet that connects to a guess work wifi account, and mail configured through my work computer.
1) Work - same issue but the message is the 452 4.7.1 error
Where the 299.299.299.299 IP is my public IP of my work network.
2) from my phone and tablet connected to the public work wifi - I get the same error, only it is the IP of the public WiFi
3) Interesting fact ... on the phone, if I turn off WiFi and let it use data (Verizon) the message will send... my wife can get the same result through (TotalWireless)
I did a deep scan of my wife's PC that has the mail open all the time checking... no malware. My work PC is heavily protected at the endpoint and no malware there.
- Work and Home networks are blocked
- Effects all Frontier accounts we have (3) configured
- Effects multiple devices
- mail.yahoo.com (the frontier login) works just fine send and receive
- POP3 port 110 and 995 both work for getting mail - no mail has stopped coming to us, we just cannot send messages
- Verizon and TotalWireless cellular networks seem to work
- The issue started on 2/24/2020 or 2/25/2020 at some point for us as well.
I chatted with Frontier on 2/25/2020 (web chat) and all i kept getting was we suggest you use the webmail... RRRGGGG!!! i said no, this is not an accepted solution and to escalate. THen i got, "we do not support outlook" ... then i got "we have learned that yahoo is having issues with no resoluton time for a solution"
Last night 2/26/2020 i called - got a very nice person who was going to remote in and look at my settings, run a few tools and see if there was something that was causing the issue... very nice... i just could not do it at that time.
Now i found your thread here! VERY INTERSTING.
Your test worked great.
i changed all of my machines to use
I used 995 & 465 using SSL and requiring a secure connection - and it worked perfectly.
I think the root issue... and maybe if someone is paying attention...
When you are accessing the mail account from a 'non-approved' network (e.g. your work network or home like spectrum) there is a rule on their smtp server for relaying that is killing the connection as soon as it starts. I tried to start a telnet (putty) session over 465 to the frontier server and the connection died right way, not message.
Now, if i were still using slow Frontier DSL - and connected to their smtp server their rules would have permitted it. What baffles me is that Frontier tech support could not figure this out, or that the issue is with yahoo's configuration of their servers.
Anyway... kudos to you, for testing all sorts of ways and keeping it working... i too did not want to change my account of 20+ years
Keep me posted if you hear anything from Frontier or Yahoo (seems like we should be able to force the issue with yahoo)
So, I decided to bite the bullet and configure Apple Mail on my Mac. It was quite painless and access to Yahoo was not an issue. I am staying with POP for now even though IMAP is more convenient for multiple devices. I have one IMAP account on the laptop I use for my church treasurer duties and it is very slow compared to POP. It takes 30 seconds or so to sync the folders every time I fire it up. Probably if I used it every day, the syncs would be faster, but POP it is always fairly fast even if 50 new messages need to be downloaded.
From what I read, if I had access to a Yahoo account that owns my frontier and epix domain addresses, I could change a setting that allows older “less secure” email clients to work with Yahoo, but when I try to log into yahoo using my old email addresses, Yahoo redirects me to frontier. And since I am no longer a Frontier customer, I can’t access my frontier accounts. Oh well, it was probably high time to leave Seamonkey anyway, but after 25 years of Netscape and then Seamonkey, I was pretty familiar with it.
My partner noticed this issue first on her machine, apparently I haven't sent out email in a while so have not noticed it.
She has Outlook and was getting bounces with the error and as these were collecting in a folder only noticed the issue when people didn't not respond back to her emails. When I tried with Thunderbird, got an immediate popup message, same thing on my iPad.
I fiddled with the settings, even tried frontier.com, but the mail.yahoo.com setting saved the day.
I've been with this email for 20 years, it works mostly. I feel that they used to have fairly OK support when it was under there control, but after a while and after changes that happen unannounced or happen and aren't necessary. One time they had something about a device specific password going on, which forced you to have different passwords on various devices. Seems like they dropped that one off again, but that they did have this whole email warning that it was coming, only to silently recall the idea later.
I have been tolerant of all of the Frontier issues and I am reluctant to dump the email too as it seems like a pain to switch over to something. I do have a HostGator account and can create as many emails as I want through that but that also has issues with Frontier and Yahoo on the incoming side. As in Frontier and Yahoo will block and bounce emails sent from that account which renders it a hit and miss when you sent someone email from any account I can create there. My suspicion is that HostGator shares the same IP among various users and someone has sent out spam in the past from the IP range, so it was put on a naughty list, which causes it to be blocked by Yahoo/Frontier occasionally. From what I read years ago this is some kind of deferred delivery. It looks for a number of similar looking messages come through the system it assumes that they are spam, holds them in a queue and using some logic that is not made public, sits on them a while then delivers them if they stop coming through in large numbers or junks them, creating a bounce message to the sender. But, it can also cause single small messages, like test messages to fail. I mention this here just in case anyone has noticed any issues on the incoming side with Yahoo/Frontier, especially with short test messages.
For clarification, I used smtp.mail.yahoo.com on T-bird, Port 465 Connection Security: SSL/TLS Authentication Method: Normal Password Username: firstname.lastname@example.org
On Outlook smtp.mail.yahoo.com as well. But I had to go to the Advanced tab by clicking on More Settings and set the port manually to 465 as it was still at 25 from the previous Frontier smtp settings that worked up till a month ago and manually set to SSL as well.
Connection problem. (554 5.7.1 sender address rejected: Access denied)
Connection problem. (4188.8.131.52 recipient address rejected: 184.108.40.206 exceeded hourly recipients threshold)
Liars, neither of those messages had any merit. So I tried the tip about changing the outgoing to "smtp.mail.yahoo.com" and using port 465. No luck. I've never had problems with my email until today. What the heck?
Am I out of luck? Should I even bother continuing to use this ancient email address anymore if I can no longer use an email app to faithfully send my mail, or has anyone found another fix for this issue?
Thanks for any help and blessings.