[mtmail]

https://postmarkapp.com/ warned us a 0.1% complaint rate. A stern warning. "For transactional email spam complaints should not exceed 10 complaints in 10,000 emails sent and we're seeing much higher in your activity. This is an expectation that many ISPs have set, which we work very hard to uphold. "

We now use their API to forward any complaint to us to doublecheck, we became paranoid to keep the number lower.

We're very happy with postmarkapp.

Somebody was using random IPs, but real email addresses to signup. We don't know why, it never led to pageviews later. Maybe it was an attempt to check which user (email address) clicks the link in the confirmation email of a service they haven't signed up for. I can understand if such users click 'this is spam' which then gets reported back by the big email providers to postmarkapp.

[I_dev_outdoors]

I'm having the same issue with a project I'm working on. Did you end up doing anything to mitigate random signups with fake emails? For me, they all follow the same pattern so I can usually guess which users are fake but I haven't been able to programmatically block them yet.

[4d66ba06]

Any chance the user agents are the same? On some form spam I've seen often only a few user agents with some really old browser versions are used.

[I_dev_outdoors]

Yes and no. It looks like there are at least two different tools creating users on my platform. One of them looks likes it's using chromedriver, and the other one has a varying user agent but some other constant things that they do.

In my case, it's pretty easy to tell a real user from who has an email that matches up with the username and what form they used to signup.

[wilsmex]

Thanks for info here. Definitely will look into them. I'll also have to look into if MG has some webhook for complaints, as we're also now suddenly super paranoid about that metric.