Skip to content

FireFish5000

My feedback

4 results found

  1. 8 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    FireFish5000 commented  · 

    I'd prefer integration with simplelogin to be at the same level as mail alias is. Where instead of this unnecessary reverse-alias redirect to/from simplelogin which is also running on proton, we just plain receive it into our inbox if the alias is enabled and can plain send an email as the alias using the alias's own pgp key.

  2. 99 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    FireFish5000 supported this idea  · 
    An error occurred while saving the comment
    FireFish5000 commented  · 

    I seriously question why simplelogin has unlimited alias and proton has only 15 when simplelogin is hosted on proton (or are they not). (I also have a custom domain btw). With reverse-aliasing and unnecessary extra step of forwarding to my actual mailbox, I can only imagine simplelogin as being more computationally intensive on the backend then an actual alias would be.

    I'd personally be fine though with simple login if integration was better (like the same level as alias, where you can send from with pgp key attatched and see icons for the sender). Currently using SL for everything with my proton email just being the mailbox and domain I login to and tell no one about.

  3. 1,252 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    FireFish5000 supported this idea  · 
    An error occurred while saving the comment
    FireFish5000 commented  · 

    Contacts having phone number support without contacts having an app for phone kinda threw me off. +1.

    Would help make migrating from another provider easier. Without this another provider's contacts app has to be used(like google/apple) for phone/daily life and keeping proton's contacts up to date thus becomes a dubious chore.

  4. 35 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    How important is this to you?

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)
    An error occurred while saving the comment
    FireFish5000 commented  · 

    FWIW, this feature is actualy documented as if it already exists in the variables sections of the docs

    https://proton.me/support/sieve-advanced-custom-filters#creating-variables

    https://proton.me/support/sieve-advanced-custom-filters#transforming-variables

    Last example they provide is supposed to label based on the sender's address character count plus some math. Definitely not something your expected to create labels for beforehand.

    require "variables";
    require "fileinto";
    require "vnd.proton.eval";
    # do a match test on the sender address
    if header :matches "from" "*" {
    # create a variable called length, containing the length of the first
    # matching variable
    set :length "length" "${1}";
    # Create a variable called fileintovar containing the result of the expression written below
    set :eval "fileintovar" "${length} * 25 - 1 / 8+3";
    fileinto "${fileintovar}";
    }

    That said, none of the 3 examples would work in practice as documented since proton uses fileinto for both folders and labels. But if they added some small extensions to the language `fileinto :create :folder "${1}"` and `fileinto :create :label "${1}"` and modified the docs it should work and be backwards compatible since all new features would only be enabled by more explicit syntax.

    I, like the docs, find this to be "The most interesting use case of variables".

    FireFish5000 supported this idea  · 

Feedback and Knowledge Base