If the sender has established reputation on previous IP address(es), you might be able to ask for the "preemptive accommodation" form. I've never tried it under these specific circumstances, but it could be a workaround.
Luke On Fri, Apr 10, 2020 at 1:02 PM Brad Slavin via mailop <mailop@mailop.org> wrote: > Happy Quarantine Friday to all... > > I have spent almost two weeks in groundhogs day with SNDS and AWS IPs > trying to get 10 clean IPs in the Frankfurt and Oregon regions. > > My conclusion is that AWS IPs are almost impossible to provision that are > clean on SNDS. And even if you request removal from the SNDS blocked list > the response from MS is that the IPs cannot be mitigated. > > Its painful, time consuming and nearly fruitless. I have tried over 300 > IP's, a lot of these are blacklisted on other lists so I did not even both > but of the 180 that were submitted to SNDS... I got four that were clean. > > You have to request rdns, which takes a day. > Then monitor against all publishing blacklists - this takes a few hours > Add to SNDS - wait 24-36 hours for a result. > Find the blocked IP's > Request removal of the rdns from AWS or you cant release the IPs from your > account. > Remove from SNDS > > I get that people recycle AWS IPs and burn their reputations, but is there > any way to work with Microsoft and let them know that this address is > associated with a completely new customer? (Yes I know that spammers can > setup multiple accounts) ... is this Microsoft just being anti-competitive > with AWS/Azure or is there a timeline that IP's can be placed on so that if > there has not been email sent that MS will reconsider? > > Other than BYOIP or moving from AWS what is the way forward? > > Brad > > > > _______________________________________________ > mailop mailing list > mailop@mailop.org > https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop >
_______________________________________________ mailop mailing list mailop@mailop.org https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
