Hi,
Is anyone from Trend Micro on the list who can help us diagnose some persistent
re-listings?
We log tickets, and the IP is removed, but 24 hours later, it is back on the
list - we've checked and all content is clean.
Graeme
Email secured by Trustwave advanced threat protection. Learn
Correct, 1.1.1.1 is the anycast address that clients use. The resolvers behind
that anycast address will be part of the listed IP addresses.
Servers will not see the query coming from 1.1.1.1.
Regards,
Graeme Slogrove
-Original Message-
From: mailop On Behalf Of Jose Morales Velazquez
Hi,
Looking for a Mimecast contact to help review some issues we are seeing with
their DMARC reports.
Thanks in advance,
Graeme
Email secured by Trustwave advanced threat protection. Learn more at
https://trus.tw/mailmarshal
This transmission may contain information that is privileged,
Hi,
We are having emails from our cloud service going directly to the SPAM folder
in Yahoo/ATT.
SPF/DKIM/DMARC show pass in the message
Is there someone we can connect with to understand why and correct?
Thanks!
Graeme
Email secured by Trustwave advanced threat protection. Learn more at
aw connections from an IP with no SWIP and no website, would YOU allow
traffic from it?
On 2022-03-28 15:30, Graeme Slogrove via mailop wrote:
> We are actively using the new IP ranges as published a few weeks ago,
> everything seemed fine until this morning
>
> Server refused mail a
We are actively using the new IP ranges as published a few weeks ago,
everything seemed fine until this morning
Server refused mail at MAIL FROM - 553 5.3.0 flpd577 DNSBL:RBL 521<
52.165.84.32 >_is_blocked.For assistance forward this error to
Hi,
If anyone from emailsrvr.com is on this list, please contact me. A new IP range
is being limited.
Thanks in advance.
Graeme
Email secured by Trustwave advanced threat protection. Learn more at
https://trus.tw/mailmarshal
This transmission may contain information that is privileged,
Hi everyone,
Looking for some resources at Yahoo and Google to allow for a warm up period of
some new IP addresses. I have already logged a ticket with MS for IP Mitigation.
We are moving our US services from our own datacenters to Azure. Our operations
in EU and AU run in Azure already.
I think he meant mails that are over 400k, not 400k mails.
We encountered a similar issue around 10 years ago, where mails over 2MB to
Gmail timed out from various global locations. Worked fine from the US.
They did eventually fix the issue after we provided the logs and pcaps, it was
due to
they're just cycling through
cloud IPs like candy. They're also rotating out domains and email subjects
quite rapidly.
Maybe I need to rethink the method entirely. Microsoft IP + no envelope sender
looks to be a good combo to target what I'm seeing.
On 2021-11-01 22:38, Graeme Slogrove via mailop
(That link is being deprecated)
One must be careful about blocking entire Azure ranges. There are valid
third-party services (authorized for SMTP) that run on Azure hosted VM
infrastructure (Office 365 included) that you should expect to receive email
from.
I've just received multiple
Yes, we see it regularly.
Would not surprise me that it pings/test the users domain endpoint when setting
up outlook on mobile client and confirming the details.
-Original Message-
From: mailop On Behalf Of J Doe via mailop
Sent: Friday, 10 September 2021 11:30 AM
To: mailop@mailop.org
Hi,
It's unfortunate to see others experiencing the same issues we've had with
Microsoft in general. We're not a massive player in the market and constantly
experience these service-disrupting incidents with MS and Office365.
(Side note - I am also personally a paying premium customer of
Circling back - we eventually managed to escalate to Exchange Online support.
Since it wasn't our "tenant" that had the problem, it took a while.
Standard answers of "this is a rate change problem", asking if the IP was new.
After showing them 30 days of traffic statistics, they reset the
Hi,
At exactly midnight UTC, one of our servers started receiving the error
451 4.7.500 Server busy. Please try again later from [20.40.161.177]. (S77719)
The error codes seem to indicate a problem with IP throttling due to changes in
traffic patterns, but our logs show less than 2% variance
Hi,
We run a shared mail security platform, serving thousands of customers.
One of our customers decided to shut off certain outbound spam detection
features (We have subsequently forced the configuration back on)
A mailbox of theirs was compromised and they sent out around 5000 new spam
16 matches
Mail list logo