emails might end up in spam #96

guaka · 2014-12-25T11:40:37Z

happened to Erga

looks fine:

http://mxtoolbox.com/domain/trustroots.org/?source=findmonitors
trustroots.org. 86400 IN TXT "v=spf1 include:spf.mandrillapp.com ?all"

to do:

add warning Texts #14
plain text versions Plain text emails #92
include recipient's name at To field, not only email
include "unsubscribe" word into emails
add support info at email footer Add support contact to email footers #190
add contact info at email footer Add name, username and email address to email footers #189
...anything else?

The text was updated successfully, but these errors were encountered:

simison · 2014-12-25T11:49:09Z

I got quite a few reports about this already as well.

I thought adding dedicated IP would help (instead of free cloud IP we have now), but it turns out with low mail traffic it's more hard to keep reputation good.

simison · 2014-12-26T01:23:20Z

Related to slow mails #38

CRCulver · 2014-12-27T07:23:11Z

It might be worth implementing dkim on the mail server as well. I could do this if I access to the mail server and its DNS. I had to do this for my own server not long ago.

simison · 2014-12-27T09:44:51Z

@CRCulver we're using a gateway (Mandrill) to send all the mails so no problem at that side.

If no dedicated IP from Mandrill, the only option is to try technically/verbally improve the messages we send.

Let's also hope that over the enough time people click "not spam" at Gmail for our messages.

Meanwhile we've got warnings written at all important places.

simison · 2014-12-27T09:56:01Z

Oh and SPF/DKIM records are all set and ok.

CRCulver · 2014-12-27T15:28:35Z

When I query the DNS information for trustroots.org, I see a TXT-type record for SPF, but none for DKIM.

simison · 2014-12-27T15:34:34Z

Huh? Look for TXT record mandrill._domainkey.trustroots.org or validate it with the tool (enter "mandrill" and "trustroots.org")

CRCulver · 2014-12-27T15:38:14Z

When did you add it? Perhaps it hasn't propagated to the couple of DNS servers I queried. Anyway, I guess all is well.

simison · 2014-12-27T15:42:54Z

No, DKIM TXT record has been there for months.

Now I realised there's also possibility to add SPF type record (not just TXT). In my understanding TXT type should be enough, but now we've got both. Let's wait and see if this has any affect.

guaka · 2014-12-27T15:57:42Z

SPF is inside a TXT record.

Where is the DKIM?

I think it's good to remove ?all. That would only allow trustroots.org
emails coming from mandrillapp.com.

dig txt trustroots.org|grep spf
trustroots.org. 86388 IN TXT "v=spf1 include:spf.mandrillapp.com ?all"

On Sat, Dec 27, 2014 at 4:42 PM, Mikael Korpela [email protected]
wrote:

No, SPF TXT record has been there for months.

Now I realised there's also possibility to add SPF type record (not just
TXT). In my understanding TXT type should be enough, but now we've got
both. Let's wait and see if this has any affect.

—
Reply to this email directly or view it on GitHub
#96 (comment)
.

CRCulver · 2014-12-27T16:04:10Z

DKIM is also inside a TXT record. However, dig -t ANY on my own domain doesn't show my DKIM, though it shows the SPF, so I guess it is some kind of limitation of dig, and DKIM is set up fine on the trustroots.org DNS record.

By the way, have you sent an e-mail to [email protected] to see what it reports?

guaka · 2014-12-28T19:33:35Z

http://www.port25.com/support/authentication-center/email-verification/

- Text versions for several mails - Improve existing text versions - Add receiver’s name, helps with spam filters #96 - Wrap links to <> at text mails, should help with #83

simison · 2015-01-05T12:42:55Z

Humm! I just realised no-reply@ doesn't exist currently. @chmac

On the other hand this article suggests we should use something else. Thoughts/experiences?

We're obviously not going to collect no-reply mails anywhere but dev/null anyway. Bounce errors we would get from Nodemailer once we implement them properly.

guaka · 2015-01-05T13:30:51Z

otherwise, to get around the "marked as spam", use e.g.
kasper@tr for a while and forward that to my G inbox, I'll
filter and label it and check it once a day, if this improves the spam
situation by the end of the month we can move towards noreply@

On Mon, Jan 5, 2015 at 1:42 PM, Mikael Korpela [email protected]
wrote:

Humm! I just realised no-reply@ doesn't exist currently. @chmac
https://github.com/chmac

