Hello @gc8086,
Thanks for participating in the Rogers Community Forums! What a great question--I think it may be one that we've never gotten before! 🤔
I'm going to tag in some of our lovely Resident Experts in hopes that they can provide some help on this particular subject matter!
Cheers!
RogersLaura
Looks like Rogers made some changes. For the past couple of days when I go to use Outlook for Mac 2011 it gives me an "Error Code 150" if I try to send an e-mail, or if I start Outlook (and there's an e-mail in the outbox). I'm still able to receive e-mails on my computer. I've encountered the issue on all 4 of our e-mail accounts (I have 3 and my wife (different user on the computer, has one).
I can go to Webmail (Rogers/Yahoo) and everything works fine there. I can use mail on my iPad and it works fine there. I also deleted and recreated an app PW on one of my accounts in case that was the problem.
I don't know whether this issue with Outlook was caused by the same changes at Rogers/Yahoo, or whether this post should be in the same thread, but it certainly appears that something has gone wrong.
I checked my settings with the following link and everything looks good, but there must have been some sort of SMTP change, or similar...
Hello @japples ,
Thanks for your post! 🙂
Is your issue still happening as we speak? You mentioned being unable to send any emails, but can you receive them? Here are a few things you can look at to try and resolve the problem:
Check your outgoing mail server settings:
1. Navigate to Tools > Accounts... from the menu.
2. Highlight the desired account and click Properties.
3. Make sure the correct server name is entered under Outgoing mail (SMTP): on the Servers tab.
4. On the same tab, verify My server requires authentication is checked if needed (which is typically the case). Under Settings..., you can specify a username and password different from your incoming mail credentials.
5. On the Advanced tab, make sure This server requires a secure connection (SSL) is checked under Outgoing mail (SMTP): if your outgoing mail connection must be encrypted.
6. Check the port under Outgoing mail (SMTP):, too. Typical ports include 25 and 465.
Make Sure Your "Sent Items" Folder Isn't Too Large:
The folder can hold 2 GB at most. To check the size, go into your Outlook Express store folder and examine the Sent Items.dbx file size.
Move messages from the Sent Items folder in Outlook Express to another folder. Make separate folders for separate things, such as one for all mail sent out over the course of a year.
Make sure you compact folders manually after moving messages.
Rename a Corrupt "Outbox.dbx" File:
1. With Outlook Express closed, open your Outlook Express store folder in Windows Explorer and rename the Outbox.dbx file to Outlook.old.
2. Note that you can no longer access any messages in your "old" Outbox folder.
3. If the renaming has fixed your delivery problems, you can delete the Outbox.old file.
@57 , I just saw your post: Perhaps this applies to your issue as well?
Let us know if any of these workarounds help!
RogersLaura
@RogersYasmine : Looks like you were typing while I added my own problem to this thread (post 6). I checked all the SMTP settings and they look fine. Perhaps Yahoo/Rogers made some sort of change there.
@japples wrote: My outgoing mail server settings seem to be fine. I use port 25 and it takes awhile to get an error as the email program is trying to connect, finally giving me a "connection to server has failed". Port 465 gives me a lightning quick error as soon as I click send.
I tried similar experiments and got exactly the same thing. I deselected SSL as discussed on the internet just as an experiment and in that case the error message took longer, like your port 25.... I'm using 465 as before, I get the lightning quick error message too. When I deselect SSL I get a different error code instead of 150... Pretty sure this has something to do with Rogers/Yahoo. @RogersYasmine please check for recent changes.
Perhaps as more and more people run into problems with e-mail clients they will come here (and other Rogers contact sites) and complain. I'm guessing that most people now use their phones, so people using computers are out of luck until enough of them call/text/tweet/post to complain. Let's hope it reaches critical mass soon. I'm sure lots of people are wasting many hours trying to troubleshoot their e-mail clients...
PM sent per request below.
Greetings and good afternoon Community!
If you're encountering this issue and don't have an active ticket, please PM us @CommunityHelps. If you're not familiar with our PMing process, you can find instructions here.
I don't want to see anyone abandoning their email platform of choice unnecessarily. There must be a commonality with all of these cases so the more escalations we perform, the more likely we are to identify the pattern.
Looking forward to troubleshooting and working with you all towards finding a solution.
Regards,
RogersCorey
@gc8086 : Sorry to have highjacked your thread. I'm thinking that whatever change in Yahoo is causing your issue may have also affected computer e-mail clients. This is often the case when a number of people encounter problems at around the same time, even when they are not identical.
One idea for me and for @japples to try would be to create a new e-mail user in Outlook and in Webmail/Yahoo. In this way we can rule out corrupt user information in Outlook. I already sort-of ruled that out since I have 4 e-mails with 2 users on my computer, but I may give it a try once I have some quiet time...
I also deleted the Outlook app from my computer and restored it from a backup from before this started.
Receiving in Outlook works fine - it's only sending that's affected. I'm still leaning towards some sort of SMTP change at Yahoo/Rogers. Also, changing the Port or SSL changes the response/error code as well as how long it takes to get the error code in Outlook.
Anyone else out there who can check if their e-mail clients are sending properly from their computer even if they normally don't use their computer? Of course, as we saw with the App PW change, it may take some time for more people to be affected since the change may not have been "global".
-
12823 views
-
6 Likes
-
-
