Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Buoy features not working #4

Open
havengoer opened this issue Mar 29, 2017 · 6 comments
Open

Buoy features not working #4

havengoer opened this issue Mar 29, 2017 · 6 comments
Assignees
Labels

Comments

@havengoer
Copy link
Collaborator

  • map location
  • voice/video recording
  • text notification doesn't have the proper link
@havengoer havengoer added the bug label Mar 29, 2017
@christyleos
Copy link
Member

This should help https://github.com/betterangels/buoy/wiki/Submitting-a-bug-report

@the-phoebe
Copy link
Collaborator

OK, here goes my breakdown of Buoy (cover page), then delving into the issues with various parts of the on boarding process (pages 1-5)

https://drive.google.com/file/d/0B5lzGDr3bT1XdnBudlRxQ1RGeDg/view?usp=sharing

First and most importantly though is to figure out how to keep the Buoy invites (sent to Crisis Response Team members) from getting routed immediately to the Junk folder. In the CRT member's Junk folder, the invite shows the sender as "[email protected]". I wonder if it has anything to do with the domain name (after the "@" symbol)?

Page 1: (1a) and (1b) - issue: email routed to Spam folder
Page 5: (1b) - issue: never ending "loading" status
(2b) - issue: map/GPS location not showing
(3b) - issue: "record" button(s) not working
(4b) - issue: "video recording" button not working
(5b) - issue: tlk.io chat not working (I sent a message from "menchies" (my bf's phone) saying "u ok?", but I never got this message on my phone; then I sent a message from my phone in the tlk.io chat to "menchies", but this message was never received on his phone) (edited)

^^ these are all of the issues/bugs with Buoy. Getting these things worked out/fixed is kind of crucial since it is one of the MVP features of our app. I have no familiarity at all with how to go about fixing those things, so we def need someone with technical knowledge of how to go about fixing these issues

@christyleos
Copy link
Member

Thank you @the-phoebe for staying on top of this - a great bug report takes time and I like the ones you posted to the list.

Do you need to test w/ someone? I can take some time to test w/ you, just let me know when would work.

@the-phoebe
Copy link
Collaborator

Thanks Christy! I checked out the thread with info on keeping our emails from getting routed to Spam and ran a report. Here are the results:

This message is an automatic response from isNOTspam's authentication verifier service. The service allows email senders to perform a simple check of various sender authentication mechanisms. It is provided free of charge, in the hope that it is useful to the email community. While it is not officially supported, we welcome any feedback you may have at .

Thank you for using isNOTspam.

The isNOTspam team

==========================================================
Summary of Results

SPF Check : pass
Sender-ID Check : pass
DKIM Check : neutral
SpamAssassin Check : ham (non-spam)

Details:

HELO hostname: gateway23.websitewelcome.com
Source IP: 192.185.49.180
mail-from: [email protected]
Anonymous To: [email protected]

SPF check details:

Result: pass
ID(s) verified: smtp.mail=[email protected]
DNS record(s):
carryon.online. 13523 IN TXT "v=spf1 a mx include:websitewelcome.com ~all"


Sender-ID check details:

Result: pass

ID(s) verified: smtp.mail=[email protected]
DNS record(s):
carryon.online. 13523 IN TXT "v=spf1 a mx include:websitewelcome.com ~all"


DKIM check details:

Result: neutral (message not signed)
ID(s) verified: header.From=[email protected]
Selector=
domain=
DomainKeys DNS Record=


SpamAssassin check details:

SpamAssassin 3.4.1 (2015-04-28)

Result: ham (non-spam) (03.7points, 10.0 required)

pts rule name description


  • -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no
  • trust
  • [192.185.49.180 listed in list.dnswl.org]
  • 3.5 BAYES_99 BODY: Bayes spam probability is 99 to 100%
  • [score: 1.0000]
  • 0.0 HEADER_FROM_DIFFERENT_DOMAINS From and EnvelopeFrom 2nd level mail
  • domains are different
  • -0.0 SPF_PASS SPF: sender matches SPF record
  • 0.2 BAYES_999 BODY: Bayes spam probability is 99.9 to 100%
  • [score: 1.0000]
    X-Spam-Status: Yes, hits=3.7 required=-20.0 tests=BAYES_99,BAYES_999,
    HEADER_FROM_DIFFERENT_DOMAINS,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=no
    autolearn_force=no version=3.4.0
    X-Spam-Score: 3.7

To learn more about the terms used in the SpamAssassin report, please search
here: http://wiki.apache.org/spamassassin/

==========================================================
Explanation of the possible results (adapted from
draft-kucherawy-sender-auth-header-04.txt):

"pass"
the message passed the authentication test.

"fail"
the message failed the authentication test.

"softfail"
the message failed the authentication test, and the authentication
method has either an explicit or implicit policy which doesn't require
successful authentication of all messages from that domain.

"neutral"
the authentication method completed without errors, but was unable
to reach either a positive or a negative result about the message.

"temperror"
a temporary (recoverable) error occurred attempting to authenticate
the sender; either the process couldn't be completed locally, or
there was a temporary failure retrieving data required for the
authentication. A later retry may produce a more final result.

"permerror"
a permanent (unrecoverable) error occurred attempting to
authenticate the sender; either the process couldn't be completed
locally, or there was a permanent failure retrieving data required
for the authentication.

==========================================================
Original Email

From [email protected] Tue Apr 04 00:12:23 2017
Return-path: [email protected]
X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on isnotspam.com
X-Spam-Flag: YES
X-Spam-Level: ***
X-Spam-Report:

  • -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no
  • trust
  • [192.185.49.180 listed in list.dnswl.org]
  • 3.5 BAYES_99 BODY: Bayes spam probability is 99 to 100%
  • [score: 1.0000]
  • 0.0 HEADER_FROM_DIFFERENT_DOMAINS From and EnvelopeFrom 2nd level mail
  • domains are different
  • -0.0 SPF_PASS SPF: sender matches SPF record
  • 0.2 BAYES_999 BODY: Bayes spam probability is 99.9 to 100%
  • [score: 1.0000]
    X-Spam-Status: Yes, hits=3.7 required=-20.0 tests=BAYES_99,BAYES_999,
    HEADER_FROM_DIFFERENT_DOMAINS,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=no
    autolearn_force=no version=3.4.0
    Envelope-to: [email protected]
    Delivery-date: Tue, 04 Apr 2017 00:12:23 +0000
    Received: from gateway23.websitewelcome.com ([192.185.49.180])
    by localhost.localdomain with esmtp (Exim 4.84_2)
    (envelope-from [email protected])
    id 1cvC58-000E7S-UY
    for [email protected]; Tue, 04 Apr 2017 00:12:23 +0000
    Received: from cm11.websitewelcome.com (cm11.websitewelcome.com [100.42.49.5])
    by gateway23.websitewelcome.com (Postfix) with ESMTP id 077AC1EBF6
    for [email protected]; Mon, 3 Apr 2017 19:12:30 -0500 (CDT)
    Received: from gator4097.hostgator.com ([192.185.4.109])
    by cmsmtp with SMTP
    id vBztcWrch5sV9vBztcGnbn; Mon, 03 Apr 2017 19:06:57 -0500
    Received: from havengoer by gator4097.hostgator.com with local (Exim 4.87)
    (envelope-from [email protected])
    id 1cvC0Q-0006v4-17
    for [email protected]; Mon, 03 Apr 2017 19:07:30 -0500
    To: [email protected]
    Subject: Phoebe invites you to join the Buoy emergency response alternative on Carry On!
    X-PHP-Script: carryon.online/wp-admin/post.php for 73.32.135.2
    Date: Tue, 4 Apr 2017 00:07:29 +0000
    From: WordPress [email protected]
    Message-ID: [email protected]
    X-Mailer: PHPMailer 5.2.22 (https://github.com/PHPMailer/PHPMailer)
    MIME-Version: 1.0
    Content-Type: text/plain; charset=UTF-8
    X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
    X-AntiAbuse: Primary Hostname - gator4097.hostgator.com
    X-AntiAbuse: Original Domain - isnotspam.com
    X-AntiAbuse: Originator/Caller UID/GID - [913 500] / [47 12]
    X-AntiAbuse: Sender Address Domain - gator4097.hostgator.com
    X-BWhitelist: no
    X-Source-IP:
    X-Exim-ID: 1cvC0Q-0006v4-17
    X-Source:
    X-Source-Args: /opt/php56/bin/php-cgi /home1/havengoer/carryon.online/wp-admin/post.php
    X-Source-Dir: hvngr.com:/carryon.online/wp-admin
    X-Source-Sender:
    X-Source-Auth: havengoer
    X-Email-Count: 3
    X-Source-Cap: aGF2ZW5nb2VyO2hhdmVuZ29lcjtnYXRvcjQwOTcuaG9zdGdhdG9yLmNvbQ==
    Buoy is a community-based crisis response system. It is designed to connect people in need with trusted friends, family, and other nearby allies who can help. We believe that in situations where traditional emergency services are not available, reliable, trustworthy, or sufficient, communities can come together to aid each other in times of need.

Phoebe wants you to join her crisis response team.

To join, sign up for an account here:

https://carryon.online/wp-login.php?action=register

@the-phoebe
Copy link
Collaborator

I think it has something to do with the DKIM check details: result: neutral (not signed) how do we go about fixing this?

@the-phoebe
Copy link
Collaborator

the-phoebe commented Apr 7, 2017

@havengoer did any of that ^^ make any sense to you? @_@

OO yeah and here's a link to the YouTube video I made demonstrating said issues: https://www.youtube.com/watch?v=I4Zpbpc3Iqs

Sound is muted bc I had hiccups at the time of filming. -_-

PS. After the first take of the video, I watched it and was like "eww my hands look all gross" (I'd been gardening all day, hands/cuticles were dry etc.) then I went and slapped some red nail polish on and reshot. Luckily, you can't see the imperfections of my rushed mani in the video... lol.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants