Hi Michael, Thank you for your response.
I’ve reviewed both our SNDS data and internal logs, but I’m not sure if the throttle explanation applies to our situation. We have rate limits in place for all IPs, typically set to 15-minute intervals, to prevent sudden traffic spikes. For the IPs that were blocked, we observed no unusual increase in sent messages. One specific IP I’m investigating sends approximately 1,000 emails per day, with consistent green days in SNDS and no spam trap hits. On the day it was blocked, only 487 messages were sent until the block happened. We’ve previously tried allowing blocks to expire, but even after 2-3 weeks with no activity, the IPs remained blocked. The only solution was to submit a ticket to have them manually unblocked. At least for us, it looks like a recurring task that is being run, because it happens with 80+ IPs on a specific day. I understand that you no longer work in this area, but could there be other factors contributing to S3150 blocks besides sending too much traffic in a short period? Thanks, Fernando On Wed, Dec 4, 2024 at 2:15 PM Michael Wise <michael.w...@microsoft.com> wrote: > > > S 3150 is a throttle block, possibly related to IP reputation > classification. > > It should automatically expire on its own, and is generally caused by > sending too much traffic too fast. > > > > Usually. > > > > But I no longer work in that particular area, so can’t be of any further > assistance. > > > > Aloha, > > Michael. > > -- > > *Michael J Wise* > Microsoft Corporation| Spam Analysis > > "Your Spam Specimen Has Been Processed." > > Open a ticket for Hotmail <http://go.microsoft.com/fwlink/?LinkID=614866> > ? > > > > *From:* mailop <mailop-boun...@mailop.org> *On Behalf Of *Fernando MM via > mailop > *Sent:* Wednesday, December 4, 2024 2:58 AM > *To:* Mailop <mailop@mailop.org> > *Subject:* [EXTERNAL] [mailop] Any tips on how to escalate a request in > Outlook.com? > > > > Hi, > > I was wondering if anyone has experienced a similar issue and was able to > fix it, or if you have any tips on how to escalate a ticket in Outlook.com. > > For the past year, our IPs have been getting blocked every 2–3 months by > Outlook.com. What happens is: > > > > 1) Start getting the error "550 5.7.1 Unfortunately, messages from > [x.x.x.x] weren't sent. Please contact your Internet service provider since > part of their network is on our block list (S3150). You can also refer your > provider to http://mail.live.com/mail/troubleshooting.aspx#errors."; > > > > 2) Open a ticket at https://olcsupport.office.com/ > > > > 3) Receive the first response with "Nothing was detected to prevent your > mail from reaching Outlook.com customers." > > > > 4) Send the error message and ask them to investigate. > > > > 5) Finally receive the message "We have implemented mitigation for your IP > (x.x.x.x) and this process may take 24 - 48 hours to replicate completely > throughout our system." > > > > 6) Wait 2-3 months and start over > > > > Asking them to escalate the request or for more information leads to > nowhere since they always respond with "I do apologize, but I am unable to > provide any details about this situation since we do not have the liberty > to discuss the nature of the block.". > > > > Some additional information: > > > > - DKIM, SPF, DMARC are correctly configured. > > - JMPR is working. Very low number of spam reports as we mainly send > invoices, orders confirmation and order delivery updates for different > companies. > > - We have no issues with other providers: not listed in any RBLs, in > gmail.com all the IPs have high reputation, etc. > > > > Since we manage hundreds of IPs, at some point we even had to create a bot > to submit/respond to the tickets automatically with ChatGPT. > > > > It works fine but since the mitigation takes 24-48 hours, we have to > temporarily rotate the IPs so that messages are delivered. > > > > Thanks, > > > > Fernando > > > > > > > > > > > > >
_______________________________________________ mailop mailing list mailop@mailop.org https://list.mailop.org/listinfo/mailop
