Email issue starting again

I had this problem about a year ago.

“Unfortunately, messages from [135.181.139.185] weren’t sent. Please contact your Internet service provider since part of their network is on our block list (S3150).”

Can you resolve thus urgently please…

Regain your privacy! Adopt /e/OS the unGoogled mobile OS and online servicesphone

I am experiencing the same since yesterday. If I interpret @Manoj’s answer on this issue, all we can do is indeed report and wait for /e/ to get in touch with Microsoft and then for Microsoft to solve the issue.

This was the issue last time:

It got fixed fairly quickly. Suspect Microsoft is desperate for custom.

I still (again?) have this issue, three weeks seems like a long time to get this fixed, no?

Just started using Evolution on a different distro. On other distributions (GNU/Linux) it has automatically picked up incoming and outgoing server details. What is interesting tonight is I got this:

Which if US Date format, the server certificate expired on the 8th April! I got the same warning for the IMAP server settings too!

Have passed the details of this message to the infra team to check and resolve.

Which OS was this and mail client is Evolution I guess from your post.

Yes. This was non a fresh installation of Zorin 17 Core which is not my daily driver. My main OS’s are PCLOS Debian and Q4OS. Both of those OS’s were setup before the date in that error message. I have only ever used APT versions of Evolution, I refuse to use Snap or Flatpak.
This is the first time i got a certification error which suggests why Microsoft are not accepting emails because the Certificate expired on 8th April.

autoconfigure with Evolution works out of the box and uses “mail.ecloud.global”. Was this a temporary error? don’t use smtp.ecloud.global, it’s nowhere advertised, thus no vaild cert

all use “mail.ecloud.global” since ages and the cert will not include the smtp subdomain. Why should it?

1 Like

It usually does automatic, yes. I did not enter smtp etc. I should have explained I had to manually enter incoming and outgoing settings when in the past it would get filled in automatically after entering my @e.email address. When I select temporarily allow, there is a slight delay tgen the Inbox get’s populated.

I use evolution with autoconfig from a clean state (removed account and re-added)

for sending it will use mail.ecloud.global with starttls on port 587 (as the autoconfig will set this to)

no issues. Not sure how you got there, but a fix is either setting the correct sending domain, port and starttls, or just re-add the account by just giving your email-address - no manual editing of connection.

Edit to add: this is marked as solution for the Evolution murena account setup, not the initial S3150 delivery error from outlook

1 Like