On the other hand this article
http://www.gettingemaildelivered.com/do-not-use-noreply-or-dontreply-as-your-from-return-address-in-email
suggests we should use something else. Thoughts/experiences?

We're obviously not going to collect no-reply mails anywhere but dev/null
anyway. Bounce errors we would get from Nodemailer once we implement them
properly.

—
Reply to this email directly or view it on GitHub
#96 (comment)
.

simison · 2015-01-05T14:01:20Z

@chmac @guaka does that forwarder already exist & can I switch to that right away?

chmac · 2015-01-05T15:31:40Z

I believe mail hits my mail host. If you want an alias configured and forwarded somewhere, just let me know what @ and where you want it to go...

simison · 2015-01-05T15:45:22Z

@chmac: kasper@ —> Kasper's Gmail, thanks. :-)

Why not mikael@ to my mail, too.

chmac · 2015-01-05T16:30:01Z

Done.

I also added Mikael to the forward for hello@ which I realise wasn't going to you previously. Hope I didn't miss any messages in there assuming you would answer them...

chmac · 2015-01-05T16:30:22Z

Whoops, realise this issue was not only about creating email aliases.

simison · 2015-01-05T17:24:09Z

@chmac I don't think hello@ was written down anywhere publicly earlier anyway?

simison · 2015-02-16T12:11:21Z

Looks like kasper@ as "from" address works better for spam stuff compared to noreply@ — interesting!

Let's change it to something more generic one that we'd also keep checking since people seem to sometimes reply mails directly for support. Additionally I'll add support contact more visibly to mails #190

hello@, from@, notification@, or ping@ — what do you think?

guaka · 2015-02-16T13:32:18Z

I don't get that many emails, I'm totally fine with average of less than 1 per week.

I like hello@

simison · 2015-02-16T15:58:33Z

@chmac, hello@ is forwarded for us three?

guaka · 2015-02-17T12:18:47Z

"Unsubscribe [email protected] from LinkedIn invitation reminders?" yes! :)

chmac · 2015-02-17T15:56:38Z

Just changed hello@ to reach all 3 of us. Going to be tricky to track how we reply. Maybe worth one of those online ticket type things? Or a single gmail account that we all log into from? Or we always CC the hello@ address when we reply? Or we solve the problem when we have it? :-)

guaka · 2015-02-17T16:04:36Z

with hitchwiki we cc contact@ most of the time, has worked
well enough the past years :)

On Tue, Feb 17, 2015 at 4:56 PM, Callum Macdonald [email protected]
wrote:

Just changed hello@ to reach all 3 of us. Going to be tricky to track how
we reply. Maybe worth one of those online ticket type things? Or a single
gmail account that we all log into from? Or we always CC the hello@
address when we reply? Or we solve the problem when we have it? :-)

—
Reply to this email directly or view it on GitHub
#96 (comment)
.

simison · 2015-02-17T16:30:40Z

I changed from-address to "hello" at production.

Yep, CC'ing works fine.

In any case you can expect me to be able to solve most of the support mails (they often need checking something from the DB), so you can wait for a few hours before replying them. Support mails from WP come now only to me.

I want to install some support/ticket thingy anyway just because it'd be so much easier to follow easier which mails I have replied and to have some basic reply templates at handy etc. #106

simison · 2015-02-27T20:15:09Z

http://mxtoolbox.com/domain/trustroots.org/?source=findmonitors
now gives:

Hostname has returned a SPF Record that has been deprecated

The use of alternative DNS RR types that was formerly supported during the experimental phase of SPF was discontinued in 2014. SPF records must now only be published as a DNS TXT (type 16) Resource Record (RR) [RFC1035]. See RFC7208 for further detail on this change.

According to RFC 7208 Section 3.1: During the period when SPF was in development, requirements for assigning a new DNS RR type were more stringent than they are today and support for the deployment of new DNS RR types was not deployed in DNS servers and provisioning systems. The end result was that developers of SPF discovered it was easier and more practical to follow the TXT RR type for SPF.

I'll look into it today.

chmac · 2015-02-27T20:37:13Z

I think the problem is that both of these commands return the same, but the second one should not return anything, as SPF as a type of records has been deprecated. So instead of having types like MX, and SPF, and TXT, it's now just TXT which contains an SPF string.

➜  ~  dig +short txt trustroots.org
"v=spf1 include:spf.mandrillapp.com ?all"
➜  ~  dig +short txt trustroots.org
"v=spf1 include:spf.mandrillapp.com ?all"

chmac · 2015-02-27T20:37:41Z

