[driaug]

It is very hard to make statements about this. It very much depends on the reputation of your own domain (if you are not using our domain to send your emails) and the content of your emails if they will end up in spam. I have yet to see one of my own emails origination from @useplunk.com end up in somebody's spam folder! I believe that is a great start and further down the line (with more data) I may be able to make specific claims about it!

[eappleby]

It sounds like the free version sends emails from the useplunk.com domain. If that is the case and some of those emails get marked as spam, won't all emails from the useplunk.com domain be more likely to be identified as spam?

[aquark]

Do not use your own corporate domain for user generated content.

Source: been there, done that ... there is no benefit to it and only pain.

Have a separate plunk-emails.com domain that is used for all emails. Or even have a bunch set up and rotate through them. This will mitigate spam impact too -- you will get spam issues even with 100% legit users

[driaug]

I have built-in an automatic catch, if x% (still looking at what a good value for x is) of your emails bounce then your account gets quarantined and we see what we can do about that. That way we can prevent damage before other users get affected.

Does that make sense?

[djbusby]

Bounce is different than spam. Are you DMARC monitoring?

[driaug]

Sorry about the confusing wording, with bounce I mean both hard bounces, rejects and complaints (they are all monitored appropriately). They are all taken into account when calculating the % because they all have impact on the domain reputation.

[djbusby]

But how do you know a message lands in the SPAM folder in Google?

[driaug]

I believe email clients send back a rejection if it landed in spam. It is one of the metrics AWS SES can track for you.

https://docs.aws.amazon.com/ses/latest/dg/monitor-sending-ac...

[rglover]

Guessing you've already done it, but I worked on something loosely related to this a couple years back and best things you can do to avoid it are:

1. Make sure you've done DKIM and SPF verification via your SMTP provider.

2. Use an SMTP provider with a solid sender reputation (e.g., Postmark).

3. Help users keep lists clean. Aggressively handle bounces and make sure unsubscribe is easy to avoid spam complaints.

P.S. Dig the design/feel of everything. No immediate use but I've bookmarked to come back and give it a try when I do.