Hi, I’m Hunter Perrin, and I made a new email service called Port87.

Gmail was a great email service back in 2006, but now it just sucks. They put ads in your inbox that look like unread emails to trick you into clicking them. To me, that means Gmail is malware.

I’ve been degoogling my life for the past 7 years, and Gmail is the last Google service I depended on. I love ProtonMail and use it too, but I developed a new way to sort email automatically, and wanted to write my own service based on it.

Port87 lets you use a tagged address like yourname-netflix@port87.com, and that automically creates a “netflix” label and puts all email to that address in it. This helps keep your email organized automatically, and protects against spam and phishing.

The database abstraction library I wrote for Port87 is called Nymph.js, and it’s open source. Also the UI library I wrote is called Svelte Material UI, and it’s open source too.

I hope you all like it, and hopefully it can help migrate away from Gmail.

  • hperrin@lemmy.worldOP
    link
    fedilink
    arrow-up
    2
    arrow-down
    1
    ·
    1 year ago

    I’ve never used Fastmail, so I don’t know what it’s like. You’re welcome to try mine out, and if there’s something you would like me to add, I’m open to suggestions. :)

    So the 100% spam block rate is talking about the prototype, which is what I was doing with ProtonMail and my Gmail account (which is where I prototyped the screening system). I’ve never gotten spam in my inbox in those places since I set up these systems. I’m not saying it’s impervious to spam, but I am saying spamming it is not really easy. If you start to get spam in a label, you can just block that label and change your address to a new label’s address for whatever account that is.

    • evulhotdog@lemmy.world
      link
      fedilink
      arrow-up
      8
      arrow-down
      1
      ·
      1 year ago

      This is where I think the flaw is in your system. You wouldn’t necessarily want to give your friends evul-friends@foo.com. Because once you start getting spam to it, you can’t nuke the email, because more then one person has it.

      This is why one address per recipient or service makes the most sense. Not user defined, but completely random or maybe what the Fastmail automated emails do.

      I suggest doing some market research before building your product/service so you are designing something that has the best fit for your consumer, and I think Fastmail handles things better than your service would right now, based upon what you’ve shared.

      • hperrin@lemmy.worldOP
        link
        fedilink
        arrow-up
        1
        arrow-down
        2
        ·
        edit-2
        1 year ago

        That’s why you’d use screening on evul-friends@foo.com. Spam mail generally doesn’t have a valid Return-Path, and if it does, it’s probably not a monitored mailbox, so the spammer wouldn’t even receive the screening email, let alone follow the instructions in it.

        (By not valid, I mean a return path that leads to an actual mailbox. It can be a valid email address, just a bogus or spoofed one.)

        • beetus@lemmy.world
          link
          fedilink
          arrow-up
          4
          ·
          edit-2
          1 year ago

          I think you are misconstruing spam in this context.

          While you are right about “spam” mail not meeting valid header details or authentication, a lot of “spammy” content does - marketing emails.

          fastmails aliased emails allow for users to generate unique email addresses for each individual service they sign up for. What this enables is that when that service inevitably sells that email address to another spammy, potentially legitimate, but still spammy provider. They can then unsubscribe from that alias email entirely.

          What you are describing seems less focused on protecting one address from being sold and shared. I think you need to accommodate for the fact that businesses sell lists of email addresses against their users wishes. That use case doesn’t seem to be met yet

          • hperrin@lemmy.worldOP
            link
            fedilink
            arrow-up
            1
            arrow-down
            1
            ·
            1 year ago

            You can block a label in Port87. So, if some place sells the address you gave them, you can block that label, and that address will start rejecting emails. The error response that is returned to their server is “that mailbox doesn’t exist”, so if they look at the bounce message (which they almost definitely won’t do), it will look like that email address was deleted.

            • beetus@lemmy.world
              link
              fedilink
              arrow-up
              3
              ·
              1 year ago

              Yeah but your pattern is to re use labels (eg: beetus-friends@port87.com). If you suggest users reuse the labels they lose their effectiveness in working as aliases.

              You are designing for a different feature set, I see this, however I think you may have some blind spots with what other email inbox providers offer and what users are looking for.

              Good luck on the journey, your product already seems quite feature rich :)

              • hperrin@lemmy.worldOP
                link
                fedilink
                arrow-up
                1
                ·
                1 year ago

                Yes, you would reuse a label like “friends” to give out to all your friends, but you’d also enable screening on that label, so any automated sender (spam is almost always sent by automated senders) wouldn’t pass the screening challenge, and their email wouldn’t be delivered.

                So there are basically two different types of labels, one for bots and one for people. The bot ones should be single sender, something like “netflix”, and the people ones can be single sender like “davesmith” or multiple like “bookclub”, and you can enable screening on them.