D

My feedback

  1. 32 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    6 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    D supported this idea  · 
    An error occurred while saving the comment
    D commented  · 

    While I'd like this too, there is the complication that spamgourmet owns many domains. I don't use *.me@spamgourmet.com, but rather *.me@<other-spamgourmet-domain>.net.

    There was at one time the ability to use one's own domain as a spamgourmet domain (see their FAQ). I did contact the dev's to let me use one of my domains, but I didn't get any response.

  2. 7 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    1 comment  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    D supported this idea  · 
    An error occurred while saving the comment
    D commented  · 

    Good point, I missed it too.

    Note that when we verify a domain, which I did via a txt record, we are then told we can delete the record. What happens if the domain changes hands? I'd suggest the txt record should stay and that it should be checked before new notifications.

  3. 116 votes
    Vote
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    8 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
    An error occurred while saving the comment
    D commented  · 
    An error occurred while saving the comment
    D commented  · 

    I'm concerned only with #2: Option to monitor a domain. If we leave the TXT record in the domain, then perhaps you could alert us when there is any new breach containing emails from that domain.

Feedback and Knowledge Base