My domain host's server is blocking my IP address every few days

glasskuter said:

Is the reason his isp whitelists his email account because his ISP is seeing unsuccessful sign-in attempts to his account?

Click to expand...

The domain host has no idea.

It’s Ian’s end. I just need to finish what I started.

Whenever suits you Ian, you know I’m always available to you time allowed

glasskuter said:

Is the reason his isp whitelists his email account because his ISP is seeing unsuccessful sign-in attempts to his account?

Click to expand...

Yes - that is what they tell me. They see a number of attempts to logon to their mail server using my email address but an incorrect password so protection kicks in and blocks my domain. They can see all attempts are from my IP address. Work around while we have been trying to find the solution has been to whitelist my IP address but that only works until my ISP changes the dynamic address for whatever reason.

Glasscutter - Just to clarify. It's the domain host and mail service provider that whitelists my dynamic IP address. My ISP is different and they periodically change my IP address.

I tend to think simply (which ends me up in left field sometimes) because I've lost most every complex brain cell I ever had. Is there any possibility at all you could have someone else piggy-backing onto your wireless network at times? It certainly would not hurt to change your wireless password and make it difficult. I'd even change the network name your router broadcasts. Depending on the number of devices on your network, it might take a bit, but I would even set up MAC address control in the router. If any device you have not specifically added attempts to connect, they can't, whether they know your wireless password or not. Another thing, make sure your router is NOT using its default administrator password. Assign your own. So many people leave it at defualt which just welcomes someone to mess with their network.

That's all I got, back to antspants now.

Valid suggestions and in a town or city quite possible. Where I live, very unlikely. I know everyone that lives within range of my network and have known them for years and decades. However your suggestions regarding passwords is one I haven't looked at for some time in respect of my lAN so it wouldn't do any harm to update all passwords anyway. Thaks.

Ian I'm going to jump out of this thread. I’ll catch up via conversation on Monday or before if you need anything.

This is the plan for Monday.

• Remove the email address from Outlook
• Remove the profile from Outlook and anything from HKEY_CURRENT_USER\Software\Microsoft\Office\Office 365\Outlook\Profiles
• Remove everything in your AppData\Local\Microsoft\Outlook\ folder
• Possibly remove 365.
• Start again.

If it returns and you find yourself blocked again:

• Removing your current email address from Outlook
• We’ll be creating a second email address for StBees. Call it redirect (or something)
• In the PLESK interface we’ll be redirecting the email for the current email address to the new one, redirect@
• Adding redirect@ to Outlook
• You’ll receive all you original Stbees mail via the redirect@ into Outlook 365

This is for 2 reasons

1. You won’t have to lose your original email address
2. If it happens again and your ip address is blocked, we’re looking in the wrong place.

That would mean there could be something fishy in your router
You may need to triple check your phone (I know you said it’s a newer phone post this problem)

I don’t believe anyone is accessing your router or account.

One thing I would like to know?:

Have you made an email address at YNH for your wife?
Have you considered it’s her setup?
If your wifes email is the culprit, the router gets blocked, the block doesn’t discriminate between email addresses at YNH, it just blocks access to all of them (the IP for your Router)

YNH tells me the problem is triggered by my address not my wife's. Her address is also with YNH and is obviously different from mine though on the same domain.
Failed attempts to log in to my mail server using my email address and wrong password result in my IP being blocked. That takes everything using my domain down with it - all email addresses using that domain and the two web site hosted by YNH.
Talk to you Monday.

There is yet another option.
We backup your email via pst
Delete your email address from the YNH server
Re-add it
Create an IMAP in outlook for your address
Copy the PST content back into the IMAP from the PST and let it all sync back into the server

This would rule out a server issue
It’ll be a semi long process, Ian

But my previous post first

We can trigger an ip change possibly by restarting your router, to test

antspants said:

There is yet another option.
We backup your email via pst
Delete your email address from the YNH server
Re-add it
Create an IMAP in outlook for your address
Copy the PST content back into the IMAP from the PST and let it all sync back into the server

Click to expand...

I thought you or I had already tried that one?

Sigurd said:

I thought you or I had already tried that one?

Click to expand...

We’ve never deleted the email account from the server. Only from Outlook.

There is a system though, so you don’t lose anything.
If you remove the email account from the server before a proper process, you could lose all your mail. At least mail since we did that last POP/PST

We’ll start with the first mention. Server option is if this keeps happening after the first mentioned fix

So….
The last time I connected to Sigurd and tried to resolve the server lockouts, I removed the Outlook (New) app as it had the same server email address that has been causing problems. Sigurd uses Outlook Classic 365

As we can see from the last few posts above, the issue wan’t resolved.

Connected again today.

What I poorly failed to check last time, is that Windows Mail also had the offending email account in it.
The date of the last received mail in there was more than likely pre these server lockouts.

This could explain a lot if the password or settings were changed since it was last used.
Windows Mail checks for mail in the background and the offending email address was still active however not receiving mail.
The constant attempts by Windows Mail to get mail with the incorrect credentials would of been triggering the server lockouts.

Moving forward, we uninstalled Windows Mail & deleted all remnants of the email address and profile from Outlook classic.
We created a new profile and re-added the email address.
If this hasn’t fixed it, I attack the Web Server.

Goes without saying, Sigurd and I have our fingers crossed.

(This is more a reminder for me to look back on if there is a next time. But there wont be. Please ignore)

My thanks to Sinto aka Antspants for the on-line session we have just spent between the UK and Australia! Hopefully this long running problem has been solved, but regardless of the outcome I am very grateful for the time he has given me.

Sigurd said:

My thanks to Sinto aka Antspants for the on-line session we have just spent between the UK and Australia! Hopefully this long running problem has been solved, but regardless of the outcome I am very grateful for the time he has given me.

Click to expand...

Thank you. Always a pleasure, Ian.