4 ms·
We can agree to disagree here. You have no recourse when one of the Sendgrid shared IPs you are using gets put on Spamcop. Sendgrid might get around to working
by karmicthreat 6y ago
We can agree to disagree here. You have no recourse when one of the Sendgrid shared IPs you are using gets put on Spamcop. Sendgrid might get around to working with them to remove it in a couple weeks. You also have no way to eliminate that IP from your pool of IPs. So in my case about 40% of reports I was sending out were getting blocked at the email server of the receiver.
Buying a private IP is your only recourse. Unless your emails don't matter, in which case it might be fine to lose 40% of them.
- yread 6y agoThis is my experience as well. Submitted a support request, after a week got told "we're working on it" while my users were not receiving email address confirmation emails. Moved away from SendGrid very quickly after that.
- karmicthreat 6y agoI have some legacy IoT devices in the field that directly talk to sendgrid. Would be a big pain if I had to recredential them. So I stayed on sendgrid. My newer devices get their email proxied through a proxy I host. It was a dumb mistake on my part to tie myself to so tightly to a SaaS vendor.
- iamacyborg 6y agoHow much worse do you think it'd be if you had a static IP and were essentially having to manage your own sender rep yourself? Google and microsoft postmasters are unlikely to pay much attention to someone running an IP maybe sending a few thousand emails a day.