I guess the solution is just to remove the type=SPF record from the DNS server. Not sure who controls DNS though, maybe @guaka ?

simison · 2015-02-27T20:50:31Z

@chmac I removed type=SPF record now (and left type=TXT containing SPF record), thanks!

Less “hey” and “!” and make it look more like a confirmation mail.

simison · 2016-01-19T01:18:03Z

— to check at some point; https://sendgrid.com/blog/5-ways-check-sending-reputation/

guaka added bug labels Dec 25, 2014

simison added a commit that referenced this issue Dec 25, 2014

#96 #16 Add warning about spam-box

cb5e155

guaka modified the milestones: equinox, next up Dec 28, 2014

simison removed the prio:HIGH label Dec 28, 2014

guaka added the tech:email label Jan 2, 2015

simison added a commit that referenced this issue Jan 3, 2015

#96 Notice about spam box

3583cdd

chmac closed this as completed Jan 5, 2015

chmac reopened this Jan 5, 2015

simison added a commit that referenced this issue Jan 6, 2015

#96 Add "Trustroots" as a name for outbound emails

47993d2

simison mentioned this issue Apr 14, 2015

Add name, username and email address to email footers #189

Closed

simison added keep observing and removed bug labels Apr 14, 2015

simison added a commit that referenced this issue Sep 6, 2015

#96 Change signup email's copy slightly to help spam issue

108fe43

Less “hey” and “!” and make it look more like a confirmation mail.

simison closed this as completed Mar 3, 2016

simison added a commit that referenced this issue Mar 28, 2017

Add address to the email footer for spam-prevention #96

6e57659

simison added a commit that referenced this issue Mar 28, 2017

Add address to the email footer for spam-prevention #96

553edc7

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

emails might end up in spam #96

emails might end up in spam #96

guaka commented Dec 25, 2014 •

edited by simison

Loading

simison commented Dec 25, 2014

simison commented Dec 26, 2014

CRCulver commented Dec 27, 2014

simison commented Dec 27, 2014

simison commented Dec 27, 2014

CRCulver commented Dec 27, 2014

simison commented Dec 27, 2014

CRCulver commented Dec 27, 2014

simison commented Dec 27, 2014

guaka commented Dec 27, 2014

CRCulver commented Dec 27, 2014

guaka commented Dec 28, 2014

simison commented Jan 5, 2015

guaka commented Jan 5, 2015

simison commented Jan 5, 2015

chmac commented Jan 5, 2015

simison commented Jan 5, 2015

chmac commented Jan 5, 2015

chmac commented Jan 5, 2015

simison commented Jan 5, 2015

simison commented Feb 16, 2015

guaka commented Feb 16, 2015

simison commented Feb 16, 2015

guaka commented Feb 17, 2015

chmac commented Feb 17, 2015

guaka commented Feb 17, 2015

simison commented Feb 17, 2015

simison commented Feb 27, 2015

chmac commented Feb 27, 2015

chmac commented Feb 27, 2015

simison commented Feb 27, 2015 •

edited

Loading

simison commented Jan 19, 2016

emails might end up in spam #96

emails might end up in spam #96

Comments

guaka commented Dec 25, 2014 • edited by simison Loading

simison commented Dec 25, 2014

simison commented Dec 26, 2014

CRCulver commented Dec 27, 2014

simison commented Dec 27, 2014

simison commented Dec 27, 2014

CRCulver commented Dec 27, 2014

simison commented Dec 27, 2014

CRCulver commented Dec 27, 2014

simison commented Dec 27, 2014

guaka commented Dec 27, 2014

CRCulver commented Dec 27, 2014

guaka commented Dec 28, 2014

simison commented Jan 5, 2015

guaka commented Jan 5, 2015

simison commented Jan 5, 2015

chmac commented Jan 5, 2015

simison commented Jan 5, 2015

chmac commented Jan 5, 2015

chmac commented Jan 5, 2015

simison commented Jan 5, 2015

simison commented Feb 16, 2015

guaka commented Feb 16, 2015

simison commented Feb 16, 2015

guaka commented Feb 17, 2015

chmac commented Feb 17, 2015

guaka commented Feb 17, 2015

simison commented Feb 17, 2015

simison commented Feb 27, 2015

chmac commented Feb 27, 2015

chmac commented Feb 27, 2015

simison commented Feb 27, 2015 • edited Loading

simison commented Jan 19, 2016

guaka commented Dec 25, 2014 •

edited by simison

Loading

simison commented Feb 27, 2015 •

edited

Loading