search

Trustroots / trustroots

Travellers' community for sharing, hosting and getting people together.
https://www.trustroots.org
GNU Affero General Public License v3.0
398 stars 137 forks source link

emails might end up in spam #96

Closed guaka closed 8 years ago

guaka commented 9 years ago

happened to Erga

looks fine:

to do:

simison commented 9 years ago

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 commented 9 years ago

Related to slow mails #38

CRCulver commented 9 years ago

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 commented 9 years ago

@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 commented 9 years ago

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

CRCulver commented 9 years ago

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

simison commented 9 years ago

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

CRCulver commented 9 years ago

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 commented 9 years ago

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 commented 9 years ago

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 notifications@github.com 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 https://github.com/Trustroots/trustroots/issues/96#issuecomment-68181833 .

CRCulver commented 9 years ago

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 check-auth@verifier.port25.com to see what it reports?

guaka commented 9 years ago

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

simison commented 9 years ago

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 commented 9 years ago

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 notifications@github.com 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 https://github.com/Trustroots/trustroots/issues/96#issuecomment-68703037 .

simison commented 9 years ago

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

chmac commented 9 years ago

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 commented 9 years ago

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

Why not mikael@ to my mail, too.

chmac commented 9 years ago

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 commented 9 years ago

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

simison commented 9 years ago

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

simison commented 9 years ago

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 commented 9 years ago

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

I like hello@

simison commented 9 years ago

@chmac, hello@ is forwarded for us three?

guaka commented 9 years ago

"Unsubscribe kasper@trustroots.org from LinkedIn invitation reminders?" yes! :)

chmac commented 9 years ago

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 commented 9 years ago

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 notifications@github.com 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 https://github.com/Trustroots/trustroots/issues/96#issuecomment-74691060 .

simison commented 9 years ago

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 commented 9 years ago

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 commented 9 years ago

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 commented 9 years ago

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 commented 9 years ago

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

simison commented 8 years ago

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