Found out that this was the result of some new features in our software digging up and using old sms email addresses. Consequently, we had the appearance of directory harvesting due to many bad numbers. Working that out, just wish the errors had been more clear in the error that this was "rate limiting" instead of just dropping us silently.
On Tue, Mar 12, 2019 at 3:25 PM Josiah Ritchie < [email protected]> wrote: > All our outbound mail servers have seen strange responses to messages to > sprintpcs.com, vmobl.com, sms.myboostmobile.com and message.ting.com. > They are delivered to postmark's spr-sms.mx.a.cloudfilter.net MX servers > and frequently given a 250 with the message "ESMTP server not available". > Our postfix servers assume that means delivered, but in testing we're > finding that they are not actually arriving. We're estimating approximately > 1/3rd of our messages to those domains are impacted. We do not see it on > other domains using cloudfilter.net. > > Example: > Mar 5 16:07:20 mailout-i-008204 postfix/smtp[14802]: 9DF126126B: to=< > [email protected]>, > relay=spr-sms.mx.a.cloudfilter.net[52.23.25.191]:25, > delay=2.9, delays=0.05/0/0.44/2.4, dsn=2.0.0, status=sent (250 2.0.0 ESMTP > server not available) > > Anyone know what is actually going on here? Seems like a conflicting > response and I'm not sure what they want me to think about it. > > Thanks, > Josiah Ritchie > -- Josiah Ritchie Church Community Builder (719) 266-2888
_______________________________________________ mailop mailing list [email protected] https://chilli.nosignal.org/cgi-bin/mailman/listinfo/mailop
