Rules

• Use random 20 digits and letters as the prefix for the address. This keeps it impossible for anyone to guess. For example if you choose battle@frii.day for battlenet, then battlenet probably knows you have a facebook@frii.day.
• One alias per service so you know where spam is coming from
• Delete emails after you process them. This keeps you from having to worry about storage limits and lets you read the emails without having to mark them unread after if you want to delay processing.
• Do not mark any emails as spam because you will damage simplelogin / addy.io reputation.
  • Setup anti spam rules to allow all emails from (add more depending on the alias domain you choose):
    • simplelogin.co
    • anonaddy.com
  • Your options instead are:
    • Disable the alias where the spam arrived from
    • Report the spam to the alias service
• Setup a catch all so attackers can't tell if your email addresses are real or fake because all requests return a 200. However, this will autogenerate aliases, so probably just going to turn it off. Guessing the actual randomly generated emails is infeasable anyway.
• Always email directly to the reverse alias for the contact, if you email them directly you will leak your actual email.

Helper

tr -dc 'a-z0-9' </dev/urandom | head -c20;echo